Comment by [email protected]:
I have installed OpenMeeting v1.7 on Ubuntu 10.04.
Everything seems to work EXCEPT starting the OpenMeeting /etc/init.d/red5
file automatically at bootup.
note: yes I have executed the
sudo update-rc.d red5 defaults
and red5 shows up in all of the /etc/rc.* run-level directories
And after reboot if I execute ps -ax | grep red5 ... it shows that it is
running
However, I cannot use a browser to access it
http://myipaddress:5080/openmeetings/
does not work.
If I ...
1) manually stop the red5 that started on system bootup
sudo /etc/init.d/red5 stop
2) THEN if I manually execute
sudo /etc/init.d/red5 start
THEN.... I can successfully access http://myipaddress:5080/openmeetings/
Maybe its just Ubuntu's startup methods -- ubuntu uses Upstart but from
what I've read it also supports backward compatibility with the older
sys5init (rc2.d, rc3.d etc) run level inits
But I cannot for the life of me figure out why it doesn't "fully" start
Openmeetings automatically at bootup.
On reboot could there be a race condition between when the /etc/init.d/red5
script executes AND when the tomcat server is ready? Tomcat starts at an
earlier run level than the /etc/init.d/red5 so I have been dismissing that
as the problem.
Anyone got any ideas what I might be doing wrong?
thanks
brian
For more information:
http://code.google.com/p/openmeetings/wiki/OpenmeetingsEnUbuntu
--
You received this message because you are subscribed to the Google Groups
"OpenMeetings developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/openmeetings-dev?hl=en.
