Can't access Espo after upgrade

[lazovic]

Gomez,

Now that the container for the database (espocrm-db) is running, you can at least make a backup and begin the steps that were described in this post: https://forum.espocrm.com/forum/inst...070#post108070

[Gomez]

lazovic

I'm afraid I'm still having problems and I can't backup the db

sudo /var/www/espocrm/command.sh export-sql /home/gomez/
Exporting the database...
mariadb-dump: Got error: 2002: "Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)" when trying to connect
ERROR: Unable to export the database.

It seems that the database container is constantly restartiing

sudo /var/www/espocrm/command.sh status
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b5aba2b5bf97 espocrm/espocrm:fpm "docker-daemon.sh" 21 hours ago Up 25 seconds 9000/tcp espocrm-daemon
2c6122b8fa22 espocrm/espocrm:fpm "docker-websocket.sh" 21 hours ago Up 25 seconds 0.0.0.0:8080->8080/tcp, :::8080->8080/tcp, 9000/tcp espocrm-websocket
b188dcfa8206 espocrm/espocrm:fpm "docker-entrypoint.s…" 21 hours ago Up 25 seconds 9000/tcp espocrm
14008970a370 mariadb:latest "docker-entrypoint.s…" 21 hours ago Restarting (1) 1 second ago

[lazovic]

Gomez,

Please show me the output of the sudo docker logs espocrm-db command in the CLI.

[Gomez]

lazovic

Thanks for coming back to me - it's this repeatedly

2024-07-04 14:54:36+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.4.2+maria~ubu2404 started.
2024-07-04 14:54:37+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup///memory.pressure not writable, functionality unavailable to MariaDB
2024-07-04 14:54:37+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-07-04 14:54:37+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.4.2+maria~ubu2404 started.
2024-07-04 14:54:37+00:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade or creating healthcheck users) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
2024-07-04 14:54:37 0 [Note] Starting MariaDB 11.4.2-MariaDB-ubu2404 source revision 3fca5ed772fb75e3e57c507edef2985f8eba5b12 as process 1
2024-07-04 14:54:37 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-07-04 14:54:37 0 [Note] InnoDB: Number of transaction pools: 1
2024-07-04 14:54:37 0 [Note] InnoDB: Using generic crc32 instructions
2024-07-04 14:54:37 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2024-07-04 14:54:37 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-07-04 14:54:37 0 [Note] InnoDB: Completed initialization of buffer pool
2024-07-04 14:54:37 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2024-07-04 14:54:37 0 [Note] InnoDB: End of log at LSN=10237440424
2024-07-04 14:54:38 0 [Note] InnoDB: Opened 3 undo tablespaces
2024-07-04 14:54:38 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.
2024-07-04 14:54:38 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2024-07-04 14:54:38 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2024-07-04 14:54:38 0 [Note] InnoDB: log sequence number 10237440424; transaction id 26368390
2024-07-04 14:54:38 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2024-07-04 14:54:38 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-07-04 14:54:38 0 [Note] Plugin 'wsrep-provider' is disabled.
2024-07-04 14:54:38 0 [Note] InnoDB: Buffer pool(s) load completed at 240704 14:54:38
2024-07-04 14:54:38 0 [Note] Recovering after a crash using tc.log
2024-07-04 14:54:38 0 [ERROR] Bad magic header in tc log
2024-07-04 14:54:38 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 server with --tc-heuristic-recover={commit|rollback}
2024-07-04 14:54:38 0 [ERROR] Can't init tc log
2024-07-04 14:54:38 0 [ERROR] Aborting

[Gomez]

lazovic

I'm sure you're busy but I was wondering if you had any suggestion of what I could try next?

[lazovic]

Gomez,

Thank you for your waiting.

The main task is to work correctly with the database container.

Try entering this container first with the following command:

sudo docker exec -it espocrm-db bash

If everything is fine, exit the container (just type exit) and use the following command to export the database (instead of the your-password characters, enter the root password for the database):

sudo docker exec -i espocrm-db /usr/bin/mysqldump -uroot -pyour-password espocrm > db.sql​

[Gomez]

lazovic

Thanks for responding, I really appreciate it .

Unfortunately I can't get into the container

gomez@lexx:~$ sudo docker exec -it espocrm-db bash
Error response from daemon: Container 14008970a3706d85bfa9148c683c6c19270f66245a2e60f70f c4a5d65659d193 is restarting, wait until the container is running

[lazovic]

Gomez,

Please try the following steps:

1. Stop all the containers with the following command:
   

   sudo /var/www/espocrm/command.sh stop​

2. Move the tc.log file from the /var/www/espocrm/data/mariadb/data directory to some other directory on the server.
3. Start all the containers with the following command:
   

   sudo /var/www/espocrm/command.sh start

4. Try entering into the database container using the following command:
   

   sudo docker exec -it espocrm-db bash

[Gomez]

lazovic

Allow me to apologise for going AWOL as I got called away on business. I really appreciate all your help so far.

I followed your instructions in the previous post but I wasn't able to execute

sudo /var/www/espocrm/command.sh start

As it kept telling me that a continaer was already in use.

After some searching I figured how to start and individual container and was able to restart espocrm-db and enter it. I had to install mysqldump as that wasn't there.

Now when I run

sudo docker exec -i espocrm-db /usr/bin/mysqldump -uroot -pyour-password espocrm > db.sql​

(Obviously replacing the relevant parameters) I'm getting a db.sql file created but when I open it all it contains is -

OCI runtime exec failed: exec failed: unable to start container process: exec: "/usr/bin/mysqldump": stat /usr/bin/mysqldump: no such file or directory: unknown