Unable to connect to ZM db.SQLSTATE[HY000] [2002] No such file or directory

[zmad34]

I have been using zoneminder for about a week.

My system Ubuntu Server 20.04 LTS

The server was shut down due to an intermediate electrical problem, and when I turned it on again, I was unable to connect the zoneminder.

When I try to go to http: // hostip / zm I get the following error:

Error Code on Web page: Unable to connect to ZM db.SQLSTATE[HY000] [2002] No such file or directory

can you help me ? please..

[iconnor]

check into your mysql state.

systemctl status mysql
systemctl start mysql

if it won't start check error logs in /var/log/mysql/error.log

[zmad34]

I checked. There is such a log.

mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: deactivating (stop-sigterm) (Result: timeout)
Process: 2247 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
Main PID: 2258 (mysqld)
Status: "Server startup in progress"
Tasks: 20 (limit: 38372)
Memory: 323.1M
CGroup: /system.slice/mysql.service
└─2258 /usr/sbin/mysqld

Jun 17 17:37:40 shewarobitnvr systemd[1]: Starting MySQL Community Server...
Jun 17 17:47:40 shewarobitnvr systemd[1]: mysql.service: start operation timed out. Terminating.



LOG:
2020-06-16T21:24:46.720179Z 48541 [Warning] [MY-013360] [Server] Plugin sha256_password reported: ''sha256_password' is deprecated and will b>

[~Rob]

I've had this a few times lately and the cause seems to be disk space.

Can you run

Code: Select all

df -h

?

[Kiwijunglist]

I'm getting this error too, I'm using zoneminder docker - https://github.com/dlandon/zoneminder - which I've just discovered is now depreciated. I think the error relates to mysql server not running correctly.

[bkjaya1952]

I'm getting this error too, I'm using zoneminder docker - https://github.com/dlandon/zoneminder - which I've just discovered is now depreciated. I think the error relates to mysql server not running correctly.

Please try the following

https://hub.docker.com/r/bkjaya1952/zon ... ker-latest

[poohbah]

I'm running ZM in a container on Proxmox, but was having the exact same issue. I couldn't get the DB to work even after a reboot. Disk space was fine too. I ended up going into mysql error logs where I found this

2021-01-11 1:38:05 0 [ERROR] Bad magic header in tc log
2021-01-11 1:38:05 0 [ERROR] Crash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}
2021-01-11 1:38:05 0 [ERROR] Can't init tc log
2021-01-11 1:38:05 0 [ERROR] Aborting

Upon doing some research into the tc log problem, I came upon this discussion:https://dba.stackexchange.com/questions ... nit-tc-log

The gist of it is to delete or mv the tc log. As soon as I did that, ZM came back to life. Now I just need to figure out why the tc log is causing this problem.

Hope this helps someone