Skip to content
This repository has been archived by the owner on Jul 4, 2023. It is now read-only.

Suscribe error #25

Open
raulsanchez-gig opened this issue Apr 25, 2019 · 2 comments
Open

Suscribe error #25

raulsanchez-gig opened this issue Apr 25, 2019 · 2 comments

Comments

@raulsanchez-gig
Copy link

raulsanchez-gig commented Apr 25, 2019

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.

> [email protected] 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
Copy link

abhishekamralkar commented Jul 9, 2019

Same for me. Did you got any solution?

@raulsanchez-gig
Copy link
Author

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants