-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have a strange (new) problem with 9.3, to which I updated recently from 9.1: Service "postfix" does not start at boot up. The boot init script and the corresponding links are in place: nimrodel:~ # l /etc/init.d/postfix -rwxr-xr-x 1 root root 5224 Mar 19 22:15 /etc/init.d/postfix* nimrodel:~ # l /etc/init.d/*/*postfix lrwxrwxrwx 1 root root 10 Apr 24 13:52 /etc/init.d/rc3.d/K07postfix -> ../postfix* lrwxrwxrwx 1 root root 10 Apr 24 13:52 /etc/init.d/rc3.d/S15postfix -> ../postfix* lrwxrwxrwx 1 root root 10 Apr 24 13:52 /etc/init.d/rc5.d/K07postfix -> ../postfix* lrwxrwxrwx 1 root root 10 Apr 24 13:51 /etc/init.d/rc5.d/S15postfix -> ../postfix* However, I don't see any mention of "postfix" in the boot screen. If I search in /var/log/boot.msg the word "postfix" is nowhere to be found, nor in /var/log/mail.* If I run "rcpostfix status" first thing I get "dead". Strange. :-? If I start it manually, I get "done", and after stopping it manually, I get "unused" if I ask for the status. But after boot it says "dead". When did it die? Why? Not when I booted, surely... There is no mention in the log of postfix dying or closing the previous day (only amavis and spamd): therefore, I'd think that during halt the kill script doesn't run either. There are more things. I can not insert/remove the service. "chkconfig postfix off" can not remove the service, if I ask "chkconfig postfix" it reports "on". If I delete the symlinks, it reports "off", but "chkconfig postfix on" does not enable it. With Yast, the same thing: I can not remove/insert the service. It doesn't complain, but it doesn't change a thing. Calling "inserv" directly doesn't help, it fails (with the symlinks removed manually): nimrodel:~ # chkconfig postfix on insserv: script postfix: service sendmail already provided! insserv: exiting now! /sbin/insserv failed, exit code 1 Forcing it (chkconfig -f) does nothing. :-/ insserv: script postfix: service sendmail already provided! insserv: exiting now! nimrodel:/etc/init.d # insserv -f -d postfix insserv: script postfix: service sendmail already provided! insserv: script postfix: service postfix already provided! nimrodel:/etc/init.d # chkconfig postfix postfix off nimrodel:/etc/init.d # chkconfig sendmail sendmail: unknown service To insert the service, I had to manually create the symlinks. This something I had not done in SuSE ever. What is happening? :-/ - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD4DBQFCbKdGtTMYHG2NR9URAtjcAJ9kkpv7uvLD4WsjISRS/paTmhfylwCY0G7a vfNUXev9WK0/L1+WexQvSw== =Fkso -----END PGP SIGNATURE-----
On Mon, Apr 25, 2005 at 10:15:51AM +0200, Carlos E. R. Wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I have a strange (new) problem with 9.3, to which I updated recently from 9.1: Service "postfix" does not start at boot up.
The boot init script and the corresponding links are in place:
nimrodel:~ # l /etc/init.d/postfix -rwxr-xr-x 1 root root 5224 Mar 19 22:15 /etc/init.d/postfix*
nimrodel:~ # l /etc/init.d/*/*postfix lrwxrwxrwx 1 root root 10 Apr 24 13:52 /etc/init.d/rc3.d/K07postfix -> ../postfix* lrwxrwxrwx 1 root root 10 Apr 24 13:52 /etc/init.d/rc3.d/S15postfix -> ../postfix* lrwxrwxrwx 1 root root 10 Apr 24 13:52 /etc/init.d/rc5.d/K07postfix -> ../postfix* lrwxrwxrwx 1 root root 10 Apr 24 13:51 /etc/init.d/rc5.d/S15postfix -> ../postfix*
However, I don't see any mention of "postfix" in the boot screen. If I search in /var/log/boot.msg the word "postfix" is nowhere to be found, nor in /var/log/mail.*
If I run "rcpostfix status" first thing I get "dead". Strange. :-?
If I start it manually, I get "done", and after stopping it manually, I get "unused" if I ask for the status. But after boot it says "dead". When did it die? Why? Not when I booted, surely...
There is no mention in the log of postfix dying or closing the previous day (only amavis and spamd): therefore, I'd think that during halt the kill script doesn't run either.
There are more things.
I can not insert/remove the service. "chkconfig postfix off" can not remove the service, if I ask "chkconfig postfix" it reports "on". If I delete the symlinks, it reports "off", but "chkconfig postfix on" does not enable it.
With Yast, the same thing: I can not remove/insert the service. It doesn't complain, but it doesn't change a thing. Calling "inserv" directly doesn't help, it fails (with the symlinks removed manually):
nimrodel:~ # chkconfig postfix on insserv: script postfix: service sendmail already provided! insserv: exiting now! /sbin/insserv failed, exit code 1
Forcing it (chkconfig -f) does nothing. :-/
insserv: script postfix: service sendmail already provided! insserv: exiting now! nimrodel:/etc/init.d # insserv -f -d postfix insserv: script postfix: service sendmail already provided! insserv: script postfix: service postfix already provided! nimrodel:/etc/init.d # chkconfig postfix postfix off nimrodel:/etc/init.d # chkconfig sendmail sendmail: unknown service
To insert the service, I had to manually create the symlinks. This something I had not done in SuSE ever.
What is happening? :-/
- -- Cheers, Carlos Robinson
Carlos, After my upgrade from 9.2--->9.3, I had a similar problem, dependent on your configuration (mine being Postfix+Cyrus+Amavis-New+Spamd), you should check your mailbox_transport. Basically I had to go through my configurations and check all my settings. Look at your mail log and see what is killing postfix. I had a slew of problems, the main issue was mail_transport connecting to public/lmtp, which I had to change to cyrus' lmtp, which in 9.2 couldn't get to work. Also check that your main.cf and master.cf files are intact. Look at how amavis is connecting also, had an issue with it too. I got the same error with postfix, thinking it was running, only to get a "dead" message when checking status. Wish I could help you more. Watch how everything is starting and you'll find something in the configuration probably changed. Good luck :)
The Monday 2005-04-25 at 08:03 -0700, Robert Sweet wrote:
After my upgrade from 9.2--->9.3, I had a similar problem, dependent on your configuration (mine being Postfix+Cyrus+Amavis-New+Spamd), you should check your mailbox_transport. Basically I had to go through my
No, you got it wrong. Postfix is not the problem, the problem is that the postfix init script is not called. The fault is in /etc/init.d/rc. My guess is that SuSE is trying a new method and it is faulty. I have disabled in /etc/sysconfig/boot this variable: USE_MAKE=no which was "YES". Also, the files /etc/init.d/.depend.start, and .depend.stop are wrong. The contain lines like this: apache2: nfs network named xntpd postgresql postfix.rpmorig.borraralgundia mysql where the line corresponding to postfix is mistaken.
configurations and check all my settings. Look at your mail log and see what is killing postfix.
Read again my post: I said:
However, I don't see any mention of "postfix" in the boot screen. If I search in /var/log/boot.msg the word "postfix" is nowhere to be found, nor in /var/log/mail.*
There is no mention of "postfix" in the mail log. Postfix is not started, not even called. It doesn't get a chance. -- Cheers, Carlos Robinson
The Monday 2005-04-25 at 10:15 +0200, I wrote:
I have a strange (new) problem with 9.3, to which I updated recently from 9.1: Service "postfix" does not start at boot up. ...
However, I don't see any mention of "postfix" in the boot screen. If I search in /var/log/boot.msg the word "postfix" is nowhere to be found, nor in /var/log/mail.* ... I can not insert/remove the service. "chkconfig postfix off" can not remove the service, if I ask "chkconfig postfix" it reports "on". If I delete the symlinks, it reports "off", but "chkconfig postfix on" does not enable it.
SuSE has designed a new feature, and it is missbeheaving. In "/etc/sysconfig/boot" I found this: ## Type: yesno ## Default: yes # # Run all scripts or rather start/stop all services # by using the make command and if RUN_PARALLEL is # set to "yes" just use a make like boot behaviour # USE_MAKE=yes And in "/etc/init.d" I see this: # Check if we are able to use make like booting # test -s /etc/init.d/.depend.start || USE_MAKE="no" test -s /etc/init.d/.depend.stop || USE_MAKE="no" test "$DO_CONFIRM" = "yes" && USE_MAKE="no" test "$RUN_PARALLEL" = "yes" || USE_MAKE="no" startpar -v &> /dev/null || USE_MAKE="no" I don't understand any of this new "feature", but it is supicious. Thus, I check the file "/etc/init.d/.depend.start", and I see this: postfix.rpmorig.borraralgundia: network named syslog xntpd ldap ypbind The entry is refering to the wrong script file, a backup copy I made time ago during some tests. The moment I deleted that (postfix.rpmorig.borraralgundia) file things started to work right away. I have also set "USE_MAKE" to no. It is not documented, I don't understand it, and it caused all those problems. :-( -- Cheers, Carlos Robinson
Op dinsdag 26 april 2005 01:32, schreef Carlos E. R.:
The Monday 2005-04-25 at 10:15 +0200, I wrote:
I have a strange (new) problem with 9.3, to which I updated recently from 9.1: Service "postfix" does not start at boot up.
...
However, I don't see any mention of "postfix" in the boot screen. If I search in /var/log/boot.msg the word "postfix" is nowhere to be found, nor in /var/log/mail.*
...
I can not insert/remove the service. "chkconfig postfix off" can not remove the service, if I ask "chkconfig postfix" it reports "on". If I delete the symlinks, it reports "off", but "chkconfig postfix on" does not enable it.
SuSE has designed a new feature, and it is missbeheaving.
In "/etc/sysconfig/boot" I found this:
## Type: yesno ## Default: yes # # Run all scripts or rather start/stop all services # by using the make command and if RUN_PARALLEL is # set to "yes" just use a make like boot behaviour # USE_MAKE=yes
And in "/etc/init.d" I see this:
# Check if we are able to use make like booting # test -s /etc/init.d/.depend.start || USE_MAKE="no" test -s /etc/init.d/.depend.stop || USE_MAKE="no" test "$DO_CONFIRM" = "yes" && USE_MAKE="no" test "$RUN_PARALLEL" = "yes" || USE_MAKE="no" startpar -v &> /dev/null || USE_MAKE="no"
I don't understand any of this new "feature", but it is supicious. Thus, I
Faster startup time.
check the file "/etc/init.d/.depend.start", and I see this:
postfix.rpmorig.borraralgundia: network named syslog xntpd ldap ypbind
The entry is refering to the wrong script file, a backup copy I made time ago during some tests. The moment I deleted that (postfix.rpmorig.borraralgundia) file things started to work right away.
I have also set "USE_MAKE" to no. It is not documented, I don't understand it, and it caused all those problems.
:-(
-- Cheers, Carlos Robinson
Is it reported to suse? Would be nice to see this in a wiki, e.g. at: http://www.susewiki.org/ -- Richard Bos Without a home the journey is endless
The Tuesday 2005-04-26 at 09:22 +0200, Richard Bos wrote:
I don't understand any of this new "feature", but it is supicious. Thus, I
Faster startup time.
Probably. Smaller code.
check the file "/etc/init.d/.depend.start", and I see this:
postfix.rpmorig.borraralgundia: network named syslog xntpd ldap ypbind
Is it reported to suse?
I intend to, when I get the time. I don't browse much, my network connection is not permanent and charges by the minute.
Would be nice to see this in a wiki, e.g. at: http://www.susewiki.org/
Mmmm. I never used wiki; in fact, I don't know what it is
participants (3)
-
Carlos E. R. -
Richard Bos -
Robert Sweet