Unable to commit message: disk error (80040116)
Closed this issue · 8 comments
theoneandonly-vector commented
Describe the bug
After a few days I can't receive E-mails anymore.
When I restart the containers it will work again for a few days.
To Reproduce
Steps to reproduce the behavior:
Send an E-Mail -> Kopano-user.
Expected behavior
The E-Mail will be delivered to my inbox.
Log
docker-compose logs -f kopano_dagent:
kopano_dagent_1` | 2020-06-12T01:22:37.729200: [kopano-dagent|T6] [=======] Starting kopano-dagent version 10.0.5 (pid 6 uid 0) (LMTP mode)
kopano_dagent_1 | 2020-06-12T01:22:37.745566: [kopano-dagent|T6] [=======] Starting kopano-dagent version 10.0.5 (pid 6 uid 999) (LMTP mode)
kopano_dagent_1 | 2020-06-12T14:44:24.281500: [kopano-dagent|T9880] [warning] renovate_encoding: unknown charset "3DUTF-8", skipping
kopano_dagent_1 | 2020-06-12T14:44:24.281722: [kopano-dagent|T9880] [error ] HTML part not readable in any charset. Storing as attachment instead.
kopano_dagent_1 | 2020-06-14T11:29:38.616493: [kopano-dagent|T34069] [error ] Unable to login for user "SYSTEM": disk error (80040116)
kopano_dagent_1 | 2020-06-14T11:29:40.406301: [kopano-dagent|T34069] [error ] void* HandlerLMTP(void*): HrGetSession failed: disk error (80040116)
kopano_dagent_1 | 2020-06-14T14:10:24.374606: [kopano-dagent|T34084] [error ] HRESULT ProcessDeliveryToRecipient(pym_plugin_intf*, IMAPISession*, IMsgStore*, bool, LPADRBOOK, IMessage*, bool, const string&, ECRecipient*, DeliveryArgs*, IMessage**, bool*): Unable to determine quota status: disk error (80040116)
kopano_dagent_1 | 2020-06-14T14:14:23.388043: [kopano-dagent|T34084] [error ] Unable to commit message: disk error (80040116)
kopano_dagent_1 | 2020-06-14T14:14:53.770297: [kopano-dagent|T34084] [error ] Unable to deliver message to "test@testserver.tld": disk error (80040116)
kopano_dagent_1 | 2020-06-14T14:15:01.149741: [kopano-dagent|T34084] [error ] Unable to deliver all messages for server "default:"
fbartels commented
"disk error" means that kopano-server could not write the received data to disk/database. You should be looking in its logging for further insights.
theoneandonly-vector commented
I do see a ton of:
[warning] SQL [00001519] info: MySQL server has gone away. Reconnecting
while it's working completely fine.
and I get this:
kopano_server | 2020-06-15T18:35:41.764948: [error ] mysql_real_connect: Unknown MySQL server host 'db' (-3)
kopano_server | 2020-06-15T18:35:42.314752: [warning] Replacing notification request for ID 6050246659330295928
kopano_server | 2020-06-15T18:35:44.762561: [error ] KDatabase::DoSelect(): query failed: "MYSQL not initialized", query: SELECT hierarchy_id FROM stores WHERE stores.user_id=18 LIMIT 1
kopano_server | 2020-06-15T18:35:48.172061: [warning] Replacing notification request for ID 4237756867761773496
kopano_server | 2020-06-15T18:35:49.401172: [error ] SQL [00000000] Failed: Unknown MySQL server host 'db' (-3), Query Size: 63, Query: "SELECT hierarchy_id FROM stores WHERE stores.user_id=31 LIMIT 1"
kopano_server | 2020-06-15T18:35:52.308664: [error ] KDatabase::DoSelect(): query failed: "MYSQL not initialized", query: SELECT hierarchy_id FROM stores WHERE stores.user_id=31 LIMIT 1
kopano_server | 2020-06-15T18:35:54.821510: [warning] Replacing notification request for ID 9638860224364359190
kopano_server | 2020-06-15T18:35:57.407228: [error ] SQL [00000000] Failed: Unknown MySQL server host 'db' (-3), Query Size: 63, Query: "SELECT hierarchy_id FROM stores WHERE stores.user_id=16 LIMIT 1"
kopano_server | 2020-06-15T18:36:00.176355: [error ] KDatabase::DoSelect(): query failed: "MYSQL not initialized", query: SELECT hierarchy_id FROM stores WHERE stores.user_id=16 LIMIT 1
kopano_server | 2020-06-15T18:36:03.952301: [warning] Writeout of logon/off time cache unsuccessful
kopano_server | 2020-06-15T18:36:10.745419: [warning] Replacing notification request for ID 1315267430910946821
kopano_server | 2020-06-15T18:36:15.305998: [error ] SQL [00000000] Failed: Unknown MySQL server host 'db' (-3), Query Size: 63, Query: "SELECT hierarchy_id FROM stores WHERE stores.user_id=17 LIMIT 1"
kopano_server | 2020-06-15T18:36:19.164564: [error ] KDatabase::DoSelect(): query failed: "MYSQL not initialized", query: SELECT hierarchy_id FROM stores WHERE stores.user_id=17 LIMIT 1
kopano_server | 2020-06-15T18:36:18.531382: [warning] Replacing notification request for ID 5853284035397166315
kopano_server | 2020-06-15T18:36:23.573017: [error ] SQL [00000000] Failed: Unknown MySQL server host 'db' (-3), Query Size: 63, Query: "SELECT hierarchy_id FROM stores WHERE stores.user_id=11 LIMIT 1"
kopano_server | 2020-06-15T18:36:26.210103: [error ] KDatabase::DoSelect(): query failed: "MYSQL not initialized", query: SELECT hierarchy_id FROM stores WHERE stores.user_id=11 LIMIT 1
kopano_server | 2020-06-15T18:36:29.154350: [warning] Writeout of logon/off time cache unsuccessful
kopano_server | 2020-06-15T18:36:32.147121: [warning] Replacing notification request for ID 6615280907016544630
fbartels commented
Unknown MySQL server host 'db'
Kind of sounds like a dns issue between kopano-server and the database server.
theoneandonly-vector commented
do you have an idea why this happens after some time?
fbartels commented
No, without direct access or knowledge about the host system I don't have an idea what could cause it.
theoneandonly-vector commented
Do you have some tips for debbuging when it happens next time?
fbartels commented
When it happens:
- check if dns resolution works inside and outside of containers
- check if all containers are running
- check memory and utilisation on the host
github-actions commented
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days