Thomas Osterried created OPENMEETINGS-636:
---------------------------------------------
Summary: field report: Problems with my installation on debian
wheezy
Key: OPENMEETINGS-636
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-636
Project: Openmeetings
Issue Type: Test
Affects Versions: 2.1.0 Apache Release
Reporter: Thomas Osterried
My first installation on debian wheezy went quite ok (afair, I had an issue
that I could not login. I cleared the database and installed again). My video
recording test lead to dark pictures, with correct audio.
My second installation on a better server on debian wheezy:
1. Recording did not work (due to log: sox not found - should have to put
/usr/bin to path, in admin interface), ffmpeg was not found (path problem),
etc.. Obviously, the process inherits a bad environment variable for $PATH
(empty path?). I added
PATH=/bin:/usr/bin:/usr/local/bin:$PATH
to the /etc/init.d/red5 script. Then the path problem disappeared.
2. Due to an unknown reason, OM does not start on system boot.
$ ls -l /etc/rc2.d/*red5
lrwxrwxrwx 1 root root 14 May 12 11:54 /etc/rc2.d/S99red5 -> ../init.d/red5
$ ls -l /etc/init.d/*red5
-rwxr-xr-x 1 root root 1877 May 17 22:47 /etc/init.d/red5
I added /etc/init.d/red5 start to /etc/rc.local and it starts on boot. Hmm..
3. It took me *hours* to trace a problem with jodconverter.
system default for jod.path is "./jodconverter-core-3.0-beta-4/lib"
It worked on my first test installation, but not on the second server.
Startup-Script (/etc/init.d/red5) is copied -> same root path (/usr/lib/red5).
On both systems, iodconverter-core... is in /usr/lib/red5/webapps/openmeetings
(checked it, of course)
On the first system, jodconverter worked fine. On the new system,
log/openmeetings.log states JOD converter not found. I moved it to
/usr/lib/red5 - then it's found. jod.path should be
./webapps/openmeetings/jodconverter-core-3.0-beta-4/lib
Can't say why it diffes on both debian wheezy systems.
4. I still have a problem with the jodconverter on the new system. Log:
DEBUG 05-18 09:51:12.009 o.a.o.d.f.FileProcessor:101 [http-bio-0.0.0.0-5080-exec
-1] - writing file to: /usr/lib/red5/webapps/openmeetings/uploadtemp/files/7126c
fb1cea4018aa7c6f72097781a7b.odt
$ find /usr/lib/red5/webapps/openmeetings/|grep 7126c
The directory permissions for uploadtemp/ and uploadtemp/files/ are correct.
Interestingly, the file is uploaded, but in upload/, not in uploadtemp/:
/usr/lib/red5/webapps/openmeetings/upload/files/7126cfb1cea4018aa7c6f72097781a7b
/usr/lib/red5/webapps/openmeetings/upload/files/7126cfb1cea4018aa7c6f72097781a7b/7126cfb1cea4018aa7c6f72097781a7b.odt
/usr/lib/red5/webapps/openmeetings/upload/files/7126cfb1cea4018aa7c6f72097781a7b/library.xml
I'd to stop here testing it due to lack of time, but will report what I'll
figure out.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
