Thank you Jamie.
I will keep that in mind. If I go that route, I could use all the help I can get.

Just for anyone who runs into this in the future you can use a clone zilla live usb stick to pxe boot the system to fog.

Takes a flash drive with 140mb of space and works really slick.

I had this issue with our 500B MT’s.

check the /images/dev folder for the temp files named after the mac address of the computer they came from

[quote=“Tom Elliott, post: 29356, member: 7271”]Try the command:
[code]sed -i ‘s/SELINUX=enforcing/SELINUX=disabled/’ /etc/selinux/config[/code]

Normally the /etc/sysconfig/selinux is just a symbolic link to /etc/selinux/config, but sometimes the link doesn’t happen and it becomes it’s own file.

Once you do the sed command, you will likely need to restart the system again.

Thanks[/quote]

Yes, that was it, selinux is now disabled. Thanks for the quick fix.

Thanks for your responses. I’ll be moving this to RHEL6 so this will probably help in case I have any issues. Thanks for all the work on FOG! Been using it for over 4 years and it has been a big help!

Found it, works correctly now. Thanks for all the Help!

🙂 it works for me thank you very much !!!

Time to update 🙂

[quote=“zacharylewis07, post: 29144, member: 24431”]Having Printer Issues Also…
I’ve installed FOG 1.1.0 with patches from svn version 1780, yet I’m still having issues with PrinterManager adding and removing printers. I have “Add and Remove” selected for all hosts under “Printers” in Host Management.

Experiencing the following…
[LIST]
[]Random comments in the FOG log: PrinterManager Service is disabled and I get no printers deployed at all.
[]When printers do finally decide to deploy, I can’t remove them afterwards without cleaning up the registry.
[/LIST]
Any help is greatly appreciated.

User since FOG 0.26 (Love the software)[/quote]

Did you upgrade from 0.32 or is this a “fresh” install of 1.1.0?

Can i try both? Or does it have to be a undionly.kpxe?

Also, after restarting my server every time to try these new files, when trying to hit the web GUI i get an unable to connect to database error - although i’ve put the password in the commons/config.php folder…it was workign previously

Okay…They are “In Progress” now.

Thanks,

Andy

All errors were related to FTP, realized my FTP client was connecting on port 22, not 21. VSFTPD would not connect on 21. I removed VSFTPD and installed ProFTP and it is working now! Images created!

[quote=“Junkhacker, post: 29161, member: 21583”]if you run
[FONT=Consolas]tftp x.x.x.x get default.ipxe[/FONT]
does it download the file?[/quote]

I see what I did. When updating the tftboot files I accidentally moved default.ipxe. Thanks!

You don’t need to wallow or anything. It happens, thats why you ask questions.

[quote=“Tom Elliott, post: 29051, member: 7271”]Change the document root of your apache information to /var/www[/quote]

I’ve changed the documentroot, but there’s no difference.

[CODE][Wed Jun 04 12:15:10.484125 2014] [:error] [pid 7062] [client 10.4.30.43:49221] PHP Warning: require(…/commons/base.inc.php): failed to open stream: No such file or directory in /var/www/fog/service/servicemodule-active.php on line 2
[Wed Jun 04 12:15:10.484155 2014] [:error] [pid 7062] [client 10.4.30.43:49221] PHP Fatal error: require(): Failed opening required ‘…/commons/base.inc.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/service/servicemodule-active.php on line 2
[Wed Jun 04 12:15:13.479323 2014] [:error] [pid 7091] [client 10.4.30.43:49220] PHP Warning: require(…/commons/base.inc.php): failed to open stream: No such file or directory in /var/www/fog/service/servicemodule-active.php on line 2
[Wed Jun 04 12:15:13.479352 2014] [:error] [pid 7091] [client 10.4.30.43:49220] PHP Fatal error: require(): Failed opening required ‘…/commons/base.inc.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/service/servicemodule-active.php on line 2
[Wed Jun 04 12:26:44.439631 2014] [:error] [pid 7157] [client 10.4.30.174:49235] PHP Warning: require(…/commons/base.inc.php): failed to open stream: No such file or directory in /var/www/fog/service/servicemodule-active.php on line 2
[Wed Jun 04 12:26:44.439661 2014] [:error] [pid 7157] [client 10.4.30.174:49235] PHP Fatal error: require(): Failed opening required ‘…/commons/base.inc.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/service/servicemodule-active.php on line 2
[Wed Jun 04 12:26:47.437465 2014] [:error] [pid 7121] [client 10.4.30.174:49234] PHP Warning: require(…/commons/base.inc.php): failed to open stream: No such file or directory in /var/www/fog/service/servicemodule-active.php on line 2
[Wed Jun 04 12:26:47.437494 2014] [:error] [pid 7121] [client 10.4.30.174:49234] PHP Fatal error: require(): Failed opening required ‘…/commons/base.inc.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/service/servicemodule-active.php on line 2
[Wed Jun 04 12:33:39.110303 2014] [:error] [pid 7199] [client 10.4.30.174:49184] PHP Warning: require(…/commons/base.inc.php): failed to open stream: No such file or directory in /var/www/fog/service/servicemodule-active.php on line 2
[Wed Jun 04 12:33:39.110333 2014] [:error] [pid 7199] [client 10.4.30.174:49184] PHP Fatal error: require(): Failed opening required ‘…/commons/base.inc.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/service/servicemodule-active.php on line 2
[/CODE]

Could these errors be made by clients with the old fog client installed?

Ahh thanks for that, I have another question but I’ll create a new thread for that 🙂

To add, actually it seems almost 100% stable with this modification, no crashes today…

Maybe the one crash after I made this change was a fluke and/or I had not rebooted yet, I cannot remember with all the different testing that I’ve been doing…

does each site have it’s own tftp server as well?

The MySQL Issues could play into account as much of the data Polled comes out of the database. So it’s not too surprising to see the issue. This may also explain why a reinstall seems to help fix some of the issues. Not a complete reinstall from scratch, just simply rerunning the installer in place.