Zammad: Slack integration - Unable to post webhook (Net::OpenTimeout: execution expired)

Created on 9 Oct 2017 · 3Comments · Source: zammad/zammad

Infos:

Used Zammad version: 2.0.0
Used Zammad installation source: source
Operating system: Server - Debian 9 (x86); Client - Windows 10 (x64)
Browser + version: Firefox 56 (x64)

Expected behavior:

Webhook is sent and the ticket notification appears in the dedicated Slack channel

Actual behavior:

Webhook doesn't get sent with the following error in production.log:

E, [2017-10-09T03:41:36.467269 #22391] ERROR -- : Unable to post webhook: https://hooks.slack.com/services/XXXXXXXXX/XXXXXXXXX/XXXXXXXXXXXXXXXXXXXXXXXX: #<UserAgent::Result:0x839650f4 @success=false, @body=nil, @data=nil, @code=0, @content_type=nil, @error="#<Net::OpenTimeout: execution expired>">

Steps to reproduce the behavior:

Add "Incoming Webhooks" app to a Slack workspace/channel
Use given webhook address to enable Slack integration in Zammad settings
Create a new ticket or update existing one

Posting the same request generated by Zammad (Integration > Slack > Recent logs > HTTP log) via bash using curl -X POST works perfectly fine.
Googling for similar/related Rails errors brought up only a suggestion to disable IPv6 on the machine, but that didn't solve the issue.

Has anybody else encountered this "_Net::OpenTimeout: execution expired_" error?
Thanks

question

Source

em-ex

All 3 comments

Hi @em-ex , Thanks for your report. Did you try to run curl at the same server as zammad which you say it works fine?

I just tested hooking up to slack from my development machine and it works ok for zammad 2.0.0

muhammadn on 9 Oct 2017

👍1

@muhammadn Thanks for looking into this!
Yes, curl post was tested from the same server and it worked:

The problem is supposedly with how Rails handles DNS, but I'm not an expert...

em-ex on 9 Oct 2017

Ok so I went to examine the code and in app\models\transaction\slack.rb I found that open_timeout was set to 4. Out of ~despair~ curiosity I changed it to 20 and the Slack notification went through.

I should've mentioned that the server is running on pretty old hardware... I think it's ok to close the issue now.

Once again, @muhammadn thanks for taking time to look into this!

em-ex on 10 Oct 2017

👍1

Was this page helpful?

0 / 5 - 0 ratings