No updates of the system have been performed, and FOG is the only software in use on this system. I’ve had zero issues upgrading all along from 1.3 through various RC releases as they come out and onward to this final 1.4.0 release. This is the first time I’ve seen a failed message during an upgrade.

Specifically the error log shows:
“update-rc.d: error: cannot find a LSB script for FOGMulticastManager”

I was able to bypass the issue by grabbing the init.d scripts out of the packages folder, and manually placing them into /etc/init.d following with a chmod +x. Once those scripts were copied into init.d the foginstaller script moved along nicely.

You’ll also want to update if that 7050 was purchased with an NVMe drive. FOG 1.2.0 doesn’t support NVMe drives or Win10 very well.

@Joe-Gill look in the .fogsettings file and see if there is a password set for the mysql one.

ISSUE RESOLVED By following this

TLDR; Rerun the fog installer if you have lost “Database Connectivity” to your fog server, or run the ALTER USER syntax shown below.

So Ubuntu 16, among others I suppose, enable a “security updates” to be applied automatically as a “default” to things. Why, well it makes it simpler to ensure your Ubuntu systems are in compliance and patched for any potential exploits. This causes unknown and unexpected issues.

I figured it’d be a safe thing to express that there could be problems (as many of you have already experienced) that when these updates go up (with or without your knowledge) it can break functionality in unexpected and inopportune ways.

The quickest fix is to simply rerun the fog installer which should correct the problem.

As a note, it seems this problem is specific only when the mysql account is the ‘root’ user AND the password is blank.

The “fix” if you must do it manually is to open a terminal and obtain root:
Super (Windows Key) + T then sudo -i (in most cases).

From there, open mysql with mysql -u root

NOTE: MySQL MUST be run with ROOT.

Run:

ALTER USER ‘root’@‘127.0.0.1’ IDENTIFIED WITH mysql_native_password BY ‘’; AND
ALTER USER ‘root’@‘localhost’ IDENTIFIED WITH mysql_native_password BY ‘’;

It’s okay if one of them fails. This is going to fix Most people’s issues.

I would highly recommend removing the unattended-upgrades as many of these “sudden” issues came as a security patch ubuntu pushed out. By default Ubuntu typically set’s this for you as enabled and it can cause havoc on you as you (the admin) may not have “done” anything.

To prevent this problem from happening in the future you could run:

apt-get -y remove unattended-upgrades (AS Root again).

@noelpd Thanks!!!

@george1421 I didn’t know this was a multi-master setup, if that’s what you meant. I was referring to a video on just configuring a second node into an existing fog setup. With the new access control plugin and site plugin, multi-master setups are just that less a good idea.

As it stands now with the access control plugin, location plugin, and site plugin - the only benifit one stands to gain in a multi-master setup is some level of fault tolerance against the upstream box failing - and fault tolerance against the link failing - and for those two things you loose a comprehensive database/control center in a central location - a major drawback.

@george1421

Hey george1421 some update: 🙂
all PC getting IP and seeing the Fog menu for deployment and registration much appreciated again, for direction.

might be its for new post but wondering I notice one thing that after Deploy image when PC rebooting he is looking for pxe instead load OS, so I need change the BIOS manually to UEFI enabled.
before the change it was done automatically enable/disable UEFI on BIOS

thanks ,
Kpax

@Tom-Elliott said in Database Schema error after installation:

I’m lost. What question are you asking?

When I responded to it the message was asking for the login information.

As for phpmyadmin, I don’t know what is or isn’t on your system. You shouldn’t have to do anything special to work with phpmyadmin though. How did you install phpmyadmin? YOu might look into using the “source” information rather than the package as Ubuntu has a nasty habit of telling packages exactly what packages MUST be used for things. While this is normal and fine for most things, when it comes to phpMyAdmin, they have decided it MUST contain PHP version 5, but FOG installs PHP version 7.

Well… let’s say that in the first “blank” installation I’ve installed ubuntu server than using apt-get command I’ve installed, in order, apache2, mysql and php7.
Then I’ve installed phpmyadmin with the command sudo apt-get install phpmyadmin apache2-utils.
After that everything was working fine.

Then I’ve installed Fog 1.3.5.
The setup seemed to be ok but I’ve received an error when udpating the database.
This is the output:

Configuring services Setting up fog user…OK Setting up fog password…OK Stopping FOGMulticastManager.service Service…OK Stopping FOGImageReplicator.service Service…OK Stopping FOGSnapinReplicator.service Service…OK Stopping FOGScheduler.service Service…OK Stopping FOGPingHosts.service Service…OK Stopping FOGSnapinHash.service Service…OK Stopping FOGImageSize.service Service…OK Setting up and starting MySQL…OK Backing up user reports…Done Stopping web service…OK Setting up Apache and PHP files…OK Testing and removing symbolic links if found…OK Backing up old data…OK Copying new files to web folder…OK
find: /home//fog_web_1.3.5.BACKUP/management/other/: No such file or directory Creating config file…OK Downloading binaries needed…OK Unzipping the binaries…Done Copying binaries where needed…Done Enabling apache and fpm services on boot…OK Creating SSL CA…OK Creating SSL Private Key…OK Creating SSL Certificate…OK Creating auth pub key and cert…OK Resetting SSL Permissions…OK Setting up SSL FOG Server…OK Restarting Apache2 for fog vhost…OK Changing permissions on apache log files…OK Backing up database…OK Updating Database…Failed!

Then phpmyadmin was still working BUT pointing to http://ipaddress/fog I received the error i told you before: Database Schema Installer / Updater etc…

Using the command mysql -D fog I received a message about the database non existing.

I’ve solved the FOG problem with the mysql command ALTER USER ‘root’@‘localhost’ IDENTIFIED WITH mysql_native_password BY ‘’;
So I’ve installed the database and FOG was up and running but phpmyadmin stopped working (???).

Then I’ve “resetted” the phpmyadmin installation with the command sudo dpkg-reconfigure phpmyadmin setting user:root password: password

After that phpmyadmin was ok BUT fog presented the warning messagge “Database Schema Installer/ Updater bla bla bla…”

Finally in the /var/www/html/fog/lib/fog/config.class.php I’ve set the parameter define(‘DATABASE_PASSWORD’, “password”);

Now FOG and phpmyadmin are working.

@captatim Would you mind telling us what the problem was and how you were able to fix it? Other users might find this information very helpful too. Thanks in advance!

Thanks for the quick response! The reply with the proper field data helped tremendously, at least after I updated to 1.3.5.

I had a few issues, particularly with the Group Search DN and the Search Scope option, but I got it to work by using my Base DN (dc=company,dc=local) and the Subtree and Below option. Not sure why it wouldn’t work when I narrowed the scope and chose Base and Subtree, but long story short it’s working now after upgrading to 1.3.5.

I also had a few binding issues but found that instead of using the full DN for the bind user I just used the username and it worked fine.

@K.Hays When booting into FOS this way we only need to ensure that the FOS kernel is updated to support new hardware.

So as the developers release new version of the FOS engine all you need to do is download these files and move them to the previously created usb flash drive into the boot folder replacing the existing files.

https://fogproject.org/inits/init.xz https://fogproject.org/inits/init_32.xz https://fogproject.org/kernels/bzImage https://fogproject.org/kernels/bzImage32

In regards to the usb network adapters. When you pxe boot uefi devices you MUST use network adapters recommended by the manufacturer to support pxe booting. When you usb boot into FOS you will have better luck with older USB 2.0 network adapters since those are most likely supported by the linux developers.

Alright, well I already addressed the “file not found” type problem in the RC’s thanks to this. So at least there’s that.

Moved into FOG Problems for now.

Moved as this should be much more prevalent than being reported currently. As stated, I’m not saying this isn’t a problem. Just saying it’s one that I cannot seem to replicate and it isn’t breaking any normal functionality.

@Junkhacker, it worked! Thanks!

Problem solved.It was an old image…

Could this be an IO error beyond 2 GB ?
That used to happen on older 32-bits systems, and is still something to care about with minGW.
I would not expect that from Ubuntu x64, but that conclusion may depend on the compiler used.

Did you check the rcs? I’m pretty sure this was addressed already.

Please install the latest rcs of which you’ll find this issue is already fixed.

@jpaul said in network printers not coming in when imaging with fog 1.2.0:

ill not populate even after all the forced group policy updates per machine . Has anyone found the the problem might be with fog imagining or is it just something wrong with our group policies,

@jpaul it sounds like an issue with your GPO. Is there also a reason why you just started using 1.2.0? It’s fairly outdated and doesn’t support newer operating systems (like Windows 10) very well.

@Tom-Elliott Its works! I’m with RC12 version with dev-branch. Thank you very much for your help.

Running Version 1.4.0-RC-12 SVN Revision: 6069