| View previous topic :: View next topic |
| Author |
Message |
TL_Amitola
n00b
Joined: 25 Jan 2004
Posts: 69
Location: Utah, USA
|
 Posted: Sun Feb 27, 2005 1:00 am Post subject: Critical error messages: metalog process died |
 |
|
I was poking around my log files, trying to get a feel for what each one reports about..
I stuck my head into the /var/log/critical/current and here's what I see:
| Code: | Feb 26 16:14:34 [metalog] Process [4835] died with signal [15]
Feb 26 16:14:34 [metalog] Process [4840] died with signal [15]
Feb 26 16:19:59 [metalog] Process [4838] died with signal [15]
Feb 26 16:19:59 [metalog] Process [4843] died with signal [15]
Feb 26 16:41:47 [metalog] Process [4841] died with signal [15]
Feb 26 16:41:47 [metalog] Process [4846] died with signal [15]
Feb 26 16:52:28 [metalog] Process [4838] died with signal [15]
Feb 26 16:52:28 [metalog] Process [4843] died with signal [15] |
(there were spaces between line that I removed for formatting's sake)
I'm pretty sure those timestamps correlate to when I shutdown the machine (I was playing the kernel settings....)
I have no idea what the importance of the message is, or if I have to worry about it... but since it's in the "critical" directory I felt I better find out if it's something I need to worry about.
Anyone got any information about it?
_________________
:-/ |
|
| Back to top |
|
 |
adaptr
Watchman
Joined: 06 Oct 2002
Posts: 6730
Location: Rotterdam, Netherlands
|
| Posted: Sun Feb 27, 2005 1:43 am Post subject: |
|
|
Signal 15 is SIGTERM - normal termination request.
You may see these quite frequently when shutting down - it means that those processes were terminated by init, so they probably don't have a shutdown script themselves.
If you look at the console when the system is shutting down you will see a line saying:
| Code: | | Sending all processes the TERM signal. |
So there 
_________________
>>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen |
|
| Back to top |
|
|
TL_Amitola
n00b
Joined: 25 Jan 2004
Posts: 69
Location: Utah, USA
|
| Posted: Sun Feb 27, 2005 2:03 am Post subject: |
|
|
ok... I'll assume that means there's nothing to worry about... anyway I can make it so these don't get logged?
_________________
:-/ |
|
| Back to top |
|
|
adaptr
Watchman
Joined: 06 Oct 2002
Posts: 6730
Location: Rotterdam, Netherlands
|
| Posted: Sun Feb 27, 2005 4:15 am Post subject: |
|
|
Well, init sends all processes a TERM signal (and a KILL signal after that) when shutting down to ensure that any pending writes to disk get flushed out before the system enters power-cycle - which resets the disks.
This will only affect processes that did not shut down cleanly - if all your processes are correctly configured for a clean shutdown and all system processes work as they should then there should not be anything for init to kill.
So yes, if you can reproduce this and figure out whats causing it then you should be able to fix it - which causes the messages not to be logged again
_________________
>>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen |
|
| Back to top |
|
|
|
Other Things Gentoo
