@KnightRaven There are no words to describe how happy I am right now. I finally got it working and I’m in fog again and everything looks okay! Knight I want to thank you so much for your help you had me on the right path all along, however, I did have to do a few extra steps. I’m going to explain so if anyone has this issue later on and they stumble upon this post hopefully it will help them out.

First thing is the reason I could never get mysqld to start is during the installation of mySQL it never created the directory /var/run/mysqld so that’s why it would never start a mysql instance. So using these commands you can accomplish that.

mkdir -p /var/run/mysqld
chown mysql:mysql /var/run/mysqld

Once that was done, make sure all instances of regular mysql is gone. I used killall mysql and then to verify killall -9 mysql Then I ran the following command

mysqld_safe --skip-grant-tables --skip-networking &

Once that is done you’ll need to open a different terminal. And do the following:

mysql -u root

If all is well you should now be in the database once more, here I checked for the user account like you mentioned Knight, but mine seemed to still be in there. So if the user is there use the following commands (this is what I had to do in my case, since my root user still existed)

use mysql;
update user set authentication_string=PASSWORD('<YOURPASSWORDHERE>') where user='root';
flush privileges;
\q

So now your password should be updated, so now to verify kill all of the mysqld instances and start the regular mysql ones. This can be accomplished by the following.

killall mysqld
service mysql start
#now you can check your new password...
mysql -u root -p
#Enter your password and you should be brought to the following prompt...
mysql>

After that I was able to get to the fog homepage and update my schema, and now I’m back in with everything in tact. After this was done I followed Tom’s advice and disabled automatic updates because I’m really tired of Ubuntu breaking everything lol.

I hope this helps any future readers, so you don’t have to go through this madness like I did. Turn off automatic updates as soon as you can, because from my experience it only causes issues, and if you have to update your Ubuntu fog machine prepare for problems.

I also want’s to extend one last thanks to @KnightRaven @Tom-Elliott and @george1421 for their help on this, you guys rock!

Along with everyone else’s references here is the one I used: https://askubuntu.com/questions/489098/unable-to-reset-root-password-of-mysql

@KnightRaven There are no words to describe how happy I am right now. I finally got it working and I’m in fog again and everything looks okay! Knight I want to thank you so much for your help you had me on the right path all along, however, I did have to do a few extra steps. I’m going to explain so if anyone has this issue later on and they stumble upon this post hopefully it will help them out.

First thing is the reason I could never get mysqld to start is during the installation of mySQL it never created the directory /var/run/mysqld so that’s why it would never start a mysql instance. So using these commands you can accomplish that.

mkdir -p /var/run/mysqld
chown mysql:mysql /var/run/mysqld

Once that was done, make sure all instances of regular mysql is gone. I used killall mysql and then to verify killall -9 mysql Then I ran the following command

mysqld_safe --skip-grant-tables --skip-networking &

Once that is done you’ll need to open a different terminal. And do the following:

mysql -u root

If all is well you should now be in the database once more, here I checked for the user account like you mentioned Knight, but mine seemed to still be in there. So if the user is there use the following commands (this is what I had to do in my case, since my root user still existed)

use mysql;
update user set authentication_string=PASSWORD('<YOURPASSWORDHERE>') where user='root';
flush privileges;
\q

So now your password should be updated, so now to verify kill all of the mysqld instances and start the regular mysql ones. This can be accomplished by the following.

killall mysqld
service mysql start
#now you can check your new password...
mysql -u root -p
#Enter your password and you should be brought to the following prompt...
mysql>

After that I was able to get to the fog homepage and update my schema, and now I’m back in with everything in tact. After this was done I followed Tom’s advice and disabled automatic updates because I’m really tired of Ubuntu breaking everything lol.

I hope this helps any future readers, so you don’t have to go through this madness like I did. Turn off automatic updates as soon as you can, because from my experience it only causes issues, and if you have to update your Ubuntu fog machine prepare for problems.

I also want’s to extend one last thanks to @KnightRaven @Tom-Elliott and @george1421 for their help on this, you guys rock!

Along with everyone else’s references here is the one I used: https://askubuntu.com/questions/489098/unable-to-reset-root-password-of-mysql

@KnightRaven This is driving me insane lol, Ubuntu absolutely hates me. I completely removed sql and reinstalled it, and it still denies access to everything. The only other thing I can think of doing is saving my images then installing Ubuntu and fog again.

Any ideas? Or does this seem like the only other option?

@KnightRaven Okay thanks man, I’m about to try those things and see if it works for me. If it doesn’t I may resort to uninstalling mySQL.

Maybe @Tom-Elliott could answer, whether or not, my fog database should stay intact if I uninstall and then re-install mySQL?

Also Knight, what commands did you run to uninstall mySQL and re-install it? The ones I found seem to get rid of anything SQL related.

@KnightRaven Thanks for the help man! I am definitely not in anyway a SQL pro lol, so I tried what you did. I used the command sudo service mysql stop and then ran the first command. When I attempted to run the second command I receive this error: ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2) I then checked the status of the mysql service and it was still stopped. I also attempted the command in the article you provided /etc/init.d/mysql stop mysqld_safe --skip-grant-tables but that was also to no avail. I even attempted to replace “stop” with “start” in that command but that didn’t work either. :L

@Tom-Elliott ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY ''; that one actually executed the first failed, but like I said after this command I still was unable to get to the homepage of fog, and now I can’t seem to login to my sql database.

@Tom-Elliott I did the steps you provided, the second command worked on that post, but now it’s still a blank screen and I can’t get into the mySQL database.

@george1421 Okay thanks for your help man, I really appreciate you looking at this with me!

@george1421 I do see a re-direct occuring no matter what i put in for example: http://<server-ip>/asdfasdf it adds “?node=schema” don’t know if that helps any. As for the error logs see below, I have omitted the server ip intentionally. The error there may be because I was messing around with the settings in that article, so after you told me to check the log out I restarted the apache2 service and tried to pull the page up, but the error never showed up again in the error log.

[Wed May 17 17:19:29.081733 2017] [php7:error] [pid 29225] [client x.x.x.x:37264] PHP Fatal error: Uncaught Error: Call to a member function lastInsertId() on boolean in /var/www/fog/lib/db/pdodb.class.php:443\nStack trace:\n#0 /var/www/fog/lib/fog/fogcontroller.class.php(527): PDODB->insertId()\n#1 /var/www/fog/lib/fog/hookmanager.class.php(176): FOGController->save()\n#2 /var/www/fog/lib/fog/fogpagemanager.class.php(82): HookManager->processEvent(‘SEARCH_PAGES’, Array)\n#3 [internal function]: FOGPageManager->__construct()\n#4 /var/www/fog/lib/fog/fogbase.class.php(457): ReflectionClass->newInstanceArgs(Array)\n#5 /var/www/fog/management/index.php(23): FOGBase::getClass(‘FOGPageManager’)\n#6 {main}\n thrown in /var/www/fog/lib/db/pdodb.class.php on line 443
[Wed May 17 17:35:14.867060 2017] [mpm_prefork:notice] [pid 29220] AH00169: caught SIGTERM, shutting down
[Wed May 17 17:35:14.959750 2017] [mpm_prefork:notice] [pid 29342] AH00163: Apache/2.4.25 (Ubuntu) OpenSSL/1.0.2k configured – resuming normal operations
[Wed May 17 17:35:14.959797 2017] [core:notice] [pid 29342] AH00094: Command line: ‘/usr/sbin/apache2’

Edit: After about 18 mins the above error populated to the apache error log.

I never set up a redirect for fog, I would always key in the whole server address. In the location Tom specified in his first post in the article you shared i don’t have an index.php I do have an index.html. I attempted to do what Wanderson posted but the issue is still occuring. I don’t necessarily believe it’s an issue with the update itself as this was a problem before I upgraded fog.

Hi,

I was experiencing an issue with our fog server not loading the homepage, so I updated to the current stable build. The problem persisted so I went ahead and updated to the most current release. The issue is when I try to go to http://<server-ip>/fog/management I get an error in firefox that it would keep redirecting forever. I know after you update fog, you need to update the schema, and I have experienced database connection issues in the past could this be what the problem is? Fog is running on a 16.04 Ubuntu machine. Any help with this would be greatly appreciated!

Thanks