Going to try going back to my snapshot just after server was created to see what’s happening there and try updating that to see if it is working after the update. I can go back and forth between snapshots to troubleshoot if anyone sees something.
Posts made by gwhitfield
-
RE: FOGMulticastManager won't start
-
RE: FOGMulticastManager won't start
@Sebastian-Roth I noticed in another forum using “aux” instead of ax gave a little more info so just in case it helps:
-
RE: FOGMulticastManager won't start
@Sebastian-Roth said in FOGMulticastManager won't start:
service mysql status
Sure doesn’t seem like a happy response:
edit: well, maybe happy after all since my one working server is giving essentially the same response
-
RE: FOGMulticastManager won't start
@Sebastian-Roth Please forgive my ignorance but how do I determine this? MySQL service is running
-
RE: FOGMulticastManager won't start
@gwhitfield Dang, deleted /opt/fog/ and re-run installer and now have no log files except for apache error logs. Have restarted several times, no luck at all here. Any ideas?
-
RE: FOGMulticastManager won't start
@gwhitfield Found this thread [ https://forums.fogproject.org/topic/7414/multicast-not-starting] and trying the solution there to delete /opt/fog/ and re-run the installer. Will update as needed.
-
RE: FOGMulticastManager won't start
@gwhitfield Noticed ServiceMaster log has entries that stop on 2016/05/18 - probably a day that I did a trunk update. Don’t know if that’s relevant but when I can’t get FOGMulticastManager, FOGImageReplicator, or FOGScheduler services to start it seems it could be related somehow, maybe?
-
RE: FOGMulticastManager won't start
@gwhitfield udp send/receive test in “Troubleshoot Downloading - Multicast” wiki article was successful. File was sent and received
-
FOGMulticastManager won't start
I have two different Ubuntu 14.0.4, Trunk 8088 servers that I can’t get to multicast. I’m working on an additional FOG server in each location so I can do the testing described in “Troubleshoot Downloading - Multicast” wiki article. I have already cleared database as described in article, re-run installer and rebooted several times - no luck. I can’t get FOG MulticastManager service to start, stop, or restart. Here’s last 20 entries in Apache Error logs:
[Mon Jun 13 11:51:00.859643 2016] [:error] [pid 25884] [client 192.168.1.251:64102] PHP Warning: fopen(/var/log/apache2/error.log): failed to open stream: Permission denied in /var/www/html/fog/status/logtoview.php on line 14, referer: http://192.168.132.19/fog/management/index.php?node=about&sub=logviewer [Mon Jun 13 11:51:00.948499 2016] [:error] [pid 25783] [client 192.168.1.251:64103] PHP Warning: fopen(/var/log/apache2/error.log): failed to open stream: Permission denied in /var/www/html/fog/status/logtoview.php on line 14, referer: http://192.168.132.19/fog/management/index.php?node=about&sub=logviewer [Mon Jun 13 11:51:03.014450 2016] [:error] [pid 25782] [client 192.168.1.251:64110] PHP Warning: fopen(/var/log/apache2/error.log): failed to open stream: Permission denied in /var/www/html/fog/status/logtoview.php on line 14, referer: http://192.168.132.19/fog/management/index.php?node=about&sub=logviewer [Mon Jun 13 11:51:05.316755 2016] [:error] [pid 25785] [client 192.168.1.251:64133] PHP Warning: fopen(/var/log/apache2/error.log): failed to open stream: Permission denied in /var/www/html/fog/status/logtoview.php on line 14, referer: http://192.168.132.19/fog/management/index.php?node=about&sub=logviewer [Mon Jun 13 11:51:08.817558 2016] [:error] [pid 25784] [client 192.168.1.251:64134] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 32, referer: http://192.168.132.19/fog/management/index.php?node=about&sub=logviewer [Mon Jun 13 11:51:08.853842 2016] [:error] [pid 26629] [client 192.168.1.251:64135] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 32, referer: http://192.168.132.19/fog/management/index.php?node=about&sub=logviewer [Mon Jun 13 11:51:10.949570 2016] [:error] [pid 25781] [client 192.168.1.251:64137] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 32, referer: http://192.168.132.19/fog/management/index.php?node=about&sub=logviewer [Mon Jun 13 11:51:10.983563 2016] [:error] [pid 25884] [client 192.168.1.251:64138] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 32, referer: http://192.168.132.19/fog/management/index.php?node=about&sub=logviewer [Mon Jun 13 11:51:11.039406 2016] [:error] [pid 25783] [client 192.168.1.251:64139] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 32, referer: http://192.168.132.19/fog/management/index.php?node=about&sub=logviewer [Mon Jun 13 11:51:11.087299 2016] [:error] [pid 25782] [client 192.168.1.251:64140] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 32, referer: http://192.168.132.19/fog/management/index.php?node=about&sub=logviewer [Mon Jun 13 11:51:13.069976 2016] [:error] [pid 25785] [client 192.168.1.251:64141] PHP Warning: PDO::__construct(): MySQL server has gone away in /var/www/html/fog/lib/db/pdodb.class.php on line 32, referer: http://192.168.132.19/fog/management/index.php?node=about&sub=logviewer [Mon Jun 13 11:51:13.296923 2016] [:error] [pid 25785] [client 192.168.1.251:64141] PHP Warning: fopen(/var/log/apache2/error.log): failed to open stream: Permission denied in /var/www/html/fog/status/logtoview.php on line 14, referer: http://192.168.132.19/fog/management/index.php?node=about&sub=logviewer [Mon Jun 13 11:51:15.424429 2016] [:error] [pid 25784] [client 192.168.1.251:64142] PHP Warning: fopen(/var/log/apache2/error.log): failed to open stream: Permission denied in /var/www/html/fog/status/logtoview.php on line 14, referer: http://192.168.132.19/fog/management/index.php?node=about&sub=logviewer [Mon Jun 13 11:51:15.983670 2016] [mpm_prefork:notice] [pid 1156] AH00169: caught SIGTERM, shutting down [Mon Jun 13 11:51:33.252823 2016] [mpm_prefork:notice] [pid 29140] AH00163: Apache/2.4.20 (Ubuntu) OpenSSL/1.0.2h configured -- resuming normal operations [Mon Jun 13 11:51:33.252889 2016] [core:notice] [pid 29140] AH00094: Command line: '/usr/sbin/apache2' [Mon Jun 13 11:52:27.771849 2016] [:error] [pid 29143] [client 192.168.1.251:64191] PHP Strict Standards: Only variables should be passed by reference in /var/www/html/fog/lib/pages/schemaupdaterpage.class.php on line 46, referer: http://192.168.132.19/fog/management/index.php?node=schema [Mon Jun 13 11:53:32.257703 2016] [mpm_prefork:notice] [pid 29140] AH00169: caught SIGTERM, shutting down [Mon Jun 13 11:53:51.418307 2016] [mpm_prefork:notice] [pid 1186] AH00163: Apache/2.4.20 (Ubuntu) OpenSSL/1.0.2h configured -- resuming normal operations [Mon Jun 13 11:53:51.418853 2016] [core:notice] [pid 1186] AH00094: Command line: '/usr/sbin/apache2'
FYI -192.168.1.251 is my machine that I’m using to view the GUI. Seems odd the Multicast log has nothing but very old entries in it.
-
RE: Report management returning "###Invalid Login", Apache error log not opening
@Tom-Elliott Feeling like dullest knife in drawer. Update fixed everything just fine.
-
Report management returning "###Invalid Login", Apache error log not opening
Ubuntu 14.0.4, Trunk Version 7981. When I run a report and click on the icon to download, I get “###Invalid Login”. When I go to look at Apache error logs I get “Unable o open log file for reading.” Not sure what credentials are being used for these functions and everything else seems okay so I don’t want to go blindly changing things and break something else. Can someone point me in the right direction?
-
User Cleanup?
I’m not seeing this working. Trunk ver 7981, Ubuntu 14.0.4. I have it globally enabled and enabled it for one host as a test but it’s not showing up in fog.log at all even through three restarts. Is this feature dead? I saw a note in a forum post that it wasn’t going to be around much longer. I think it would be cool to have since I have lots of school machines with MANY student accounts building up, but can’t use Dynamic Local User to deal with them. We used to use Deep Freeze so accounts didn’t last past a restart, but we’re in different territory now.
-
RE: Utilizing Postscripts (Rename, JoinDomain, Drivers, Snapins)
@Lee-Rowlett Success!! Evidently my fog.postdownload and fog.drivers files got corrupted by editing in Notepad. Thank you for sending me a clean version! Working like a champ. Also for purpose of posterity or future users, the name of the folder for each individual hardware type needs to exactly match the spelling and case of the “System Product” field in the “Inventory” for that machine (or type of machine):
-
RE: Utilizing Postscripts (Rename, JoinDomain, Drivers, Snapins)
@Lee-Rowlett Sure, here’s the goods:
Screenshot of folders in /images
-
RE: Utilizing Postscripts (Rename, JoinDomain, Drivers, Snapins)
@Lee-Rowlett Seems like I’m very close. The image task completes and I get the following just before the machine restarts. Unfortunately no drivers are copied so the image fails to bootup since there’s no drivers in it:
/images/postdownloadscripts/fog.postdownload: line 2: syntax error near unexpected token '$' in\r'' 'images/postdownloadscripts/fog.postdownload: line 2: 'case $osid in * Mounting directory ............................Done * Mounting directory ............................Done * Changing hostname .............................Done * Task complete * Updating Database..............................Done * Rebooting system as task is complete Reboot: Restarting system
-
RE: Help! DHCP suddenly gone haywire!
@Junkhacker @Quazz Thank you both ! I did try re-installing FOG on one server and it worked. Then I tried just restarting another server and that worked too. I then restarted ALL the affected servers and they all worked. Don’t know why the problem occurred, never seen that happen in 10 years so I guess I learned something today and I can sleep well tonight
-
Help! DHCP suddenly gone haywire!
Yikes!! All of a sudden this morning I have at least 7 different FOG servers screwing up DHCP booting for machines at their respective locations. All of them are Ubuntu 14.0.4, TRUNK version 7695 or later. ALl have been working fine for months if not years. I have had to shut them down so DHCP will work (eventually). I can’t even troubleshoot them without messing with users. All I got was a glimpse of a boot screen saying chainloading failed and then screen would cycle through boot again and never get to the client’s HD to boot.
The only think I can think of that would cause so many servers to go wrong at the same time is an Ubuntu update, Maybe it was a mistake to configure the server during install to automatically update security patches but now I’m hoping someone has an idea of what I can do to correct this situation quickly??? I’m no Ubuntu expert but I figure this is the best place to go for the time being to see if anyone can assist?
-
RE: Utilizing Postscripts (Rename, JoinDomain, Drivers, Snapins)
@Lee-Rowlett Sorry,trunk version 7709 i believe