Mailing List CGatePro@mail.stalker.com Message #106397
From: Jeff Wark <jwark@tbaytel.net>
Subject: Re: Stuck sessions
Date: Thu, 04 May 2017 11:58:28 -0400
To: CommuniGate Pro Discussions <CGatePro@mail.stalker.com>
X-Mailer: CommuniGate Pro WebUser v6.1.11
Oh.  That is interesting.  I have used the long web format for a while.

Anyhow, if appears that the first set of numbers in front of the '-' character is the session id you are talking about.  Two things now come up:

1.  There are no active sessions that are older than 10 hours on the Monitors->Access->Sessions page.  The Monitors->Access->HTTPU is showing the 72 'sessions' that aren't going away.  This is extra interesting in that it probably isn't an active session, but a stuck HTTPU process.

2.  The KillSession command doesn't seem to work with just the short version of the session that you describe.  My code is as follows:
>print "The submitted session is: $sessionID\n";
>if ( $cli->KillSession($sessionID) ) {
>  print "Successfully killed session $sessionID\n";
>}
>else {
>  printf "ERROR: Could not kill session: %s\n", $cli->getErrMessage;
>}

Running it looks like this:
$ killaccountsessions.pl 374499
The submitted session is: 374499
ERROR: Could not kill session: sessionID format error
$ killaccountsessions.pl 374499-OyvWZCpFe6D376dMl39C-aodhhdy
The submitted session is: 374499-OyvWZCpFe6D376dMl39C-aodhhdy
Successfully killed session 374499-OyvWZCpFe6D376dMl39C-aodhhdy

Strange.
--

Jeff Wark
Tbaytel Internet
On Thu, 4 May 2017 17:04:23 +0200
"Brian Turnbow" <b.turnbow@twt.it> wrote:
>> Hi Jeff,
>>
>> That is not the session ID in CGP
>> You need to look under monitor -->access--> sessions to find the session
>> ID , it will be a number only.
>>
>> Like this
>> ID Protocol
>> 1354052 XIMSS (HTTPU)
>> 1374741 WEBUSER (HTTP)
>>
>> Then from cli
>> KILLSESSION 1354052
>>
>> When sessions would hang in sip we could not kill them with
>> killaccountsessions, only the session directly.
>>
>> Otherwise a service restart looks like your only option
>>
>> Brian
>>
>>
>>From: CommuniGate Pro Discussions [mailto:CGatePro@mail.stalker.com] On
>> Behalf Of Jeff Wark
>> Sent: giovedý 4 maggio 2017 16:31
>> To: CommuniGate Pro Discussions
>> Subject: Re: Stuck sessions
>>
>> Yep.
>>
>> $ killaccountsessions.pl
>> Enter a session:
>> 1018376-UPDRsN7e50ipUbO5s2pw-aodhhdz
>> The submitted session is: 1018376-UPDRsN7e50ipUbO5s2pw-aodhhdz
>> Couldn't kill session: invalid sessionID
>>
>> But the same program can be used to terminate my own webmail session in
>> the same fashion.
>>
>> Very strange.
>>
>> --
>>
>> Jeff Wark
>> Tbaytel Internet
>> On Thu, 4 May 2017 15:51:06 +0200
>> "Brian Turnbow" <b.turnbow@twt.it> wrote:
>>>> Have you tried to kill the session directly?
>>>>
>>>> i.e. look on the sessions page  to find the corresponding ID and use
>>>> killsession via cli.
>>>> We had to do this with sip sessions previously but 6.1 has been much
>>>> better about not hanging sessions for us.
>>>>
>>>> Best Regards
>>>>
>>>>
>>>> Brian
>>>>
>>>>From: CommuniGate Pro Discussions [mailto:CGatePro@mail.stalker.com] On
>>>> Behalf Of Jeff Wark
>>>> Sent: giovedý 4 maggio 2017 15:26
>>>> To: CommuniGate Pro Discussions
>>>> Subject: Stuck sessions
>>>>
>>>> Hello.
>>>>
>>>> We appear to have a number of stuck user sessions on one of our back
>>>> servers.  We could restart the server, but it would be better if we
>> could
>>>> just get rid of them.  We're running CommuniGate version 6.1.11 on
>>FreeBSD
>>>> 10.
>>>>
>>>> The Threads monitor page has many entries like this:
>>>>
>>>> VHTTPUser Stream 82646312 opening target session 12 day(s)
>>>> locked at VSession VHTTPUser Stream-82645460 
>>>> VHTTPUser Stream 82652950 opening target session 12 day(s)
>>>> locked at VSession VHTTPUser Stream-82652573 
>>>> VHTTPUser Stream 82652573 applying server rules 1 sec
>>>> sleeping
>>>> VHTTPUser Stream 82645848 opening target session 12 day(s)
>>>> locked at VSession VHTTPUser Stream-82645460 
>>>> VHTTPUser Stream 82645460 applying server rules 1 sec
>>>> sleeping
>>>> VHTTPUser Stream 82646574 opening target session 12 day(s)
>>>> locked at VSession VHTTPUser Stream-82645460 
>>>> VHTTPUser Stream 82646052 opening target session 12 day(s)
>>>> locked at VSession VHTTPUser Stream-82645460 
>>>> VHTTPUser Stream 82645564 opening target session 12 day(s)
>>>> locked at VSession VHTTPUser Stream-82645460 
>>>> VHTTPUser Stream 82646747 opening target session 12 day(s)
>>>> locked at VSession VHTTPUser Stream-82645460 
>>>> VHTTPUser Stream 82652605 opening target session 12 day(s)
>>>> locked at VSession VHTTPUser Stream-82652573 
>>>> VHTTPUser Stream 82653192 opening target session 12 day(s)
>>>> locked at VSession VHTTPUser Stream-82652573 
>>>> VHTTPUser Stream 82653450 opening target session 12 day(s)
>>>> locked at VSession VHTTPUser Stream-82652573 
>>>> VHTTPUser Stream 82653717 opening target session 12 day(s)
>>>> locked at VSession VHTTPUser Stream-82652573
>>>>
>>>> And the Monitors->Access->HTTPU page looks a little like this:
>>>> 82645460 [216.211.16.158]:51225 [10.1.1.102]:30737 12
>>>> day(s) applying server rules 12 day(s)
>>>> /Session/958033-zXmodjKbr13zcUQQfH02-aodhhdz/compose.wssp
>>>> 82645564 [216.211.16.158]:51226 [10.1.1.102]:30898 12
>>>> day(s) opening target session 12 day(s)
>>>> /Session/958033-zXmodjKbr13zcUQQfH02-aodhhdz/mailbox.wssp
>>>> 82645848 [216.211.16.158]:51228 [10.1.1.102]:31328 12
>>>> day(s) opening target session 12 day(s)
>>>> /Session/958033-zXmodjKbr13zcUQQfH02-aodhhdz/mailbox.wssp
>>>> 82646052 [216.211.16.158]:51229 [10.1.1.102]:31688 12
>>>> day(s) opening target session 12 day(s)
>>>> /Session/958033-zXmodjKbr13zcUQQfH02-aodhhdz/mailbox.wssp
>>>> 82646312 [216.211.16.158]:51230 [10.1.1.102]:32142 12
>>>> day(s) opening target session 12 day(s)
>>>> /Session/958033-zXmodjKbr13zcUQQfH02-aodhhdz/mailbox.wssp
>>>> 82646574 [216.211.16.158]:51231 [10.1.1.102]:32620 12
>>>> day(s) opening target session 12 day(s)
>>>> /Session/958033-zXmodjKbr13zcUQQfH02-aodhhdz/mailbox.wssp
>>>> 82646747 [216.211.16.158]:51232 [10.1.1.102]:32974 12
>>>> day(s) opening target session 12 day(s)
>>>> /Session/958033-zXmodjKbr13zcUQQfH02-aodhhdz/mailbox.wssp
>>>> 82652573 [216.211.16.158]:51299 [10.1.1.102]:42768 12
>>>> day(s) applying server rules 12 day(s)
>>>> /Session/958125-ifmvTFCo0BGVKHf1jSHs-aodhhdz/compose.wssp
>>>> 82652605 [216.211.16.158]:51300 [10.1.1.102]:42798 12
>>>> day(s) opening target session 12 day(s)
>>>> /Session/958125-ifmvTFCo0BGVKHf1jSHs-aodhhdz/mailbox.wssp
>>>> 82652950 [216.211.16.158]:51301 [10.1.1.102]:43313 12
>>>> day(s) opening target session 12 day(s)
>>>> /Session/958125-ifmvTFCo0BGVKHf1jSHs-aodhhdz/mailbox.wssp
>>>> 82653192 [216.211.16.158]:51302 [10.1.1.102]:43671 12
>>>> day(s) opening target session 12 day(s)
>>>> /Session/958125-ifmvTFCo0BGVKHf1jSHs-aodhhdz/mailbox.wssp
>>>> 82653450 [216.211.16.158]:51303 [10.1.1.102]:44102 12
>>>> day(s) opening target session 12 day(s)
>>>> /Session/958125-ifmvTFCo0BGVKHf1jSHs-aodhhdz/mailbox.wssp
>>>> 82653717 [216.211.16.158]:51304 [10.1.1.102]:44529 12
>>>> day(s) opening target session 12 day(s)
>>>> /Session/958125-ifmvTFCo0BGVKHf1jSHs-aodhhdz/mailbox.wssp
>>>>
>>>> Our sessions have a limit of 12 hours, so 12 days is a bit high.  We
>> also
>>>> have several other sessions that have been open for between 18 and 20
>>>> hours.
>>>>
>>>> Interestingly, we did reboot a front server yesterday at around that
>> time.
>>>>
>>>> When I attempt to use the CLI to kill the account sessions, I just get
>> an
>>>> 'Invalid Session' error.
>>>>
>>>> Any ideas?
>>>> --
>>>>
>>>> Jeff Wark
>>>> Tbaytel Internet
>>>> #############################################################
>>>> This message is sent to you because you are subscribed to
>>>>  the mailing list <CGatePro@mail.stalker.com>.
>>>> To unsubscribe, E-mail to: <CGatePro-off@mail.stalker.com>
>>>> To switch to the DIGEST mode, E-mail to
>> <CGatePro-digest@mail.stalker.com>
>>>> To switch to the INDEX mode, E-mail to
>> <CGatePro-index@mail.stalker.com>
>>>> Send administrative queries to  <CGatePro-request@mail.stalker.com>
>>>>
>>>> #############################################################
>>>> This message is sent to you because you are subscribed to
>>>>  the mailing list <CGatePro@mail.stalker.com>.
>>>> To unsubscribe, E-mail to: <CGatePro-off@mail.stalker.com>
>>>> To switch to the DIGEST mode, E-mail to
>> <CGatePro-digest@mail.stalker.com>
>>>> To switch to the INDEX mode, E-mail to
>> <CGatePro-index@mail.stalker.com>
>>>> Send administrative queries to  <CGatePro-request@mail.stalker.com>
>> #############################################################
>> This message is sent to you because you are subscribed to
>>  the mailing list <CGatePro@mail.stalker.com>.
>> To unsubscribe, E-mail to: <CGatePro-off@mail.stalker.com>
>> To switch to the DIGEST mode, E-mail to <CGatePro-digest@mail.stalker.com>
>> To switch to the INDEX mode, E-mail to <CGatePro-index@mail.stalker.com>
>> Send administrative queries to  <CGatePro-request@mail.stalker.com>
>>
>> #############################################################
>> This message is sent to you because you are subscribed to
>>  the mailing list <CGatePro@mail.stalker.com>.
>> To unsubscribe, E-mail to: <CGatePro-off@mail.stalker.com>
>> To switch to the DIGEST mode, E-mail to <CGatePro-digest@mail.stalker.com>
>> To switch to the INDEX mode, E-mail to <CGatePro-index@mail.stalker.com>
>> Send administrative queries to  <CGatePro-request@mail.stalker.com>

Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster