search

tobilg / marathon-slack

Integration for Marathon's Event Bus with Slack
MIT License
42 stars 23 forks source link

Suscribe error #25

Open raulsanchez-gig opened 5 years ago

raulsanchez-gig commented 5 years ago

Hi,

I'm getting this error when I start marathon-slack in DC/OS, this was working a while ago, and suddenly it stopped working.

> marathon-slack@0.4.5 start /usr/local/marathon-slack
> node index.js

Express server listening on port 11681 on 10.90.2.9
Subscribed to the Marathon Event Bus: {"timestamp":1556214433563,"message":"Subscribed to the Marathon Event Bus"}
Error: {"timestamp":1556214433.566,"message":{"type":"error"}}
Subscribed to the Marathon Event Bus: {"timestamp":1556214434581,"message":"Subscribed to the Marathon Event Bus"}
Error: {"timestamp":1556214434.582,"message":{"type":"error"}}
Subscribed to the Marathon Event Bus: {"timestamp":1556214435596,"message":"Subscribed to the Marathon Event Bus"}
Error: {"timestamp":1556214435.597,"message":{"type":"error"}}

Since then, I don't get any notifications in the channel where this is supposed to send the events.

If I send a curl request to listen to the events on mesos api, everything works fine and events are listed if any update happens.

Not sure what could be causing this, and / or how to debug it.

abhishekamralkar commented 5 years ago

Same for me. Did you got any solution?

raulsanchez-gig commented 5 years ago

Hi @abhishekamralkar not really, I've patched the dc/os installation to 1.12 and seems to have fixed this, so there must be a bug somewhere in marathon api that returns the subscribe error unfortunately.