PXE Boot stopped working
-
I hate to throw this out there but did you disable windows firewall yet?
-
No firewalls on Windows boxes (via GPO) or the FOG server.
Just a reminder, the upload task works fine if I deploy the task instantly.
-
SO instant works but not delayed. have you tried cron-syle?
Sry currently testing the delayed on my configuration. I usually don’t use the delayed method. Just instant and cron-style.
Edit: delayed donate works for me. about 3 mins off from scheduled time thought. Most likely due to task check periods
-
I’m trying cron-style now. I set it up as 56, 13, 20, month, dow. That is, 1356 on the 20th, no month, no day of week. (I’m in California)
It is now 1407 and nothing.
-
YOu have Cron set to run, every 1:56 pm, on the 20th day. When did you set this? Do you set it before 1356?
-
Yes, at 1354
Edit: The task appeared in the scheduled tasks window
-
Okay,
What is the last 20 lines of:
[code]tail -20 /opt/fog/log/fogscheduler.log[/code] -
Here you are:
The clock looks wrong
[ATTACH]1614[/ATTACH]
I just ran the tail command again and the time did not change…
[url=“/_imported_xf_attachments/1/1614_FogSchedLog.png?:”]FogSchedLog.png[/url]
-
Precisely.
What’s the output of:
[code]date -u[/code]
-
[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
-
Tue Jan 20 22:37:20 UTC 2015
This looks correct
-
As the time of the log did not change does that indicate that something is not running?
-
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?
-
I’m leaving the office in a few minutes. Hopefully we can track this down tomorrow.
Thanks,
Geoff -
Yes, but there were the messages that I posted earlier.
-
Can you maybe restart the server? Hopefully it’ll help the timing too!
My guess is something is interferring
-
I just restarted apache2 and the three FOG services. The scheduler appears to be running. Let’s see what happens overnight.
Thanks
-
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/wolThe path in FOG Configuration->FOG Settings->General Settings->FOG_WOL_PATH = /fog/wol/wol.php.
Do I need to change the path?
-
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.
-
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.
