Posts made by arainero

@Tom-Elliott Do you think I should try updating to the latest trunk version or hold off on that for the time being?

@Tom-Elliott This is a Windows 7 image. There are two disks, the first one has the Win7 OS and the second one is the 1TB storage disk. So multipartition, all disk.

I have used these options before and never had a problem with a capture. This problem has only come to surface after my multicasting problem was fixed, from https://forums.fogproject.org/topic/6129/multicasting-stuck-on-starting-to-restore-image

In regards to my previous thread, I did change password for the FTP, FOG user, and FOG config to trouble shoot that problem before. I did change them back though. I am not sure if that would be related to this new problem or not as I can FTP in just fine.

@Wayne-Workman There is no encryption happening.

@Wayne-Workman I believe that youtube link is the one I supplied.

Here is a picture of the image settings screen. I used to use the default setting of 6 for compression, but now I have been experimenting when this problem started happening.

@Wayne-Workman Earthshaker is from a video game lol.

Where do you set what the image type is? I don’t believe I have ever seen a RAW option.

I am capturing Windows 7 machines with two hard drives.

It was short lived. After about 10 minutes this was displayed http://i.imgur.com/WnSPX10.jpg

@Wayne-Workman Here is a video of the ending of the capture process. As you can see, it finishes and starts right back up. We turned the computer off when it got to the calculating bitmap screen.

https://www.youtube.com/watch?v=cdoXnM_DHrw&feature=youtu.be&t=1m2s

I then made a folder in /images 1282015 (the of the name of the image) and moved the files from /images/dev/fcaa14310b5b/ to /images/1282015. I am now multicasting this to another computer to see if it works.

However, that won’t fix the root problem as you said.

I did notice that the files created in /images/dev/fcaa14310b5b/ were created as user root with rw-r–r-- permissions. I was able to move the files from /images/dev/fcaa14310b5b/ to /images via ftp. I was unable to move the files from /images to /images/1282015 via ftp. I had to use mv to move them.

It may be because I made the fold 1282015 as root and it is owned by root:root.

@Wayne-Workman I am taking another image now since the drive was filled up by the previous one. I will update again when I attempt this. As of right now I can FTP to those folders from a different computer.

@george1421 After the computer finishes taking the capture the computer does not shutdown or reboot. It just starts to take the capture again.

It doesn’t delete the image either, just keeps adding to it. The one drive is 60 GB and the other is 1 TB.

@Wayne-Workman “#!nj” is being reported. There are currently no active tasks, if that makes a difference with this test.

Here is the output of the command:0_1449550371121_fogout.txt (I had to upload it, it was being marked as spam)

@Wayne-Workman I did a test from a different PC and the problem still persists. When the upload finishes it immediately starts to reupload again.

Not sure if this matters or not, but I have the following settings set:

OS - Win7
Image Type - Multiple Partition - All Disks
Partition - Everything
Compression - 0
Protected - Unchecked
Image Enabled - Checked
Replicate - Unchecked

This is what I have used in the past and never had a problem.

@Wayne-Workman

• /images/.mntcheck exists

• The image directory is 777 and can FTP to it from other computers.

• Currently 1.7TB free of disk space. I am trying to take an image of at max ~1.1TB

I will try to do a test upload from a different computer now.

Hello,

After I start a capture on a computer FOG will start the capture process, but when the capture finishes the computer starts the process over again. In the past the computer would reboot and go back into the OS. It appears that the capture task is not being completed and goes into a loop.

I noticed that it adds to the image file and does not rewrite over it. Before when everything worked normally the file would be around ~1TB, now it is around ~1.5TB, I am using SVN version 5624.

I’m not sure which logs would be beneficial in this instance. Please let me know what you would like to see and I will gladly supply it.

Also, I had a side question. I noticed a new option called “Replicate”, is there any documentation about what it does?

Thank you for your time!

@Tom-Elliott What time works for you?

@Sebastian-Roth There is enough space and I don’t notice any errors while updating.

@Tom-Elliott Yes, after doing a multicast service restart I get:

[root@fogserv bin]# PHP Fatal error:  Call to undefined method MulticastManager::getBanner() in /opt/fog/service/FOGMulticastManager/FOGMulticastManager on line 14

@Sebastian-Roth I just updated to the latest trunk and attempted a multicast. The multicast failed and this was in the apache error log. I no longer have a multicast log from the drop down menu in the Log Viewer.

[Fri Nov 20 16:06:55 2015] [error] [client 192.168.1.2] Directory index forbidden by Options directive: /var/www/html/
[Fri Nov 20 22:20:30 2015] [notice] caught SIGTERM, shutting down
[Fri Nov 20 22:20:46 2015] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Nov 20 22:20:46 2015] [notice] Digest: generating secret for digest authentication ...
[Fri Nov 20 22:20:46 2015] [notice] Digest: done
[Fri Nov 20 22:20:46 2015] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.6.15 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips configured -- resuming normal operations
BFD: /var/www/html/fog/service/ipxe/bzImage: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage32: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss```

@Sebastian-Roth No, I do not know what to do next. I was waiting to see if anyone had any thoughts.

@Tom-Elliott Since we can rule out password mismatch not being the problem here, is there anything else you recommend to try next?

Thank you.

@Tom-Elliott The interface is eth0 for ifconfig and in the storage node. Here are some recent logs from Service Master:

[11-13-15 10:19:17 pm] FOGMulticastManager fork()ed child process (25996).
[11-13-15 10:19:17 pm] FOGMulticastManager child process (25996) is running.
[11-13-15 10:19:17 pm] FOGMulticastManager fork()ed child process (25997).
[11-13-15 10:19:17 pm] FOGMulticastManager child process (25997) is running.
[11-13-15 10:19:17 pm] FOGImageReplicator fork()ed child process (25998).
[11-13-15 10:19:17 pm] FOGImageReplicator child process (25998) is running.
[11-13-15 10:19:17 pm] FOGImageReplicator fork()ed child process (25999).
[11-13-15 10:19:17 pm] FOGImageReplicator child process (25999) is running.
[11-13-15 10:19:19 pm] FOGImageReplicator fork()ed child process (26001).
[11-13-15 10:19:19 pm] FOGImageReplicator child process (26001) is running.
[11-13-15 10:19:19 pm] FOGTaskScheduler child process (25995) exited with code 2                                                55.
[11-13-15 10:19:20 pm] FOGTaskScheduler fork()ed child process (26002).
[11-13-15 10:19:20 pm] FOGTaskScheduler child process (26002) is running.
[11-13-15 10:19:20 pm] FOGImageReplicator fork()ed child process (26003).
[11-13-15 10:19:20 pm] FOGImageReplicator child process (26003) is running.
[11-13-15 10:19:20 pm] FOGMulticastManager child process (25996) exited with cod                                                e 255.
[11-13-15 10:19:20 pm] FOGMulticastManager child process (25997) exited with cod                                                e 255.
[11-13-15 10:19:20 pm] FOGImageReplicator child process (25998) exited with code                                                 255.
[11-13-15 10:19:20 pm] FOGImageReplicator child process (25999) exited with code                                                 255.
[11-13-15 10:19:22 pm] FOGImageReplicator child process (26001) exited with code                                                 255.
[11-13-15 10:19:22 pm] FOGTaskScheduler fork()ed child process (26004).
[11-13-15 10:19:22 pm] FOGTaskScheduler child process (26004) is running.
[11-13-15 10:19:23 pm] FOGTaskScheduler child process (26002) exited with code 2                                                55.
[11-13-15 10:19:23 pm] FOGImageReplicator child process (26003) exited with code                                                 255.
[11-13-15 10:19:23 pm] FOGMulticastManager fork()ed child process (26005).
[11-13-15 10:19:23 pm] FOGMulticastManager child process (26005) is running.
[11-13-15 10:19:23 pm] FOGMulticastManager fork()ed child process (26006).
[11-13-15 10:19:23 pm] FOGMulticastManager child process (26006) is running.
[11-13-15 10:19:23 pm] FOGImageReplicator fork()ed child process (26007).
[11-13-15 10:19:23 pm] FOGImageReplicator child process (26007) is running.
[11-13-15 10:19:23 pm] FOGImageReplicator fork()ed child process (26008).
[11-13-15 10:19:23 pm] FOGImageReplicator child process (26008) is running.
[11-13-15 10:19:25 pm] FOGImageReplicator fork()ed child process (26009).
[11-13-15 10:19:25 pm] FOGImageReplicator child process (26009) is running.
[11-13-15 10:19:25 pm] FOGTaskScheduler child process (26004) exited with code 255.
[11-13-15 10:19:26 pm] FOGTaskScheduler fork()ed child process (26010).
[11-13-15 10:19:26 pm] FOGTaskScheduler child process (26010) is running.
[11-13-15 10:19:26 pm] FOGImageReplicator fork()ed child process (26011).
[11-13-15 10:19:26 pm] FOGImageReplicator child process (26011) is running.
[11-13-15 10:19:26 pm] FOGMulticastManager child process (26005) exited with code 255.
[11-13-15 10:19:26 pm] FOGMulticastManager child process (26006) exited with code 255.
[11-13-15 10:19:26 pm] FOGImageReplicator child process (26007) exited with code 255.
[11-13-15 10:19:26 pm] FOGImageReplicator child process (26008) exited with code 255.
[11-13-15 10:19:28 pm] FOGImageReplicator child process (26009) exited with code 255.