import or migrate images and host to a new serveur

[Sebastian Roth]

@patrice Yes, check disk space first. Then take a look at log files in /var/log/mysql or /var/log/mariadb…

[patrice]

@george1421 @Sebastian-Roth
apologies, as I’m not the one using fog I didn’t think about looking at the disk space.
I was able to arrive on the graphical interface, but on firefox I cannot connect: Database connection unavailable
I think the database did not like :
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: The InnoDB memory heap is disabled
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Using Linux native AIO
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Using SSE crc32 instructions
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Completed initialization of buffer pool
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Highest supported file format is Barracuda.
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: 128 rollback segment(s) are active.
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Waiting for purge to start
2021-03-01 19:01:48 140500859161728 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.46-86.2 started; log sequence number 1618255
2021-03-01 19:01:48 140500187215616 [Note] InnoDB: Dumping buffer pool(s) not yet started
2021-03-01 19:01:48 140500859161728 [Note] Plugin ‘FEEDBACK’ is disabled.
2021-03-01 19:01:48 140500859161728 [Note] Recovering after a crash using tc.log
2021-03-01 19:01:48 140500859161728 [ERROR] Can’t init tc log
2021-03-01 19:01:48 140500859161728 [ERROR] Aborting

[george1421]

@patrice connect to the fog server linux console and run the command sudo df -h and post the results here.

[patrice]

@george1421

Voici le résulltat:

Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
udev               7,8G       0  7,8G   0% /dev
tmpfs              1,6G    1,9M  1,6G   1% /run
/dev/sda2          1,9T    1,7T   53G  98% /
tmpfs              7,8G     57M  7,8G   1% /dev/shm
tmpfs              5,0M    4,0K  5,0M   1% /run/lock
tmpfs              7,8G       0  7,8G   0% /sys/fs/cgroup
/dev/loop0         2,5M    2,5M     0 100% /snap/gnome-calculator/826
/dev/loop1         1,0M    1,0M     0 100% /snap/gnome-logs/100
/dev/loop2          98M     98M     0 100% /snap/core/10185
/dev/loop3         146M    146M     0 100% /snap/opera/99
/dev/loop4         163M    163M     0 100% /snap/gnome-3-28-1804/145
/dev/loop6          15M     15M     0 100% /snap/gnome-characters/399
/dev/loop5         3,8M    3,8M     0 100% /snap/gnome-system-monitor/127
/dev/loop8         4,3M    4,3M     0 100% /snap/gnome-calculator/544
/dev/loop7         146M    146M     0 100% /snap/opera/97
/dev/loop10         45M     45M     0 100% /snap/gtk-common-themes/1440
/dev/loop9          55M     55M     0 100% /snap/core18/1668
/dev/loop11        161M    161M     0 100% /snap/gnome-3-28-1804/116
/dev/loop12        1,0M    1,0M     0 100% /snap/gnome-logs/81
/dev/loop14         56M     56M     0 100% /snap/core18/1932
/dev/loop13        218M    218M     0 100% /snap/gnome-3-34-1804/60
/dev/loop15        2,3M    2,3M     0 100% /snap/gnome-system-monitor/148
/dev/loop16         33M     33M     0 100% /snap/chromium-ffmpeg/17
/dev/loop18         63M     63M     0 100% /snap/gtk-common-themes/1506
/dev/loop17         90M     90M     0 100% /snap/core/8268
/dev/loop19        384K    384K     0 100% /snap/gnome-characters/570
/dev/sda1          511M    6,1M  505M   2% /boot/efi
tmpfs              1,6G     40K  1,6G   1% /run/user/1000

[george1421]

@patrice said in import or migrate images and host to a new serveur:

 /dev/sda2          1,9T    1,7T   53G  98% /

This will be a problem soon. You only have 53GB free. Look in /images/dev directory on the fog server linux console, for any directory names that look like mac addresses. If you are not currently uploading an image those directories should not exist. You can safely delete those bad upload directories to free some disk space.

But I have to say that 53GB is enough free space to allow mariadb to startup.

[patrice]

@george1421
Here is the result
I removed 3 disk images to restart the PC

[george1421]

@patrice Now rereading the thread I see your old server crashed and this is the server where you are trying to get the mariadb running again. If you can’t get the old database server started you might have to rebuild the metadata by hand.

article on fixing corrupt innodb databases: https://chepri.com/mysql-innodb-corruption-and-recovery/

[patrice]

@george1421
I plugged the disk into usb and I had 0 bytes left. I then deleted 3 disk images and then I plugged the disk back into the computer, it started (no more problem with maria DB).
I then have in firefox: Database connection unavailable

[patrice]

@george1421
thank you for your answer george, I go through google translate that’s why I take time to answer
I will try to rebuild the database as you told me, tomorrow because suir I have to go to bed, I will work early tomorrow
I’ll keep you informed tomorrow
thank you

[patrice]

@george1421
Hello george,
I did not succeed in restoring the database, I do a complete reinstallation of the server.
Thank you for everything