Problem with rh-mariadb102-mariadb

linux

#1

Hi,

After i the cells installation i found this problem in mariadb logs :

2018-06-01 12:37:25 140156460406528 [Warning] Aborted connection 8 to db: ‘cells’ user: ‘pydio’ host: ‘localhost’ (Got an error reading communication packets).

During the installation the connection test was correct.

Hints ?

thx


#2

Hi,
this issue seems to be database related,
it could happen because you did multiple installations with the database, it’s one of the many possibilities,
maybe if you clean and restart the database service it could fix that or even restart the server if you’re not using it right now otherwise i found this issue on the internet it might helpful.


#3

hi,
i already tried to change “max_allowed_packet”, but seems it doesn’t works.

./cells install go fine

:heavy_check_mark: Deploying interface assets: 90% done…
2018-06-01T14:15:11.736+0200 INFO Extracted 8015 files for a total size of 95909460
:heavy_check_mark: Deploying interface assets: 100% done…
:heavy_check_mark: Interface assets: Copied 8015 files
Writing file /home/pydio/.config/pydio/cells/static/pydio/data/plugins/boot.conf/bootstrap.json
:heavy_check_mark: Created interface config files

:heavy_check_mark: Installation Finished: please restart with ‘./cells start’ command

but the database is empty

MariaDB [(none)]> use cells;
Database changed
MariaDB [cells]> show tables;
Empty set (0.00 sec)

The installer say

:heavy_check_mark: Database Password (leave empty if not needed): *****
:heavy_check_mark: Successfully connected to the database

instead mariadb

2018-06-01 14:15:11 140456304948992 [Warning] Aborted connection 8 to db: ‘cells’ user: ‘pydio’ host: ‘localhost’ (Got an error reading communication packets)
2018-06-01 14:15:11 140456304641792 [Warning] Aborted connection 9 to db: ‘cells’ user: ‘pydio’ host: ‘localhost’ (Got an error reading communication packets)

any suggestion about it?


#4

Then it means that cells could not create the database and tables therefore it could be a rights issue, actually with mariaDB 10.2 it should work perfectly, you could reinstall mariadb-server and re configure it.