I can NOT access the website

Pilar

When trying to access the website
http://IP/fog/management
I get the following message:
Database connection unavailable

Pilar

me falla el servicio MariaDB, como puedo solucionarlo?

Sebastian Roth

@Pilar First check disk space (command df -h) and if that’s fine then start looking at the log files to see what error is causing the DB to start. Usually you find those in /var/log/mysql/...!

Pilar

root@FOG:/var/lib/mysql/fog# systemctl status mariadb.service
● mariadb.service - MariaDB 10.3.31 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2021-12-07 14:45:11 CET; 15min ago
       Docs: man:mysqld(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 11921 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 11922 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 11924 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery>
    Process: 11968 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
   Main PID: 11968 (code=exited, status=1/FAILURE)
     Status: "MariaDB server is down"

dic 07 14:45:05 FOG systemd[1]: Starting MariaDB 10.3.31 database server...
dic 07 14:45:05 FOG mysqld[11968]: 2021-12-07 14:45:05 0 [Note] /usr/sbin/mysqld (mysqld 10.3.31-MariaDB-0ubuntu0.20.04.1) starting >
dic 07 14:45:11 FOG systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
dic 07 14:45:11 FOG systemd[1]: mariadb.service: Failed with result 'exit-code'.
dic 07 14:45:11 FOG systemd[1]: Failed to start MariaDB 10.3.31 database server.

root@FOG:/var/lib/mysql/fog# systemctl start mariadb.service
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
root@FOG:/var/lib/mysql/fog#

Pilar

@pilar
when It failed I had a lack of disk space but now i have a new disk bigger to add.

Sebastian Roth

@Pilar The output from systemctl doesn’t give enough information. Check the log files I suggested.

when It failed I had a lack of disk space but now i have a new disk bigger to add.

Most probably the database is “corrupted”. In most cases this can be recovered easily but we need the information from the logs to be able to help you.

Pilar

@pilar
the c:\fog.log of the host machine was deleted, is it possible that it is also on the server?
Sorry but I don’t see where you have suggested log files, which ones?

Pilar

I may clarify, I had an active task, a capture, and I realized that I had not changed the storage location, where I was there was no space, so I stopped the task and deleted it. I let it finish the activity on the host, it finished giving an error.
I deleted the image or empty container via web, created another image or empty container, indicated another storage path in the node, I left the web page. When I wanted to log in again via web, the password was no longer accepted, I tried several times and nothing and it didn’t even show me the screen to enter the credentials, it only tells me “Database connection unavailable”

Translated with www.DeepL.com/Translator (free version)

Pilar

@sebastian-roth
Here’s what inside /var/log/mysql/error.log
2021-12-07 11:10:29 0 [Note] InnoDB: Removed temporary tablespace data file: “ibtmp1”
2021-12-07 11:10:29 0 [Note] InnoDB: Shutdown completed; log sequence number 1625693; transa ction id 21
2021-12-07 11:10:29 0 [Note] /usr/sbin/mysqld: Shutdown complete

2021-12-07 11:10:52 0 [Note] InnoDB: Using Linux native AIO
2021-12-07 11:10:52 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-12-07 11:10:52 0 [Note] InnoDB: Uses event mutexes
2021-12-07 11:10:52 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-12-07 11:10:52 0 [Note] InnoDB: Number of pools: 1
2021-12-07 11:10:52 0 [Note] InnoDB: Using SSE2 crc32 instructions
2021-12-07 11:10:52 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-12-07 11:10:52 0 [Note] InnoDB: Completed initialization of buffer pool
2021-12-07 11:10:52 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleane r thread priority can be changed. See the man page of setpriority().
2021-12-07 11:10:52 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2021-12-07 11:10:52 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-12-07 11:10:52 0 [Note] InnoDB: Setting file ‘./ibtmp1’ size to 12 MB. Physically writi ng the file full; Please wait …
2021-12-07 11:10:52 0 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibtmp1 failed with error 28
2021-12-07 11:10:52 0 [ERROR] InnoDB: Could not set the file size of ‘./ibtmp1’. Probably ou t of disk space
2021-12-07 11:10:52 0 [ERROR] InnoDB: Unable to create the shared innodb_temporary
2021-12-07 11:10:52 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2021-12-07 11:10:52 0 [Note] InnoDB: FTS optimize thread exiting.
2021-12-07 11:10:57 0 [Note] InnoDB: Starting shutdown…
2021-12-07 11:10:57 0 [Note] InnoDB: Removed temporary tablespace data file: “ibtmp1”
2021-12-07 11:10:57 0 [ERROR] Plugin ‘InnoDB’ init function returned error.
2021-12-07 11:10:57 0 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
2021-12-07 11:10:57 0 [Note] Plugin ‘FEEDBACK’ is disabled.
2021-12-07 11:10:57 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2021-12-07 11:10:57 0 [ERROR] Aborting

2021-12-07 12:01:33 0 [Note] InnoDB: Using Linux native AIO
2021-12-07 12:01:33 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-12-07 12:01:33 0 [Note] InnoDB: Uses event mutexes
2021-12-07 12:01:33 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-12-07 12:01:33 0 [Note] InnoDB: Number of pools: 1
2021-12-07 12:01:33 0 [Note] InnoDB: Using SSE2 crc32 instructions
2021-12-07 12:01:33 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-12-07 12:01:33 0 [Note] InnoDB: Completed initialization of buffer pool
2021-12-07 12:01:33 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleane r thread priority can be changed. See the man page of setpriority().
2021-12-07 12:01:33 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2021-12-07 12:01:33 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-12-07 12:01:33 0 [Note] InnoDB: Setting file ‘./ibtmp1’ size to 12 MB. Physically writi ng the file full; Please wait …
2021-12-07 12:01:33 0 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibtmp1 failed with error 28
2021-12-07 12:01:33 0 [ERROR] InnoDB: Could not set the file size of ‘./ibtmp1’. Probably ou t of disk space
2021-12-07 12:01:33 0 [ERROR] InnoDB: Unable to create the shared innodb_temporary
2021-12-07 12:01:33 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2021-12-07 12:01:33 0 [Note] InnoDB: FTS optimize thread exiting.
2021-12-07 12:01:38 0 [Note] InnoDB: Starting shutdown…
2021-12-07 12:01:38 0 [Note] InnoDB: Removed temporary tablespace data file: “ibtmp1”
2021-12-07 12:01:38 0 [ERROR] Plugin ‘InnoDB’ init function returned error.
2021-12-07 12:01:38 0 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
2021-12-07 12:01:38 0 [Note] Plugin ‘FEEDBACK’ is disabled.

Sebastian Roth

@Pilar As I said before you should fine log files with more details on your FOG server in /var/log/mysql/ directory!

Pilar

I think that when I changed the storage path it did NOT find it and saved the images in the default folder \images. It started to replicate everything to the system disk and there was no space there. I still can’t access via web, is it possible to fix or recover the database?

Pilar

I have registered a lot of hosts (about 60), from several labs, groups, images created, …, if I reinstall the fog server I lose everything or is there any way to keep what has been created?
I can’t get the database server (MariaDB) to start, so I can’t access the web interface of the FOG server (Database connection unavailable).
I think it was due to the lack of space on the system disk because I have activated the image replication without realizing it.
If I reinstall FOG it will respect me or I will be able to recover the database and all the parameters that I had and I will be able to use the images that I already had created.

Sebastian Roth

@george1421 @Pilar I moved your posts about disk space and all that to the other topic: https://forums.fogproject.org/topic/15904/repositorio-de-imágenes-duplicado

Somehow just saw the logs you posted…

2021-12-07 12:01:33 0 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibtmp1 failed with error 28
2021-12-07 12:01:33 0 [ERROR] InnoDB: Could not set the file size of ‘./ibtmp1’. Probably ou t of disk space
2021-12-07 12:01:33 0 [ERROR] InnoDB: Unable to create the shared innodb_temporary
2021-12-07 12:01:33 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
…
2021-12-07 12:01:38 0 [ERROR] Plugin ‘InnoDB’ init function returned error.
2021-12-07 12:01:38 0 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
2021-12-07 12:01:38 0 [Note] Plugin ‘FEEDBACK’ is disabled.

Is this the most recent log entry?

What I found is this: https://stackoverflow.com/questions/59029267/mariadb-error-on-startup-keeps-restarting

While it’s very similar from the log messages it has the error “Unknown/unsupported storage engine: InnoDB” which you don’t have.

Well could still be a disk space issue but from what we have seen in the output of df -h (reference) it doesn’t seem to be the case here.

Sebastian Roth

@Pilar After some more reading I suggest you run the following commands (as root) :

systemctl stop mariadb.service
mv /var/lib/mysql/ib_logfile0 /var/lib/mysql/ib_logfile0_bak
mv /var/lib/mysql/ib_logfile1 /var/lib/mysql/ib_logfile1_bak
systemctl start mariadb.service
# wait for 10 seconds
tail -n 20 /var/log/mysql/error.log
systemctl status mariadb.service

Pilar

@sebastian-roth
SOLVED. Thank you very much. ENDLESS THANKS

Pilar

@pilar
Well, it really solved the problem of being able to access the web page, but I have tried to make a capture and it fails.
I think it always creates the images in the default path \images although in the node the specified path is not that one. Hence all the failures.
Is it possible that the images are saved in a different path than the \images directory?

Sebastian Roth

@Pilar Well the issue this topic is about was solved. May I ask you to open a new topic for this new question. We try to keep things sorted so other people will find information and help more easily.

In that new topic post a picture of the settings you changed to move the image storage location as well as a picture of the error when capturing an image. We’ll tell you what’s missing.

I can NOT access the website

272

11.7k

17.1k

154.7k