Prev: [patch] build failure against db-5.0
Next: Postfix, SASL and LDAPDB [solved]
From: "Len Conrad" on 20 May 2010 15:55
---------- Original Message ----------------------------------
From: Wietse Venema <wietse(a)porcupine.org>
Reply-To: Postfix users <postfix-users(a)postfix.org>
Date: Thu, 20 May 2010 15:34:27 -0400 (EDT)

>Len Conrad:
>> >> postfix/postfix-script: fatal: the Postfix mail system is not running
>> >>
>> >> ps auxw| egrep master
>> >>
>> >> ... nothing.
>> >
>> >So, what has changed?
>> >
>> > Wietse
>>
>> /change/ DUNNO
>>
>> I found that pf, packet filter was activated in rc.conf.local, but no rules in place. deactivated it.
>>
>> the machine had over 1 year uptime (it's our syslog server), but I rebooted anyway.
>>
>> no change. Master refuses quietly to stay resident.
>>
>> master's last maillog words are still:
>>
>> postfix/master[2137]: setugid: uid 0 gid 0
>>
>> and then silence.
>
>Try running the master under ktrace:
>
>ktrace /some/where/master -d
>kdump
>
>My speculation is that some library (or the master executable)
>got corrupted.

=========

the end of kdump :

18781 master CALL setuid(0)
18781 master RET setuid 0
18781 master CALL gettimeofday(0xbfbfde78,0)
18781 master RET gettimeofday 0
18781 master CALL getpid
18781 master RET getpid 18781/0x495d
18781 master CALL sendto(0x3,0xbfbfdebe,0x81,0,0,0)
18781 master GIO fd 3 wrote 129 bytes
"<18>May 20 14:51:40 postfix/master[18781]: fatal: open lock file /var/db/postfix/master.lock: cannot open file: Permission denied"
18781 master RET sendto 129/0x81
18781 master CALL nanosleep(0xbfbfebc8,0xbfbfebc0)
18781 master RET nanosleep 0
18781 master CALL exit(0x1)

Just to get something going, I've chmod -R 777 /var/db/postfix, but no change.

Len

From: Wietse Venema on 20 May 2010 17:35
Len Conrad:
> setsid(0x805c71d,0x2,0x0,0xbfbfeb1c,0xbfbfeb24,0x281beda0) ERR#1 'Operation not permitted'
> getsid(0x0,0x2,0x0,0xbfbfeb1c,0xbfbfeb24,0x281beda0) = 798 (0x31e)
> getpid(0x0,0x2,0x0,0xbfbfeb1c,0xbfbfeb24,0x281beda0) = 18366 (0x47be)
> gettimeofday({1274384341.299480},0x0) = 0 (0x0)
> getpid(0x28201068,0x281c3e20,0xbfbfe8c2,0x0,0x0,0xbfbfdc7e) = 18366 (0x47be)
> sendto(3,"<18>May 20 14:39:01 postfix/mast"...,117,0x0,NULL,0x0) = 117 (0x75)

In that case, you will have an error message in the syslog file
that starts with "May 20 14:39:01 postfix/master..." and that
explains why it terminates.

Wietse

From: Wietse Venema on 20 May 2010 17:37
Len Conrad:
> the end of kdump :
>
> 18781 master CALL setuid(0)
> 18781 master RET setuid 0
> 18781 master CALL gettimeofday(0xbfbfde78,0)
> 18781 master RET gettimeofday 0
> 18781 master CALL getpid
> 18781 master RET getpid 18781/0x495d
> 18781 master CALL sendto(0x3,0xbfbfdebe,0x81,0,0,0)
> 18781 master GIO fd 3 wrote 129 bytes
> "<18>May 20 14:51:40 postfix/master[18781]: fatal: open lock file /var/db/postfix/master.lock: cannot open file: Permission denied"
> 18781 master RET sendto 129/0x81
> 18781 master CALL nanosleep(0xbfbfebc8,0xbfbfebc0)
> 18781 master RET nanosleep 0
> 18781 master CALL exit(0x1)

In that case, you have an error message in the syslog file.

> Just to get something going, I've chmod -R 777 /var/db/postfix, but no change.

Of course not. The directory can be accessible ONLY if the PARENT
directories are accessible.

Wietse

From: "Len Conrad" on 20 May 2010 17:44
---------- Original Message ----------------------------------
From: Wietse Venema <wietse(a)porcupine.org>
Date: Thu, 20 May 2010 17:35:46 -0400 (EDT)

>Len Conrad:
>> setsid(0x805c71d,0x2,0x0,0xbfbfeb1c,0xbfbfeb24,0x281beda0) ERR#1 'Operation not permitted'
>> getsid(0x0,0x2,0x0,0xbfbfeb1c,0xbfbfeb24,0x281beda0) = 798 (0x31e)
>> getpid(0x0,0x2,0x0,0xbfbfeb1c,0xbfbfeb24,0x281beda0) = 18366 (0x47be)
>> gettimeofday({1274384341.299480},0x0) = 0 (0x0)
>> getpid(0x28201068,0x281c3e20,0xbfbfe8c2,0x0,0x0,0xbfbfdc7e) = 18366 (0x47be)
>> sendto(3,"<18>May 20 14:39:01 postfix/mast"...,117,0x0,NULL,0x0) = 117 (0x75)
>
>In that case, you will have an error message in the syslog file
>that starts with "May 20 14:39:01 postfix/master..." and that
>explains why it terminates.

=========

found it:

/var/log/console.log:May 20 14:39:01 src(a)sl1.hctc.net postfix/master[18366]: fatal: unable to set session and process group ID: Operation not permitted

Len

From: Ralf Hildebrandt on 21 May 2010 07:01
* Len Conrad <lconrad(a)Go2France.com>:

> May 20 10:37:35 src(a)sl1.hctc.net postfix/master[29415]: dict_eval: const

Don't run master verbosely.
I had a similar problem once when I umounted the /var/spool/postfix on
a DRBD system. There were POstfix processes still lingering around (ps
auxwww|grep postfix) which I all killed, after that it would work again.

--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
ralf.hildebrandt(a)charite.de | http://www.charite.de


First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: [patch] build failure against db-5.0
Next: Postfix, SASL and LDAPDB [solved]