I’m fairly certain it’s a php issue, there was an update for php on ubuntu earlier today, so I’m fairly certain it has to do with that.
Posts
-
RE: Boot.php invalid loginposted in FOG Problems
-
RE: Boot.php invalid loginposted in FOG Problems
After some more testing, none of the default FOG menu items, except memtest work. (not even debug)
edit: This bug is not present on my backup FOG Server, which is running version 6186
-
RE: Boot.php invalid loginposted in FOG Problems
@Tom-Elliott I’m sure they’re not, it was the first thing I checked, would be odd anyway, it had been working fine for weeks
Here’s a screenshot for quick image for example.

-
Boot.php invalid loginposted in FOG Problems
Hi, after updating to trunk any menu that has login protection by default gives Invalid login! now. I removed the parameters/lines that require you to login from the WebGUI some time ago so we can use the functionalities without needing to login.
To clarify, the option to login does not appear (as that was removed by me), but it will block me from continuing. (guessing it’s enforced that you need to login elsewhere?)
Any help would be appreciated.
-
RE: Manually import image files on newly installed Fog serverposted in FOG Problems
Are you sure you chose the correct image type when adding the images to the database?
I believe “size on client” is something generated when capturing the image, by the way.
-
RE: Windows 10 Audit mode - no start menu or searchposted in Windows Problems
@Rusty Not sure how much work you already put into it, but it’s probably safer to just start over.
Also, you can only update Windows 10 to a certain point, you can’t do “upgrades” unless you exit audit mode (you can later go back into audit mode if you remove two registry files)
-
RE: FOG Compatibility Test Failedposted in Hardware Compatibility
With option subnetmask included, could you run
dhcpd -t -cf /path/to/dhcpd.confAnd post the output here? (or on pastebin if it’s a lot)
-
RE: FOG Compatibility Test Failedposted in Hardware Compatibility
@techlover28 That should not cause an issue, but I do note that in my dhcp configs there’s a space between netmask 255.255.255.0 and {
Might be irrelevant, but I’ve yet to see a valid config without that space.
-
RE: Fog upload in /images/dev (default node) instead of /home/backup/dev (other node)posted in FOG Problems
Is there a reason why they have to be in seperate storage nodes? Or why the smaller one is the default one?
-
RE: Can't login using putty after upgrading to 6110posted in FOG Problems
My understanding is that you use “fog” as your login account for ssh and what not. (I generally recommend having a user that is not fog to manage the system precisely in case something goes wrong)
The Webgui login is entirely unrelated to the login you use for ssh and what not.
So, the only thing left to do if that’s your only account is to boot into recovery mode and change the password or add a new account and login using that info.
If you still can’t SSH after that then your SSH is misconfigured or broken.
-
RE: Boot PXE - UEFIposted in FOG Problems
In my experience, under efi initializing devices takes quite a bit longer, sometimes several minutes. That’s assuming it actually works of course.
-
RE: Windows 10 - Image upload - sectorsize errorposted in FOG Problems
@Tom-Elliott Then I’m not sure what happened. How come the first time it stops the process entirely when it fails to resize the fat32 partition (claiming the mbr partition is too large and needs to be resized), but then when I reboot and try again it works fine?
It’s no big deal since it works the second time around, just want to know what’s going on.

-
RE: Windows 10 - Image upload - sectorsize errorposted in FOG Problems
I had this same issue and after updating it seems to work for me. I was busy switching all my images to single disk resizable, so this is great timing for me

Although I do have to try it twice, it fails on resizing the first partition (fat32 UEFI partition), but then on second try it always works. I’m guessing it DOES succeed on resizing the partition, but doesn’t realize it for some reason!
-
RE: Manually typing TFTP address after bootingposted in FOG Problems
@Tom-Elliott Alright, good to hear, I’ll update to the newest revision in a bit after I’ve captured these images.
I believe everything is thus resolved on my end, thanks

-
RE: Manually typing TFTP address after bootingposted in FOG Problems
Dropped my database, purged mysql and apache and reran an older revision to fix the previously mentioned glitches. I know it’s extreme, but my database had quite a few issues and this will be cleaner and faster for me.
-
RE: Manually typing TFTP address after bootingposted in FOG Problems
@Sebastian-Roth I’ll switch back to ISC-DHCP-SERVER in a bit to check for real, but currently on proxydhcp it seems to no longer complain about getting information from both the DHCP and ProxyDHCP server, so that seems to have improved things greatly.
EDIT: ISC-DHCP-SERVER no longer asks for tftp address on my end, as far as I’ve tested, so far so good!
EDIT2: Encountered the TFTP prompt again, think I’ll stick to proxydhcp for now.
EDIT3: I noticed sloppy name lookup was off, but I am unable to enable it (the checkbox clears itself when you try to save the information. In fact, I can’t change any settings it seems, and there’s some other glitches, I’ll post a picture.
WebGUI is now also unresponsive after restarting the server.

The unrespoviness seems to be related to the following apache error as far as I can tell
[Fri Jan 22 11:27:43.497568 2016] [:error] [pid 1367] [client 192.168.1.29:53467] PHP Warning: Division by zero in /var/www/html/fog/lib/pages/dashboardpage.class.php on line 79
Manually navigating to other pages of the webgui (avoiding the dashboard) works
-
RE: FOG WebGUI logviewer server error 500posted in FOG Problems
@Tom-Elliott I copied the info as is. That’s webgui login information, I haven’t altered anything to do with FTP passwords, they’re all stil set to what they were weeks ago in .fogsettings as well, so I’m not even sure how that would have happened.
At any rate, I’ll recheck all the ftp passwords and report back below.
I reentered the password for the fog storage node and now the error log viewer is back, good call Tom!
I’m guessing this is also why the clients were unable to update the database.
That just leaves the minor errors about mysql outlined in the original post.
Thank you already for you help

-
RE: FOG WebGUI logviewer server error 500posted in FOG Problems
@Wayne-Workman Yes, the WebGUI works fine for the most part, only discovered this with the log viewer specifically.
-
RE: FOG WebGUI logviewer server error 500posted in FOG Problems
@Wayne-Workman There were no errors in the installer, but I see there’s a new version so I’ll try updating, fingers crossed.
-
RE: FOG WebGUI logviewer server error 500posted in FOG Problems
@Wayne-Workman There seems to be a new apache error:
[Wed Jan 20 14:41:04.711486 2016] [:error] [pid 2227] [client 192.168.1.29:52272] PHP Fatal error: Uncaught exception 'Exception' with message 'FOGFTP: Login failed. Host: 192.168.1.156, Username: fog, Password: password, Error: ftp_login(): Login incorrect.' in /var/www/html/fog/lib/fog/fogftp.class.php:29\nStack trace:\n#0 /var/www/html/fog/lib/pages/fogconfigurationpage.class.php(637): FOGFTP->connect()\n#1 [internal function]: FOGConfigurationPage->log()\n#2 /var/www/html/fog/lib/fog/fogpagemanager.class.php(67): call_user_func(Array)\n#3 /var/www/html/fog/management/index.php(24): FOGPageManager->render()\n#4 {main}\n thrown in /var/www/html/fog/lib/fog/fogftp.class.php on line 29, referer: http://192.168.1.156/fog/management/?node=aboutRestarting the services doesn’t help.
I have been adding a few new hosts and capturing a few images, it was working fine yesterday.
Mysql service status complains about error logs after starting:
Jan 20 16:28:56 fogserver mysqld_safe[10167]: 160120 16:28:56 mysqld_safe Can't log to error log and syslog at the same time. Remove all --log-error...e effect.```