PXE Boot stopped working
-
It does not need to be in quotes, though it doesn’t hurt it either.
-
Thanks for your quick replies.
-
I just tried a manual upload. I have been busy with something else and I wasn’t monitoring the progress. I thought it would have been done some time ago and the FOG server showed 99.85% complete. I looked at the client and it was displaying FOGFTP: login failed with user “fog” and incorrect password every few seconds.
I did not recognize the password it was attempting to use.
Where do I edit that password? Could it have something to do with the files I copied from trunk?
-
It would not have anything to do with the files you downloaded from trunk.
To fix, I would recommend changing the Unix user fog with:
[code]sudo passwd fog[/code] Specify your new password and confirm it as required.Then go to Storage Management Page->List All Nodes->Your relevant node->Management Password and change this password to what you changed in the above step.
Then, go to FOG Configuration Page->FOG Settings->TFTP Server->FOG_TFTP_FTP_PASSWORD. Set the password to the same you set above, then all should be back to operational.
Hopefully this helps.
-
OK. I have changed the password in all locations and a manual upload works fine. I can create an instant task, the client restarts and the upload completes successfully.
I still cannot run a delayed upload. The client is showing the Ctl-Alt-Del screen. The client machine does not restart.
How do I best troubleshoot this.
I don’t think this is related, it pertains to WOL. 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.
-
Is this before or after the delayed task has started?
-
The delayed task never shows that it has started. Actually, I’m not sure what I should see in Task Management. If I look at Scheduled Tasks I see the Upload task I just created. Under Active/Type I see Yes/Delayed. The task never appears in the Active Tasks window. It is now 10 minutes after the scheduled start time.
-
my guess is the time is off then.
Have you ensured the date.timezone setting of both the /etc/php5/apache/php.ini and /etc/php5/cli/php.ini were set, and that the FOG Services were all restarted after the apache service was restarted?
-
Yes, both php.ini files contain date.timezone=“America/Los_Angeles”. My path includes apache2, I assume that is OK.
I followed the steps you outlined and I restarted the FOG server.
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.”When I restart the FOG services I see this:
“Restarting FOG Computer Imaging Solution: FOGScheduler
start-stop-daemon: warning: failed to kill 939: no such process” [OK] -
[quote=“geoffpeters, post: 41043, member: 25329”]Yes, both php.ini files contain date.timezone=“America/Los_Angeles”. My path includes apache2, I assume that is OK.
I followed the steps you outlined and I restarted the FOG server.
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.”
[/quote]check this out you may want to look at those files again and change 127.0.1.1 to localhost
[url]http://askubuntu.com/questions/256013/could-not-reliably-determine-the-servers-fully-qualified-domain-name[/url] -
I fixed the ServerName problem.
I tried to insert screen shots of the php.ini files but it seems I don’t know how.
In any case it looks to me as if they are both correct.
-
Use the “More Options…” button
-
OK. how about these:
[ATTACH]1612[/ATTACH]
[ATTACH]1613[/ATTACH]
[url=“/_imported_xf_attachments/1/1612_apache2.png?:”]apache2.png[/url][url=“/_imported_xf_attachments/1/1613_cli.png?:”]cli.png[/url]
-
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.
