apache / openmeetings

Mirror of Apache Openmeetings

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Run instructions refer to red5.sh but this file doesn't exist

yurivict opened this issue · comments

Run instructions say:

  - To run the OpenMeetings project:
    - go to `openmeetings-server/target` directory
    - extract `apache-openmeetings-x.x.x.tar.gz` (or `apache-openmeetings-x.x.x.zip` for windows) to **new** directory
    - enter to this new directory and execute `red5.sh` (`red5.bat` for windows)

I run these commands:

mkdir mydir
cd mydir
tar xzf ../work/openmeetings-5.0.0/openmeetings-server/target/apache-openmeetings-5.0.0-M1.tar.gz
find . -name red5.sh

The find command doesn't find red5.sh referred to in the above instructions.

@yurivict what instructions are you referring to?
Could you share the URL?

Here is the full port directory, with the build directory inside. .m2 is removed.
https://people.freebsd.org/~yuri/openmeetings-port-dir.tar

@yurivict you wrote: "Run instructions say:"
What instructions are you referring to? Could you provide an URL?

OM5 should be started with ./bin/startup.sh OR ./bin/catalina.sh run or using systemctl (https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/main/assembly/scripts/openmeetings.service)

Instructions are in the README.md file in the root of your source repository.

./bin/catalina.sh run works. ./bin/catalina.sh start also works.
But ./bin/catalina.sh stop doesn't work. It doesn't stop the server.

It also prints warnings like:

WARN  06-20 02:48:29.247 o.a.o.c.r.KurentoHandler:124 [pool-1-thread-1] - Fail to create Kurento client, will re-try in 10000 ms

and

WARN  06-20 02:46:42.613 o.a.o.c.r.KurentoHandler:112 [io-5080-exec-10] - Media Server is not accessible

For the purposes of a package, the installed files should be in the read-only location (ex. /usr/local), but the DB should be in /var/db/openmeetings.

What is the best way to achieve this?

Instructions are updated
Thanks for catching this :)

Media Server is not accessible KMS (https://www.kurento.org/) need to be installed in the system
OR link to the working KMS need to be specified in applicationContext.xml