On Wed, 8 Apr 2020 at 16:00, Robert Savickas <robsavic...@gmail.com> wrote:
> Gentlemen, > > You all are an absolute dream team. And the product you produce is superb. > > It works now! After I saw Maxim's message about the flowoutTimeout (that > was a verbatim copy from Alvaro's manual), I just removed that Bean > property, restarted the kurento and the tomcat, and visited my website at > port 5443, and... The 404 error was all gone! > It should contain valid numeric value will fallback to default if removed :) > > I was able to login on my computer and, separately, on my cell phone. Now, > both cameras were visible on both devices, and the sound was going through, > as well. So, Alvaro's document about SSL helped me to also solve the > problem of not working cameras and microphones. > > It is all good now. Should be clear sailing from here on. > > I did have a couple of operational questions, but perhaps Openmeetings > help-files would have the answers; so, if you all have more urgent > questions to answer, no worries. The questions are: > > 1) is it possible to add users from a file that contains their > information, rather than one-by-one. If I have 50 students in class, or > more, it would be more efficient to use a file. I do *not* want to have > self-registration, since that may result in a number of people "from the > street", which might get me in trouble with the administration. > Not out-of-the box > > 2) Is it possible to have a setting whereby each user has the camera > automatically turned on when joining a meeting room and the microphone > turned off? Furthermore, it would be excellent if I can restrict their > ability to turn off the camera (the microphone can be free under their > control, so that they can ask questions). Because, otherwise, they may turn > the camera off, and I do not have a way to see if they are following the > class or not. > > Camera will start automatically in room og type "conference" there is no chance to *force* users to have camera ON (as well as we can't stop them from unplugging USB camera for ex.) > 3) Even less pressing question. Whether there is a way to integrate users > between Openmeetings and B2Evolution.... Recently, I have been using > B2Evolution to run my websites. All my students have accounts on the B2E > site relevant to their specific classes (each class has its own DB on > mariadb). It would be superb to transfer those users to Openmeetings, > without having to register them separately. I guess this should be done > somehow via mariadb databases, between the DB used by Openmeetings and the > DB used by B2E... > Not sure what BEvolution is OpenMeeting is plugable to many CMS, so such integration can be created > > Thank you very much for your all's prompt and helpful responses with > solving the 404 error. Honestly, I did not dare to hope that we would have > that resolved before the sun rises this morning, but we did! > > Have a good the rest of the day and stay safe. > > Robert. > > On Wed, Apr 8, 2020 at 4:37 AM Maxim Solodovnik <solomax...@gmail.com> > wrote: > >> Hello Alvaro, >> >> `-u` parameter for catalina.sh is useless :( it will not change current >> user >> I believe it should be >> sudo -u USER ./bin/catalina.sh ....... >> >> >> On Wed, 8 Apr 2020 at 15:34, Alvaro <zurca...@gmail.com> wrote: >> >>> >>> i think you have the right "kurento" user not nobody at: >>> >>> /etc/init.d/tomcat3 >>> >>> $CATALINA_HOME/bin/startup.sh -u *kurento* -Dcatalina.base$CATALINA_BASE >>> >>> >>> ........................ >>> >>> El mié, 08-04-2020 a las 04:03 -0400, Robert Savickas escribió: >>> >>> Dear Alvaro, >>> >>> Thank you for your response and your excellent manuals! >>> >>> Yes, I did have it as kurento: >>> >>> # Settings loaded by the initscript >>> START_DAEMON="true" # If not "true", the daemon will refuse to load >>> DAEMON_ARGS="" # Passed directly to the kurento-media-server >>> executable >>> DAEMON_USER="kurento" # User as whom Kurento Media Server will run >>> DAEMON_LOG_DIR="/var/log/kurento-media-server" # Where to store daemon >>> logs >>> >>> But to be sure, I just now restarted kurento and tried to access the >>> site. Still Error 404. I did completely clear the history from my browser. >>> >>> Even when I access the site over the 5080 port, with just http (without >>> the "s"), still Error 404. >>> >>> Thank you >>> Robert. >>> >>> On Wed, Apr 8, 2020 at 3:54 AM Alvaro <zurca...@gmail.com> wrote: >>> >>> Robert, please be sure you made this: >>> >>> >>> sudo nano /etc/default/kurento-media-server >>> >>> ...and there is: >>> >>> >>> DAEMON_USER="kurento" ...not nobody >>> >>> >>> ...and then restart kurento: >>> >>> >>> sudo /etc/init.d/kurento-media-server restart >>> >>> >>> >>> ........................... >>> >>> >>> >>> El mié, 08-04-2020 a las 14:17 +0700, Maxim Solodovnik escribió: >>> > This one is useless >>> > please share more :)) >>> > >>> > On Wed, 8 Apr 2020 at 14:15, Robert Savickas <robsavic...@gmail.com> >>> > wrote: >>> > > >>> > > Dear Maxim, >>> > > >>> > > Thank you for your prompt attention to my question. Below, I post >>> > > the last section of the catalina.out file. This type of log appears >>> > > more than once in that file. Perhaps, once for each launch of the >>> > > tomcat. >>> > > >>> > > Thank you. >>> > > Robert. >>> > > >>> > > 08-Apr-2020 01:54:23.731 INFO [hz.server-1.scheduled.thread-] >>> > > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResou >>> > > rceLoading Illegal access: this web application instance has been >>> > > stopped already. Could not load >>> > > [com.hazelcast.util.executor.CachedExecutorServiceDelegate$1]. The >>> > > following stack trace is thrown for debugging purposes as well as >>> > > to attempt to terminate the thread which caused the illegal access. >>> > > java.lang.IllegalStateException: Illegal access: this web >>> > > application instance has been stopped already. Could not load >>> > > [com.hazelcast.util.executor.CachedExecutorServiceDelegate$1]. The >>> > > following stack trace is thrown for debugging purposes as well as >>> > > to attempt to terminate the thread which caused the illegal access. >>> > > at >>> > > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResou >>> > > rceLoading(WebappClassLoaderBase.java:1385) >>> > > at >>> > > org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClass >>> > > Loading(WebappClassLoaderBase.java:1373) >>> > > at >>> > > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappCl >>> > > assLoaderBase.java:1226) >>> > > at >>> > > org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappCl >>> > > assLoaderBase.java:1188) >>> > > at >>> > > com.hazelcast.util.executor.CachedExecutorServiceDelegate$Worker.<i >>> > > nit>(CachedExecutorServiceDelegate.java:218) >>> > > at >>> > > com.hazelcast.util.executor.CachedExecutorServiceDelegate.addNewWor >>> > > kerIfRequired(CachedExecutorServiceDelegate.java:146) >>> > > at >>> > > com.hazelcast.util.executor.CachedExecutorServiceDelegate.execute(C >>> > > achedExecutorServiceDelegate.java:116) >>> > > at >>> > > com.hazelcast.spi.impl.executionservice.impl.DelegateAndSkipOnConcu >>> > > rrentExecutionDecorator.run(DelegateAndSkipOnConcurrentExecutionDec >>> > > orator.java:52) >>> > > at >>> > > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Execu >>> > > tors.java:515) >>> > > at >>> > > java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.ja >>> > > va:305) >>> > > at >>> > > java.base/java.util.concurrent.ScheduledThreadPoolExecutor$Schedule >>> > > dFutureTask.run(ScheduledThreadPoolExecutor.java:305) >>> > > at >>> > > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadP >>> > > oolExecutor.java:1128) >>> > > at >>> > > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Thread >>> > > PoolExecutor.java:628) >>> > > at java.base/java.lang.Thread.run(Thread.java:834) >>> > > at >>> > > com.hazelcast.util.executor.HazelcastManagedThread.executeRun(Hazel >>> > > castManagedThread.java:64) >>> > > at >>> > > com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastMan >>> > > agedThread.java:80) >>> > > >>> > > On Wed, Apr 8, 2020 at 3:01 AM Maxim Solodovnik <solomax666@gmail.c >>> > > om> wrote: >>> > > > >>> > > > (this seems to be some global error, I guess `openmeetings` >>> > > > context >>> > > > fails to start) >>> > > > What do you have in logs/catalina.out? >>> > > > >>> > > > On Wed, 8 Apr 2020 at 13:39, Robert Savickas <robsavickas@gmail.c >>> > > > om> wrote: >>> > > > > >>> > > > > Dear friends, >>> > > > > >>> > > > > This is a bit critical for me because I was hoping to use >>> > > > > OpenMeetings to conduct my online classes at the university (I >>> > > > > am a professor), since we are all locked up at our homes due to >>> > > > > the virus. My class is in less than two days. I had set up >>> > > > > RocketChat with Jitsi meetings previously, but I did not like >>> > > > > them. OpenMeetings is far superior. So, I am trying to move to >>> > > > > OpenMeetings by my next class the day after tomorrow. >>> > > > > >>> > > > > I have followed *verbatim* all the instructions in the two fine >>> > > > > documents by Alvaro Bustos about installing Openmeetings 5.0.0- >>> > > > > M3 on Ubuntu 18.04 and also about installing the SSL >>> > > > > certificated and Coturn. >>> > > > > >>> > > > > Openmeetings was working OK prior to installing SSL; I was able >>> > > > > to go to https://localhost:5443/openmeetings, login, set up, >>> > > > > etc. (In a conference room, the video and sound were not >>> > > > > transmitting, but I reckoned it was because Kurento was not set >>> > > > > up with SSL). >>> > > > > >>> > > > > The installation of SSL went very smoothly, due to the very >>> > > > > well written white paper by Alvaro. >>> > > > > >>> > > > > However, after the SSL installation, when I go to https://local >>> > > > > host:5443/openmeetings, I get error 404: Not found, even though >>> > > > > the directory is definitely there. I reckon that a java servlet >>> > > > > is missing or incorrect, or something similar. But I do not >>> > > > > know how to find it and how to fix it. >>> > > > > >>> > > > > Telnetting into the port 5443 does show that there is service >>> > > > > on that port. Whether I telnet to localhost at 5443 or ip- >>> > > > > address at 5443 or domain-name at 5443, all respond >>> > > > > fine. (Same is true for ports 3478 and 8888.) However, when I >>> > > > > go to https://localhost:5443/openmeetings or https://ip- >>> > > > > address:5443/openmeetings or https://domain- >>> > > > > name:5443/openmeetings, I get the 404 error. >>> > > > > >>> > > > > I would really appreciate it if there are any hints or >>> > > > > suggestions you could offer. >>> > > > > >>> > > > > Thank you. >>> > > > > Robert. >>> > > > >>> > > > >>> > > > >>> > > > -- >>> > > > Best regards, >>> > > > Maxim >>> > >>> > >>> > >>> >>> >> >> -- >> Best regards, >> Maxim >> > -- Best regards, Maxim
