Home › Forums › Archives › Computer Support › Online Status Indicator › OSI won’t start
- This topic has 9 replies, 3 voices, and was last updated 21 years, 4 months ago by raypang.
-
AuthorPosts
-
December 14, 2002 at 4:31 pm #13914raypangMember
Hi all
I’ve used OSI on Win2k before, and I’ve moved to a Linux server.
I can’t get it to work! A couple of questions:
1) Can it be run without being root? I get a permissions error if I’m not logged in as root
2) Why is it hanging when I run it, using java -jar status.jar? The log just gets to the Looking for connections on port 91… part.
Cheers
Ray
December 14, 2002 at 6:10 pm #99228TonyMember1) It depends on the security settings on your Linux server.
2) Do you have a firewall installed? (some Linux distributions have a firewall built in)
December 14, 2002 at 6:31 pm #99236raypangMemberIt was running, but only accessible locally, due to the firewall! I took a look at the settings myself, opened up port 91, and it worked.
Thanks for the reply. Just one thing. When I run osi, it still hangs on the “Starting server…” message. OSI is running. Is it safe to ctrl+c out of it, or is there a way of running it as a background service?
December 14, 2002 at 7:47 pm #99233GeoffreyMember/usr/java/j2re…/bin/java -jar /path/to/status.jar &
& makes it run as a daemon in the background, just press “enter” 1 more time after it says “Starting server…” and you are done.
[edit]
and to stop it again (for updates e.a.)
/usr/java/j2re../bin/java -jar /path/to/status.jar stop
[/edit]
December 14, 2002 at 7:52 pm #99235raypangMemberHmm, that almost works. I’m sshing into my server, and it works while the ssh connection is alive. As soon as I exit my ssh client, it stops again. If I was to put this into my startup script, would the extra enter keypress be required?
Thanks
December 14, 2002 at 7:59 pm #99232GeoffreyMemberno the enter is not required, but & should make it run as 100% daemon… so even if you quit the ssh session it should keep running.
Otherwise make a new “start” script.
[you@server path] vi start
“fill in”
/usr/java/j2re1.4.1_01/bin/java -jar /path/to/your/status.jar &
use “ctrl + c” then “:w” then “:q”
in console again
[you@server path] chmod a+x start “press enter”
[you@server path] ./start
try this one.
December 14, 2002 at 8:05 pm #99231GeoffreyMemberQuestion, when you are done in the terminal you type “exit” right ? does it say that it stopped [1++] jobs ?
December 14, 2002 at 8:25 pm #99234raypangMemberRight, now it’s working. I was closing the putty window rather than using exit first, which seems to have done the trick. I still need to press enter, even with that “vi start” trick, but at least it’s working now.
thanks
ps it doesn’t say anything about stopping jobs in the putty log.
December 14, 2002 at 8:39 pm #99230GeoffreyMemberah well pressing enter 1 time isn`t that much work.
putty doesn`t force the jobs to stop, but your o/s is. when a term gets closed “dirty” it can hold all jobs you started. you really should always use “exit” when you logoff.
December 14, 2002 at 9:44 pm #99229TonyMemberYou can find documentation about Running OSI as a service on Linux at http://itwarlocks.com/status/?docs
-
AuthorPosts
- You must be logged in to reply to this topic.