Ubuntu
postfix package

dpkg postinst failed, because it tries to start postfix twice (and does not catch running state)

Bug #59268 reported by Wolfgang SZ
30
This bug affects 2 people
Affects Status Importance Assigned to Milestone
postfix (Ubuntu)
Fix Released
Undecided
LaMont Jones

Bug Description

Binary package hint: update-manager

Last night I upgraded from 5.10 to 6.06, using Synaptic. During the process it was reported that the upgrade had failed for postfix, mailx and mantis and on each occasion I was asked to report a bug for this.
So here we go.
Unfortunately I will not be able to attach the upgrade logfiles, as the upgrade has also caused another serious problem: all desktop applications and all terminal windows started from Gnome now insist on directing their traffic through a (non-existant) proxy at local IP 192.168.100.2. In consequence, Firefox is not operational and I submitting this bug from my Windows desktop (running on a separate PC with no access to the Linux filesystem).
I am not a Linux fundi, so no idea how I could get these files across (if anyone can help, I will gladly submit them here).

Revision history for this message
Wolfgang SZ (wolfgangs) wrote :

I have managed to transfer the upgrade logs and they are attached here for investigation.

Revision history for this message
Wolfgang SZ (wolfgangs) wrote :

Here is the next one.

Revision history for this message
Wolfgang SZ (wolfgangs) wrote :

Finally, the last one.

Revision history for this message
Michael Vogt (mvo) wrote :

Here is what causes the error:

Running newaliases
 * Stopping Postfix Mail Transport Agent postfix [ ok ]
 * Starting Postfix Mail Transport Agent postfix
 * Starting Postfix Mail Transport Agent postfix postfix/postfix-script: fatal: the Postfix mail system is already running
                                                                         [fail]
invoke-rc.d: initscript postfix, action "restart" failed.
dpkg: error processing postfix (--configure):
 subprocess post-installation script returned error exit status 1

This is a bug in postfix, reassigning.

Cheers,
 Michael

Revision history for this message
Daniel Hahler (blueyed) wrote :

Given the log output and the duplicates I'm setting it to confirmed.

Changed in postfix:
status: New → Confirmed
Revision history for this message
Scott Kitterman (kitterman) wrote :

Just upgrading from 2.3.8 (Feisty) to 2.4.5 (proposed Feisty Backport) I saw Stopping ... twice, but it started OK.

Revision history for this message
LaMont Jones (lamont) wrote :

Fixed sometime prior to 2.4.5

Changed in postfix:
assignee: nobody → lamont
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.