PXE Boot stopped working
-
This is good for the time zone.
However, for your error of “Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName.”
[SIZE=14px][quote][/quote][/SIZE][quote][SIZE=14px][FONT=UbuntuRegular][COLOR=#333333]If you insert a[/COLOR][/FONT][/SIZE]
[COLOR=#333333][FONT=Ubuntu Mono][SIZE=14px][COLOR=#222222]ServerName localhost[/COLOR][/SIZE][/FONT][/COLOR]
[FONT=UbuntuRegular][COLOR=#333333][SIZE=14px]in either [COLOR=#222222][FONT=Ubuntu Mono][SIZE=14px]httpd.conf[/SIZE][/FONT][/COLOR] or [COLOR=#222222][FONT=Ubuntu Mono][SIZE=14px]apache2.conf[/SIZE][/FONT][/COLOR] in [COLOR=#222222][FONT=Ubuntu Mono][SIZE=14px]/etc/apache2[/SIZE][/FONT][/COLOR] and restart apache the notice will disappear.[/SIZE][/COLOR][/FONT]
[/quote] -
Yes, I did that.
[S]The scheduled task now appears in the Active Tasks window.[/S]
My mistake. The scheduled task is not running.
I tried the client with a user logged in, at the ctl-alt-del screen, and with a reboot.
In the first two cases nothing happened. In the reboot it went through the PXE menu and by default booted from the hard drive
-
Any more ideas about getting the scheduled task deployment to work?
-
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
