Werner,

 

I am currently using OpenMeetings version 2.0 because it is quite stable and 
has few bugs.

 

If you managed to install version 1.91, then I suggest that you follow 
Stephen's instructions from 

https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+related+to+OpenMeetings

Installing OM2.x On Debian64 - Headless.pdf (Debian Squeeze) - Updated 
28/5/2012 

Installing OM2.x On WindowsXP-7-2003-2008.pdf (Windows XP\7\2003\2008) - 
Updated 13/06/2012

Installing OM2.x On Ubuntu64 - Headless.pdf (Unbuntu 12.04) - Updated 23/5/2012

 

and build and install version 2.0 from 

"svn checkout 
http://svn.apache.org/repos/asf/incubator/openmeetings/branches/2.0/";

 

I use Stephen's instructions but I use Debian 32 bit for my OS, not 64 bit and 
all works well.  Stephen will soon be updating the instructions as some of the 
instructions don't go quite as well as the instructions suggest. I have found 
issues with building SWFtools due to issues with the swftools source, and ANT 
is now at version 1.8.4. And a command not mentioned in the instructions is 
also required "ant clean.all" before running the "ant -Ddb=mysql" command.

/usr/adm/apache-ant-1.8.4/bin/ant clean.all

/usr/adm/apache-ant-1.8.4/bin/ant -Ddb=mysql

 

 

I had the following issues when using Stephen's instructions.

 

1)    Do an "ant clean.all" before the "ant -Ddb=mysql".  Since I have been 
adding this extra step in, I can now playback records, in particularly the five 
second "Start recording test".  This issue had been bugging me for quite some 
time.

 

2)    The "swftools-0.9.2" fails (e.g. error messages " rm: invalid option -- 
'o' " and also "-L") to build because this version still has the "-o -L" left 
in the "rm" commands.  Edit these the files "swftools-0.9.2/swfs/Makefile.in" 
and "swftools-0.9.2/swfs/Makefile" to remove these from the file before doing 
the "make" command.  If you have already run make before realising the problem, 
then a "make distclean" should clean up and allow you to do run "make" again.

 

Makefile.in

                rm -f $(pkgdatadir)/swfs/default_viewer.swf -o -L 
$(pkgdatadir)/swfs/default_viewer.swf

                $(LN_S) $(pkgdatadir)/swfs/simple_viewer.swf 
$(pkgdatadir)/swfs/default_viewer.swf

                rm -f $(pkgdatadir)/swfs/default_loader.swf -o -L 
$(pkgdatadir)/swfs/default_loader.swf

                $(LN_S) $(pkgdatadir)/swfs/tessel_loader.swf 
$(pkgdatadir)/swfs/default_loader.swf

 

 

Makefile

                rm -f $(pkgdatadir)/swfs/default_viewer.swf -o -L 
$(pkgdatadir)/swfs/default_viewer.swf

                $(LN_S) $(pkgdatadir)/swfs/simple_viewer.swf 
$(pkgdatadir)/swfs/default_viewer.swf

                rm -f $(pkgdatadir)/swfs/default_loader.swf -o -L 
$(pkgdatadir)/swfs/default_loader.swf

                $(LN_S) $(pkgdatadir)/swfs/tessel_loader.swf 
$(pkgdatadir)/swfs/default_loader.swf

 

And to recover after the build failed, I had to run a "make distclean" before 
running make again.

make distclean

 

3)    ANT has now moved to version 1.8.4 so "wget 
http://mirror.catn.com/pub/apache//ant/binaries/apache-ant-1.8.3-bin.tar.gz"; 
does not work anymore and needs to be replaced by  "wget 
http://mirror.catn.com/pub/apache//ant/binaries/apache-ant-1.8.4-bin.tar.gz";.

 

 

Below are some steps that  I use to build a new server, comparing these steps 
to the documentation may help you too.  I have supplied some of the text output 
from the processes so you have some idea what to expect. I have also included 
some of the steps that I use to customise OpenMeetings the way I like it to be.

 

# mkdir /usr/adm

# cd /usr/adm

# mkdir om20

# cd om20

# svn checkout 
http://svn.apache.org/repos/asf/incubator/openmeetings/branches/2.0/

...

A    2.0/.settings/.jsdtscope

A    2.0/.settings/org.eclipse.wst.common.component

U   2.0

Checked out revision 1359425.

 

# cd 2.0

# /usr/adm/apache-ant-1.8.4/bin/ant clean.all

Buildfile: /usr/adm/om20/2.0/build.xml

clean.dist:

clean.all:

BUILD SUCCESSFUL

Total time: 0 seconds

 

# /usr/adm/apache-ant-1.8.4/bin/ant -Ddb=mysql

-copy-libraries:

     [copy] Copying 10 files to /usr/adm/om20/2.0/dist/red5/lib

     [copy] Copying 84 files to 
/usr/adm/om20/2.0/dist/red5/webapps/openmeetings/WEB-INF/lib

dist:

BUILD SUCCESSFUL

Total time: 2 minutes 19 seconds

 

# mysql -h localhost -u root -p

drop database openmeetings;

CREATE DATABASE openmeetings DEFAULT CHARACTER SET 'utf8';

GRANT ALL PRIVILEGES ON openmeetings.* TO 'openmeetings'@'localhost' IDENTIFIED 
BY 'yourOMpassword' WITH GRANT OPTION;

quit;

 

# mv /usr/lib/red5 /usr/lib/red5.$(date -u +\%Y\%m\%d\%H\%M\%S)

# mv dist/red5 /usr/lib/red5

# cp -R /usr/adm/jodconverter-core-3.0-beta-4 
/usr/lib/red5/webapps/openmeetings/

# mv 
/usr/lib/red5/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml 
/usr/lib/red5/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml-ori

# cp 
/usr/lib/red5/webapps/openmeetings/WEB-INF/classes/META-INF/mysql_persistence.xml
 /usr/lib/red5/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml

# sed -i 's/Username=root/Username=openmeetings/g' 
/usr/lib/red5/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml

# sed -i 's/Password=/Password=yourOMpassword/g' 
/usr/lib/red5/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml

# sed -i 's/0x666666/0x000000/g' 
/usr/lib/red5/webapps/openmeetings/default-theme.xml

# sed -i 's/0xBBBBBB/0x000000/g' 
/usr/lib/red5/webapps/openmeetings/default-theme.xml

# sed -i 's/Apache OpenMeetings \[Incubating\]/OpenMeetings    2\.0\.r[my 
build's revision number]/g' /usr/lib/red5/webapps/openmeetings/config.xml

# sed -i 's/loudnessAcitviation>0</loudnessAcitviation>20</g' 
/usr/lib/red5/webapps/openmeetings/config.xml

# chown -R nobody /usr/lib/red5

# chmod -R 775 /usr/lib/red5/*.sh

# /etc/init.d/red5 start

# netstat -anp | grep java

 

I have had issues with firewalls blocking ports 5080, 1935 and 8088 and because 
I do not run Apache on my OpenMeetings server or on any other server that uses 
port 80 on my Openmeetings IP address I also run these other commands but don't 
do this until your sure your Openmeetings server is running well. And you will 
need to change the "start-stop-daemon --start -c nobody --pidfile $PIDFILE" to 
"start-stop-daemon --start -c root --pidfile $PIDFILE" because when using ports 
below 1024, you need to run the service as root.  I have attached my "red5" 
scripts that are run from "/etc/init.d", depending whether you use Debian or 
Ubuntu, rename the appropriate file to just "red5".

 

# sed -i 's/http.port=5080/http.port=80/g' /usr/lib/red5/conf/red5.properties

# sed -i 's/rtmpt.port=8088/rtmpt.port=80/g' /usr/lib/red5/conf/red5.properties

# sed -i 's/>5080</>80</g' /usr/lib/red5/webapps/openmeetings/config.xml

# sed -i 's/8088/80/g' /usr/lib/red5/webapps/openmeetings/config.xml

 

Thanks,

 

George Kirkham

 

 

 

-----Original Message-----
From: werner ginzky [mailto:[email protected]] 
Sent: Sunday, 15 July 2012 2:34 PM
To: [email protected]
Subject: can´t upload files

 

Hi,

 

I´m newbie using openmeeting. I installed version 1.91, using a howto and so 
long it run´s.

 

We can´t upload file, first I saw a message like "http .... 404", now nothing 
happens klicking on the right button.

 

There are the information:

home drive size 0 MBytes,

public drive size 0 MBytes.

 

How can I change that?

 

How can I upgrade to 2.x? Is that for testing and using later a good idea?

Where can I find a howto?

 

Thanks for helping,

Werner

Attachment: red5.debian
Description: red5.debian

Attachment: red5.ubuntu
Description: red5.ubuntu

Reply via email to