You are not logged in.
Hi my fav. Community,
I'm trying some Jabber Server right now and I'm stuck with prosody.
Some strange things happen, when I use the original ABS package.
When I try to restart It shows something like this:
:: Starting prosody daemon [BUSY]
Usage:
kill pid ... Send SIGTERM to every process listed.
kill signal pid ... Send a signal to every process listed.
kill -s signal pid ... Send a signal to every process listed.
kill -l List all signal names.
kill -L List all signal names in a nice table.
kill -l signal Convert between signal numbers and names.
[FAIL]
I had tried to prevent the init script from saying things like that.:D
So I altered the init script.;)
I changed the function get_pid ()
before:
get_pid() {
if [ -f $pid_file ]; then
/bin/kill -0 $(cat $pid_file)
if [ $? == 0 ]; then
cat $pid_file
fi
fi
}
after:
get_pid() {
ps -fC lua | awk '/prosody/ {print $2}'
}
This worked quite well.
Not at all but the "Usage" message disappeared.
Nevertheless I'm not able to start the server in any way.
The process is running but won't accept connections or things like this.
Someone had experience with this?
Any advice would be helpful...
BTW: Which Jabberserver are you using?
Cheers,
nIcE
Last edited by nicebloom (2009-11-25 20:03:32)
...:::h4cK:y0uR:d4y:::...
Offline
This worked quite well.
Not at all but the "Usage" message disappeared.
hmm not positive what you meant by this.. are you saying the usage message disappeared but prosodyctl still doesn't start? If the daemon still doesn't work, try using this for the get_pid() function:
get_pid() {
pidof -o %PPID /usr/bin/prosodyctl
}
Last edited by tdy (2009-11-20 16:10:33)
Offline
nicebloom wrote:This worked quite well.
Not at all but the "Usage" message disappeared.hmm not positive what you meant by this.. are you saying the usage message disappeared but prosodyctl still doesn't start?
Yes this is what I wanted to say, nearly...
Well it is running but you aren't able to connect.
Also prosodyctl is only for controlling the daemon (as far as I know ... ) which is a lua application with name prosody.
We will see what the weekend will reveal...
Also you have to get the lua pid, because it is run as an lua app as mentioned before.
With the original init script it will start (despite it says "FAIL") and I'm even able to connect.
But things which aren't working:
- restarting
- stopping
Last edited by nicebloom (2009-11-20 16:37:33)
...:::h4cK:y0uR:d4y:::...
Offline
Hi nicebloom, I maintain the Prosody package for Arch. The first bit of output you posted indicates that for whatever reason the kill command received bad parameters, since it's a fairly simple command my guess is that for whatever reason the pid file existed but was empty causing the actual command to be executed to be:
/bin/kill -0
which would generate those usage messages. Could you check if this is the case? I'd like to know why the pid file would be empty.
Also as far as your connection issues, it's probably a configuration issue, if you post your config file I can take a look at it and figure out what's causing it.
Last edited by dbb (2009-11-24 02:26:25)
Offline
Everything seems to be good by now.
Had updated to the 0.6.1 and everything seems fine now.
Hadn't tested the PID thingy before the update, but now everything looks quiet well.
But thanks...
Cheers,
nIcE
...:::h4cK:y0uR:d4y:::...
Offline