Your message dated Sat, 30 Jun 2007 20:43:03 +0400
with message-id <[EMAIL PROTECTED]>
and subject line Closing the bug
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: ejabberd
Version: 1.1.2-8
Severity: important
zeno:~# ps aux | grep ejabberd
root 21342 0.0 0.1 3732 1212 pts/0 S+ 14:14 0:00 /bin/sh
/usr/bin/sensible-editor /tmp/reportbug-ejabberd-20070625-22001-oQaIkA
root 21346 0.0 0.2 4516 2336 pts/0 S+ 14:14 0:00 editor
/tmp/reportbug-ejabberd-20070625-22001-oQaIkA
root 27647 0.0 0.0 2948 732 pts/9 R+ 14:14 0:00 grep --color
ejabberd
zeno:~#
zeno:~# /etc/init.d/ejabberd start
Starting jabber server: ejabberd.
zeno:~# ps aux | grep ejabberd
root 21342 0.0 0.1 3732 1212 pts/0 S+ 14:14 0:00 /bin/sh
/usr/bin/sensible-editor /tmp/reportbug-ejabberd-20070625-22001-oQaIkA
root 21346 0.1 0.2 4516 2348 pts/0 S+ 14:14 0:00 editor
/tmp/reportbug-ejabberd-20070625-22001-oQaIkA
ejabberd 5263 12.5 0.6 19988 6800 pts/9 Sl 14:15 0:00
/usr/lib/erlang/erts-5.5.4/bin/beam -- -root /usr/lib/erlang -progname erl --
-home /var/lib/ejabberd -sname ejabberd -s ejabberd -kernel inetrc
"/etc/ejabberd/inetrc" -ejabberd config "/etc/ejabberd/ejabberd.cfg" log_path
"/var/log/ejabberd/ejabberd.log" -sasl sasl_error_logger
{file,"/var/log/ejabberd/sasl.log"} -mnesia dir "/var/lib/ejabberd" -noshell
-noshell -noinput
root 5531 0.0 0.0 2948 732 pts/9 R+ 14:15 0:00 grep --color
ejabberd
zeno:~#
zeno:~# fuser -n tcp 5223
zeno:~# fuser -n tcp 5222
I am not able to connect to the server after starting it (check ports in config)
zeno:~# /etc/init.d/ejabberd stop
Stopping jabber server: ejabberd already stopped.
zeno:~# ps aux | grep ejabberd
root 21342 0.0 0.1 3732 1212 pts/0 S+ 14:14 0:00 /bin/sh
/usr/bin/sensible-editor /tmp/reportbug-ejabberd-20070625-22001-oQaIkA
root 21346 0.1 0.2 4516 2352 pts/0 S+ 14:14 0:00 editor
/tmp/reportbug-ejabberd-20070625-22001-oQaIkA
ejabberd 5263 0.1 0.6 19988 7088 pts/9 Sl 14:15 0:00
/usr/lib/erlang/erts-5.5.4/bin/beam -- -root /usr/lib/erlang -progname erl --
-home /var/lib/ejabberd -sname ejabberd -s ejabberd -kernel inetrc
"/etc/ejabberd/inetrc" -ejabberd config "/etc/ejabberd/ejabberd.cfg" log_path
"/var/log/ejabberd/ejabberd.log" -sasl sasl_error_logger
{file,"/var/log/ejabberd/sasl.log"} -mnesia dir "/var/lib/ejabberd" -noshell
-noshell -noinput
root 13314 0.0 0.0 2952 732 pts/9 R+ 14:18 0:00 grep --color
ejabberd
zeno:~#
So the init script does not know that ejabberd has been started (perhaps
because the server does not open listen ports), when I start the server
manually, everything seems to work (even stopping
the daemon using the init script).
zeno:~# apt-show-versions | grep ejabberd
ejabberd/unstable uptodate 1.1.2-8
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-k7 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages ejabberd depends on:
ii adduser 3.103 Add and remove users and groups
ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy
ii erlang-nox 1:11.b.4-3 Concurrent, real-time, distributed
ii libc6 2.5-11 GNU C Library: Shared libraries
ii libexpat1 1.95.8-3.4 XML parsing C library - runtime li
ii libssl0.9.8 0.9.8e-5 SSL shared libraries
ii openssl 0.9.8e-5 Secure Socket Layer (SSL) binary a
ii ucf 3.001 Update Configuration File: preserv
ii zlib1g 1:1.2.3-15 compression library - runtime
ejabberd recommends no packages.
-- debconf information excluded
--- End Message ---
--- Begin Message ---
After some conversation with bug submitter we've found that the
problem is in incorrect owner of files in /var/lib/ejabberd.
Some files were owned by root and can't be overwritten by ejabberd user.
It shouldn't happen during normal package installation, because it
starts ejabberd via init script, which sets username to ejabberd.
So, I'm closing the bug.
--
Sergei Golovan
--- End Message ---
