You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Daniel Baker <in...@collisiondetection.biz> on 2020/03/25 21:15:24 UTC

Invalid Hash via SOAP API call

Not sure  why  I am getting this  during  entering of a room :


I get invalid  hash / Access denied   show in the browser:


image



The  url  looks  like this  which seems correct  to my understanding  :


tail -f localhost_access_log.2020-03-25

XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "GET 
/openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1" 
200 96
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "POST 
/openmeetings/services/user/hash?&sid=973f7132-39f7-47d0-b614-7845c4ed0411 
HTTP/1.1" 200 96
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET 
/openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1 
HTTP/1.1" 200 7231
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET 
/openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET 
/openmeetings/css/theme.css HTTP/1.1" 304 -
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET 
/openmeetings/css/custom.css HTTP/1.1" 304 -
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET 
/openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1" 
200 96
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET 
/openmeetings/services/room/32?&sid=25d019cb-728c-4c7e-a88e-88910b3eae51 
HTTP/1.1" 200 444
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "GET 
/openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1" 
200 96
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "POST 
/openmeetings/services/user/hash?&sid=bd8227ad-88d1-41ba-b4ce-69239844e5a1 
HTTP/1.1" 200 96
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET 
**/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.pages.HashPage?0-1.0*-access~denied*&secure=9c271470-cfaa-4e95-9d64-**9210b9e4a7cc&language=1&_=1585164268523 
HTTP/1.1" 200 180
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET 
/openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1 
HTTP/1.1" 200 7328
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET 
/openmeetings/wicket/resource/com.googlecode.wicket.kendo.ui.theme.Initializer/kendo.default.mobile.min-ver-70A144DCABA4386C973AE2446CA25F3D.css 
HTTP/1.1" 200 111339
XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET 
/openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -



OM  Version :


Name OpenMeetings  Version5.0.0-M3 Revisionb739f87 Build date2019-12-11T11:42:09Z


I  can see access denied in the log so  that pinpoints it somewhat.  Is 
there a way  to see my  SOAP call is  correct  or a verbose  logging mode ?

Thanks,

Dan


Re: Invalid Hash via SOAP API call

Posted by Daniel Baker <in...@collisiondetection.biz>.
ok  maybe for another time.


Thanks

On 27/03/2020 15:18, Maxim Solodovnik wrote:
> The only possible ways to achieve this:
> 1) incognito tabs (should work)
> 2) different browsers
>
> I'm not aware of other ways to isolate browser session
>
> It is can be done on server
> But it will be HUGE changes :(((
>
> On Fri, 27 Mar 2020 at 22:16, Daniel Baker 
> <info@collisiondetection.biz <ma...@collisiondetection.biz>> wrote:
>
>     Would it not  be beneficial  to be able to  have the user  be 
>     able to have access to different  rooms at the same  time  without
>     receiving an error?
>
>
>
>     On 27/03/2020 15:07, Maxim Solodovnik wrote:
>>     `open in same browser`
>>     This is the question I have asked million times ....
>>     multiple tabs/windows share _the same_ session
>>     You can't be loggen in with different hashes and have same session
>>
>>     once in ~30 seconds page ping back to refresh session
>>     and you got "Access denied"
>>     expected
>>
>>     On Fri, 27 Mar 2020 at 21:54, Daniel Baker
>>     <info@collisiondetection.biz
>>     <ma...@collisiondetection.biz>> wrote:
>>
>>         Yes  I can  reproduce  this.
>>
>>
>>         If I have  2  different  rooms ( room 29 , 31 ) open  in
>>         same  browser   invalid  hash is  shown.
>>
>>         It also  happens  if  I have   2  rooms  the same ( 29, 29,
>>         ... )
>>
>>
>>         It  actually  takes *some time,   30 seconds* or so  for  the
>>         Invalid  hash  error to show.
>>
>>
>>         Thanks,
>>
>>
>>         Dan
>>
>>         On 27/03/2020 05:07, Maxim Solodovnik wrote:
>>>         Well,
>>>
>>>         just tested hashes
>>>         This error is only observed in case multiple tabs are opened
>>>         in the same browser
>>>
>>>         Is this issue reproducible for you if there is only one user
>>>         in the room?
>>>
>>>         Can you test this behavior with latest M4
>>>         (new version of Moodle plugin will be required)
>>>
>>>         On Thu, 26 Mar 2020 at 14:12, Maxim Solodovnik
>>>         <solomax666@gmail.com <ma...@gmail.com>> wrote:
>>>
>>>             According to above access log
>>>             This URL
>>>             /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>             has been queried 2 times
>>>             First one was
>>>             /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>             Second
>>>             /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>
>>>             Since secureHash is one-time hash here might be the issue
>>>             It is not clear why session was invalidated .....
>>>             I'll try to perform more test tonight/tomorrow
>>>
>>>             On Thu, 26 Mar 2020 at 13:49, Daniel Baker
>>>             <info@collisiondetection.biz
>>>             <ma...@collisiondetection.biz>> wrote:
>>>
>>>                 No other  OM logins.
>>>
>>>
>>>                 I  actually  titled this  wrong, it  is a  REST 
>>>                 call not  SOAP.
>>>
>>>
>>>                 Thanks,
>>>
>>>
>>>                 Dan
>>>
>>>
>>>                 On 26/03/2020 00:27, Maxim Solodovnik wrote:
>>>>                 is it possible OM was opened in second tab with
>>>>                 active login?
>>>>
>>>>                 On Thu, 26 Mar 2020 at 04:15, Daniel Baker
>>>>                 <info@collisiondetection.biz
>>>>                 <ma...@collisiondetection.biz>> wrote:
>>>>
>>>>                     Not sure  why  I am getting this  during 
>>>>                     entering of a room :
>>>>
>>>>
>>>>                     I get invalid  hash / Access denied   show in
>>>>                     the browser:
>>>>
>>>>
>>>>                     image
>>>>
>>>>
>>>>
>>>>                     The  url  looks  like this which seems correct 
>>>>                     to my understanding  :
>>>>
>>>>
>>>>                     tail -f localhost_access_log.2020-03-25
>>>>
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000]
>>>>                     "GET
>>>>                     /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>>>>                     HTTP/1.1" 200 96
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000]
>>>>                     "POST
>>>>                     /openmeetings/services/user/hash?&sid=973f7132-39f7-47d0-b614-7845c4ed0411
>>>>                     HTTP/1.1" 200 96
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000]
>>>>                     "GET
>>>>                     /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>>                     HTTP/1.1" 200 7231
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000]
>>>>                     "GET
>>>>                     /openmeetings/css/theme_om/jquery-ui.min.css
>>>>                     HTTP/1.1" 304 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000]
>>>>                     "GET /openmeetings/css/theme.css HTTP/1.1" 304 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000]
>>>>                     "GET /openmeetings/css/custom.css HTTP/1.1" 304 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000]
>>>>                     "-" 400 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000]
>>>>                     "-" 400 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000]
>>>>                     "GET
>>>>                     /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>>>>                     HTTP/1.1" 200 96
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000]
>>>>                     "GET
>>>>                     /openmeetings/services/room/32?&sid=25d019cb-728c-4c7e-a88e-88910b3eae51
>>>>                     HTTP/1.1" 200 444
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000]
>>>>                     "GET
>>>>                     /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>>>>                     HTTP/1.1" 200 96
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000]
>>>>                     "POST
>>>>                     /openmeetings/services/user/hash?&sid=bd8227ad-88d1-41ba-b4ce-69239844e5a1
>>>>                     HTTP/1.1" 200 96
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000]
>>>>                     "GET
>>>>                     **/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.pages.HashPage?0-1.0*-access~denied*&secure=9c271470-cfaa-4e95-9d64-**9210b9e4a7cc&language=1&_=1585164268523
>>>>                     HTTP/1.1" 200 180
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000]
>>>>                     "GET
>>>>                     /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>>                     HTTP/1.1" 200 7328
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000]
>>>>                     "-" 400 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000]
>>>>                     "-" 400 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000]
>>>>                     "-" 400 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000]
>>>>                     "GET
>>>>                     /openmeetings/wicket/resource/com.googlecode.wicket.kendo.ui.theme.Initializer/kendo.default.mobile.min-ver-70A144DCABA4386C973AE2446CA25F3D.css
>>>>                     HTTP/1.1" 200 111339
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000]
>>>>                     "GET
>>>>                     /openmeetings/css/theme_om/jquery-ui.min.css
>>>>                     HTTP/1.1" 304 -
>>>>
>>>>
>>>>
>>>>                     OM  Version :
>>>>
>>>>
>>>>                     Name OpenMeetings  Version5.0.0-M3 Revisionb739f87 Build date2019-12-11T11:42:09Z
>>>>
>>>>
>>>>                     I  can see access denied in the log so  that
>>>>                     pinpoints it somewhat.  Is there a way  to see
>>>>                     my  SOAP call is  correct or a  verbose 
>>>>                     logging mode ?
>>>>
>>>>                     Thanks,
>>>>
>>>>                     Dan
>>>>
>>>>
>>>>
>>>>                 -- 
>>>>                 WBR
>>>>                 Maxim aka solomax
>>>
>>>
>>>
>>>             -- 
>>>             WBR
>>>             Maxim aka solomax
>>>
>>>
>>>
>>>         -- 
>>>         WBR
>>>         Maxim aka solomax
>>
>>
>>
>>     -- 
>>     WBR
>>     Maxim aka solomax
>
>
>
> -- 
> WBR
> Maxim aka solomax

Re: Invalid Hash via SOAP API call

Posted by Maxim Solodovnik <so...@gmail.com>.
Unfortunately this is impossible
https://stackoverflow.com/questions/16148136/how-can-we-open-a-link-in-private-browsing-mode/16148152#16148152

On Fri, 27 Mar 2020 at 23:09, Daniel Baker <in...@collisiondetection.biz>
wrote:

> I think  maybe there is an easy way to do this .   Yo said   ' 1)
> incognito tabs (should work)'
>
>
> So   we could provide another option :  Open in incognito
>
>
>
> On 27/03/2020 15:18, Maxim Solodovnik wrote:
>
> The only possible ways to achieve this:
> 1) incognito tabs (should work)
> 2) different browsers
>
> I'm not aware of other ways to isolate browser session
>
> It is can be done on server
> But it will be HUGE changes :(((
>
> On Fri, 27 Mar 2020 at 22:16, Daniel Baker <in...@collisiondetection.biz>
> wrote:
>
>> Would it not  be beneficial  to be able to  have the   user  be  able to
>> have access to different  rooms at the same  time  without receiving an
>> error?
>>
>>
>>
>> On 27/03/2020 15:07, Maxim Solodovnik wrote:
>>
>> `open in same browser`
>> This is the question I have asked million times ....
>> multiple tabs/windows share _the same_ session
>> You can't be loggen in with different hashes and have same session
>>
>> once in ~30 seconds page ping back to refresh session
>> and you got "Access denied"
>> expected
>>
>> On Fri, 27 Mar 2020 at 21:54, Daniel Baker <in...@collisiondetection.biz>
>> wrote:
>>
>>> Yes  I can  reproduce  this.
>>>
>>>
>>> If I have  2  different  rooms ( room 29 , 31 )   open  in same  browser
>>>   invalid  hash is  shown.
>>>
>>> It also  happens  if  I have   2  rooms  the  same ( 29, 29, ... )
>>>
>>>
>>> It  actually  takes * some time,   30 seconds* or so  for  the Invalid
>>> hash  error to show.
>>>
>>>
>>> Thanks,
>>>
>>>
>>> Dan
>>> On 27/03/2020 05:07, Maxim Solodovnik wrote:
>>>
>>> Well,
>>>
>>> just tested hashes
>>> This error is only observed in case multiple tabs are opened in the same
>>> browser
>>>
>>> Is this issue reproducible for you if there is only one user in the room?
>>>
>>> Can you test this behavior with latest M4
>>> (new version of Moodle plugin will be required)
>>>
>>> On Thu, 26 Mar 2020 at 14:12, Maxim Solodovnik <so...@gmail.com>
>>> wrote:
>>>
>>>> According to above access log
>>>> This URL
>>>> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>> has been queried 2 times
>>>> First one was
>>>>
>>>> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>> Second
>>>>
>>>> /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>>
>>>> Since secureHash is one-time hash here might be the issue
>>>> It is not clear why session was invalidated .....
>>>> I'll try to perform more test tonight/tomorrow
>>>>
>>>> On Thu, 26 Mar 2020 at 13:49, Daniel Baker <in...@collisiondetection.biz>
>>>> wrote:
>>>>
>>>>> No other  OM logins.
>>>>>
>>>>>
>>>>> I  actually  titled this  wrong,  it  is a  REST  call not  SOAP.
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>>
>>>>> Dan
>>>>>
>>>>>
>>>>> On 26/03/2020 00:27, Maxim Solodovnik wrote:
>>>>>
>>>>> is it possible OM was opened in second tab with active login?
>>>>>
>>>>> On Thu, 26 Mar 2020 at 04:15, Daniel Baker <
>>>>> info@collisiondetection.biz> wrote:
>>>>>
>>>>>> Not sure  why  I am getting this  during  entering of a room :
>>>>>>
>>>>>>
>>>>>> I get invalid  hash / Access denied   show in the browser:
>>>>>>
>>>>>>
>>>>>> [image: image]
>>>>>>
>>>>>>
>>>>>> The  url  looks  like this  which seems correct  to my understanding
>>>>>> :
>>>>>>
>>>>>>
>>>>>>  tail -f localhost_access_log.2020-03-25
>>>>>>
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "GET
>>>>>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>>>>>> 200 96
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "POST
>>>>>> /openmeetings/services/user/hash?&sid=973f7132-39f7-47d0-b614-7845c4ed0411
>>>>>> HTTP/1.1" 200 96
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>>>> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>>>> HTTP/1.1" 200 7231
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>>>> /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>>>> /openmeetings/css/theme.css HTTP/1.1" 304 -
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>>>> /openmeetings/css/custom.css HTTP/1.1" 304 -
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>>>>>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>>>>>> 200 96
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>>>>>> /openmeetings/services/room/32?&sid=25d019cb-728c-4c7e-a88e-88910b3eae51
>>>>>> HTTP/1.1" 200 444
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "GET
>>>>>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>>>>>> 200 96
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "POST
>>>>>> /openmeetings/services/user/hash?&sid=bd8227ad-88d1-41ba-b4ce-69239844e5a1
>>>>>> HTTP/1.1" 200 96
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>>>>>> **/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.pages.HashPage?0-1.0
>>>>>> *-access~denied*&secure=9c271470-cfaa-4e95-9d64-**9210b9e4a7cc&language=1&_=1585164268523
>>>>>> HTTP/1.1" 200 180
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>>>>>> /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>>>> HTTP/1.1" 200 7328
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>>>>>> /openmeetings/wicket/resource/com.googlecode.wicket.kendo.ui.theme.Initializer/kendo.default.mobile.min-ver-70A144DCABA4386C973AE2446CA25F3D.css
>>>>>> HTTP/1.1" 200 111339
>>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>>>>>> /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>>>>>>
>>>>>>
>>>>>>
>>>>>> OM  Version :
>>>>>>
>>>>>>
>>>>>> Name OpenMeetings  Version5.0.0-M3 Revisionb739f87 Build date2019-12-11T11:42:09Z
>>>>>>
>>>>>>
>>>>>> I  can see access denied in the log so  that pinpoints it somewhat.
>>>>>> Is there a way  to see my  SOAP call is  correct  or a  verbose  logging
>>>>>> mode ?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Dan
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> WBR
>>>>> Maxim aka solomax
>>>>>
>>>>>
>>>>
>>>> --
>>>> WBR
>>>> Maxim aka solomax
>>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>>
>
> --
> WBR
> Maxim aka solomax
>
>

-- 
WBR
Maxim aka solomax

Re: Invalid Hash via SOAP API call

Posted by Daniel Baker <in...@collisiondetection.biz>.
I think  maybe there is an easy way to do this .   Yo said   ' 1) 
incognito tabs (should work)'


So   we could provide another option :  Open in incognito



On 27/03/2020 15:18, Maxim Solodovnik wrote:
> The only possible ways to achieve this:
> 1) incognito tabs (should work)
> 2) different browsers
>
> I'm not aware of other ways to isolate browser session
>
> It is can be done on server
> But it will be HUGE changes :(((
>
> On Fri, 27 Mar 2020 at 22:16, Daniel Baker 
> <info@collisiondetection.biz <ma...@collisiondetection.biz>> wrote:
>
>     Would it not  be beneficial  to be able to  have the user  be 
>     able to have access to different  rooms at the same  time  without
>     receiving an error?
>
>
>
>     On 27/03/2020 15:07, Maxim Solodovnik wrote:
>>     `open in same browser`
>>     This is the question I have asked million times ....
>>     multiple tabs/windows share _the same_ session
>>     You can't be loggen in with different hashes and have same session
>>
>>     once in ~30 seconds page ping back to refresh session
>>     and you got "Access denied"
>>     expected
>>
>>     On Fri, 27 Mar 2020 at 21:54, Daniel Baker
>>     <info@collisiondetection.biz
>>     <ma...@collisiondetection.biz>> wrote:
>>
>>         Yes  I can  reproduce  this.
>>
>>
>>         If I have  2  different  rooms ( room 29 , 31 ) open  in
>>         same  browser   invalid  hash is  shown.
>>
>>         It also  happens  if  I have   2  rooms  the same ( 29, 29,
>>         ... )
>>
>>
>>         It  actually  takes *some time,   30 seconds* or so  for  the
>>         Invalid  hash  error to show.
>>
>>
>>         Thanks,
>>
>>
>>         Dan
>>
>>         On 27/03/2020 05:07, Maxim Solodovnik wrote:
>>>         Well,
>>>
>>>         just tested hashes
>>>         This error is only observed in case multiple tabs are opened
>>>         in the same browser
>>>
>>>         Is this issue reproducible for you if there is only one user
>>>         in the room?
>>>
>>>         Can you test this behavior with latest M4
>>>         (new version of Moodle plugin will be required)
>>>
>>>         On Thu, 26 Mar 2020 at 14:12, Maxim Solodovnik
>>>         <solomax666@gmail.com <ma...@gmail.com>> wrote:
>>>
>>>             According to above access log
>>>             This URL
>>>             /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>             has been queried 2 times
>>>             First one was
>>>             /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>             Second
>>>             /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>
>>>             Since secureHash is one-time hash here might be the issue
>>>             It is not clear why session was invalidated .....
>>>             I'll try to perform more test tonight/tomorrow
>>>
>>>             On Thu, 26 Mar 2020 at 13:49, Daniel Baker
>>>             <info@collisiondetection.biz
>>>             <ma...@collisiondetection.biz>> wrote:
>>>
>>>                 No other  OM logins.
>>>
>>>
>>>                 I  actually  titled this  wrong, it  is a  REST 
>>>                 call not  SOAP.
>>>
>>>
>>>                 Thanks,
>>>
>>>
>>>                 Dan
>>>
>>>
>>>                 On 26/03/2020 00:27, Maxim Solodovnik wrote:
>>>>                 is it possible OM was opened in second tab with
>>>>                 active login?
>>>>
>>>>                 On Thu, 26 Mar 2020 at 04:15, Daniel Baker
>>>>                 <info@collisiondetection.biz
>>>>                 <ma...@collisiondetection.biz>> wrote:
>>>>
>>>>                     Not sure  why  I am getting this  during 
>>>>                     entering of a room :
>>>>
>>>>
>>>>                     I get invalid  hash / Access denied   show in
>>>>                     the browser:
>>>>
>>>>
>>>>                     image
>>>>
>>>>
>>>>
>>>>                     The  url  looks  like this which seems correct 
>>>>                     to my understanding  :
>>>>
>>>>
>>>>                     tail -f localhost_access_log.2020-03-25
>>>>
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000]
>>>>                     "GET
>>>>                     /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>>>>                     HTTP/1.1" 200 96
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000]
>>>>                     "POST
>>>>                     /openmeetings/services/user/hash?&sid=973f7132-39f7-47d0-b614-7845c4ed0411
>>>>                     HTTP/1.1" 200 96
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000]
>>>>                     "GET
>>>>                     /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>>                     HTTP/1.1" 200 7231
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000]
>>>>                     "GET
>>>>                     /openmeetings/css/theme_om/jquery-ui.min.css
>>>>                     HTTP/1.1" 304 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000]
>>>>                     "GET /openmeetings/css/theme.css HTTP/1.1" 304 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000]
>>>>                     "GET /openmeetings/css/custom.css HTTP/1.1" 304 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000]
>>>>                     "-" 400 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000]
>>>>                     "-" 400 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000]
>>>>                     "GET
>>>>                     /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>>>>                     HTTP/1.1" 200 96
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000]
>>>>                     "GET
>>>>                     /openmeetings/services/room/32?&sid=25d019cb-728c-4c7e-a88e-88910b3eae51
>>>>                     HTTP/1.1" 200 444
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000]
>>>>                     "GET
>>>>                     /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>>>>                     HTTP/1.1" 200 96
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000]
>>>>                     "POST
>>>>                     /openmeetings/services/user/hash?&sid=bd8227ad-88d1-41ba-b4ce-69239844e5a1
>>>>                     HTTP/1.1" 200 96
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000]
>>>>                     "GET
>>>>                     **/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.pages.HashPage?0-1.0*-access~denied*&secure=9c271470-cfaa-4e95-9d64-**9210b9e4a7cc&language=1&_=1585164268523
>>>>                     HTTP/1.1" 200 180
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000]
>>>>                     "GET
>>>>                     /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>>                     HTTP/1.1" 200 7328
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000]
>>>>                     "-" 400 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000]
>>>>                     "-" 400 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000]
>>>>                     "-" 400 -
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000]
>>>>                     "GET
>>>>                     /openmeetings/wicket/resource/com.googlecode.wicket.kendo.ui.theme.Initializer/kendo.default.mobile.min-ver-70A144DCABA4386C973AE2446CA25F3D.css
>>>>                     HTTP/1.1" 200 111339
>>>>                     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000]
>>>>                     "GET
>>>>                     /openmeetings/css/theme_om/jquery-ui.min.css
>>>>                     HTTP/1.1" 304 -
>>>>
>>>>
>>>>
>>>>                     OM  Version :
>>>>
>>>>
>>>>                     Name OpenMeetings  Version5.0.0-M3 Revisionb739f87 Build date2019-12-11T11:42:09Z
>>>>
>>>>
>>>>                     I  can see access denied in the log so  that
>>>>                     pinpoints it somewhat.  Is there a way  to see
>>>>                     my  SOAP call is  correct or a  verbose 
>>>>                     logging mode ?
>>>>
>>>>                     Thanks,
>>>>
>>>>                     Dan
>>>>
>>>>
>>>>
>>>>                 -- 
>>>>                 WBR
>>>>                 Maxim aka solomax
>>>
>>>
>>>
>>>             -- 
>>>             WBR
>>>             Maxim aka solomax
>>>
>>>
>>>
>>>         -- 
>>>         WBR
>>>         Maxim aka solomax
>>
>>
>>
>>     -- 
>>     WBR
>>     Maxim aka solomax
>
>
>
> -- 
> WBR
> Maxim aka solomax

Re: Invalid Hash via SOAP API call

Posted by Maxim Solodovnik <so...@gmail.com>.
The only possible ways to achieve this:
1) incognito tabs (should work)
2) different browsers

I'm not aware of other ways to isolate browser session

It is can be done on server
But it will be HUGE changes :(((

On Fri, 27 Mar 2020 at 22:16, Daniel Baker <in...@collisiondetection.biz>
wrote:

> Would it not  be beneficial  to be able to  have the   user  be  able to
> have access to different  rooms at the same  time  without receiving an
> error?
>
>
>
> On 27/03/2020 15:07, Maxim Solodovnik wrote:
>
> `open in same browser`
> This is the question I have asked million times ....
> multiple tabs/windows share _the same_ session
> You can't be loggen in with different hashes and have same session
>
> once in ~30 seconds page ping back to refresh session
> and you got "Access denied"
> expected
>
> On Fri, 27 Mar 2020 at 21:54, Daniel Baker <in...@collisiondetection.biz>
> wrote:
>
>> Yes  I can  reproduce  this.
>>
>>
>> If I have  2  different  rooms ( room 29 , 31 )   open  in same  browser
>>   invalid  hash is  shown.
>>
>> It also  happens  if  I have   2  rooms  the  same ( 29, 29, ... )
>>
>>
>> It  actually  takes * some time,   30 seconds* or so  for  the Invalid
>> hash  error to show.
>>
>>
>> Thanks,
>>
>>
>> Dan
>> On 27/03/2020 05:07, Maxim Solodovnik wrote:
>>
>> Well,
>>
>> just tested hashes
>> This error is only observed in case multiple tabs are opened in the same
>> browser
>>
>> Is this issue reproducible for you if there is only one user in the room?
>>
>> Can you test this behavior with latest M4
>> (new version of Moodle plugin will be required)
>>
>> On Thu, 26 Mar 2020 at 14:12, Maxim Solodovnik <so...@gmail.com>
>> wrote:
>>
>>> According to above access log
>>> This URL
>>> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>> has been queried 2 times
>>> First one was
>>>
>>> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>> Second
>>>
>>> /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>
>>> Since secureHash is one-time hash here might be the issue
>>> It is not clear why session was invalidated .....
>>> I'll try to perform more test tonight/tomorrow
>>>
>>> On Thu, 26 Mar 2020 at 13:49, Daniel Baker <in...@collisiondetection.biz>
>>> wrote:
>>>
>>>> No other  OM logins.
>>>>
>>>>
>>>> I  actually  titled this  wrong,  it  is a  REST  call not  SOAP.
>>>>
>>>>
>>>> Thanks,
>>>>
>>>>
>>>> Dan
>>>>
>>>>
>>>> On 26/03/2020 00:27, Maxim Solodovnik wrote:
>>>>
>>>> is it possible OM was opened in second tab with active login?
>>>>
>>>> On Thu, 26 Mar 2020 at 04:15, Daniel Baker <in...@collisiondetection.biz>
>>>> wrote:
>>>>
>>>>> Not sure  why  I am getting this  during  entering of a room :
>>>>>
>>>>>
>>>>> I get invalid  hash / Access denied   show in the browser:
>>>>>
>>>>>
>>>>> [image: image]
>>>>>
>>>>>
>>>>> The  url  looks  like this  which seems correct  to my understanding  :
>>>>>
>>>>>
>>>>>  tail -f localhost_access_log.2020-03-25
>>>>>
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "GET
>>>>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>>>>> 200 96
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "POST
>>>>> /openmeetings/services/user/hash?&sid=973f7132-39f7-47d0-b614-7845c4ed0411
>>>>> HTTP/1.1" 200 96
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>>> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>>> HTTP/1.1" 200 7231
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>>> /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>>> /openmeetings/css/theme.css HTTP/1.1" 304 -
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>>> /openmeetings/css/custom.css HTTP/1.1" 304 -
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>>>>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>>>>> 200 96
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>>>>> /openmeetings/services/room/32?&sid=25d019cb-728c-4c7e-a88e-88910b3eae51
>>>>> HTTP/1.1" 200 444
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "GET
>>>>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>>>>> 200 96
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "POST
>>>>> /openmeetings/services/user/hash?&sid=bd8227ad-88d1-41ba-b4ce-69239844e5a1
>>>>> HTTP/1.1" 200 96
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>>>>> **/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.pages.HashPage?0-1.0
>>>>> *-access~denied*&secure=9c271470-cfaa-4e95-9d64-**9210b9e4a7cc&language=1&_=1585164268523
>>>>> HTTP/1.1" 200 180
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>>>>> /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>>> HTTP/1.1" 200 7328
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>>>>> /openmeetings/wicket/resource/com.googlecode.wicket.kendo.ui.theme.Initializer/kendo.default.mobile.min-ver-70A144DCABA4386C973AE2446CA25F3D.css
>>>>> HTTP/1.1" 200 111339
>>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>>>>> /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>>>>>
>>>>>
>>>>>
>>>>> OM  Version :
>>>>>
>>>>>
>>>>> Name OpenMeetings  Version5.0.0-M3 Revisionb739f87 Build date2019-12-11T11:42:09Z
>>>>>
>>>>>
>>>>> I  can see access denied in the log so  that pinpoints it somewhat.
>>>>> Is there a way  to see my  SOAP call is  correct  or a  verbose  logging
>>>>> mode ?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Dan
>>>>>
>>>>
>>>>
>>>> --
>>>> WBR
>>>> Maxim aka solomax
>>>>
>>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>>
>
> --
> WBR
> Maxim aka solomax
>
>

-- 
WBR
Maxim aka solomax

Re: Invalid Hash via SOAP API call

Posted by Daniel Baker <in...@collisiondetection.biz>.
Would it not  be beneficial  to be able to  have the   user  be able to 
have access to different  rooms at the same  time  without receiving an 
error?



On 27/03/2020 15:07, Maxim Solodovnik wrote:
> `open in same browser`
> This is the question I have asked million times ....
> multiple tabs/windows share _the same_ session
> You can't be loggen in with different hashes and have same session
>
> once in ~30 seconds page ping back to refresh session
> and you got "Access denied"
> expected
>
> On Fri, 27 Mar 2020 at 21:54, Daniel Baker 
> <info@collisiondetection.biz <ma...@collisiondetection.biz>> wrote:
>
>     Yes  I can  reproduce  this.
>
>
>     If I have  2  different  rooms ( room 29 , 31 )   open in same 
>     browser   invalid  hash is  shown.
>
>     It also  happens  if  I have   2  rooms  the  same ( 29, 29, ... )
>
>
>     It  actually  takes *some time,   30 seconds* or so  for  the
>     Invalid  hash  error to show.
>
>
>     Thanks,
>
>
>     Dan
>
>     On 27/03/2020 05:07, Maxim Solodovnik wrote:
>>     Well,
>>
>>     just tested hashes
>>     This error is only observed in case multiple tabs are opened in
>>     the same browser
>>
>>     Is this issue reproducible for you if there is only one user in
>>     the room?
>>
>>     Can you test this behavior with latest M4
>>     (new version of Moodle plugin will be required)
>>
>>     On Thu, 26 Mar 2020 at 14:12, Maxim Solodovnik
>>     <solomax666@gmail.com <ma...@gmail.com>> wrote:
>>
>>         According to above access log
>>         This URL
>>         /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>         has been queried 2 times
>>         First one was
>>         /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>         Second
>>         /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>
>>         Since secureHash is one-time hash here might be the issue
>>         It is not clear why session was invalidated .....
>>         I'll try to perform more test tonight/tomorrow
>>
>>         On Thu, 26 Mar 2020 at 13:49, Daniel Baker
>>         <info@collisiondetection.biz
>>         <ma...@collisiondetection.biz>> wrote:
>>
>>             No other  OM logins.
>>
>>
>>             I  actually  titled this  wrong,  it  is a REST  call
>>             not  SOAP.
>>
>>
>>             Thanks,
>>
>>
>>             Dan
>>
>>
>>             On 26/03/2020 00:27, Maxim Solodovnik wrote:
>>>             is it possible OM was opened in second tab with active
>>>             login?
>>>
>>>             On Thu, 26 Mar 2020 at 04:15, Daniel Baker
>>>             <info@collisiondetection.biz
>>>             <ma...@collisiondetection.biz>> wrote:
>>>
>>>                 Not sure  why  I am getting this during  entering of
>>>                 a room :
>>>
>>>
>>>                 I get invalid  hash / Access denied show in the browser:
>>>
>>>
>>>                 image
>>>
>>>
>>>
>>>                 The  url  looks  like this  which seems correct  to
>>>                 my understanding  :
>>>
>>>
>>>                 tail -f localhost_access_log.2020-03-25
>>>
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "GET
>>>                 /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>>>                 HTTP/1.1" 200 96
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000]
>>>                 "POST
>>>                 /openmeetings/services/user/hash?&sid=973f7132-39f7-47d0-b614-7845c4ed0411
>>>                 HTTP/1.1" 200 96
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>                 /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>                 HTTP/1.1" 200 7231
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>                 /openmeetings/css/theme_om/jquery-ui.min.css
>>>                 HTTP/1.1" 304 -
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>                 /openmeetings/css/theme.css HTTP/1.1" 304 -
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>                 /openmeetings/css/custom.css HTTP/1.1" 304 -
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-"
>>>                 400 -
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-"
>>>                 400 -
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>>>                 /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>>>                 HTTP/1.1" 200 96
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>>>                 /openmeetings/services/room/32?&sid=25d019cb-728c-4c7e-a88e-88910b3eae51
>>>                 HTTP/1.1" 200 444
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "GET
>>>                 /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>>>                 HTTP/1.1" 200 96
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000]
>>>                 "POST
>>>                 /openmeetings/services/user/hash?&sid=bd8227ad-88d1-41ba-b4ce-69239844e5a1
>>>                 HTTP/1.1" 200 96
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>>>                 **/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.pages.HashPage?0-1.0*-access~denied*&secure=9c271470-cfaa-4e95-9d64-**9210b9e4a7cc&language=1&_=1585164268523
>>>                 HTTP/1.1" 200 180
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>>>                 /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>                 HTTP/1.1" 200 7328
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-"
>>>                 400 -
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-"
>>>                 400 -
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-"
>>>                 400 -
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>>>                 /openmeetings/wicket/resource/com.googlecode.wicket.kendo.ui.theme.Initializer/kendo.default.mobile.min-ver-70A144DCABA4386C973AE2446CA25F3D.css
>>>                 HTTP/1.1" 200 111339
>>>                 XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>>>                 /openmeetings/css/theme_om/jquery-ui.min.css
>>>                 HTTP/1.1" 304 -
>>>
>>>
>>>
>>>                 OM  Version :
>>>
>>>
>>>                 Name OpenMeetings  Version5.0.0-M3 Revisionb739f87 Build date2019-12-11T11:42:09Z
>>>
>>>
>>>                 I  can see access denied in the log so  that
>>>                 pinpoints it somewhat.  Is there a way  to see my 
>>>                 SOAP call is correct  or a  verbose  logging mode ?
>>>
>>>                 Thanks,
>>>
>>>                 Dan
>>>
>>>
>>>
>>>             -- 
>>>             WBR
>>>             Maxim aka solomax
>>
>>
>>
>>         -- 
>>         WBR
>>         Maxim aka solomax
>>
>>
>>
>>     -- 
>>     WBR
>>     Maxim aka solomax
>
>
>
> -- 
> WBR
> Maxim aka solomax

Re: unable to get KMS 6.13.0 started on debian buster 5.0.0 M3 tomcat3 running OK

Posted by Maxim Solodovnik <so...@gmail.com>.
I would start init.d stript in "manual mode" i.e. so it will output to
console
maybe this will show what is going on ...

On Fri, 27 Mar 2020 at 23:45, <in...@bureau-de-poste.net> wrote:

> not really - an "invalid argument" and a "pipe call broken":
>
>
> Mar 27 17:26:54 server1.searchy.biz systemd[1]: Starting LSB: Kurento
> Media Server daemon...
> -- Subject: A start job for unit kurento-media-server.service has begun
> execution
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> --
> -- A start job for unit kurento-media-server.service has begun execution.
> --
> -- The job identifier is 2344.
> Mar 27 17:26:54 server1.searchy.biz kurento-media-server[12061]: Start
> Kurento Media Server:Configure Kernel resource limits for Kurento Media Ser
> Mar 27 17:26:54 server1.searchy.biz kurento-media-server[12061]:
> /etc/init.d/kurento-media-server: 122: /etc/init.d/kurento-media-server:
> Pipe call failed
> Mar 27 17:26:54 server1.searchy.biz systemd[1]:
> kurento-media-server.service: Control process exited, code=exited,
> status=2/INVALIDARGUMENT
> -- Subject: Unit process exited
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> --
> -- An ExecStart= process belonging to unit kurento-media-server.service
> has exited.
> --
> -- The process' exit code is 'exited' and its exit status is 2.
> Mar 27 17:26:54 server1.searchy.biz systemd[1]:
> kurento-media-server.service: Failed with result 'exit-code'.
> -- Subject: Unit failed
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> --
> -- The unit kurento-media-server.service has entered the 'failed' state
> with result 'exit-code'.
> Mar 27 17:26:54 server1.searchy.biz systemd[1]: Failed to start LSB:
> Kurento Media Server daemon.
> -- Subject: A start job for unit kurento-media-server.service has failed
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support
> --
> -- A start job for unit kurento-media-server.service has finished with a
> failure.
> --
> -- The job identifier is 2344 and the job result is failed.
>
>
>
> Quoting Maxim Solodovnik <so...@gmail.com>:
>
> Any hint from `journalctl -xe` ?
>
> On Fri, 27 Mar 2020 at 23:14, <in...@bureau-de-poste.net> wrote:
>
>>
>>
>> *of course - on both the /etc/init.d/kurento-media-server and
>> /etc/default/kurento-media-server files Quoting Maxim Solodovnik
>> <solomax666@gmail.com <so...@gmail.com>>:*
>>
>> *Do you have START_DAEMON="true" ?*
>>
>> *On Fri, 27 Mar 2020 at 23:05, <info@bureau-de-poste.net
>> <in...@bureau-de-poste.net>> wrote:*
>>
>>>
>>> *It's true that in /etc/default/kurento-media-server the user was set to
>>> "kurento" - changing it to "nobody" (which I HAD done before but probably
>>> forgot to do with update from 6.10 to 6.13 did not help:  *
>>> *● kurento-media-server.service - LSB: Kurento Media Server daemon*
>>> *   Loaded: loaded (/etc/init.d/kurento-media-server; generated)*
>>> *   Active: failed (Result: exit-code) since Fri 2020-03-27 17:00:24
>>> CET; 6s ago*
>>> *     Docs: man:systemd-sysv-generator(8)*
>>> *  Process: 6939 ExecStart=/etc/init.d/kurento-media-server start
>>> (code=exited, status=2)*
>>>
>>> *Mar 27 17:00:24 server1.searchy.biz <http://server1.searchy.biz>
>>> systemd[1]: Starting LSB: Kurento Media Server daemon...*
>>> *Mar 27 17:00:24 server1.searchy.biz <http://server1.searchy.biz>
>>> kurento-media-server[6939]: Start Kurento Media Server:Configure Kernel
>>> resource limits for Kurento Media Serv*
>>> *Mar 27 17:00:24 server1.searchy.biz <http://server1.searchy.biz>
>>> kurento-media-server[6939]: /etc/init.d/kurento-media-server: 122:
>>> /etc/init.d/kurento-media-server: Pipe call*
>>> *Mar 27 17:00:24 server1.searchy.biz <http://server1.searchy.biz>
>>> systemd[1]: kurento-media-server.service: Control process exited,
>>> code=exited, status=2/INVALIDARGUMENT*
>>> *Mar 27 17:00:24 server1.searchy.biz <http://server1.searchy.biz>
>>> systemd[1]: kurento-media-server.service: Failed with result 'exit-code'.*
>>> *Mar 27 17:00:24 server1.searchy.biz <http://server1.searchy.biz>
>>> systemd[1]: Failed to start LSB: Kurento Media Server daemon.*
>>>
>>>
>>>
>>>
>>>
>>> *You probably don't have time to help with this now, Maxim, as work on
>>> getting 5.0.0 to release is more important I understand.  If someone else
>>> has this up and running  - especially M4 (which I plan to move to tomorrow)
>>> on buster, please let me know if you can help debug om logs. regards,*
>>>
>>>
>>>
>>> *ed Quoting Maxim Solodovnik <solomax666@gmail.com
>>> <so...@gmail.com>>:*
>>>
>>> */etc/default/kurento-media-server*
>>>
>>> *START_DAEMON="true"*
>>> *DAEMON_USER="nobody"    #### SAME USER AS STARTED OM*
>>>
>>> *On Fri, 27 Mar 2020 at 22:15, <info@bureau-de-poste.net
>>> <in...@bureau-de-poste.net>> wrote:*
>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *    systemctl status kurento-media-server.status returns: ●
>>>> kurento-media-server.service - LSB: Kurento Media Server daemon
>>>>  Loaded: loaded (/etc/init.d/kurento-media-server; generated)       Active:
>>>> failed (Result: exit-code) since Sat 2020-03-21 22:12:26  CET; 5 days ago
>>>>       Docs: man:systemd-sysv-generator(8)      Process: 7791
>>>> ExecStart=/etc/init.d/kurento-media-server start  (code=exited, status=2)
>>>>       Mar 21 22:12:26 server1.searchy.biz <http://server1.searchy.biz>
>>>> systemd[1]: Starting LSB:  Kurento Media Server daemon...    Mar 21
>>>> 22:12:26 server1.searchy.biz <http://server1.searchy.biz>
>>>> kurento-media-server[7791]:  Start Kurento Media Server:Configure Kernel
>>>> resource limits for  Kurento Media Server.    Mar 21 22:12:26
>>>> server1.searchy.biz <http://server1.searchy.biz>
>>>> kurento-media-server[7791]:  /etc/init.d/kurento-media-server: 122:
>>>> /etc/init.d/kurento-media-server: Pipe call failed    Mar 21 22:12:26
>>>> server1.searchy.biz <http://server1.searchy.biz> systemd[1]:
>>>> kurento-media-server.service: Control process exited, code=exited,
>>>> status=2/INVALIDARGUMENT    Mar 21 22:12:26 server1.searchy.biz
>>>> <http://server1.searchy.biz> systemd[1]:  kurento-media-server.service:
>>>> Failed with result 'exit-code'.    Mar 21 22:12:26 server1.searchy.biz
>>>> <http://server1.searchy.biz> systemd[1]: Failed to start  LSB: Kurento
>>>> Media Server daemon.   root@server1 ~ # aptitude show kurento-media-server
>>>>   Package: kurento-media-server   Version: 6.13.0-0kurento1.18.04   New:
>>>> yes   State: installed   Automatically installed: no   Priority: optional
>>>> Section: video   Maintainer: Kurento <kurento@googlegroups.com
>>>> <ku...@googlegroups.com>>   Architecture: amd64   Uncompressed Size:
>>>> 2,043 k   Depends: kms-core (>= 6.7.0), kms-jsonrpc, kmsjsoncpp,
>>>> libboost-filesystem1.65.1, libboost-log1.65.1,
>>>> libboost-program-options1.65.1,            libboost-system1.65.1,
>>>> libboost-thread1.65.1, libc6 (>=  2.24), libgcc1 (>= 1:3.0), libglib2.0-0
>>>> (>= 2.41.1), libglibmm-2.4-1v5  (>= 2.54.0),            libgstreamer1.5-0
>>>> (>= 1.8.1), libsigc++-2.0-0v5 (>= 2.8.0),  libssl1.0.0 (>= 1.0.0),
>>>> libstdc++6 (>= 6), binutils, gstreamer1.5-libav,
>>>>  gstreamer1.5-plugins-bad, gstreamer1.5-plugins-base,
>>>> gstreamer1.5-plugins-good, gstreamer1.5-plugins-ugly, kms-elements (>=
>>>> 6.7.0), kms-filters            (>= 6.7.0), libgstreamer-plugins-base1.5-0
>>>> Suggests: kurento-dbg   Breaks: kurento-media-server-6.0   Replaces:
>>>> kurento-media-server-6.0   Description: Kurento Media Server    KMS is a
>>>> WebRTC-compatible server that processes audio and video  streams, doing
>>>> composable pipeline-based processing of media.   Homepage:
>>>> https://www.kurento.org <https://www.kurento.org> this is the output of
>>>> /opt/log/openmeetings.log:     INFO 03-14 15:54:38.301
>>>> o.s.w.c.ContextLoader:271 [main] - Root  WebApplicationContext:
>>>> initialization started     INFO 03-14 15:54:38.953
>>>> o.s.o.j.LocalEntityManagerFactoryBean:416  [main] - Initialized JPA
>>>> EntityManagerFactory for persistence unit  'openmeetings'     INFO 03-14
>>>> 15:54:39.170 o.s.s.c.ThreadPoolTaskExecutor:171 [main]  - Initializing
>>>> ExecutorService 'taskExecutor'     INFO 03-14 15:54:40.406
>>>> o.k.j.c.JsonRpcClientNettyWebSocket:191  [rbeatExec-e1-t0] -
>>>> [KurentoClient]  Connecting native client     INFO 03-14 15:54:40.409
>>>> o.k.j.c.JsonRpcClientNettyWebSocket:220  [rbeatExec-e1-t0] -
>>>> [KurentoClient]  Creating new NioEventLoopGroup     INFO 03-14 15:54:40.526
>>>> o.k.j.c.JsonRpcClientNettyWebSocket:234  [ntLoopGroup-2-1] -
>>>> [KurentoClient]  Initiating new Netty channel.  Will create new handler
>>>> too!     WARN 03-14 15:54:40.579 o.k.j.c.JsonRpcClientNettyWebSocket:308
>>>> [rbeatExec-e1-t0] - [KurentoClient]  Trying to close a
>>>> JsonRpcClientNettyWebSocket with channel == null     WARN 03-14
>>>> 15:54:40.581 o.k.j.c.JsonRpcClient:270  [rbeatExec-e1-t0] -
>>>> [KurentoClient]  Error sending heartbeat to  server. Exception:
>>>> [KurentoClient]  Exception connecting to WebSocket  server
>>>> ws://127.0.0.1:8888/kurento <http://127.0.0.1:8888/kurento>     INFO 03-14
>>>> 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:191  [main] -
>>>> [KurentoClient]  Connecting native client     WARN 03-14 15:54:40.581
>>>> o.k.j.c.JsonRpcClient:287  [rbeatExec-e1-t0] - [KurentoClient]  Stopping
>>>> heartbeat and closing  client: failure during heartbeat mechanism     INFO
>>>> 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:220  [main] -
>>>> [KurentoClient]  Creating new NioEventLoopGroup     INFO 03-14 15:54:40.582
>>>> o.k.j.c.JsonRpcClientNettyWebSocket:234  [ntLoopGroup-3-1] -
>>>> [KurentoClient]  Initiating new Netty channel.  Will create new handler
>>>> too!     WARN 03-14 15:54:40.584 o.k.j.c.JsonRpcClientNettyWebSocket:308
>>>> [main] - [KurentoClient]  Trying to close a  JsonRpcClientNettyWebSocket
>>>> with channel == null     WARN 03-14 15:54:40.585
>>>> o.a.o.c.r.KurentoHandler:124 [main] - Fail  to create Kurento client, will
>>>> re-try in 10000 ms     INFO 03-14 15:54:40.707
>>>> o.q.i.StdSchedulerFactory:1220 [main] -  Using default implementation for
>>>> ThreadExecutor     INFO 03-14 15:54:40.716 o.q.c.SchedulerSignalerImpl:61
>>>> [main] -  Initialized Scheduler Signaller of type: class
>>>> org.quartz.core.SchedulerSignalerImpl     INFO 03-14 15:54:40.716
>>>> o.q.c.QuartzScheduler:229 [main] - Quartz  Scheduler v.2.3.2 created.
>>>>   INFO 03-14 15:54:40.717 o.q.s.RAMJobStore:155 [main] - RAMJobStore
>>>> initialized.     INFO 03-14 15:54:40.717 o.q.c.QuartzScheduler:294 [main]
>>>> -  Scheduler meta-data: Quartz Scheduler (v2.3.2)
>>>> 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' with
>>>> instanceId 'NON_CLUSTERED'      Scheduler class:
>>>> 'org.quartz.core.QuartzScheduler' - running locally.      NOT STARTED.
>>>> Currently in standby mode.      Number of jobs executed: 0      Using
>>>> thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
>>>> Using job-store 'org.quartz.simpl.RAMJobStore' - which does not  support
>>>> persistence. and is not clustered. port 8888 is not firewalles - neither is
>>>> 5443. Any idea what to do to start KMS on buster - tomcat3 is running fine
>>>> -  this is 5.0.0 M3 adn I want to install M4 very soon. Thanks for any
>>>> ideas or help Ed*
>>>>
>>>
>>>
>>> *--*
>>>
>>> *WBR Maxim aka solomax*
>>>
>>>
>>>
>>>
>>
>>
>> *--*
>>
>> *WBR Maxim aka solomax*
>>
>>
>>
>>
>
>
> *--*
>
> *WBR Maxim aka solomax*
>
>
>
>

-- 
WBR
Maxim aka solomax

Re: unable to get KMS 6.13.0 started on debian buster 5.0.0 M3 tomcat3 running OK

Posted by in...@bureau-de-poste.net.
  not really - an "invalid argument" and a "pipe call broken":

 
  Mar 27 17:26:54 server1.searchy.biz systemd[1]: Starting LSB:  
Kurento Media Server daemon...
  -- Subject: A start job for unit kurento-media-server.service has  
begun execution
  -- Defined-By: systemd
  -- Support: https://www.debian.org/support
  --
  -- A start job for unit kurento-media-server.service has begun execution.
  --
  -- The job identifier is 2344.
  Mar 27 17:26:54 server1.searchy.biz kurento-media-server[12061]:  
Start Kurento Media Server:Configure Kernel resource limits for  
Kurento Media Ser
  Mar 27 17:26:54 server1.searchy.biz kurento-media-server[12061]:  
/etc/init.d/kurento-media-server: 122:  
/etc/init.d/kurento-media-server: Pipe call failed
  Mar 27 17:26:54 server1.searchy.biz systemd[1]:  
kurento-media-server.service: Control process exited, code=exited,  
status=2/INVALIDARGUMENT
  -- Subject: Unit process exited
  -- Defined-By: systemd
  -- Support: https://www.debian.org/support
  --
  -- An ExecStart= process belonging to unit  
kurento-media-server.service has exited.
  --
  -- The process' exit code is 'exited' and its exit status is 2.
  Mar 27 17:26:54 server1.searchy.biz systemd[1]:  
kurento-media-server.service: Failed with result 'exit-code'.
  -- Subject: Unit failed
  -- Defined-By: systemd
  -- Support: https://www.debian.org/support
  --
  -- The unit kurento-media-server.service has entered the 'failed'  
state with result 'exit-code'.
  Mar 27 17:26:54 server1.searchy.biz systemd[1]: Failed to start LSB:  
Kurento Media Server daemon.
  -- Subject: A start job for unit kurento-media-server.service has failed
  -- Defined-By: systemd
  -- Support: https://www.debian.org/support
  --
  -- A start job for unit kurento-media-server.service has finished  
with a failure.
  --
  -- The job identifier is 2344 and the job result is failed.



Quoting Maxim Solodovnik <so...@gmail.com>:

> Any hint from `journalctl -xe` ?
>
>      On Fri, 27 Mar 2020 at 23:14, <in...@bureau-de-poste.net> wrote:
>
>> _of course - on both the /etc/init.d/kurento-media-server and  
>> /etc/default/kurento-media-server files
>>
>> Quoting Maxim Solodovnik <so...@gmail.com>:_
>>
>>> _Do you have START_DAEMON="true" ?_
>>>
>>>              _On Fri, 27 Mar 2020 at 23:05,  
>>> <in...@bureau-de-poste.net> wrote:_
>>>
>>>> __It's true that in /etc/default/kurento-media-server the user  
>>>> was set to "kurento" - changing it to "nobody" (which I HAD done  
>>>> before but probably forgot to do with update from 6.10 to 6.13  
>>>> did not help:
>>>>  __
>>>>          __● kurento-media-server.service - LSB: Kurento Media  
>>>> Server daemon__
>>>>          __   Loaded: loaded (/etc/init.d/kurento-media-server;  
>>>> generated)__
>>>>          __   Active: failed (Result: exit-code) since Fri  
>>>> 2020-03-27 17:00:24 CET; 6s ago__
>>>>          __     Docs: man:systemd-sysv-generator(8)__
>>>>          __  Process: 6939  
>>>> ExecStart=/etc/init.d/kurento-media-server start (code=exited,  
>>>> status=2)__
>>>>          __ __
>>>>          __Mar 27 17:00:24 server1.searchy.biz[1] systemd[1]:  
>>>> Starting LSB: Kurento Media Server daemon...__
>>>>          __Mar 27 17:00:24 server1.searchy.biz[1]  
>>>> kurento-media-server[6939]: Start Kurento Media Server:Configure  
>>>> Kernel resource limits for Kurento Media Serv__
>>>>          __Mar 27 17:00:24 server1.searchy.biz[1]  
>>>> kurento-media-server[6939]: /etc/init.d/kurento-media-server:  
>>>> 122: /etc/init.d/kurento-media-server: Pipe call__
>>>>          __Mar 27 17:00:24 server1.searchy.biz[1] systemd[1]:  
>>>> kurento-media-server.service: Control process exited,  
>>>> code=exited, status=2/INVALIDARGUMENT__
>>>>          __Mar 27 17:00:24 server1.searchy.biz[1] systemd[1]:  
>>>> kurento-media-server.service: Failed with result 'exit-code'.__
>>>>          __Mar 27 17:00:24 server1.searchy.biz[1] systemd[1]:  
>>>> Failed to start LSB: Kurento Media Server daemon.__
>>>>
>>>>
>>>>
>>>> __You probably don't have time to help with this now, Maxim, as  
>>>> work on getting 5.0.0 to release is more important I understand.   
>>>> If someone else has this up and running  - especially M4 (which I  
>>>> plan to move to tomorrow) on buster, please let me know if you  
>>>> can help debug om logs.
>>>>
>>>> regards,__
>>>>
>>>>          __ed
>>>>
>>>> Quoting Maxim Solodovnik <so...@gmail.com>:__
>>>>
>>>>> __/etc/default/kurento-media-server__
>>>>>            __ __
>>>>>            __START_DAEMON="true"__
>>>>>            __DAEMON_USER="nobody"    #### SAME USER AS STARTED OM__
>>>>>
>>>>>                      __On Fri, 27 Mar 2020 at 22:15,  
>>>>> <in...@bureau-de-poste.net> wrote:__
>>>>>
>>>>>> __    systemctl status kurento-media-server.status returns:
>>>>>> ● kurento-media-server.service - LSB: Kurento Media Server daemon
>>>>>>       Loaded: loaded (/etc/init.d/kurento-media-server; generated)
>>>>>>       Active: failed (Result: exit-code) since Sat 2020-03-21 22:12:26 
>>>>>> CET; 5 days ago
>>>>>>         Docs: man:systemd-sysv-generator(8)
>>>>>>      Process: 7791 ExecStart=/etc/init.d/kurento-media-server start 
>>>>>> (code=exited, status=2)
>>>>>>     
>>>>>>    Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]: Starting LSB: 
>>>>>> Kurento Media Server daemon...
>>>>>>    Mar 21 22:12:26 server1.searchy.biz[1] kurento-media-server[7791]: 
>>>>>> Start Kurento Media Server:Configure Kernel resource limits for 
>>>>>> Kurento Media Server.
>>>>>>    Mar 21 22:12:26 server1.searchy.biz[1] kurento-media-server[7791]: 
>>>>>> /etc/init.d/kurento-media-server: 122: 
>>>>>> /etc/init.d/kurento-media-server: Pipe call failed
>>>>>>    Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]: 
>>>>>> kurento-media-server.service: Control process exited, code=exited, 
>>>>>> status=2/INVALIDARGUMENT
>>>>>>    Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]: 
>>>>>> kurento-media-server.service: Failed with result 'exit-code'.
>>>>>>    Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]: Failed to start 
>>>>>> LSB: Kurento Media Server daemon.
>>>>>>  
>>>>>>
>>>>>> root@server1 ~ # aptitude show kurento-media-server
>>>>>>   Package: kurento-media-server
>>>>>>   Version: 6.13.0-0kurento1.18.04
>>>>>>   New: yes
>>>>>>   State: installed
>>>>>>   Automatically installed: no
>>>>>>   Priority: optional
>>>>>>   Section: video
>>>>>>   Maintainer: Kurento <ku...@googlegroups.com>
>>>>>>   Architecture: amd64
>>>>>>   Uncompressed Size: 2,043 k
>>>>>>   Depends: kms-core (>= 6.7.0), kms-jsonrpc, kmsjsoncpp, 
>>>>>> libboost-filesystem1.65.1, libboost-log1.65.1, 
>>>>>> libboost-program-options1.65.1,
>>>>>>            libboost-system1.65.1, libboost-thread1.65.1, libc6 (>= 
>>>>>> 2.24), libgcc1 (>= 1:3.0), libglib2.0-0 (>= 2.41.1), libglibmm-2.4-1v5 
>>>>>> (>= 2.54.0),
>>>>>>            libgstreamer1.5-0 (>= 1.8.1), libsigc++-2.0-0v5 (>= 2.8.0), 
>>>>>> libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 6), binutils, gstreamer1.5-libav,
>>>>>>            gstreamer1.5-plugins-bad, gstreamer1.5-plugins-base, 
>>>>>> gstreamer1.5-plugins-good, gstreamer1.5-plugins-ugly, kms-elements (>= 
>>>>>> 6.7.0), kms-filters
>>>>>>            (>= 6.7.0), libgstreamer-plugins-base1.5-0
>>>>>>   Suggests: kurento-dbg
>>>>>>   Breaks: kurento-media-server-6.0
>>>>>>   Replaces: kurento-media-server-6.0
>>>>>>   Description: Kurento Media Server
>>>>>>    KMS is a WebRTC-compatible server that processes audio and video 
>>>>>> streams, doing composable pipeline-based processing of media.
>>>>>>   Homepage: https://www.kurento.org
>>>>>>
>>>>>> this is the output of /opt/log/openmeetings.log:
>>>>>>     INFO 03-14 15:54:38.301 o.s.w.c.ContextLoader:271 [main] - Root 
>>>>>> WebApplicationContext: initialization started
>>>>>>     INFO 03-14 15:54:38.953 o.s.o.j.LocalEntityManagerFactoryBean:416 
>>>>>> [main] - Initialized JPA EntityManagerFactory for persistence unit 
>>>>>> 'openmeetings'
>>>>>>     INFO 03-14 15:54:39.170 o.s.s.c.ThreadPoolTaskExecutor:171 [main] 
>>>>>> - Initializing ExecutorService 'taskExecutor'
>>>>>>     INFO 03-14 15:54:40.406 o.k.j.c.JsonRpcClientNettyWebSocket:191 
>>>>>> [rbeatExec-e1-t0] - [KurentoClient]  Connecting native client
>>>>>>     INFO 03-14 15:54:40.409 o.k.j.c.JsonRpcClientNettyWebSocket:220 
>>>>>> [rbeatExec-e1-t0] - [KurentoClient]  Creating new NioEventLoopGroup
>>>>>>     INFO 03-14 15:54:40.526 o.k.j.c.JsonRpcClientNettyWebSocket:234 
>>>>>> [ntLoopGroup-2-1] - [KurentoClient]  Initiating new Netty channel. 
>>>>>> Will create new handler too!
>>>>>>     WARN 03-14 15:54:40.579 o.k.j.c.JsonRpcClientNettyWebSocket:308 
>>>>>> [rbeatExec-e1-t0] - [KurentoClient]  Trying to close a 
>>>>>> JsonRpcClientNettyWebSocket with channel == null
>>>>>>     WARN 03-14 15:54:40.581 o.k.j.c.JsonRpcClient:270 
>>>>>> [rbeatExec-e1-t0] - [KurentoClient]  Error sending heartbeat to 
>>>>>> server. Exception: [KurentoClient]  Exception connecting to WebSocket 
>>>>>> server ws://127.0.0.1:8888/kurento
>>>>>>     INFO 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:191 
>>>>>> [main] - [KurentoClient]  Connecting native client
>>>>>>     WARN 03-14 15:54:40.581 o.k.j.c.JsonRpcClient:287 
>>>>>> [rbeatExec-e1-t0] - [KurentoClient]  Stopping heartbeat and closing 
>>>>>> client: failure during heartbeat mechanism
>>>>>>     INFO 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:220 
>>>>>> [main] - [KurentoClient]  Creating new NioEventLoopGroup
>>>>>>     INFO 03-14 15:54:40.582 o.k.j.c.JsonRpcClientNettyWebSocket:234 
>>>>>> [ntLoopGroup-3-1] - [KurentoClient]  Initiating new Netty channel. 
>>>>>> Will create new handler too!
>>>>>>     WARN 03-14 15:54:40.584 o.k.j.c.JsonRpcClientNettyWebSocket:308 
>>>>>> [main] - [KurentoClient]  Trying to close a 
>>>>>> JsonRpcClientNettyWebSocket with channel == null
>>>>>>     WARN 03-14 15:54:40.585 o.a.o.c.r.KurentoHandler:124 [main] - Fail 
>>>>>> to create Kurento client, will re-try in 10000 ms
>>>>>>     INFO 03-14 15:54:40.707 o.q.i.StdSchedulerFactory:1220 [main] - 
>>>>>> Using default implementation for ThreadExecutor
>>>>>>     INFO 03-14 15:54:40.716 o.q.c.SchedulerSignalerImpl:61 [main] - 
>>>>>> Initialized Scheduler Signaller of type: class 
>>>>>> org.quartz.core.SchedulerSignalerImpl
>>>>>>     INFO 03-14 15:54:40.716 o.q.c.QuartzScheduler:229 [main] - Quartz 
>>>>>> Scheduler v.2.3.2 created.
>>>>>>     INFO 03-14 15:54:40.717 o.q.s.RAMJobStore:155 [main] - RAMJobStore 
>>>>>> initialized.
>>>>>>     INFO 03-14 15:54:40.717 o.q.c.QuartzScheduler:294 [main] - 
>>>>>> Scheduler meta-data: Quartz Scheduler (v2.3.2) 
>>>>>> 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' with 
>>>>>> instanceId 'NON_CLUSTERED'
>>>>>>      Scheduler class: 'org.quartz.core.QuartzScheduler' -  
>>>>>> running locally.
>>>>>>      NOT STARTED.
>>>>>>      Currently in standby mode.
>>>>>>      Number of jobs executed: 0
>>>>>>      Using thread pool 'org.quartz.simpl.SimpleThreadPool' -  
>>>>>> with 10 threads.
>>>>>>      Using job-store 'org.quartz.simpl.RAMJobStore' - which does not 
>>>>>> support persistence. and is not clustered.
>>>>>>
>>>>>> port 8888 is not firewalles - neither is 5443.
>>>>>>
>>>>>> Any idea what to do to start KMS on buster - tomcat3 is running fine - 
>>>>>> this is 5.0.0 M3 adn I want to install M4 very soon.
>>>>>>
>>>>>> Thanks for any ideas or help
>>>>>>
>>>>>> Ed__
>>>>>
>>>>>           __ __
>>>>> __--__
>>>>>           __WBR
>>>>> Maxim aka solomax__
>>>>
>>>>
>>>> _ _
>>>
>>>       _ _
>>> __--__
>>>       __WBR
>>> Maxim aka solomax__
>>
>>
>>  
>
>    
> _-- _
>   _WBR
> Maxim aka solomax_



Links:
------
[1] http://server1.searchy.biz

Re: unable to get KMS 6.13.0 started on debian buster 5.0.0 M3 tomcat3 running OK

Posted by Maxim Solodovnik <so...@gmail.com>.
Any hint from `journalctl -xe` ?

On Fri, 27 Mar 2020 at 23:14, <in...@bureau-de-poste.net> wrote:

> of course - on both the /etc/init.d/kurento-media-server and
> /etc/default/kurento-media-server files
>
> Quoting Maxim Solodovnik <so...@gmail.com>:
>
> Do you have START_DAEMON="true" ?
>
> On Fri, 27 Mar 2020 at 23:05, <in...@bureau-de-poste.net> wrote:
>
>>
>> *It's true that in /etc/default/kurento-media-server the user was set to
>> "kurento" - changing it to "nobody" (which I HAD done before but probably
>> forgot to do with update from 6.10 to 6.13 did not help:  *
>> *● kurento-media-server.service - LSB: Kurento Media Server daemon*
>> *   Loaded: loaded (/etc/init.d/kurento-media-server; generated)*
>> *   Active: failed (Result: exit-code) since Fri 2020-03-27 17:00:24 CET;
>> 6s ago*
>> *     Docs: man:systemd-sysv-generator(8)*
>> *  Process: 6939 ExecStart=/etc/init.d/kurento-media-server start
>> (code=exited, status=2)*
>>
>> *Mar 27 17:00:24 server1.searchy.biz <http://server1.searchy.biz>
>> systemd[1]: Starting LSB: Kurento Media Server daemon...*
>> *Mar 27 17:00:24 server1.searchy.biz <http://server1.searchy.biz>
>> kurento-media-server[6939]: Start Kurento Media Server:Configure Kernel
>> resource limits for Kurento Media Serv*
>> *Mar 27 17:00:24 server1.searchy.biz <http://server1.searchy.biz>
>> kurento-media-server[6939]: /etc/init.d/kurento-media-server: 122:
>> /etc/init.d/kurento-media-server: Pipe call*
>> *Mar 27 17:00:24 server1.searchy.biz <http://server1.searchy.biz>
>> systemd[1]: kurento-media-server.service: Control process exited,
>> code=exited, status=2/INVALIDARGUMENT*
>> *Mar 27 17:00:24 server1.searchy.biz <http://server1.searchy.biz>
>> systemd[1]: kurento-media-server.service: Failed with result 'exit-code'.*
>> *Mar 27 17:00:24 server1.searchy.biz <http://server1.searchy.biz>
>> systemd[1]: Failed to start LSB: Kurento Media Server daemon.*
>>
>>
>>
>>
>>
>> *You probably don't have time to help with this now, Maxim, as work on
>> getting 5.0.0 to release is more important I understand.  If someone else
>> has this up and running  - especially M4 (which I plan to move to tomorrow)
>> on buster, please let me know if you can help debug om logs. regards,*
>>
>>
>>
>> *ed Quoting Maxim Solodovnik <solomax666@gmail.com
>> <so...@gmail.com>>:*
>>
>> */etc/default/kurento-media-server*
>>
>> *START_DAEMON="true"*
>> *DAEMON_USER="nobody"    #### SAME USER AS STARTED OM*
>>
>> *On Fri, 27 Mar 2020 at 22:15, <info@bureau-de-poste.net
>> <in...@bureau-de-poste.net>> wrote:*
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *    systemctl status kurento-media-server.status returns: ●
>>> kurento-media-server.service - LSB: Kurento Media Server daemon
>>>  Loaded: loaded (/etc/init.d/kurento-media-server; generated)       Active:
>>> failed (Result: exit-code) since Sat 2020-03-21 22:12:26  CET; 5 days ago
>>>       Docs: man:systemd-sysv-generator(8)      Process: 7791
>>> ExecStart=/etc/init.d/kurento-media-server start  (code=exited, status=2)
>>>       Mar 21 22:12:26 server1.searchy.biz <http://server1.searchy.biz>
>>> systemd[1]: Starting LSB:  Kurento Media Server daemon...    Mar 21
>>> 22:12:26 server1.searchy.biz <http://server1.searchy.biz>
>>> kurento-media-server[7791]:  Start Kurento Media Server:Configure Kernel
>>> resource limits for  Kurento Media Server.    Mar 21 22:12:26
>>> server1.searchy.biz <http://server1.searchy.biz>
>>> kurento-media-server[7791]:  /etc/init.d/kurento-media-server: 122:
>>> /etc/init.d/kurento-media-server: Pipe call failed    Mar 21 22:12:26
>>> server1.searchy.biz <http://server1.searchy.biz> systemd[1]:
>>> kurento-media-server.service: Control process exited, code=exited,
>>> status=2/INVALIDARGUMENT    Mar 21 22:12:26 server1.searchy.biz
>>> <http://server1.searchy.biz> systemd[1]:  kurento-media-server.service:
>>> Failed with result 'exit-code'.    Mar 21 22:12:26 server1.searchy.biz
>>> <http://server1.searchy.biz> systemd[1]: Failed to start  LSB: Kurento
>>> Media Server daemon.   root@server1 ~ # aptitude show kurento-media-server
>>>   Package: kurento-media-server   Version: 6.13.0-0kurento1.18.04   New:
>>> yes   State: installed   Automatically installed: no   Priority: optional
>>> Section: video   Maintainer: Kurento <kurento@googlegroups.com
>>> <ku...@googlegroups.com>>   Architecture: amd64   Uncompressed Size:
>>> 2,043 k   Depends: kms-core (>= 6.7.0), kms-jsonrpc, kmsjsoncpp,
>>> libboost-filesystem1.65.1, libboost-log1.65.1,
>>> libboost-program-options1.65.1,            libboost-system1.65.1,
>>> libboost-thread1.65.1, libc6 (>=  2.24), libgcc1 (>= 1:3.0), libglib2.0-0
>>> (>= 2.41.1), libglibmm-2.4-1v5  (>= 2.54.0),            libgstreamer1.5-0
>>> (>= 1.8.1), libsigc++-2.0-0v5 (>= 2.8.0),  libssl1.0.0 (>= 1.0.0),
>>> libstdc++6 (>= 6), binutils, gstreamer1.5-libav,
>>>  gstreamer1.5-plugins-bad, gstreamer1.5-plugins-base,
>>> gstreamer1.5-plugins-good, gstreamer1.5-plugins-ugly, kms-elements (>=
>>> 6.7.0), kms-filters            (>= 6.7.0), libgstreamer-plugins-base1.5-0
>>> Suggests: kurento-dbg   Breaks: kurento-media-server-6.0   Replaces:
>>> kurento-media-server-6.0   Description: Kurento Media Server    KMS is a
>>> WebRTC-compatible server that processes audio and video  streams, doing
>>> composable pipeline-based processing of media.   Homepage:
>>> https://www.kurento.org <https://www.kurento.org> this is the output of
>>> /opt/log/openmeetings.log:     INFO 03-14 15:54:38.301
>>> o.s.w.c.ContextLoader:271 [main] - Root  WebApplicationContext:
>>> initialization started     INFO 03-14 15:54:38.953
>>> o.s.o.j.LocalEntityManagerFactoryBean:416  [main] - Initialized JPA
>>> EntityManagerFactory for persistence unit  'openmeetings'     INFO 03-14
>>> 15:54:39.170 o.s.s.c.ThreadPoolTaskExecutor:171 [main]  - Initializing
>>> ExecutorService 'taskExecutor'     INFO 03-14 15:54:40.406
>>> o.k.j.c.JsonRpcClientNettyWebSocket:191  [rbeatExec-e1-t0] -
>>> [KurentoClient]  Connecting native client     INFO 03-14 15:54:40.409
>>> o.k.j.c.JsonRpcClientNettyWebSocket:220  [rbeatExec-e1-t0] -
>>> [KurentoClient]  Creating new NioEventLoopGroup     INFO 03-14 15:54:40.526
>>> o.k.j.c.JsonRpcClientNettyWebSocket:234  [ntLoopGroup-2-1] -
>>> [KurentoClient]  Initiating new Netty channel.  Will create new handler
>>> too!     WARN 03-14 15:54:40.579 o.k.j.c.JsonRpcClientNettyWebSocket:308
>>> [rbeatExec-e1-t0] - [KurentoClient]  Trying to close a
>>> JsonRpcClientNettyWebSocket with channel == null     WARN 03-14
>>> 15:54:40.581 o.k.j.c.JsonRpcClient:270  [rbeatExec-e1-t0] -
>>> [KurentoClient]  Error sending heartbeat to  server. Exception:
>>> [KurentoClient]  Exception connecting to WebSocket  server
>>> ws://127.0.0.1:8888/kurento <http://127.0.0.1:8888/kurento>     INFO 03-14
>>> 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:191  [main] -
>>> [KurentoClient]  Connecting native client     WARN 03-14 15:54:40.581
>>> o.k.j.c.JsonRpcClient:287  [rbeatExec-e1-t0] - [KurentoClient]  Stopping
>>> heartbeat and closing  client: failure during heartbeat mechanism     INFO
>>> 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:220  [main] -
>>> [KurentoClient]  Creating new NioEventLoopGroup     INFO 03-14 15:54:40.582
>>> o.k.j.c.JsonRpcClientNettyWebSocket:234  [ntLoopGroup-3-1] -
>>> [KurentoClient]  Initiating new Netty channel.  Will create new handler
>>> too!     WARN 03-14 15:54:40.584 o.k.j.c.JsonRpcClientNettyWebSocket:308
>>> [main] - [KurentoClient]  Trying to close a  JsonRpcClientNettyWebSocket
>>> with channel == null     WARN 03-14 15:54:40.585
>>> o.a.o.c.r.KurentoHandler:124 [main] - Fail  to create Kurento client, will
>>> re-try in 10000 ms     INFO 03-14 15:54:40.707
>>> o.q.i.StdSchedulerFactory:1220 [main] -  Using default implementation for
>>> ThreadExecutor     INFO 03-14 15:54:40.716 o.q.c.SchedulerSignalerImpl:61
>>> [main] -  Initialized Scheduler Signaller of type: class
>>> org.quartz.core.SchedulerSignalerImpl     INFO 03-14 15:54:40.716
>>> o.q.c.QuartzScheduler:229 [main] - Quartz  Scheduler v.2.3.2 created.
>>>   INFO 03-14 15:54:40.717 o.q.s.RAMJobStore:155 [main] - RAMJobStore
>>> initialized.     INFO 03-14 15:54:40.717 o.q.c.QuartzScheduler:294 [main]
>>> -  Scheduler meta-data: Quartz Scheduler (v2.3.2)
>>> 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' with
>>> instanceId 'NON_CLUSTERED'      Scheduler class:
>>> 'org.quartz.core.QuartzScheduler' - running locally.      NOT STARTED.
>>> Currently in standby mode.      Number of jobs executed: 0      Using
>>> thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
>>> Using job-store 'org.quartz.simpl.RAMJobStore' - which does not  support
>>> persistence. and is not clustered. port 8888 is not firewalles - neither is
>>> 5443. Any idea what to do to start KMS on buster - tomcat3 is running fine
>>> -  this is 5.0.0 M3 adn I want to install M4 very soon. Thanks for any
>>> ideas or help Ed*
>>>
>>
>>
>> *--*
>>
>> *WBR Maxim aka solomax*
>>
>>
>>
>>
>
>
> *--*
>
> *WBR Maxim aka solomax*
>
>
>
>

-- 
WBR
Maxim aka solomax

Re: unable to get KMS 6.13.0 started on debian buster 5.0.0 M3 tomcat3 running OK

Posted by in...@bureau-de-poste.net.
  of course - on both the /etc/init.d/kurento-media-server and  
/etc/default/kurento-media-server files

Quoting Maxim Solodovnik <so...@gmail.com>:

> Do you have START_DAEMON="true" ?
>
>      On Fri, 27 Mar 2020 at 23:05, <in...@bureau-de-poste.net> wrote:
>
>> _It's true that in /etc/default/kurento-media-server the user was  
>> set to "kurento" - changing it to "nobody" (which I HAD done before  
>> but probably forgot to do with update from 6.10 to 6.13 did not help:
>>  _
>>      _● kurento-media-server.service - LSB: Kurento Media Server daemon_
>>      _   Loaded: loaded (/etc/init.d/kurento-media-server; generated)_
>>      _   Active: failed (Result: exit-code) since Fri 2020-03-27  
>> 17:00:24 CET; 6s ago_
>>      _     Docs: man:systemd-sysv-generator(8)_
>>      _  Process: 6939 ExecStart=/etc/init.d/kurento-media-server  
>> start (code=exited, status=2)_
>>      _ _
>>      _Mar 27 17:00:24 server1.searchy.biz[1] systemd[1]: Starting  
>> LSB: Kurento Media Server daemon..._
>>      _Mar 27 17:00:24 server1.searchy.biz[1]  
>> kurento-media-server[6939]: Start Kurento Media Server:Configure  
>> Kernel resource limits for Kurento Media Serv_
>>      _Mar 27 17:00:24 server1.searchy.biz[1]  
>> kurento-media-server[6939]: /etc/init.d/kurento-media-server: 122:  
>> /etc/init.d/kurento-media-server: Pipe call_
>>      _Mar 27 17:00:24 server1.searchy.biz[1] systemd[1]:  
>> kurento-media-server.service: Control process exited, code=exited,  
>> status=2/INVALIDARGUMENT_
>>      _Mar 27 17:00:24 server1.searchy.biz[1] systemd[1]:  
>> kurento-media-server.service: Failed with result 'exit-code'._
>>      _Mar 27 17:00:24 server1.searchy.biz[1] systemd[1]: Failed to  
>> start LSB: Kurento Media Server daemon._
>>
>>
>>
>> _You probably don't have time to help with this now, Maxim, as work  
>> on getting 5.0.0 to release is more important I understand.  If  
>> someone else has this up and running  - especially M4 (which I plan  
>> to move to tomorrow) on buster, please let me know if you can help  
>> debug om logs.
>>
>> regards,_
>>
>>      _ed
>>
>> Quoting Maxim Solodovnik <so...@gmail.com>:_
>>
>>> _/etc/default/kurento-media-server_
>>>        _ _
>>>        _START_DAEMON="true"_
>>>        _DAEMON_USER="nobody"    #### SAME USER AS STARTED OM_
>>>
>>>              _On Fri, 27 Mar 2020 at 22:15,  
>>> <in...@bureau-de-poste.net> wrote:_
>>>
>>>> _    systemctl status kurento-media-server.status returns:
>>>> ● kurento-media-server.service - LSB: Kurento Media Server daemon
>>>>       Loaded: loaded (/etc/init.d/kurento-media-server; generated)
>>>>       Active: failed (Result: exit-code) since Sat 2020-03-21 22:12:26 
>>>> CET; 5 days ago
>>>>         Docs: man:systemd-sysv-generator(8)
>>>>      Process: 7791 ExecStart=/etc/init.d/kurento-media-server start 
>>>> (code=exited, status=2)
>>>>     
>>>>    Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]: Starting LSB: 
>>>> Kurento Media Server daemon...
>>>>    Mar 21 22:12:26 server1.searchy.biz[1] kurento-media-server[7791]: 
>>>> Start Kurento Media Server:Configure Kernel resource limits for 
>>>> Kurento Media Server.
>>>>    Mar 21 22:12:26 server1.searchy.biz[1] kurento-media-server[7791]: 
>>>> /etc/init.d/kurento-media-server: 122: 
>>>> /etc/init.d/kurento-media-server: Pipe call failed
>>>>    Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]: 
>>>> kurento-media-server.service: Control process exited, code=exited, 
>>>> status=2/INVALIDARGUMENT
>>>>    Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]: 
>>>> kurento-media-server.service: Failed with result 'exit-code'.
>>>>    Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]: Failed to start 
>>>> LSB: Kurento Media Server daemon.
>>>>  
>>>>
>>>> root@server1 ~ # aptitude show kurento-media-server
>>>>   Package: kurento-media-server
>>>>   Version: 6.13.0-0kurento1.18.04
>>>>   New: yes
>>>>   State: installed
>>>>   Automatically installed: no
>>>>   Priority: optional
>>>>   Section: video
>>>>   Maintainer: Kurento <ku...@googlegroups.com>
>>>>   Architecture: amd64
>>>>   Uncompressed Size: 2,043 k
>>>>   Depends: kms-core (>= 6.7.0), kms-jsonrpc, kmsjsoncpp, 
>>>> libboost-filesystem1.65.1, libboost-log1.65.1, 
>>>> libboost-program-options1.65.1,
>>>>            libboost-system1.65.1, libboost-thread1.65.1, libc6 (>= 
>>>> 2.24), libgcc1 (>= 1:3.0), libglib2.0-0 (>= 2.41.1), libglibmm-2.4-1v5 
>>>> (>= 2.54.0),
>>>>            libgstreamer1.5-0 (>= 1.8.1), libsigc++-2.0-0v5 (>= 2.8.0), 
>>>> libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 6), binutils, gstreamer1.5-libav,
>>>>            gstreamer1.5-plugins-bad, gstreamer1.5-plugins-base, 
>>>> gstreamer1.5-plugins-good, gstreamer1.5-plugins-ugly, kms-elements (>= 
>>>> 6.7.0), kms-filters
>>>>            (>= 6.7.0), libgstreamer-plugins-base1.5-0
>>>>   Suggests: kurento-dbg
>>>>   Breaks: kurento-media-server-6.0
>>>>   Replaces: kurento-media-server-6.0
>>>>   Description: Kurento Media Server
>>>>    KMS is a WebRTC-compatible server that processes audio and video 
>>>> streams, doing composable pipeline-based processing of media.
>>>>   Homepage: https://www.kurento.org
>>>>
>>>> this is the output of /opt/log/openmeetings.log:
>>>>     INFO 03-14 15:54:38.301 o.s.w.c.ContextLoader:271 [main] - Root 
>>>> WebApplicationContext: initialization started
>>>>     INFO 03-14 15:54:38.953 o.s.o.j.LocalEntityManagerFactoryBean:416 
>>>> [main] - Initialized JPA EntityManagerFactory for persistence unit 
>>>> 'openmeetings'
>>>>     INFO 03-14 15:54:39.170 o.s.s.c.ThreadPoolTaskExecutor:171 [main] 
>>>> - Initializing ExecutorService 'taskExecutor'
>>>>     INFO 03-14 15:54:40.406 o.k.j.c.JsonRpcClientNettyWebSocket:191 
>>>> [rbeatExec-e1-t0] - [KurentoClient]  Connecting native client
>>>>     INFO 03-14 15:54:40.409 o.k.j.c.JsonRpcClientNettyWebSocket:220 
>>>> [rbeatExec-e1-t0] - [KurentoClient]  Creating new NioEventLoopGroup
>>>>     INFO 03-14 15:54:40.526 o.k.j.c.JsonRpcClientNettyWebSocket:234 
>>>> [ntLoopGroup-2-1] - [KurentoClient]  Initiating new Netty channel. 
>>>> Will create new handler too!
>>>>     WARN 03-14 15:54:40.579 o.k.j.c.JsonRpcClientNettyWebSocket:308 
>>>> [rbeatExec-e1-t0] - [KurentoClient]  Trying to close a 
>>>> JsonRpcClientNettyWebSocket with channel == null
>>>>     WARN 03-14 15:54:40.581 o.k.j.c.JsonRpcClient:270 
>>>> [rbeatExec-e1-t0] - [KurentoClient]  Error sending heartbeat to 
>>>> server. Exception: [KurentoClient]  Exception connecting to WebSocket 
>>>> server ws://127.0.0.1:8888/kurento
>>>>     INFO 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:191 
>>>> [main] - [KurentoClient]  Connecting native client
>>>>     WARN 03-14 15:54:40.581 o.k.j.c.JsonRpcClient:287 
>>>> [rbeatExec-e1-t0] - [KurentoClient]  Stopping heartbeat and closing 
>>>> client: failure during heartbeat mechanism
>>>>     INFO 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:220 
>>>> [main] - [KurentoClient]  Creating new NioEventLoopGroup
>>>>     INFO 03-14 15:54:40.582 o.k.j.c.JsonRpcClientNettyWebSocket:234 
>>>> [ntLoopGroup-3-1] - [KurentoClient]  Initiating new Netty channel. 
>>>> Will create new handler too!
>>>>     WARN 03-14 15:54:40.584 o.k.j.c.JsonRpcClientNettyWebSocket:308 
>>>> [main] - [KurentoClient]  Trying to close a 
>>>> JsonRpcClientNettyWebSocket with channel == null
>>>>     WARN 03-14 15:54:40.585 o.a.o.c.r.KurentoHandler:124 [main] - Fail 
>>>> to create Kurento client, will re-try in 10000 ms
>>>>     INFO 03-14 15:54:40.707 o.q.i.StdSchedulerFactory:1220 [main] - 
>>>> Using default implementation for ThreadExecutor
>>>>     INFO 03-14 15:54:40.716 o.q.c.SchedulerSignalerImpl:61 [main] - 
>>>> Initialized Scheduler Signaller of type: class 
>>>> org.quartz.core.SchedulerSignalerImpl
>>>>     INFO 03-14 15:54:40.716 o.q.c.QuartzScheduler:229 [main] - Quartz 
>>>> Scheduler v.2.3.2 created.
>>>>     INFO 03-14 15:54:40.717 o.q.s.RAMJobStore:155 [main] - RAMJobStore 
>>>> initialized.
>>>>     INFO 03-14 15:54:40.717 o.q.c.QuartzScheduler:294 [main] - 
>>>> Scheduler meta-data: Quartz Scheduler (v2.3.2) 
>>>> 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' with 
>>>> instanceId 'NON_CLUSTERED'
>>>>      Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
>>>>      NOT STARTED.
>>>>      Currently in standby mode.
>>>>      Number of jobs executed: 0
>>>>      Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with  
>>>> 10 threads.
>>>>      Using job-store 'org.quartz.simpl.RAMJobStore' - which does not 
>>>> support persistence. and is not clustered.
>>>>
>>>> port 8888 is not firewalles - neither is 5443.
>>>>
>>>> Any idea what to do to start KMS on buster - tomcat3 is running fine - 
>>>> this is 5.0.0 M3 adn I want to install M4 very soon.
>>>>
>>>> Thanks for any ideas or help
>>>>
>>>> Ed_
>>>
>>>       _ _
>>> _--_
>>>       _WBR
>>> Maxim aka solomax_
>>
>>
>>  
>
>    
> _-- _
>   _WBR
> Maxim aka solomax_



Links:
------
[1] http://server1.searchy.biz

Re: unable to get KMS 6.13.0 started on debian buster 5.0.0 M3 tomcat3 running OK

Posted by Maxim Solodovnik <so...@gmail.com>.
Do you have START_DAEMON="true" ?

On Fri, 27 Mar 2020 at 23:05, <in...@bureau-de-poste.net> wrote:

> It's true that in /etc/default/kurento-media-server the user was set to
> "kurento" - changing it to "nobody" (which I HAD done before but probably
> forgot to do with update from 6.10 to 6.13 did not help:
>
> ● kurento-media-server.service - LSB: Kurento Media Server daemon
>    Loaded: loaded (/etc/init.d/kurento-media-server; generated)
>    Active: failed (Result: exit-code) since Fri 2020-03-27 17:00:24 CET;
> 6s ago
>      Docs: man:systemd-sysv-generator(8)
>   Process: 6939 ExecStart=/etc/init.d/kurento-media-server start
> (code=exited, status=2)
>
> Mar 27 17:00:24 server1.searchy.biz systemd[1]: Starting LSB: Kurento
> Media Server daemon...
> Mar 27 17:00:24 server1.searchy.biz kurento-media-server[6939]: Start
> Kurento Media Server:Configure Kernel resource limits for Kurento Media Serv
> Mar 27 17:00:24 server1.searchy.biz kurento-media-server[6939]:
> /etc/init.d/kurento-media-server: 122: /etc/init.d/kurento-media-server:
> Pipe call
> Mar 27 17:00:24 server1.searchy.biz systemd[1]:
> kurento-media-server.service: Control process exited, code=exited,
> status=2/INVALIDARGUMENT
> Mar 27 17:00:24 server1.searchy.biz systemd[1]:
> kurento-media-server.service: Failed with result 'exit-code'.
> Mar 27 17:00:24 server1.searchy.biz systemd[1]: Failed to start LSB:
> Kurento Media Server daemon.
>
>
>
> You probably don't have time to help with this now, Maxim, as work on
> getting 5.0.0 to release is more important I understand.  If someone else
> has this up and running  - especially M4 (which I plan to move to tomorrow)
> on buster, please let me know if you can help debug om logs.
>
> regards,
>
> ed
>
> Quoting Maxim Solodovnik <so...@gmail.com>:
>
> /etc/default/kurento-media-server
>
> START_DAEMON="true"
> DAEMON_USER="nobody"    #### SAME USER AS STARTED OM
>
> On Fri, 27 Mar 2020 at 22:15, <in...@bureau-de-poste.net> wrote:
>
>>     systemctl status kurento-media-server.status returns:
>> ● kurento-media-server.service - LSB: Kurento Media Server daemon
>>       Loaded: loaded (/etc/init.d/kurento-media-server; generated)
>>       Active: failed (Result: exit-code) since Sat 2020-03-21 22:12:26
>> CET; 5 days ago
>>         Docs: man:systemd-sysv-generator(8)
>>      Process: 7791 ExecStart=/etc/init.d/kurento-media-server start
>> (code=exited, status=2)
>>
>>    Mar 21 22:12:26 server1.searchy.biz systemd[1]: Starting LSB:
>> Kurento Media Server daemon...
>>    Mar 21 22:12:26 server1.searchy.biz kurento-media-server[7791]:
>> Start Kurento Media Server:Configure Kernel resource limits for
>> Kurento Media Server.
>>    Mar 21 22:12:26 server1.searchy.biz kurento-media-server[7791]:
>> /etc/init.d/kurento-media-server: 122:
>> /etc/init.d/kurento-media-server: Pipe call failed
>>    Mar 21 22:12:26 server1.searchy.biz systemd[1]:
>> kurento-media-server.service: Control process exited, code=exited,
>> status=2/INVALIDARGUMENT
>>    Mar 21 22:12:26 server1.searchy.biz systemd[1]:
>> kurento-media-server.service: Failed with result 'exit-code'.
>>    Mar 21 22:12:26 server1.searchy.biz systemd[1]: Failed to start
>> LSB: Kurento Media Server daemon.
>>
>>
>> root@server1 ~ # aptitude show kurento-media-server
>>   Package: kurento-media-server
>>   Version: 6.13.0-0kurento1.18.04
>>   New: yes
>>   State: installed
>>   Automatically installed: no
>>   Priority: optional
>>   Section: video
>>   Maintainer: Kurento <ku...@googlegroups.com>
>>   Architecture: amd64
>>   Uncompressed Size: 2,043 k
>>   Depends: kms-core (>= 6.7.0), kms-jsonrpc, kmsjsoncpp,
>> libboost-filesystem1.65.1, libboost-log1.65.1,
>> libboost-program-options1.65.1,
>>            libboost-system1.65.1, libboost-thread1.65.1, libc6 (>=
>> 2.24), libgcc1 (>= 1:3.0), libglib2.0-0 (>= 2.41.1), libglibmm-2.4-1v5
>> (>= 2.54.0),
>>            libgstreamer1.5-0 (>= 1.8.1), libsigc++-2.0-0v5 (>= 2.8.0),
>> libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 6), binutils, gstreamer1.5-libav,
>>            gstreamer1.5-plugins-bad, gstreamer1.5-plugins-base,
>> gstreamer1.5-plugins-good, gstreamer1.5-plugins-ugly, kms-elements (>=
>> 6.7.0), kms-filters
>>            (>= 6.7.0), libgstreamer-plugins-base1.5-0
>>   Suggests: kurento-dbg
>>   Breaks: kurento-media-server-6.0
>>   Replaces: kurento-media-server-6.0
>>   Description: Kurento Media Server
>>    KMS is a WebRTC-compatible server that processes audio and video
>> streams, doing composable pipeline-based processing of media.
>>   Homepage: https://www.kurento.org
>>
>> this is the output of /opt/log/openmeetings.log:
>>     INFO 03-14 15:54:38.301 o.s.w.c.ContextLoader:271 [main] - Root
>> WebApplicationContext: initialization started
>>     INFO 03-14 15:54:38.953 o.s.o.j.LocalEntityManagerFactoryBean:416
>> [main] - Initialized JPA EntityManagerFactory for persistence unit
>> 'openmeetings'
>>     INFO 03-14 15:54:39.170 o.s.s.c.ThreadPoolTaskExecutor:171 [main]
>> - Initializing ExecutorService 'taskExecutor'
>>     INFO 03-14 15:54:40.406 o.k.j.c.JsonRpcClientNettyWebSocket:191
>> [rbeatExec-e1-t0] - [KurentoClient]  Connecting native client
>>     INFO 03-14 15:54:40.409 o.k.j.c.JsonRpcClientNettyWebSocket:220
>> [rbeatExec-e1-t0] - [KurentoClient]  Creating new NioEventLoopGroup
>>     INFO 03-14 15:54:40.526 o.k.j.c.JsonRpcClientNettyWebSocket:234
>> [ntLoopGroup-2-1] - [KurentoClient]  Initiating new Netty channel.
>> Will create new handler too!
>>     WARN 03-14 15:54:40.579 o.k.j.c.JsonRpcClientNettyWebSocket:308
>> [rbeatExec-e1-t0] - [KurentoClient]  Trying to close a
>> JsonRpcClientNettyWebSocket with channel == null
>>     WARN 03-14 15:54:40.581 o.k.j.c.JsonRpcClient:270
>> [rbeatExec-e1-t0] - [KurentoClient]  Error sending heartbeat to
>> server. Exception: [KurentoClient]  Exception connecting to WebSocket
>> server ws://127.0.0.1:8888/kurento
>>     INFO 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:191
>> [main] - [KurentoClient]  Connecting native client
>>     WARN 03-14 15:54:40.581 o.k.j.c.JsonRpcClient:287
>> [rbeatExec-e1-t0] - [KurentoClient]  Stopping heartbeat and closing
>> client: failure during heartbeat mechanism
>>     INFO 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:220
>> [main] - [KurentoClient]  Creating new NioEventLoopGroup
>>     INFO 03-14 15:54:40.582 o.k.j.c.JsonRpcClientNettyWebSocket:234
>> [ntLoopGroup-3-1] - [KurentoClient]  Initiating new Netty channel.
>> Will create new handler too!
>>     WARN 03-14 15:54:40.584 o.k.j.c.JsonRpcClientNettyWebSocket:308
>> [main] - [KurentoClient]  Trying to close a
>> JsonRpcClientNettyWebSocket with channel == null
>>     WARN 03-14 15:54:40.585 o.a.o.c.r.KurentoHandler:124 [main] - Fail
>> to create Kurento client, will re-try in 10000 ms
>>     INFO 03-14 15:54:40.707 o.q.i.StdSchedulerFactory:1220 [main] -
>> Using default implementation for ThreadExecutor
>>     INFO 03-14 15:54:40.716 o.q.c.SchedulerSignalerImpl:61 [main] -
>> Initialized Scheduler Signaller of type: class
>> org.quartz.core.SchedulerSignalerImpl
>>     INFO 03-14 15:54:40.716 o.q.c.QuartzScheduler:229 [main] - Quartz
>> Scheduler v.2.3.2 created.
>>     INFO 03-14 15:54:40.717 o.q.s.RAMJobStore:155 [main] - RAMJobStore
>> initialized.
>>     INFO 03-14 15:54:40.717 o.q.c.QuartzScheduler:294 [main] -
>> Scheduler meta-data: Quartz Scheduler (v2.3.2)
>> 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' with
>> instanceId 'NON_CLUSTERED'
>>      Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
>>      NOT STARTED.
>>      Currently in standby mode.
>>      Number of jobs executed: 0
>>      Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10
>> threads.
>>      Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
>> support persistence. and is not clustered.
>>
>> port 8888 is not firewalles - neither is 5443.
>>
>> Any idea what to do to start KMS on buster - tomcat3 is running fine -
>> this is 5.0.0 M3 adn I want to install M4 very soon.
>>
>> Thanks for any ideas or help
>>
>> Ed
>>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
>

-- 
WBR
Maxim aka solomax

Re: unable to get KMS 6.13.0 started on debian buster 5.0.0 M3 tomcat3 running OK

Posted by in...@bureau-de-poste.net.
  It's true that in /etc/default/kurento-media-server the user was set  
to "kurento" - changing it to "nobody" (which I HAD done before but  
probably forgot to do with update from 6.10 to 6.13 did not help:
 
  ● kurento-media-server.service - LSB: Kurento Media Server daemon
     Loaded: loaded (/etc/init.d/kurento-media-server; generated)
     Active: failed (Result: exit-code) since Fri 2020-03-27 17:00:24  
CET; 6s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 6939 ExecStart=/etc/init.d/kurento-media-server start  
(code=exited, status=2)
   
  Mar 27 17:00:24 server1.searchy.biz systemd[1]: Starting LSB:  
Kurento Media Server daemon...
  Mar 27 17:00:24 server1.searchy.biz kurento-media-server[6939]:  
Start Kurento Media Server:Configure Kernel resource limits for  
Kurento Media Serv
  Mar 27 17:00:24 server1.searchy.biz kurento-media-server[6939]:  
/etc/init.d/kurento-media-server: 122:  
/etc/init.d/kurento-media-server: Pipe call
  Mar 27 17:00:24 server1.searchy.biz systemd[1]:  
kurento-media-server.service: Control process exited, code=exited,  
status=2/INVALIDARGUMENT
  Mar 27 17:00:24 server1.searchy.biz systemd[1]:  
kurento-media-server.service: Failed with result 'exit-code'.
  Mar 27 17:00:24 server1.searchy.biz systemd[1]: Failed to start LSB:  
Kurento Media Server daemon.



You probably don't have time to help with this now, Maxim, as work on  
getting 5.0.0 to release is more important I understand.  If someone  
else has this up and running  - especially M4 (which I plan to move to  
tomorrow) on buster, please let me know if you can help debug om logs.

regards,

  ed

Quoting Maxim Solodovnik <so...@gmail.com>:

> /etc/default/kurento-media-server
>     
>    START_DAEMON="true"
>    DAEMON_USER="nobody"    #### SAME USER AS STARTED OM
>
>      On Fri, 27 Mar 2020 at 22:15, <in...@bureau-de-poste.net> wrote:
>
>>     systemctl status kurento-media-server.status returns:
>> ● kurento-media-server.service - LSB: Kurento Media Server daemon
>>       Loaded: loaded (/etc/init.d/kurento-media-server; generated)
>>       Active: failed (Result: exit-code) since Sat 2020-03-21 22:12:26 
>> CET; 5 days ago
>>         Docs: man:systemd-sysv-generator(8)
>>      Process: 7791 ExecStart=/etc/init.d/kurento-media-server start 
>> (code=exited, status=2)
>>     
>>    Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]: Starting LSB: 
>> Kurento Media Server daemon...
>>    Mar 21 22:12:26 server1.searchy.biz[1] kurento-media-server[7791]: 
>> Start Kurento Media Server:Configure Kernel resource limits for 
>> Kurento Media Server.
>>    Mar 21 22:12:26 server1.searchy.biz[1] kurento-media-server[7791]: 
>> /etc/init.d/kurento-media-server: 122: 
>> /etc/init.d/kurento-media-server: Pipe call failed
>>    Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]: 
>> kurento-media-server.service: Control process exited, code=exited, 
>> status=2/INVALIDARGUMENT
>>    Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]: 
>> kurento-media-server.service: Failed with result 'exit-code'.
>>    Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]: Failed to start 
>> LSB: Kurento Media Server daemon.
>>  
>>
>> root@server1 ~ # aptitude show kurento-media-server
>>   Package: kurento-media-server
>>   Version: 6.13.0-0kurento1.18.04
>>   New: yes
>>   State: installed
>>   Automatically installed: no
>>   Priority: optional
>>   Section: video
>>   Maintainer: Kurento <ku...@googlegroups.com>
>>   Architecture: amd64
>>   Uncompressed Size: 2,043 k
>>   Depends: kms-core (>= 6.7.0), kms-jsonrpc, kmsjsoncpp, 
>> libboost-filesystem1.65.1, libboost-log1.65.1, 
>> libboost-program-options1.65.1,
>>            libboost-system1.65.1, libboost-thread1.65.1, libc6 (>= 
>> 2.24), libgcc1 (>= 1:3.0), libglib2.0-0 (>= 2.41.1), libglibmm-2.4-1v5 
>> (>= 2.54.0),
>>            libgstreamer1.5-0 (>= 1.8.1), libsigc++-2.0-0v5 (>= 2.8.0), 
>> libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 6), binutils, gstreamer1.5-libav,
>>            gstreamer1.5-plugins-bad, gstreamer1.5-plugins-base, 
>> gstreamer1.5-plugins-good, gstreamer1.5-plugins-ugly, kms-elements (>= 
>> 6.7.0), kms-filters
>>            (>= 6.7.0), libgstreamer-plugins-base1.5-0
>>   Suggests: kurento-dbg
>>   Breaks: kurento-media-server-6.0
>>   Replaces: kurento-media-server-6.0
>>   Description: Kurento Media Server
>>    KMS is a WebRTC-compatible server that processes audio and video 
>> streams, doing composable pipeline-based processing of media.
>>   Homepage: https://www.kurento.org
>>
>> this is the output of /opt/log/openmeetings.log:
>>     INFO 03-14 15:54:38.301 o.s.w.c.ContextLoader:271 [main] - Root 
>> WebApplicationContext: initialization started
>>     INFO 03-14 15:54:38.953 o.s.o.j.LocalEntityManagerFactoryBean:416 
>> [main] - Initialized JPA EntityManagerFactory for persistence unit 
>> 'openmeetings'
>>     INFO 03-14 15:54:39.170 o.s.s.c.ThreadPoolTaskExecutor:171 [main] 
>> - Initializing ExecutorService 'taskExecutor'
>>     INFO 03-14 15:54:40.406 o.k.j.c.JsonRpcClientNettyWebSocket:191 
>> [rbeatExec-e1-t0] - [KurentoClient]  Connecting native client
>>     INFO 03-14 15:54:40.409 o.k.j.c.JsonRpcClientNettyWebSocket:220 
>> [rbeatExec-e1-t0] - [KurentoClient]  Creating new NioEventLoopGroup
>>     INFO 03-14 15:54:40.526 o.k.j.c.JsonRpcClientNettyWebSocket:234 
>> [ntLoopGroup-2-1] - [KurentoClient]  Initiating new Netty channel. 
>> Will create new handler too!
>>     WARN 03-14 15:54:40.579 o.k.j.c.JsonRpcClientNettyWebSocket:308 
>> [rbeatExec-e1-t0] - [KurentoClient]  Trying to close a 
>> JsonRpcClientNettyWebSocket with channel == null
>>     WARN 03-14 15:54:40.581 o.k.j.c.JsonRpcClient:270 
>> [rbeatExec-e1-t0] - [KurentoClient]  Error sending heartbeat to 
>> server. Exception: [KurentoClient]  Exception connecting to WebSocket 
>> server ws://127.0.0.1:8888/kurento
>>     INFO 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:191 
>> [main] - [KurentoClient]  Connecting native client
>>     WARN 03-14 15:54:40.581 o.k.j.c.JsonRpcClient:287 
>> [rbeatExec-e1-t0] - [KurentoClient]  Stopping heartbeat and closing 
>> client: failure during heartbeat mechanism
>>     INFO 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:220 
>> [main] - [KurentoClient]  Creating new NioEventLoopGroup
>>     INFO 03-14 15:54:40.582 o.k.j.c.JsonRpcClientNettyWebSocket:234 
>> [ntLoopGroup-3-1] - [KurentoClient]  Initiating new Netty channel. 
>> Will create new handler too!
>>     WARN 03-14 15:54:40.584 o.k.j.c.JsonRpcClientNettyWebSocket:308 
>> [main] - [KurentoClient]  Trying to close a 
>> JsonRpcClientNettyWebSocket with channel == null
>>     WARN 03-14 15:54:40.585 o.a.o.c.r.KurentoHandler:124 [main] - Fail 
>> to create Kurento client, will re-try in 10000 ms
>>     INFO 03-14 15:54:40.707 o.q.i.StdSchedulerFactory:1220 [main] - 
>> Using default implementation for ThreadExecutor
>>     INFO 03-14 15:54:40.716 o.q.c.SchedulerSignalerImpl:61 [main] - 
>> Initialized Scheduler Signaller of type: class 
>> org.quartz.core.SchedulerSignalerImpl
>>     INFO 03-14 15:54:40.716 o.q.c.QuartzScheduler:229 [main] - Quartz 
>> Scheduler v.2.3.2 created.
>>     INFO 03-14 15:54:40.717 o.q.s.RAMJobStore:155 [main] - RAMJobStore 
>> initialized.
>>     INFO 03-14 15:54:40.717 o.q.c.QuartzScheduler:294 [main] - 
>> Scheduler meta-data: Quartz Scheduler (v2.3.2) 
>> 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' with 
>> instanceId 'NON_CLUSTERED'
>>      Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
>>      NOT STARTED.
>>      Currently in standby mode.
>>      Number of jobs executed: 0
>>      Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with  
>> 10 threads.
>>      Using job-store 'org.quartz.simpl.RAMJobStore' - which does not 
>> support persistence. and is not clustered.
>>
>> port 8888 is not firewalles - neither is 5443.
>>
>> Any idea what to do to start KMS on buster - tomcat3 is running fine - 
>> this is 5.0.0 M3 adn I want to install M4 very soon.
>>
>> Thanks for any ideas or help
>>
>> Ed
>
>    
> --
>   WBR
> Maxim aka solomax



Links:
------
[1] http://server1.searchy.biz

Re: unable to get KMS 6.13.0 started on debian buster 5.0.0 M3 tomcat3 running OK

Posted by Maxim Solodovnik <so...@gmail.com>.
/etc/default/kurento-media-server

START_DAEMON="true"
DAEMON_USER="nobody"    #### SAME USER AS STARTED OM

On Fri, 27 Mar 2020 at 22:15, <in...@bureau-de-poste.net> wrote:

>     systemctl status kurento-media-server.status returns:
> ● kurento-media-server.service - LSB: Kurento Media Server daemon
>       Loaded: loaded (/etc/init.d/kurento-media-server; generated)
>       Active: failed (Result: exit-code) since Sat 2020-03-21 22:12:26
> CET; 5 days ago
>         Docs: man:systemd-sysv-generator(8)
>      Process: 7791 ExecStart=/etc/init.d/kurento-media-server start
> (code=exited, status=2)
>
>    Mar 21 22:12:26 server1.searchy.biz systemd[1]: Starting LSB:
> Kurento Media Server daemon...
>    Mar 21 22:12:26 server1.searchy.biz kurento-media-server[7791]:
> Start Kurento Media Server:Configure Kernel resource limits for
> Kurento Media Server.
>    Mar 21 22:12:26 server1.searchy.biz kurento-media-server[7791]:
> /etc/init.d/kurento-media-server: 122:
> /etc/init.d/kurento-media-server: Pipe call failed
>    Mar 21 22:12:26 server1.searchy.biz systemd[1]:
> kurento-media-server.service: Control process exited, code=exited,
> status=2/INVALIDARGUMENT
>    Mar 21 22:12:26 server1.searchy.biz systemd[1]:
> kurento-media-server.service: Failed with result 'exit-code'.
>    Mar 21 22:12:26 server1.searchy.biz systemd[1]: Failed to start
> LSB: Kurento Media Server daemon.
>
>
> root@server1 ~ # aptitude show kurento-media-server
>   Package: kurento-media-server
>   Version: 6.13.0-0kurento1.18.04
>   New: yes
>   State: installed
>   Automatically installed: no
>   Priority: optional
>   Section: video
>   Maintainer: Kurento <ku...@googlegroups.com>
>   Architecture: amd64
>   Uncompressed Size: 2,043 k
>   Depends: kms-core (>= 6.7.0), kms-jsonrpc, kmsjsoncpp,
> libboost-filesystem1.65.1, libboost-log1.65.1,
> libboost-program-options1.65.1,
>            libboost-system1.65.1, libboost-thread1.65.1, libc6 (>=
> 2.24), libgcc1 (>= 1:3.0), libglib2.0-0 (>= 2.41.1), libglibmm-2.4-1v5
> (>= 2.54.0),
>            libgstreamer1.5-0 (>= 1.8.1), libsigc++-2.0-0v5 (>= 2.8.0),
> libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 6), binutils, gstreamer1.5-libav,
>            gstreamer1.5-plugins-bad, gstreamer1.5-plugins-base,
> gstreamer1.5-plugins-good, gstreamer1.5-plugins-ugly, kms-elements (>=
> 6.7.0), kms-filters
>            (>= 6.7.0), libgstreamer-plugins-base1.5-0
>   Suggests: kurento-dbg
>   Breaks: kurento-media-server-6.0
>   Replaces: kurento-media-server-6.0
>   Description: Kurento Media Server
>    KMS is a WebRTC-compatible server that processes audio and video
> streams, doing composable pipeline-based processing of media.
>   Homepage: https://www.kurento.org
>
> this is the output of /opt/log/openmeetings.log:
>     INFO 03-14 15:54:38.301 o.s.w.c.ContextLoader:271 [main] - Root
> WebApplicationContext: initialization started
>     INFO 03-14 15:54:38.953 o.s.o.j.LocalEntityManagerFactoryBean:416
> [main] - Initialized JPA EntityManagerFactory for persistence unit
> 'openmeetings'
>     INFO 03-14 15:54:39.170 o.s.s.c.ThreadPoolTaskExecutor:171 [main]
> - Initializing ExecutorService 'taskExecutor'
>     INFO 03-14 15:54:40.406 o.k.j.c.JsonRpcClientNettyWebSocket:191
> [rbeatExec-e1-t0] - [KurentoClient]  Connecting native client
>     INFO 03-14 15:54:40.409 o.k.j.c.JsonRpcClientNettyWebSocket:220
> [rbeatExec-e1-t0] - [KurentoClient]  Creating new NioEventLoopGroup
>     INFO 03-14 15:54:40.526 o.k.j.c.JsonRpcClientNettyWebSocket:234
> [ntLoopGroup-2-1] - [KurentoClient]  Initiating new Netty channel.
> Will create new handler too!
>     WARN 03-14 15:54:40.579 o.k.j.c.JsonRpcClientNettyWebSocket:308
> [rbeatExec-e1-t0] - [KurentoClient]  Trying to close a
> JsonRpcClientNettyWebSocket with channel == null
>     WARN 03-14 15:54:40.581 o.k.j.c.JsonRpcClient:270
> [rbeatExec-e1-t0] - [KurentoClient]  Error sending heartbeat to
> server. Exception: [KurentoClient]  Exception connecting to WebSocket
> server ws://127.0.0.1:8888/kurento
>     INFO 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:191
> [main] - [KurentoClient]  Connecting native client
>     WARN 03-14 15:54:40.581 o.k.j.c.JsonRpcClient:287
> [rbeatExec-e1-t0] - [KurentoClient]  Stopping heartbeat and closing
> client: failure during heartbeat mechanism
>     INFO 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:220
> [main] - [KurentoClient]  Creating new NioEventLoopGroup
>     INFO 03-14 15:54:40.582 o.k.j.c.JsonRpcClientNettyWebSocket:234
> [ntLoopGroup-3-1] - [KurentoClient]  Initiating new Netty channel.
> Will create new handler too!
>     WARN 03-14 15:54:40.584 o.k.j.c.JsonRpcClientNettyWebSocket:308
> [main] - [KurentoClient]  Trying to close a
> JsonRpcClientNettyWebSocket with channel == null
>     WARN 03-14 15:54:40.585 o.a.o.c.r.KurentoHandler:124 [main] - Fail
> to create Kurento client, will re-try in 10000 ms
>     INFO 03-14 15:54:40.707 o.q.i.StdSchedulerFactory:1220 [main] -
> Using default implementation for ThreadExecutor
>     INFO 03-14 15:54:40.716 o.q.c.SchedulerSignalerImpl:61 [main] -
> Initialized Scheduler Signaller of type: class
> org.quartz.core.SchedulerSignalerImpl
>     INFO 03-14 15:54:40.716 o.q.c.QuartzScheduler:229 [main] - Quartz
> Scheduler v.2.3.2 created.
>     INFO 03-14 15:54:40.717 o.q.s.RAMJobStore:155 [main] - RAMJobStore
> initialized.
>     INFO 03-14 15:54:40.717 o.q.c.QuartzScheduler:294 [main] -
> Scheduler meta-data: Quartz Scheduler (v2.3.2)
> 'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' with
> instanceId 'NON_CLUSTERED'
>      Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
>      NOT STARTED.
>      Currently in standby mode.
>      Number of jobs executed: 0
>      Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10
> threads.
>      Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
> support persistence. and is not clustered.
>
> port 8888 is not firewalles - neither is 5443.
>
> Any idea what to do to start KMS on buster - tomcat3 is running fine -
> this is 5.0.0 M3 adn I want to install M4 very soon.
>
> Thanks for any ideas or help
>
> Ed
>


-- 
WBR
Maxim aka solomax

unable to get KMS 6.13.0 started on debian buster 5.0.0 M3 tomcat3 running OK

Posted by in...@bureau-de-poste.net.
    systemctl status kurento-media-server.status returns:
● kurento-media-server.service - LSB: Kurento Media Server daemon
      Loaded: loaded (/etc/init.d/kurento-media-server; generated)
      Active: failed (Result: exit-code) since Sat 2020-03-21 22:12:26  
CET; 5 days ago
        Docs: man:systemd-sysv-generator(8)
     Process: 7791 ExecStart=/etc/init.d/kurento-media-server start  
(code=exited, status=2)
    
   Mar 21 22:12:26 server1.searchy.biz systemd[1]: Starting LSB:  
Kurento Media Server daemon...
   Mar 21 22:12:26 server1.searchy.biz kurento-media-server[7791]:  
Start Kurento Media Server:Configure Kernel resource limits for  
Kurento Media Server.
   Mar 21 22:12:26 server1.searchy.biz kurento-media-server[7791]:  
/etc/init.d/kurento-media-server: 122:  
/etc/init.d/kurento-media-server: Pipe call failed
   Mar 21 22:12:26 server1.searchy.biz systemd[1]:  
kurento-media-server.service: Control process exited, code=exited,  
status=2/INVALIDARGUMENT
   Mar 21 22:12:26 server1.searchy.biz systemd[1]:  
kurento-media-server.service: Failed with result 'exit-code'.
   Mar 21 22:12:26 server1.searchy.biz systemd[1]: Failed to start  
LSB: Kurento Media Server daemon.
 

root@server1 ~ # aptitude show kurento-media-server
  Package: kurento-media-server
  Version: 6.13.0-0kurento1.18.04
  New: yes
  State: installed
  Automatically installed: no
  Priority: optional
  Section: video
  Maintainer: Kurento <ku...@googlegroups.com>
  Architecture: amd64
  Uncompressed Size: 2,043 k
  Depends: kms-core (>= 6.7.0), kms-jsonrpc, kmsjsoncpp,  
libboost-filesystem1.65.1, libboost-log1.65.1,  
libboost-program-options1.65.1,
           libboost-system1.65.1, libboost-thread1.65.1, libc6 (>=  
2.24), libgcc1 (>= 1:3.0), libglib2.0-0 (>= 2.41.1), libglibmm-2.4-1v5  
(>= 2.54.0),
           libgstreamer1.5-0 (>= 1.8.1), libsigc++-2.0-0v5 (>= 2.8.0),  
libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 6), binutils, gstreamer1.5-libav,
           gstreamer1.5-plugins-bad, gstreamer1.5-plugins-base,  
gstreamer1.5-plugins-good, gstreamer1.5-plugins-ugly, kms-elements (>=  
6.7.0), kms-filters
           (>= 6.7.0), libgstreamer-plugins-base1.5-0
  Suggests: kurento-dbg
  Breaks: kurento-media-server-6.0
  Replaces: kurento-media-server-6.0
  Description: Kurento Media Server
   KMS is a WebRTC-compatible server that processes audio and video  
streams, doing composable pipeline-based processing of media.
  Homepage: https://www.kurento.org

this is the output of /opt/log/openmeetings.log:
    INFO 03-14 15:54:38.301 o.s.w.c.ContextLoader:271 [main] - Root  
WebApplicationContext: initialization started
    INFO 03-14 15:54:38.953 o.s.o.j.LocalEntityManagerFactoryBean:416  
[main] - Initialized JPA EntityManagerFactory for persistence unit  
'openmeetings'
    INFO 03-14 15:54:39.170 o.s.s.c.ThreadPoolTaskExecutor:171 [main]  
- Initializing ExecutorService 'taskExecutor'
    INFO 03-14 15:54:40.406 o.k.j.c.JsonRpcClientNettyWebSocket:191  
[rbeatExec-e1-t0] - [KurentoClient]  Connecting native client
    INFO 03-14 15:54:40.409 o.k.j.c.JsonRpcClientNettyWebSocket:220  
[rbeatExec-e1-t0] - [KurentoClient]  Creating new NioEventLoopGroup
    INFO 03-14 15:54:40.526 o.k.j.c.JsonRpcClientNettyWebSocket:234  
[ntLoopGroup-2-1] - [KurentoClient]  Initiating new Netty channel.  
Will create new handler too!
    WARN 03-14 15:54:40.579 o.k.j.c.JsonRpcClientNettyWebSocket:308  
[rbeatExec-e1-t0] - [KurentoClient]  Trying to close a  
JsonRpcClientNettyWebSocket with channel == null
    WARN 03-14 15:54:40.581 o.k.j.c.JsonRpcClient:270  
[rbeatExec-e1-t0] - [KurentoClient]  Error sending heartbeat to  
server. Exception: [KurentoClient]  Exception connecting to WebSocket  
server ws://127.0.0.1:8888/kurento
    INFO 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:191  
[main] - [KurentoClient]  Connecting native client
    WARN 03-14 15:54:40.581 o.k.j.c.JsonRpcClient:287  
[rbeatExec-e1-t0] - [KurentoClient]  Stopping heartbeat and closing  
client: failure during heartbeat mechanism
    INFO 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:220  
[main] - [KurentoClient]  Creating new NioEventLoopGroup
    INFO 03-14 15:54:40.582 o.k.j.c.JsonRpcClientNettyWebSocket:234  
[ntLoopGroup-3-1] - [KurentoClient]  Initiating new Netty channel.  
Will create new handler too!
    WARN 03-14 15:54:40.584 o.k.j.c.JsonRpcClientNettyWebSocket:308  
[main] - [KurentoClient]  Trying to close a  
JsonRpcClientNettyWebSocket with channel == null
    WARN 03-14 15:54:40.585 o.a.o.c.r.KurentoHandler:124 [main] - Fail  
to create Kurento client, will re-try in 10000 ms
    INFO 03-14 15:54:40.707 o.q.i.StdSchedulerFactory:1220 [main] -  
Using default implementation for ThreadExecutor
    INFO 03-14 15:54:40.716 o.q.c.SchedulerSignalerImpl:61 [main] -  
Initialized Scheduler Signaller of type: class  
org.quartz.core.SchedulerSignalerImpl
    INFO 03-14 15:54:40.716 o.q.c.QuartzScheduler:229 [main] - Quartz  
Scheduler v.2.3.2 created.
    INFO 03-14 15:54:40.717 o.q.s.RAMJobStore:155 [main] - RAMJobStore  
initialized.
    INFO 03-14 15:54:40.717 o.q.c.QuartzScheduler:294 [main] -  
Scheduler meta-data: Quartz Scheduler (v2.3.2)  
'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' with  
instanceId 'NON_CLUSTERED'
     Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
     NOT STARTED.
     Currently in standby mode.
     Number of jobs executed: 0
     Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
     Using job-store 'org.quartz.simpl.RAMJobStore' - which does not  
support persistence. and is not clustered.

port 8888 is not firewalles - neither is 5443.

Any idea what to do to start KMS on buster - tomcat3 is running fine -  
this is 5.0.0 M3 adn I want to install M4 very soon.

Thanks for any ideas or help

Ed

Re: Invalid Hash via SOAP API call

Posted by Maxim Solodovnik <so...@gmail.com>.
`open in same browser`
This is the question I have asked million times ....
multiple tabs/windows share _the same_ session
You can't be loggen in with different hashes and have same session

once in ~30 seconds page ping back to refresh session
and you got "Access denied"
expected

On Fri, 27 Mar 2020 at 21:54, Daniel Baker <in...@collisiondetection.biz>
wrote:

> Yes  I can  reproduce  this.
>
>
> If I have  2  different  rooms ( room 29 , 31 )   open  in same  browser
> invalid  hash is  shown.
>
> It also  happens  if  I have   2  rooms  the  same ( 29, 29, ... )
>
>
> It  actually  takes * some time,   30 seconds* or so  for  the Invalid
> hash  error to show.
>
>
> Thanks,
>
>
> Dan
> On 27/03/2020 05:07, Maxim Solodovnik wrote:
>
> Well,
>
> just tested hashes
> This error is only observed in case multiple tabs are opened in the same
> browser
>
> Is this issue reproducible for you if there is only one user in the room?
>
> Can you test this behavior with latest M4
> (new version of Moodle plugin will be required)
>
> On Thu, 26 Mar 2020 at 14:12, Maxim Solodovnik <so...@gmail.com>
> wrote:
>
>> According to above access log
>> This URL
>> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>> has been queried 2 times
>> First one was
>> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>> Second
>>
>> /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>
>> Since secureHash is one-time hash here might be the issue
>> It is not clear why session was invalidated .....
>> I'll try to perform more test tonight/tomorrow
>>
>> On Thu, 26 Mar 2020 at 13:49, Daniel Baker <in...@collisiondetection.biz>
>> wrote:
>>
>>> No other  OM logins.
>>>
>>>
>>> I  actually  titled this  wrong,  it  is a  REST  call not  SOAP.
>>>
>>>
>>> Thanks,
>>>
>>>
>>> Dan
>>>
>>>
>>> On 26/03/2020 00:27, Maxim Solodovnik wrote:
>>>
>>> is it possible OM was opened in second tab with active login?
>>>
>>> On Thu, 26 Mar 2020 at 04:15, Daniel Baker <in...@collisiondetection.biz>
>>> wrote:
>>>
>>>> Not sure  why  I am getting this  during  entering of a room :
>>>>
>>>>
>>>> I get invalid  hash / Access denied   show in the browser:
>>>>
>>>>
>>>> [image: image]
>>>>
>>>>
>>>> The  url  looks  like this  which seems correct  to my understanding  :
>>>>
>>>>
>>>>  tail -f localhost_access_log.2020-03-25
>>>>
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "GET
>>>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>>>> 200 96
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "POST
>>>> /openmeetings/services/user/hash?&sid=973f7132-39f7-47d0-b614-7845c4ed0411
>>>> HTTP/1.1" 200 96
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>> HTTP/1.1" 200 7231
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>> /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>> /openmeetings/css/theme.css HTTP/1.1" 304 -
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>>> /openmeetings/css/custom.css HTTP/1.1" 304 -
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>>>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>>>> 200 96
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>>>> /openmeetings/services/room/32?&sid=25d019cb-728c-4c7e-a88e-88910b3eae51
>>>> HTTP/1.1" 200 444
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "GET
>>>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>>>> 200 96
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "POST
>>>> /openmeetings/services/user/hash?&sid=bd8227ad-88d1-41ba-b4ce-69239844e5a1
>>>> HTTP/1.1" 200 96
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>>>> **/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.pages.HashPage?0-1.0
>>>> *-access~denied*&secure=9c271470-cfaa-4e95-9d64-**9210b9e4a7cc&language=1&_=1585164268523
>>>> HTTP/1.1" 200 180
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>>>> /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>>> HTTP/1.1" 200 7328
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>>>> /openmeetings/wicket/resource/com.googlecode.wicket.kendo.ui.theme.Initializer/kendo.default.mobile.min-ver-70A144DCABA4386C973AE2446CA25F3D.css
>>>> HTTP/1.1" 200 111339
>>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>>>> /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>>>>
>>>>
>>>>
>>>> OM  Version :
>>>>
>>>>
>>>> Name OpenMeetings  Version5.0.0-M3 Revisionb739f87 Build date2019-12-11T11:42:09Z
>>>>
>>>>
>>>> I  can see access denied in the log so  that pinpoints it somewhat.  Is
>>>> there a way  to see my  SOAP call is  correct  or a  verbose  logging mode ?
>>>>
>>>> Thanks,
>>>>
>>>> Dan
>>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
> --
> WBR
> Maxim aka solomax
>
>

-- 
WBR
Maxim aka solomax

Re: Invalid Hash via SOAP API call

Posted by Daniel Baker <in...@collisiondetection.biz>.
Yes  I can  reproduce  this.


If I have  2  different  rooms ( room 29 , 31 )   open  in same browser 
   invalid  hash is  shown.

It also  happens  if  I have   2  rooms  the  same ( 29, 29, ... )


It  actually  takes *some time,   30 seconds* or so  for the Invalid  
hash  error to show.


Thanks,


Dan

On 27/03/2020 05:07, Maxim Solodovnik wrote:
> Well,
>
> just tested hashes
> This error is only observed in case multiple tabs are opened in the 
> same browser
>
> Is this issue reproducible for you if there is only one user in the room?
>
> Can you test this behavior with latest M4
> (new version of Moodle plugin will be required)
>
> On Thu, 26 Mar 2020 at 14:12, Maxim Solodovnik <solomax666@gmail.com 
> <ma...@gmail.com>> wrote:
>
>     According to above access log
>     This URL
>     /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>     has been queried 2 times
>     First one was
>     /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>     Second
>     /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>
>     Since secureHash is one-time hash here might be the issue
>     It is not clear why session was invalidated .....
>     I'll try to perform more test tonight/tomorrow
>
>     On Thu, 26 Mar 2020 at 13:49, Daniel Baker
>     <info@collisiondetection.biz <ma...@collisiondetection.biz>>
>     wrote:
>
>         No other  OM logins.
>
>
>         I  actually  titled this  wrong,  it  is a  REST call not  SOAP.
>
>
>         Thanks,
>
>
>         Dan
>
>
>         On 26/03/2020 00:27, Maxim Solodovnik wrote:
>>         is it possible OM was opened in second tab with active login?
>>
>>         On Thu, 26 Mar 2020 at 04:15, Daniel Baker
>>         <info@collisiondetection.biz
>>         <ma...@collisiondetection.biz>> wrote:
>>
>>             Not sure  why  I am getting this  during entering of a room :
>>
>>
>>             I get invalid  hash / Access denied   show in the browser:
>>
>>
>>             image
>>
>>
>>
>>             The  url  looks  like this  which seems correct  to my
>>             understanding  :
>>
>>
>>             tail -f localhost_access_log.2020-03-25
>>
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "GET
>>             /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>>             HTTP/1.1" 200 96
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "POST
>>             /openmeetings/services/user/hash?&sid=973f7132-39f7-47d0-b614-7845c4ed0411
>>             HTTP/1.1" 200 96
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>             /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>             HTTP/1.1" 200 7231
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>             /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>             /openmeetings/css/theme.css HTTP/1.1" 304 -
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>             /openmeetings/css/custom.css HTTP/1.1" 304 -
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>>             /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>>             HTTP/1.1" 200 96
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>>             /openmeetings/services/room/32?&sid=25d019cb-728c-4c7e-a88e-88910b3eae51
>>             HTTP/1.1" 200 444
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "GET
>>             /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>>             HTTP/1.1" 200 96
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "POST
>>             /openmeetings/services/user/hash?&sid=bd8227ad-88d1-41ba-b4ce-69239844e5a1
>>             HTTP/1.1" 200 96
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>>             **/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.pages.HashPage?0-1.0*-access~denied*&secure=9c271470-cfaa-4e95-9d64-**9210b9e4a7cc&language=1&_=1585164268523
>>             HTTP/1.1" 200 180
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>>             /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>             HTTP/1.1" 200 7328
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>>             /openmeetings/wicket/resource/com.googlecode.wicket.kendo.ui.theme.Initializer/kendo.default.mobile.min-ver-70A144DCABA4386C973AE2446CA25F3D.css
>>             HTTP/1.1" 200 111339
>>             XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>>             /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>>
>>
>>
>>             OM  Version :
>>
>>
>>             Name OpenMeetings  Version5.0.0-M3 Revisionb739f87 Build date2019-12-11T11:42:09Z
>>
>>
>>             I  can see access denied in the log so  that pinpoints it
>>             somewhat.  Is there a way  to see my  SOAP call is 
>>             correct  or a  verbose logging mode ?
>>
>>             Thanks,
>>
>>             Dan
>>
>>
>>
>>         -- 
>>         WBR
>>         Maxim aka solomax
>
>
>
>     -- 
>     WBR
>     Maxim aka solomax
>
>
>
> -- 
> WBR
> Maxim aka solomax

Re: Invalid Hash via SOAP API call

Posted by Maxim Solodovnik <so...@gmail.com>.
Well,

just tested hashes
This error is only observed in case multiple tabs are opened in the same
browser

Is this issue reproducible for you if there is only one user in the room?

Can you test this behavior with latest M4
(new version of Moodle plugin will be required)

On Thu, 26 Mar 2020 at 14:12, Maxim Solodovnik <so...@gmail.com> wrote:

> According to above access log
> This URL
> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
> has been queried 2 times
> First one was
> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
> Second
>
> /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>
> Since secureHash is one-time hash here might be the issue
> It is not clear why session was invalidated .....
> I'll try to perform more test tonight/tomorrow
>
> On Thu, 26 Mar 2020 at 13:49, Daniel Baker <in...@collisiondetection.biz>
> wrote:
>
>> No other  OM logins.
>>
>>
>> I  actually  titled this  wrong,  it  is a  REST  call not  SOAP.
>>
>>
>> Thanks,
>>
>>
>> Dan
>>
>>
>> On 26/03/2020 00:27, Maxim Solodovnik wrote:
>>
>> is it possible OM was opened in second tab with active login?
>>
>> On Thu, 26 Mar 2020 at 04:15, Daniel Baker <in...@collisiondetection.biz>
>> wrote:
>>
>>> Not sure  why  I am getting this  during  entering of a room :
>>>
>>>
>>> I get invalid  hash / Access denied   show in the browser:
>>>
>>>
>>> [image: image]
>>>
>>>
>>> The  url  looks  like this  which seems correct  to my understanding  :
>>>
>>>
>>>  tail -f localhost_access_log.2020-03-25
>>>
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "GET
>>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>>> 200 96
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "POST
>>> /openmeetings/services/user/hash?&sid=973f7132-39f7-47d0-b614-7845c4ed0411
>>> HTTP/1.1" 200 96
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>> HTTP/1.1" 200 7231
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>> /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>> /openmeetings/css/theme.css HTTP/1.1" 304 -
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>>> /openmeetings/css/custom.css HTTP/1.1" 304 -
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>>> 200 96
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>>> /openmeetings/services/room/32?&sid=25d019cb-728c-4c7e-a88e-88910b3eae51
>>> HTTP/1.1" 200 444
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "GET
>>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>>> 200 96
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "POST
>>> /openmeetings/services/user/hash?&sid=bd8227ad-88d1-41ba-b4ce-69239844e5a1
>>> HTTP/1.1" 200 96
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>>> **/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.pages.HashPage?0-1.0
>>> *-access~denied*&secure=9c271470-cfaa-4e95-9d64-**9210b9e4a7cc&language=1&_=1585164268523
>>> HTTP/1.1" 200 180
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>>> /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>>> HTTP/1.1" 200 7328
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>>> /openmeetings/wicket/resource/com.googlecode.wicket.kendo.ui.theme.Initializer/kendo.default.mobile.min-ver-70A144DCABA4386C973AE2446CA25F3D.css
>>> HTTP/1.1" 200 111339
>>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>>> /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>>>
>>>
>>>
>>> OM  Version :
>>>
>>>
>>> Name OpenMeetings  Version5.0.0-M3 Revisionb739f87 Build date2019-12-11T11:42:09Z
>>>
>>>
>>> I  can see access denied in the log so  that pinpoints it somewhat.  Is
>>> there a way  to see my  SOAP call is  correct  or a  verbose  logging mode ?
>>>
>>> Thanks,
>>>
>>> Dan
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>>
>
> --
> WBR
> Maxim aka solomax
>


-- 
WBR
Maxim aka solomax

Re: Invalid Hash via SOAP API call

Posted by Maxim Solodovnik <so...@gmail.com>.
According to above access log
This URL
/openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
has been queried 2 times
First one was
/openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
Second
/openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1

Since secureHash is one-time hash here might be the issue
It is not clear why session was invalidated .....
I'll try to perform more test tonight/tomorrow

On Thu, 26 Mar 2020 at 13:49, Daniel Baker <in...@collisiondetection.biz>
wrote:

> No other  OM logins.
>
>
> I  actually  titled this  wrong,  it  is a  REST  call not  SOAP.
>
>
> Thanks,
>
>
> Dan
>
>
> On 26/03/2020 00:27, Maxim Solodovnik wrote:
>
> is it possible OM was opened in second tab with active login?
>
> On Thu, 26 Mar 2020 at 04:15, Daniel Baker <in...@collisiondetection.biz>
> wrote:
>
>> Not sure  why  I am getting this  during  entering of a room :
>>
>>
>> I get invalid  hash / Access denied   show in the browser:
>>
>>
>> [image: image]
>>
>>
>> The  url  looks  like this  which seems correct  to my understanding  :
>>
>>
>>  tail -f localhost_access_log.2020-03-25
>>
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "GET
>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>> 200 96
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "POST
>> /openmeetings/services/user/hash?&sid=973f7132-39f7-47d0-b614-7845c4ed0411
>> HTTP/1.1" 200 96
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>> HTTP/1.1" 200 7231
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>> /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>> /openmeetings/css/theme.css HTTP/1.1" 304 -
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>> /openmeetings/css/custom.css HTTP/1.1" 304 -
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>> 200 96
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>> /openmeetings/services/room/32?&sid=25d019cb-728c-4c7e-a88e-88910b3eae51
>> HTTP/1.1" 200 444
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "GET
>> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
>> 200 96
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "POST
>> /openmeetings/services/user/hash?&sid=bd8227ad-88d1-41ba-b4ce-69239844e5a1
>> HTTP/1.1" 200 96
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>> **/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.pages.HashPage?0-1.0
>> *-access~denied*&secure=9c271470-cfaa-4e95-9d64-**9210b9e4a7cc&language=1&_=1585164268523
>> HTTP/1.1" 200 180
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>> /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>> HTTP/1.1" 200 7328
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>> /openmeetings/wicket/resource/com.googlecode.wicket.kendo.ui.theme.Initializer/kendo.default.mobile.min-ver-70A144DCABA4386C973AE2446CA25F3D.css
>> HTTP/1.1" 200 111339
>> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>> /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>>
>>
>>
>> OM  Version :
>>
>>
>> Name OpenMeetings  Version5.0.0-M3 Revisionb739f87 Build date2019-12-11T11:42:09Z
>>
>>
>> I  can see access denied in the log so  that pinpoints it somewhat.  Is
>> there a way  to see my  SOAP call is  correct  or a  verbose  logging mode ?
>>
>> Thanks,
>>
>> Dan
>>
>
>
> --
> WBR
> Maxim aka solomax
>
>

-- 
WBR
Maxim aka solomax

Re: Invalid Hash via SOAP API call

Posted by Daniel Baker <in...@collisiondetection.biz>.
No other  OM logins.


I  actually  titled this  wrong,  it  is a  REST  call not SOAP.


Thanks,


Dan


On 26/03/2020 00:27, Maxim Solodovnik wrote:
> is it possible OM was opened in second tab with active login?
>
> On Thu, 26 Mar 2020 at 04:15, Daniel Baker 
> <info@collisiondetection.biz <ma...@collisiondetection.biz>> wrote:
>
>     Not sure  why  I am getting this  during  entering of a room :
>
>
>     I get invalid  hash / Access denied   show in the browser:
>
>
>     image
>
>
>
>     The  url  looks  like this  which seems correct  to my
>     understanding  :
>
>
>     tail -f localhost_access_log.2020-03-25
>
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "GET
>     /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>     HTTP/1.1" 200 96
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "POST
>     /openmeetings/services/user/hash?&sid=973f7132-39f7-47d0-b614-7845c4ed0411
>     HTTP/1.1" 200 96
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>     /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>     HTTP/1.1" 200 7231
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>     /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>     /openmeetings/css/theme.css HTTP/1.1" 304 -
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
>     /openmeetings/css/custom.css HTTP/1.1" 304 -
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>     /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>     HTTP/1.1" 200 96
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
>     /openmeetings/services/room/32?&sid=25d019cb-728c-4c7e-a88e-88910b3eae51
>     HTTP/1.1" 200 444
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "GET
>     /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40
>     HTTP/1.1" 200 96
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "POST
>     /openmeetings/services/user/hash?&sid=bd8227ad-88d1-41ba-b4ce-69239844e5a1
>     HTTP/1.1" 200 96
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>     **/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.pages.HashPage?0-1.0*-access~denied*&secure=9c271470-cfaa-4e95-9d64-**9210b9e4a7cc&language=1&_=1585164268523
>     HTTP/1.1" 200 180
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
>     /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
>     HTTP/1.1" 200 7328
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>     /openmeetings/wicket/resource/com.googlecode.wicket.kendo.ui.theme.Initializer/kendo.default.mobile.min-ver-70A144DCABA4386C973AE2446CA25F3D.css
>     HTTP/1.1" 200 111339
>     XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
>     /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>
>
>
>     OM  Version :
>
>
>     Name OpenMeetings  Version5.0.0-M3 Revisionb739f87 Build date2019-12-11T11:42:09Z
>
>
>     I  can see access denied in the log so  that pinpoints it
>     somewhat.  Is there a way  to see my  SOAP call is correct  or a 
>     verbose  logging mode ?
>
>     Thanks,
>
>     Dan
>
>
>
> -- 
> WBR
> Maxim aka solomax

Re: Invalid Hash via SOAP API call

Posted by Maxim Solodovnik <so...@gmail.com>.
is it possible OM was opened in second tab with active login?

On Thu, 26 Mar 2020 at 04:15, Daniel Baker <in...@collisiondetection.biz>
wrote:

> Not sure  why  I am getting this  during  entering of a room :
>
>
> I get invalid  hash / Access denied   show in the browser:
>
>
> [image: image]
>
>
> The  url  looks  like this  which seems correct  to my understanding  :
>
>
>  tail -f localhost_access_log.2020-03-25
>
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "GET
> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
> 200 96
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "POST
> /openmeetings/services/user/hash?&sid=973f7132-39f7-47d0-b614-7845c4ed0411
> HTTP/1.1" 200 96
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
> HTTP/1.1" 200 7231
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
> /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
> /openmeetings/css/theme.css HTTP/1.1" 304 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
> /openmeetings/css/custom.css HTTP/1.1" 304 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
> 200 96
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
> /openmeetings/services/room/32?&sid=25d019cb-728c-4c7e-a88e-88910b3eae51
> HTTP/1.1" 200 444
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "GET
> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
> 200 96
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "POST
> /openmeetings/services/user/hash?&sid=bd8227ad-88d1-41ba-b4ce-69239844e5a1
> HTTP/1.1" 200 96
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
> **/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.pages.HashPage?0-1.0
> *-access~denied*&secure=9c271470-cfaa-4e95-9d64-**9210b9e4a7cc&language=1&_=1585164268523
> HTTP/1.1" 200 180
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
> /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
> HTTP/1.1" 200 7328
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
> /openmeetings/wicket/resource/com.googlecode.wicket.kendo.ui.theme.Initializer/kendo.default.mobile.min-ver-70A144DCABA4386C973AE2446CA25F3D.css
> HTTP/1.1" 200 111339
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
> /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>
>
>
> OM  Version :
>
>
> Name OpenMeetings  Version5.0.0-M3 Revisionb739f87 Build date2019-12-11T11:42:09Z
>
>
> I  can see access denied in the log so  that pinpoints it somewhat.  Is
> there a way  to see my  SOAP call is  correct  or a  verbose  logging mode ?
>
> Thanks,
>
> Dan
>


-- 
WBR
Maxim aka solomax

Re: Invalid Hash via SOAP API call

Posted by Rodolfo Gonzalez <ro...@gmail.com>.
I'm having exactly the same problem (posted another thread).

El mié., 25 mar. 2020 a las 15:15, Daniel Baker (<
info@collisiondetection.biz>) escribió:

> Not sure  why  I am getting this  during  entering of a room :
>
>
> I get invalid  hash / Access denied   show in the browser:
>
>
> [image: image]
>
>
> The  url  looks  like this  which seems correct  to my understanding  :
>
>
>  tail -f localhost_access_log.2020-03-25
>
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "GET
> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
> 200 96
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:27 +0000] "POST
> /openmeetings/services/user/hash?&sid=973f7132-39f7-47d0-b614-7845c4ed0411
> HTTP/1.1" 200 96
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
> /openmeetings/hash?&secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
> HTTP/1.1" 200 7231
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
> /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
> /openmeetings/css/theme.css HTTP/1.1" 304 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "GET
> /openmeetings/css/custom.css HTTP/1.1" 304 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:28 +0000] "-" 400 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
> 200 96
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:29 +0000] "GET
> /openmeetings/services/room/32?&sid=25d019cb-728c-4c7e-a88e-88910b3eae51
> HTTP/1.1" 200 444
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "GET
> /openmeetings/services/user/login?&user=admin&pass=PASSWORD%40 HTTP/1.1"
> 200 96
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:30 +0000] "POST
> /openmeetings/services/user/hash?&sid=bd8227ad-88d1-41ba-b4ce-69239844e5a1
> HTTP/1.1" 200 96
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
> **/openmeetings/wicket/bookmarkable/org.apache.openmeetings.web.pages.HashPage?0-1.0
> *-access~denied*&secure=9c271470-cfaa-4e95-9d64-**9210b9e4a7cc&language=1&_=1585164268523
> HTTP/1.1" 200 180
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:32 +0000] "GET
> /openmeetings/hash;jsessionid=CE0DC1A368404F8AFDCE934313E81C96?secure=9c271470-cfaa-4e95-9d64-9210b9e4a7cc&language=1
> HTTP/1.1" 200 7328
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "-" 400 -
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
> /openmeetings/wicket/resource/com.googlecode.wicket.kendo.ui.theme.Initializer/kendo.default.mobile.min-ver-70A144DCABA4386C973AE2446CA25F3D.css
> HTTP/1.1" 200 111339
> XX.XXX.XXX.XXX - - [25/Mar/2020:19:24:33 +0000] "GET
> /openmeetings/css/theme_om/jquery-ui.min.css HTTP/1.1" 304 -
>
>
>
> OM  Version :
>
>
> Name OpenMeetings  Version5.0.0-M3 Revisionb739f87 Build date2019-12-11T11:42:09Z
>
>
> I  can see access denied in the log so  that pinpoints it somewhat.  Is
> there a way  to see my  SOAP call is  correct  or a  verbose  logging mode ?
>
> Thanks,
>
> Dan
>