Ok looks like the error can be reproduced with the demo as well.
When the room is 1st entered on a fresh reboot the white board is present and
you can upload a file to that.
But if you close the original WB and then open a new WB you cannot upload a
file to the WB. It remains blank.
I have attached the debug log but it does not tell much (to myself that is)
-----Original Message-----
From: Maxim Solodovnik <[email protected]>
Sent: Monday, August 6, 2018 12:22 PM
To: Openmeetings user-list <[email protected]>
Subject: Re: Conference Room creation update error
Demo-next is updated to latest revision
On Mon, Aug 6, 2018 at 10:10 PM <[email protected]> wrote:
>
> Ok. If they are skipped on import then no need to delete the dB object. I
> just noticed when the backup was ran they were still listed, was the only
> reason for the delete.
>
> If you/someone has the latest snapshot running (revision 3f2c95f) can they
> test something for me. I am currently running live with the startup script
> so I cannot get the debug information until after the day is over. But looks
> like I cannot upload a file to the WB. May be localized, but was wondering
> if one had the revision up and going if they could test. This is the same VM
> that has been ran previous version so all needed pacakges should already be
> installed.
>
> Demo looks like its still running some revisions back so couldn't test there.
>
> -----Original Message-----
> From: Maxim Solodovnik <[email protected]>
> Sent: Monday, August 6, 2018 11:01 AM
> To: Openmeetings user-list <[email protected]>
> Subject: Re: Conference Room creation update error
>
> Actually both command line and UI installers uses same java code I'll
> retest with UI installer ASAP
>
> According to your question: deleted/purged users are included into XML
> backup files, but are being skipped during import
>
> I would not recommend to run queries like 'delete from om_user where
> id = #' since data integrity will be broken Here is the brief list of
> what need to done for user "hard" delete
> https://issues.apache.org/jira/browse/OPENMEETINGS-1864 (hard delete
> section)
> On Sun, Aug 5, 2018 at 5:14 PM Aaron H <[email protected]> wrote:
> >
> > Took a back-up of running system *one thing to note that prior to back-up
> > being preformed there was users that were purged, but also deleted from the
> > dB via manual process (delete from om_user where id = #) Wasn't for sure
> > if the back-up would pick up these "purged" users reason for the manual
> > deletion. Everything was restarted before back-up was performed.
> >
> > Then followed the normal steps for a build
> >
> > Move current install to old
> > * mv /opt/current /opt/old
> > Delete existing dB and create new
> > wGET new package and unzip in /opt/current folder Run new install
> > script *script copies customization files from stored location into
> > new install (can supply list of files that are copied if needed)
> > Restart server Run sh red5.sh to start process Go through the setup
> > process and restart server once complete
> > * during setup the tick for install default objects is not selected
> > Log in as admin and preformed import
> >
> > After the import was ran it put everything into the folder
> > /webapps/Openmeetings/upload/import/import_2018_08_04_05_59_04/roomF
> > il
> > es/profiles
> >
> > I had never did a command line import as I have always done it after the
> > system was configured. Since your import was successful then I would
> > assume there is something wrong with the back-up that was taken and not a
> > bug.
> >
> > One question to see if the step still needs to be taken. When you delete a
> > user and it creates the "purged" information; when you take a back-up are
> > those entries also included or does it omit them? Since I still seen the
> > entries in the dB I figured that the back-up would include this data. That
> > is the reason for the manual deletion prior to taking the backup.
> >
> >
> > -----Original Message-----
> > From: Maxim Solodovnik <[email protected]>
> > Sent: Sunday, August 5, 2018 12:16 AM
> > To: Openmeetings user-list <[email protected]>
> > Subject: Re: Conference Room creation update error
> >
> > Just performed command line import ~50k users with lots of profile
> > pictures All images seems to be preserved So everything seems to
> > work as expected
> >
> > `./admin.sh -v -i -file
> > ~/work/openmeetings/backup/backup_2015_12_07_03_35_39.zip`
> >
> > Could you please provide your steps?
> >
> > On Sun, Aug 5, 2018 at 10:35 AM Maxim Solodovnik <[email protected]>
> > wrote:
> > >
> > > According to pictures uploaded by users: format change does not
> > > affect such profile images, cause file name with extension is
> > > stored in xml/DB :))) On Sun, Aug 5, 2018 at 10:30 AM Maxim
> > > Solodovnik <[email protected]> wrote:
> > > >
> > > > Hello Aaron,
> > > >
> > > > Thanks for detailed testing
> > > > Profile folders should be moved to proper locations ...
> > > > (https://github.com/apache/openmeetings/blob/4.0.x/openmeetings-
> > > > in
> > > > st
> > > > all/src/main/java/org/apache/openmeetings/backup/BackupImport.ja
> > > > va
> > > > #L
> > > > 1040)
> > > >
> > > > I'll double-check and report back On Sun, Aug 5, 2018 at 2:42 AM
> > > > Aaron H <[email protected]> wrote:
> > > > >
> > > > > After further testing it will still accept the profile image being in
> > > > > jpg format. Any new image will be saved in the .png format.
> > > > >
> > > > > Looks like my problem I was having was due to the import not running
> > > > > properly (I'm assuming). The user.xml import was successful (as all
> > > > > user data was there), but what failed was putting each user's profile
> > > > > (profile_#) into the proper place
> > > > > /webapps/openmeeting/upload/profiles/. Instead it left all the files
> > > > > in the import/<importdatetime>/roomfiles/profiles/ folder. So while
> > > > > the users.xml files was parsed and it said in each profile_# the
> > > > > profile image was profile.jpg, that jpg file did not exist due to it
> > > > > not being imported properly.
> > > > >
> > > > > After manually moving each users profile_# folder into the proper
> > > > > place everything worked as expected. If a user had no stored image
> > > > > then there was no need to do the import as their profile would be
> > > > > created on their returning login.
> > > > >
> > > > > So it was either 1 of 2 things. Either A) a bad import function (as
> > > > > imported filed were placed in wrong locations, or B) import partially
> > > > > failed due to image format change. Was 4.0.4 image format still .jpg
> > > > > or had that one been moved to .png? I was going to stand up an
> > > > > official release if file format was still .jpg to see if it can
> > > > > narrow down what caused the import to not run fully.
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: [email protected] <[email protected]>
> > > > > Sent: Saturday, August 4, 2018 6:23 AM
> > > > > To: [email protected]
> > > > > Subject: RE: Conference Room creation update error
> > > > >
> > > > > Yes looks like the room crashing has been resolved. Thank you for
> > > > > the prompt fix.
> > > > >
> > > > > The profile image I am referring to is the default profile image that
> > > > > is located at /webapps/Openmeetings/images/profile.* But I see why
> > > > > the issue. Looks like the default image format was changed from .jpg
> > > > > to .png and in my customization script I was importing profile.jpg so
> > > > > I changed the script to .png and this resolved that issue. Didn't
> > > > > notice the file extension had changed.
> > > > >
> > > > > The last issue I am seeing is the import from the previous backup.
> > > > > It is importing all the users data for the database account
> > > > > name / password / contact info / .etc, but it is not importing
> > > > > the users profile image they had uploaded. The import was
> > > > > placed at
> > > > >
> > > > > /webapps/Openmeetings/upload/import/import_2018_08_04_05_59_04
> > > > > /r
> > > > > oo
> > > > > mFiles/profiles/
> > > > >
> > > > > so when a returning user logs in their profile is created:
> > > > >
> > > > > /webapps/Openmeetings/upload/profiles/
> > > > >
> > > > > But just now looking as I uploaded a new profile picture for myself
> > > > > as a test I see the reason. It looks like it stems from the file
> > > > > format change. The backup has everything as profile.jpg where it is
> > > > > looking for a .png file.
> > > > >
> > > > > Just a heads up for anyone taking an older backup from a
> > > > > previous version, you will have to manually copy each users
> > > > > profile.jpg file from the import folder to each users profile
> > > > > space as a .png file
> > > > >
> > > > > For me this was an example:
> > > > >
> > > > > cp
> > > > > /opt/current/webapps/trade-group/upload/import/import_2018_08_
> > > > > 04
> > > > > _0 5_59_04/roomFiles/profiles/profile_2/profile.jpg
> > > > > /opt/current/webapps/trade-group/upload/profiles/profile_2/pro
> > > > > fi
> > > > > le
> > > > > .png
> > > > >
> > > > > this must be done for each user or tell each user that they just have
> > > > > to re-upload their image if they want one.
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: Maxim Solodovnik <[email protected]>
> > > > > Sent: Friday, August 3, 2018 11:08 PM
> > > > > To: Openmeetings user-list <[email protected]>
> > > > > Subject: Re: Conference Room creation update error
> > > > >
> > > > > Just have tried, profile images in jpg format are being displayed as
> > > > > expected Could you please tell me what were your exact steps to
> > > > > reproduce?
> > > > >
> > > > > BTW Thanks a lot for checking latest nightly :))) On Sat, Aug
> > > > > 4,
> > > > > 2018 at
> > > > > 9:39 AM Maxim Solodovnik <[email protected]> wrote:
> > > > > >
> > > > > > Hello Aaron,
> > > > > >
> > > > > > page crash was just fixed
> > > > > > Will take a look at profile image issue (most probably
> > > > > > caused by migration from JPG to PNG)
> > > > > >
> > > > > > According to new install, then import I would recommend to
> > > > > > use command line admin in this case
> > > > > > http://openmeetings.apache.org/CommandLineAdmin.html
> > > > > > the options I'm using: -file --skip-default-objects On
> > > > > > Sat, Aug 4,
> > > > > > 2018 at 9:26 AM <[email protected]> wrote:
> > > > > > >
> > > > > > > Looks like my 1st attachment did not have the complete debug in
> > > > > > > it.
> > > > > > > Attached is the full log.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Looks like also whatever is causing this error is also
> > > > > > > what is causing the import not to work properly. I use a
> > > > > > > different profile.jpg image for default users (located at
> > > > > > > /webapps/openmeetings/images/profile.jpg) and that does
> > > > > > > not get shown on the users profile. It is pulling the
> > > > > > > image that is the standard image that has the question mark in
> > > > > > > the body.
> > > > > > > Not even sure where it is pulling that from since the file
> > > > > > > was replaced with a different file all together. When you
> > > > > > > copy the image location it states
> > > > > > > (/profile/1?anticache=1532949138000)
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > I re-installed the official release and that one works as
> > > > > > > expected (room configuration and changed default image)
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > From: [email protected] <[email protected]>
> > > > > > > Sent: Friday, August 3, 2018 9:19 PM
> > > > > > > To: [email protected]
> > > > > > > Subject: Conference Room creation update error
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Looks like an old error is back. I just installed the
> > > > > > > latest nightly build and now get thrown to the internal
> > > > > > > error page if you try to update and existing conference
> > > > > > > room or when you type the first letter for a new room name.
> > > > > > > Looks like the old error where even if the user was
> > > > > > > granted admin access Group Admin Access is denied (see
> > > > > > > attached log)
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Version4.0.5-SNAPSHOT
> > > > > > >
> > > > > > > Revisionb154bef
> > > > > > >
> > > > > > > Build date2018-08-03T10:13:48Z
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Also looks like when doing the import there is a problem.
> > > > > > > When you are 1st setting up your new install of OM you
> > > > > > > create an admin account; so in the database that is “Profile 1”.
> > > > > > > Where the problem lies is when you do an export from your
> > > > > > > old system it also exports the old “admin” account (which
> > > > > > > on the old system was also profile_1) but when you do the
> > > > > > > import since there is already a profile_1 it moves
> > > > > > > everything down 1 so the old admin account become id 2 on down
> > > > > > > the line. My account when exported was profile_2 but now my
> > > > > > > account is now labeled as profile_3 so the
> > > > > > > image is not there but the old admin account has my profile.jpg.
> > > > > > > (also
> > > > > > > in attachment)
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > WBR
> > > > > > Maxim aka solomax
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > WBR
> > > > > Maxim aka solomax
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > WBR
> > > > Maxim aka solomax
> > >
> > >
> > >
> > > --
> > > WBR
> > > Maxim aka solomax
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
> >
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
DEBUG 08-06 17:38:51.529 o.a.o.c.u.WebSocketHelper:151 [.0.0-443-exec-5] -
Sending WebSocket message: roomEnter
DEBUG 08-06 17:38:51.672 o.a.o.d.d.f.FileItemDao:55 [Thread-8] - getByOwner()
started
DEBUG 08-06 17:38:51.677 o.a.o.d.d.f.FileItemDao:50 [Thread-8] - getByRoom
roomId :: 5
DEBUG 08-06 17:38:51.939 o.a.o.w.r.RoomBroadcaster:57 [.0.0-443-exec-3] -
----------- sendUpdatedClient
DEBUG 08-06 17:38:51.953 o.a.o.w.r.RoomBroadcaster:57 [.0.0-443-exec-3] -
----------- sendUpdatedClient
DEBUG 08-06 17:38:51.965 o.a.o.c.r.ScopeApplicationAdapter:791 [Thread-9] -
[MessageSender] -> 'Unable to send message to NULL scope' clientUpdated, null
DEBUG 08-06 17:38:51.972 o.a.o.c.u.WebSocketHelper:151 [.0.0-443-exec-3] -
Sending WebSocket message: rightUpdated 9ca78615-d0df-422e-a055-9ad935209c31
DEBUG 08-06 17:38:51.984 o.a.o.c.r.ScopeApplicationAdapter:791 [Thread-10] -
[MessageSender] -> 'Unable to send message to NULL scope' clientUpdated, null
DEBUG 08-06 17:38:52.064 o.a.o.c.u.WebSocketHelper:229 [.0.0-443-exec-9] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:38:52.172 o.a.o.c.u.WebSocketHelper:229 [.0.0-443-exec-4] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:38:52.315 o.a.o.c.u.WebSocketHelper:229 [0.0-443-exec-10] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:38:52.464 o.a.o.d.u.AuthLevelUtil:42 [.0.0-443-exec-9] - Level
Admin :: [GRANTED]
DEBUG 08-06 17:38:52.618 o.a.o.c.u.WebSocketHelper:229 [.0.0-443-exec-2] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:38:52.693 o.a.o.c.u.WebSocketHelper:229 [.0.0-443-exec-5] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:38:52.764 o.a.o.c.u.WebSocketHelper:229 [.0.0-443-exec-3] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:38:52.995 o.a.o.c.u.WebSocketHelper:229 [.0.0-443-exec-6] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:38:53.069 o.a.o.c.u.WebSocketHelper:229 [.0.0-443-exec-4] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:39:07.780 o.a.o.c.d.f.FileProcessor:71 [.0.0-443-exec-1] - file
extension: png
Aug 06, 2018 5:39:08 PM org.apache.tika.config.InitializableProblemHandler$3
handleInitializableProblem
WARNING: J2KImageReader not loaded. JPEG2000 files will not be processed.
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.
WARN 08-06 17:39:08.008 o.a.t.p.PDFParser:69 [.0.0-443-exec-1] -
J2KImageReader not loaded. JPEG2000 files will not be processed.
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.
Aug 06, 2018 5:39:08 PM org.apache.tika.config.InitializableProblemHandler$3
handleInitializableProblem
WARNING: org.xerial's sqlite-jdbc is not loaded.
Please provide the jar on your classpath to parse sqlite files.
See tika-parsers/pom.xml for the correct version.
WARN 08-06 17:39:08.046 o.a.t.p.SQLite3Parser:69 [.0.0-443-exec-1] -
org.xerial's sqlite-jdbc is not loaded.
Please provide the jar on your classpath to parse sqlite files.
See tika-parsers/pom.xml for the correct version.
DEBUG 08-06 17:39:08.391 o.a.o.c.d.f.FileProcessor:75 [.0.0-443-exec-1] -
isAsIs: true
DEBUG 08-06 17:39:08.392 o.a.o.c.d.f.FileProcessor:105 [.0.0-443-exec-1] -
writing file to:
/opt/current/webapps/trade-group/upload/files/0cbf1150-5fd5-4f41-b9e8-19d46585f0db/0cbf1150-5fd5-4f41-b9e8-19d46585f0db.png
DEBUG 08-06 17:39:08.393 o.a.o.c.d.f.FileProcessor:122 [.0.0-443-exec-1] -
##### convert it to PNG:
DEBUG 08-06 17:39:08.480 o.a.o.c.d.f.FileProcessor:135 [.0.0-443-exec-1] -
fileId: 5
DEBUG 08-06 17:39:08.481 o.a.o.c.d.f.FileProcessor:96 [.0.0-443-exec-1] - Clean
up was successful ? true
DEBUG 08-06 17:39:08.499 o.a.o.d.d.f.FileItemDao:55 [.0.0-443-exec-1] -
getByOwner() started
DEBUG 08-06 17:39:08.504 o.a.o.d.d.f.FileItemDao:50 [.0.0-443-exec-1] -
getByRoom roomId :: 5
DEBUG 08-06 17:39:08.509 o.a.o.c.u.WebSocketHelper:229 [.0.0-443-exec-1] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:39:08.526 o.a.o.c.u.WebSocketHelper:229 [.0.0-443-exec-1] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:39:08.769 o.a.o.c.u.WebSocketHelper:229 [.0.0-443-exec-5] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:39:15.131 o.a.o.c.u.WebSocketHelper:229 [.0.0-443-exec-6] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:39:16.486 o.a.o.w.c.MainPanel:118 [.0.0-443-exec-4] - Sending
WebSocket PING
DEBUG 08-06 17:39:23.156 o.a.o.c.u.WebSocketHelper:229 [.0.0-443-exec-9] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:39:23.270 o.a.o.c.u.WebSocketHelper:229 [.0.0-443-exec-1] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:39:23.339 o.a.o.c.u.WebSocketHelper:229 [.0.0-443-exec-2] -
Sending WebSocket message: {"type":"wb"}
DEBUG 08-06 17:39:31.511 o.a.o.c.d.f.FileProcessor:71 [.0.0-443-exec-4] - file
extension: png
DEBUG 08-06 17:39:31.543 o.a.o.c.d.f.FileProcessor:75 [.0.0-443-exec-4] -
isAsIs: true
DEBUG 08-06 17:39:31.545 o.a.o.c.d.f.FileProcessor:105 [.0.0-443-exec-4] -
writing file to:
/opt/current/webapps/trade-group/upload/files/cacb6339-24d2-49f2-983c-aa25cd0e301b/cacb6339-24d2-49f2-983c-aa25cd0e301b.png
DEBUG 08-06 17:39:31.546 o.a.o.c.d.f.FileProcessor:122 [.0.0-443-exec-4] -
##### convert it to PNG:
DEBUG 08-06 17:39:31.574 o.a.o.c.d.f.FileProcessor:135 [.0.0-443-exec-4] -
fileId: 6
DEBUG 08-06 17:39:31.576 o.a.o.c.d.f.FileProcessor:96 [.0.0-443-exec-4] - Clean
up was successful ? true
DEBUG 08-06 17:39:31.643 o.a.o.d.d.f.FileItemDao:55 [.0.0-443-exec-4] -
getByOwner() started
DEBUG 08-06 17:39:31.659 o.a.o.d.d.f.FileItemDao:50 [.0.0-443-exec-4] -
getByRoom roomId :: 5
DEBUG 08-06 17:39:46.610 o.a.o.w.c.MainPanel:118 [.0.0-443-exec-8] - Sending
WebSocket PING
DEBUG 08-06 17:39:31.511 o.a.o.c.d.f.FileProcessor:71 [.0.0-443-exec-4] - file
extension: png
DEBUG 08-06 17:39:31.543 o.a.o.c.d.f.FileProcessor:75 [.0.0-443-exec-4] -
isAsIs: true
DEBUG 08-06 17:39:31.545 o.a.o.c.d.f.FileProcessor:105 [.0.0-443-exec-4] -
writing file to:
/opt/current/webapps/trade-group/upload/files/cacb6339-24d2-49f2-983c-aa25cd0e301b/cacb6339-24d2-49f2-983c-aa25cd0e301b.png
DEBUG 08-06 17:39:31.546 o.a.o.c.d.f.FileProcessor:122 [.0.0-443-exec-4] -
##### convert it to PNG:
DEBUG 08-06 17:39:31.574 o.a.o.c.d.f.FileProcessor:135 [.0.0-443-exec-4] -
fileId: 6
DEBUG 08-06 17:39:31.576 o.a.o.c.d.f.FileProcessor:96 [.0.0-443-exec-4] - Clean
up was successful ? true
DEBUG 08-06 17:39:31.643 o.a.o.d.d.f.FileItemDao:55 [.0.0-443-exec-4] -
getByOwner() started
DEBUG 08-06 17:39:31.659 o.a.o.d.d.f.FileItemDao:50 [.0.0-443-exec-4] -
getByRoom roomId :: 5
