fixed in #30

On 18 June 2014 20:35, Peter Dähn <[email protected]> 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 <[email protected]>
> 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 <[email protected]
>>  > <mailto:[email protected]>> 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
>> >     <[email protected]
>>  >     <mailto:[email protected]>> 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
>> >         > <[email protected]
>> >         <mailto:[email protected]>
>>  >         > <mailto:[email protected]
>> >         <mailto:[email protected]>>> 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
>> >         <[email protected] <mailto:[email protected]>
>> >         >     <mailto:[email protected] <mailto:[email protected]>>
>> >         >     > <mailto:[email protected] <mailto:[email protected]>
>> >         <mailto:[email protected] <mailto:[email protected]>>>> 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
>> >         <mailto:michael.wuttke@beuth-__hochschule.de>
>>  >         >     <mailto:michael.wuttke@beuth-__hochschule.de
>> >         <mailto:michael.wuttke@beuth-__hochschule.de>>
>> >         >     >             <mailto:[email protected]
>> >         <mailto:[email protected]>
>> >         >     <mailto:[email protected]
>> >         <mailto:[email protected]>>>
>> >         >     >             <mailto:
>> michael.wuttke@beuth-__hochschule.de
>> >         <mailto:michael.wuttke@beuth-__hochschule.de>
>>  >         >     <mailto:michael.wuttke@beuth-__hochschule.de
>> >         <mailto:michael.wuttke@beuth-__hochschule.de>>
>> >         >     >             <mailto:[email protected]
>> >         <mailto:[email protected]>
>>  >         >     <mailto:[email protected]
>> >         <mailto:[email protected]>>>>> 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

Reply via email to