PXE Boot stopped working

[Tom Elliott]

Precisely.

What’s the output of:

[code]date -u[/code]

[Tom Elliott]

[quote=“Tom Elliott, post: 41082, member: 7271”]Precisely.

What’s the output of:

[code]date -u[/code][/quote]

My current is: Tue Jan 20 22:29:50 UTC 2015

[geoffpeters]

Tue Jan 20 22:37:20 UTC 2015

This looks correct

[geoffpeters]

As the time of the log did not change does that indicate that something is not running?

[Tom Elliott]

It looks like the service isn’t restarted properly.

WHen you edited the date.timezone stuff, did you restart apache2 and restart the related FOG Services?

[geoffpeters]

I’m leaving the office in a few minutes. Hopefully we can track this down tomorrow.

Thanks,
Geoff

[geoffpeters]

Yes, but there were the messages that I posted earlier.

[Tom Elliott]

Can you maybe restart the server? Hopefully it’ll help the timing too!

My guess is something is interferring

[geoffpeters]

I just restarted apache2 and the three FOG services. The scheduler appears to be running. Let’s see what happens overnight.

Thanks

[geoffpeters]

The scheduler is running.

I think the problem was due to this:
When I restart the apache2 service I get a message:
“Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName.”

I think apache2 did not restart.

When I added the ServerName localhost line to apache2.conf the apache2 service did restart.

One of the clients did not upload at the scheduled time. It was in sleep mode (S4?) and it did not wake.

Could this be the cause?:
If I search for wol.php I find it in two locations.
/var/www/fog/wol
/home/pmusfog/desktop/fog_1.2.0/packages/web/wol

The path in FOG Configuration->FOG Settings->General Settings->FOG_WOL_PATH = /fog/wol/wol.php.

Do I need to change the path?

[Tom Elliott]

I’m assuming you’re using updatedb and locate as your ‘finders’?

The one in /home/pmusfog/desktop/fog_1.2.0/ is just the extracted folder info. The correct one is the location in /var/www/fog/ as that’s your web directory.

The /fog/wol/wol.php is correct path unless you changed it somewhere else.

My guess is either S4 didn’t allow wakeup, or wol isn’t enabled on that system. I don’t know all the potential values or changes in your environment either. Maybe that system is on another subnet or vlan which the fog server wouldn’t be able to send the traffic to.

[geoffpeters]

As far as I know I did not change the path to /fog/wol/wol.php anywhere.

All workstations are on a single subnet with no vlans in place.

I’ll have to do some more testing with the WOL bit. That is the last thing I need to make the scheduled uploads work.

[geoffpeters]

I’m not sure which WOL options to choose to work with FOG.

For example, the Intel 82578DC NICs have there options:
Wake on Magic Packet
Wake on Magic Packet from Off State
Wake on Link
Wake on Pattern Match

[Wolfbane8653]

So your saying in your OS your NIC options are those. BUT What are your options in the BIOS. This is where WOL should first be enabled.

[geoffpeters]

The BIOS options are:

System Power Options
After Power Failure <Stay Off>
Wake on LAN from S5 <Power On>
ACPI Suspend State <S3 State>
S3 State Indicator <Blink>
S1 State Indicator <On>
Wake System from S5 <Disabled>
PCIe ASPM Support <Disabled>

Boot Device Priority
Network is first in list

[Tom Elliott]

Wake System from S5 <Disabled>

Can you enable?

[geoffpeters]

I believe this option is to wake at a user specified time.

I think the important option is Wake on LAN from S5 <Power On>

[geoffpeters]

Does FOG use a Magic Packet?

[Tom Elliott]

Yes, to use WakeOnLan it generates it as needed.

[geoffpeters]

When I schedule an upload task does FOG automatically send the packet or do I have to enable that somewhere?