-
Notifications
You must be signed in to change notification settings - Fork 188
Multiprocessing problems #90
Comments
The Twilio Notification works fine for me. I receive SMS. Well at least the first time. |
Well. Sounds there is a strange problem. [2017-09-21 09:42:55,736: WARNING/ForkPoolWorker-6] Failed to send Rocket message:Invalid URL u'': No schema supplied. Perhaps you meant http://? [2017-09-21 09:43:56,740: INFO/MainProcess] Task notification.tasks.send_notifications[82f101d7-614b-4091-a0cc-30686ce50871] succeeded in 1.02826371184s: None |
Well notifications seem not working for me when an incident is triggered. They only work when I click on the TEST NOTIFICATIONS in the user page. :( |
Ok. I confirm that notifications for Twilio SMS are working when an event is triggered. I receive Twilio SMS on my phone. |
I am running on a Debian 8 |
Fixed for ROCKET first error. Rocket Webhook URl must be set in USer's profile not in settings.py |
Found the "Solution" pretty embarrassing... Turns out celery has to be started seperately. Probably therefore 'celery -A openduty worker -l info' is listed in the Readme file... |
@kjetilmjos co gratulations. Anyway, have you succeeded in running celery using supervisord as a daemonizer? |
Is that the same as running it in daemon mode using systemd? I found a fork from Oxalide, they have made the pull request here with a range of improvements posted by @sofixa. In their repo there is also a folder showing how the project can be runned as deamon using systemd. Check out the systemd folder at: https://github.com/Oxalide/openduty |
Perfect. That is better. Thanks a lot. |
The one I use works with the oxalide fork. They have written a more general email notifier than the original email based one. |
Great. Thanks
…On Sep 22, 2017 06:30, "Kjetil" ***@***.***> wrote:
The one I use works with the oxalide fork. They have written a more
general email notifier than the original email based one.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#90 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABIfkBuBjo6xw9ipyzNQu_xdcTn0Qh7-ks5sk0YEgaJpZM4PcDDr>
.
|
Hi I'm experiencing problems with the
.apply_asynch
method in thehelper.py
line 20.If I leave the
.apply_asynch
on no notifications are sent. Have tried to remove asynch by replacing the line:send_notifications.apply_async((notification.id,) ,eta=notification.send_at)
with
send_notifications(notification.id)
This works and I'm then able to send notifications.
Problem is then off-course that only the first configured notification is sent due to the code being synchronous. Has anybody encountered the same issues?
Really like the functionality of Openduty and to have a open source and free alternative to the expensive pagerduty etc. Would be really nice if we could get a more active community up and running around the repo and maybe port the code to python 3?
The text was updated successfully, but these errors were encountered: