8000 check can login but cant read the message · Issue #3 · ThomasLeister/check_xmpp · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

check can login but cant read the message #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
hagenbauer opened this issue Feb 17, 2018 · 4 comments
Open

check can login but cant read the message #3

hagenbauer opened this issue Feb 17, 2018 · 4 comments
Labels
bug

Comments

@hagenbauer
Copy link
hagenbauer commented Feb 17, 2018 •
edited
Loading

Env

  • Rasbian 8.0
  • go version go1.3.3 linux/arm
  • xmpp ejabberd-17.12

I create a special account on my server for monitoring tasks. I can login into this account with the conversation app on android.

When I try to execute a check my conversation app on android is killed and the check is running into a timeout.
Any ideas?

./check_xmpp -timeout 15s -userid monitoring@caserio.de -password secret -debug
2018/02/17 10:48:01 XMPP check starting ...
2018/02/17 10:48:01 Remote host: chat.caserio.de.
2018/02/17 10:48:01 Connecting to XMPP host chat.caserio.de. ...
2018/02/17 10:48:02 Authentication successful
2018/02/17 10:48:02 XMPP stream is established
2018/02/17 10:48:02 Sending message ...
2018/02/17 10:48:02 Waiting for message to arrive ...
CRITICAL - Timeout
@ThomasLeister
Copy link
Owner

Does the XMPP server work in general? (Can we be sure this is a check_xmpp issue?) Your server seems to crash if either

  • any message is sent ... or
  • a user sends at message to himself/herself (this is how the check works)

@hagenbauer
Copy link
Author
hagenbauer commented Feb 25, 2018 •
edited
Loading
8000

yes. the xmpp server is working. my server is not crashing. just the android app

This is what I see in ejabberd log

ejabberd_listener:accept:302 (<0.1583.1>) Accepted connection ::ffff:7....-> ::ffff:...
ejabberd_c2s:handle_auth_success:432 (tls|<0.1583.1>) Accepted c2s PLAIN authentication for monitoring@xxxxx by mnesia backend from ::ffff:7xxxxx
ejabberd_c2s:bind:403 (tls|<0.1583.1>) Opened c2s session for monxxxx
ejabberd_c2s:process_terminated:271 (tls|<0.1583.1>) Closing c2s session for monitoring@cxxxxConnection failed: connection closed

@ThomasLeister
Copy link
Owner

I have no idea what causes this :( Maybe you can try and use a XMPP account that is not connected to any other client?

@hagenbauer
Copy link
Author
hagenbauer commented Feb 27, 2018 •
edited
Loading

yes. tested that already, no luck

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hagenbauer @ThomasLeister
0