I opened this ticket on GitHub as a bug report. Dominik closed it as a technical issue and Marcel, in his infinite tact, thumbs down emoji’d my requests to reopen. I was able to reproduce the issue in a different server with similar setup.
Used Zammad Version
5.4.0-1680261642.c296586b.focal
Environment
- Installation method: [e.g. source, package] Package
- Operating system (if you’re unsure:
cat /etc/os-release
): [e.g. debian 10.4, ubuntu 20.04] Ubuntu 22.04.2 - Database + version: [e.g. postgresql 9.3, mysql 5.7, mariadb 10.3] postgres (PostgreSQL) 14.7 (Ubuntu 14.7-0ubuntu0.22.04.1)
- Elasticsearch version: [e.g. 7.17] 7.17.9
- Browser + version: [e.g. chrome 83, safari 14, firefox 105] not browser specific
Actual behaviour
I disabled notifications were for one of the groups that had been enabled for years. Didn’t notice the lack of notifications for all groups for a period of hours. Reenabled for the group notifications were removed for. Still no notifications in Slack. Updated from 5.3.1-1676465796.746f9768.focal to 5.4.0-1680261642.c296586b.focal hoping that would fix the issue. This version brought along bugs that prevented Microsoft 365 integration from functioning. Reverted back to snap of 5.3.1. Still no notifications. Screenshot of most recent log posted with personal information removed. I’m not sure if Response “” is normal because I never checked the logs when it was functioning properly to have noticed a difference.
Expected behaviour
Slack notifications received.
Steps to reproduce the behaviour
Unselect a group from ‘Only for these groups’ under Slack integration, then lose all slack integration functionality.
I’ve ran through the logs and there’s a myriad of listings for Slack. The error messages are virtually identical to the first block below. The other block at the bottom is what I’m seeing before the error message posts in the log.
E, [2023-03-31T13:20:35.876434 #906-111620] ERROR – : Unable to post webhook: https://hooks.slack.com/services/[REDACTED]: [#<UserAgent::Result:0x000055be6733d198 @success=false, @Body=nil, @DaTa=nil, @code=0, @content_type=nil, @error=“#<Net::ReadTimeout: Net::ReadTimeout>”, @Header=nil>]
I, [2023-03-31T13:41:18.158134 #906-111620] INFO – : 2023-03-31T13:41:18+0000: [Worker(host:helpdesk pid:906)] Job TicketArticleCommunicateEmailJob [REDACTED] from DelayedJob(default) with arguments: [62011] (id=3229311) (queue=default) RUNNING
I, [2023-03-31T13:41:19.329610 #896-28864360] INFO – : Started GET “/api/v1/http_logs/slack_webhook?limit=50&=1680267654594” for 192.168.53.25 at 2023-03-31 13:41:19 +0000
I, [2023-03-31T13:41:19.335589 #896-28864360] INFO – : Processing by HttpLogsController#index as JSON
I, [2023-03-31T13:41:19.335666 #896-28864360] INFO – : Parameters: {“limit”=>“50”, “”=>“1680267654594”, “facility”=>“slack_webhook”}
I, [2023-03-31T13:41:19.375004 #896-28864360] INFO – : Completed 200 OK in 39ms (Views: 27.0ms | ActiveRecord: 1.6ms | Allocations: 22238)
In spite of the ‘ReadTimeout’ I can curl and successfully post immediately after a fail from Zammad shows up in the logs.
On the Slack side, I have moved the integration amongst various channels, regenerated the key, and deleted and rebuilt the integration.
On the Zammad side, I disabled/enabled the integration, rebooted the server, disabled the integration rebooted the server and then re-enabled the integration.