[2.050][SCHEDULED] Ulogd crashed twice within 1 hour

Hi

I've just restarted my acc test VM... (was down since 3 or 4 days as I moved to another place)...

and I got 2 mails about "Ulogd not running" in about 1 hour...

in self monitoring log I have:


2009:10:28-18:05:23 acc selfmonng[4862]: W actionCmd(+): '/etc/init.d/ulog restart'
2009:10:28-18:05:23 acc selfmonng[4862]: W child returned status: exit='0' signal='0'
2009:10:28-18:50:24 acc selfmonng[4862]: I check Failed increment ulogd_running counter 1 - 3
2009:10:28-18:50:29 acc selfmonng[4862]: I check Failed increment ulogd_running counter 2 - 3
2009:10:28-18:50:34 acc selfmonng[4862]: W check Failed increment ulogd_running counter 3 - 3
2009:10:28-18:50:34 acc selfmonng[4862]: Ulogd not running - restarted
2009:10:28-18:50:34 acc selfmonng[4862]: W NOTIFYEVENT Name=ulogd_running Level=INFO Id=114 sent
2009:10:28-18:50:34 acc selfmonng[4862]: W triggerAction: 'cmd'
2009:10:28-18:50:34 acc selfmonng[4862]: W actionCmd(+): '/etc/init.d/ulog restart'
2009:10:28-18:50:35 acc selfmonng[4862]: W child returned status: exit='0' signal='0'

if you need more info, let me know...

I got 2 mails about it...

thx

edit1: crashed once again !

Parents

0 BuBU over 14 years ago

Since yesterday I've a total of 14 notifications about Ulogd not running...

I can provide for an ssh access if needed ?

thx
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 megaposer over 14 years ago in reply to BuBU

Yep, that would be fine - you know the usual address [:)]

As an alternative, you could wait for the upcoming 2.060 and re-check if the issue persists?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BuBU over 14 years ago in reply to megaposer

Yep, that would be fine - you know the usual address [:)]

As an alternative, you could wait for the upcoming 2.060 and re-check if the issue persists?

I've sent you an email with infos to connect on my acc... if u need more info, let me know...
thx
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 megaposer over 14 years ago in reply to BuBU

Mail received ... we will check that as soon as one of our kernel-heroes can support us in this matter.

Thanks!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 megaposer over 14 years ago in reply to megaposer
Hi,

quick update - we activated debug logging so that we can see whether ulog gets restarted because some check is haywire or it dies itself ...

Seems you have the only installation where that is happening though.

BTW: Your machine says:

# date
Thu Oct 29 20:55:13 CET 2009

Want to reach the weekend a bit earlier? [:$]

Cheers,
Henning
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 megaposer over 14 years ago in reply to megaposer
Hi,

quick update - we activated debug logging so that we can see whether ulog gets restarted because some check is haywire or it dies itself ...

Seems you have the only installation where that is happening though.

BTW: Your machine says:

# date
Thu Oct 29 20:55:13 CET 2009

Want to reach the weekend a bit earlier? [:$]

Cheers,
Henning
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 BuBU over 14 years ago in reply to megaposer

for the date/time indeed, that's a virtualbox VM did not updated the time/date...

meanwhile I've just got another notification... so you will probably things for your logs..

thx
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BuBU over 14 years ago in reply to BuBU

Hi

I've installed a new acc 2.060 VM and I get same problem ! ulogd restarted several times..

have u found anything into the logs ?

I think you can reproduce it quite easily by installing acc under Virtualbox... (mine is virtualbox 3.0.8, under ubuntu 9.04)

thx
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel