The issue might be indeed that postfix is not running.
It appears that starting the policyd daemon "just" fails in your case.

The code for this is just:
  start)
        echo -n "Starting $DESC: "
        start-stop-daemon --start --quiet --background --pidfile $PIDFILE 
--exec $DAEMON -- -c $DAEMON_CONFIG
        echo "$NAME."
        ;;

Try running the daemon from the command line, maybe there's more info.

** Description changed:

  Binary package hint: postfix-policyd
  
  startup error: postfix-policyd
  current system info:
  d...@dt-mbpro:~$ lsb_release -rd
  Description:  Ubuntu 9.04
  Release:      9.04
  
- d...@dt-mbpro:~$ uname -a 
+ d...@dt-mbpro:~$ uname -a
  Linux dt-MBPro 2.6.28-13-server #44-Ubuntu SMP Tue Jun 2 08:47:41 UTC 2009 
i686 GNU/Linux
  
  Believe it is similar to Bug 92386 but did not take screenshot
  (yesterday when bug occurred and then had to wait for
  registration)--have since removed postfix-policyd and upgraded to 9.04
  (from 8.04 but not without issues)...
  
  I am setting up a LAMP server to run/test various packages including
  KOHA & Moodle and wanted email server available, so am not sure what app
  caused startup conflict for postfix-policyd... looked at log files but
  have not determined which if any apply.
  
  I did not expect any issues since postfix is not configured - if
  postfix-policyd wants postfix enabled it should install in off state,
  ask for configuration  or should not install.
  
  Kind Regards,
  Don
  
  ProblemType: Package
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ErrorMessage: subprocess post-installation script returned error exit status 1
  Package: postfix-policyd 1.82-2
  SourcePackage: postfix-policyd
  Title: package postfix-policyd 1.82-2 failed to install/upgrade: subprocess 
post-installation script returned error exit status 1
  Uname: Linux 2.6.28-13-server i686
+ 
+ 
+ ERROR:
+ Setting up postfix-policyd (1.82-2) ...
+ dbconfig-common: writing config to /etc/dbconfig-common/postfix-policyd.conf
+ *** WARNING: ucf was run from a maintainer script that uses debconf, but
+              the script did not pass --debconf-ok to ucf. The maintainer
+              script should be fixed to not stop debconf before calling ucf,
+              and pass it this parameter. For now, ucf will revert to using
+              old-style, non-debconf prompting. Ugh!
+ 
+              Please inform the package maintainer about this problem.
+ dbconfig-common: flushing administrative password
+ Starting Postfix greylisting policy daemon: invoke-rc.d: initscript 
postfix-policyd, action "start" failed.
+ dpkg: error processing postfix-policyd (--configure):
+  subprocess post-installation script returned error exit status 1

** Changed in: postfix-policyd (Ubuntu)
       Status: New => Triaged

** Changed in: postfix-policyd (Ubuntu)
   Importance: Undecided => Medium

** Changed in: postfix-policyd (Ubuntu)
       Status: Triaged => Incomplete

-- 
errors on startup
https://bugs.launchpad.net/bugs/390293
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

-- 
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs

Reply via email to