[SOLVED] ERROR after update 22/10/21

noplan · 2021-10-22T13:07:20+00:00

baseline: Die folgenden 6 Pakete werden aktualisiert: grommunio-admin-web gromox gromox-debuginfo gromox-debugsource libexmdbpp0 python3-pyexmdb rpm -q...

WalterH

My system:
find / -type s | grep my /run/mysql/mysql.sock

noplan ignore the log file ?

I would never ignore an error message, always look for the error or at least watch until the solution is found.

noplan

mwilliams

mwilliams 2021-10-22 17:49:29 41 [Warning] Access denied for user 'gromm'@'localhost' (using password: NO)

this was fixed by changing

passwd to password in/etc/gromox/adaptor.cfg

WalterH

This is my adaptor.cfg:
cat /etc/gromox/adaptor.cfg mysql_username = grommunio mysql_password = PWD mysql_dbname = grommunio schema_upgrade = host:localhost

noplan

WalterH

username here waschanged during the setup to gromm
host from localhost or 127.0.0.1 to gromm.domain.com

do u think tahts the issue ?

mysql_username = gromm
mysql_password = Mvj1A
mysql_dbname = grommunio
schema_upgrade = host:gromm.domain.com

mwilliams

WalterH

@noplan was probably using a bit an older version of the appliance. He's right, there was once a typo (bug) in the setup process, which though has been fixed in the meanwhile.

WalterH

The adaptor.cfg from customer system:
cat /etc/gromox/adaptor.cfg mysql_username = grommunio mysql_password = PWD mysql_dbname = grommunio schema_upgrade = host:email.customer.at
I changed host:email.customer.at to host:localhost, but did noch solved this issue.

noplan username here was changed during the setup to gromm
host from localhost or 127.0.0.1 to gromm.domain.com

do u think tahts the issue ?

This question can only be answered by a grommunio engineer.

WalterH

mwilliams was probably using a bit an older version of the appliance. He's right, there was once a typo (bug) in the setup process, which though has been fixed in the meanwhile.

But why I see on an about 2 weeks old system the same error in sa.log as noplan ?
But the system works.

WalterH

I looked at a customer system and I see the same errors in sa.log but the system works as expected. So I will monitor this error.

noplan

just out of the blue maybe of interest

tail -f /var/log/mysql/mysqld.log
021-10-22 20:22:23 0 [Note] InnoDB: Buffer pool(s) load completed at 211022 20:22:23
2021-10-22 20:25:25 3 [Warning] Aborted connection 3 to db: 'grommunio' user: 'gromm' host: 'localhost' (Got an error reading communication packets)
2021-10-22 20:28:27 24 [Warning] Aborted connection 24 to db: 'grommunio' user: 'gromm' host: 'localhost' (Got an error reading communication packets)

changed from gromm.domain.com to localhost /etc/gromox/adaptor.cfg
reboot

2021-10-22 20:30:45 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2021-10-22 20:30:45 0 [Note] Server socket created on IP: '127.0.0.1'.
2021-10-22 20:30:45 0 [Note] InnoDB: Buffer pool(s) load completed at 211022 20:30:45
2021-10-22 20:30:45 0 [Note] Reading of all Master_info entries succeeded
2021-10-22 20:30:45 0 [Note] Added new Master_info '' to hash table
2021-10-22 20:30:45 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.5.8-MariaDB' socket: '/run/mysql/mysql.sock' port: 3306 MariaDB package

maybe not a smart idea to change localhost / in adaptor.cfg
but i cant find if it was changed manually or during the initial setup
too much testing on ths machine and less not documenting ;)

noplan

noplan changed from gromm.domain.com to localhost /etc/gromox/adaptor.cfg
reboot

doesnt change the error

tail -f /var/log/mysql/mysqld.log
2021-10-22 20:33:48 3 [Warning] Aborted connection 3 to db: 'grommunio' user: 'gromm' host: 'localhost' (Got an error reading communication packets)
2021-10-22 20:36:50 24 [Warning] Aborted connection 24 to db: 'grommunio' user: 'gromm' host: 'localhost' (Got an error reading communication packets)

noplan

zypper up ??

gggg

WalterH

noplan changed from gromm.domain.com to localhost /etc/gromox/adaptor.cfg
reboot

faster:
systemctl restart gromox-adaptor.service

WalterH

All updates ere installed.
zypper ref Repository 'SESAM' is up to date. Repository 'base' is up to date. Repository 'debug' is up to date. Repository 'debug-update' is up to date. Repository 'grommunio' is up to date. Repository 'repo-backports-debug-update' is up to date. Repository 'repo-backports-update' is up to date. Repository 'repo-sle-debug-update' is up to date. Repository 'repo-sle-update' is up to date. Repository 'update' is up to date. All repositories have been refreshed. mail:~ # zypper up Loading repository data... Reading installed packages... Nothing to do.

noplan

can u have a look at
tail -f /var/log/mysql/mysqld.log

if the same error occurs plz ?

WalterH

On one system I see one warning in mysqld.log, but is some time ago:
2021-10-22 16:06:12 44 [Warning] Aborted connection 44 to db: 'grommunio' user: 'grommunio' host: 'localhost' (Got an error reading communication packets)

noplan

so next i'm gonna check the permissions of sock(s)

thx for the log so I'am not alone out there

« Previous Page