checking /var/log/gromox/sa.log
a ton of
[data_source]:
Failed to connect to mysql server, reason: Access denied for user 'grommunio'@'localhost' (using password: NO)
this error occurs also after a fresh installation.
any hints how to fix this
[SOLVED] gromox error in /var/log/gromox/sa.log (any idea howto fix)
noplan
If you find a fix, please post.
After more investigating and experimenting, it appears that mysql_password value in /etc/gromox/adapter.cfg is not being parsed correctly.
(https://docs.grommunio.com/man/adaptor.8gx.html) states:
mysql_password
Default: (unset)
However, when looking at (https://github.com/grommunio/gromox/blob/master/tools/adaptor/main.cpp), the way the config file is parsed states (line 78):
data_source_init(pconfig->get_value("mysql_host"),
strtol(pconfig->get_value("mysql_port"), nullptr, 0),
pconfig->get_value("mysql_username"), pconfig->get_value("mysql_passwd"),
pconfig->get_value("mysql_dbname"));
Thus when reading the config file, the token it is looking for is mysql_passwd and not mysql_password as the documentation states. I'm opening a github issue about this, as once I made the change the errors disappear:
(https://github.com/grommunio/gromox/issues/11)
For the time being, if you edit /etc/gromox/adapter.cfg and change mysql_password to mysql_passwd this should get rid of these errors. Be sure to restart gromox-adapter after making the changes.
I'm new to Grommunio - only just installed it last night, so please excuse me if I am wrong.
Thanks @obsidiangroup , i tried your solution and can confirm that this worked for me. No more errors in the sa.log
Already addressed by gromox-1.2-136-gc7dc2f6b .
Thank you very much for this report and the PR for it - This issue has been shadowed for us, since our testing was shadowed by grommunio-setup which had set the database credentials automatically. In the meanwhile the fix has been upstreamed: https://github.com/grommunio/gromox/commit/c7dc2f6be644e0390757f9a7d8d77c4494de160f
Repository updates are in progress and will surface within 24 hours.
No problem. I was just trying to figure out why the problem was happening and once I ruled out everything else I started looking through the source code. I actually overlooked it a few times because my brain saw 'mysql_passwd' but it just looked right. Then my last glance of the code, it just popped out at me. I've made the same mistake many times. 'passwd' just looks right.
23 days later
noplan changed the title to [solved ]gromox error in /var/log/gromox/sa.log (any idea howto fix) .
solved with correction of config file
and later with update
mwilliams changed the title to [SOLVED] gromox error in /var/log/gromox/sa.log (any idea howto fix) .