You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openmeetings.apache.org by Maxim Solodovnik <so...@gmail.com> on 2014/06/01 06:15:25 UTC
[DISCUSSION] ACLs in Openmeetings
Hello All,
Due to multiple requests and issues (please see [1], [2], [3]) I would like
to change User object (remove status and "user level") and add Permissions.
As I can see the permissions should be
Admin == access to Admin module
Room == enter the room
Dashboard == access the whiteboard
Login == login to Om internal DB
Soap == use rest/soap calls
for example
current "regular" user will have all permissions except for Admin and Soap
current "soap" user will have soap permission only
current OAuth user will have no Login parmission
The proposed system looks extendable and should cover all current needs
I'm going to implement it in 3.0.3 and 3.1.0
Please let me know if you have any concerns/corrections
Thanks in advance
[1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
[2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
[3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
--
WBR
Maxim aka solomax
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Maxim Solodovnik <so...@gmail.com>.
Status is one user properties enabled/disabled. Disabled user will now be
the user with no permissions
All users in the system will remain as they are now, but with different set
of permissions.
On Sun, Jun 1, 2014 at 2:42 PM, 小野圭二 <on...@gmail.com> wrote:
> It's OK about removing 'user level'.
> But i could not say OK about 'remove status' immediately.
> Dose the mean of it as removing a registered user without changing the
> status?
>
> And what have permissions the SOAP user?
> I do not have any SOAP user , but have some users who are registered
> by using REST API.
>
> -Ono
>
> 2014-06-01 13:15 GMT+09:00 Maxim Solodovnik <so...@gmail.com>:
> > Hello All,
> >
> > Due to multiple requests and issues (please see [1], [2], [3]) I would
> like
> > to change User object (remove status and "user level") and add
> Permissions.
> >
> > As I can see the permissions should be
> > Admin == access to Admin module
> > Room == enter the room
> > Dashboard == access the whiteboard
> > Login == login to Om internal DB
> > Soap == use rest/soap calls
> >
> > for example
> > current "regular" user will have all permissions except for Admin and
> Soap
> > current "soap" user will have soap permission only
> > current OAuth user will have no Login parmission
> >
> > The proposed system looks extendable and should cover all current needs
> >
> > I'm going to implement it in 3.0.3 and 3.1.0
> >
> > Please let me know if you have any concerns/corrections
> >
> > Thanks in advance
> >
> > [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> > [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
> > [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
> >
> > --
> > WBR
> > Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: [DISCUSSION] ACLs in Openmeetings
Posted by 小野圭二 <on...@gmail.com>.
It's OK about removing 'user level'.
But i could not say OK about 'remove status' immediately.
Dose the mean of it as removing a registered user without changing the status?
And what have permissions the SOAP user?
I do not have any SOAP user , but have some users who are registered
by using REST API.
-Ono
2014-06-01 13:15 GMT+09:00 Maxim Solodovnik <so...@gmail.com>:
> Hello All,
>
> Due to multiple requests and issues (please see [1], [2], [3]) I would like
> to change User object (remove status and "user level") and add Permissions.
>
> As I can see the permissions should be
> Admin == access to Admin module
> Room == enter the room
> Dashboard == access the whiteboard
> Login == login to Om internal DB
> Soap == use rest/soap calls
>
> for example
> current "regular" user will have all permissions except for Admin and Soap
> current "soap" user will have soap permission only
> current OAuth user will have no Login parmission
>
> The proposed system looks extendable and should cover all current needs
>
> I'm going to implement it in 3.0.3 and 3.1.0
>
> Please let me know if you have any concerns/corrections
>
> Thanks in advance
>
> [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
> [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
>
> --
> WBR
> Maxim aka solomax
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Maxim Solodovnik <so...@gmail.com>.
Sure
The only difference, I guess, LDAP users should have no "Login" permission,
so these users need to be authenticated against LDAP only by default.
OFFTOPIC current LDAP code is very messy :( we have
https://issues.apache.org/jira/browse/OPENMEETINGS-964 to reimplement it
On Mon, Jun 2, 2014 at 12:46 AM, BBS Technik <do...@gmx.de> wrote:
> Hi Maxim,
>
> would your new concept influence the ldap login, or better, could ldap be
> a part of the new permission concept?
> Ldap is a needed authentication method for me and I think for a lot of
> productiv om servers.
>
> Best regards
>
> Ed
>
>
> Gesendet: Sonntag, 01. Juni 2014 um 06:15 Uhr
> Von: "Maxim Solodovnik" <so...@gmail.com>
> An: dev <de...@openmeetings.apache.org>, "Openmeetings user-list" <
> user@openmeetings.apache.org>
> Betreff: [DISCUSSION] ACLs in Openmeetings
>
> Hello All,
>
> Due to multiple requests and issues (please see [1], [2], [3]) I would
> like to change User object (remove status and "user level") and add
> Permissions.
>
> As I can see the permissions should be
> Admin == access to Admin module
> Room == enter the room
> Dashboard == access the whiteboard
> Login == login to Om internal DB
> Soap == use rest/soap calls
>
> for example
> current "regular" user will have all permissions except for Admin and Soap
> current "soap" user will have soap permission only
> current OAuth user will have no Login parmission
>
> The proposed system looks extendable and should cover all current needs
>
> I'm going to implement it in 3.0.3 and 3.1.0
>
> Please let me know if you have any concerns/corrections
>
> Thanks in advance
>
> [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> [2]
> https://issues.apache.org/jira/browse/OPENMEETINGS-1007[https://issues.apache.org/jira/browse/OPENMEETINGS-1007]
> [3]
> https://issues.apache.org/jira/browse/OPENMEETINGS-986[https://issues.apache.org/jira/browse/OPENMEETINGS-986]
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Aw: [DISCUSSION] ACLs in Openmeetings
Posted by BBS Technik <do...@gmx.de>.
Hi Maxim,
would your new concept influence the ldap login, or better, could ldap be a part of the new permission concept?
Ldap is a needed authentication method for me and I think for a lot of productiv om servers.
Best regards
Ed
Gesendet: Sonntag, 01. Juni 2014 um 06:15 Uhr
Von: "Maxim Solodovnik" <so...@gmail.com>
An: dev <de...@openmeetings.apache.org>, "Openmeetings user-list" <us...@openmeetings.apache.org>
Betreff: [DISCUSSION] ACLs in Openmeetings
Hello All,
Due to multiple requests and issues (please see [1], [2], [3]) I would like to change User object (remove status and "user level") and add Permissions.
As I can see the permissions should be
Admin == access to Admin module
Room == enter the room
Dashboard == access the whiteboard
Login == login to Om internal DB
Soap == use rest/soap calls
for example
current "regular" user will have all permissions except for Admin and Soap
current "soap" user will have soap permission only
current OAuth user will have no Login parmission
The proposed system looks extendable and should cover all current needs
I'm going to implement it in 3.0.3 and 3.1.0
Please let me know if you have any concerns/corrections
Thanks in advance
[1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
[2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007[https://issues.apache.org/jira/browse/OPENMEETINGS-1007]
[3] https://issues.apache.org/jira/browse/OPENMEETINGS-986[https://issues.apache.org/jira/browse/OPENMEETINGS-986]
--
WBR
Maxim aka solomax
Re: test of branch 3.0.3 (build 36)
Posted by Maxim Solodovnik <so...@gmail.com>.
I believe things might be better in #37
On 26 June 2014 18:32, Maxim Solodovnik <so...@gmail.com> wrote:
> I was able to start recording, but unfortunately the recorded video was
> not playable
> investigating :(
>
>
> On 26 June 2014 17:43, Michael Wuttke <mw...@beuth-hochschule.de> wrote:
>
>> Hello Maxim,
>>
>> I was not able to start the recording in an interview room. In the
>> settings/rights of that room recording is allowed.
>>
>> Please could you have look at it?
>>
>> Thanks,
>> Michael
>>
>> Am 26.6.2014 11:59, schrieb Maxim Solodovnik:
>>
>>> Userlevel class is missing: it is OK
>>>
>>> On 26 June 2014 16:47, Michael Wuttke <mw...@beuth-hochschule.de>
>>> wrote:
>>>
>>> Hi Peter,
>>>>
>>>> You are right. I've forgot it.
>>>>
>>>> I am sorry!
>>>> Michael
>>>>
>>>> Am 26.6.2014 10:34, schrieb Peter Dähn:
>>>> Hi Michael,
>>>>
>>>> I thought i read something about Java-Version caused this
>>>> problem,
>>>> but I can't find the e-mail regarding this... :-(
>>>>
>>>> I think it must be java 7 (oracle or openjdk).
>>>>
>>>> Greetings Peter
>>>>
>>>> Am 26.06.2014 10:22, schrieb Michael Wuttke:
>>>>
>>>> Hello Maxim,
>>>>
>>>> I tried to upgrade from om version 3.0.2 to the latest test build
>>>> 3.0.3 with:
>>>> ./admin.sh -v -i -file ../backup_20140626_302.zip --drop
>>>> --skip-default-rooms
>>>>
>>>> But I've got the following error messages:
>>>> Exception in thread "main" java.lang.UnsupportedClassVersionError:
>>>> org/apache/openmeetings/cli/Admin : Unsupported major.minor version
>>>> 51.0
>>>> at java.lang.ClassLoader.defineClass1(Native Method)
>>>>
>>>> at
>>>> java.lang.ClassLoader.defineClass(ClassLoader.java:643)
>>>> at
>>>>
>>>>
>>>> java.security.SecureClassLoader.defineClass(
>>> SecureClassLoader.java:142)
>>>
>>>>
>>>> at
>>>> java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
>>>> at
>>>> java.net.URLClassLoader.access$000(URLClassLoader.java:73)
>>>> at
>>>> java.net.URLClassLoader$1.run(URLClassLoader.java:212)
>>>> at
>>>> java.security.AccessController.doPrivileged(Native Method)
>>>> at
>>>> java.net.URLClassLoader.findClass(URLClassLoader.java:205)
>>>> at
>>>> java.lang.ClassLoader.loadClass(ClassLoader.java:323)
>>>> at
>>>> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
>>>> at
>>>> java.lang.ClassLoader.loadClass(ClassLoader.java:268)
>>>> Could not find the main class: org.apache.openmeetings.cli.Admin.
>>>> Program will exit.
>>>>
>>>> In the persistence.xml the
>>>> org.apache.openmeetings.db.entity.user.Userlevel class is missing.
>>>> Is it right?
>>>>
>>>> Do you have any idea what is wrong?
>>>>
>>>> Thank you & Greetings,
>>>> Michael
>>>>
>>>> --
>>>> B.Sc. Peter Dähn
>>>> Virtueller Campus Rheinland-Pfalz [1]
>>>> Postfach 3049
>>>> 67653 Kaiserslautern
>>>> Tel: 0631/205-4944
>>>> Olat [2]
>>>>
>>>> Links:
>>>> ------
>>>> [1] http://www.vcrp.de/ [1]
>>>> [2] https://olat.vcrp.de/ [2]
>>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>> Links:
>>> ------
>>> [1] http://www.vcrp.de/
>>> [2] https://olat.vcrp.de/
>>>
>>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: test of branch 3.0.3 (build 36)
Posted by Maxim Solodovnik <so...@gmail.com>.
I was able to start recording, but unfortunately the recorded video was not
playable
investigating :(
On 26 June 2014 17:43, Michael Wuttke <mw...@beuth-hochschule.de> wrote:
> Hello Maxim,
>
> I was not able to start the recording in an interview room. In the
> settings/rights of that room recording is allowed.
>
> Please could you have look at it?
>
> Thanks,
> Michael
>
> Am 26.6.2014 11:59, schrieb Maxim Solodovnik:
>
>> Userlevel class is missing: it is OK
>>
>> On 26 June 2014 16:47, Michael Wuttke <mw...@beuth-hochschule.de>
>> wrote:
>>
>> Hi Peter,
>>>
>>> You are right. I've forgot it.
>>>
>>> I am sorry!
>>> Michael
>>>
>>> Am 26.6.2014 10:34, schrieb Peter Dähn:
>>> Hi Michael,
>>>
>>> I thought i read something about Java-Version caused this
>>> problem,
>>> but I can't find the e-mail regarding this... :-(
>>>
>>> I think it must be java 7 (oracle or openjdk).
>>>
>>> Greetings Peter
>>>
>>> Am 26.06.2014 10:22, schrieb Michael Wuttke:
>>>
>>> Hello Maxim,
>>>
>>> I tried to upgrade from om version 3.0.2 to the latest test build
>>> 3.0.3 with:
>>> ./admin.sh -v -i -file ../backup_20140626_302.zip --drop
>>> --skip-default-rooms
>>>
>>> But I've got the following error messages:
>>> Exception in thread "main" java.lang.UnsupportedClassVersionError:
>>> org/apache/openmeetings/cli/Admin : Unsupported major.minor version
>>> 51.0
>>> at java.lang.ClassLoader.defineClass1(Native Method)
>>>
>>> at
>>> java.lang.ClassLoader.defineClass(ClassLoader.java:643)
>>> at
>>>
>>>
>>> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
>>
>>>
>>> at
>>> java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
>>> at
>>> java.net.URLClassLoader.access$000(URLClassLoader.java:73)
>>> at
>>> java.net.URLClassLoader$1.run(URLClassLoader.java:212)
>>> at
>>> java.security.AccessController.doPrivileged(Native Method)
>>> at
>>> java.net.URLClassLoader.findClass(URLClassLoader.java:205)
>>> at
>>> java.lang.ClassLoader.loadClass(ClassLoader.java:323)
>>> at
>>> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
>>> at
>>> java.lang.ClassLoader.loadClass(ClassLoader.java:268)
>>> Could not find the main class: org.apache.openmeetings.cli.Admin.
>>> Program will exit.
>>>
>>> In the persistence.xml the
>>> org.apache.openmeetings.db.entity.user.Userlevel class is missing.
>>> Is it right?
>>>
>>> Do you have any idea what is wrong?
>>>
>>> Thank you & Greetings,
>>> Michael
>>>
>>> --
>>> B.Sc. Peter Dähn
>>> Virtueller Campus Rheinland-Pfalz [1]
>>> Postfach 3049
>>> 67653 Kaiserslautern
>>> Tel: 0631/205-4944
>>> Olat [2]
>>>
>>> Links:
>>> ------
>>> [1] http://www.vcrp.de/ [1]
>>> [2] https://olat.vcrp.de/ [2]
>>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>> Links:
>> ------
>> [1] http://www.vcrp.de/
>> [2] https://olat.vcrp.de/
>>
>
--
WBR
Maxim aka solomax
Re: test of branch 3.0.3 (build 36)
Posted by Michael Wuttke <mw...@beuth-hochschule.de>.
Hello Maxim,
I was not able to start the recording in an interview room. In the
settings/rights of that room recording is allowed.
Please could you have look at it?
Thanks,
Michael
Am 26.6.2014 11:59, schrieb Maxim Solodovnik:
> Userlevel class is missing: it is OK
>
> On 26 June 2014 16:47, Michael Wuttke <mw...@beuth-hochschule.de>
> wrote:
>
>> Hi Peter,
>>
>> You are right. I've forgot it.
>>
>> I am sorry!
>> Michael
>>
>> Am 26.6.2014 10:34, schrieb Peter Dähn:
>> Hi Michael,
>>
>> I thought i read something about Java-Version caused this
>> problem,
>> but I can't find the e-mail regarding this... :-(
>>
>> I think it must be java 7 (oracle or openjdk).
>>
>> Greetings Peter
>>
>> Am 26.06.2014 10:22, schrieb Michael Wuttke:
>>
>> Hello Maxim,
>>
>> I tried to upgrade from om version 3.0.2 to the latest test build
>> 3.0.3 with:
>> ./admin.sh -v -i -file ../backup_20140626_302.zip --drop
>> --skip-default-rooms
>>
>> But I've got the following error messages:
>> Exception in thread "main" java.lang.UnsupportedClassVersionError:
>> org/apache/openmeetings/cli/Admin : Unsupported major.minor version
>> 51.0
>> at java.lang.ClassLoader.defineClass1(Native Method)
>>
>> at
>> java.lang.ClassLoader.defineClass(ClassLoader.java:643)
>> at
>>
>>
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
>>
>> at
>> java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
>> at
>> java.net.URLClassLoader.access$000(URLClassLoader.java:73)
>> at
>> java.net.URLClassLoader$1.run(URLClassLoader.java:212)
>> at
>> java.security.AccessController.doPrivileged(Native Method)
>> at
>> java.net.URLClassLoader.findClass(URLClassLoader.java:205)
>> at
>> java.lang.ClassLoader.loadClass(ClassLoader.java:323)
>> at
>> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
>> at
>> java.lang.ClassLoader.loadClass(ClassLoader.java:268)
>> Could not find the main class: org.apache.openmeetings.cli.Admin.
>> Program will exit.
>>
>> In the persistence.xml the
>> org.apache.openmeetings.db.entity.user.Userlevel class is missing.
>> Is it right?
>>
>> Do you have any idea what is wrong?
>>
>> Thank you & Greetings,
>> Michael
>>
>> --
>> B.Sc. Peter Dähn
>> Virtueller Campus Rheinland-Pfalz [1]
>> Postfach 3049
>> 67653 Kaiserslautern
>> Tel: 0631/205-4944
>> Olat [2]
>>
>> Links:
>> ------
>> [1] http://www.vcrp.de/ [1]
>> [2] https://olat.vcrp.de/ [2]
>
> --
> WBR
> Maxim aka solomax
>
> Links:
> ------
> [1] http://www.vcrp.de/
> [2] https://olat.vcrp.de/
Re: test of branch 3.0.3 (build 36)
Posted by Maxim Solodovnik <so...@gmail.com>.
Userlevel class is missing: it is OK
On 26 June 2014 16:47, Michael Wuttke <mw...@beuth-hochschule.de> wrote:
> Hi Peter,
>
> You are right. I've forgot it.
>
> I am sorry!
> Michael
>
> Am 26.6.2014 10:34, schrieb Peter Dähn:
>
>> Hi Michael,
>>
>> I thought i read something about Java-Version caused this problem,
>> but I can't find the e-mail regarding this... :-(
>>
>> I think it must be java 7 (oracle or openjdk).
>>
>> Greetings Peter
>>
>> Am 26.06.2014 10:22, schrieb Michael Wuttke:
>>
>>
>> Hello Maxim,
>>>
>>> I tried to upgrade from om version 3.0.2 to the latest test build
>>> 3.0.3 with:
>>> ./admin.sh -v -i -file ../backup_20140626_302.zip --drop
>>> --skip-default-rooms
>>>
>>> But I've got the following error messages:
>>> Exception in thread "main" java.lang.UnsupportedClassVersionError:
>>> org/apache/openmeetings/cli/Admin : Unsupported major.minor version
>>> 51.0
>>> at java.lang.ClassLoader.defineClass1(Native Method)
>>>
>>> at
>>> java.lang.ClassLoader.defineClass(ClassLoader.java:643)
>>> at
>>>
>>> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
>>
>>>
>>> at
>>> java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
>>> at
>>> java.net.URLClassLoader.access$000(URLClassLoader.java:73)
>>> at
>>> java.net.URLClassLoader$1.run(URLClassLoader.java:212)
>>> at
>>> java.security.AccessController.doPrivileged(Native Method)
>>> at
>>> java.net.URLClassLoader.findClass(URLClassLoader.java:205)
>>> at
>>> java.lang.ClassLoader.loadClass(ClassLoader.java:323)
>>> at
>>> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
>>> at
>>> java.lang.ClassLoader.loadClass(ClassLoader.java:268)
>>> Could not find the main class: org.apache.openmeetings.cli.Admin.
>>> Program will exit.
>>>
>>> In the persistence.xml the
>>> org.apache.openmeetings.db.entity.user.Userlevel class is missing.
>>> Is it right?
>>>
>>> Do you have any idea what is wrong?
>>>
>>> Thank you & Greetings,
>>> Michael
>>>
>>
>> --
>> B.Sc. Peter Dähn
>> Virtueller Campus Rheinland-Pfalz [1]
>> Postfach 3049
>> 67653 Kaiserslautern
>> Tel: 0631/205-4944
>> Olat [2]
>>
>>
>> Links:
>> ------
>> [1] http://www.vcrp.de/
>> [2] https://olat.vcrp.de/
>>
>
>
--
WBR
Maxim aka solomax
Re: test of branch 3.0.3 (build 36)
Posted by Michael Wuttke <mw...@beuth-hochschule.de>.
Hi Peter,
You are right. I've forgot it.
I am sorry!
Michael
Am 26.6.2014 10:34, schrieb Peter Dähn:
> Hi Michael,
>
> I thought i read something about Java-Version caused this problem,
> but I can't find the e-mail regarding this... :-(
>
> I think it must be java 7 (oracle or openjdk).
>
> Greetings Peter
>
> Am 26.06.2014 10:22, schrieb Michael Wuttke:
>
>> Hello Maxim,
>>
>> I tried to upgrade from om version 3.0.2 to the latest test build
>> 3.0.3 with:
>> ./admin.sh -v -i -file ../backup_20140626_302.zip --drop
>> --skip-default-rooms
>>
>> But I've got the following error messages:
>> Exception in thread "main" java.lang.UnsupportedClassVersionError:
>> org/apache/openmeetings/cli/Admin : Unsupported major.minor version
>> 51.0
>> at java.lang.ClassLoader.defineClass1(Native Method)
>>
>> at
>> java.lang.ClassLoader.defineClass(ClassLoader.java:643)
>> at
>>
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
>>
>> at
>> java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
>> at
>> java.net.URLClassLoader.access$000(URLClassLoader.java:73)
>> at
>> java.net.URLClassLoader$1.run(URLClassLoader.java:212)
>> at
>> java.security.AccessController.doPrivileged(Native Method)
>> at
>> java.net.URLClassLoader.findClass(URLClassLoader.java:205)
>> at
>> java.lang.ClassLoader.loadClass(ClassLoader.java:323)
>> at
>> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
>> at
>> java.lang.ClassLoader.loadClass(ClassLoader.java:268)
>> Could not find the main class: org.apache.openmeetings.cli.Admin.
>> Program will exit.
>>
>> In the persistence.xml the
>> org.apache.openmeetings.db.entity.user.Userlevel class is missing.
>> Is it right?
>>
>> Do you have any idea what is wrong?
>>
>> Thank you & Greetings,
>> Michael
>
> --
> B.Sc. Peter Dähn
> Virtueller Campus Rheinland-Pfalz [1]
> Postfach 3049
> 67653 Kaiserslautern
> Tel: 0631/205-4944
> Olat [2]
>
>
> Links:
> ------
> [1] http://www.vcrp.de/
> [2] https://olat.vcrp.de/
test of branch 3.0.3 (build 36)
Posted by Michael Wuttke <mw...@beuth-hochschule.de>.
Hello Maxim,
I tried to upgrade from om version 3.0.2 to the latest test build 3.0.3
with:
./admin.sh -v -i -file ../backup_20140626_302.zip --drop
--skip-default-rooms
But I've got the following error messages:
Exception in thread "main" java.lang.UnsupportedClassVersionError:
org/apache/openmeetings/cli/Admin : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:643)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
at java.net.URLClassLoader.access$000(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:212)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
at java.lang.ClassLoader.loadClass(ClassLoader.java:323)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:268)
Could not find the main class: org.apache.openmeetings.cli.Admin.
Program will exit.
In the persistence.xml the
org.apache.openmeetings.db.entity.user.Userlevel class is missing. Is it
right?
Do you have any idea what is wrong?
Thank you & Greetings,
Michael
Re: test of branch 3.0.3 (build 29)
Posted by Peter Dähn <da...@vcrp.de>.
ok.. weekly restart in the night could help for a while, till we install
a newer version...
Am 18.06.2014 15:50, schrieb Maxim Solodovnik:
> permgen is something need to be deeply analyzed :(
> will try to take a look
>
>
> On 18 June 2014 20:49, Maxim Solodovnik <solomax666@gmail.com
> <ma...@gmail.com>> wrote:
>
> fixed in #30
>
>
> On 18 June 2014 20:35, Peter Dähn <daehn@vcrp.de
> <ma...@vcrp.de>> wrote:
>
> Hi there,
>
> we also use postgres...
>
> I realized this a few days ago... OM starts with used perm gen
> space ~65M at the 12th of june...
>
> and it grows every day... see attached screenshot
>
> I think I need to observe this for a while...
>
> Greetings Peter
>
> Am 18.06.2014 11:39, schrieb Maxim Solodovnik:
>> reproducible in postgres :(
>> hate such iissues :(
>>
>>
>> On 18 June 2014 16:29, Michael Wuttke
>> <michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>> wrote:
>>
>> Hello Maxim,
>>
>> 2) I will test it tomorrow again with a fresh mysql
>> install, ok?
>> 3) I added -XX:MaxPermSize=256M to the JAVA_OPTS= in th
>> ./red5.sh script
>> in line 31 and now om works as expected without any
>> outofmemory errors. ;-)
>>
>> Tnaks,
>> Michael
>>
>> Am 18.06.2014 11:13, schrieb Maxim Solodovnik:
>> > 2) works for me
>> > very weird, not sure what else can be done :(
>> >
>> >
>> > On 18 June 2014 16:03, Maxim Solodovnik
>> <solomax666@gmail.com <ma...@gmail.com>
>> > <mailto:solomax666@gmail.com
>> <ma...@gmail.com>>> wrote:
>> >
>> > 2) will check
>> > 3) you can use it like this:
>> >
>> > JAVA_OPTS=-XX:MaxPermSize=256M ./red5.sh
>> >
>> >
>> > On 18 June 2014 16:00, Michael Wuttke
>> > <michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>
>> > <mailto:michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>>> wrote:
>> >
>> > Hello Maxim,
>> >
>> > what a quick response, great! ;-)
>> >
>> > 1) I've tested it and it works as expected. ;-)
>> (my test
>> > scenario see my
>> > last mail)
>> >
>> > 2) My steps:
>> > I. I log in as an OM admin at the OM GUI (works
>> as expected).
>> > II. Administration -> Users -> adding &
>> selecting the user 'soap' ->
>> > User details -> Usergroup -> select usergroup
>> 'webbase' -> click
>> > button
>> > Save (works as expected).
>> > III. Administration -> Usergroups -> new record
>> -> enter a Name
>> > for a
>> > new usergroup 'soap' -> click button Save
>> (works as expected).
>> > IV. select usergroup 'soap' on the left site of
>> the page
>> > Administration
>> > -> Usergroups (works as expected).
>> > V. Select the user 'soap' in the middle part
>> Usergroup -> Add
>> > user ->
>> > select user 'soap' from the drop down menu
>> caused for me an
>> > Internal error.
>> >
>> > 3) I tested ~/red5/red5-highperf.sh but I've
>> got the same error
>> > message
>> > after a while.
>> >
>> > "*|-XX:MaxPermSize=256M|*" is an JVM option for the red5.sh
>> > start script?
>> >
>> > Thanks,
>> > Michael
>> >
>> > Am 17.06.2014 20:06, schrieb Maxim Solodovnik:
>> > > 1) fixed
>> > > 2) I cannot reproduce :( can you provide as
>> detailed steps as
>> > possible?
>> > > 3) you can run "highperf" or add PermGen
>> memory using
>> > > "*|-XX:MaxPermSize=256M|*"
>> > >
>> > >
>> > > On 17 June 2014 22:15, Michael Wuttke
>> > > <michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>
>> > <mailto:michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>>
>> > > <mailto:michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>
>> > <mailto:michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>>>> wrote:
>> > >
>> > > Hello,
>> > >
>> > > I've tested the latest om build with the
>> following scenario:
>> > >
>> > > - om server:
>> > > * OS: debian wheezy
>> > > * database server: postgresql (version
>> 9.3)
>> > > * OM version: branch 3.0.3 (build 28)
>> > > * a clean install via cliadmin with
>> > > ./admin.sh -i -v -file backup.zip -tz
>> Europe/Berlin --drop
>> > > --skip-default-rooms --db-type postgresql
>> --db-host
>> > somehost --db-name
>> > > somename --db-user someuser --db-pass
>> somepass
>> > >
>> > > - moodle server:
>> > > * OS: debian wheezy
>> > > * database server: postgresql (version
>> 9.1)
>> > > * Moodle version: 2.7+ (build:
>> 20140613) -> not a
>> > clean install
>> > > * om moodle plugin: version 1.7.1 -
>> (build 2014051301)
>> > >
>> > > - user client:
>> > > * OS: ubuntu 14.04 LTS (trusty tahr)
>> > > * browser: FF 30.0 & Opera 12.16.1860
>> > >
>> > > Adding in OM a 'SOAP' user to create,
>> modify or delete OM
>> > rooms via
>> > > moodle is not a problem, or changing the
>> settings of a OM
>> > user.
>> > >
>> > > But some issues occurred during the test.
>> > >
>> > > 1. I still get the following error
>> message on the moodle
>> > server, when I
>> > > try to enter a new created om room (an
>> interview room in
>> > this case; I
>> > > created a conference, a webinar and a
>> interview room):
>> > >
>> > > Can not find data record in database
>> table course_modules.
>> > >
>> > > Debug info: SELECT id,course FROM
>> {course_modules}
>> > WHERE id = ?
>> > > [array (
>> > > 0 => '6',
>> > > )]
>> > > Error code: invalidrecord
>> > >
>> > > Stack trace:
>> > > line 1451 of
>> /lib/dml/moodle_database.php:
>> > > dml_missing_record_exception thrown
>> > > line 1427 of
>> /lib/dml/moodle_database.php: call to
>> > > moodle_database->get_record_select()
>> > > line 7088 of /lib/accesslib.php:
>> call to
>> > > moodle_database->get_record()
>> > > line 61 of
>> /mod/openmeetings/view.php: call to
>> > > context_module::instance()
>> > >
>> > > 2. When I try to add a user to a group
>> via the OM GUI:
>> > Administration ->
>> > > Usergroups -> new record -> enter a Name
>> for a new
>> > usergroup - this
>> > > works. But if I try to add a user to this
>> new usergroup
>> > via the drop
>> > > down menu Add user and try then to select
>> a user, I will
>> > get an Internal
>> > > error.
>> > >
>> > > Please see the pastebin entry for the
>> error message:
>> > > http://pastebin.com/ddm93jbS
>> > >
>> > > 3. Often I get a OutOfMemoryError:
>> PermGen space in the
>> > red5.log
>> > >
>> > > Please see also the pastebin entry for
>> this error message:
>> > > http://pastebin.com/SL5gXDGw
>> > >
>> > > Thanks,
>> > > Michael
>> > >
>> > > Am 17.06.2014 08:25, schrieb Maxim
>> Solodovnik:
>> > > > Regarding 1
>> > > > Could you please provide any repo steps?
>> > > >
>> > > >
>> > > > On 16 June 2014 19:03, Vasiliy Degtyarev
>> > <vasya@unipro.ru <ma...@unipro.ru>
>> <mailto:vasya@unipro.ru <ma...@unipro.ru>>
>> > > <mailto:vasya@unipro.ru
>> <ma...@unipro.ru> <mailto:vasya@unipro.ru
>> <ma...@unipro.ru>>>
>> > > > <mailto:vasya@unipro.ru
>> <ma...@unipro.ru> <mailto:vasya@unipro.ru
>> <ma...@unipro.ru>>
>> > <mailto:vasya@unipro.ru
>> <ma...@unipro.ru> <mailto:vasya@unipro.ru
>> <ma...@unipro.ru>>>>> wrote:
>> > > >
>> > > > Hello Michael,
>> > > >
>> > > > I have fixed second error for the
>> 3.0.3 branch.
>> > > >
>> > > > Vasiliy.
>> > > >
>> > > >
>> > > > On 16.06.2014 17:28, Michael Wuttke
>> wrote:
>> > > >
>> > > > Hello Maxim,
>> > > >
>> > > > I've tested the latest om build with the
>> > following scenario:
>> > > >
>> > > > - om server:
>> > > > * OS: debian wheezy
>> > > > * db server: postgresql (version
>> 9.3) ->
>> > a clean
>> > > install
>> > > > * OM version: branch 3.0.3
>> (build 27)
>> > > >
>> > > > - om server:
>> > > > * OS: debian wheezy
>> > > > * db server: postgresql (version 9.1)
>> > > > * Moodle version: 2.7+ (build:
>> 20140605) and
>> > > > + om moodle plugin: version 1.7.1 -
>> > (build 2014051301)
>> > > >
>> > > > - user client:
>> > > > * OS: ubuntu 14.04 LTS (trusty tahr)
>> > > > * browser: FF 30.0 & Opera 12.16.1860
>> > > >
>> > > > Adding in OM a 'SOAP' user to create,
>> modify or
>> > delete OM
>> > > rooms via
>> > > > moodle was not the problem. I also
>> could change the
>> > > settings of a OM
>> > > > user (f.e. add or change the
>> > usergroup/organisation). The
>> > > network
>> > > > testing works now. Thanks. ;-)
>> > > >
>> > > > But two issues occurred during this test.
>> > > >
>> > > > 1. Sometimes I've got the following error
>> > message on the
>> > > moodle
>> > > > server,
>> > > > when I tried to enter a new room (an
>> interview
>> > room in
>> > > this case):
>> > > >
>> > > > Can not find data record in database table
>> > course_modules.
>> > > >
>> > > > Debug info: SELECT id,course FROM
>> > {course_modules} WHERE
>> > > id = ?
>> > > > [array (
>> > > > 0 => '6',
>> > > > )]
>> > > > Error code: invalidrecord
>> > > >
>> > > > Stack trace:
>> > > > line 1451 of
>> /lib/dml/moodle_database.php:
>> > > > dml_missing_record_exception thrown
>> > > > line 1427 of
>> /lib/dml/moodle_database.php:
>> > call to
>> > > > moodle_database->get_record___select()
>> > > > line 7088 of /lib/accesslib.php: call to
>> > > > moodle_database->get_record()
>> > > > line 61 of
>> /mod/openmeetings/view.php: call to
>> > > > context_module::instance()
>> > > >
>> > > > 2. When I tried to change the OM
>> > settings/configuration
>> > > via the
>> > > > OM GUI:
>> > > > Administration -> Configuration ->
>> selecting the
>> > id 54
>> > > > (redirect.url.for.external.__users) ->
>> entering
>> > the Value
>> > > > 'mymoodleurl'
>> > > > and tried to save this entry, I've got an
>> > Internal error.
>> > > >
>> > > > See pastebin for the error messages:
>> > > > http://pastebin.com/hY15zvqv
>> > > >
>> > > > Thanks,
>> > > > Michael
>> > > >
>> > > > Am 14.06.2014 10:53, schrieb Maxim
>> Solodovnik:
>> > > >
>> > > > Thanks for the detailed report!
>> > > > build #27 should address first issue
>> > > >
>> > > > second was not reproducible here,
>> could you
>> > please
>> > > re-check?
>> > > >
>> > > >
>> > > > On 13 June 2014 19:33, Michael Wuttke
>> > > > <michael.wuttke@beuth-__hochschule.de
>> <ma...@beuth-__hochschule.de>
>> > <mailto:michael.wuttke@beuth-__hochschule.de
>> <ma...@beuth-__hochschule.de>>
>> > >
>> <mailto:michael.wuttke@beuth-__hochschule.de
>> <ma...@beuth-__hochschule.de>
>> > <mailto:michael.wuttke@beuth-__hochschule.de
>> <ma...@beuth-__hochschule.de>>>
>> > > >
>> <mailto:michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>
>> > <mailto:michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>>
>> > >
>> <mailto:michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>
>> > <mailto:michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>>>>
>> > > >
>> <mailto:michael.wuttke@beuth-__hochschule.de
>> <ma...@beuth-__hochschule.de>
>> > <mailto:michael.wuttke@beuth-__hochschule.de
>> <ma...@beuth-__hochschule.de>>
>> > >
>> <mailto:michael.wuttke@beuth-__hochschule.de
>> <ma...@beuth-__hochschule.de>
>> > <mailto:michael.wuttke@beuth-__hochschule.de
>> <ma...@beuth-__hochschule.de>>>
>> > > >
>> <mailto:michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>
>> > <mailto:michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>>
>> > >
>> <mailto:michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>
>> > <mailto:michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>>>>>> wrote:
>> > > >
>> > > > Hello Maxim,
>> > > >
>> > > > I've tested the branch 3.0.3
>> (build 26)
>> > now with a
>> > > > clean postgresql
>> > > > install. Two issues occurred during
>> > this test.
>> > > >
>> > > > 1. Adding a 'SOAP' user to create OM
>> > rooms via moodle
>> > > > (version 2.7 and
>> > > > om moodle plugin version 1.7.1 -
>> build
>> > 2014051301) is
>> > > > not a problem,
>> > > > like I tested yesterday. But to open
>> > the new
>> > > created OM
>> > > > room via moodle
>> > > > doesn't work. In the
>> openmeetings.log
>> > file I
>> > > found the
>> > > > following error
>> > > > messages:
>> > > > http://pastebin.com/rpTfhJcW
>> > > >
>> > > > 2. When I tried to add the new soap
>> > user to a
>> > > > organisation via the OM
>> > > > GUI: Administration -> Usergroups ->
>> > selecting the
>> > > > usergroup -> Add user
>> > > > via the drop down menu If got an
>> > Internal error.
>> > > >
>> > > > In the openmeetings.log file I found
>> > the following
>> > > > error messages:
>> > > > http://pastebin.com/q0h1aR3G
>> > > >
>> > > > Thanks,
>> > > > Michael
>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>
>
>
>
> --
> WBR
> Maxim aka solomax
>
>
>
>
> --
> WBR
> Maxim aka solomax
Re: test of branch 3.0.3 (build 29)
Posted by Maxim Solodovnik <so...@gmail.com>.
permgen is something need to be deeply analyzed :(
will try to take a look
On 18 June 2014 20:49, Maxim Solodovnik <so...@gmail.com> wrote:
> fixed in #30
>
>
> On 18 June 2014 20:35, Peter Dähn <da...@vcrp.de> wrote:
>
>> Hi there,
>>
>> we also use postgres...
>>
>> I realized this a few days ago... OM starts with used perm gen space ~65M
>> at the 12th of june...
>>
>> and it grows every day... see attached screenshot
>>
>> I think I need to observe this for a while...
>>
>> Greetings Peter
>>
>> Am 18.06.2014 11:39, schrieb Maxim Solodovnik:
>>
>> reproducible in postgres :(
>> hate such iissues :(
>>
>>
>> On 18 June 2014 16:29, Michael Wuttke <michael.wuttke@beuth-hochschule.de
>> > wrote:
>>
>>> Hello Maxim,
>>>
>>> 2) I will test it tomorrow again with a fresh mysql install, ok?
>>> 3) I added -XX:MaxPermSize=256M to the JAVA_OPTS= in th ./red5.sh script
>>> in line 31 and now om works as expected without any outofmemory errors.
>>> ;-)
>>>
>>> Tnaks,
>>> Michael
>>>
>>> Am 18.06.2014 11:13, schrieb Maxim Solodovnik:
>>> > 2) works for me
>>> > very weird, not sure what else can be done :(
>>> >
>>> >
>>> > On 18 June 2014 16:03, Maxim Solodovnik <solomax666@gmail.com
>>> > <ma...@gmail.com>> wrote:
>>> >
>>> > 2) will check
>>> > 3) you can use it like this:
>>> >
>>> > JAVA_OPTS=-XX:MaxPermSize=256M ./red5.sh
>>> >
>>> >
>>> > On 18 June 2014 16:00, Michael Wuttke
>>> > <michael.wuttke@beuth-hochschule.de
>>> > <ma...@beuth-hochschule.de>> wrote:
>>> >
>>> > Hello Maxim,
>>> >
>>> > what a quick response, great! ;-)
>>> >
>>> > 1) I've tested it and it works as expected. ;-) (my test
>>> > scenario see my
>>> > last mail)
>>> >
>>> > 2) My steps:
>>> > I. I log in as an OM admin at the OM GUI (works as expected).
>>> > II. Administration -> Users -> adding & selecting the user
>>> 'soap' ->
>>> > User details -> Usergroup -> select usergroup 'webbase' ->
>>> click
>>> > button
>>> > Save (works as expected).
>>> > III. Administration -> Usergroups -> new record -> enter a Name
>>> > for a
>>> > new usergroup 'soap' -> click button Save (works as expected).
>>> > IV. select usergroup 'soap' on the left site of the page
>>> > Administration
>>> > -> Usergroups (works as expected).
>>> > V. Select the user 'soap' in the middle part Usergroup -> Add
>>> > user ->
>>> > select user 'soap' from the drop down menu caused for me an
>>> > Internal error.
>>> >
>>> > 3) I tested ~/red5/red5-highperf.sh but I've got the same error
>>> > message
>>> > after a while.
>>> >
>>> > "*|-XX:MaxPermSize=256M|*" is an JVM option for the red5.sh
>>> > start script?
>>> >
>>> > Thanks,
>>> > Michael
>>> >
>>> > Am 17.06.2014 20:06, schrieb Maxim Solodovnik:
>>> > > 1) fixed
>>> > > 2) I cannot reproduce :( can you provide as detailed steps as
>>> > possible?
>>> > > 3) you can run "highperf" or add PermGen memory using
>>> > > "*|-XX:MaxPermSize=256M|*"
>>> > >
>>> > >
>>> > > On 17 June 2014 22:15, Michael Wuttke
>>> > > <michael.wuttke@beuth-hochschule.de
>>> > <ma...@beuth-hochschule.de>
>>> > > <mailto:michael.wuttke@beuth-hochschule.de
>>> > <ma...@beuth-hochschule.de>>> wrote:
>>> > >
>>> > > Hello,
>>> > >
>>> > > I've tested the latest om build with the following
>>> scenario:
>>> > >
>>> > > - om server:
>>> > > * OS: debian wheezy
>>> > > * database server: postgresql (version 9.3)
>>> > > * OM version: branch 3.0.3 (build 28)
>>> > > * a clean install via cliadmin with
>>> > > ./admin.sh -i -v -file backup.zip -tz Europe/Berlin
>>> --drop
>>> > > --skip-default-rooms --db-type postgresql --db-host
>>> > somehost --db-name
>>> > > somename --db-user someuser --db-pass somepass
>>> > >
>>> > > - moodle server:
>>> > > * OS: debian wheezy
>>> > > * database server: postgresql (version 9.1)
>>> > > * Moodle version: 2.7+ (build: 20140613) -> not a
>>> > clean install
>>> > > * om moodle plugin: version 1.7.1 - (build 2014051301)
>>> > >
>>> > > - user client:
>>> > > * OS: ubuntu 14.04 LTS (trusty tahr)
>>> > > * browser: FF 30.0 & Opera 12.16.1860
>>> > >
>>> > > Adding in OM a 'SOAP' user to create, modify or delete OM
>>> > rooms via
>>> > > moodle is not a problem, or changing the settings of a OM
>>> > user.
>>> > >
>>> > > But some issues occurred during the test.
>>> > >
>>> > > 1. I still get the following error message on the moodle
>>> > server, when I
>>> > > try to enter a new created om room (an interview room in
>>> > this case; I
>>> > > created a conference, a webinar and a interview room):
>>> > >
>>> > > Can not find data record in database table
>>> course_modules.
>>> > >
>>> > > Debug info: SELECT id,course FROM {course_modules}
>>> > WHERE id = ?
>>> > > [array (
>>> > > 0 => '6',
>>> > > )]
>>> > > Error code: invalidrecord
>>> > >
>>> > > Stack trace:
>>> > > line 1451 of /lib/dml/moodle_database.php:
>>> > > dml_missing_record_exception thrown
>>> > > line 1427 of /lib/dml/moodle_database.php: call
>>> to
>>> > > moodle_database->get_record_select()
>>> > > line 7088 of /lib/accesslib.php: call to
>>> > > moodle_database->get_record()
>>> > > line 61 of /mod/openmeetings/view.php: call to
>>> > > context_module::instance()
>>> > >
>>> > > 2. When I try to add a user to a group via the OM GUI:
>>> > Administration ->
>>> > > Usergroups -> new record -> enter a Name for a new
>>> > usergroup - this
>>> > > works. But if I try to add a user to this new usergroup
>>> > via the drop
>>> > > down menu Add user and try then to select a user, I will
>>> > get an Internal
>>> > > error.
>>> > >
>>> > > Please see the pastebin entry for the error message:
>>> > > http://pastebin.com/ddm93jbS
>>> > >
>>> > > 3. Often I get a OutOfMemoryError: PermGen space in the
>>> > red5.log
>>> > >
>>> > > Please see also the pastebin entry for this error
>>> message:
>>> > > http://pastebin.com/SL5gXDGw
>>> > >
>>> > > Thanks,
>>> > > Michael
>>> > >
>>> > > Am 17.06.2014 08:25, schrieb Maxim Solodovnik:
>>> > > > Regarding 1
>>> > > > Could you please provide any repo steps?
>>> > > >
>>> > > >
>>> > > > On 16 June 2014 19:03, Vasiliy Degtyarev
>>> > <vasya@unipro.ru <ma...@unipro.ru>
>>> > > <mailto:vasya@unipro.ru <ma...@unipro.ru>>
>>> > > > <mailto:vasya@unipro.ru <ma...@unipro.ru>
>>> > <mailto:vasya@unipro.ru <ma...@unipro.ru>>>> wrote:
>>> > > >
>>> > > > Hello Michael,
>>> > > >
>>> > > > I have fixed second error for the 3.0.3 branch.
>>> > > >
>>> > > > Vasiliy.
>>> > > >
>>> > > >
>>> > > > On 16.06.2014 17:28, Michael Wuttke wrote:
>>> > > >
>>> > > > Hello Maxim,
>>> > > >
>>> > > > I've tested the latest om build with the
>>> > following scenario:
>>> > > >
>>> > > > - om server:
>>> > > > * OS: debian wheezy
>>> > > > * db server: postgresql (version 9.3)
>>> ->
>>> > a clean
>>> > > install
>>> > > > * OM version: branch 3.0.3 (build 27)
>>> > > >
>>> > > > - om server:
>>> > > > * OS: debian wheezy
>>> > > > * db server: postgresql (version 9.1)
>>> > > > * Moodle version: 2.7+ (build:
>>> 20140605) and
>>> > > > + om moodle plugin: version 1.7.1 -
>>> > (build 2014051301)
>>> > > >
>>> > > > - user client:
>>> > > > * OS: ubuntu 14.04 LTS (trusty tahr)
>>> > > > * browser: FF 30.0 & Opera 12.16.1860
>>> > > >
>>> > > > Adding in OM a 'SOAP' user to create, modify or
>>> > delete OM
>>> > > rooms via
>>> > > > moodle was not the problem. I also could
>>> change the
>>> > > settings of a OM
>>> > > > user (f.e. add or change the
>>> > usergroup/organisation). The
>>> > > network
>>> > > > testing works now. Thanks. ;-)
>>> > > >
>>> > > > But two issues occurred during this test.
>>> > > >
>>> > > > 1. Sometimes I've got the following error
>>> > message on the
>>> > > moodle
>>> > > > server,
>>> > > > when I tried to enter a new room (an interview
>>> > room in
>>> > > this case):
>>> > > >
>>> > > > Can not find data record in database table
>>> > course_modules.
>>> > > >
>>> > > > Debug info: SELECT id,course FROM
>>> > {course_modules} WHERE
>>> > > id = ?
>>> > > > [array (
>>> > > > 0 => '6',
>>> > > > )]
>>> > > > Error code: invalidrecord
>>> > > >
>>> > > > Stack trace:
>>> > > > line 1451 of /lib/dml/moodle_database.php:
>>> > > > dml_missing_record_exception thrown
>>> > > > line 1427 of /lib/dml/moodle_database.php:
>>> > call to
>>> > > > moodle_database->get_record___select()
>>> > > > line 7088 of /lib/accesslib.php: call to
>>> > > > moodle_database->get_record()
>>> > > > line 61 of /mod/openmeetings/view.php:
>>> call to
>>> > > > context_module::instance()
>>> > > >
>>> > > > 2. When I tried to change the OM
>>> > settings/configuration
>>> > > via the
>>> > > > OM GUI:
>>> > > > Administration -> Configuration -> selecting
>>> the
>>> > id 54
>>> > > > (redirect.url.for.external.__users) -> entering
>>> > the Value
>>> > > > 'mymoodleurl'
>>> > > > and tried to save this entry, I've got an
>>> > Internal error.
>>> > > >
>>> > > > See pastebin for the error messages:
>>> > > > http://pastebin.com/hY15zvqv
>>> > > >
>>> > > > Thanks,
>>> > > > Michael
>>> > > >
>>> > > > Am 14.06.2014 10:53, schrieb Maxim Solodovnik:
>>> > > >
>>> > > > Thanks for the detailed report!
>>> > > > build #27 should address first issue
>>> > > >
>>> > > > second was not reproducible here, could you
>>> > please
>>> > > re-check?
>>> > > >
>>> > > >
>>> > > > On 13 June 2014 19:33, Michael Wuttke
>>> > > > <michael.wuttke@beuth-__hochschule.de
>>> > <ma...@beuth-__hochschule.de>
>>> > > <mailto:michael.wuttke@beuth-__hochschule.de
>>> > <ma...@beuth-__hochschule.de>>
>>> > > > <mailto:michael.wuttke@beuth-hochschule.de
>>> > <ma...@beuth-hochschule.de>
>>> > > <mailto:michael.wuttke@beuth-hochschule.de
>>> > <ma...@beuth-hochschule.de>>>
>>> > > > <mailto:
>>> michael.wuttke@beuth-__hochschule.de
>>> > <ma...@beuth-__hochschule.de>
>>> > > <mailto:michael.wuttke@beuth-__hochschule.de
>>> > <ma...@beuth-__hochschule.de>>
>>> > > > <mailto:michael.wuttke@beuth-hochschule.de
>>> > <ma...@beuth-hochschule.de>
>>> > > <mailto:michael.wuttke@beuth-hochschule.de
>>> > <ma...@beuth-hochschule.de>>>>> wrote:
>>> > > >
>>> > > > Hello Maxim,
>>> > > >
>>> > > > I've tested the branch 3.0.3 (build
>>> 26)
>>> > now with a
>>> > > > clean postgresql
>>> > > > install. Two issues occurred during
>>> > this test.
>>> > > >
>>> > > > 1. Adding a 'SOAP' user to create OM
>>> > rooms via moodle
>>> > > > (version 2.7 and
>>> > > > om moodle plugin version 1.7.1 - build
>>> > 2014051301) is
>>> > > > not a problem,
>>> > > > like I tested yesterday. But to open
>>> > the new
>>> > > created OM
>>> > > > room via moodle
>>> > > > doesn't work. In the openmeetings.log
>>> > file I
>>> > > found the
>>> > > > following error
>>> > > > messages:
>>> > > > http://pastebin.com/rpTfhJcW
>>> > > >
>>> > > > 2. When I tried to add the new soap
>>> > user to a
>>> > > > organisation via the OM
>>> > > > GUI: Administration -> Usergroups ->
>>> > selecting the
>>> > > > usergroup -> Add user
>>> > > > via the drop down menu If got an
>>> > Internal error.
>>> > > >
>>> > > > In the openmeetings.log file I found
>>> > the following
>>> > > > error messages:
>>> > > > http://pastebin.com/q0h1aR3G
>>> > > >
>>> > > > Thanks,
>>> > > > Michael
>>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: test of branch 3.0.3 (build 29)
Posted by Maxim Solodovnik <so...@gmail.com>.
fixed in #30
On 18 June 2014 20:35, Peter Dähn <da...@vcrp.de> wrote:
> Hi there,
>
> we also use postgres...
>
> I realized this a few days ago... OM starts with used perm gen space ~65M
> at the 12th of june...
>
> and it grows every day... see attached screenshot
>
> I think I need to observe this for a while...
>
> Greetings Peter
>
> Am 18.06.2014 11:39, schrieb Maxim Solodovnik:
>
> reproducible in postgres :(
> hate such iissues :(
>
>
> On 18 June 2014 16:29, Michael Wuttke <mi...@beuth-hochschule.de>
> wrote:
>
>> Hello Maxim,
>>
>> 2) I will test it tomorrow again with a fresh mysql install, ok?
>> 3) I added -XX:MaxPermSize=256M to the JAVA_OPTS= in th ./red5.sh script
>> in line 31 and now om works as expected without any outofmemory errors.
>> ;-)
>>
>> Tnaks,
>> Michael
>>
>> Am 18.06.2014 11:13, schrieb Maxim Solodovnik:
>> > 2) works for me
>> > very weird, not sure what else can be done :(
>> >
>> >
>> > On 18 June 2014 16:03, Maxim Solodovnik <solomax666@gmail.com
>> > <ma...@gmail.com>> wrote:
>> >
>> > 2) will check
>> > 3) you can use it like this:
>> >
>> > JAVA_OPTS=-XX:MaxPermSize=256M ./red5.sh
>> >
>> >
>> > On 18 June 2014 16:00, Michael Wuttke
>> > <michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>> wrote:
>> >
>> > Hello Maxim,
>> >
>> > what a quick response, great! ;-)
>> >
>> > 1) I've tested it and it works as expected. ;-) (my test
>> > scenario see my
>> > last mail)
>> >
>> > 2) My steps:
>> > I. I log in as an OM admin at the OM GUI (works as expected).
>> > II. Administration -> Users -> adding & selecting the user
>> 'soap' ->
>> > User details -> Usergroup -> select usergroup 'webbase' -> click
>> > button
>> > Save (works as expected).
>> > III. Administration -> Usergroups -> new record -> enter a Name
>> > for a
>> > new usergroup 'soap' -> click button Save (works as expected).
>> > IV. select usergroup 'soap' on the left site of the page
>> > Administration
>> > -> Usergroups (works as expected).
>> > V. Select the user 'soap' in the middle part Usergroup -> Add
>> > user ->
>> > select user 'soap' from the drop down menu caused for me an
>> > Internal error.
>> >
>> > 3) I tested ~/red5/red5-highperf.sh but I've got the same error
>> > message
>> > after a while.
>> >
>> > "*|-XX:MaxPermSize=256M|*" is an JVM option for the red5.sh
>> > start script?
>> >
>> > Thanks,
>> > Michael
>> >
>> > Am 17.06.2014 20:06, schrieb Maxim Solodovnik:
>> > > 1) fixed
>> > > 2) I cannot reproduce :( can you provide as detailed steps as
>> > possible?
>> > > 3) you can run "highperf" or add PermGen memory using
>> > > "*|-XX:MaxPermSize=256M|*"
>> > >
>> > >
>> > > On 17 June 2014 22:15, Michael Wuttke
>> > > <michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>
>> > > <mailto:michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>>> wrote:
>> > >
>> > > Hello,
>> > >
>> > > I've tested the latest om build with the following
>> scenario:
>> > >
>> > > - om server:
>> > > * OS: debian wheezy
>> > > * database server: postgresql (version 9.3)
>> > > * OM version: branch 3.0.3 (build 28)
>> > > * a clean install via cliadmin with
>> > > ./admin.sh -i -v -file backup.zip -tz Europe/Berlin --drop
>> > > --skip-default-rooms --db-type postgresql --db-host
>> > somehost --db-name
>> > > somename --db-user someuser --db-pass somepass
>> > >
>> > > - moodle server:
>> > > * OS: debian wheezy
>> > > * database server: postgresql (version 9.1)
>> > > * Moodle version: 2.7+ (build: 20140613) -> not a
>> > clean install
>> > > * om moodle plugin: version 1.7.1 - (build 2014051301)
>> > >
>> > > - user client:
>> > > * OS: ubuntu 14.04 LTS (trusty tahr)
>> > > * browser: FF 30.0 & Opera 12.16.1860
>> > >
>> > > Adding in OM a 'SOAP' user to create, modify or delete OM
>> > rooms via
>> > > moodle is not a problem, or changing the settings of a OM
>> > user.
>> > >
>> > > But some issues occurred during the test.
>> > >
>> > > 1. I still get the following error message on the moodle
>> > server, when I
>> > > try to enter a new created om room (an interview room in
>> > this case; I
>> > > created a conference, a webinar and a interview room):
>> > >
>> > > Can not find data record in database table
>> course_modules.
>> > >
>> > > Debug info: SELECT id,course FROM {course_modules}
>> > WHERE id = ?
>> > > [array (
>> > > 0 => '6',
>> > > )]
>> > > Error code: invalidrecord
>> > >
>> > > Stack trace:
>> > > line 1451 of /lib/dml/moodle_database.php:
>> > > dml_missing_record_exception thrown
>> > > line 1427 of /lib/dml/moodle_database.php: call
>> to
>> > > moodle_database->get_record_select()
>> > > line 7088 of /lib/accesslib.php: call to
>> > > moodle_database->get_record()
>> > > line 61 of /mod/openmeetings/view.php: call to
>> > > context_module::instance()
>> > >
>> > > 2. When I try to add a user to a group via the OM GUI:
>> > Administration ->
>> > > Usergroups -> new record -> enter a Name for a new
>> > usergroup - this
>> > > works. But if I try to add a user to this new usergroup
>> > via the drop
>> > > down menu Add user and try then to select a user, I will
>> > get an Internal
>> > > error.
>> > >
>> > > Please see the pastebin entry for the error message:
>> > > http://pastebin.com/ddm93jbS
>> > >
>> > > 3. Often I get a OutOfMemoryError: PermGen space in the
>> > red5.log
>> > >
>> > > Please see also the pastebin entry for this error message:
>> > > http://pastebin.com/SL5gXDGw
>> > >
>> > > Thanks,
>> > > Michael
>> > >
>> > > Am 17.06.2014 08:25, schrieb Maxim Solodovnik:
>> > > > Regarding 1
>> > > > Could you please provide any repo steps?
>> > > >
>> > > >
>> > > > On 16 June 2014 19:03, Vasiliy Degtyarev
>> > <vasya@unipro.ru <ma...@unipro.ru>
>> > > <mailto:vasya@unipro.ru <ma...@unipro.ru>>
>> > > > <mailto:vasya@unipro.ru <ma...@unipro.ru>
>> > <mailto:vasya@unipro.ru <ma...@unipro.ru>>>> wrote:
>> > > >
>> > > > Hello Michael,
>> > > >
>> > > > I have fixed second error for the 3.0.3 branch.
>> > > >
>> > > > Vasiliy.
>> > > >
>> > > >
>> > > > On 16.06.2014 17:28, Michael Wuttke wrote:
>> > > >
>> > > > Hello Maxim,
>> > > >
>> > > > I've tested the latest om build with the
>> > following scenario:
>> > > >
>> > > > - om server:
>> > > > * OS: debian wheezy
>> > > > * db server: postgresql (version 9.3) ->
>> > a clean
>> > > install
>> > > > * OM version: branch 3.0.3 (build 27)
>> > > >
>> > > > - om server:
>> > > > * OS: debian wheezy
>> > > > * db server: postgresql (version 9.1)
>> > > > * Moodle version: 2.7+ (build:
>> 20140605) and
>> > > > + om moodle plugin: version 1.7.1 -
>> > (build 2014051301)
>> > > >
>> > > > - user client:
>> > > > * OS: ubuntu 14.04 LTS (trusty tahr)
>> > > > * browser: FF 30.0 & Opera 12.16.1860
>> > > >
>> > > > Adding in OM a 'SOAP' user to create, modify or
>> > delete OM
>> > > rooms via
>> > > > moodle was not the problem. I also could change
>> the
>> > > settings of a OM
>> > > > user (f.e. add or change the
>> > usergroup/organisation). The
>> > > network
>> > > > testing works now. Thanks. ;-)
>> > > >
>> > > > But two issues occurred during this test.
>> > > >
>> > > > 1. Sometimes I've got the following error
>> > message on the
>> > > moodle
>> > > > server,
>> > > > when I tried to enter a new room (an interview
>> > room in
>> > > this case):
>> > > >
>> > > > Can not find data record in database table
>> > course_modules.
>> > > >
>> > > > Debug info: SELECT id,course FROM
>> > {course_modules} WHERE
>> > > id = ?
>> > > > [array (
>> > > > 0 => '6',
>> > > > )]
>> > > > Error code: invalidrecord
>> > > >
>> > > > Stack trace:
>> > > > line 1451 of /lib/dml/moodle_database.php:
>> > > > dml_missing_record_exception thrown
>> > > > line 1427 of /lib/dml/moodle_database.php:
>> > call to
>> > > > moodle_database->get_record___select()
>> > > > line 7088 of /lib/accesslib.php: call to
>> > > > moodle_database->get_record()
>> > > > line 61 of /mod/openmeetings/view.php:
>> call to
>> > > > context_module::instance()
>> > > >
>> > > > 2. When I tried to change the OM
>> > settings/configuration
>> > > via the
>> > > > OM GUI:
>> > > > Administration -> Configuration -> selecting the
>> > id 54
>> > > > (redirect.url.for.external.__users) -> entering
>> > the Value
>> > > > 'mymoodleurl'
>> > > > and tried to save this entry, I've got an
>> > Internal error.
>> > > >
>> > > > See pastebin for the error messages:
>> > > > http://pastebin.com/hY15zvqv
>> > > >
>> > > > Thanks,
>> > > > Michael
>> > > >
>> > > > Am 14.06.2014 10:53, schrieb Maxim Solodovnik:
>> > > >
>> > > > Thanks for the detailed report!
>> > > > build #27 should address first issue
>> > > >
>> > > > second was not reproducible here, could you
>> > please
>> > > re-check?
>> > > >
>> > > >
>> > > > On 13 June 2014 19:33, Michael Wuttke
>> > > > <michael.wuttke@beuth-__hochschule.de
>> > <ma...@beuth-__hochschule.de>
>> > > <mailto:michael.wuttke@beuth-__hochschule.de
>> > <ma...@beuth-__hochschule.de>>
>> > > > <mailto:michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>
>> > > <mailto:michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>>>
>> > > > <mailto:
>> michael.wuttke@beuth-__hochschule.de
>> > <ma...@beuth-__hochschule.de>
>> > > <mailto:michael.wuttke@beuth-__hochschule.de
>> > <ma...@beuth-__hochschule.de>>
>> > > > <mailto:michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>
>> > > <mailto:michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>>>>> wrote:
>> > > >
>> > > > Hello Maxim,
>> > > >
>> > > > I've tested the branch 3.0.3 (build 26)
>> > now with a
>> > > > clean postgresql
>> > > > install. Two issues occurred during
>> > this test.
>> > > >
>> > > > 1. Adding a 'SOAP' user to create OM
>> > rooms via moodle
>> > > > (version 2.7 and
>> > > > om moodle plugin version 1.7.1 - build
>> > 2014051301) is
>> > > > not a problem,
>> > > > like I tested yesterday. But to open
>> > the new
>> > > created OM
>> > > > room via moodle
>> > > > doesn't work. In the openmeetings.log
>> > file I
>> > > found the
>> > > > following error
>> > > > messages:
>> > > > http://pastebin.com/rpTfhJcW
>> > > >
>> > > > 2. When I tried to add the new soap
>> > user to a
>> > > > organisation via the OM
>> > > > GUI: Administration -> Usergroups ->
>> > selecting the
>> > > > usergroup -> Add user
>> > > > via the drop down menu If got an
>> > Internal error.
>> > > >
>> > > > In the openmeetings.log file I found
>> > the following
>> > > > error messages:
>> > > > http://pastebin.com/q0h1aR3G
>> > > >
>> > > > Thanks,
>> > > > Michael
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>
>
--
WBR
Maxim aka solomax
Re: test of branch 3.0.3 (build 29)
Posted by Peter Dähn <da...@vcrp.de>.
Hi there,
we also use postgres...
I realized this a few days ago... OM starts with used perm gen space
~65M at the 12th of june...
and it grows every day... see attached screenshot
I think I need to observe this for a while...
Greetings Peter
Am 18.06.2014 11:39, schrieb Maxim Solodovnik:
> reproducible in postgres :(
> hate such iissues :(
>
>
> On 18 June 2014 16:29, Michael Wuttke
> <michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>> wrote:
>
> Hello Maxim,
>
> 2) I will test it tomorrow again with a fresh mysql install, ok?
> 3) I added -XX:MaxPermSize=256M to the JAVA_OPTS= in th ./red5.sh
> script
> in line 31 and now om works as expected without any outofmemory
> errors. ;-)
>
> Tnaks,
> Michael
>
> Am 18.06.2014 11:13, schrieb Maxim Solodovnik:
> > 2) works for me
> > very weird, not sure what else can be done :(
> >
> >
> > On 18 June 2014 16:03, Maxim Solodovnik <solomax666@gmail.com
> <ma...@gmail.com>
> > <mailto:solomax666@gmail.com <ma...@gmail.com>>> wrote:
> >
> > 2) will check
> > 3) you can use it like this:
> >
> > JAVA_OPTS=-XX:MaxPermSize=256M ./red5.sh
> >
> >
> > On 18 June 2014 16:00, Michael Wuttke
> > <michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>> wrote:
> >
> > Hello Maxim,
> >
> > what a quick response, great! ;-)
> >
> > 1) I've tested it and it works as expected. ;-) (my test
> > scenario see my
> > last mail)
> >
> > 2) My steps:
> > I. I log in as an OM admin at the OM GUI (works as
> expected).
> > II. Administration -> Users -> adding & selecting the
> user 'soap' ->
> > User details -> Usergroup -> select usergroup 'webbase'
> -> click
> > button
> > Save (works as expected).
> > III. Administration -> Usergroups -> new record -> enter
> a Name
> > for a
> > new usergroup 'soap' -> click button Save (works as
> expected).
> > IV. select usergroup 'soap' on the left site of the page
> > Administration
> > -> Usergroups (works as expected).
> > V. Select the user 'soap' in the middle part Usergroup
> -> Add
> > user ->
> > select user 'soap' from the drop down menu caused for me an
> > Internal error.
> >
> > 3) I tested ~/red5/red5-highperf.sh but I've got the
> same error
> > message
> > after a while.
> >
> > "*|-XX:MaxPermSize=256M|*" is an JVM option for the red5.sh
> > start script?
> >
> > Thanks,
> > Michael
> >
> > Am 17.06.2014 20:06, schrieb Maxim Solodovnik:
> > > 1) fixed
> > > 2) I cannot reproduce :( can you provide as detailed
> steps as
> > possible?
> > > 3) you can run "highperf" or add PermGen memory using
> > > "*|-XX:MaxPermSize=256M|*"
> > >
> > >
> > > On 17 June 2014 22:15, Michael Wuttke
> > > <michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>
> > > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>>> wrote:
> > >
> > > Hello,
> > >
> > > I've tested the latest om build with the following
> scenario:
> > >
> > > - om server:
> > > * OS: debian wheezy
> > > * database server: postgresql (version 9.3)
> > > * OM version: branch 3.0.3 (build 28)
> > > * a clean install via cliadmin with
> > > ./admin.sh -i -v -file backup.zip -tz
> Europe/Berlin --drop
> > > --skip-default-rooms --db-type postgresql --db-host
> > somehost --db-name
> > > somename --db-user someuser --db-pass somepass
> > >
> > > - moodle server:
> > > * OS: debian wheezy
> > > * database server: postgresql (version 9.1)
> > > * Moodle version: 2.7+ (build: 20140613) -> not a
> > clean install
> > > * om moodle plugin: version 1.7.1 - (build
> 2014051301)
> > >
> > > - user client:
> > > * OS: ubuntu 14.04 LTS (trusty tahr)
> > > * browser: FF 30.0 & Opera 12.16.1860
> > >
> > > Adding in OM a 'SOAP' user to create, modify or
> delete OM
> > rooms via
> > > moodle is not a problem, or changing the settings
> of a OM
> > user.
> > >
> > > But some issues occurred during the test.
> > >
> > > 1. I still get the following error message on the
> moodle
> > server, when I
> > > try to enter a new created om room (an interview
> room in
> > this case; I
> > > created a conference, a webinar and a interview room):
> > >
> > > Can not find data record in database table
> course_modules.
> > >
> > > Debug info: SELECT id,course FROM {course_modules}
> > WHERE id = ?
> > > [array (
> > > 0 => '6',
> > > )]
> > > Error code: invalidrecord
> > >
> > > Stack trace:
> > > line 1451 of /lib/dml/moodle_database.php:
> > > dml_missing_record_exception thrown
> > > line 1427 of
> /lib/dml/moodle_database.php: call to
> > > moodle_database->get_record_select()
> > > line 7088 of /lib/accesslib.php: call to
> > > moodle_database->get_record()
> > > line 61 of /mod/openmeetings/view.php:
> call to
> > > context_module::instance()
> > >
> > > 2. When I try to add a user to a group via the OM GUI:
> > Administration ->
> > > Usergroups -> new record -> enter a Name for a new
> > usergroup - this
> > > works. But if I try to add a user to this new
> usergroup
> > via the drop
> > > down menu Add user and try then to select a user,
> I will
> > get an Internal
> > > error.
> > >
> > > Please see the pastebin entry for the error message:
> > > http://pastebin.com/ddm93jbS
> > >
> > > 3. Often I get a OutOfMemoryError: PermGen space
> in the
> > red5.log
> > >
> > > Please see also the pastebin entry for this error
> message:
> > > http://pastebin.com/SL5gXDGw
> > >
> > > Thanks,
> > > Michael
> > >
> > > Am 17.06.2014 08:25, schrieb Maxim Solodovnik:
> > > > Regarding 1
> > > > Could you please provide any repo steps?
> > > >
> > > >
> > > > On 16 June 2014 19:03, Vasiliy Degtyarev
> > <vasya@unipro.ru <ma...@unipro.ru>
> <mailto:vasya@unipro.ru <ma...@unipro.ru>>
> > > <mailto:vasya@unipro.ru <ma...@unipro.ru>
> <mailto:vasya@unipro.ru <ma...@unipro.ru>>>
> > > > <mailto:vasya@unipro.ru <ma...@unipro.ru>
> <mailto:vasya@unipro.ru <ma...@unipro.ru>>
> > <mailto:vasya@unipro.ru <ma...@unipro.ru>
> <mailto:vasya@unipro.ru <ma...@unipro.ru>>>>> wrote:
> > > >
> > > > Hello Michael,
> > > >
> > > > I have fixed second error for the 3.0.3 branch.
> > > >
> > > > Vasiliy.
> > > >
> > > >
> > > > On 16.06.2014 17:28, Michael Wuttke wrote:
> > > >
> > > > Hello Maxim,
> > > >
> > > > I've tested the latest om build with the
> > following scenario:
> > > >
> > > > - om server:
> > > > * OS: debian wheezy
> > > > * db server: postgresql (version
> 9.3) ->
> > a clean
> > > install
> > > > * OM version: branch 3.0.3
> (build 27)
> > > >
> > > > - om server:
> > > > * OS: debian wheezy
> > > > * db server: postgresql (version
> 9.1)
> > > > * Moodle version: 2.7+ (build:
> 20140605) and
> > > > + om moodle plugin: version 1.7.1 -
> > (build 2014051301)
> > > >
> > > > - user client:
> > > > * OS: ubuntu 14.04 LTS (trusty tahr)
> > > > * browser: FF 30.0 & Opera
> 12.16.1860
> > > >
> > > > Adding in OM a 'SOAP' user to create,
> modify or
> > delete OM
> > > rooms via
> > > > moodle was not the problem. I also could
> change the
> > > settings of a OM
> > > > user (f.e. add or change the
> > usergroup/organisation). The
> > > network
> > > > testing works now. Thanks. ;-)
> > > >
> > > > But two issues occurred during this test.
> > > >
> > > > 1. Sometimes I've got the following error
> > message on the
> > > moodle
> > > > server,
> > > > when I tried to enter a new room (an
> interview
> > room in
> > > this case):
> > > >
> > > > Can not find data record in database table
> > course_modules.
> > > >
> > > > Debug info: SELECT id,course FROM
> > {course_modules} WHERE
> > > id = ?
> > > > [array (
> > > > 0 => '6',
> > > > )]
> > > > Error code: invalidrecord
> > > >
> > > > Stack trace:
> > > > line 1451 of
> /lib/dml/moodle_database.php:
> > > > dml_missing_record_exception thrown
> > > > line 1427 of
> /lib/dml/moodle_database.php:
> > call to
> > > > moodle_database->get_record___select()
> > > > line 7088 of /lib/accesslib.php:
> call to
> > > > moodle_database->get_record()
> > > > line 61 of
> /mod/openmeetings/view.php: call to
> > > > context_module::instance()
> > > >
> > > > 2. When I tried to change the OM
> > settings/configuration
> > > via the
> > > > OM GUI:
> > > > Administration -> Configuration ->
> selecting the
> > id 54
> > > > (redirect.url.for.external.__users) -> entering
> > the Value
> > > > 'mymoodleurl'
> > > > and tried to save this entry, I've got an
> > Internal error.
> > > >
> > > > See pastebin for the error messages:
> > > > http://pastebin.com/hY15zvqv
> > > >
> > > > Thanks,
> > > > Michael
> > > >
> > > > Am 14.06.2014 10:53, schrieb Maxim
> Solodovnik:
> > > >
> > > > Thanks for the detailed report!
> > > > build #27 should address first issue
> > > >
> > > > second was not reproducible here,
> could you
> > please
> > > re-check?
> > > >
> > > >
> > > > On 13 June 2014 19:33, Michael Wuttke
> > > >
> <michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-__hochschule.de>
> > <mailto:michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-__hochschule.de>>
> > > <mailto:michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-__hochschule.de>
> > <mailto:michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-__hochschule.de>>>
> > > >
> <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>
> > > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>>>
> > > >
> <mailto:michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-__hochschule.de>
> > <mailto:michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-__hochschule.de>>
> > > <mailto:michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-__hochschule.de>
> > <mailto:michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-__hochschule.de>>>
> > > >
> <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>
> > > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>>>>> wrote:
> > > >
> > > > Hello Maxim,
> > > >
> > > > I've tested the branch 3.0.3
> (build 26)
> > now with a
> > > > clean postgresql
> > > > install. Two issues occurred during
> > this test.
> > > >
> > > > 1. Adding a 'SOAP' user to
> create OM
> > rooms via moodle
> > > > (version 2.7 and
> > > > om moodle plugin version 1.7.1
> - build
> > 2014051301) is
> > > > not a problem,
> > > > like I tested yesterday. But to
> open
> > the new
> > > created OM
> > > > room via moodle
> > > > doesn't work. In the
> openmeetings.log
> > file I
> > > found the
> > > > following error
> > > > messages:
> > > > http://pastebin.com/rpTfhJcW
> > > >
> > > > 2. When I tried to add the new soap
> > user to a
> > > > organisation via the OM
> > > > GUI: Administration ->
> Usergroups ->
> > selecting the
> > > > usergroup -> Add user
> > > > via the drop down menu If got an
> > Internal error.
> > > >
> > > > In the openmeetings.log file I
> found
> > the following
> > > > error messages:
> > > > http://pastebin.com/q0h1aR3G
> > > >
> > > > Thanks,
> > > > Michael
>
>
>
>
> --
> WBR
> Maxim aka solomax
Re: test of branch 3.0.3 (build 29)
Posted by Maxim Solodovnik <so...@gmail.com>.
its great ....
but seems to be too strict :)
On 18 June 2014 16:47, Michael Wuttke <mi...@beuth-hochschule.de>
wrote:
> Come on! Postgres is not as bad as all that! ;-)
>
> Am 18.06.2014 11:39, schrieb Maxim Solodovnik:
> > hate such iissues :(
> >
>
--
WBR
Maxim aka solomax
Re: test of branch 3.0.3 (build 29)
Posted by Michael Wuttke <mi...@beuth-hochschule.de>.
Come on! Postgres is not as bad as all that! ;-)
Am 18.06.2014 11:39, schrieb Maxim Solodovnik:
> hate such iissues :(
>
Re: test of branch 3.0.3 (build 29)
Posted by Maxim Solodovnik <so...@gmail.com>.
seems to fond this one
please wait for build #30
On 18 June 2014 16:39, Maxim Solodovnik <so...@gmail.com> wrote:
> reproducible in postgres :(
> hate such iissues :(
>
>
> On 18 June 2014 16:29, Michael Wuttke <mi...@beuth-hochschule.de>
> wrote:
>
>> Hello Maxim,
>>
>> 2) I will test it tomorrow again with a fresh mysql install, ok?
>> 3) I added -XX:MaxPermSize=256M to the JAVA_OPTS= in th ./red5.sh script
>> in line 31 and now om works as expected without any outofmemory errors.
>> ;-)
>>
>> Tnaks,
>> Michael
>>
>> Am 18.06.2014 11:13, schrieb Maxim Solodovnik:
>> > 2) works for me
>> > very weird, not sure what else can be done :(
>> >
>> >
>> > On 18 June 2014 16:03, Maxim Solodovnik <solomax666@gmail.com
>> > <ma...@gmail.com>> wrote:
>> >
>> > 2) will check
>> > 3) you can use it like this:
>> >
>> > JAVA_OPTS=-XX:MaxPermSize=256M ./red5.sh
>> >
>> >
>> > On 18 June 2014 16:00, Michael Wuttke
>> > <michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>> wrote:
>> >
>> > Hello Maxim,
>> >
>> > what a quick response, great! ;-)
>> >
>> > 1) I've tested it and it works as expected. ;-) (my test
>> > scenario see my
>> > last mail)
>> >
>> > 2) My steps:
>> > I. I log in as an OM admin at the OM GUI (works as expected).
>> > II. Administration -> Users -> adding & selecting the user
>> 'soap' ->
>> > User details -> Usergroup -> select usergroup 'webbase' -> click
>> > button
>> > Save (works as expected).
>> > III. Administration -> Usergroups -> new record -> enter a Name
>> > for a
>> > new usergroup 'soap' -> click button Save (works as expected).
>> > IV. select usergroup 'soap' on the left site of the page
>> > Administration
>> > -> Usergroups (works as expected).
>> > V. Select the user 'soap' in the middle part Usergroup -> Add
>> > user ->
>> > select user 'soap' from the drop down menu caused for me an
>> > Internal error.
>> >
>> > 3) I tested ~/red5/red5-highperf.sh but I've got the same error
>> > message
>> > after a while.
>> >
>> > "*|-XX:MaxPermSize=256M|*" is an JVM option for the red5.sh
>> > start script?
>> >
>> > Thanks,
>> > Michael
>> >
>> > Am 17.06.2014 20:06, schrieb Maxim Solodovnik:
>> > > 1) fixed
>> > > 2) I cannot reproduce :( can you provide as detailed steps as
>> > possible?
>> > > 3) you can run "highperf" or add PermGen memory using
>> > > "*|-XX:MaxPermSize=256M|*"
>> > >
>> > >
>> > > On 17 June 2014 22:15, Michael Wuttke
>> > > <michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>
>> > > <mailto:michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>>> wrote:
>> > >
>> > > Hello,
>> > >
>> > > I've tested the latest om build with the following
>> scenario:
>> > >
>> > > - om server:
>> > > * OS: debian wheezy
>> > > * database server: postgresql (version 9.3)
>> > > * OM version: branch 3.0.3 (build 28)
>> > > * a clean install via cliadmin with
>> > > ./admin.sh -i -v -file backup.zip -tz Europe/Berlin --drop
>> > > --skip-default-rooms --db-type postgresql --db-host
>> > somehost --db-name
>> > > somename --db-user someuser --db-pass somepass
>> > >
>> > > - moodle server:
>> > > * OS: debian wheezy
>> > > * database server: postgresql (version 9.1)
>> > > * Moodle version: 2.7+ (build: 20140613) -> not a
>> > clean install
>> > > * om moodle plugin: version 1.7.1 - (build 2014051301)
>> > >
>> > > - user client:
>> > > * OS: ubuntu 14.04 LTS (trusty tahr)
>> > > * browser: FF 30.0 & Opera 12.16.1860
>> > >
>> > > Adding in OM a 'SOAP' user to create, modify or delete OM
>> > rooms via
>> > > moodle is not a problem, or changing the settings of a OM
>> > user.
>> > >
>> > > But some issues occurred during the test.
>> > >
>> > > 1. I still get the following error message on the moodle
>> > server, when I
>> > > try to enter a new created om room (an interview room in
>> > this case; I
>> > > created a conference, a webinar and a interview room):
>> > >
>> > > Can not find data record in database table
>> course_modules.
>> > >
>> > > Debug info: SELECT id,course FROM {course_modules}
>> > WHERE id = ?
>> > > [array (
>> > > 0 => '6',
>> > > )]
>> > > Error code: invalidrecord
>> > >
>> > > Stack trace:
>> > > line 1451 of /lib/dml/moodle_database.php:
>> > > dml_missing_record_exception thrown
>> > > line 1427 of /lib/dml/moodle_database.php: call
>> to
>> > > moodle_database->get_record_select()
>> > > line 7088 of /lib/accesslib.php: call to
>> > > moodle_database->get_record()
>> > > line 61 of /mod/openmeetings/view.php: call to
>> > > context_module::instance()
>> > >
>> > > 2. When I try to add a user to a group via the OM GUI:
>> > Administration ->
>> > > Usergroups -> new record -> enter a Name for a new
>> > usergroup - this
>> > > works. But if I try to add a user to this new usergroup
>> > via the drop
>> > > down menu Add user and try then to select a user, I will
>> > get an Internal
>> > > error.
>> > >
>> > > Please see the pastebin entry for the error message:
>> > > http://pastebin.com/ddm93jbS
>> > >
>> > > 3. Often I get a OutOfMemoryError: PermGen space in the
>> > red5.log
>> > >
>> > > Please see also the pastebin entry for this error message:
>> > > http://pastebin.com/SL5gXDGw
>> > >
>> > > Thanks,
>> > > Michael
>> > >
>> > > Am 17.06.2014 08:25, schrieb Maxim Solodovnik:
>> > > > Regarding 1
>> > > > Could you please provide any repo steps?
>> > > >
>> > > >
>> > > > On 16 June 2014 19:03, Vasiliy Degtyarev
>> > <vasya@unipro.ru <ma...@unipro.ru>
>> > > <mailto:vasya@unipro.ru <ma...@unipro.ru>>
>> > > > <mailto:vasya@unipro.ru <ma...@unipro.ru>
>> > <mailto:vasya@unipro.ru <ma...@unipro.ru>>>> wrote:
>> > > >
>> > > > Hello Michael,
>> > > >
>> > > > I have fixed second error for the 3.0.3 branch.
>> > > >
>> > > > Vasiliy.
>> > > >
>> > > >
>> > > > On 16.06.2014 17:28, Michael Wuttke wrote:
>> > > >
>> > > > Hello Maxim,
>> > > >
>> > > > I've tested the latest om build with the
>> > following scenario:
>> > > >
>> > > > - om server:
>> > > > * OS: debian wheezy
>> > > > * db server: postgresql (version 9.3) ->
>> > a clean
>> > > install
>> > > > * OM version: branch 3.0.3 (build 27)
>> > > >
>> > > > - om server:
>> > > > * OS: debian wheezy
>> > > > * db server: postgresql (version 9.1)
>> > > > * Moodle version: 2.7+ (build:
>> 20140605) and
>> > > > + om moodle plugin: version 1.7.1 -
>> > (build 2014051301)
>> > > >
>> > > > - user client:
>> > > > * OS: ubuntu 14.04 LTS (trusty tahr)
>> > > > * browser: FF 30.0 & Opera 12.16.1860
>> > > >
>> > > > Adding in OM a 'SOAP' user to create, modify or
>> > delete OM
>> > > rooms via
>> > > > moodle was not the problem. I also could change
>> the
>> > > settings of a OM
>> > > > user (f.e. add or change the
>> > usergroup/organisation). The
>> > > network
>> > > > testing works now. Thanks. ;-)
>> > > >
>> > > > But two issues occurred during this test.
>> > > >
>> > > > 1. Sometimes I've got the following error
>> > message on the
>> > > moodle
>> > > > server,
>> > > > when I tried to enter a new room (an interview
>> > room in
>> > > this case):
>> > > >
>> > > > Can not find data record in database table
>> > course_modules.
>> > > >
>> > > > Debug info: SELECT id,course FROM
>> > {course_modules} WHERE
>> > > id = ?
>> > > > [array (
>> > > > 0 => '6',
>> > > > )]
>> > > > Error code: invalidrecord
>> > > >
>> > > > Stack trace:
>> > > > line 1451 of /lib/dml/moodle_database.php:
>> > > > dml_missing_record_exception thrown
>> > > > line 1427 of /lib/dml/moodle_database.php:
>> > call to
>> > > > moodle_database->get_record___select()
>> > > > line 7088 of /lib/accesslib.php: call to
>> > > > moodle_database->get_record()
>> > > > line 61 of /mod/openmeetings/view.php:
>> call to
>> > > > context_module::instance()
>> > > >
>> > > > 2. When I tried to change the OM
>> > settings/configuration
>> > > via the
>> > > > OM GUI:
>> > > > Administration -> Configuration -> selecting the
>> > id 54
>> > > > (redirect.url.for.external.__users) -> entering
>> > the Value
>> > > > 'mymoodleurl'
>> > > > and tried to save this entry, I've got an
>> > Internal error.
>> > > >
>> > > > See pastebin for the error messages:
>> > > > http://pastebin.com/hY15zvqv
>> > > >
>> > > > Thanks,
>> > > > Michael
>> > > >
>> > > > Am 14.06.2014 10:53, schrieb Maxim Solodovnik:
>> > > >
>> > > > Thanks for the detailed report!
>> > > > build #27 should address first issue
>> > > >
>> > > > second was not reproducible here, could you
>> > please
>> > > re-check?
>> > > >
>> > > >
>> > > > On 13 June 2014 19:33, Michael Wuttke
>> > > > <michael.wuttke@beuth-__hochschule.de
>> > <ma...@beuth-__hochschule.de>
>> > > <mailto:michael.wuttke@beuth-__hochschule.de
>> > <ma...@beuth-__hochschule.de>>
>> > > > <mailto:michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>
>> > > <mailto:michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>>>
>> > > > <mailto:
>> michael.wuttke@beuth-__hochschule.de
>> > <ma...@beuth-__hochschule.de>
>> > > <mailto:michael.wuttke@beuth-__hochschule.de
>> > <ma...@beuth-__hochschule.de>>
>> > > > <mailto:michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>
>> > > <mailto:michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>>>>> wrote:
>> > > >
>> > > > Hello Maxim,
>> > > >
>> > > > I've tested the branch 3.0.3 (build 26)
>> > now with a
>> > > > clean postgresql
>> > > > install. Two issues occurred during
>> > this test.
>> > > >
>> > > > 1. Adding a 'SOAP' user to create OM
>> > rooms via moodle
>> > > > (version 2.7 and
>> > > > om moodle plugin version 1.7.1 - build
>> > 2014051301) is
>> > > > not a problem,
>> > > > like I tested yesterday. But to open
>> > the new
>> > > created OM
>> > > > room via moodle
>> > > > doesn't work. In the openmeetings.log
>> > file I
>> > > found the
>> > > > following error
>> > > > messages:
>> > > > http://pastebin.com/rpTfhJcW
>> > > >
>> > > > 2. When I tried to add the new soap
>> > user to a
>> > > > organisation via the OM
>> > > > GUI: Administration -> Usergroups ->
>> > selecting the
>> > > > usergroup -> Add user
>> > > > via the drop down menu If got an
>> > Internal error.
>> > > >
>> > > > In the openmeetings.log file I found
>> > the following
>> > > > error messages:
>> > > > http://pastebin.com/q0h1aR3G
>> > > >
>> > > > Thanks,
>> > > > Michael
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: test of branch 3.0.3 (build 29)
Posted by Maxim Solodovnik <so...@gmail.com>.
reproducible in postgres :(
hate such iissues :(
On 18 June 2014 16:29, Michael Wuttke <mi...@beuth-hochschule.de>
wrote:
> Hello Maxim,
>
> 2) I will test it tomorrow again with a fresh mysql install, ok?
> 3) I added -XX:MaxPermSize=256M to the JAVA_OPTS= in th ./red5.sh script
> in line 31 and now om works as expected without any outofmemory errors. ;-)
>
> Tnaks,
> Michael
>
> Am 18.06.2014 11:13, schrieb Maxim Solodovnik:
> > 2) works for me
> > very weird, not sure what else can be done :(
> >
> >
> > On 18 June 2014 16:03, Maxim Solodovnik <solomax666@gmail.com
> > <ma...@gmail.com>> wrote:
> >
> > 2) will check
> > 3) you can use it like this:
> >
> > JAVA_OPTS=-XX:MaxPermSize=256M ./red5.sh
> >
> >
> > On 18 June 2014 16:00, Michael Wuttke
> > <michael.wuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>> wrote:
> >
> > Hello Maxim,
> >
> > what a quick response, great! ;-)
> >
> > 1) I've tested it and it works as expected. ;-) (my test
> > scenario see my
> > last mail)
> >
> > 2) My steps:
> > I. I log in as an OM admin at the OM GUI (works as expected).
> > II. Administration -> Users -> adding & selecting the user
> 'soap' ->
> > User details -> Usergroup -> select usergroup 'webbase' -> click
> > button
> > Save (works as expected).
> > III. Administration -> Usergroups -> new record -> enter a Name
> > for a
> > new usergroup 'soap' -> click button Save (works as expected).
> > IV. select usergroup 'soap' on the left site of the page
> > Administration
> > -> Usergroups (works as expected).
> > V. Select the user 'soap' in the middle part Usergroup -> Add
> > user ->
> > select user 'soap' from the drop down menu caused for me an
> > Internal error.
> >
> > 3) I tested ~/red5/red5-highperf.sh but I've got the same error
> > message
> > after a while.
> >
> > "*|-XX:MaxPermSize=256M|*" is an JVM option for the red5.sh
> > start script?
> >
> > Thanks,
> > Michael
> >
> > Am 17.06.2014 20:06, schrieb Maxim Solodovnik:
> > > 1) fixed
> > > 2) I cannot reproduce :( can you provide as detailed steps as
> > possible?
> > > 3) you can run "highperf" or add PermGen memory using
> > > "*|-XX:MaxPermSize=256M|*"
> > >
> > >
> > > On 17 June 2014 22:15, Michael Wuttke
> > > <michael.wuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>
> > > <mailto:michael.wuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>>> wrote:
> > >
> > > Hello,
> > >
> > > I've tested the latest om build with the following
> scenario:
> > >
> > > - om server:
> > > * OS: debian wheezy
> > > * database server: postgresql (version 9.3)
> > > * OM version: branch 3.0.3 (build 28)
> > > * a clean install via cliadmin with
> > > ./admin.sh -i -v -file backup.zip -tz Europe/Berlin --drop
> > > --skip-default-rooms --db-type postgresql --db-host
> > somehost --db-name
> > > somename --db-user someuser --db-pass somepass
> > >
> > > - moodle server:
> > > * OS: debian wheezy
> > > * database server: postgresql (version 9.1)
> > > * Moodle version: 2.7+ (build: 20140613) -> not a
> > clean install
> > > * om moodle plugin: version 1.7.1 - (build 2014051301)
> > >
> > > - user client:
> > > * OS: ubuntu 14.04 LTS (trusty tahr)
> > > * browser: FF 30.0 & Opera 12.16.1860
> > >
> > > Adding in OM a 'SOAP' user to create, modify or delete OM
> > rooms via
> > > moodle is not a problem, or changing the settings of a OM
> > user.
> > >
> > > But some issues occurred during the test.
> > >
> > > 1. I still get the following error message on the moodle
> > server, when I
> > > try to enter a new created om room (an interview room in
> > this case; I
> > > created a conference, a webinar and a interview room):
> > >
> > > Can not find data record in database table
> course_modules.
> > >
> > > Debug info: SELECT id,course FROM {course_modules}
> > WHERE id = ?
> > > [array (
> > > 0 => '6',
> > > )]
> > > Error code: invalidrecord
> > >
> > > Stack trace:
> > > line 1451 of /lib/dml/moodle_database.php:
> > > dml_missing_record_exception thrown
> > > line 1427 of /lib/dml/moodle_database.php: call to
> > > moodle_database->get_record_select()
> > > line 7088 of /lib/accesslib.php: call to
> > > moodle_database->get_record()
> > > line 61 of /mod/openmeetings/view.php: call to
> > > context_module::instance()
> > >
> > > 2. When I try to add a user to a group via the OM GUI:
> > Administration ->
> > > Usergroups -> new record -> enter a Name for a new
> > usergroup - this
> > > works. But if I try to add a user to this new usergroup
> > via the drop
> > > down menu Add user and try then to select a user, I will
> > get an Internal
> > > error.
> > >
> > > Please see the pastebin entry for the error message:
> > > http://pastebin.com/ddm93jbS
> > >
> > > 3. Often I get a OutOfMemoryError: PermGen space in the
> > red5.log
> > >
> > > Please see also the pastebin entry for this error message:
> > > http://pastebin.com/SL5gXDGw
> > >
> > > Thanks,
> > > Michael
> > >
> > > Am 17.06.2014 08:25, schrieb Maxim Solodovnik:
> > > > Regarding 1
> > > > Could you please provide any repo steps?
> > > >
> > > >
> > > > On 16 June 2014 19:03, Vasiliy Degtyarev
> > <vasya@unipro.ru <ma...@unipro.ru>
> > > <mailto:vasya@unipro.ru <ma...@unipro.ru>>
> > > > <mailto:vasya@unipro.ru <ma...@unipro.ru>
> > <mailto:vasya@unipro.ru <ma...@unipro.ru>>>> wrote:
> > > >
> > > > Hello Michael,
> > > >
> > > > I have fixed second error for the 3.0.3 branch.
> > > >
> > > > Vasiliy.
> > > >
> > > >
> > > > On 16.06.2014 17:28, Michael Wuttke wrote:
> > > >
> > > > Hello Maxim,
> > > >
> > > > I've tested the latest om build with the
> > following scenario:
> > > >
> > > > - om server:
> > > > * OS: debian wheezy
> > > > * db server: postgresql (version 9.3) ->
> > a clean
> > > install
> > > > * OM version: branch 3.0.3 (build 27)
> > > >
> > > > - om server:
> > > > * OS: debian wheezy
> > > > * db server: postgresql (version 9.1)
> > > > * Moodle version: 2.7+ (build: 20140605)
> and
> > > > + om moodle plugin: version 1.7.1 -
> > (build 2014051301)
> > > >
> > > > - user client:
> > > > * OS: ubuntu 14.04 LTS (trusty tahr)
> > > > * browser: FF 30.0 & Opera 12.16.1860
> > > >
> > > > Adding in OM a 'SOAP' user to create, modify or
> > delete OM
> > > rooms via
> > > > moodle was not the problem. I also could change
> the
> > > settings of a OM
> > > > user (f.e. add or change the
> > usergroup/organisation). The
> > > network
> > > > testing works now. Thanks. ;-)
> > > >
> > > > But two issues occurred during this test.
> > > >
> > > > 1. Sometimes I've got the following error
> > message on the
> > > moodle
> > > > server,
> > > > when I tried to enter a new room (an interview
> > room in
> > > this case):
> > > >
> > > > Can not find data record in database table
> > course_modules.
> > > >
> > > > Debug info: SELECT id,course FROM
> > {course_modules} WHERE
> > > id = ?
> > > > [array (
> > > > 0 => '6',
> > > > )]
> > > > Error code: invalidrecord
> > > >
> > > > Stack trace:
> > > > line 1451 of /lib/dml/moodle_database.php:
> > > > dml_missing_record_exception thrown
> > > > line 1427 of /lib/dml/moodle_database.php:
> > call to
> > > > moodle_database->get_record___select()
> > > > line 7088 of /lib/accesslib.php: call to
> > > > moodle_database->get_record()
> > > > line 61 of /mod/openmeetings/view.php: call
> to
> > > > context_module::instance()
> > > >
> > > > 2. When I tried to change the OM
> > settings/configuration
> > > via the
> > > > OM GUI:
> > > > Administration -> Configuration -> selecting the
> > id 54
> > > > (redirect.url.for.external.__users) -> entering
> > the Value
> > > > 'mymoodleurl'
> > > > and tried to save this entry, I've got an
> > Internal error.
> > > >
> > > > See pastebin for the error messages:
> > > > http://pastebin.com/hY15zvqv
> > > >
> > > > Thanks,
> > > > Michael
> > > >
> > > > Am 14.06.2014 10:53, schrieb Maxim Solodovnik:
> > > >
> > > > Thanks for the detailed report!
> > > > build #27 should address first issue
> > > >
> > > > second was not reproducible here, could you
> > please
> > > re-check?
> > > >
> > > >
> > > > On 13 June 2014 19:33, Michael Wuttke
> > > > <michael.wuttke@beuth-__hochschule.de
> > <ma...@beuth-__hochschule.de>
> > > <mailto:michael.wuttke@beuth-__hochschule.de
> > <ma...@beuth-__hochschule.de>>
> > > > <mailto:michael.wuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>
> > > <mailto:michael.wuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>>>
> > > > <mailto:michael.wuttke@beuth-__hochschule.de
> > <ma...@beuth-__hochschule.de>
> > > <mailto:michael.wuttke@beuth-__hochschule.de
> > <ma...@beuth-__hochschule.de>>
> > > > <mailto:michael.wuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>
> > > <mailto:michael.wuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>>>>> wrote:
> > > >
> > > > Hello Maxim,
> > > >
> > > > I've tested the branch 3.0.3 (build 26)
> > now with a
> > > > clean postgresql
> > > > install. Two issues occurred during
> > this test.
> > > >
> > > > 1. Adding a 'SOAP' user to create OM
> > rooms via moodle
> > > > (version 2.7 and
> > > > om moodle plugin version 1.7.1 - build
> > 2014051301) is
> > > > not a problem,
> > > > like I tested yesterday. But to open
> > the new
> > > created OM
> > > > room via moodle
> > > > doesn't work. In the openmeetings.log
> > file I
> > > found the
> > > > following error
> > > > messages:
> > > > http://pastebin.com/rpTfhJcW
> > > >
> > > > 2. When I tried to add the new soap
> > user to a
> > > > organisation via the OM
> > > > GUI: Administration -> Usergroups ->
> > selecting the
> > > > usergroup -> Add user
> > > > via the drop down menu If got an
> > Internal error.
> > > >
> > > > In the openmeetings.log file I found
> > the following
> > > > error messages:
> > > > http://pastebin.com/q0h1aR3G
> > > >
> > > > Thanks,
> > > > Michael
>
--
WBR
Maxim aka solomax
Re: test of branch 3.0.3 (build 29)
Posted by Michael Wuttke <mi...@beuth-hochschule.de>.
Hello Maxim,
2) I will test it tomorrow again with a fresh mysql install, ok?
3) I added -XX:MaxPermSize=256M to the JAVA_OPTS= in th ./red5.sh script
in line 31 and now om works as expected without any outofmemory errors. ;-)
Tnaks,
Michael
Am 18.06.2014 11:13, schrieb Maxim Solodovnik:
> 2) works for me
> very weird, not sure what else can be done :(
>
>
> On 18 June 2014 16:03, Maxim Solodovnik <solomax666@gmail.com
> <ma...@gmail.com>> wrote:
>
> 2) will check
> 3) you can use it like this:
>
> JAVA_OPTS=-XX:MaxPermSize=256M ./red5.sh
>
>
> On 18 June 2014 16:00, Michael Wuttke
> <michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>> wrote:
>
> Hello Maxim,
>
> what a quick response, great! ;-)
>
> 1) I've tested it and it works as expected. ;-) (my test
> scenario see my
> last mail)
>
> 2) My steps:
> I. I log in as an OM admin at the OM GUI (works as expected).
> II. Administration -> Users -> adding & selecting the user 'soap' ->
> User details -> Usergroup -> select usergroup 'webbase' -> click
> button
> Save (works as expected).
> III. Administration -> Usergroups -> new record -> enter a Name
> for a
> new usergroup 'soap' -> click button Save (works as expected).
> IV. select usergroup 'soap' on the left site of the page
> Administration
> -> Usergroups (works as expected).
> V. Select the user 'soap' in the middle part Usergroup -> Add
> user ->
> select user 'soap' from the drop down menu caused for me an
> Internal error.
>
> 3) I tested ~/red5/red5-highperf.sh but I've got the same error
> message
> after a while.
>
> "*|-XX:MaxPermSize=256M|*" is an JVM option for the red5.sh
> start script?
>
> Thanks,
> Michael
>
> Am 17.06.2014 20:06, schrieb Maxim Solodovnik:
> > 1) fixed
> > 2) I cannot reproduce :( can you provide as detailed steps as
> possible?
> > 3) you can run "highperf" or add PermGen memory using
> > "*|-XX:MaxPermSize=256M|*"
> >
> >
> > On 17 June 2014 22:15, Michael Wuttke
> > <michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>> wrote:
> >
> > Hello,
> >
> > I've tested the latest om build with the following scenario:
> >
> > - om server:
> > * OS: debian wheezy
> > * database server: postgresql (version 9.3)
> > * OM version: branch 3.0.3 (build 28)
> > * a clean install via cliadmin with
> > ./admin.sh -i -v -file backup.zip -tz Europe/Berlin --drop
> > --skip-default-rooms --db-type postgresql --db-host
> somehost --db-name
> > somename --db-user someuser --db-pass somepass
> >
> > - moodle server:
> > * OS: debian wheezy
> > * database server: postgresql (version 9.1)
> > * Moodle version: 2.7+ (build: 20140613) -> not a
> clean install
> > * om moodle plugin: version 1.7.1 - (build 2014051301)
> >
> > - user client:
> > * OS: ubuntu 14.04 LTS (trusty tahr)
> > * browser: FF 30.0 & Opera 12.16.1860
> >
> > Adding in OM a 'SOAP' user to create, modify or delete OM
> rooms via
> > moodle is not a problem, or changing the settings of a OM
> user.
> >
> > But some issues occurred during the test.
> >
> > 1. I still get the following error message on the moodle
> server, when I
> > try to enter a new created om room (an interview room in
> this case; I
> > created a conference, a webinar and a interview room):
> >
> > Can not find data record in database table course_modules.
> >
> > Debug info: SELECT id,course FROM {course_modules}
> WHERE id = ?
> > [array (
> > 0 => '6',
> > )]
> > Error code: invalidrecord
> >
> > Stack trace:
> > line 1451 of /lib/dml/moodle_database.php:
> > dml_missing_record_exception thrown
> > line 1427 of /lib/dml/moodle_database.php: call to
> > moodle_database->get_record_select()
> > line 7088 of /lib/accesslib.php: call to
> > moodle_database->get_record()
> > line 61 of /mod/openmeetings/view.php: call to
> > context_module::instance()
> >
> > 2. When I try to add a user to a group via the OM GUI:
> Administration ->
> > Usergroups -> new record -> enter a Name for a new
> usergroup - this
> > works. But if I try to add a user to this new usergroup
> via the drop
> > down menu Add user and try then to select a user, I will
> get an Internal
> > error.
> >
> > Please see the pastebin entry for the error message:
> > http://pastebin.com/ddm93jbS
> >
> > 3. Often I get a OutOfMemoryError: PermGen space in the
> red5.log
> >
> > Please see also the pastebin entry for this error message:
> > http://pastebin.com/SL5gXDGw
> >
> > Thanks,
> > Michael
> >
> > Am 17.06.2014 08:25, schrieb Maxim Solodovnik:
> > > Regarding 1
> > > Could you please provide any repo steps?
> > >
> > >
> > > On 16 June 2014 19:03, Vasiliy Degtyarev
> <vasya@unipro.ru <ma...@unipro.ru>
> > <mailto:vasya@unipro.ru <ma...@unipro.ru>>
> > > <mailto:vasya@unipro.ru <ma...@unipro.ru>
> <mailto:vasya@unipro.ru <ma...@unipro.ru>>>> wrote:
> > >
> > > Hello Michael,
> > >
> > > I have fixed second error for the 3.0.3 branch.
> > >
> > > Vasiliy.
> > >
> > >
> > > On 16.06.2014 17:28, Michael Wuttke wrote:
> > >
> > > Hello Maxim,
> > >
> > > I've tested the latest om build with the
> following scenario:
> > >
> > > - om server:
> > > * OS: debian wheezy
> > > * db server: postgresql (version 9.3) ->
> a clean
> > install
> > > * OM version: branch 3.0.3 (build 27)
> > >
> > > - om server:
> > > * OS: debian wheezy
> > > * db server: postgresql (version 9.1)
> > > * Moodle version: 2.7+ (build: 20140605) and
> > > + om moodle plugin: version 1.7.1 -
> (build 2014051301)
> > >
> > > - user client:
> > > * OS: ubuntu 14.04 LTS (trusty tahr)
> > > * browser: FF 30.0 & Opera 12.16.1860
> > >
> > > Adding in OM a 'SOAP' user to create, modify or
> delete OM
> > rooms via
> > > moodle was not the problem. I also could change the
> > settings of a OM
> > > user (f.e. add or change the
> usergroup/organisation). The
> > network
> > > testing works now. Thanks. ;-)
> > >
> > > But two issues occurred during this test.
> > >
> > > 1. Sometimes I've got the following error
> message on the
> > moodle
> > > server,
> > > when I tried to enter a new room (an interview
> room in
> > this case):
> > >
> > > Can not find data record in database table
> course_modules.
> > >
> > > Debug info: SELECT id,course FROM
> {course_modules} WHERE
> > id = ?
> > > [array (
> > > 0 => '6',
> > > )]
> > > Error code: invalidrecord
> > >
> > > Stack trace:
> > > line 1451 of /lib/dml/moodle_database.php:
> > > dml_missing_record_exception thrown
> > > line 1427 of /lib/dml/moodle_database.php:
> call to
> > > moodle_database->get_record___select()
> > > line 7088 of /lib/accesslib.php: call to
> > > moodle_database->get_record()
> > > line 61 of /mod/openmeetings/view.php: call to
> > > context_module::instance()
> > >
> > > 2. When I tried to change the OM
> settings/configuration
> > via the
> > > OM GUI:
> > > Administration -> Configuration -> selecting the
> id 54
> > > (redirect.url.for.external.__users) -> entering
> the Value
> > > 'mymoodleurl'
> > > and tried to save this entry, I've got an
> Internal error.
> > >
> > > See pastebin for the error messages:
> > > http://pastebin.com/hY15zvqv
> > >
> > > Thanks,
> > > Michael
> > >
> > > Am 14.06.2014 10:53, schrieb Maxim Solodovnik:
> > >
> > > Thanks for the detailed report!
> > > build #27 should address first issue
> > >
> > > second was not reproducible here, could you
> please
> > re-check?
> > >
> > >
> > > On 13 June 2014 19:33, Michael Wuttke
> > > <michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-__hochschule.de>
> > <mailto:michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-__hochschule.de>>
> > > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>>
> > > <mailto:michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-__hochschule.de>
> > <mailto:michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-__hochschule.de>>
> > > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>>>> wrote:
> > >
> > > Hello Maxim,
> > >
> > > I've tested the branch 3.0.3 (build 26)
> now with a
> > > clean postgresql
> > > install. Two issues occurred during
> this test.
> > >
> > > 1. Adding a 'SOAP' user to create OM
> rooms via moodle
> > > (version 2.7 and
> > > om moodle plugin version 1.7.1 - build
> 2014051301) is
> > > not a problem,
> > > like I tested yesterday. But to open
> the new
> > created OM
> > > room via moodle
> > > doesn't work. In the openmeetings.log
> file I
> > found the
> > > following error
> > > messages:
> > > http://pastebin.com/rpTfhJcW
> > >
> > > 2. When I tried to add the new soap
> user to a
> > > organisation via the OM
> > > GUI: Administration -> Usergroups ->
> selecting the
> > > usergroup -> Add user
> > > via the drop down menu If got an
> Internal error.
> > >
> > > In the openmeetings.log file I found
> the following
> > > error messages:
> > > http://pastebin.com/q0h1aR3G
> > >
> > > Thanks,
> > > Michael
Re: test of branch 3.0.3 (build 29)
Posted by Maxim Solodovnik <so...@gmail.com>.
or, you are using postgres
will try it
On 18 June 2014 16:13, Maxim Solodovnik <so...@gmail.com> wrote:
> 2) works for me
> very weird, not sure what else can be done :(
>
>
> On 18 June 2014 16:03, Maxim Solodovnik <so...@gmail.com> wrote:
>
>> 2) will check
>> 3) you can use it like this:
>>
>> JAVA_OPTS=-XX:MaxPermSize=256M ./red5.sh
>>
>>
>> On 18 June 2014 16:00, Michael Wuttke <michael.wuttke@beuth-hochschule.de
>> > wrote:
>>
>>> Hello Maxim,
>>>
>>> what a quick response, great! ;-)
>>>
>>> 1) I've tested it and it works as expected. ;-) (my test scenario see my
>>> last mail)
>>>
>>> 2) My steps:
>>> I. I log in as an OM admin at the OM GUI (works as expected).
>>> II. Administration -> Users -> adding & selecting the user 'soap' ->
>>> User details -> Usergroup -> select usergroup 'webbase' -> click button
>>> Save (works as expected).
>>> III. Administration -> Usergroups -> new record -> enter a Name for a
>>> new usergroup 'soap' -> click button Save (works as expected).
>>> IV. select usergroup 'soap' on the left site of the page Administration
>>> -> Usergroups (works as expected).
>>> V. Select the user 'soap' in the middle part Usergroup -> Add user ->
>>> select user 'soap' from the drop down menu caused for me an Internal
>>> error.
>>>
>>> 3) I tested ~/red5/red5-highperf.sh but I've got the same error message
>>> after a while.
>>>
>>> "*|-XX:MaxPermSize=256M|*" is an JVM option for the red5.sh start script?
>>>
>>> Thanks,
>>> Michael
>>>
>>> Am 17.06.2014 20:06, schrieb Maxim Solodovnik:
>>> > 1) fixed
>>> > 2) I cannot reproduce :( can you provide as detailed steps as possible?
>>> > 3) you can run "highperf" or add PermGen memory using
>>> > "*|-XX:MaxPermSize=256M|*"
>>> >
>>> >
>>> > On 17 June 2014 22:15, Michael Wuttke
>>> > <michael.wuttke@beuth-hochschule.de
>>> > <ma...@beuth-hochschule.de>> wrote:
>>> >
>>> > Hello,
>>> >
>>> > I've tested the latest om build with the following scenario:
>>> >
>>> > - om server:
>>> > * OS: debian wheezy
>>> > * database server: postgresql (version 9.3)
>>> > * OM version: branch 3.0.3 (build 28)
>>> > * a clean install via cliadmin with
>>> > ./admin.sh -i -v -file backup.zip -tz Europe/Berlin --drop
>>> > --skip-default-rooms --db-type postgresql --db-host somehost
>>> --db-name
>>> > somename --db-user someuser --db-pass somepass
>>> >
>>> > - moodle server:
>>> > * OS: debian wheezy
>>> > * database server: postgresql (version 9.1)
>>> > * Moodle version: 2.7+ (build: 20140613) -> not a clean install
>>> > * om moodle plugin: version 1.7.1 - (build 2014051301)
>>> >
>>> > - user client:
>>> > * OS: ubuntu 14.04 LTS (trusty tahr)
>>> > * browser: FF 30.0 & Opera 12.16.1860
>>> >
>>> > Adding in OM a 'SOAP' user to create, modify or delete OM rooms via
>>> > moodle is not a problem, or changing the settings of a OM user.
>>> >
>>> > But some issues occurred during the test.
>>> >
>>> > 1. I still get the following error message on the moodle server,
>>> when I
>>> > try to enter a new created om room (an interview room in this
>>> case; I
>>> > created a conference, a webinar and a interview room):
>>> >
>>> > Can not find data record in database table course_modules.
>>> >
>>> > Debug info: SELECT id,course FROM {course_modules} WHERE id = ?
>>> > [array (
>>> > 0 => '6',
>>> > )]
>>> > Error code: invalidrecord
>>> >
>>> > Stack trace:
>>> > line 1451 of /lib/dml/moodle_database.php:
>>> > dml_missing_record_exception thrown
>>> > line 1427 of /lib/dml/moodle_database.php: call to
>>> > moodle_database->get_record_select()
>>> > line 7088 of /lib/accesslib.php: call to
>>> > moodle_database->get_record()
>>> > line 61 of /mod/openmeetings/view.php: call to
>>> > context_module::instance()
>>> >
>>> > 2. When I try to add a user to a group via the OM GUI:
>>> Administration ->
>>> > Usergroups -> new record -> enter a Name for a new usergroup - this
>>> > works. But if I try to add a user to this new usergroup via the
>>> drop
>>> > down menu Add user and try then to select a user, I will get an
>>> Internal
>>> > error.
>>> >
>>> > Please see the pastebin entry for the error message:
>>> > http://pastebin.com/ddm93jbS
>>> >
>>> > 3. Often I get a OutOfMemoryError: PermGen space in the red5.log
>>> >
>>> > Please see also the pastebin entry for this error message:
>>> > http://pastebin.com/SL5gXDGw
>>> >
>>> > Thanks,
>>> > Michael
>>> >
>>> > Am 17.06.2014 08:25, schrieb Maxim Solodovnik:
>>> > > Regarding 1
>>> > > Could you please provide any repo steps?
>>> > >
>>> > >
>>> > > On 16 June 2014 19:03, Vasiliy Degtyarev <vasya@unipro.ru
>>> > <ma...@unipro.ru>
>>> > > <mailto:vasya@unipro.ru <ma...@unipro.ru>>> wrote:
>>> > >
>>> > > Hello Michael,
>>> > >
>>> > > I have fixed second error for the 3.0.3 branch.
>>> > >
>>> > > Vasiliy.
>>> > >
>>> > >
>>> > > On 16.06.2014 17:28, Michael Wuttke wrote:
>>> > >
>>> > > Hello Maxim,
>>> > >
>>> > > I've tested the latest om build with the following
>>> scenario:
>>> > >
>>> > > - om server:
>>> > > * OS: debian wheezy
>>> > > * db server: postgresql (version 9.3) -> a clean
>>> > install
>>> > > * OM version: branch 3.0.3 (build 27)
>>> > >
>>> > > - om server:
>>> > > * OS: debian wheezy
>>> > > * db server: postgresql (version 9.1)
>>> > > * Moodle version: 2.7+ (build: 20140605) and
>>> > > + om moodle plugin: version 1.7.1 - (build
>>> 2014051301)
>>> > >
>>> > > - user client:
>>> > > * OS: ubuntu 14.04 LTS (trusty tahr)
>>> > > * browser: FF 30.0 & Opera 12.16.1860
>>> > >
>>> > > Adding in OM a 'SOAP' user to create, modify or delete OM
>>> > rooms via
>>> > > moodle was not the problem. I also could change the
>>> > settings of a OM
>>> > > user (f.e. add or change the usergroup/organisation). The
>>> > network
>>> > > testing works now. Thanks. ;-)
>>> > >
>>> > > But two issues occurred during this test.
>>> > >
>>> > > 1. Sometimes I've got the following error message on the
>>> > moodle
>>> > > server,
>>> > > when I tried to enter a new room (an interview room in
>>> > this case):
>>> > >
>>> > > Can not find data record in database table
>>> course_modules.
>>> > >
>>> > > Debug info: SELECT id,course FROM {course_modules} WHERE
>>> > id = ?
>>> > > [array (
>>> > > 0 => '6',
>>> > > )]
>>> > > Error code: invalidrecord
>>> > >
>>> > > Stack trace:
>>> > > line 1451 of /lib/dml/moodle_database.php:
>>> > > dml_missing_record_exception thrown
>>> > > line 1427 of /lib/dml/moodle_database.php: call to
>>> > > moodle_database->get_record___select()
>>> > > line 7088 of /lib/accesslib.php: call to
>>> > > moodle_database->get_record()
>>> > > line 61 of /mod/openmeetings/view.php: call to
>>> > > context_module::instance()
>>> > >
>>> > > 2. When I tried to change the OM settings/configuration
>>> > via the
>>> > > OM GUI:
>>> > > Administration -> Configuration -> selecting the id 54
>>> > > (redirect.url.for.external.__users) -> entering the Value
>>> > > 'mymoodleurl'
>>> > > and tried to save this entry, I've got an Internal error.
>>> > >
>>> > > See pastebin for the error messages:
>>> > > http://pastebin.com/hY15zvqv
>>> > >
>>> > > Thanks,
>>> > > Michael
>>> > >
>>> > > Am 14.06.2014 10:53, schrieb Maxim Solodovnik:
>>> > >
>>> > > Thanks for the detailed report!
>>> > > build #27 should address first issue
>>> > >
>>> > > second was not reproducible here, could you please
>>> > re-check?
>>> > >
>>> > >
>>> > > On 13 June 2014 19:33, Michael Wuttke
>>> > > <michael.wuttke@beuth-__hochschule.de
>>> > <ma...@beuth-__hochschule.de>
>>> > > <mailto:michael.wuttke@beuth-hochschule.de
>>> > <ma...@beuth-hochschule.de>>
>>> > > <mailto:michael.wuttke@beuth-__hochschule.de
>>> > <ma...@beuth-__hochschule.de>
>>> > > <mailto:michael.wuttke@beuth-hochschule.de
>>> > <ma...@beuth-hochschule.de>>>> wrote:
>>> > >
>>> > > Hello Maxim,
>>> > >
>>> > > I've tested the branch 3.0.3 (build 26) now
>>> with a
>>> > > clean postgresql
>>> > > install. Two issues occurred during this test.
>>> > >
>>> > > 1. Adding a 'SOAP' user to create OM rooms via
>>> moodle
>>> > > (version 2.7 and
>>> > > om moodle plugin version 1.7.1 - build
>>> 2014051301) is
>>> > > not a problem,
>>> > > like I tested yesterday. But to open the new
>>> > created OM
>>> > > room via moodle
>>> > > doesn't work. In the openmeetings.log file I
>>> > found the
>>> > > following error
>>> > > messages:
>>> > > http://pastebin.com/rpTfhJcW
>>> > >
>>> > > 2. When I tried to add the new soap user to a
>>> > > organisation via the OM
>>> > > GUI: Administration -> Usergroups -> selecting
>>> the
>>> > > usergroup -> Add user
>>> > > via the drop down menu If got an Internal error.
>>> > >
>>> > > In the openmeetings.log file I found the
>>> following
>>> > > error messages:
>>> > > http://pastebin.com/q0h1aR3G
>>> > >
>>> > > Thanks,
>>> > > Michael
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > --
>>> > > WBR
>>> > > Maxim aka solomax
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > WBR
>>> > Maxim aka solomax
>>>
>>> --
>>> Vielen Dank & mit freundlichen Grüßen,
>>> Michael Wuttke
>>>
>>> Administration - Learning Management System
>>> Beuth Hochschule Berlin - Labor Online Learning
>>> Luxemburger Str. 10
>>> 13353 Berlin
>>> Tel: +49 (0)30 45 04 2184
>>> E-Mail: michael.wuttke@beuth-hochschule.de
>>> News: https://lms.beuth-hochschule.de/rss
>>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: test of branch 3.0.3 (build 29)
Posted by Maxim Solodovnik <so...@gmail.com>.
2) works for me
very weird, not sure what else can be done :(
On 18 June 2014 16:03, Maxim Solodovnik <so...@gmail.com> wrote:
> 2) will check
> 3) you can use it like this:
>
> JAVA_OPTS=-XX:MaxPermSize=256M ./red5.sh
>
>
> On 18 June 2014 16:00, Michael Wuttke <mi...@beuth-hochschule.de>
> wrote:
>
>> Hello Maxim,
>>
>> what a quick response, great! ;-)
>>
>> 1) I've tested it and it works as expected. ;-) (my test scenario see my
>> last mail)
>>
>> 2) My steps:
>> I. I log in as an OM admin at the OM GUI (works as expected).
>> II. Administration -> Users -> adding & selecting the user 'soap' ->
>> User details -> Usergroup -> select usergroup 'webbase' -> click button
>> Save (works as expected).
>> III. Administration -> Usergroups -> new record -> enter a Name for a
>> new usergroup 'soap' -> click button Save (works as expected).
>> IV. select usergroup 'soap' on the left site of the page Administration
>> -> Usergroups (works as expected).
>> V. Select the user 'soap' in the middle part Usergroup -> Add user ->
>> select user 'soap' from the drop down menu caused for me an Internal
>> error.
>>
>> 3) I tested ~/red5/red5-highperf.sh but I've got the same error message
>> after a while.
>>
>> "*|-XX:MaxPermSize=256M|*" is an JVM option for the red5.sh start script?
>>
>> Thanks,
>> Michael
>>
>> Am 17.06.2014 20:06, schrieb Maxim Solodovnik:
>> > 1) fixed
>> > 2) I cannot reproduce :( can you provide as detailed steps as possible?
>> > 3) you can run "highperf" or add PermGen memory using
>> > "*|-XX:MaxPermSize=256M|*"
>> >
>> >
>> > On 17 June 2014 22:15, Michael Wuttke
>> > <michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>> wrote:
>> >
>> > Hello,
>> >
>> > I've tested the latest om build with the following scenario:
>> >
>> > - om server:
>> > * OS: debian wheezy
>> > * database server: postgresql (version 9.3)
>> > * OM version: branch 3.0.3 (build 28)
>> > * a clean install via cliadmin with
>> > ./admin.sh -i -v -file backup.zip -tz Europe/Berlin --drop
>> > --skip-default-rooms --db-type postgresql --db-host somehost
>> --db-name
>> > somename --db-user someuser --db-pass somepass
>> >
>> > - moodle server:
>> > * OS: debian wheezy
>> > * database server: postgresql (version 9.1)
>> > * Moodle version: 2.7+ (build: 20140613) -> not a clean install
>> > * om moodle plugin: version 1.7.1 - (build 2014051301)
>> >
>> > - user client:
>> > * OS: ubuntu 14.04 LTS (trusty tahr)
>> > * browser: FF 30.0 & Opera 12.16.1860
>> >
>> > Adding in OM a 'SOAP' user to create, modify or delete OM rooms via
>> > moodle is not a problem, or changing the settings of a OM user.
>> >
>> > But some issues occurred during the test.
>> >
>> > 1. I still get the following error message on the moodle server,
>> when I
>> > try to enter a new created om room (an interview room in this case;
>> I
>> > created a conference, a webinar and a interview room):
>> >
>> > Can not find data record in database table course_modules.
>> >
>> > Debug info: SELECT id,course FROM {course_modules} WHERE id = ?
>> > [array (
>> > 0 => '6',
>> > )]
>> > Error code: invalidrecord
>> >
>> > Stack trace:
>> > line 1451 of /lib/dml/moodle_database.php:
>> > dml_missing_record_exception thrown
>> > line 1427 of /lib/dml/moodle_database.php: call to
>> > moodle_database->get_record_select()
>> > line 7088 of /lib/accesslib.php: call to
>> > moodle_database->get_record()
>> > line 61 of /mod/openmeetings/view.php: call to
>> > context_module::instance()
>> >
>> > 2. When I try to add a user to a group via the OM GUI:
>> Administration ->
>> > Usergroups -> new record -> enter a Name for a new usergroup - this
>> > works. But if I try to add a user to this new usergroup via the drop
>> > down menu Add user and try then to select a user, I will get an
>> Internal
>> > error.
>> >
>> > Please see the pastebin entry for the error message:
>> > http://pastebin.com/ddm93jbS
>> >
>> > 3. Often I get a OutOfMemoryError: PermGen space in the red5.log
>> >
>> > Please see also the pastebin entry for this error message:
>> > http://pastebin.com/SL5gXDGw
>> >
>> > Thanks,
>> > Michael
>> >
>> > Am 17.06.2014 08:25, schrieb Maxim Solodovnik:
>> > > Regarding 1
>> > > Could you please provide any repo steps?
>> > >
>> > >
>> > > On 16 June 2014 19:03, Vasiliy Degtyarev <vasya@unipro.ru
>> > <ma...@unipro.ru>
>> > > <mailto:vasya@unipro.ru <ma...@unipro.ru>>> wrote:
>> > >
>> > > Hello Michael,
>> > >
>> > > I have fixed second error for the 3.0.3 branch.
>> > >
>> > > Vasiliy.
>> > >
>> > >
>> > > On 16.06.2014 17:28, Michael Wuttke wrote:
>> > >
>> > > Hello Maxim,
>> > >
>> > > I've tested the latest om build with the following
>> scenario:
>> > >
>> > > - om server:
>> > > * OS: debian wheezy
>> > > * db server: postgresql (version 9.3) -> a clean
>> > install
>> > > * OM version: branch 3.0.3 (build 27)
>> > >
>> > > - om server:
>> > > * OS: debian wheezy
>> > > * db server: postgresql (version 9.1)
>> > > * Moodle version: 2.7+ (build: 20140605) and
>> > > + om moodle plugin: version 1.7.1 - (build
>> 2014051301)
>> > >
>> > > - user client:
>> > > * OS: ubuntu 14.04 LTS (trusty tahr)
>> > > * browser: FF 30.0 & Opera 12.16.1860
>> > >
>> > > Adding in OM a 'SOAP' user to create, modify or delete OM
>> > rooms via
>> > > moodle was not the problem. I also could change the
>> > settings of a OM
>> > > user (f.e. add or change the usergroup/organisation). The
>> > network
>> > > testing works now. Thanks. ;-)
>> > >
>> > > But two issues occurred during this test.
>> > >
>> > > 1. Sometimes I've got the following error message on the
>> > moodle
>> > > server,
>> > > when I tried to enter a new room (an interview room in
>> > this case):
>> > >
>> > > Can not find data record in database table course_modules.
>> > >
>> > > Debug info: SELECT id,course FROM {course_modules} WHERE
>> > id = ?
>> > > [array (
>> > > 0 => '6',
>> > > )]
>> > > Error code: invalidrecord
>> > >
>> > > Stack trace:
>> > > line 1451 of /lib/dml/moodle_database.php:
>> > > dml_missing_record_exception thrown
>> > > line 1427 of /lib/dml/moodle_database.php: call to
>> > > moodle_database->get_record___select()
>> > > line 7088 of /lib/accesslib.php: call to
>> > > moodle_database->get_record()
>> > > line 61 of /mod/openmeetings/view.php: call to
>> > > context_module::instance()
>> > >
>> > > 2. When I tried to change the OM settings/configuration
>> > via the
>> > > OM GUI:
>> > > Administration -> Configuration -> selecting the id 54
>> > > (redirect.url.for.external.__users) -> entering the Value
>> > > 'mymoodleurl'
>> > > and tried to save this entry, I've got an Internal error.
>> > >
>> > > See pastebin for the error messages:
>> > > http://pastebin.com/hY15zvqv
>> > >
>> > > Thanks,
>> > > Michael
>> > >
>> > > Am 14.06.2014 10:53, schrieb Maxim Solodovnik:
>> > >
>> > > Thanks for the detailed report!
>> > > build #27 should address first issue
>> > >
>> > > second was not reproducible here, could you please
>> > re-check?
>> > >
>> > >
>> > > On 13 June 2014 19:33, Michael Wuttke
>> > > <michael.wuttke@beuth-__hochschule.de
>> > <ma...@beuth-__hochschule.de>
>> > > <mailto:michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>>
>> > > <mailto:michael.wuttke@beuth-__hochschule.de
>> > <ma...@beuth-__hochschule.de>
>> > > <mailto:michael.wuttke@beuth-hochschule.de
>> > <ma...@beuth-hochschule.de>>>> wrote:
>> > >
>> > > Hello Maxim,
>> > >
>> > > I've tested the branch 3.0.3 (build 26) now with
>> a
>> > > clean postgresql
>> > > install. Two issues occurred during this test.
>> > >
>> > > 1. Adding a 'SOAP' user to create OM rooms via
>> moodle
>> > > (version 2.7 and
>> > > om moodle plugin version 1.7.1 - build
>> 2014051301) is
>> > > not a problem,
>> > > like I tested yesterday. But to open the new
>> > created OM
>> > > room via moodle
>> > > doesn't work. In the openmeetings.log file I
>> > found the
>> > > following error
>> > > messages:
>> > > http://pastebin.com/rpTfhJcW
>> > >
>> > > 2. When I tried to add the new soap user to a
>> > > organisation via the OM
>> > > GUI: Administration -> Usergroups -> selecting
>> the
>> > > usergroup -> Add user
>> > > via the drop down menu If got an Internal error.
>> > >
>> > > In the openmeetings.log file I found the
>> following
>> > > error messages:
>> > > http://pastebin.com/q0h1aR3G
>> > >
>> > > Thanks,
>> > > Michael
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > --
>> > > WBR
>> > > Maxim aka solomax
>> >
>> >
>> >
>> >
>> > --
>> > WBR
>> > Maxim aka solomax
>>
>> --
>> Vielen Dank & mit freundlichen Grüßen,
>> Michael Wuttke
>>
>> Administration - Learning Management System
>> Beuth Hochschule Berlin - Labor Online Learning
>> Luxemburger Str. 10
>> 13353 Berlin
>> Tel: +49 (0)30 45 04 2184
>> E-Mail: michael.wuttke@beuth-hochschule.de
>> News: https://lms.beuth-hochschule.de/rss
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: test of branch 3.0.3 (build 29)
Posted by Maxim Solodovnik <so...@gmail.com>.
2) will check
3) you can use it like this:
JAVA_OPTS=-XX:MaxPermSize=256M ./red5.sh
On 18 June 2014 16:00, Michael Wuttke <mi...@beuth-hochschule.de>
wrote:
> Hello Maxim,
>
> what a quick response, great! ;-)
>
> 1) I've tested it and it works as expected. ;-) (my test scenario see my
> last mail)
>
> 2) My steps:
> I. I log in as an OM admin at the OM GUI (works as expected).
> II. Administration -> Users -> adding & selecting the user 'soap' ->
> User details -> Usergroup -> select usergroup 'webbase' -> click button
> Save (works as expected).
> III. Administration -> Usergroups -> new record -> enter a Name for a
> new usergroup 'soap' -> click button Save (works as expected).
> IV. select usergroup 'soap' on the left site of the page Administration
> -> Usergroups (works as expected).
> V. Select the user 'soap' in the middle part Usergroup -> Add user ->
> select user 'soap' from the drop down menu caused for me an Internal error.
>
> 3) I tested ~/red5/red5-highperf.sh but I've got the same error message
> after a while.
>
> "*|-XX:MaxPermSize=256M|*" is an JVM option for the red5.sh start script?
>
> Thanks,
> Michael
>
> Am 17.06.2014 20:06, schrieb Maxim Solodovnik:
> > 1) fixed
> > 2) I cannot reproduce :( can you provide as detailed steps as possible?
> > 3) you can run "highperf" or add PermGen memory using
> > "*|-XX:MaxPermSize=256M|*"
> >
> >
> > On 17 June 2014 22:15, Michael Wuttke
> > <michael.wuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>> wrote:
> >
> > Hello,
> >
> > I've tested the latest om build with the following scenario:
> >
> > - om server:
> > * OS: debian wheezy
> > * database server: postgresql (version 9.3)
> > * OM version: branch 3.0.3 (build 28)
> > * a clean install via cliadmin with
> > ./admin.sh -i -v -file backup.zip -tz Europe/Berlin --drop
> > --skip-default-rooms --db-type postgresql --db-host somehost
> --db-name
> > somename --db-user someuser --db-pass somepass
> >
> > - moodle server:
> > * OS: debian wheezy
> > * database server: postgresql (version 9.1)
> > * Moodle version: 2.7+ (build: 20140613) -> not a clean install
> > * om moodle plugin: version 1.7.1 - (build 2014051301)
> >
> > - user client:
> > * OS: ubuntu 14.04 LTS (trusty tahr)
> > * browser: FF 30.0 & Opera 12.16.1860
> >
> > Adding in OM a 'SOAP' user to create, modify or delete OM rooms via
> > moodle is not a problem, or changing the settings of a OM user.
> >
> > But some issues occurred during the test.
> >
> > 1. I still get the following error message on the moodle server,
> when I
> > try to enter a new created om room (an interview room in this case; I
> > created a conference, a webinar and a interview room):
> >
> > Can not find data record in database table course_modules.
> >
> > Debug info: SELECT id,course FROM {course_modules} WHERE id = ?
> > [array (
> > 0 => '6',
> > )]
> > Error code: invalidrecord
> >
> > Stack trace:
> > line 1451 of /lib/dml/moodle_database.php:
> > dml_missing_record_exception thrown
> > line 1427 of /lib/dml/moodle_database.php: call to
> > moodle_database->get_record_select()
> > line 7088 of /lib/accesslib.php: call to
> > moodle_database->get_record()
> > line 61 of /mod/openmeetings/view.php: call to
> > context_module::instance()
> >
> > 2. When I try to add a user to a group via the OM GUI:
> Administration ->
> > Usergroups -> new record -> enter a Name for a new usergroup - this
> > works. But if I try to add a user to this new usergroup via the drop
> > down menu Add user and try then to select a user, I will get an
> Internal
> > error.
> >
> > Please see the pastebin entry for the error message:
> > http://pastebin.com/ddm93jbS
> >
> > 3. Often I get a OutOfMemoryError: PermGen space in the red5.log
> >
> > Please see also the pastebin entry for this error message:
> > http://pastebin.com/SL5gXDGw
> >
> > Thanks,
> > Michael
> >
> > Am 17.06.2014 08:25, schrieb Maxim Solodovnik:
> > > Regarding 1
> > > Could you please provide any repo steps?
> > >
> > >
> > > On 16 June 2014 19:03, Vasiliy Degtyarev <vasya@unipro.ru
> > <ma...@unipro.ru>
> > > <mailto:vasya@unipro.ru <ma...@unipro.ru>>> wrote:
> > >
> > > Hello Michael,
> > >
> > > I have fixed second error for the 3.0.3 branch.
> > >
> > > Vasiliy.
> > >
> > >
> > > On 16.06.2014 17:28, Michael Wuttke wrote:
> > >
> > > Hello Maxim,
> > >
> > > I've tested the latest om build with the following
> scenario:
> > >
> > > - om server:
> > > * OS: debian wheezy
> > > * db server: postgresql (version 9.3) -> a clean
> > install
> > > * OM version: branch 3.0.3 (build 27)
> > >
> > > - om server:
> > > * OS: debian wheezy
> > > * db server: postgresql (version 9.1)
> > > * Moodle version: 2.7+ (build: 20140605) and
> > > + om moodle plugin: version 1.7.1 - (build
> 2014051301)
> > >
> > > - user client:
> > > * OS: ubuntu 14.04 LTS (trusty tahr)
> > > * browser: FF 30.0 & Opera 12.16.1860
> > >
> > > Adding in OM a 'SOAP' user to create, modify or delete OM
> > rooms via
> > > moodle was not the problem. I also could change the
> > settings of a OM
> > > user (f.e. add or change the usergroup/organisation). The
> > network
> > > testing works now. Thanks. ;-)
> > >
> > > But two issues occurred during this test.
> > >
> > > 1. Sometimes I've got the following error message on the
> > moodle
> > > server,
> > > when I tried to enter a new room (an interview room in
> > this case):
> > >
> > > Can not find data record in database table course_modules.
> > >
> > > Debug info: SELECT id,course FROM {course_modules} WHERE
> > id = ?
> > > [array (
> > > 0 => '6',
> > > )]
> > > Error code: invalidrecord
> > >
> > > Stack trace:
> > > line 1451 of /lib/dml/moodle_database.php:
> > > dml_missing_record_exception thrown
> > > line 1427 of /lib/dml/moodle_database.php: call to
> > > moodle_database->get_record___select()
> > > line 7088 of /lib/accesslib.php: call to
> > > moodle_database->get_record()
> > > line 61 of /mod/openmeetings/view.php: call to
> > > context_module::instance()
> > >
> > > 2. When I tried to change the OM settings/configuration
> > via the
> > > OM GUI:
> > > Administration -> Configuration -> selecting the id 54
> > > (redirect.url.for.external.__users) -> entering the Value
> > > 'mymoodleurl'
> > > and tried to save this entry, I've got an Internal error.
> > >
> > > See pastebin for the error messages:
> > > http://pastebin.com/hY15zvqv
> > >
> > > Thanks,
> > > Michael
> > >
> > > Am 14.06.2014 10:53, schrieb Maxim Solodovnik:
> > >
> > > Thanks for the detailed report!
> > > build #27 should address first issue
> > >
> > > second was not reproducible here, could you please
> > re-check?
> > >
> > >
> > > On 13 June 2014 19:33, Michael Wuttke
> > > <michael.wuttke@beuth-__hochschule.de
> > <ma...@beuth-__hochschule.de>
> > > <mailto:michael.wuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>>
> > > <mailto:michael.wuttke@beuth-__hochschule.de
> > <ma...@beuth-__hochschule.de>
> > > <mailto:michael.wuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>>>> wrote:
> > >
> > > Hello Maxim,
> > >
> > > I've tested the branch 3.0.3 (build 26) now with a
> > > clean postgresql
> > > install. Two issues occurred during this test.
> > >
> > > 1. Adding a 'SOAP' user to create OM rooms via
> moodle
> > > (version 2.7 and
> > > om moodle plugin version 1.7.1 - build
> 2014051301) is
> > > not a problem,
> > > like I tested yesterday. But to open the new
> > created OM
> > > room via moodle
> > > doesn't work. In the openmeetings.log file I
> > found the
> > > following error
> > > messages:
> > > http://pastebin.com/rpTfhJcW
> > >
> > > 2. When I tried to add the new soap user to a
> > > organisation via the OM
> > > GUI: Administration -> Usergroups -> selecting the
> > > usergroup -> Add user
> > > via the drop down menu If got an Internal error.
> > >
> > > In the openmeetings.log file I found the following
> > > error messages:
> > > http://pastebin.com/q0h1aR3G
> > >
> > > Thanks,
> > > Michael
> > >
> > >
> > >
> > >
> > >
> > > --
> > > WBR
> > > Maxim aka solomax
> >
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
>
> --
> Vielen Dank & mit freundlichen Grüßen,
> Michael Wuttke
>
> Administration - Learning Management System
> Beuth Hochschule Berlin - Labor Online Learning
> Luxemburger Str. 10
> 13353 Berlin
> Tel: +49 (0)30 45 04 2184
> E-Mail: michael.wuttke@beuth-hochschule.de
> News: https://lms.beuth-hochschule.de/rss
>
--
WBR
Maxim aka solomax
test of branch 3.0.3 (build 29)
Posted by Michael Wuttke <mi...@beuth-hochschule.de>.
Hello Maxim,
what a quick response, great! ;-)
1) I've tested it and it works as expected. ;-) (my test scenario see my
last mail)
2) My steps:
I. I log in as an OM admin at the OM GUI (works as expected).
II. Administration -> Users -> adding & selecting the user 'soap' ->
User details -> Usergroup -> select usergroup 'webbase' -> click button
Save (works as expected).
III. Administration -> Usergroups -> new record -> enter a Name for a
new usergroup 'soap' -> click button Save (works as expected).
IV. select usergroup 'soap' on the left site of the page Administration
-> Usergroups (works as expected).
V. Select the user 'soap' in the middle part Usergroup -> Add user ->
select user 'soap' from the drop down menu caused for me an Internal error.
3) I tested ~/red5/red5-highperf.sh but I've got the same error message
after a while.
"*|-XX:MaxPermSize=256M|*" is an JVM option for the red5.sh start script?
Thanks,
Michael
Am 17.06.2014 20:06, schrieb Maxim Solodovnik:
> 1) fixed
> 2) I cannot reproduce :( can you provide as detailed steps as possible?
> 3) you can run "highperf" or add PermGen memory using
> "*|-XX:MaxPermSize=256M|*"
>
>
> On 17 June 2014 22:15, Michael Wuttke
> <michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>> wrote:
>
> Hello,
>
> I've tested the latest om build with the following scenario:
>
> - om server:
> * OS: debian wheezy
> * database server: postgresql (version 9.3)
> * OM version: branch 3.0.3 (build 28)
> * a clean install via cliadmin with
> ./admin.sh -i -v -file backup.zip -tz Europe/Berlin --drop
> --skip-default-rooms --db-type postgresql --db-host somehost --db-name
> somename --db-user someuser --db-pass somepass
>
> - moodle server:
> * OS: debian wheezy
> * database server: postgresql (version 9.1)
> * Moodle version: 2.7+ (build: 20140613) -> not a clean install
> * om moodle plugin: version 1.7.1 - (build 2014051301)
>
> - user client:
> * OS: ubuntu 14.04 LTS (trusty tahr)
> * browser: FF 30.0 & Opera 12.16.1860
>
> Adding in OM a 'SOAP' user to create, modify or delete OM rooms via
> moodle is not a problem, or changing the settings of a OM user.
>
> But some issues occurred during the test.
>
> 1. I still get the following error message on the moodle server, when I
> try to enter a new created om room (an interview room in this case; I
> created a conference, a webinar and a interview room):
>
> Can not find data record in database table course_modules.
>
> Debug info: SELECT id,course FROM {course_modules} WHERE id = ?
> [array (
> 0 => '6',
> )]
> Error code: invalidrecord
>
> Stack trace:
> line 1451 of /lib/dml/moodle_database.php:
> dml_missing_record_exception thrown
> line 1427 of /lib/dml/moodle_database.php: call to
> moodle_database->get_record_select()
> line 7088 of /lib/accesslib.php: call to
> moodle_database->get_record()
> line 61 of /mod/openmeetings/view.php: call to
> context_module::instance()
>
> 2. When I try to add a user to a group via the OM GUI: Administration ->
> Usergroups -> new record -> enter a Name for a new usergroup - this
> works. But if I try to add a user to this new usergroup via the drop
> down menu Add user and try then to select a user, I will get an Internal
> error.
>
> Please see the pastebin entry for the error message:
> http://pastebin.com/ddm93jbS
>
> 3. Often I get a OutOfMemoryError: PermGen space in the red5.log
>
> Please see also the pastebin entry for this error message:
> http://pastebin.com/SL5gXDGw
>
> Thanks,
> Michael
>
> Am 17.06.2014 08:25, schrieb Maxim Solodovnik:
> > Regarding 1
> > Could you please provide any repo steps?
> >
> >
> > On 16 June 2014 19:03, Vasiliy Degtyarev <vasya@unipro.ru
> <ma...@unipro.ru>
> > <mailto:vasya@unipro.ru <ma...@unipro.ru>>> wrote:
> >
> > Hello Michael,
> >
> > I have fixed second error for the 3.0.3 branch.
> >
> > Vasiliy.
> >
> >
> > On 16.06.2014 17:28, Michael Wuttke wrote:
> >
> > Hello Maxim,
> >
> > I've tested the latest om build with the following scenario:
> >
> > - om server:
> > * OS: debian wheezy
> > * db server: postgresql (version 9.3) -> a clean
> install
> > * OM version: branch 3.0.3 (build 27)
> >
> > - om server:
> > * OS: debian wheezy
> > * db server: postgresql (version 9.1)
> > * Moodle version: 2.7+ (build: 20140605) and
> > + om moodle plugin: version 1.7.1 - (build 2014051301)
> >
> > - user client:
> > * OS: ubuntu 14.04 LTS (trusty tahr)
> > * browser: FF 30.0 & Opera 12.16.1860
> >
> > Adding in OM a 'SOAP' user to create, modify or delete OM
> rooms via
> > moodle was not the problem. I also could change the
> settings of a OM
> > user (f.e. add or change the usergroup/organisation). The
> network
> > testing works now. Thanks. ;-)
> >
> > But two issues occurred during this test.
> >
> > 1. Sometimes I've got the following error message on the
> moodle
> > server,
> > when I tried to enter a new room (an interview room in
> this case):
> >
> > Can not find data record in database table course_modules.
> >
> > Debug info: SELECT id,course FROM {course_modules} WHERE
> id = ?
> > [array (
> > 0 => '6',
> > )]
> > Error code: invalidrecord
> >
> > Stack trace:
> > line 1451 of /lib/dml/moodle_database.php:
> > dml_missing_record_exception thrown
> > line 1427 of /lib/dml/moodle_database.php: call to
> > moodle_database->get_record___select()
> > line 7088 of /lib/accesslib.php: call to
> > moodle_database->get_record()
> > line 61 of /mod/openmeetings/view.php: call to
> > context_module::instance()
> >
> > 2. When I tried to change the OM settings/configuration
> via the
> > OM GUI:
> > Administration -> Configuration -> selecting the id 54
> > (redirect.url.for.external.__users) -> entering the Value
> > 'mymoodleurl'
> > and tried to save this entry, I've got an Internal error.
> >
> > See pastebin for the error messages:
> > http://pastebin.com/hY15zvqv
> >
> > Thanks,
> > Michael
> >
> > Am 14.06.2014 10:53, schrieb Maxim Solodovnik:
> >
> > Thanks for the detailed report!
> > build #27 should address first issue
> >
> > second was not reproducible here, could you please
> re-check?
> >
> >
> > On 13 June 2014 19:33, Michael Wuttke
> > <michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-__hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>
> > <mailto:michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-__hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>>> wrote:
> >
> > Hello Maxim,
> >
> > I've tested the branch 3.0.3 (build 26) now with a
> > clean postgresql
> > install. Two issues occurred during this test.
> >
> > 1. Adding a 'SOAP' user to create OM rooms via moodle
> > (version 2.7 and
> > om moodle plugin version 1.7.1 - build 2014051301) is
> > not a problem,
> > like I tested yesterday. But to open the new
> created OM
> > room via moodle
> > doesn't work. In the openmeetings.log file I
> found the
> > following error
> > messages:
> > http://pastebin.com/rpTfhJcW
> >
> > 2. When I tried to add the new soap user to a
> > organisation via the OM
> > GUI: Administration -> Usergroups -> selecting the
> > usergroup -> Add user
> > via the drop down menu If got an Internal error.
> >
> > In the openmeetings.log file I found the following
> > error messages:
> > http://pastebin.com/q0h1aR3G
> >
> > Thanks,
> > Michael
> >
> >
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
>
>
>
>
> --
> WBR
> Maxim aka solomax
--
Vielen Dank & mit freundlichen Grüßen,
Michael Wuttke
Administration - Learning Management System
Beuth Hochschule Berlin - Labor Online Learning
Luxemburger Str. 10
13353 Berlin
Tel: +49 (0)30 45 04 2184
E-Mail: michael.wuttke@beuth-hochschule.de
News: https://lms.beuth-hochschule.de/rss
Re: test of branch 3.0.3 (build 28)
Posted by Maxim Solodovnik <so...@gmail.com>.
1) fixed
2) I cannot reproduce :( can you provide as detailed steps as possible?
3) you can run "highperf" or add PermGen memory using "
*-XX:MaxPermSize=256M*"
On 17 June 2014 22:15, Michael Wuttke <mi...@beuth-hochschule.de>
wrote:
> Hello,
>
> I've tested the latest om build with the following scenario:
>
> - om server:
> * OS: debian wheezy
> * database server: postgresql (version 9.3)
> * OM version: branch 3.0.3 (build 28)
> * a clean install via cliadmin with
> ./admin.sh -i -v -file backup.zip -tz Europe/Berlin --drop
> --skip-default-rooms --db-type postgresql --db-host somehost --db-name
> somename --db-user someuser --db-pass somepass
>
> - moodle server:
> * OS: debian wheezy
> * database server: postgresql (version 9.1)
> * Moodle version: 2.7+ (build: 20140613) -> not a clean install
> * om moodle plugin: version 1.7.1 - (build 2014051301)
>
> - user client:
> * OS: ubuntu 14.04 LTS (trusty tahr)
> * browser: FF 30.0 & Opera 12.16.1860
>
> Adding in OM a 'SOAP' user to create, modify or delete OM rooms via
> moodle is not a problem, or changing the settings of a OM user.
>
> But some issues occurred during the test.
>
> 1. I still get the following error message on the moodle server, when I
> try to enter a new created om room (an interview room in this case; I
> created a conference, a webinar and a interview room):
>
> Can not find data record in database table course_modules.
>
> Debug info: SELECT id,course FROM {course_modules} WHERE id = ?
> [array (
> 0 => '6',
> )]
> Error code: invalidrecord
>
> Stack trace:
> line 1451 of /lib/dml/moodle_database.php:
> dml_missing_record_exception thrown
> line 1427 of /lib/dml/moodle_database.php: call to
> moodle_database->get_record_select()
> line 7088 of /lib/accesslib.php: call to
> moodle_database->get_record()
> line 61 of /mod/openmeetings/view.php: call to
> context_module::instance()
>
> 2. When I try to add a user to a group via the OM GUI: Administration ->
> Usergroups -> new record -> enter a Name for a new usergroup - this
> works. But if I try to add a user to this new usergroup via the drop
> down menu Add user and try then to select a user, I will get an Internal
> error.
>
> Please see the pastebin entry for the error message:
> http://pastebin.com/ddm93jbS
>
> 3. Often I get a OutOfMemoryError: PermGen space in the red5.log
>
> Please see also the pastebin entry for this error message:
> http://pastebin.com/SL5gXDGw
>
> Thanks,
> Michael
>
> Am 17.06.2014 08:25, schrieb Maxim Solodovnik:
> > Regarding 1
> > Could you please provide any repo steps?
> >
> >
> > On 16 June 2014 19:03, Vasiliy Degtyarev <vasya@unipro.ru
> > <ma...@unipro.ru>> wrote:
> >
> > Hello Michael,
> >
> > I have fixed second error for the 3.0.3 branch.
> >
> > Vasiliy.
> >
> >
> > On 16.06.2014 17:28, Michael Wuttke wrote:
> >
> > Hello Maxim,
> >
> > I've tested the latest om build with the following scenario:
> >
> > - om server:
> > * OS: debian wheezy
> > * db server: postgresql (version 9.3) -> a clean install
> > * OM version: branch 3.0.3 (build 27)
> >
> > - om server:
> > * OS: debian wheezy
> > * db server: postgresql (version 9.1)
> > * Moodle version: 2.7+ (build: 20140605) and
> > + om moodle plugin: version 1.7.1 - (build 2014051301)
> >
> > - user client:
> > * OS: ubuntu 14.04 LTS (trusty tahr)
> > * browser: FF 30.0 & Opera 12.16.1860
> >
> > Adding in OM a 'SOAP' user to create, modify or delete OM rooms
> via
> > moodle was not the problem. I also could change the settings of
> a OM
> > user (f.e. add or change the usergroup/organisation). The network
> > testing works now. Thanks. ;-)
> >
> > But two issues occurred during this test.
> >
> > 1. Sometimes I've got the following error message on the moodle
> > server,
> > when I tried to enter a new room (an interview room in this
> case):
> >
> > Can not find data record in database table course_modules.
> >
> > Debug info: SELECT id,course FROM {course_modules} WHERE id = ?
> > [array (
> > 0 => '6',
> > )]
> > Error code: invalidrecord
> >
> > Stack trace:
> > line 1451 of /lib/dml/moodle_database.php:
> > dml_missing_record_exception thrown
> > line 1427 of /lib/dml/moodle_database.php: call to
> > moodle_database->get_record___select()
> > line 7088 of /lib/accesslib.php: call to
> > moodle_database->get_record()
> > line 61 of /mod/openmeetings/view.php: call to
> > context_module::instance()
> >
> > 2. When I tried to change the OM settings/configuration via the
> > OM GUI:
> > Administration -> Configuration -> selecting the id 54
> > (redirect.url.for.external.__users) -> entering the Value
> > 'mymoodleurl'
> > and tried to save this entry, I've got an Internal error.
> >
> > See pastebin for the error messages:
> > http://pastebin.com/hY15zvqv
> >
> > Thanks,
> > Michael
> >
> > Am 14.06.2014 10:53, schrieb Maxim Solodovnik:
> >
> > Thanks for the detailed report!
> > build #27 should address first issue
> >
> > second was not reproducible here, could you please re-check?
> >
> >
> > On 13 June 2014 19:33, Michael Wuttke
> > <michael.wuttke@beuth-__hochschule.de
> > <ma...@beuth-hochschule.de>
> > <mailto:michael.wuttke@beuth-__hochschule.de
> > <ma...@beuth-hochschule.de>>> wrote:
> >
> > Hello Maxim,
> >
> > I've tested the branch 3.0.3 (build 26) now with a
> > clean postgresql
> > install. Two issues occurred during this test.
> >
> > 1. Adding a 'SOAP' user to create OM rooms via moodle
> > (version 2.7 and
> > om moodle plugin version 1.7.1 - build 2014051301) is
> > not a problem,
> > like I tested yesterday. But to open the new created OM
> > room via moodle
> > doesn't work. In the openmeetings.log file I found the
> > following error
> > messages:
> > http://pastebin.com/rpTfhJcW
> >
> > 2. When I tried to add the new soap user to a
> > organisation via the OM
> > GUI: Administration -> Usergroups -> selecting the
> > usergroup -> Add user
> > via the drop down menu If got an Internal error.
> >
> > In the openmeetings.log file I found the following
> > error messages:
> > http://pastebin.com/q0h1aR3G
> >
> > Thanks,
> > Michael
> >
> >
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
>
--
WBR
Maxim aka solomax
test of branch 3.0.3 (build 28)
Posted by Michael Wuttke <mi...@beuth-hochschule.de>.
Hello,
I've tested the latest om build with the following scenario:
- om server:
* OS: debian wheezy
* database server: postgresql (version 9.3)
* OM version: branch 3.0.3 (build 28)
* a clean install via cliadmin with
./admin.sh -i -v -file backup.zip -tz Europe/Berlin --drop
--skip-default-rooms --db-type postgresql --db-host somehost --db-name
somename --db-user someuser --db-pass somepass
- moodle server:
* OS: debian wheezy
* database server: postgresql (version 9.1)
* Moodle version: 2.7+ (build: 20140613) -> not a clean install
* om moodle plugin: version 1.7.1 - (build 2014051301)
- user client:
* OS: ubuntu 14.04 LTS (trusty tahr)
* browser: FF 30.0 & Opera 12.16.1860
Adding in OM a 'SOAP' user to create, modify or delete OM rooms via
moodle is not a problem, or changing the settings of a OM user.
But some issues occurred during the test.
1. I still get the following error message on the moodle server, when I
try to enter a new created om room (an interview room in this case; I
created a conference, a webinar and a interview room):
Can not find data record in database table course_modules.
Debug info: SELECT id,course FROM {course_modules} WHERE id = ?
[array (
0 => '6',
)]
Error code: invalidrecord
Stack trace:
line 1451 of /lib/dml/moodle_database.php:
dml_missing_record_exception thrown
line 1427 of /lib/dml/moodle_database.php: call to
moodle_database->get_record_select()
line 7088 of /lib/accesslib.php: call to
moodle_database->get_record()
line 61 of /mod/openmeetings/view.php: call to
context_module::instance()
2. When I try to add a user to a group via the OM GUI: Administration ->
Usergroups -> new record -> enter a Name for a new usergroup - this
works. But if I try to add a user to this new usergroup via the drop
down menu Add user and try then to select a user, I will get an Internal
error.
Please see the pastebin entry for the error message:
http://pastebin.com/ddm93jbS
3. Often I get a OutOfMemoryError: PermGen space in the red5.log
Please see also the pastebin entry for this error message:
http://pastebin.com/SL5gXDGw
Thanks,
Michael
Am 17.06.2014 08:25, schrieb Maxim Solodovnik:
> Regarding 1
> Could you please provide any repo steps?
>
>
> On 16 June 2014 19:03, Vasiliy Degtyarev <vasya@unipro.ru
> <ma...@unipro.ru>> wrote:
>
> Hello Michael,
>
> I have fixed second error for the 3.0.3 branch.
>
> Vasiliy.
>
>
> On 16.06.2014 17:28, Michael Wuttke wrote:
>
> Hello Maxim,
>
> I've tested the latest om build with the following scenario:
>
> - om server:
> * OS: debian wheezy
> * db server: postgresql (version 9.3) -> a clean install
> * OM version: branch 3.0.3 (build 27)
>
> - om server:
> * OS: debian wheezy
> * db server: postgresql (version 9.1)
> * Moodle version: 2.7+ (build: 20140605) and
> + om moodle plugin: version 1.7.1 - (build 2014051301)
>
> - user client:
> * OS: ubuntu 14.04 LTS (trusty tahr)
> * browser: FF 30.0 & Opera 12.16.1860
>
> Adding in OM a 'SOAP' user to create, modify or delete OM rooms via
> moodle was not the problem. I also could change the settings of a OM
> user (f.e. add or change the usergroup/organisation). The network
> testing works now. Thanks. ;-)
>
> But two issues occurred during this test.
>
> 1. Sometimes I've got the following error message on the moodle
> server,
> when I tried to enter a new room (an interview room in this case):
>
> Can not find data record in database table course_modules.
>
> Debug info: SELECT id,course FROM {course_modules} WHERE id = ?
> [array (
> 0 => '6',
> )]
> Error code: invalidrecord
>
> Stack trace:
> line 1451 of /lib/dml/moodle_database.php:
> dml_missing_record_exception thrown
> line 1427 of /lib/dml/moodle_database.php: call to
> moodle_database->get_record___select()
> line 7088 of /lib/accesslib.php: call to
> moodle_database->get_record()
> line 61 of /mod/openmeetings/view.php: call to
> context_module::instance()
>
> 2. When I tried to change the OM settings/configuration via the
> OM GUI:
> Administration -> Configuration -> selecting the id 54
> (redirect.url.for.external.__users) -> entering the Value
> 'mymoodleurl'
> and tried to save this entry, I've got an Internal error.
>
> See pastebin for the error messages:
> http://pastebin.com/hY15zvqv
>
> Thanks,
> Michael
>
> Am 14.06.2014 10:53, schrieb Maxim Solodovnik:
>
> Thanks for the detailed report!
> build #27 should address first issue
>
> second was not reproducible here, could you please re-check?
>
>
> On 13 June 2014 19:33, Michael Wuttke
> <michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-hochschule.de>
> <mailto:michael.wuttke@beuth-__hochschule.de
> <ma...@beuth-hochschule.de>>> wrote:
>
> Hello Maxim,
>
> I've tested the branch 3.0.3 (build 26) now with a
> clean postgresql
> install. Two issues occurred during this test.
>
> 1. Adding a 'SOAP' user to create OM rooms via moodle
> (version 2.7 and
> om moodle plugin version 1.7.1 - build 2014051301) is
> not a problem,
> like I tested yesterday. But to open the new created OM
> room via moodle
> doesn't work. In the openmeetings.log file I found the
> following error
> messages:
> http://pastebin.com/rpTfhJcW
>
> 2. When I tried to add the new soap user to a
> organisation via the OM
> GUI: Administration -> Usergroups -> selecting the
> usergroup -> Add user
> via the drop down menu If got an Internal error.
>
> In the openmeetings.log file I found the following
> error messages:
> http://pastebin.com/q0h1aR3G
>
> Thanks,
> Michael
>
>
>
>
>
> --
> WBR
> Maxim aka solomax
Re: test of branch 3.0.3 (build 27)
Posted by Maxim Solodovnik <so...@gmail.com>.
Regarding 1
Could you please provide any repo steps?
On 16 June 2014 19:03, Vasiliy Degtyarev <va...@unipro.ru> wrote:
> Hello Michael,
>
> I have fixed second error for the 3.0.3 branch.
>
> Vasiliy.
>
>
> On 16.06.2014 17:28, Michael Wuttke wrote:
>
>> Hello Maxim,
>>
>> I've tested the latest om build with the following scenario:
>>
>> - om server:
>> * OS: debian wheezy
>> * db server: postgresql (version 9.3) -> a clean install
>> * OM version: branch 3.0.3 (build 27)
>>
>> - om server:
>> * OS: debian wheezy
>> * db server: postgresql (version 9.1)
>> * Moodle version: 2.7+ (build: 20140605) and
>> + om moodle plugin: version 1.7.1 - (build 2014051301)
>>
>> - user client:
>> * OS: ubuntu 14.04 LTS (trusty tahr)
>> * browser: FF 30.0 & Opera 12.16.1860
>>
>> Adding in OM a 'SOAP' user to create, modify or delete OM rooms via
>> moodle was not the problem. I also could change the settings of a OM
>> user (f.e. add or change the usergroup/organisation). The network
>> testing works now. Thanks. ;-)
>>
>> But two issues occurred during this test.
>>
>> 1. Sometimes I've got the following error message on the moodle server,
>> when I tried to enter a new room (an interview room in this case):
>>
>> Can not find data record in database table course_modules.
>>
>> Debug info: SELECT id,course FROM {course_modules} WHERE id = ?
>> [array (
>> 0 => '6',
>> )]
>> Error code: invalidrecord
>>
>> Stack trace:
>> line 1451 of /lib/dml/moodle_database.php:
>> dml_missing_record_exception thrown
>> line 1427 of /lib/dml/moodle_database.php: call to
>> moodle_database->get_record_select()
>> line 7088 of /lib/accesslib.php: call to
>> moodle_database->get_record()
>> line 61 of /mod/openmeetings/view.php: call to
>> context_module::instance()
>>
>> 2. When I tried to change the OM settings/configuration via the OM GUI:
>> Administration -> Configuration -> selecting the id 54
>> (redirect.url.for.external.users) -> entering the Value 'mymoodleurl'
>> and tried to save this entry, I've got an Internal error.
>>
>> See pastebin for the error messages:
>> http://pastebin.com/hY15zvqv
>>
>> Thanks,
>> Michael
>>
>> Am 14.06.2014 10:53, schrieb Maxim Solodovnik:
>>
>>> Thanks for the detailed report!
>>> build #27 should address first issue
>>>
>>> second was not reproducible here, could you please re-check?
>>>
>>>
>>> On 13 June 2014 19:33, Michael Wuttke
>>> <michael.wuttke@beuth-hochschule.de
>>> <ma...@beuth-hochschule.de>> wrote:
>>>
>>> Hello Maxim,
>>>
>>> I've tested the branch 3.0.3 (build 26) now with a clean postgresql
>>> install. Two issues occurred during this test.
>>>
>>> 1. Adding a 'SOAP' user to create OM rooms via moodle (version 2.7
>>> and
>>> om moodle plugin version 1.7.1 - build 2014051301) is not a problem,
>>> like I tested yesterday. But to open the new created OM room via
>>> moodle
>>> doesn't work. In the openmeetings.log file I found the following
>>> error
>>> messages:
>>> http://pastebin.com/rpTfhJcW
>>>
>>> 2. When I tried to add the new soap user to a organisation via the
>>> OM
>>> GUI: Administration -> Usergroups -> selecting the usergroup -> Add
>>> user
>>> via the drop down menu If got an Internal error.
>>>
>>> In the openmeetings.log file I found the following error messages:
>>> http://pastebin.com/q0h1aR3G
>>>
>>> Thanks,
>>> Michael
>>>
>>
>
--
WBR
Maxim aka solomax
Re: test of branch 3.0.3 (build 27)
Posted by Vasiliy Degtyarev <va...@unipro.ru>.
Hello Michael,
I have fixed second error for the 3.0.3 branch.
Vasiliy.
On 16.06.2014 17:28, Michael Wuttke wrote:
> Hello Maxim,
>
> I've tested the latest om build with the following scenario:
>
> - om server:
> * OS: debian wheezy
> * db server: postgresql (version 9.3) -> a clean install
> * OM version: branch 3.0.3 (build 27)
>
> - om server:
> * OS: debian wheezy
> * db server: postgresql (version 9.1)
> * Moodle version: 2.7+ (build: 20140605) and
> + om moodle plugin: version 1.7.1 - (build 2014051301)
>
> - user client:
> * OS: ubuntu 14.04 LTS (trusty tahr)
> * browser: FF 30.0 & Opera 12.16.1860
>
> Adding in OM a 'SOAP' user to create, modify or delete OM rooms via
> moodle was not the problem. I also could change the settings of a OM
> user (f.e. add or change the usergroup/organisation). The network
> testing works now. Thanks. ;-)
>
> But two issues occurred during this test.
>
> 1. Sometimes I've got the following error message on the moodle server,
> when I tried to enter a new room (an interview room in this case):
>
> Can not find data record in database table course_modules.
>
> Debug info: SELECT id,course FROM {course_modules} WHERE id = ?
> [array (
> 0 => '6',
> )]
> Error code: invalidrecord
>
> Stack trace:
> line 1451 of /lib/dml/moodle_database.php:
> dml_missing_record_exception thrown
> line 1427 of /lib/dml/moodle_database.php: call to
> moodle_database->get_record_select()
> line 7088 of /lib/accesslib.php: call to moodle_database->get_record()
> line 61 of /mod/openmeetings/view.php: call to
> context_module::instance()
>
> 2. When I tried to change the OM settings/configuration via the OM GUI:
> Administration -> Configuration -> selecting the id 54
> (redirect.url.for.external.users) -> entering the Value 'mymoodleurl'
> and tried to save this entry, I've got an Internal error.
>
> See pastebin for the error messages:
> http://pastebin.com/hY15zvqv
>
> Thanks,
> Michael
>
> Am 14.06.2014 10:53, schrieb Maxim Solodovnik:
>> Thanks for the detailed report!
>> build #27 should address first issue
>>
>> second was not reproducible here, could you please re-check?
>>
>>
>> On 13 June 2014 19:33, Michael Wuttke
>> <michael.wuttke@beuth-hochschule.de
>> <ma...@beuth-hochschule.de>> wrote:
>>
>> Hello Maxim,
>>
>> I've tested the branch 3.0.3 (build 26) now with a clean postgresql
>> install. Two issues occurred during this test.
>>
>> 1. Adding a 'SOAP' user to create OM rooms via moodle (version 2.7 and
>> om moodle plugin version 1.7.1 - build 2014051301) is not a problem,
>> like I tested yesterday. But to open the new created OM room via moodle
>> doesn't work. In the openmeetings.log file I found the following error
>> messages:
>> http://pastebin.com/rpTfhJcW
>>
>> 2. When I tried to add the new soap user to a organisation via the OM
>> GUI: Administration -> Usergroups -> selecting the usergroup -> Add user
>> via the drop down menu If got an Internal error.
>>
>> In the openmeetings.log file I found the following error messages:
>> http://pastebin.com/q0h1aR3G
>>
>> Thanks,
>> Michael
test of branch 3.0.3 (build 27)
Posted by Michael Wuttke <mi...@beuth-hochschule.de>.
Hello Maxim,
I've tested the latest om build with the following scenario:
- om server:
* OS: debian wheezy
* db server: postgresql (version 9.3) -> a clean install
* OM version: branch 3.0.3 (build 27)
- om server:
* OS: debian wheezy
* db server: postgresql (version 9.1)
* Moodle version: 2.7+ (build: 20140605) and
+ om moodle plugin: version 1.7.1 - (build 2014051301)
- user client:
* OS: ubuntu 14.04 LTS (trusty tahr)
* browser: FF 30.0 & Opera 12.16.1860
Adding in OM a 'SOAP' user to create, modify or delete OM rooms via
moodle was not the problem. I also could change the settings of a OM
user (f.e. add or change the usergroup/organisation). The network
testing works now. Thanks. ;-)
But two issues occurred during this test.
1. Sometimes I've got the following error message on the moodle server,
when I tried to enter a new room (an interview room in this case):
Can not find data record in database table course_modules.
Debug info: SELECT id,course FROM {course_modules} WHERE id = ?
[array (
0 => '6',
)]
Error code: invalidrecord
Stack trace:
line 1451 of /lib/dml/moodle_database.php:
dml_missing_record_exception thrown
line 1427 of /lib/dml/moodle_database.php: call to
moodle_database->get_record_select()
line 7088 of /lib/accesslib.php: call to moodle_database->get_record()
line 61 of /mod/openmeetings/view.php: call to
context_module::instance()
2. When I tried to change the OM settings/configuration via the OM GUI:
Administration -> Configuration -> selecting the id 54
(redirect.url.for.external.users) -> entering the Value 'mymoodleurl'
and tried to save this entry, I've got an Internal error.
See pastebin for the error messages:
http://pastebin.com/hY15zvqv
Thanks,
Michael
Am 14.06.2014 10:53, schrieb Maxim Solodovnik:
> Thanks for the detailed report!
> build #27 should address first issue
>
> second was not reproducible here, could you please re-check?
>
>
> On 13 June 2014 19:33, Michael Wuttke
> <michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>> wrote:
>
> Hello Maxim,
>
> I've tested the branch 3.0.3 (build 26) now with a clean postgresql
> install. Two issues occurred during this test.
>
> 1. Adding a 'SOAP' user to create OM rooms via moodle (version 2.7 and
> om moodle plugin version 1.7.1 - build 2014051301) is not a problem,
> like I tested yesterday. But to open the new created OM room via moodle
> doesn't work. In the openmeetings.log file I found the following error
> messages:
> http://pastebin.com/rpTfhJcW
>
> 2. When I tried to add the new soap user to a organisation via the OM
> GUI: Administration -> Usergroups -> selecting the usergroup -> Add user
> via the drop down menu If got an Internal error.
>
> In the openmeetings.log file I found the following error messages:
> http://pastebin.com/q0h1aR3G
>
> Thanks,
> Michael
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Maxim Solodovnik <so...@gmail.com>.
Thanks for the detailed report!
build #27 should address first issue
second was not reproducible here, could you please re-check?
On 13 June 2014 19:33, Michael Wuttke <mi...@beuth-hochschule.de>
wrote:
> Hello Maxim,
>
> I've tested the branch 3.0.3 (build 26) now with a clean postgresql
> install. Two issues occurred during this test.
>
> 1. Adding a 'SOAP' user to create OM rooms via moodle (version 2.7 and
> om moodle plugin version 1.7.1 - build 2014051301) is not a problem,
> like I tested yesterday. But to open the new created OM room via moodle
> doesn't work. In the openmeetings.log file I found the following error
> messages:
> http://pastebin.com/rpTfhJcW
>
> 2. When I tried to add the new soap user to a organisation via the OM
> GUI: Administration -> Usergroups -> selecting the usergroup -> Add user
> via the drop down menu If got an Internal error.
>
> In the openmeetings.log file I found the following error messages:
> http://pastebin.com/q0h1aR3G
>
> Thanks,
> Michael
>
> Am 12.06.2014 20:30, schrieb Maxim Solodovnik:
> > should be fixed
> > Committed revision 1602257.
> >
> > will create another build later this week
> >
> >
> > On 13 June 2014 01:08, Maxim Solodovnik <solomax666@gmail.com
> > <ma...@gmail.com>> wrote:
> >
> > ups :( forgot to check it
> > will do
> >
> >
> > On 13 June 2014 01:08, Michael Wuttke <mwuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>> wrote:
> >
> > Hello Maxim,
> >
> > I've tested the branch 3.0.3 (build 26) with a clean mysql
> install.
> > The Admin user has now the admin rights. Also the logout is
> possible
> > now. Adding a 'SOAP' user to create OM rooms via moodle is now
> > possible.
> > But the Network testing still doesn't work: Access denied.
> >
> > Thanks,
> > Michael
> >
> > Am 12.06.14 10:09, schrieb Maxim Solodovnik:
> > > should be fixed
> > > please try build #26
> > >
> > >
> > > On 11 June 2014 16:14, Maxim Solodovnik <solomax666@gmail.com
> > <ma...@gmail.com>> wrote:
> > >
> > >> Thanks!
> > >> really appreciate your testing efforts :)
> > >> Will try to fix it ASAP
> > >>
> > >>
> > >> On 11 June 2014 16:09, Juan Carrera <carreraj@unizar.es
> > <ma...@unizar.es>> wrote:
> > >>
> > >>> Hi, i.ve <http://i.ve> tested on a clean mysql install
> > (branch 3.0.x)
> > >>> Admin user has no admin rights, only 'Room', 'Login' and
> > 'Dashboard'.
> > >>> Logout is failing. Adding 'Admin' RIGTH0 to user_id 1 in
> > om_user_right
> > >>> table doesn't work.
> > >>> Network testing doesn't work for me /Access denied).
> > >>>
> > >>>
> > >>>
> > >>> El 10/06/14 18:58, Maxim Solodovnik escribió:
> > >>>
> > >>> Can you please check if the implemented solution works as
> > expected?
> > >>> Latest 3.0.3 build contains the changes
> > >>>
> > >>>
> > >>> On 2 June 2014 17:31, Michael Wuttke
> > <michael.wuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>>
> > >>> wrote:
> > >>>
> > >>>> Hello Maxim,
> > >>>>
> > >>>> I think so too, using OM via moodle or directly via LDAP
> > like Juan in
> > >>>> the jira issue nr. 1007 described - with the same
> > credentials would be
> > >>>> great.
> > >>>>
> > >>>> Thanks & Greetings,
> > >>>> Michael
> > >>>>
> > >>>> Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
> > >>>> > Hello All,
> > >>>>>
> > >>>>> Due to multiple requests and issues (please see [1], [2],
> > [3]) I would
> > >>>>> like to change User object (remove status and "user
> > level") and add
> > >>>>> Permissions.
> > >>>>>
> > >>>>> As I can see the permissions should be
> > >>>>> Admin == access to Admin module
> > >>>>> Room == enter the room
> > >>>>> Dashboard == access the whiteboard
> > >>>>> Login == login to Om internal DB
> > >>>>> Soap == use rest/soap calls
> > >>>>>
> > >>>>> for example
> > >>>>> current "regular" user will have all permissions except
> > for Admin and
> > >>>> Soap
> > >>>>> current "soap" user will have soap permission only
> > >>>>> current OAuth user will have no Login parmission
> > >>>>>
> > >>>>> The proposed system looks extendable and should cover all
> > current needs
> > >>>>>
> > >>>>> I'm going to implement it in 3.0.3 and 3.1.0
> > >>>>>
> > >>>>> Please let me know if you have any concerns/corrections
> > >>>>>
> > >>>>> Thanks in advance
> > >>>>>
> > >>>>> [1]
> http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> > >>>>> [2]
> https://issues.apache.org/jira/browse/OPENMEETINGS-1007
> > >>>>> [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
> > >>>>>
> > >>>>> --
> > >>>>> WBR
> > >>>>> Maxim aka solomax
> > >>>>
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> WBR
> > >>> Maxim aka solomax
> > >>>
> > >>>
> > >>> --
> > >>> [image: Logotipo del servicio de informática y
> comunicaciones.
> > >>> Universidad Zaragoza]
> > >>>
> > >>> *Juan Ramón Carrera Marcén *
> > >>> * Área de gestión*
> > >>> Residencia de profesores
> > >>> Pedro Cerbuna 12, 50009 Zaragoza
> > >>> Tel. (34) 876553689
> > >>> carreraj@unizar.es <ma...@unizar.es>
> > >>>
> > >>> [image: unizar.es <http://unizar.es>]
> > >>>
>
>
--
WBR
Maxim aka solomax
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Michael Wuttke <mi...@beuth-hochschule.de>.
Hello Maxim,
I've tested the branch 3.0.3 (build 26) now with a clean postgresql
install. Two issues occurred during this test.
1. Adding a 'SOAP' user to create OM rooms via moodle (version 2.7 and
om moodle plugin version 1.7.1 - build 2014051301) is not a problem,
like I tested yesterday. But to open the new created OM room via moodle
doesn't work. In the openmeetings.log file I found the following error
messages:
http://pastebin.com/rpTfhJcW
2. When I tried to add the new soap user to a organisation via the OM
GUI: Administration -> Usergroups -> selecting the usergroup -> Add user
via the drop down menu If got an Internal error.
In the openmeetings.log file I found the following error messages:
http://pastebin.com/q0h1aR3G
Thanks,
Michael
Am 12.06.2014 20:30, schrieb Maxim Solodovnik:
> should be fixed
> Committed revision 1602257.
>
> will create another build later this week
>
>
> On 13 June 2014 01:08, Maxim Solodovnik <solomax666@gmail.com
> <ma...@gmail.com>> wrote:
>
> ups :( forgot to check it
> will do
>
>
> On 13 June 2014 01:08, Michael Wuttke <mwuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>> wrote:
>
> Hello Maxim,
>
> I've tested the branch 3.0.3 (build 26) with a clean mysql install.
> The Admin user has now the admin rights. Also the logout is possible
> now. Adding a 'SOAP' user to create OM rooms via moodle is now
> possible.
> But the Network testing still doesn't work: Access denied.
>
> Thanks,
> Michael
>
> Am 12.06.14 10:09, schrieb Maxim Solodovnik:
> > should be fixed
> > please try build #26
> >
> >
> > On 11 June 2014 16:14, Maxim Solodovnik <solomax666@gmail.com
> <ma...@gmail.com>> wrote:
> >
> >> Thanks!
> >> really appreciate your testing efforts :)
> >> Will try to fix it ASAP
> >>
> >>
> >> On 11 June 2014 16:09, Juan Carrera <carreraj@unizar.es
> <ma...@unizar.es>> wrote:
> >>
> >>> Hi, i.ve <http://i.ve> tested on a clean mysql install
> (branch 3.0.x)
> >>> Admin user has no admin rights, only 'Room', 'Login' and
> 'Dashboard'.
> >>> Logout is failing. Adding 'Admin' RIGTH0 to user_id 1 in
> om_user_right
> >>> table doesn't work.
> >>> Network testing doesn't work for me /Access denied).
> >>>
> >>>
> >>>
> >>> El 10/06/14 18:58, Maxim Solodovnik escribió:
> >>>
> >>> Can you please check if the implemented solution works as
> expected?
> >>> Latest 3.0.3 build contains the changes
> >>>
> >>>
> >>> On 2 June 2014 17:31, Michael Wuttke
> <michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>
> >>> wrote:
> >>>
> >>>> Hello Maxim,
> >>>>
> >>>> I think so too, using OM via moodle or directly via LDAP
> like Juan in
> >>>> the jira issue nr. 1007 described - with the same
> credentials would be
> >>>> great.
> >>>>
> >>>> Thanks & Greetings,
> >>>> Michael
> >>>>
> >>>> Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
> >>>> > Hello All,
> >>>>>
> >>>>> Due to multiple requests and issues (please see [1], [2],
> [3]) I would
> >>>>> like to change User object (remove status and "user
> level") and add
> >>>>> Permissions.
> >>>>>
> >>>>> As I can see the permissions should be
> >>>>> Admin == access to Admin module
> >>>>> Room == enter the room
> >>>>> Dashboard == access the whiteboard
> >>>>> Login == login to Om internal DB
> >>>>> Soap == use rest/soap calls
> >>>>>
> >>>>> for example
> >>>>> current "regular" user will have all permissions except
> for Admin and
> >>>> Soap
> >>>>> current "soap" user will have soap permission only
> >>>>> current OAuth user will have no Login parmission
> >>>>>
> >>>>> The proposed system looks extendable and should cover all
> current needs
> >>>>>
> >>>>> I'm going to implement it in 3.0.3 and 3.1.0
> >>>>>
> >>>>> Please let me know if you have any concerns/corrections
> >>>>>
> >>>>> Thanks in advance
> >>>>>
> >>>>> [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> >>>>> [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
> >>>>> [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
> >>>>>
> >>>>> --
> >>>>> WBR
> >>>>> Maxim aka solomax
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> WBR
> >>> Maxim aka solomax
> >>>
> >>>
> >>> --
> >>> [image: Logotipo del servicio de informática y comunicaciones.
> >>> Universidad Zaragoza]
> >>>
> >>> *Juan Ramón Carrera Marcén *
> >>> * Área de gestión*
> >>> Residencia de profesores
> >>> Pedro Cerbuna 12, 50009 Zaragoza
> >>> Tel. (34) 876553689
> >>> carreraj@unizar.es <ma...@unizar.es>
> >>>
> >>> [image: unizar.es <http://unizar.es>]
> >>>
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Maxim Solodovnik <so...@gmail.com>.
should be fixed
Committed revision 1602257.
will create another build later this week
On 13 June 2014 01:08, Maxim Solodovnik <so...@gmail.com> wrote:
> ups :( forgot to check it
> will do
>
>
> On 13 June 2014 01:08, Michael Wuttke <mw...@beuth-hochschule.de> wrote:
>
>> Hello Maxim,
>>
>> I've tested the branch 3.0.3 (build 26) with a clean mysql install.
>> The Admin user has now the admin rights. Also the logout is possible
>> now. Adding a 'SOAP' user to create OM rooms via moodle is now possible.
>> But the Network testing still doesn't work: Access denied.
>>
>> Thanks,
>> Michael
>>
>> Am 12.06.14 10:09, schrieb Maxim Solodovnik:
>> > should be fixed
>> > please try build #26
>> >
>> >
>> > On 11 June 2014 16:14, Maxim Solodovnik <so...@gmail.com> wrote:
>> >
>> >> Thanks!
>> >> really appreciate your testing efforts :)
>> >> Will try to fix it ASAP
>> >>
>> >>
>> >> On 11 June 2014 16:09, Juan Carrera <ca...@unizar.es> wrote:
>> >>
>> >>> Hi, i.ve tested on a clean mysql install (branch 3.0.x)
>> >>> Admin user has no admin rights, only 'Room', 'Login' and 'Dashboard'.
>> >>> Logout is failing. Adding 'Admin' RIGTH0 to user_id 1 in om_user_right
>> >>> table doesn't work.
>> >>> Network testing doesn't work for me /Access denied).
>> >>>
>> >>>
>> >>>
>> >>> El 10/06/14 18:58, Maxim Solodovnik escribió:
>> >>>
>> >>> Can you please check if the implemented solution works as expected?
>> >>> Latest 3.0.3 build contains the changes
>> >>>
>> >>>
>> >>> On 2 June 2014 17:31, Michael Wuttke <
>> michael.wuttke@beuth-hochschule.de>
>> >>> wrote:
>> >>>
>> >>>> Hello Maxim,
>> >>>>
>> >>>> I think so too, using OM via moodle or directly via LDAP like Juan in
>> >>>> the jira issue nr. 1007 described - with the same credentials would
>> be
>> >>>> great.
>> >>>>
>> >>>> Thanks & Greetings,
>> >>>> Michael
>> >>>>
>> >>>> Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
>> >>>> > Hello All,
>> >>>>>
>> >>>>> Due to multiple requests and issues (please see [1], [2], [3]) I
>> would
>> >>>>> like to change User object (remove status and "user level") and add
>> >>>>> Permissions.
>> >>>>>
>> >>>>> As I can see the permissions should be
>> >>>>> Admin == access to Admin module
>> >>>>> Room == enter the room
>> >>>>> Dashboard == access the whiteboard
>> >>>>> Login == login to Om internal DB
>> >>>>> Soap == use rest/soap calls
>> >>>>>
>> >>>>> for example
>> >>>>> current "regular" user will have all permissions except for Admin
>> and
>> >>>> Soap
>> >>>>> current "soap" user will have soap permission only
>> >>>>> current OAuth user will have no Login parmission
>> >>>>>
>> >>>>> The proposed system looks extendable and should cover all current
>> needs
>> >>>>>
>> >>>>> I'm going to implement it in 3.0.3 and 3.1.0
>> >>>>>
>> >>>>> Please let me know if you have any concerns/corrections
>> >>>>>
>> >>>>> Thanks in advance
>> >>>>>
>> >>>>> [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
>> >>>>> [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
>> >>>>> [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
>> >>>>>
>> >>>>> --
>> >>>>> WBR
>> >>>>> Maxim aka solomax
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> WBR
>> >>> Maxim aka solomax
>> >>>
>> >>>
>> >>> --
>> >>> [image: Logotipo del servicio de informática y comunicaciones.
>> >>> Universidad Zaragoza]
>> >>>
>> >>> *Juan Ramón Carrera Marcén *
>> >>> * Área de gestión*
>> >>> Residencia de profesores
>> >>> Pedro Cerbuna 12, 50009 Zaragoza
>> >>> Tel. (34) 876553689
>> >>> carreraj@unizar.es
>> >>>
>> >>> [image: unizar.es]
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> WBR
>> >> Maxim aka solomax
>> >>
>> >
>> >
>> >
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Maxim Solodovnik <so...@gmail.com>.
ups :( forgot to check it
will do
On 13 June 2014 01:08, Michael Wuttke <mw...@beuth-hochschule.de> wrote:
> Hello Maxim,
>
> I've tested the branch 3.0.3 (build 26) with a clean mysql install.
> The Admin user has now the admin rights. Also the logout is possible
> now. Adding a 'SOAP' user to create OM rooms via moodle is now possible.
> But the Network testing still doesn't work: Access denied.
>
> Thanks,
> Michael
>
> Am 12.06.14 10:09, schrieb Maxim Solodovnik:
> > should be fixed
> > please try build #26
> >
> >
> > On 11 June 2014 16:14, Maxim Solodovnik <so...@gmail.com> wrote:
> >
> >> Thanks!
> >> really appreciate your testing efforts :)
> >> Will try to fix it ASAP
> >>
> >>
> >> On 11 June 2014 16:09, Juan Carrera <ca...@unizar.es> wrote:
> >>
> >>> Hi, i.ve tested on a clean mysql install (branch 3.0.x)
> >>> Admin user has no admin rights, only 'Room', 'Login' and 'Dashboard'.
> >>> Logout is failing. Adding 'Admin' RIGTH0 to user_id 1 in om_user_right
> >>> table doesn't work.
> >>> Network testing doesn't work for me /Access denied).
> >>>
> >>>
> >>>
> >>> El 10/06/14 18:58, Maxim Solodovnik escribió:
> >>>
> >>> Can you please check if the implemented solution works as expected?
> >>> Latest 3.0.3 build contains the changes
> >>>
> >>>
> >>> On 2 June 2014 17:31, Michael Wuttke <
> michael.wuttke@beuth-hochschule.de>
> >>> wrote:
> >>>
> >>>> Hello Maxim,
> >>>>
> >>>> I think so too, using OM via moodle or directly via LDAP like Juan in
> >>>> the jira issue nr. 1007 described - with the same credentials would be
> >>>> great.
> >>>>
> >>>> Thanks & Greetings,
> >>>> Michael
> >>>>
> >>>> Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
> >>>> > Hello All,
> >>>>>
> >>>>> Due to multiple requests and issues (please see [1], [2], [3]) I
> would
> >>>>> like to change User object (remove status and "user level") and add
> >>>>> Permissions.
> >>>>>
> >>>>> As I can see the permissions should be
> >>>>> Admin == access to Admin module
> >>>>> Room == enter the room
> >>>>> Dashboard == access the whiteboard
> >>>>> Login == login to Om internal DB
> >>>>> Soap == use rest/soap calls
> >>>>>
> >>>>> for example
> >>>>> current "regular" user will have all permissions except for Admin and
> >>>> Soap
> >>>>> current "soap" user will have soap permission only
> >>>>> current OAuth user will have no Login parmission
> >>>>>
> >>>>> The proposed system looks extendable and should cover all current
> needs
> >>>>>
> >>>>> I'm going to implement it in 3.0.3 and 3.1.0
> >>>>>
> >>>>> Please let me know if you have any concerns/corrections
> >>>>>
> >>>>> Thanks in advance
> >>>>>
> >>>>> [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> >>>>> [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
> >>>>> [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
> >>>>>
> >>>>> --
> >>>>> WBR
> >>>>> Maxim aka solomax
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> WBR
> >>> Maxim aka solomax
> >>>
> >>>
> >>> --
> >>> [image: Logotipo del servicio de informática y comunicaciones.
> >>> Universidad Zaragoza]
> >>>
> >>> *Juan Ramón Carrera Marcén *
> >>> * Área de gestión*
> >>> Residencia de profesores
> >>> Pedro Cerbuna 12, 50009 Zaragoza
> >>> Tel. (34) 876553689
> >>> carreraj@unizar.es
> >>>
> >>> [image: unizar.es]
> >>>
> >>
> >>
> >>
> >> --
> >> WBR
> >> Maxim aka solomax
> >>
> >
> >
> >
>
--
WBR
Maxim aka solomax
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Michael Wuttke <mw...@beuth-hochschule.de>.
Hello Maxim,
I've tested the branch 3.0.3 (build 26) with a clean mysql install.
The Admin user has now the admin rights. Also the logout is possible
now. Adding a 'SOAP' user to create OM rooms via moodle is now possible.
But the Network testing still doesn't work: Access denied.
Thanks,
Michael
Am 12.06.14 10:09, schrieb Maxim Solodovnik:
> should be fixed
> please try build #26
>
>
> On 11 June 2014 16:14, Maxim Solodovnik <so...@gmail.com> wrote:
>
>> Thanks!
>> really appreciate your testing efforts :)
>> Will try to fix it ASAP
>>
>>
>> On 11 June 2014 16:09, Juan Carrera <ca...@unizar.es> wrote:
>>
>>> Hi, i.ve tested on a clean mysql install (branch 3.0.x)
>>> Admin user has no admin rights, only 'Room', 'Login' and 'Dashboard'.
>>> Logout is failing. Adding 'Admin' RIGTH0 to user_id 1 in om_user_right
>>> table doesn't work.
>>> Network testing doesn't work for me /Access denied).
>>>
>>>
>>>
>>> El 10/06/14 18:58, Maxim Solodovnik escribió:
>>>
>>> Can you please check if the implemented solution works as expected?
>>> Latest 3.0.3 build contains the changes
>>>
>>>
>>> On 2 June 2014 17:31, Michael Wuttke <mi...@beuth-hochschule.de>
>>> wrote:
>>>
>>>> Hello Maxim,
>>>>
>>>> I think so too, using OM via moodle or directly via LDAP like Juan in
>>>> the jira issue nr. 1007 described - with the same credentials would be
>>>> great.
>>>>
>>>> Thanks & Greetings,
>>>> Michael
>>>>
>>>> Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
>>>> > Hello All,
>>>>>
>>>>> Due to multiple requests and issues (please see [1], [2], [3]) I would
>>>>> like to change User object (remove status and "user level") and add
>>>>> Permissions.
>>>>>
>>>>> As I can see the permissions should be
>>>>> Admin == access to Admin module
>>>>> Room == enter the room
>>>>> Dashboard == access the whiteboard
>>>>> Login == login to Om internal DB
>>>>> Soap == use rest/soap calls
>>>>>
>>>>> for example
>>>>> current "regular" user will have all permissions except for Admin and
>>>> Soap
>>>>> current "soap" user will have soap permission only
>>>>> current OAuth user will have no Login parmission
>>>>>
>>>>> The proposed system looks extendable and should cover all current needs
>>>>>
>>>>> I'm going to implement it in 3.0.3 and 3.1.0
>>>>>
>>>>> Please let me know if you have any concerns/corrections
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
>>>>> [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
>>>>> [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
>>>>>
>>>>> --
>>>>> WBR
>>>>> Maxim aka solomax
>>>>
>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>>
>>> --
>>> [image: Logotipo del servicio de informática y comunicaciones.
>>> Universidad Zaragoza]
>>>
>>> *Juan Ramón Carrera Marcén *
>>> * Área de gestión*
>>> Residencia de profesores
>>> Pedro Cerbuna 12, 50009 Zaragoza
>>> Tel. (34) 876553689
>>> carreraj@unizar.es
>>>
>>> [image: unizar.es]
>>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
>
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Maxim Solodovnik <so...@gmail.com>.
should be fixed
please try build #26
On 11 June 2014 16:14, Maxim Solodovnik <so...@gmail.com> wrote:
> Thanks!
> really appreciate your testing efforts :)
> Will try to fix it ASAP
>
>
> On 11 June 2014 16:09, Juan Carrera <ca...@unizar.es> wrote:
>
>> Hi, i.ve tested on a clean mysql install (branch 3.0.x)
>> Admin user has no admin rights, only 'Room', 'Login' and 'Dashboard'.
>> Logout is failing. Adding 'Admin' RIGTH0 to user_id 1 in om_user_right
>> table doesn't work.
>> Network testing doesn't work for me /Access denied).
>>
>>
>>
>> El 10/06/14 18:58, Maxim Solodovnik escribió:
>>
>> Can you please check if the implemented solution works as expected?
>> Latest 3.0.3 build contains the changes
>>
>>
>> On 2 June 2014 17:31, Michael Wuttke <mi...@beuth-hochschule.de>
>> wrote:
>>
>>> Hello Maxim,
>>>
>>> I think so too, using OM via moodle or directly via LDAP like Juan in
>>> the jira issue nr. 1007 described - with the same credentials would be
>>> great.
>>>
>>> Thanks & Greetings,
>>> Michael
>>>
>>> Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
>>> > Hello All,
>>> >
>>> > Due to multiple requests and issues (please see [1], [2], [3]) I would
>>> > like to change User object (remove status and "user level") and add
>>> > Permissions.
>>> >
>>> > As I can see the permissions should be
>>> > Admin == access to Admin module
>>> > Room == enter the room
>>> > Dashboard == access the whiteboard
>>> > Login == login to Om internal DB
>>> > Soap == use rest/soap calls
>>> >
>>> > for example
>>> > current "regular" user will have all permissions except for Admin and
>>> Soap
>>> > current "soap" user will have soap permission only
>>> > current OAuth user will have no Login parmission
>>> >
>>> > The proposed system looks extendable and should cover all current needs
>>> >
>>> > I'm going to implement it in 3.0.3 and 3.1.0
>>> >
>>> > Please let me know if you have any concerns/corrections
>>> >
>>> > Thanks in advance
>>> >
>>> > [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
>>> > [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
>>> > [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
>>> >
>>> > --
>>> > WBR
>>> > Maxim aka solomax
>>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>>
>> --
>> [image: Logotipo del servicio de informática y comunicaciones.
>> Universidad Zaragoza]
>>
>> *Juan Ramón Carrera Marcén *
>> * Área de gestión*
>> Residencia de profesores
>> Pedro Cerbuna 12, 50009 Zaragoza
>> Tel. (34) 876553689
>> carreraj@unizar.es
>>
>> [image: unizar.es]
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Maxim Solodovnik <so...@gmail.com>.
Thanks!
really appreciate your testing efforts :)
Will try to fix it ASAP
On 11 June 2014 16:09, Juan Carrera <ca...@unizar.es> wrote:
> Hi, i.ve tested on a clean mysql install (branch 3.0.x)
> Admin user has no admin rights, only 'Room', 'Login' and 'Dashboard'.
> Logout is failing. Adding 'Admin' RIGTH0 to user_id 1 in om_user_right
> table doesn't work.
> Network testing doesn't work for me /Access denied).
>
>
>
> El 10/06/14 18:58, Maxim Solodovnik escribió:
>
> Can you please check if the implemented solution works as expected?
> Latest 3.0.3 build contains the changes
>
>
> On 2 June 2014 17:31, Michael Wuttke <mi...@beuth-hochschule.de>
> wrote:
>
>> Hello Maxim,
>>
>> I think so too, using OM via moodle or directly via LDAP like Juan in
>> the jira issue nr. 1007 described - with the same credentials would be
>> great.
>>
>> Thanks & Greetings,
>> Michael
>>
>> Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
>> > Hello All,
>> >
>> > Due to multiple requests and issues (please see [1], [2], [3]) I would
>> > like to change User object (remove status and "user level") and add
>> > Permissions.
>> >
>> > As I can see the permissions should be
>> > Admin == access to Admin module
>> > Room == enter the room
>> > Dashboard == access the whiteboard
>> > Login == login to Om internal DB
>> > Soap == use rest/soap calls
>> >
>> > for example
>> > current "regular" user will have all permissions except for Admin and
>> Soap
>> > current "soap" user will have soap permission only
>> > current OAuth user will have no Login parmission
>> >
>> > The proposed system looks extendable and should cover all current needs
>> >
>> > I'm going to implement it in 3.0.3 and 3.1.0
>> >
>> > Please let me know if you have any concerns/corrections
>> >
>> > Thanks in advance
>> >
>> > [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
>> > [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
>> > [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
>> >
>> > --
>> > WBR
>> > Maxim aka solomax
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>
>
> --
> [image: Logotipo del servicio de informática y comunicaciones.
> Universidad Zaragoza]
>
> *Juan Ramón Carrera Marcén *
> * Área de gestión*
> Residencia de profesores
> Pedro Cerbuna 12, 50009 Zaragoza
> Tel. (34) 876553689
> carreraj@unizar.es
>
> [image: unizar.es]
>
--
WBR
Maxim aka solomax
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Juan Carrera <ca...@unizar.es>.
Hi, i.ve tested on a clean mysql install (branch 3.0.x)
Admin user has no admin rights, only 'Room', 'Login' and 'Dashboard'.
Logout is failing. Adding 'Admin' RIGTH0 to user_id 1 in om_user_right
table doesn't work.
Network testing doesn't work for me /Access denied).
El 10/06/14 18:58, Maxim Solodovnik escribió:
> Can you please check if the implemented solution works as expected?
> Latest 3.0.3 build contains the changes
>
>
> On 2 June 2014 17:31, Michael Wuttke
> <michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>> wrote:
>
> Hello Maxim,
>
> I think so too, using OM via moodle or directly via LDAP like Juan in
> the jira issue nr. 1007 described - with the same credentials would be
> great.
>
> Thanks & Greetings,
> Michael
>
> Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
> > Hello All,
> >
> > Due to multiple requests and issues (please see [1], [2], [3]) I
> would
> > like to change User object (remove status and "user level") and add
> > Permissions.
> >
> > As I can see the permissions should be
> > Admin == access to Admin module
> > Room == enter the room
> > Dashboard == access the whiteboard
> > Login == login to Om internal DB
> > Soap == use rest/soap calls
> >
> > for example
> > current "regular" user will have all permissions except for
> Admin and Soap
> > current "soap" user will have soap permission only
> > current OAuth user will have no Login parmission
> >
> > The proposed system looks extendable and should cover all
> current needs
> >
> > I'm going to implement it in 3.0.3 and 3.1.0
> >
> > Please let me know if you have any concerns/corrections
> >
> > Thanks in advance
> >
> > [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> > [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
> > [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
> >
> > --
> > WBR
> > Maxim aka solomax
>
>
>
>
> --
> WBR
> Maxim aka solomax
--
Logotipo del servicio de informática y comunicaciones. Universidad Zaragoza
*Juan Ramón Carrera Marcén * *
Área de gestión*
Residencia de profesores
Pedro Cerbuna 12, 50009 Zaragoza
Tel. (34) 876553689
carreraj@unizar.es <ma...@unizar.es>
unizar.es
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Michael Wuttke <mi...@beuth-hochschule.de>.
Hi,
The import/export performed well.
I imported the backup from OM 3.0.2 like you suggested with:
./admin.sh -v -i -file ../backup_110614.zip --drop --skip-default-rooms
So I will wait for the next build. ;-)
Thanks a lot,
Michael
Am 11.06.2014 10:12, schrieb Maxim Solodovnik:
> import/export for build 25 should be OK.
> This build will not work on old database
>
> No need to retest in case import/export was performed
>
>
> On 11 June 2014 15:06, Michael Wuttke
> <michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>> wrote:
>
> Hello Maxim,
>
> Shoudl I install the build 25 from scratch again?
>
> And should I paste the error messages here or on http://pastebin.com in
> future times?
>
> Thanks,
> Michael
>
> Am 11.06.2014 10:00, schrieb Maxim Solodovnik:
> > Thanks!
> > will try to fix it ASAP
> >
> >
> > On 11 June 2014 14:51, Michael Wuttke
> > <michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> >
> > Hello Maxim,
> >
> > I testet the OM build 25 of version 3.0.3 (updated from
> version 3.0.2).
> >
> > Unfortunately I was not able to change the settings of the OM
> admin for
> > the GUI or to logout again as the admin.
> >
> > Maybe there is something wrong in my OM settings?
> >
> > Here are the error messages form the openmeetings.log:
> >
> > DEBUG 06-11 09:36:12.230
> > o.a.w.p.AsynchronousDataStore$PageSavingRunnable:354
> > [Wicket-PageSavingThread] - Saving asynchronously: Entry
> > [sessionId=D46DE4D12DE23DB40DDF3BBEC313F2A4, pageId=5]...
> > DEBUG 06-11 09:36:12.231 o.a.w.p.PageAccessSynchronizer:346
> > [http-nio-0.0.0.0-5080-exec-6] - 'http-nio-0.0.0.0-5080-exec-6'
> > notifying blocked threads
> > DEBUG 06-11 09:36:12.231 o.a.w.p.DiskDataStore:186
> > [Wicket-PageSavingThread] - Storing data for page with id '5'
> in session
> > with id 'D46DE4D12DE23DB40DDF3BBEC313F2A4'
> > DEBUG 06-11 09:36:20.099 o.a.w.p.h.s.ServletWebRequest:189
> > [http-nio-0.0.0.0-5080-exec-9] - Calculating context relative
> path from:
> > context path '/openmeetings', filterPrefix '', uri
> '/openmeetings/'
> > DEBUG 06-11 09:36:20.100 o.a.w.p.PageAccessSynchronizer:100
> > [http-nio-0.0.0.0-5080-exec-9] - 'http-nio-0.0.0.0-5080-exec-9'
> > attempting to acquire lock to page with id '5'
> > DEBUG 06-11 09:36:20.101 o.a.w.p.PageAccessSynchronizer:125
> > [http-nio-0.0.0.0-5080-exec-9] - http-nio-0.0.0.0-5080-exec-9
> acquired
> > lock to page 5
> > ERROR 06-11 09:36:20.104 o.a.w.DefaultExceptionMapper:129
> > [http-nio-0.0.0.0-5080-exec-9] - Unexpected error occurred
> > org.apache.wicket.WicketRuntimeException: Method onRequest of
> interface
> > org.apache.wicket.behavior.IBehaviorListener targeted at
> > org.apache.wicket.ajax.markup.html.AjaxLink$1@37cc67fd on
> component
> > [ConfirmableAjaxLink [Component id = logout]] threw an exception
> > at
> >
> org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:268)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:241)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:250)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:236)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> > ~[wicket-request-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
> > [wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
> > [wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
> > [wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:59)
> > [wicket-native-websocket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> > [wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
> > [wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> > [red5.jar:na]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:409)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1044)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1721)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1679)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> > [na:1.6.0_32]
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> > [na:1.6.0_32]
> > at java.lang.Thread.run(Thread.java:662) [na:1.6.0_32]
> > Caused by: java.lang.reflect.InvocationTargetException: null
> > at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown
> > Source) ~[na:na]
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > ~[na:1.6.0_32]
> > at java.lang.reflect.Method.invoke(Method.java:597)
> > ~[na:1.6.0_32]
> > at
> >
> org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:258)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > ... 31 common frames omitted
> > Caused by: java.lang.UnsupportedOperationException: null
> > at
> >
> java.util.Collections$UnmodifiableCollection.clear(Collections.java:1037)
> > ~[na:1.6.0_32]
> > at
> >
> org.apache.openmeetings.web.app.WebSession.invalidate(WebSession.java:119)
> > ~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
> > at
> >
> org.apache.openmeetings.web.pages.MainPage$2.onClick(MainPage.java:86)
> > ~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
> > at
> >
> org.apache.wicket.ajax.markup.html.AjaxLink$1.onEvent(AjaxLink.java:86)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:123)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:626)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > ... 35 common frames omitted
> >
> > and from the red5.log:
> > 2014-06-11 09:42:21,671 [http-nio-0.0.0.0-5080-exec-8] ERROR
> > o.a.c.c.C.[.[.0.0.0.[.[default] - Servlet.service() for servlet
> > [default] in context with path [/openmeetings] threw exception
> > java.lang.UnsupportedOperationException: null
> > at
> >
> java.util.Collections$UnmodifiableCollection.clear(Collections.java:1037)
> > ~[na:1.6.0_32]
> > at
> >
> org.apache.openmeetings.web.app.WebSession.invalidate(WebSession.java:119)
> > ~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
> > at
> org.apache.wicket.Session.invalidateNow(Session.java:530)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at org.apache.wicket.Session.detach(Session.java:674)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.cycle.RequestCycle.onDetach(RequestCycle.java:645)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.cycle.RequestCycle.detach(RequestCycle.java:589)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:59)
> > ~[wicket-native-websocket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> > ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> > ~[red5.jar:na]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> > ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> > ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:409)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1044)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1721)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1679)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> > [na:1.6.0_32]
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> > [na:1.6.0_32]
> > at java.lang.Thread.run(Thread.java:662) [na:1.6.0_32]
> >
> > I tried also the Network testing from the login screen:
> > http://myurl:5080/openmeetings/swf?swf=networktesting.swf10.swf
> >
> > I've got the Access Denied page:
> > ---
> > Access Denied
> > You do not have access to the page you requested.
> > Return to home page
> > ---
> >
> > Sorry, but I stoped testing the LDAP configuration for this build.
> >
> > Thanks & Greetings,
> > Michael
> >
> > Am 10.06.2014 18:58, schrieb Maxim Solodovnik:
> > > Can you please check if the implemented solution works as
> expected?
> > > Latest 3.0.3 build contains the changes
> > >
> > >
> > > On 2 June 2014 17:31, Michael Wuttke
> > <michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>
> > > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>>> wrote:
> > >
> > > Hello Maxim,
> > >
> > > I think so too, using OM via moodle or directly via LDAP
> like
> > Juan in
> > > the jira issue nr. 1007 described - with the same
> credentials
> > would be
> > > great.
> > >
> > > Thanks & Greetings,
> > > Michael
> > >
> > > Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
> > > > Hello All,
> > > >
> > > > Due to multiple requests and issues (please see [1], [2],
> > [3]) I would
> > > > like to change User object (remove status and "user
> level")
> > and add
> > > > Permissions.
> > > >
> > > > As I can see the permissions should be
> > > > Admin == access to Admin module
> > > > Room == enter the room
> > > > Dashboard == access the whiteboard
> > > > Login == login to Om internal DB
> > > > Soap == use rest/soap calls
> > > >
> > > > for example
> > > > current "regular" user will have all permissions
> except for
> > Admin
> > > and Soap
> > > > current "soap" user will have soap permission only
> > > > current OAuth user will have no Login parmission
> > > >
> > > > The proposed system looks extendable and should cover all
> > current
> > > needs
> > > >
> > > > I'm going to implement it in 3.0.3 and 3.1.0
> > > >
> > > > Please let me know if you have any concerns/corrections
> > > >
> > > > Thanks in advance
> > > >
> > > > [1]
> http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> > > > [2]
> https://issues.apache.org/jira/browse/OPENMEETINGS-1007
> > > > [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
> >
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
>
> --
> Vielen Dank & mit freundlichen Grüßen,
> Michael Wuttke
>
> Administration - Learning Management System
> Beuth Hochschule Berlin - Labor Online Learning
> Luxemburger Str. 10
> 13353 Berlin
> Tel: +49 (0)30 45 04 2184
> E-Mail: michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> News: https://lms.beuth-hochschule.de/rss
>
>
>
>
> --
> WBR
> Maxim aka solomax
--
Vielen Dank & mit freundlichen Grüßen,
Michael Wuttke
Administration - Learning Management System
Beuth Hochschule Berlin - Labor Online Learning
Luxemburger Str. 10
13353 Berlin
Tel: +49 (0)30 45 04 2184
E-Mail: michael.wuttke@beuth-hochschule.de
News: https://lms.beuth-hochschule.de/rss
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Maxim Solodovnik <so...@gmail.com>.
import/export for build 25 should be OK.
This build will not work on old database
No need to retest in case import/export was performed
On 11 June 2014 15:06, Michael Wuttke <mi...@beuth-hochschule.de>
wrote:
> Hello Maxim,
>
> Shoudl I install the build 25 from scratch again?
>
> And should I paste the error messages here or on http://pastebin.com in
> future times?
>
> Thanks,
> Michael
>
> Am 11.06.2014 10:00, schrieb Maxim Solodovnik:
> > Thanks!
> > will try to fix it ASAP
> >
> >
> > On 11 June 2014 14:51, Michael Wuttke
> > <michael.wuttke@beuth-hochschule.de
> >
> > Hello Maxim,
> >
> > I testet the OM build 25 of version 3.0.3 (updated from version
> 3.0.2).
> >
> > Unfortunately I was not able to change the settings of the OM admin
> for
> > the GUI or to logout again as the admin.
> >
> > Maybe there is something wrong in my OM settings?
> >
> > Here are the error messages form the openmeetings.log:
> >
> > DEBUG 06-11 09:36:12.230
> > o.a.w.p.AsynchronousDataStore$PageSavingRunnable:354
> > [Wicket-PageSavingThread] - Saving asynchronously: Entry
> > [sessionId=D46DE4D12DE23DB40DDF3BBEC313F2A4, pageId=5]...
> > DEBUG 06-11 09:36:12.231 o.a.w.p.PageAccessSynchronizer:346
> > [http-nio-0.0.0.0-5080-exec-6] - 'http-nio-0.0.0.0-5080-exec-6'
> > notifying blocked threads
> > DEBUG 06-11 09:36:12.231 o.a.w.p.DiskDataStore:186
> > [Wicket-PageSavingThread] - Storing data for page with id '5' in
> session
> > with id 'D46DE4D12DE23DB40DDF3BBEC313F2A4'
> > DEBUG 06-11 09:36:20.099 o.a.w.p.h.s.ServletWebRequest:189
> > [http-nio-0.0.0.0-5080-exec-9] - Calculating context relative path
> from:
> > context path '/openmeetings', filterPrefix '', uri '/openmeetings/'
> > DEBUG 06-11 09:36:20.100 o.a.w.p.PageAccessSynchronizer:100
> > [http-nio-0.0.0.0-5080-exec-9] - 'http-nio-0.0.0.0-5080-exec-9'
> > attempting to acquire lock to page with id '5'
> > DEBUG 06-11 09:36:20.101 o.a.w.p.PageAccessSynchronizer:125
> > [http-nio-0.0.0.0-5080-exec-9] - http-nio-0.0.0.0-5080-exec-9
> acquired
> > lock to page 5
> > ERROR 06-11 09:36:20.104 o.a.w.DefaultExceptionMapper:129
> > [http-nio-0.0.0.0-5080-exec-9] - Unexpected error occurred
> > org.apache.wicket.WicketRuntimeException: Method onRequest of
> interface
> > org.apache.wicket.behavior.IBehaviorListener targeted at
> > org.apache.wicket.ajax.markup.html.AjaxLink$1@37cc67fd on component
> > [ConfirmableAjaxLink [Component id = logout]] threw an exception
> > at
> >
> org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:268)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:241)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:250)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:236)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> > ~[wicket-request-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
> > [wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
> > [wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
> > [wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:59)
> > [wicket-native-websocket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> > [wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
> > [wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> > [red5.jar:na]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:409)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1044)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1721)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1679)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> > [na:1.6.0_32]
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> > [na:1.6.0_32]
> > at java.lang.Thread.run(Thread.java:662) [na:1.6.0_32]
> > Caused by: java.lang.reflect.InvocationTargetException: null
> > at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown
> > Source) ~[na:na]
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > ~[na:1.6.0_32]
> > at java.lang.reflect.Method.invoke(Method.java:597)
> > ~[na:1.6.0_32]
> > at
> >
> org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:258)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > ... 31 common frames omitted
> > Caused by: java.lang.UnsupportedOperationException: null
> > at
> >
> java.util.Collections$UnmodifiableCollection.clear(Collections.java:1037)
> > ~[na:1.6.0_32]
> > at
> >
> org.apache.openmeetings.web.app.WebSession.invalidate(WebSession.java:119)
> > ~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
> > at
> >
> org.apache.openmeetings.web.pages.MainPage$2.onClick(MainPage.java:86)
> > ~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
> > at
> >
> org.apache.wicket.ajax.markup.html.AjaxLink$1.onEvent(AjaxLink.java:86)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:123)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:626)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > ... 35 common frames omitted
> >
> > and from the red5.log:
> > 2014-06-11 09:42:21,671 [http-nio-0.0.0.0-5080-exec-8] ERROR
> > o.a.c.c.C.[.[.0.0.0.[.[default] - Servlet.service() for servlet
> > [default] in context with path [/openmeetings] threw exception
> > java.lang.UnsupportedOperationException: null
> > at
> >
> java.util.Collections$UnmodifiableCollection.clear(Collections.java:1037)
> > ~[na:1.6.0_32]
> > at
> >
> org.apache.openmeetings.web.app.WebSession.invalidate(WebSession.java:119)
> > ~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
> > at org.apache.wicket.Session.invalidateNow(Session.java:530)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at org.apache.wicket.Session.detach(Session.java:674)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.cycle.RequestCycle.onDetach(RequestCycle.java:645)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.cycle.RequestCycle.detach(RequestCycle.java:589)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:59)
> > ~[wicket-native-websocket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
> > ~[wicket-core-jar-6.14.0.jar:6.14.0]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> > ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> > ~[red5.jar:na]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> > ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> > ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> > ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:409)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1044)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1721)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1679)
> > [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> > [na:1.6.0_32]
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> > [na:1.6.0_32]
> > at java.lang.Thread.run(Thread.java:662) [na:1.6.0_32]
> >
> > I tried also the Network testing from the login screen:
> > http://myurl:5080/openmeetings/swf?swf=networktesting.swf10.swf
> >
> > I've got the Access Denied page:
> > ---
> > Access Denied
> > You do not have access to the page you requested.
> > Return to home page
> > ---
> >
> > Sorry, but I stoped testing the LDAP configuration for this build.
> >
> > Thanks & Greetings,
> > Michael
> >
> > Am 10.06.2014 18:58, schrieb Maxim Solodovnik:
> > > Can you please check if the implemented solution works as expected?
> > > Latest 3.0.3 build contains the changes
> > >
> > >
> > > On 2 June 2014 17:31, Michael Wuttke
> > <michael.wuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>
> > > <mailto:michael.wuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>>> wrote:
> > >
> > > Hello Maxim,
> > >
> > > I think so too, using OM via moodle or directly via LDAP like
> > Juan in
> > > the jira issue nr. 1007 described - with the same credentials
> > would be
> > > great.
> > >
> > > Thanks & Greetings,
> > > Michael
> > >
> > > Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
> > > > Hello All,
> > > >
> > > > Due to multiple requests and issues (please see [1], [2],
> > [3]) I would
> > > > like to change User object (remove status and "user level")
> > and add
> > > > Permissions.
> > > >
> > > > As I can see the permissions should be
> > > > Admin == access to Admin module
> > > > Room == enter the room
> > > > Dashboard == access the whiteboard
> > > > Login == login to Om internal DB
> > > > Soap == use rest/soap calls
> > > >
> > > > for example
> > > > current "regular" user will have all permissions except for
> > Admin
> > > and Soap
> > > > current "soap" user will have soap permission only
> > > > current OAuth user will have no Login parmission
> > > >
> > > > The proposed system looks extendable and should cover all
> > current
> > > needs
> > > >
> > > > I'm going to implement it in 3.0.3 and 3.1.0
> > > >
> > > > Please let me know if you have any concerns/corrections
> > > >
> > > > Thanks in advance
> > > >
> > > > [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> > > > [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
> > > > [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
> >
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
>
> --
> Vielen Dank & mit freundlichen Grüßen,
> Michael Wuttke
>
> Administration - Learning Management System
> Beuth Hochschule Berlin - Labor Online Learning
> Luxemburger Str. 10
> 13353 Berlin
> Tel: +49 (0)30 45 04 2184
> E-Mail: michael.wuttke@beuth-hochschule.de
> News: https://lms.beuth-hochschule.de/rss
>
--
WBR
Maxim aka solomax
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Michael Wuttke <mi...@beuth-hochschule.de>.
Hello Maxim,
Shoudl I install the build 25 from scratch again?
And should I paste the error messages here or on http://pastebin.com in
future times?
Thanks,
Michael
Am 11.06.2014 10:00, schrieb Maxim Solodovnik:
> Thanks!
> will try to fix it ASAP
>
>
> On 11 June 2014 14:51, Michael Wuttke
> <michael.wuttke@beuth-hochschule.de
>
> Hello Maxim,
>
> I testet the OM build 25 of version 3.0.3 (updated from version 3.0.2).
>
> Unfortunately I was not able to change the settings of the OM admin for
> the GUI or to logout again as the admin.
>
> Maybe there is something wrong in my OM settings?
>
> Here are the error messages form the openmeetings.log:
>
> DEBUG 06-11 09:36:12.230
> o.a.w.p.AsynchronousDataStore$PageSavingRunnable:354
> [Wicket-PageSavingThread] - Saving asynchronously: Entry
> [sessionId=D46DE4D12DE23DB40DDF3BBEC313F2A4, pageId=5]...
> DEBUG 06-11 09:36:12.231 o.a.w.p.PageAccessSynchronizer:346
> [http-nio-0.0.0.0-5080-exec-6] - 'http-nio-0.0.0.0-5080-exec-6'
> notifying blocked threads
> DEBUG 06-11 09:36:12.231 o.a.w.p.DiskDataStore:186
> [Wicket-PageSavingThread] - Storing data for page with id '5' in session
> with id 'D46DE4D12DE23DB40DDF3BBEC313F2A4'
> DEBUG 06-11 09:36:20.099 o.a.w.p.h.s.ServletWebRequest:189
> [http-nio-0.0.0.0-5080-exec-9] - Calculating context relative path from:
> context path '/openmeetings', filterPrefix '', uri '/openmeetings/'
> DEBUG 06-11 09:36:20.100 o.a.w.p.PageAccessSynchronizer:100
> [http-nio-0.0.0.0-5080-exec-9] - 'http-nio-0.0.0.0-5080-exec-9'
> attempting to acquire lock to page with id '5'
> DEBUG 06-11 09:36:20.101 o.a.w.p.PageAccessSynchronizer:125
> [http-nio-0.0.0.0-5080-exec-9] - http-nio-0.0.0.0-5080-exec-9 acquired
> lock to page 5
> ERROR 06-11 09:36:20.104 o.a.w.DefaultExceptionMapper:129
> [http-nio-0.0.0.0-5080-exec-9] - Unexpected error occurred
> org.apache.wicket.WicketRuntimeException: Method onRequest of interface
> org.apache.wicket.behavior.IBehaviorListener targeted at
> org.apache.wicket.ajax.markup.html.AjaxLink$1@37cc67fd on component
> [ConfirmableAjaxLink [Component id = logout]] threw an exception
> at
> org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:268)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:241)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:250)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:236)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> ~[wicket-request-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
> [wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
> [wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
> [wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:59)
> [wicket-native-websocket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> [wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
> [wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> [red5.jar:na]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:409)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1044)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1721)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1679)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> [na:1.6.0_32]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> [na:1.6.0_32]
> at java.lang.Thread.run(Thread.java:662) [na:1.6.0_32]
> Caused by: java.lang.reflect.InvocationTargetException: null
> at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown
> Source) ~[na:na]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> ~[na:1.6.0_32]
> at java.lang.reflect.Method.invoke(Method.java:597)
> ~[na:1.6.0_32]
> at
> org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:258)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> ... 31 common frames omitted
> Caused by: java.lang.UnsupportedOperationException: null
> at
> java.util.Collections$UnmodifiableCollection.clear(Collections.java:1037)
> ~[na:1.6.0_32]
> at
> org.apache.openmeetings.web.app.WebSession.invalidate(WebSession.java:119)
> ~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
> at
> org.apache.openmeetings.web.pages.MainPage$2.onClick(MainPage.java:86)
> ~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
> at
> org.apache.wicket.ajax.markup.html.AjaxLink$1.onEvent(AjaxLink.java:86)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:123)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:626)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> ... 35 common frames omitted
>
> and from the red5.log:
> 2014-06-11 09:42:21,671 [http-nio-0.0.0.0-5080-exec-8] ERROR
> o.a.c.c.C.[.[.0.0.0.[.[default] - Servlet.service() for servlet
> [default] in context with path [/openmeetings] threw exception
> java.lang.UnsupportedOperationException: null
> at
> java.util.Collections$UnmodifiableCollection.clear(Collections.java:1037)
> ~[na:1.6.0_32]
> at
> org.apache.openmeetings.web.app.WebSession.invalidate(WebSession.java:119)
> ~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
> at org.apache.wicket.Session.invalidateNow(Session.java:530)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at org.apache.wicket.Session.detach(Session.java:674)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.onDetach(RequestCycle.java:645)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.detach(RequestCycle.java:589)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:59)
> ~[wicket-native-websocket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> ~[red5.jar:na]
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:409)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1044)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1721)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1679)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> [na:1.6.0_32]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> [na:1.6.0_32]
> at java.lang.Thread.run(Thread.java:662) [na:1.6.0_32]
>
> I tried also the Network testing from the login screen:
> http://myurl:5080/openmeetings/swf?swf=networktesting.swf10.swf
>
> I've got the Access Denied page:
> ---
> Access Denied
> You do not have access to the page you requested.
> Return to home page
> ---
>
> Sorry, but I stoped testing the LDAP configuration for this build.
>
> Thanks & Greetings,
> Michael
>
> Am 10.06.2014 18:58, schrieb Maxim Solodovnik:
> > Can you please check if the implemented solution works as expected?
> > Latest 3.0.3 build contains the changes
> >
> >
> > On 2 June 2014 17:31, Michael Wuttke
> <michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>
> > <mailto:michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>>> wrote:
> >
> > Hello Maxim,
> >
> > I think so too, using OM via moodle or directly via LDAP like
> Juan in
> > the jira issue nr. 1007 described - with the same credentials
> would be
> > great.
> >
> > Thanks & Greetings,
> > Michael
> >
> > Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
> > > Hello All,
> > >
> > > Due to multiple requests and issues (please see [1], [2],
> [3]) I would
> > > like to change User object (remove status and "user level")
> and add
> > > Permissions.
> > >
> > > As I can see the permissions should be
> > > Admin == access to Admin module
> > > Room == enter the room
> > > Dashboard == access the whiteboard
> > > Login == login to Om internal DB
> > > Soap == use rest/soap calls
> > >
> > > for example
> > > current "regular" user will have all permissions except for
> Admin
> > and Soap
> > > current "soap" user will have soap permission only
> > > current OAuth user will have no Login parmission
> > >
> > > The proposed system looks extendable and should cover all
> current
> > needs
> > >
> > > I'm going to implement it in 3.0.3 and 3.1.0
> > >
> > > Please let me know if you have any concerns/corrections
> > >
> > > Thanks in advance
> > >
> > > [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> > > [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
> > > [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
>
>
>
>
> --
> WBR
> Maxim aka solomax
--
Vielen Dank & mit freundlichen Grüßen,
Michael Wuttke
Administration - Learning Management System
Beuth Hochschule Berlin - Labor Online Learning
Luxemburger Str. 10
13353 Berlin
Tel: +49 (0)30 45 04 2184
E-Mail: michael.wuttke@beuth-hochschule.de
News: https://lms.beuth-hochschule.de/rss
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Maxim Solodovnik <so...@gmail.com>.
Thanks!
will try to fix it ASAP
On 11 June 2014 14:51, Michael Wuttke <mi...@beuth-hochschule.de>
wrote:
> Hello Maxim,
>
> I testet the OM build 25 of version 3.0.3 (updated from version 3.0.2).
>
> Unfortunately I was not able to change the settings of the OM admin for
> the GUI or to logout again as the admin.
>
> Maybe there is something wrong in my OM settings?
>
> Here are the error messages form the openmeetings.log:
>
> DEBUG 06-11 09:36:12.230
> o.a.w.p.AsynchronousDataStore$PageSavingRunnable:354
> [Wicket-PageSavingThread] - Saving asynchronously: Entry
> [sessionId=D46DE4D12DE23DB40DDF3BBEC313F2A4, pageId=5]...
> DEBUG 06-11 09:36:12.231 o.a.w.p.PageAccessSynchronizer:346
> [http-nio-0.0.0.0-5080-exec-6] - 'http-nio-0.0.0.0-5080-exec-6'
> notifying blocked threads
> DEBUG 06-11 09:36:12.231 o.a.w.p.DiskDataStore:186
> [Wicket-PageSavingThread] - Storing data for page with id '5' in session
> with id 'D46DE4D12DE23DB40DDF3BBEC313F2A4'
> DEBUG 06-11 09:36:20.099 o.a.w.p.h.s.ServletWebRequest:189
> [http-nio-0.0.0.0-5080-exec-9] - Calculating context relative path from:
> context path '/openmeetings', filterPrefix '', uri '/openmeetings/'
> DEBUG 06-11 09:36:20.100 o.a.w.p.PageAccessSynchronizer:100
> [http-nio-0.0.0.0-5080-exec-9] - 'http-nio-0.0.0.0-5080-exec-9'
> attempting to acquire lock to page with id '5'
> DEBUG 06-11 09:36:20.101 o.a.w.p.PageAccessSynchronizer:125
> [http-nio-0.0.0.0-5080-exec-9] - http-nio-0.0.0.0-5080-exec-9 acquired
> lock to page 5
> ERROR 06-11 09:36:20.104 o.a.w.DefaultExceptionMapper:129
> [http-nio-0.0.0.0-5080-exec-9] - Unexpected error occurred
> org.apache.wicket.WicketRuntimeException: Method onRequest of interface
> org.apache.wicket.behavior.IBehaviorListener targeted at
> org.apache.wicket.ajax.markup.html.AjaxLink$1@37cc67fd on component
> [ConfirmableAjaxLink [Component id = logout]] threw an exception
> at
>
> org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:268)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:241)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:250)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:236)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> ~[wicket-request-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
> [wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
> [wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
> [wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:59)
> [wicket-native-websocket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> [wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
> [wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> [red5.jar:na]
> at
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:409)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1044)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1721)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1679)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> [na:1.6.0_32]
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> [na:1.6.0_32]
> at java.lang.Thread.run(Thread.java:662) [na:1.6.0_32]
> Caused by: java.lang.reflect.InvocationTargetException: null
> at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source)
> ~[na:na]
> at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> ~[na:1.6.0_32]
> at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_32]
> at
>
> org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:258)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> ... 31 common frames omitted
> Caused by: java.lang.UnsupportedOperationException: null
> at
> java.util.Collections$UnmodifiableCollection.clear(Collections.java:1037)
> ~[na:1.6.0_32]
> at
> org.apache.openmeetings.web.app.WebSession.invalidate(WebSession.java:119)
> ~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
> at
> org.apache.openmeetings.web.pages.MainPage$2.onClick(MainPage.java:86)
> ~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
> at
> org.apache.wicket.ajax.markup.html.AjaxLink$1.onEvent(AjaxLink.java:86)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:123)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:626)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> ... 35 common frames omitted
>
> and from the red5.log:
> 2014-06-11 09:42:21,671 [http-nio-0.0.0.0-5080-exec-8] ERROR
> o.a.c.c.C.[.[.0.0.0.[.[default] - Servlet.service() for servlet
> [default] in context with path [/openmeetings] threw exception
> java.lang.UnsupportedOperationException: null
> at
> java.util.Collections$UnmodifiableCollection.clear(Collections.java:1037)
> ~[na:1.6.0_32]
> at
> org.apache.openmeetings.web.app.WebSession.invalidate(WebSession.java:119)
> ~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
> at org.apache.wicket.Session.invalidateNow(Session.java:530)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at org.apache.wicket.Session.detach(Session.java:674)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.request.cycle.RequestCycle.onDetach(RequestCycle.java:645)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.detach(RequestCycle.java:589)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:59)
> ~[wicket-native-websocket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
> ~[wicket-core-jar-6.14.0.jar:6.14.0]
> at
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
> ~[red5.jar:na]
> at
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> ~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:409)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1044)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1721)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1679)
> [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> [na:1.6.0_32]
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> [na:1.6.0_32]
> at java.lang.Thread.run(Thread.java:662) [na:1.6.0_32]
>
> I tried also the Network testing from the login screen:
> http://myurl:5080/openmeetings/swf?swf=networktesting.swf10.swf
>
> I've got the Access Denied page:
> ---
> Access Denied
> You do not have access to the page you requested.
> Return to home page
> ---
>
> Sorry, but I stoped testing the LDAP configuration for this build.
>
> Thanks & Greetings,
> Michael
>
> Am 10.06.2014 18:58, schrieb Maxim Solodovnik:
> > Can you please check if the implemented solution works as expected?
> > Latest 3.0.3 build contains the changes
> >
> >
> > On 2 June 2014 17:31, Michael Wuttke <michael.wuttke@beuth-hochschule.de
> > <ma...@beuth-hochschule.de>> wrote:
> >
> > Hello Maxim,
> >
> > I think so too, using OM via moodle or directly via LDAP like Juan in
> > the jira issue nr. 1007 described - with the same credentials would
> be
> > great.
> >
> > Thanks & Greetings,
> > Michael
> >
> > Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
> > > Hello All,
> > >
> > > Due to multiple requests and issues (please see [1], [2], [3]) I
> would
> > > like to change User object (remove status and "user level") and add
> > > Permissions.
> > >
> > > As I can see the permissions should be
> > > Admin == access to Admin module
> > > Room == enter the room
> > > Dashboard == access the whiteboard
> > > Login == login to Om internal DB
> > > Soap == use rest/soap calls
> > >
> > > for example
> > > current "regular" user will have all permissions except for Admin
> > and Soap
> > > current "soap" user will have soap permission only
> > > current OAuth user will have no Login parmission
> > >
> > > The proposed system looks extendable and should cover all current
> > needs
> > >
> > > I'm going to implement it in 3.0.3 and 3.1.0
> > >
> > > Please let me know if you have any concerns/corrections
> > >
> > > Thanks in advance
> > >
> > > [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> > > [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
> > > [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
>
--
WBR
Maxim aka solomax
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Michael Wuttke <mi...@beuth-hochschule.de>.
Hello Maxim,
I testet the OM build 25 of version 3.0.3 (updated from version 3.0.2).
Unfortunately I was not able to change the settings of the OM admin for
the GUI or to logout again as the admin.
Maybe there is something wrong in my OM settings?
Here are the error messages form the openmeetings.log:
DEBUG 06-11 09:36:12.230
o.a.w.p.AsynchronousDataStore$PageSavingRunnable:354
[Wicket-PageSavingThread] - Saving asynchronously: Entry
[sessionId=D46DE4D12DE23DB40DDF3BBEC313F2A4, pageId=5]...
DEBUG 06-11 09:36:12.231 o.a.w.p.PageAccessSynchronizer:346
[http-nio-0.0.0.0-5080-exec-6] - 'http-nio-0.0.0.0-5080-exec-6'
notifying blocked threads
DEBUG 06-11 09:36:12.231 o.a.w.p.DiskDataStore:186
[Wicket-PageSavingThread] - Storing data for page with id '5' in session
with id 'D46DE4D12DE23DB40DDF3BBEC313F2A4'
DEBUG 06-11 09:36:20.099 o.a.w.p.h.s.ServletWebRequest:189
[http-nio-0.0.0.0-5080-exec-9] - Calculating context relative path from:
context path '/openmeetings', filterPrefix '', uri '/openmeetings/'
DEBUG 06-11 09:36:20.100 o.a.w.p.PageAccessSynchronizer:100
[http-nio-0.0.0.0-5080-exec-9] - 'http-nio-0.0.0.0-5080-exec-9'
attempting to acquire lock to page with id '5'
DEBUG 06-11 09:36:20.101 o.a.w.p.PageAccessSynchronizer:125
[http-nio-0.0.0.0-5080-exec-9] - http-nio-0.0.0.0-5080-exec-9 acquired
lock to page 5
ERROR 06-11 09:36:20.104 o.a.w.DefaultExceptionMapper:129
[http-nio-0.0.0.0-5080-exec-9] - Unexpected error occurred
org.apache.wicket.WicketRuntimeException: Method onRequest of interface
org.apache.wicket.behavior.IBehaviorListener targeted at
org.apache.wicket.ajax.markup.html.AjaxLink$1@37cc67fd on component
[ConfirmableAjaxLink [Component id = logout]] threw an exception
at
org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:268)
~[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:241)
~[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:250)
~[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:236)
~[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:862)
~[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
~[wicket-request-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:59)
[wicket-native-websocket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
[red5.jar:na]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:409)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1044)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1721)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1679)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[na:1.6.0_32]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[na:1.6.0_32]
at java.lang.Thread.run(Thread.java:662) [na:1.6.0_32]
Caused by: java.lang.reflect.InvocationTargetException: null
at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source) ~[na:na]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
~[na:1.6.0_32]
at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_32]
at
org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:258)
~[wicket-core-jar-6.14.0.jar:6.14.0]
... 31 common frames omitted
Caused by: java.lang.UnsupportedOperationException: null
at
java.util.Collections$UnmodifiableCollection.clear(Collections.java:1037) ~[na:1.6.0_32]
at
org.apache.openmeetings.web.app.WebSession.invalidate(WebSession.java:119)
~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
at
org.apache.openmeetings.web.pages.MainPage$2.onClick(MainPage.java:86)
~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
at
org.apache.wicket.ajax.markup.html.AjaxLink$1.onEvent(AjaxLink.java:86)
~[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:123)
~[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:626)
~[wicket-core-jar-6.14.0.jar:6.14.0]
... 35 common frames omitted
and from the red5.log:
2014-06-11 09:42:21,671 [http-nio-0.0.0.0-5080-exec-8] ERROR
o.a.c.c.C.[.[.0.0.0.[.[default] - Servlet.service() for servlet
[default] in context with path [/openmeetings] threw exception
java.lang.UnsupportedOperationException: null
at
java.util.Collections$UnmodifiableCollection.clear(Collections.java:1037) ~[na:1.6.0_32]
at
org.apache.openmeetings.web.app.WebSession.invalidate(WebSession.java:119)
~[openmeetings-web-3.0.3-SNAPSHOT.jar:na]
at org.apache.wicket.Session.invalidateNow(Session.java:530)
~[wicket-core-jar-6.14.0.jar:6.14.0]
at org.apache.wicket.Session.detach(Session.java:674)
~[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.request.cycle.RequestCycle.onDetach(RequestCycle.java:645)
~[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.request.cycle.RequestCycle.detach(RequestCycle.java:589)
~[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293)
~[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:59)
~[wicket-native-websocket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
~[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
~[wicket-core-jar-6.14.0.jar:6.14.0]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.red5.logging.LoggerContextFilter.doFilter(LoggerContextFilter.java:77)
~[red5.jar:na]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
~[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953) [tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:409)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1044)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1721)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1679)
[tomcat-embed-core-jar-7.0.50.jar:7.0.50]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[na:1.6.0_32]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[na:1.6.0_32]
at java.lang.Thread.run(Thread.java:662) [na:1.6.0_32]
I tried also the Network testing from the login screen:
http://myurl:5080/openmeetings/swf?swf=networktesting.swf10.swf
I've got the Access Denied page:
---
Access Denied
You do not have access to the page you requested.
Return to home page
---
Sorry, but I stoped testing the LDAP configuration for this build.
Thanks & Greetings,
Michael
Am 10.06.2014 18:58, schrieb Maxim Solodovnik:
> Can you please check if the implemented solution works as expected?
> Latest 3.0.3 build contains the changes
>
>
> On 2 June 2014 17:31, Michael Wuttke <michael.wuttke@beuth-hochschule.de
> <ma...@beuth-hochschule.de>> wrote:
>
> Hello Maxim,
>
> I think so too, using OM via moodle or directly via LDAP like Juan in
> the jira issue nr. 1007 described - with the same credentials would be
> great.
>
> Thanks & Greetings,
> Michael
>
> Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
> > Hello All,
> >
> > Due to multiple requests and issues (please see [1], [2], [3]) I would
> > like to change User object (remove status and "user level") and add
> > Permissions.
> >
> > As I can see the permissions should be
> > Admin == access to Admin module
> > Room == enter the room
> > Dashboard == access the whiteboard
> > Login == login to Om internal DB
> > Soap == use rest/soap calls
> >
> > for example
> > current "regular" user will have all permissions except for Admin
> and Soap
> > current "soap" user will have soap permission only
> > current OAuth user will have no Login parmission
> >
> > The proposed system looks extendable and should cover all current
> needs
> >
> > I'm going to implement it in 3.0.3 and 3.1.0
> >
> > Please let me know if you have any concerns/corrections
> >
> > Thanks in advance
> >
> > [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> > [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
> > [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Maxim Solodovnik <so...@gmail.com>.
Can you please check if the implemented solution works as expected?
Latest 3.0.3 build contains the changes
On 2 June 2014 17:31, Michael Wuttke <mi...@beuth-hochschule.de>
wrote:
> Hello Maxim,
>
> I think so too, using OM via moodle or directly via LDAP like Juan in
> the jira issue nr. 1007 described - with the same credentials would be
> great.
>
> Thanks & Greetings,
> Michael
>
> Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
> > Hello All,
> >
> > Due to multiple requests and issues (please see [1], [2], [3]) I would
> > like to change User object (remove status and "user level") and add
> > Permissions.
> >
> > As I can see the permissions should be
> > Admin == access to Admin module
> > Room == enter the room
> > Dashboard == access the whiteboard
> > Login == login to Om internal DB
> > Soap == use rest/soap calls
> >
> > for example
> > current "regular" user will have all permissions except for Admin and
> Soap
> > current "soap" user will have soap permission only
> > current OAuth user will have no Login parmission
> >
> > The proposed system looks extendable and should cover all current needs
> >
> > I'm going to implement it in 3.0.3 and 3.1.0
> >
> > Please let me know if you have any concerns/corrections
> >
> > Thanks in advance
> >
> > [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> > [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
> > [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
> >
> > --
> > WBR
> > Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: [DISCUSSION] ACLs in Openmeetings
Posted by Michael Wuttke <mi...@beuth-hochschule.de>.
Hello Maxim,
I think so too, using OM via moodle or directly via LDAP like Juan in
the jira issue nr. 1007 described - with the same credentials would be
great.
Thanks & Greetings,
Michael
Am 01.06.2014 06:15, schrieb Maxim Solodovnik:
> Hello All,
>
> Due to multiple requests and issues (please see [1], [2], [3]) I would
> like to change User object (remove status and "user level") and add
> Permissions.
>
> As I can see the permissions should be
> Admin == access to Admin module
> Room == enter the room
> Dashboard == access the whiteboard
> Login == login to Om internal DB
> Soap == use rest/soap calls
>
> for example
> current "regular" user will have all permissions except for Admin and Soap
> current "soap" user will have soap permission only
> current OAuth user will have no Login parmission
>
> The proposed system looks extendable and should cover all current needs
>
> I'm going to implement it in 3.0.3 and 3.1.0
>
> Please let me know if you have any concerns/corrections
>
> Thanks in advance
>
> [1] http://openmeetings.markmail.org/thread/43ouivw7ysq6jorq
> [2] https://issues.apache.org/jira/browse/OPENMEETINGS-1007
> [3] https://issues.apache.org/jira/browse/OPENMEETINGS-986
>
> --
> WBR
> Maxim aka solomax