Solved Error message when attempting to access fog
The last few days, When i attempt to access my fog server via the management console…I receive this message. I’am unsure what to do at this point. Any direction anyone could point me in would be greatly appreciated!
Thanks in Advance!
Is mysql running? You can typically check by running
service mysqld status
If so, can you log into mysql using the credentials in config.class.php?
Grep your credentials with:
grep DATABASE /var/www/html/fog/lib/fog/config.class.php
root@Fed-Fog:~# grep DATABASE /var/www/html/fog/lib/fog/config.class.php define('DATABASE_TYPE', 'mysql'); // mysql or oracle define('DATABASE_HOST', 'localhost'); define('DATABASE_NAME', 'fog'); define('DATABASE_USERNAME', 'fog'); define('DATABASE_PASSWORD', "password");
Test your connection with:
mysql -u fog -p
root@Fed-Fog:~# mysql -u fog -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MySQL connection id is 10385683 Server version: 5.5.50-0+deb8u1 (Debian) Copyright (c) 2000, 2015, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MySQL [(none)]>
I’m betting on a full base partition.
Please post the output of
Please do not skip the command and say you have lots of space; many people have claimed this in the past only to later find out their base partition was full.
/partition is full.
If i had to guess, it’s due to /boot
cd / du -ah /boot
@tom-elliott I ran that command and it populated a ton of stuff…
@kjoslin I just need the last line it should show something like:
@tom-elliott 441M /boot
I’d also recommend following the information here.
Which should help you remove the extra kernels.
With the information you’ve given us however, it appears your total disk space is about 150GB?
Did you have a mount for /images? Your disk space is completely used up currently. This means mysql can’t write the lock files to actually initiate itself, and cannot perform and updates to the database. This is why you’re seeing the message.
I’d also take a look in your /images folder and remove any images you do not need anymore to help you out a little bit.
@tom-elliott 150GB is correct.
I do have images that I can remove. Do you have a how-to for this as well?
@kjoslin This happened because your images are being stored on the base partition, rather than their own partition - and you filled up the server with probably an image capture. While we can help you get this going - without taking preventative measures, this problem will simply happen again.
We have some tutorials showing ‘generic’ good practices for setting up FOG and how to do partitioning. Both of these tutorials have videos showing the partitioning:
Here also is a tutorial detailing how to migrate from an old server to a new one:
Of course, helping you build a new server and migrate is off topic in this thread, so if you wanted help with that please create a new thread with an appropriate title.