|
|
|
|
| Re: /proc pid number off-by-one? ... 2.6.18-028test003.1 [message #8286 is a reply to message #8236] |
Mon, 13 November 2006 17:19   |
John Kelly
Messages: 97
Registered: May 2006
Location: Palmetto State
|
Member |
|
|
#!/bin/sh
SENDMAIL_CLIENT_ARGS="-L sendmail-client -Ac -qp30m"
msppid=/var/spool/clientmqueue/sm-client.pid
srvpid=/var/run/sendmail.pid
killproc -p $msppid -i $srvpid -TERM /usr/sbin/sendmail
startproc -p $msppid -i $srvpid /usr/sbin/sendmail $SENDMAIL_CLIENT_ARGS
Here is a reduced test case, the problem happens on the last line, startproc. The problem seems like some kind of race, because sometimes it happens, and other times, it does not.
I tried strace with startproc, but that seems to avoid the race. However, after running the test script above many times, followed immediately by "ps ax," I was able to see what the problem is (shown below). There is a zombie with the PID number in question, and the actual PID number of the running sendmail process is one higher. Seeing the zombie with "ps ax" is hard to reproduce, I only captured it one time.
This never happened until I started using the openvz 2.6.18 kernel. I don't know if this happens with any other VE, suse 9.1 is the only one I use enough to produce the problem.
startproc: cannot stat /proc/1372/exe: Permission denied
PID TTY STAT TIME COMMAND
1 ? Rs 0:00 init [3]
28095 ? Ss 0:00 sendmail: accepting connections
28107 ? Ss 0:00 /usr/sbin/sshd -o PidFile=/var/run/sshd.init.pid
28113 ? Ss 0:00 /usr/sbin/xinetd
28119 ? Ss 0:00 /usr/sbin/cron
28276 pts/1 Ss+ 0:00 -bash
1372 pts/0 Z 0:00 [sendmail] <defunct>
1373 ? Ss 0:00 sendmail: Queue control
1374 ? S 0:00 sendmail: running queue: /var/spool/clientmqueue
1375 pts/0 R+ 0:00 ps ax
[Updated on: Mon, 13 November 2006 20:00] Report message to a moderator |
|
|
|
|
|
|
|
|
|
| Re: /proc pid number off-by-one? ... 2.6.18-028test003.1 [message #8314 is a reply to message #8313] |
Wed, 15 November 2006 02:33 |
John Kelly
Messages: 97
Registered: May 2006
Location: Palmetto State
|
Member |
|
|
| dev wrote on Tue, 14 November 2006 17:50 |
can you give me an access to the node with exact instructions on reproducing both issues (sendmail and aptitude)?
|
Yes for aptitude, since that's in a test environment. Please send me an email, and tell me your IP address. I protect ssh logins with /etc/hosts.allow.
Email: jak@isp2dial.com
Alternate email: isp2dial@fastmail.fm
My kernel config is kernel-2.6.18-028test003-i686.config.ovz, with local changes, mostly to drop unneeded network and scsi drivers. I did remove the VDSO compat, but according to what I read, that should not make any difference, since my glibc is new enough.
Here are my kernel config changes which may possibly be relevant:
--- kernel-2.6.18-028test003-i686.config.ovz 2006-11-09 12:33:27.000000000 -0500
+++ k2618.openvz.v1 2006-11-10 09:23:23.000000000 -0500
@@ -1,7 +1,7 @@
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.18-028test003
-# Thu Nov 9 17:34:51 2006
+# Fri Nov 10 09:23:23 2006
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
@@ -194,14 +194,14 @@
# CONFIG_EFI is not set
# CONFIG_REGPARM is not set
# CONFIG_SECCOMP is not set
-# CONFIG_HZ_100 is not set
+CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
-CONFIG_HZ_1000=y
-CONFIG_HZ=1000
+# CONFIG_HZ_1000 is not set
+CONFIG_HZ=100
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
-CONFIG_COMPAT_VDSO=y
+# CONFIG_COMPAT_VDSO is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
#
@@ -858,7 +827,7 @@
#
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
-CONFIG_BONDING=m
+# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m
@@ -1111,8 +1068,56 @@
#
# Watchdog Cards
#
-# CONFIG_WATCHDOG is not set
-# CONFIG_HW_RANDOM is not set
+CONFIG_WATCHDOG=y
+# CONFIG_WATCHDOG_NOWAYOUT is not set
+
+#
+# Watchdog Device Drivers
+#
+CONFIG_SOFT_WATCHDOG=m
+# CONFIG_ACQUIRE_WDT is not set
+# CONFIG_ADVANTECH_WDT is not set
+# CONFIG_ALIM1535_WDT is not set
+# CONFIG_ALIM7101_WDT is not set
+# CONFIG_SC520_WDT is not set
+# CONFIG_EUROTECH_WDT is not set
+# CONFIG_IB700_WDT is not set
+# CONFIG_IBMASR is not set
+# CONFIG_WAFER_WDT is not set
+# CONFIG_I6300ESB_WDT is not set
+CONFIG_I8XX_TCO=m
+# CONFIG_SC1200_WDT is not set
+# CONFIG_60XX_WDT is not set
+# CONFIG_SBC8360_WDT is not set
+# CONFIG_CPU5_WDT is not set
+# CONFIG_W83627HF_WDT is not set
+# CONFIG_W83877F_WDT is not set
+# CONFIG_W83977F_WDT is not set
+# CONFIG_MACHZ_WDT is not set
+# CONFIG_SBC_EPX_C3_WATCHDOG is not set
+
+#
+# ISA-based Watchdog Cards
+#
+# CONFIG_PCWATCHDOG is not set
+# CONFIG_MIXCOMWD is not set
+# CONFIG_WDT is not set
+
+#
+# PCI-based Watchdog Cards
+#
+# CONFIG_PCIPCWATCHDOG is not set
+# CONFIG_WDTPCI is not set
+
+#
+# USB-based Watchdog Cards
+#
+# CONFIG_USBPCWATCHDOG is not set
+CONFIG_HW_RANDOM=y
+CONFIG_HW_RANDOM_INTEL=m
+CONFIG_HW_RANDOM_AMD=m
+# CONFIG_HW_RANDOM_GEODE is not set
+CONFIG_HW_RANDOM_VIA=m
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_DTLK is not set
@@ -1492,10 +1497,7 @@
CONFIG_JBD=y
CONFIG_JBD_DEBUG=y
CONFIG_FS_MBCACHE=y
-CONFIG_REISERFS_FS=y
-# CONFIG_REISERFS_CHECK is not set
-CONFIG_REISERFS_PROC_INFO=y
-# CONFIG_REISERFS_FS_XATTR is not set
+# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
# CONFIG_XFS_FS is not set
[Updated on: Wed, 15 November 2006 02:56] Report message to a moderator |
|
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
