Everything was working and the next day when trying to login on candy caht client on the website it stays on coccencting showing in firebug 503 Service Uavailable error.
Server is running and was rebuted even.
In prosody log there was day before error like this (occured 5 times:
Jun 11 20:21:09 http.server error Traceback[httpserver]: D:\Server\Prosody\plugins\mod_bosh.lua:251: bad argument #1 to 'math_min' (number expected, got nil)
stack traceback:
[C]: in function 'parse'
D:\Server\Prosody\\src\/util\xmppstream.lua:255: in function 'feed'
D:\Server\Prosody\plugins\mod_bosh.lua:128: in function <D:\Server\Prosody\plugins\mod_bosh.lua:112>
D:\Server\Prosody\\src\/util\events.lua:67: in function 'fire_event'
D:\Server\Prosody\\src\/net\http\server.lua:217: in function <D:\Server\Prosody\\src\/net\http\server.lua:160>
[C]: in function 'xpcall'
D:\Server\Prosody\\src\/net\http\server.lua:108: in function 'process_next'
D:\Server\Prosody\\src\/net\http\server.lua:124: in function 'success_cb'
D:\Server\Prosody\\src\/net\http\parser.lua:150: in function 'feed'
D:\Server\Prosody\\src\/net\http\server.lua:146: in function 'onincoming'
D:\Server\Prosody\\src\/net\server_event.lua:626: in function <D:\Server\Prosody\\src\/net\server_event.lua:572>
[C]: in function 'loop'
D:\Server\Prosody\\src\/net\server_event.lua:787: in function <D:\Server\Prosody\\src\/net\server_event.lua:786>
[C]: in function 'xpcall'
D:\Server\Prosody\\src\prosody:373: in function 'loop'
D:\Server\Prosody\\src\prosody:403: in main chunk
[C]: at 0x012f21f0
MattJ
on
Hi, thanks for the report!
Could you provide some information, such as the version of Prosody you are using, and what platform you are running it on?
Changes
owner MattJ
KonradSztukowski
on
I'm using Windows 7 and the version of prosody in console after using server:version() schows "unknown"
KonradSztukowski
on
I have zero connections on my host is shows zero incoming and outgoing when i type s2s:show command
KonradSztukowski
on
The version is probably 0.9 because i have MUC on it
KonradSztukowski
on
I have s2s on jabbim.pl could it be that they have payd service and the brought service just expired?
KonradSztukowski
on
Could it be a problem with IPv4/ IPv6 ? Or with the host on http? the 127.0.0.1 ? in logs from about a year in prosody that error occured 4 times and always randomly and always 5 times in one second.
KonradSztukowski
on
Enabled debugging and error messages on console. Showed muc lock and persistent libs not found, i added them now on startup no errors but still s2s when on console use s2s:show() it shows 0 incoming and outcoming connections. In Candy Chat trying to login still stays on connecting
Zash
on
This traceback is mentioned in #343
> muc lock and persistent libs not found
That suggests trunk, not 0.9.x
Everything was working and the next day when trying to login on candy caht client on the website it stays on coccencting showing in firebug 503 Service Uavailable error. Server is running and was rebuted even. In prosody log there was day before error like this (occured 5 times: Jun 11 20:21:09 http.server error Traceback[httpserver]: D:\Server\Prosody\plugins\mod_bosh.lua:251: bad argument #1 to 'math_min' (number expected, got nil) stack traceback: [C]: in function 'parse' D:\Server\Prosody\\src\/util\xmppstream.lua:255: in function 'feed' D:\Server\Prosody\plugins\mod_bosh.lua:128: in function <D:\Server\Prosody\plugins\mod_bosh.lua:112> D:\Server\Prosody\\src\/util\events.lua:67: in function 'fire_event' D:\Server\Prosody\\src\/net\http\server.lua:217: in function <D:\Server\Prosody\\src\/net\http\server.lua:160> [C]: in function 'xpcall' D:\Server\Prosody\\src\/net\http\server.lua:108: in function 'process_next' D:\Server\Prosody\\src\/net\http\server.lua:124: in function 'success_cb' D:\Server\Prosody\\src\/net\http\parser.lua:150: in function 'feed' D:\Server\Prosody\\src\/net\http\server.lua:146: in function 'onincoming' D:\Server\Prosody\\src\/net\server_event.lua:626: in function <D:\Server\Prosody\\src\/net\server_event.lua:572> [C]: in function 'loop' D:\Server\Prosody\\src\/net\server_event.lua:787: in function <D:\Server\Prosody\\src\/net\server_event.lua:786> [C]: in function 'xpcall' D:\Server\Prosody\\src\prosody:373: in function 'loop' D:\Server\Prosody\\src\prosody:403: in main chunk [C]: at 0x012f21f0
Hi, thanks for the report! Could you provide some information, such as the version of Prosody you are using, and what platform you are running it on?
ChangesI'm using Windows 7 and the version of prosody in console after using server:version() schows "unknown"
I have zero connections on my host is shows zero incoming and outgoing when i type s2s:show command
The version is probably 0.9 because i have MUC on it
I have s2s on jabbim.pl could it be that they have payd service and the brought service just expired?
Could it be a problem with IPv4/ IPv6 ? Or with the host on http? the 127.0.0.1 ? in logs from about a year in prosody that error occured 4 times and always randomly and always 5 times in one second.
Enabled debugging and error messages on console. Showed muc lock and persistent libs not found, i added them now on startup no errors but still s2s when on console use s2s:show() it shows 0 incoming and outcoming connections. In Candy Chat trying to login still stays on connecting
This traceback is mentioned in #343 > muc lock and persistent libs not found That suggests trunk, not 0.9.x
The traceback is fixed in https://hg.prosody.im/0.10/rev/250855633092
Can this be closed? It's unclear to me what the problem here is, apart from the (long since fixed) traceback.
ChangesNo response, guessing issue is from before the Google Code migration so no notifications were sent
Changes