PXE-E32 error, unable to boot to fog from pxe

[george1421]

@K.Hays said in [PXE-E32 error:

@george1421 the owner is fog.root but how do i check the access level?

ls -la will do that for you. it should be -rw-r--r-- 1 fog root

But as Tom said you would be better off upgrading to the trunk. Don’t let the not stable term scare you off.

[Tom Elliott]

@Wayne-Workman No it’s not, not if the user is using FOG 1.2.0.

[K.Hays]

@george1421 ill do whatever to fix the issue at hand. If you think updating it to trunk will do that, then so be it

[george1421]

@K.Hays said in [PXE-E32 error:

@george1421 ill do whatever to fix the issue at hand. If you think updating it to trunk will do that, then so be it

I don’t want to lead you on that it will for sure fix your issue. But you will then have a consistent build that we can support. While the 1.2.0 build is still supported I don’t have a 1.2.0 stable system any more to compare your system against. That is the case with most of the Mods here. I have been running the trunk build for almost a year now. My memory of 1.2.0 stable is getting pretty weak these days.

[K.Hays]

@george1421 ok so how would i upgrade to trunk then? preferably without losing my current configs.

[george1421]

@K.Hays said in [PXE-E32 error:

@george1421 ok so how would i upgrade to trunk then? preferably without losing my current configs.

If course make sure you have a solid backup of your FOG server and then follow this post https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

Just for clarity, you made reference to having an older version of FOG installed at your site. What version was that? If it was before 1.2.0 it may be a better idea to spin up a new FOG server instead of upgrading.

[K.Hays]

@george1421 The system has since been removed. I believe it was 0.32, but this fog server is not on the same machine.

[george1421]

@K.Hays OK as long as this was a fresh install of 1.2.0 then you are ok to upgrade.

[K.Hays]

@george1421 ok, Currently doing that now

[K.Hays]

@george1421 * Installing package: php5-json…Failed!

[Wayne Workman]

@K.Hays Look inside the bin directory (where the installfog.sh file is), you will find a error_log directory now. In there, there is an error log with the revision number appended to it. What’s at the bottom of that file?

[george1421]

@Wayne-Workman Just to note this is on ubuntu 12.04 from the OP.

[K.Hays]

@Wayne-Workman 7084

[Wayne Workman]

@K.Hays Right, so your current revision number is 7084, but inside that file are all the redirected outputs from the installation, and the last few lines will have info on the failure.

[K.Hays]

@Wayne-Workman Errors were encountered while processing:
/var/cache/apt/archives/apache2-bin_2.4.16-4+deb.sury.org~precise+4_i386.deb
/var/cache/apt/archives/apache2-data_2.4.16-4+deb.sury.org~precise+4_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
thats whats at the bottom sorry not 7084

[Wayne Workman]

@K.Hays said in [PXE-E32 error:

@Wayne-Workman Errors were encountered while processing:
/var/cache/apt/archives/apache2-bin_2.4.16-4+deb.sury.org~precise+4_i386.deb
/var/cache/apt/archives/apache2-data_2.4.16-4+deb.sury.org~precise+4_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
thats whats at the bottom sorry not 7084

@Tom-Elliott do you think this error is related to this: https://forums.fogproject.org/topic/7085/ubuntu-server-14-dhcp-fails

Also, @K-Hays please try re-running the installer now.

[Tom Elliott]

@Wayne-Workman I highly doubt it as its failing to install Apache.

[Wayne Workman]

@Tom-Elliott Right, my issue also started with that failing.

[K.Hays]

@Wayne-Workman now i got this
Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully

• Stopping FOG Computer Imaging Solution: FOGMulticastManager
  …done.
• Stopping FOG Computer Imaging Solution: FOGImageReplicator
  …done.
• Stopping FOG Computer Imaging Solution: FOGScheduler
  …done.
  mysql stop/waiting
  mysql start/running, process 25428
• Stopping web server apache2
• There are processes named ‘apache2’ running which do not match your pid file which are left untouched in the name of safety, Please review the situation by hand.

is this because i had my web gui open?

[Tom Elliott]

@Wayne-Workman I think it’s because he’s on an unsupported Ubuntu now. Lts is good for security but package lists trunk is expecting might not be available