You are not logged in.
Error:
A link to the SQL server could not be established. Please check your configuration.
Le serveur Mysql est inaccessible. Vérifiez votre configuration.
root@hostname:/home/username# df -h
Filesystem Size Used Avail Use% Mounted on
udev 1.9G 0 1.9G 0% /dev
tmpfs 394M 1.2M 392M 1% /run
/dev/mapper/ubuntu-ubuntu--lv 79G 76G 0 100% /
tmpfs 2.0G 0 2.0G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
/dev/loop1 56M 56M 0 100% /snap/core18/2409
/dev/loop0 62M 62M 0 100% /snap/core20/1518
/dev/loop2 47M 47M 0 100% /snap/snapd/16292
/dev/loop4 62M 62M 0 100% /snap/core20/1587
/dev/loop5 68M 68M 0 100% /snap/lxd/22753
/dev/loop6 72M 72M 0 100% /snap/lxd/16099
/dev/loop3 56M 56M 0 100% /snap/core18/2538
/dev/sda2 2.0G 106M 1.7G 6% /boot
tmpfs 394M 0 394M 0% /run/user/1000
Offline
"Le serveur Mysql est inaccessible. "
If it's not accessibile, check first if u can connect to mysql.
And expand disk..... it's almost full....
Offline
The disk has already been expanded and continues to fill up, unable to connect to the database.
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
"Le serveur Mysql est inaccessible. "
If it's not accessibile, check first if u can connect to mysql.
And expand disk..... it's almost full....
Offline
Post more information, or I have to guess where your sql server is?
Is it runnning?
Where is it?
Same machine?
systemctl status mysql ?
Offline
the database is running but it stops due to lack of space, the database is also on the same server.
● mariadb.service - MariaDB 10.3.34 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-08-10 10:07:56 -03; 1s ago
Post more information, or I have to guess where your sql server is?
Is it runnning?
Where is it?
Same machine?
systemctl status mysql ?
Offline
I can't undestand. You are here to look for help. So please be more verbose.
It's not a hotline where i make question for every steps with an answer.
Explain what u done, the enviroment ecc ecc
For example can u connect with mysql in console?
Is database ok or is corrupted.....
Offline
I'm running a ubuntu 20.04 server, with GLPI 10.0.2 and mysql Ver 15.1 Distrib 10.3.34-MariaDB.
I am not able to access the database through the console and when trying to access the web I have the above messages.
I can't undestand. You are here to look for help. So please be more verbose.
It's not a hotline where i make question for every steps with an answer.
Explain what u done, the enviroment ecc eccFor example can u connect with mysql in console?
Is database ok or is corrupted.....
Offline
I'm running a ubuntu 20.04 server, with GLPI 10.0.2 and mysql Ver 15.1 Distrib 10.3.34-MariaDB.
I am not able to access the database through the console and when trying to access the web I have the above messages.
When trying to start the database that is currently stopped:
● mariadb.service - MariaDB 10.3.34
Active: failed (Result: exit code)
I can't undestand. You are here to look for help. So please be more verbose.
It's not a hotline where i make question for every steps with an answer.
Explain what u done, the enviroment ecc eccFor example can u connect with mysql in console?
Is database ok or is corrupted.....
Offline
journalctl -xe
Aug 11 08:24:49 glpi rsyslogd[829]: Action message 'action-3-builtin:omfile' (module 'builtin:omfile') lost, could not be processed. Check for additional error messages before this one. [v8.2001.0 try
cat /var/log/syslog
Aug 11 06:13:36 glpi multipathd[697]: sda: failed to get sysfs uid: Invalid argument
Aug 11 06:13:36 glpi multipathd[697]: sda: failed to get sgio uid: No such file or directory
I can't undestand. You are here to look for help. So please be more verbose.
It's not a hotline where i make question for every steps with an answer.
Explain what u done, the enviroment ecc eccFor example can u connect with mysql in console?
Is database ok or is corrupted.....
Offline
Ok, so u have a problem with mysql server, not related to GLPI.
I read that whas active and running here..
● mariadb.service - MariaDB 10.3.34 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-08-10 10:07:56 -03; 1s agoSo.. check mysql server log. I suppose database corrupted.
Offline
I found a very large log, created by some SNMP discovery and inventory rules. Deleting this log freed up disk space and I was able to adjust the rules created.
/var/www/html/glpi/files/_log/sql-errors.log
Tks
Ok, so u have a problem with mysql server, not related to GLPI.
I read that whas active and running here..
● mariadb.service - MariaDB 10.3.34 database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2022-08-10 10:07:56 -03; 1s agoSo.. check mysql server log. I suppose database corrupted.
Offline
Good afternoon!
I apologize in advance, I am from Ukraine and there is no one to help me!
When running glpi in a browser, it gives:
A link to the SQL server could not be established. Please check your configuration.
Le serveur Mysql est inaccessible. Vérifiez votre configuration.
glpi-error.log
[Wed Dec 14 11:59:49.931794 2022] [php7:notice] [pid 8352] [client 192.168.1.59:51820] PHP Notice: Undefined index: glpilanguage in /home/glpi/www/inc/html.class.php on line 1212
[Wed Dec 14 11:59:49.931871 2022] [php7:notice] [pid 8352] [client 192.168.1.59:51820] PHP Notice: Undefined index: in /home/glpi/www/inc/html.class.php on line 1212
mysql-error.log
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xe8e68b]
/usr/sbin/mysqld(handle_fatal_signal+0x36f)[0x77524f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7efc626d7390]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7efc61a90438]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7efc61a9203a]
/usr/sbin/mysqld[0x74a77c]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x145)[0x10caa75]
/usr/sbin/mysqld(_Z20buf_page_io_completeP10buf_page_tb+0x3b4)[0x1108e44]
/usr/sbin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0x4e2)[0x113ad02]
/usr/sbin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4a3)[0x1107573]
/usr/sbin/mysqld(_Z19trx_undo_lists_initP10trx_rseg_t+0x3b2)[0x10be3e2]
/usr/sbin/mysqld[0x10a4196]
/usr/sbin/mysqld[0x10a6e2b]
/usr/sbin/mysqld(_Z24trx_sys_init_at_db_startv+0x1734)[0x10adae4]
/usr/sbin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x4dbd)[0x10738bd]
/usr/sbin/mysqld[0xf3169d]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x7c9381]
/usr/sbin/mysqld[0xc65255]
/usr/sbin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x318)[0xc68678]
/usr/sbin/mysqld[0x76d6ef]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0xa3e)[0x76f09e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7efc61a7b840]
/usr/sbin/mysqld(_start+0x29)[0x7651f9]
information that should help you find out what is causing the crash.
2022-12-07T04:24:39.282474Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2022-12-07T04:24:39.282580Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2022-12-07T04:24:39.480320Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2022-12-07T04:24:39.483342Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.33-0ubuntu0.16.04.1) starting as process 20521 ...
2022-12-07T04:24:39.493100Z 0 [Note] InnoDB: PUNCH HOLE support available
2022-12-07T04:24:39.493154Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-12-07T04:24:39.493169Z 0 [Note] InnoDB: Uses event mutexes
2022-12-07T04:24:39.493189Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-12-07T04:24:39.493203Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2022-12-07T04:24:39.493216Z 0 [Note] InnoDB: Using Linux native AIO
2022-12-07T04:24:39.493733Z 0 [Note] InnoDB: Number of pools: 1
2022-12-07T04:24:39.493980Z 0 [Note] InnoDB: Using CPU crc32 instructions
2022-12-07T04:24:39.497177Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2022-12-07T04:24:39.515341Z 0 [Note] InnoDB: Completed initialization of buffer pool
2022-12-07T04:24:39.519655Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2022-12-07T04:24:39.533166Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2022-12-07T04:24:39.535951Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 6136210956
2022-12-07T04:24:39.536010Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 6136210965
2022-12-07T04:24:39.536027Z 0 [Note] InnoDB: Database was not shutdown normally!
2022-12-07T04:24:39.536041Z 0 [Note] InnoDB: Starting crash recovery.
2022-12-07T04:24:39.544088Z 0 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=0, page number=286]. You may have to recover from a backup.
2022-12-07T04:24:39.544129Z 0 [Note] InnoDB: Page dump in ascii and hex (16384 bytes):
InnoDB: End of page dump
2022-12-07T04:24:39.672900Z 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 1170320146, calculated checksums for field1: crc32 1170320146/457218067, innodb 2135368399, none 3735928559, stored checksum in field2 1510559965, calculated checksums for field2: crc32 1170320146/457218067, innodb 3483213286, none 3735928559, page LSN 1 1841231576, low 4 bytes of LSN at page end 1841180988, page number (if stored to page already) 286, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
2022-12-07T04:24:39.672933Z 0 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption.
2022-12-07T04:24:39.672947Z 0 [ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page in the system tablespace. Or, there was a failure in tagging the tablespace as corrupt.
2022-12-07 06:24:39 0x7f3f1f3d8740 InnoDB: Assertion failure in thread 139909083793216 in file ut0ut.cc line 921
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: about forcing recovery.
04:24:39 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Offline
As written:
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Mysql server has some problems, is not glpi related.
Offline
I'm trying to dump the database
MySQL error 2002 (HY000): Unable to connect to local MySQL server via socket '/var/run/mysqld/mysqld.sock' (2)
Offline
As wrote above, it's not GLPI related.
You should ask on some mysql support forum..
Offline