Someone had made a change to the dhcp server and took option 066. Working now. Thanks

I tried editing the file and rebooted the server. Fog services no longer started. I will try to wait for the new version of Fog and only image 5 clients at a time…

Fog 1.5.4 crashes server when using a group deploy. Running Ubuntu 16.04 LTS. Happens every time. This was a clean installation of FOG. We have labs with 25 clients and this was never an issue with version 1.4.4.

Someone had made a change to the dhcp server and took option 066. Working now. Thanks

Thanks all good!

No. I have another server as my dhcp server. Here is a screenshot of the error:

After the upgrade to version 1.4.0 rc7 clients will no long pxe boot. TFTP open timeout error. Has anyone encountered this problem?

@mtanigawa
I had the same issues with the upgrade and was able to upgrade the schema with the link provided, but…
I had the same problem with my server not going to the normal http://xxx/fog/management/index.php login page.
I am fairly new to Linux. How did you change the apache dir.conf list order to put index.php to the front?

@mtanigawa said in Remove your webroot redirect to /fog when going to >= rc4:

http://xxx/fog/management/index.php?node=schemaupdater

I completed the fog installation by entering the full path http://xxx/fog/management/index.php?node=schemaupdater but had the same problem. After the installation was complete the normal http://xxx/fog/ did not resolve to the normal http://xxx/fog/management/index.php login page.
I am fairly new at Linux and am not sure how to change apache dir.conf list order. index.html.

Perfect! Thanks that worked!

Joe

We have always kept up to date with our fog servers. Went to upgrade trunk to version 1.4.0 rc4 and when it needs to update the database we get this - http://192.168.x.x/fog/management/?node=schema.

Nothing on the webpage. I am afraid to go any futher. I don’t want to mess up the database. I am using putty to do the update and it is waiting for me to hit Enter when the upgrade has updated.

Not sure how to continue. Has anyone had this issue?

Thanks

Joe