Bug#462039: (no subject)

2008-02-01 Thread Sergei Golovan
tags 462039 - unreproducible
thanks

On 1/31/08, Andrey Rahmatullin [EMAIL PROTECTED] wrote:
 All that I can say now: ejabberd starts after dpkg-reconfigure erlang-base
 and after reinstalling erlang-base using dpkg; it starts even if -detached
 is removed from initscript. But it doesn't start after apt-get install
 --reinstall erlang-base (with -detached not removed).

You're right. I can reproduce this behavior. The problem arises if apt
0.7.7 or newer is used. I think it's an apt bug and filed a bugreport
(http://bugs.debian.org/463538). Let's wait for apt maintainers
answer.

-- 
Sergei Golovan



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#462039: (no subject)

2008-01-31 Thread Andrey Rahmatullin
All that I can say now: ejabberd starts after dpkg-reconfigure erlang-base
and after reinstalling erlang-base using dpkg; it starts even if -detached
is removed from initscript. But it doesn't start after apt-get install
--reinstall erlang-base (with -detached not removed).

-- 
WBR, wRAR (ALT Linux Team)


signature.asc
Description: Digital signature


Bug#462039: (no subject)

2008-01-30 Thread Sergei Golovan
I still can't reproduce the bug. I'm afraid I'll have to close it in a few days.

-- 
Sergei Golovan



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#462039: (no subject)

2008-01-24 Thread Andrey Rahmatullin
After today ejabberd upgrade:

Starting jabber server: ejabberd.
Waiting for ejabberd to register admin user..
Admin user [EMAIL PROTECTED] is already registered. Password IS
NOT changed.

And ejabberd is not running.

/var/log/ejabberd/ejabberd.log doesn't contain anything about start.
/var/log/ejabberd/sasl.log is attached.

=PROGRESS REPORT 24-Jan-2008::08:08:55 ===
  supervisor: {local,sasl_safe_sup}
 started: [{pid,0.46.0},
   {name,alarm_handler},
   {mfa,{alarm_handler,start_link,[]}},
   {restart_type,permanent},
   {shutdown,2000},
   {child_type,worker}]

=PROGRESS REPORT 24-Jan-2008::08:08:55 ===
  supervisor: {local,sasl_safe_sup}
 started: [{pid,0.48.0},
   {name,overload},
   {mfa,{overload,start_link,[]}},
   {restart_type,permanent},
   {shutdown,2000},
   {child_type,worker}]

=PROGRESS REPORT 24-Jan-2008::08:08:55 ===
  supervisor: {local,sasl_sup}
 started: [{pid,0.45.0},
   {name,sasl_safe_sup},
   {mfa,
   {supervisor,
   start_link,
   [{local,sasl_safe_sup},sasl,safe]}},
   {restart_type,permanent},
   {shutdown,infinity},
   {child_type,supervisor}]

=PROGRESS REPORT 24-Jan-2008::08:08:55 ===
  supervisor: {local,sasl_sup}
 started: [{pid,0.49.0},
   {name,release_handler},
   {mfa,{release_handler,start_link,[]}},
   {restart_type,permanent},
   {shutdown,2000},
   {child_type,worker}]

=PROGRESS REPORT 24-Jan-2008::08:08:55 ===
 application: sasl
  started_at: [EMAIL PROTECTED]

=PROGRESS REPORT 24-Jan-2008::08:08:55 ===
  supervisor: {local,kernel_safe_sup}
 started: [{pid,0.54.0},
   {name,dets_sup},
   {mfa,{dets_sup,start_link,[]}},
   {restart_type,permanent},
   {shutdown,1000},
   {child_type,supervisor}]

=PROGRESS REPORT 24-Jan-2008::08:08:55 ===
  supervisor: {local,kernel_safe_sup}
 started: [{pid,0.55.0},
   {name,dets},
   {mfa,{dets_server,start_link,[]}},
   {restart_type,permanent},
   {shutdown,2000},
   {child_type,worker}]

=PROGRESS REPORT 24-Jan-2008::08:08:55 ===
  supervisor: {local,mnesia_sup}
 started: [{pid,0.63.0},
   {name,mnesia_event},
   {mfa,{mnesia_sup,start_event,[]}},
   {restart_type,permanent},
   {shutdown,3},
   {child_type,worker}]

=PROGRESS REPORT 24-Jan-2008::08:08:55 ===
  supervisor: {local,mnesia_kernel_sup}
 started: [{pid,0.65.0},
   {name,mnesia_monitor},
   {mfa,{mnesia_monitor,start,[]}},
   {restart_type,permanent},
   {shutdown,3000},
   {child_type,worker}]

=PROGRESS REPORT 24-Jan-2008::08:08:55 ===
  supervisor: {local,mnesia_kernel_sup}
 started: [{pid,0.66.0},
   {name,mnesia_subscr},
   {mfa,{mnesia_subscr,start,[]}},
   {restart_type,permanent},
   {shutdown,3000},
   {child_type,worker}]

=PROGRESS REPORT 24-Jan-2008::08:08:55 ===
  supervisor: {local,mnesia_kernel_sup}
 started: [{pid,0.67.0},
   {name,mnesia_locker},
   {mfa,{mnesia_locker,start,[]}},
   {restart_type,permanent},
   {shutdown,3000},
   {child_type,worker}]

=PROGRESS REPORT 24-Jan-2008::08:08:55 ===
  supervisor: {local,mnesia_kernel_sup}
 started: [{pid,0.68.0},
   {name,mnesia_recover},
   {mfa,{mnesia_recover,start,[]}},
   {restart_type,permanent},
   {shutdown,18},
   {child_type,worker}]

=PROGRESS REPORT 24-Jan-2008::08:08:55 ===
  supervisor: {local,kernel_safe_sup}
 started: [{pid,0.73.0},
   {name,disk_log_sup},
   {mfa,{disk_log_sup,start_link,[]}},
   {restart_type,permanent},
   {shutdown,1000},
   {child_type,supervisor}]

=PROGRESS REPORT 24-Jan-2008::08:08:55 ===

Bug#462039: (no subject)

2008-01-24 Thread Sergei Golovan
On 1/24/08, Andrey Rahmatullin [EMAIL PROTECTED] wrote:
 After today ejabberd upgrade:

 Starting jabber server: ejabberd.
 Waiting for ejabberd to register admin user..
 Admin user [EMAIL PROTECTED] is already registered. Password IS
 NOT changed.

This message means that ejabberdctl script is able to connect to
running ejabberd server and check if admin is registered already. It
means that ejabberd is up.


 And ejabberd is not running.

How do you check whether it's not running?


 /var/log/ejabberd/ejabberd.log doesn't contain anything about start.
 /var/log/ejabberd/sasl.log is attached.

The log is perfect. There's no any problem in it. Ejabberd should be
up and running.

-- 
Sergei Golovan



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#462039: (no subject)

2008-01-24 Thread Andrey Rahmatullin
On Thu, Jan 24, 2008 at 11:57:22AM +0300, Sergei Golovan wrote:
 This message means that ejabberdctl script is able to connect to
 running ejabberd server and check if admin is registered already. It
 means that ejabberd is up.
I see.

 How do you check whether it's not running?
ps(1), netstat(8)


signature.asc
Description: Digital signature


Bug#462039: (no subject)

2008-01-24 Thread Sergei Golovan
On 1/24/08, Andrey Rahmatullin [EMAIL PROTECTED] wrote:
 On Thu, Jan 24, 2008 at 11:57:22AM +0300, Sergei Golovan wrote:
  How do you check whether it's not running?
 ps(1), netstat(8)

Please, show the exact output of
COLUMNS=1000 ps axl |grep ejabberd

and
netstat -ltp |grep beam

after ejabberd failed to start.

-- 
Sergei Golovan



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#462039: (no subject)

2008-01-24 Thread Andrey Rahmatullin
On Thu, Jan 24, 2008 at 12:28:06PM +0300, Sergei Golovan wrote:
 Please, show the exact output of
 COLUMNS=1000 ps axl |grep ejabberd
it's empty

 netstat -ltp |grep beam
it's empty


signature.asc
Description: Digital signature


Bug#462039: (no subject)

2008-01-24 Thread Sergei Golovan
On 1/24/08, Andrey Rahmatullin [EMAIL PROTECTED] wrote:
 On Thu, Jan 24, 2008 at 12:28:06PM +0300, Sergei Golovan wrote:
  Please, show the exact output of
  COLUMNS=1000 ps axl |grep ejabberd
 it's empty

  netstat -ltp |grep beam
 it's empty

I have no idea what hapened. Ejabberd responded to register user
attempt and then quickly disappeared. I could suspect a segfault.

-- 
Sergei Golovan



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]