So we’ve been imaging fine, everything AOK and snappy. We are using 1.1.2 at the moment and random machines now say

“Unable to Connect to Fog Storage Node”

when you prep them for imaging. The fog log shows:
[CODE][08-04-14 3:40:16 pm] | StorageNode Not found on this system.
[08-04-14 3:40:26 pm] | StorageNode Not found on this system.
[08-04-14 3:40:36 pm] | StorageNode Not found on this system.
[08-04-14 3:40:46 pm] | StorageNode Not found on this system.
[08-04-14 3:40:56 pm] | StorageNode Not found on this system.
[08-04-14 3:41:06 pm] | StorageNode Not found on this system.
[08-04-14 3:41:16 pm] * No tasks found!
[08-04-14 3:41:26 pm] * No tasks found!
[08-04-14 3:41:36 pm] | StorageNode Not found on this system.
[08-04-14 3:41:46 pm] | StorageNode Not found on this system.
[08-04-14 3:41:56 pm] | StorageNode Not found on this system.
[08-04-14 3:42:06 pm] | StorageNode Not found on this system.
[08-04-14 3:42:16 pm] | StorageNode Not found on this system.
[08-04-14 3:42:26 pm] * No tasks found!
[08-04-14 3:42:36 pm] * No tasks found!
[08-04-14 3:42:46 pm] * No tasks found!
[08-04-14 3:42:56 pm] * No tasks found!
[08-04-14 3:43:06 pm] * No tasks found!
[08-04-14 3:43:16 pm] | StorageNode Not found on this system.
[08-04-14 3:43:26 pm] * No tasks found!
[08-04-14 3:43:36 pm] * No tasks found!
[08-04-14 3:43:46 pm] * No tasks found!
[08-04-14 3:43:56 pm] * No tasks found!
[08-04-14 3:44:06 pm] * No tasks found!
[08-04-14 3:44:16 pm] * No tasks found![/CODE]

But the strange thing is:

A) its working on about 1/2 to 3/4 the machines.
B) if I reboot the fog server it works perfectly fine for 10 minutes
C) we haven’t change anything.

This is what I see in the apache log

[CODE][Mon Aug 04 13:05:14.045831 2014] [core:notice] [pid 1792] AH00051: child pid 13545 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Mon Aug 04 13:08:58.349566 2014] [core:notice] [pid 1792] AH00051: child pid 14350 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Mon Aug 04 13:08:58.349605 2014] [core:notice] [pid 1792] AH00051: child pid 14351 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Mon Aug 04 13:10:59.584328 2014] [core:notice] [pid 1792] AH00051: child pid 14519 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Mon Aug 04 13:11:24.010007 2014] [:error] [pid 14773] [client 10.34.100.54:49158] PHP Warning: require(…/commons/base.inc.php): failed to open stream: No such file or directory in /var/www/fog/service/servicemodule-active.php on line 2
[Mon Aug 04 13:11:24.010042 2014] [:error] [pid 14773] [client 10.34.100.54:49158] PHP Fatal error: require(): Failed opening required ‘…/commons/base.inc.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/service/servicemodule-active.php on line 2
[Mon Aug 04 13:11:24.613239 2014] [core:notice] [pid 1792] AH00051: child pid 14667 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Mon Aug 04 13:11:36.631632 2014] [core:notice] [pid 1792] AH00051: child pid 14333 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Mon Aug 04 13:11:36.631711 2014] [core:notice] [pid 1792] AH00051: child pid 14654 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[/CODE]

Do we have a bad server? Bug in fog code?.

Any thoughts? Any one seen this before? Most of my searches have turned up information about Storage Nodes that are completely wrong, rather than intermittent.

Also anyone know why the fog log time zone is off? Everything else on the server is in sync with system clock.

D

[edited to include apache log]

We have been having major issues getting our Dells to Chainload, and I was thinking about switching back to PXELinux but I really like iPXE so I did some digging on the iPXE website. This is working for us so far on our problem machines… we will be rolling our Fog subnet farther out but in the three locations where we are testing:

1. edit default.ipxe
   add a line at the end of the file:
   [CODE]chain http://10.x.x.x/fog/grub/grub.exe --config-file=“rootnoverify (hd0);chainloader +1”[/CODE]

2. Download the grub4dos executable from here:
   [URL=‘http://sourceforge.net/projects/grub4dos/files/GRUB4DOS/’]Grub4Dos[/URL]

As can be seen in my config I dumped it in the fog directory. iPXE seems to be working still and chainloading is now working in the test environment.

I pulled the code snippets from here:
[URL=‘http://ipxe.org/appnote/work_around_bios_halting_on_ipxe_exit’]BIOS Halt on iPXE[/URL]

If this helps folks let me know, or if it doesn’t work for you, also let me know. I’ll keep testing it from here.

-D

Ok I figured it out (Finally!) Netware 6.5 DHCP can’t/doesn’t pass the undionly.kpxe var correctly. Not sure if its because our scope is messed up, or if there is something deeper that is causing the issues… I bounced a temporary Windows DHCP server and things lit up (phew!)

Yeah that was my thought, but its still not working. Strangely I CAN tftp from a workstation on the same vmware host as the FOG server, but still not from my workstation

@TE I’ve searched google/forums pretty hard, and I’ve verified all the steps in the Wiki.

I’m beginning to think the issue is either with Ubuntu or with our network environment. I installed a squeaky clean empty Fog server onto Ubuntu 14. I still had 1.0.0 in my folder, but I upgraded to 1.0.1 and I am getting the exact same errors. To re-iterate out-of-the-box Ubuntu install, clean Fog install 1.0.0 -> 1.0.1 can’t TFTP from my desktop to the client, can’t PXE boot from a workstation.

(Prevision version was Ub 10 with .33b -> 1.0.0)

@Wolf if I restart I get: tftpd-hpa start/running, process 24585
-D

I tried changing it to 777 across the board with no effect.
-D

Been beating my head against a wall for too long on this one. Upgraded from .33b to 1.0 Everything went swimmingly until TFTP time. Specifically if I try and connect from a network computer I get:

[CODE]TFTP.
PXE-T01: File not found
PXE-E3B: TFTP Error-File not found
PXE-MOF: Exiting Intel PXE ROM[/CODE]

I’ve update my DHCP server to say Option 67: undionly.kpxe.
I’ve followed this [URL=‘http://fogproject.org/wiki/index.php?title=Upgrade_to_1.0.0’]Upgrade to 1.0.0[/URL] to ensure that my Fog TFTP settings are in line
I’ve changed my fog management password to reflect the local user password, and I’ve tested FTP to ensure that I can connect via FTP

My tftpd-hpa looks as such:
[CODE]TFTP_USERNAME=“fog”
TFTP_DIRECTORY=“/tftpboot”
TFTP_ADDRESS=“10.1.2.2:69”
TFTP_OPTIONS=“-s”[/CODE]

If I try and connect from my desktop to the TFTP server I get:
[CODE]F:>tftp 10.1.2.2 GET undionly.kpxe
Timeout occurred
Connect request failed[/CODE]

(but I can ping, http and SSH to the server from my desk)

I’ve ensured that TFTP-HPA is running and pointed at the right spot:

[CODE]root 3258 0.0 0.0 14808 304 ? Ss 13:36 0:00 /usr/sbin/in.tftpd --listen --user fog --address 10.1.2.2:69 -s /tftpboot[/CODE]

The TFTP boot folder is owned by fog:

[CODE]drwxr-xr-x 3 fog root 4.0K 2014-05-13 11:41 tftpboot[/CODE]

This is on Ubuntu 10. Obviously I’m missing something stupid, but I can’t figure out what.