Hi,
you need to do several things in order to collect messages inside a Container:
1) install klogd. In my case it was a part of "sysklogd" package and was not installed by default.
[root@dhcp-10-30-19-35 run]# rpm -qf `which klogd`
sysklogd-1.4.1-46.el5
[root@dhcp-10-30-19-35 run]# cat /etc/*rele*
CentOS release 5.4 (Final)
2) "syslog" is hacked not to start klogd, so you need to revert the hack.
--- /etc/init.d/syslog.log 2010-06-23 18:22:06.000000000 +0400
+++ /etc/init.d/syslog 2010-06-23 18:22:39.000000000 +0400
@@ -38,14 +38,14 @@ start() {
RETVAL=$?
echo
echo -n $"Starting kernel logger: "
- passed klogd skipped #daemon klogd $KLOGD_OPTIONS
+ daemon klogd $KLOGD_OPTIONS
echo
[ $RETVAL -eq 0 ] && touch /var/lock/subsys/syslog
return $RETVAL
}
stop() {
echo -n $"Shutting down kernel logger: "
- passed klogd skipped #killproc klogd
+ killproc klogd
echo
echo -n $"Shutting down system logger: "
killproc syslogd
@@ -56,7 +56,7 @@ stop() {
}
rhstatus() {
status syslogd
- #status klogd
+ status klogd
}
restart() {
stop
Why it was done so?:
it was done historically in order to maximize the performance: on the one hand you'd better run syslog because it collects a lot of logs from userspace applications, on the other hand messages from kernel most often are useless inside a Container.
Hope that helps.
--
Konstantin
) 1 Vote
OpenVZ Forum
Members
Search
Help
Register
Login
Home
