Hi.
I have a strange problem monitoring the "pickup" process: we have a
monitoring system that, sometimes, warns us with "pickup process not in
memory" (master and qmgr seems to continue running). When we enter the
machine, we notice that pickup is really in memory, but after that
alarm, every monitoring cycle (every 180 seconds) tells us that pickup
is not present in memory as a process.
Starting with the first "alarm" reported by the monitoring tool, pickup
process is reported as "not in memory" in each monitoring cycle, until
we do a "postfix restart". Then it works perfectly again for a
undeterminated amount of time (days, weeks, months).
I can't find any error in the logs... and my master.cf shows:
# grep pickup /etc/postfix/master.cf
pickup fifo n - n 60 1 pickup
I noticed that pickup "wakes up" every 60 seconds, and my monitoring
system "checks processes" every 180 seconds. Maybe it's just
"synchronization" and my monitoring system performs the checking just
when postfix is restarting pickup?
Does the "wake up" restart the process itself?
The docs just say:
"""
Wake up time (default: 0)
Automatically wake up the named service after the
specified number of seconds. The wake up is imple-
mented by connecting to the service and sending a
wake up request. A ? at the end of the wake-up
time field requests that no wake up events be sent
before the first time a service is used. Specify 0
for no automatic wake up.
""
But I don't now if "wake up" means "a signal" or an o.s. "kill + new
process" (which could explain my monitoring incidence).
(if it's that, I can just change 60 to 70 seconds, and that way the "ps
auxwww | grep pickup" won't synchronize with pickup restart).
Is it safe to raise those 60 seconds to a more higher value, such as
600 or so?
Am I right with the "synchronization" hypotesis or could be something
different?
Thanks a lot.
--
Santiago Romero
