SamuelNitsche
commented
4 years ago Please take a look at the issue template and provide more information.
Closed onefckcps closed 4 years ago
SamuelNitsche
commented
4 years ago Please take a look at the issue template and provide more information.
andryyy
commented
4 years ago Yes, if you want people to help you, provide logs and don't delete the template. :/
This is not the correct place for support anyway.
onefckcps
commented
4 years ago rspamd-mailcow_1 | 2019-10-28 16:01:37 #1(main) lua; lua_cfg_transform.lua:170: overriding actions from the legacy metric settings
rspamd-mailcow_1 | 2019-10-28 16:01:37 #1(main) lua; lua_cfg_transform.lua:123: overriding group MX from the legacy metric settingsrspamd-mailcow_1 | 2019-10-28 16:01:37 #1(main) lua; lua_cfg_transform.lua:161: group excessqp has no symbols
rspamd-mailcow_1 | 2019-10-28 16:01:37 #1(main) lua; lua_cfg_transform.lua:161: group excessb64 has no symbols
rspamd-mailcow_1 | 2019-10-28 16:01:37 #1(main) <>; lua; lua_cfg_transform.lua:467: enable options.check_all_filters for neural network
rspamd-mailcow_1 | 2019-10-28 16:01:37 #1(main) <>; lua; lua_cfg_transform.lua:525: converted surbl rules to rbl rules
rspamd-mailcow_1 | 2019-10-28 16:01:37 #1(main) <>; lua; lua_cfg_transform.lua:539: converted emails rules to rbl rules
rspamd-mailcow_1 | 2019-10-28 16:01:37 #1(main) cfg; rspamd_rcl_maybe_apply_lua_transform: configuration has been transformed in Lua
rspamd-mailcow_1 | 2019-10-28 16:01:37 #1(main) <6dsnjn>; cfg; rspamd_config_set_action_score: action greylist has been already registered with priority 0, override it with new priority: 0, old score: nan
rspamd-mailcow_1 | 2019-10-28 16:01:37 #1(main) <6dsnjn>; cfg; rspamd_config_set_action_score: action add header has been already registered with priority 0, override it with new priority: 0, old score: nan
rspamd-mailcow_1 | 2019-10-28 16:01:37 #1(main) <6dsnjn>; cfg; rspamd_config_set_action_score: action reject has been already registered with priority 0, override it with new priority: 0, old score: nan
rspamd-mailcow_1 | 2019-10-28 16:01:37 #1(main) rspamd_regexp_library_init: pcre is compiled with JIT for x86 64bit (little endian + unaligned)
rspamd-mailcow_1 | 2019-10-28 16:01:38 #1(main) <6dsnjn>; cfg; rspamd_language_detector_init: loaded 46 languages, 33122 trigramms
rspamd-mailcow_1 | 2019-10-28 16:01:38 #1(main) <6dsnjn>; cfg; chartable_module_config: init internal chartable module
rspamd-mailcow_1 | 2019-10-28 16:01:38 #1(main) <6dsnjn>; cfg; dkim_module_config: init internal dkim module
rspamd-mailcow_1 | 2019-10-28 16:01:38 #1(main) <6dsnjn>; cfg; spf_module_config: init internal spf module
rspamd-mailcow_1 | 2019-10-28 16:01:38 #1(main) <6dsnjn>; cfg; regexp_module_config: init internal regexp module, 127 regexp rules and 0 lua rules are loaded
rspamd-mailcow_1 | 2019-10-28 16:01:38 #1(main) <6dsnjn>; cfg; fuzzy_parse_rule: added fuzzy rule LOCAL_FUZZY_UNKNOWN, key: ef43ae80cc8d, shingles_key: ef43ae80cc8d, algorithm: mum
rspamd-mailcow_1 | 2019-10-28 16:01:46 #1(main) <6dsnjn>; cfg; fuzzy_parse_rule: added fuzzy rule FUZZY_UNKNOWN, key: ef43ae80cc8d, shingles_key: ef43ae80cc8d, algorithm: mum
rspamd-mailcow_1 | 2019-10-28 16:01:46 #1(main) <6dsnjn>; cfg; fuzzy_check_module_config: init internal fuzzy_check module, 2 rules loaded
rspamd-mailcow_1 | 2019-10-28 16:01:46 #1(main) <6dsnjn>; lua; lua_redis.lua:540: use default Redis settings for antivirus
rspamd-mailcow_1 | 2019-10-28 16:01:46 #1(main) <6dsnjn>; cfg; rspamd_map_parse_backend: map '/etc/rspamd/antivirus.wl' is not found, but it can be loaded automatically later
rspamd-mailcow_1 | 2019-10-28 16:01:46 #1(main)
simeun
commented
4 years ago I have the same problem. It looks like mysql-mailcow container does not work correctly on fresh install. I've got php-fpm logs look like this:
root@mailgw /opt/mailcow-dockerized # docker-compose logs --tail=20 -f php-fpm-mailcow
Attaching to mailcowdockerized_php-fpm-mailcow_1
php-fpm-mailcow_1 | Waiting for SQL...
php-fpm-mailcow_1 | Waiting for SQL...
php-fpm-mailcow_1 | Waiting for SQL...
php-fpm-mailcow_1 | Waiting for SQL...
php-fpm-mailcow_1 | Waiting for SQL...
php-fpm-mailcow_1 | Waiting for SQL...
php-fpm-mailcow_1 | Waiting for SQL...
php-fpm-mailcow_1 | Waiting for SQL...
php-fpm-mailcow_1 | Waiting for SQL...
php-fpm-mailcow_1 | Waiting for SQL...
php-fpm-mailcow_1 | Waiting for SQL...
When I tried to connect to the mysql database using credentials from mailcow.conf and failed. I tried few more times with various credential combinations and determined that I can log into mysql console using mailcow and root users but only without passwords. Passwords that were set in mailcow.conf were not correct.
This example shows how I was not able to log into mysql db:
root@mailgw /opt/mailcow-dockerized # source mailcow.conf
root@mailgw /opt/mailcow-dockerized # docker-compose exec mysql-mailcow mysql -u${DBUSER} -p${DBPASS} ${DBNAME}
ERROR 1045 (28000): Access denied for user 'mailcow'@'localhost' (using password: YES)And here is how I was able to log in:
➜ mailcow-dockerized git:(master) docker-compose exec mysql-mailcow mysql -
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 293
Server version: 10.3.18-MariaDB-1:10.3.18+maria~bionic mariadb.org binary distribution
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| mysql |
| performance_schema |
| test |
+--------------------+
4 rows in set (0.001 sec)
MariaDB [(none)]> ByeI decided to try again with fresh mailcow install and it happened again - after docker-compose pull and docker-compose up -d, all containers started, but mysql-mailcow container did not had passwords configured for its users (hence php-fpm-mailcow was unable to connect to database), and the database itself was not created.
@SamuelNitsche, @andryyy Any suggestions for other logs that could be of use?
simeun
commented
4 years ago I found a solution. Comment out skip-name-resolve in /opt/mailcow-dockerized/data/conf/mysql/my.cnf. When this option is on, MySQL/MariaDB will check for user access rights only in rows having host in form of IP address. When running in docker, host will be container id (alphanumeric) so the db will not use this user for checking access rights thus preventing any access to the db (php-fpm).
@Clasoheld does this help?
Houtek
commented
4 years ago I found a solution. Comment out skip-name-resolve in
/opt/mailcow-dockerized/data/conf/mysql/my.cnf. When this option is on, MySQL/MariaDB will check for user access rights only in rows having host in form of IP address. When running in docker, host will be container id (alphanumeric) so the db will not use this user for checking access rights thus preventing any access to the db (php-fpm).@Clasoheld does this help?
I have the same problem and tried your solution. This did not work for me.
I still have
php-fpm-mailcow_1 | Waiting for SQL...
in my logs.
andryyy
commented
4 years ago We moved the tz import to php-fpm-mailcow. On "slow" disks it failed previously. Known bug in the MariaDB image.
stale[bot]
commented
4 years ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Of course I answer all your questions