The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

FreeBSD Courierup help

Discussion in 'General Discussion' started by cpeden, Jul 18, 2007.

  1. cpeden

    cpeden Member

    Joined:
    Mar 11, 2004
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    1
    anyone have any ideas how to fix this?




    max# ./courierup -force
    courier-imap Setup Script Version 1.0
    This is the courier-imap installer for OS FreeBSD
    gdbm (1.8.3_3) is already installed.
    Searching ports for courier-authlib .........................................................found courier-authlib in /usr/ports/security/courier-authlib....Done
    courier-authlib (0.59.3) is already installed.
    Searching ports for courier-imap ...........................................found courier-imap in /usr/ports/mail/courier-imap....Done
    [Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 365 packages found (-0 +1) . done]
    ---> Session started at: Wed, 18 Jul 2007 05:07:13 -0500
    ---> Upgrade of mail/courier-imap started at: Wed, 18 Jul 2007 05:07:25 -0500
    ---> Upgrading 'courier-imap-4.1.1,1' to 'courier-imap-4.1.3,1' (mail/courier-imap)
    ---> Build of mail/courier-imap started at: Wed, 18 Jul 2007 05:07:25 -0500
    ---> Building '/usr/ports/mail/courier-imap'
    ===> Cleaning for courier-imap-4.1.3,1
    ===> Vulnerability check disabled, database not found
    => courier-imap-4.1.3.tar.bz2 is not in /usr/ports/mail/courier-imap/distinfo.
    => Either /usr/ports/mail/courier-imap/distinfo is out of date, or
    => courier-imap-4.1.3.tar.bz2 is spelled incorrectly.
    *** Error code 1

    Stop in /usr/ports/mail/courier-imap.
    ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.16230.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=courier-imap-4.1.1,1 UPGRADE_PORT_VER=4.1.1,1 make FETCH_BEFORE_ARGS=-q
    ** Fix the problem and try again.
     
  2. nyjimbo

    nyjimbo Well-Known Member

    Joined:
    Jan 25, 2003
    Messages:
    1,125
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New York
    I have the same exact problem on a new Freebsd 6.1 install, so its likely something more widespread.

    :mad: Can we ever go just one week without something screwing up on these upgrades ?
     
  3. cpeden

    cpeden Member

    Joined:
    Mar 11, 2004
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    1
    BUMP BUMP


    anyone got any ideas?
     
  4. cPanelNick

    cPanelNick Administrator
    Staff Member

    Joined:
    Mar 9, 2015
    Messages:
    3,426
    Likes Received:
    2
    Trophy Points:
    38
    cPanel Access Level:
    DataCenter Provider
    Try running make clean in the port
     
  5. nyjimbo

    nyjimbo Well-Known Member

    Joined:
    Jan 25, 2003
    Messages:
    1,125
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New York
    Everything I tried failed to fix it (including doing the 'make clean') so I did a "portsnap fetch" and pulled in the whole 70+ meg ports database, which took about 20 minutes and when it was done with all its work I did a "portsnap extract" which loaded the new ports over the old.

    I went back to /usr/ports/mail/courier-imap and did a "make clean" and a "make deinstall" for the heck of it

    Went back to /scripts and did a ./courierup --force and it recompiled everything and did the
    courier stuff and its all working fine now.

    You might not need to do all that but its all I could do to get it to work.
     
    #5 nyjimbo, Jul 25, 2007
    Last edited: Jul 25, 2007
  6. cpeden

    cpeden Member

    Joined:
    Mar 11, 2004
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    1
    I did the same and it worked. I know how to update my ports but I am always hesitate because sometimes the slightest thing can break cpanel.
     
  7. idezmax

    idezmax Registered

    Joined:
    Jul 26, 2007
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
  8. nyjimbo

    nyjimbo Well-Known Member

    Joined:
    Jan 25, 2003
    Messages:
    1,125
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New York
    I went with the portsnap thing because I have been in this position before with other Freebsd installs. Once you start getting these things they tend to pile up. One of my older servers had such a broken ports install I had to rip it all out and reload from scratch and then do the portsnap. So doing it now on this install was probably the best thing to do.
     

Share This Page