Previous session PID not found

[beritt]

What version of ejabberd are you using?

17.01

What operating system (version) are you using?

Ubuntu 16.04 LTS

How did you install ejabberd (source, package, distribution)?

Package from website

What did not work as expected? Are there error messages in the log? What
was the unexpected behavior? What was the expected result?

Hello,
I am a XMPP newbie running a server at home (ejabberd 17.01). I have this issue with chatsecure most of the time and sometimes with conversations as well, so it might be server-related.

See the following error message (not the debug loglevel):

2017-02-24 14:27:32.106 [info] <0.499.0>@ejabberd_listener:accept:333 (#Port<0.21243>)
 Accepted connection xxx -> xxx:5222
2017-02-24 14:27:32.688 [info] <0.2775.0>@ejabberd_c2s:wait_for_sasl_response:942
 ({socket_state,fast_tls,{tlssock,#Port<0.21243>,#Port<0.21244>},<0.2774.0>})
 Accepted authentication for xxx by undefined from xxx 
2017-02-24 14:27:32.780 [info] <0.2775.0>@ejabberd_c2s:handle_resume:2886
 Cannot resume session for xxx: Previous session PID not found 
2017-02-24 14:27:32.827 [info] <0.2775.0>@ejabberd_c2s:open_session:1153
 ({socket_state,fast_tls,{tlssock,#Port<0.21243>,#Port<0.21244>},<0.2774.0>})
 Opened session for xxx/chatsecure67751 
2017-02-24 14:27:32.964 [info] <0.2775.0>@ejabberd_c2s:handle_enable:2786
 Stream management with resumption enabled for fxxx/chatsecure67751 
2017-02-24 14:27:32.964 [info] <0.495.0>@mod_carboncopy:iq_handler:102
 carbons enabled for user xxx 
2017-02-24 14:27:33.672 [info] <0.2775.0>@ejabberd_c2s:terminate:1851
 ({socket_state,fast_tls,{tlssock,#Port<0.21243>,#Port<0.21244>},<0.2774.0>})
 Close session for xxx/chatsecure67751 
2017-02-24 14:27:34.125 [info] <0.499.0>@ejabberd_listener:accept:333
 (#Port<0.21245>) Accepted connection xxx:58413 -> xxx:5222 
2017-02-24 14:27:34.707 [info] <0.2780.0>@ejabberd_c2s:wait_for_sasl_response:942
 ({socket_state,fast_tls,{tlssock,#Port<0.21245>,#Port<0.21246>},<0.2779.0>})
 Accepted authentication for xxx by undefined from xxxx 
2017-02-24 14:27:34.824 [info] <0.2780.0>@ejabberd_c2s:handle_resume:2886
 Cannot resume session for xxx@xxx: Previous session PID not found 
2017-02-24 14:27:34.874 [info] <0.2780.0>@ejabberd_c2s:open_session:1153
 ({socket_state,fast_tls,{tlssock,#Port<0.21245>,#Port<0.21246>},<0.2779.0>})
 Opened session for xxx/chatsecure67751 
2017-02-24 14:27:34.987 [info] <0.495.0>@mod_carboncopy:iq_handler:102
 carbons enabled for user xxxx/chatsecure67751 
2017-02-24 14:27:34.987 [info] <0.2780.0>@ejabberd_c2s:handle_enable:2786
 Stream management with resumption enabled for xxx/chatsecure67751 
2017-02-24 14:27:35.577 [info] <0.2780.0>@ejabberd_c2s:terminate:1851
 ({socket_state,fast_tls,{tlssock,#Port<0.21245>,#Port<0.21246>},<0.2779.0>})
 Close session for xxx/chatsecure67751

And this goes on an on for forever (and quite frequently).

To me it looks like the sign in process works good. However, the session is directly terminated after it is opened and for the next sign in process a wrong session PID is presented (or the server has trouble remembering it)- anyways that is only my interpretation and I am really new to that.
This problem sounds very similar to #749 , however that was an older version of ejabberd and this seems to be fixed. I am quite confused about this as nobody seems to have the same issue. So it is maybe just a bad server configuration from my side..

So any help is strongly appreciated and that would be very nice :) Tell me if you need a more detailed debug log.

[zinid]

I'm not quite sure this is a bug, for example, this can happen if a client closes the session normally (via stream trailer) - in this case nothing is resumed.
I close this issue until more info comes from newer ejabberd version.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.