Results 1 to 8 of 8

Thread: apt-get | dpkg erro

  1. #1
    Join Date
    Sep 2009
    Posts
    7

    Default apt-get | dpkg erro

    problem:

    dpkg: error processing postfix (--configure):
    subprocess post-installation script returned error exit status 75
    dpkg: dependency problems prevent configuration of bsd-mailx:
    bsd-mailx depends on exim4 | mail-transport-agent; however:
    Package exim4 is not installed.
    Package mail-transport-agent is not installed.
    Package postfix which provides mail-transport-agent is not configured yet.
    dpkg: error processing bsd-mailx (--configure):
    dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of courier-pop:
    courier-pop depends on exim4 | mail-transport-agent; however:
    Package exim4 is not installed.
    Package mail-transport-agent is not installed.
    Package postfix which provides mail-transport-agent is not configured yet.
    dpkg: error processing courier-pop (--configure):
    dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of courier-pop-ssl:
    courier-pop-ssl depends on courier-pop; however:
    Package courier-pop is not configured yet.
    dpkg: error processing courier-pop-ssl (--configure):
    dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of courier-imap:
    courier-imap depends on exim4 | mail-transport-agent; however:
    Package exim4 is not installed.
    Package mail-transport-agent is not installed.
    Package postfix which provides mail-transport-agent is not configured yet.
    dpkg: error processing courier-imap (--configure):
    dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of courier-imap-ssl:
    courier-imap-ssl depends on courier-imap (>= 1.3.7-3); however:
    Package courier-imap is not configured yet.
    dpkg: error processing courier-imap-ssl (--configure):
    dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of mailx:
    mailx depends on bsd-mailx; however:
    Package bsd-mailx is not configured yet.
    dpkg: error processing mailx (--configure):
    dependency problems - leaving unconfigured
    dpkg: dependency problems prevent configuration of postfix-mysql:
    postfix-mysql depends on postfix (= 2.5.5-1.1); however:
    Package postfix is not configured yet.
    dpkg: error processing postfix-mysql (--configure):
    dependency problems - leaving unconfigured
    Errors were encountered while processing:
    postfix
    bsd-mailx
    courier-pop
    courier-pop-ssl
    courier-imap
    courier-imap-ssl
    mailx
    postfix-mysql



    anyone know help?

  2. #2
    Join Date
    Dec 2007
    Posts
    1,141

    Default

    From the error messages it appears as though there is an issue with the postfix installation which is breaking package installations dependent upon postfix:

    Code:
    Package postfix which provides mail-transport-agent is not configured yet.
    (Note: You may want to include the command you were running when the errors occurred in the future)


    Could you provide your hostname for investigation?

  3. #3
    Join Date
    Jul 2007
    Location
    127.0.0.1
    Posts
    392

    Default

    Debian (for reasons unknown to me) seems dependant upon an MTA. Try reinstalling (& reconfiguring) an MTA.

    dpkg-reconfigure postfix

    maybe?

    aptitude reinstall postfix

    ?

  4. #4
    Join Date
    Sep 2009
    Posts
    7

    Default

    this error postfix installation is present in all debian available in both etch and lenny in

    Quote Originally Posted by DanL@VPSLink View Post
    From the error messages it appears as though there is an issue with the postfix installation which is breaking package installations dependent upon postfix:

    Code:
    Package postfix which provides mail-transport-agent is not configured yet.
    (Note: You may want to include the command you were running when the errors occurred in the future)


    Could you provide your hostname for investigation?
    please! servidor.vps / 66.249.7.160

    Quote Originally Posted by GuyPatterson View Post
    Debian (for reasons unknown to me) seems dependant upon an MTA. Try reinstalling (& reconfiguring) an MTA.

    dpkg-reconfigure postfix

    maybe?

    aptitude reinstall postfix

    ?
    :~# dpkg-reconfigure postfix
    /usr/sbin/dpkg-reconfigure: postfix is broken or not fully installed

    :~# aptitude reinstall postfix
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Initializing package states... Done
    Reading task descriptions... Error!
    E: Could not open file /var/lib/aptitude/pkgstates.new - open (2 No such file or directory)
    E: Cannot open Aptitude state file


    not resolved
    Last edited by carlos; 10-07-2009 at 05:40 PM.

  5. #5
    Join Date
    Jul 2007
    Location
    127.0.0.1
    Posts
    392

    Default

    Quote Originally Posted by carlos View Post
    :~# aptitude reinstall postfix
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Initializing package states... Done
    Reading task descriptions... Error!
    E: Could not open file /var/lib/aptitude/pkgstates.new - open (2 No such file or directory)
    E: Cannot open Aptitude state file


    not resolved
    Please paste the contents of your /etc/apt/sources.list file in a reply and try running: aptitude update then aptitude upgrade and finally, aptitude reinstall postfix

  6. #6
    Join Date
    Sep 2009
    Posts
    7

    Default apt-get | dpkg erro

    sources.list

    deb htp://debrepo.mirror.vpslink.com/debian]Index of /debian lenny main contrib
    deb htp://security.debian.org/]Debian -- Security Information lenny/updates main contrib

    apt-get install postfix

    Adding system user `postfix' (UID 102) ...
    Adding new user `postfix' (UID 102) with group `postfix' ...
    Not creating home directory `/var/spool/postfix'.
    Creating /etc/postfix/dynamicmaps.cf
    Adding tcp map entry to /etc/postfix/dynamicmaps.cf
    Adding group `postdrop' (GID 107) ...
    Done.
    setting myhostname: 69522
    setting alias maps
    setting alias database
    mailname is not a fully qualified domain name. Not changing /etc/mailname.
    setting destinations: ovz-test, 69522, localhost.localdomain, localhost
    setting relayhost:
    setting mynetworks: 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
    setting mailbox_size_limit: 0
    setting recipient_delimiter: +
    setting inet_interfaces: all
    WARNING: /etc/aliases exists, but does not have a root alias.

    Postfix is now set up with a default configuration. If you need to make
    changes, edit
    /etc/postfix/main.cf (and others) as needed. To view Postfix configuration
    values, see postconf(1).

    After modifying main.cf, be sure to run '/etc/init.d/postfix reload'.

    Running newaliases
    newaliases: warning: valid_hostname: numeric hostname: 69522
    newaliases: fatal: file /etc/postfix/main.cf: parameter myhostname: bad parameter value: 69522
    dpkg: error processing postfix (--configure):
    subprocess post-installation script returned error exit status 75
    Errors were encountered while processing:
    postfix
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    :/# aptitude update
    E: Could not open file /var/lib/aptitude/pkgstates.new - open (2 No such file or directory)
    E: Cannot open Aptitude state file
    E: Could not open file /var/lib/aptitude/pkgstates.new - open (2 No such file or directory)
    E: Cannot open Aptitude state file

    :/# aptitude upgrade
    W: The "upgrade" command is deprecated; use "safe-upgrade" instead.
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Initializing package states... Done
    Reading task descriptions... Error!
    E: Could not open file /var/lib/aptitude/pkgstates.new - open (2 No such file or directory)
    E: Cannot open Aptitude state file

  7. #7
    Join Date
    Jul 2007
    Location
    127.0.0.1
    Posts
    392

    Default

    Please use the following for the contents of your sources.list and try again (aptitude update, aptitude safe-upgrade, aptitude reinstall postfix).

    Code:
    deb http://ftp.us.debian.org/debian/ lenny main
    deb-src http://ftp.us.debian.org/debian/ lenny main
    
    deb http://security.debian.org/ lenny/updates main
    deb-src http://security.debian.org/ lenny/updates main
    
    deb http://volatile.debian.org/debian-volatile lenny/volatile main
    deb-src http://volatile.debian.org/debian-volatile lenny/volatile main
    Also, based on the dpkg errors, it appears postfix had issues properly identifying a domain/hostname (FQDN). I would suggest making sure your hostname, IPs, DNS, PTR, etc are all in order. Even easier, avoid postfix all together and use GoogApps :]

  8. #8
    Join Date
    Sep 2009
    Posts
    7

    Default

    Quote Originally Posted by GuyPatterson View Post
    Also, based on the dpkg errors, it appears postfix had issues properly identifying a domain/hostname (FQDN). I would suggest making sure your hostname, IPs, DNS, PTR, etc are all in order. Even easier, avoid postfix all together and use GoogApps :]

    Yes, the problem was the hostname ...
    had to set the right way in the main.cf of postfix, problem solved! thanks all

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •