Community Forums
Connect with us on LinkedIn
+ Reply to Thread
Results 1 to 8 of 8
  1. #1
    Member
    Join Date
    Mar 2004
    Posts
    14

    Default FreeBSD Courierup help

    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. #2
    Member nyjimbo's Avatar
    Join Date
    Jan 2003
    Location
    New York
    Posts
    1,105

    Default

    I have the same exact problem on a new Freebsd 6.1 install, so its likely something more widespread.

    Can we ever go just one week without something screwing up on these upgrades ?
    "A dog has raised it’s hind leg on the age of nevermore !"
    -- Rolf

  3. #3
    Member
    Join Date
    Mar 2004
    Posts
    14

    Default

    BUMP BUMP


    anyone got any ideas?

  4. #4
    cPanel Staff cpanelnick's Avatar
    Join Date
    Feb 2003
    Location
    Houston, TX
    Posts
    4,597

    Default

    Try running make clean in the port

  5. #5
    Member nyjimbo's Avatar
    Join Date
    Jan 2003
    Location
    New York
    Posts
    1,105

    Default

    Quote Originally Posted by cpeden View Post
    BUMP BUMP


    anyone got any ideas?
    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.
    Last edited by nyjimbo; 07-25-2007 at 11:17 AM.
    "A dog has raised it’s hind leg on the age of nevermore !"
    -- Rolf

  6. #6
    Member
    Join Date
    Mar 2004
    Posts
    14

    Default

    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. #7
    Registered User
    Join Date
    Jul 2007
    Posts
    1

    Default

    thanks.

    ------------------------------------------
    http://www.idezmax.com

    http://www.creditwidgets.info

  8. #8
    Member nyjimbo's Avatar
    Join Date
    Jan 2003
    Location
    New York
    Posts
    1,105

    Default

    Quote Originally Posted by cpeden View Post
    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.
    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.
    "A dog has raised it’s hind leg on the age of nevermore !"
    -- Rolf

Similar Threads & Tags
Similar threads

  1. i want this Os ( FreeBSD 8.1 )
    By Your Host in forum cPanel and WHM Discussions
    Replies: 3
    Last Post: 10-04-2010, 10:17 AM
  2. /scripts/courierup --force not doing anything
    By Guile in forum cPanel and WHM Discussions
    Replies: 3
    Last Post: 08-30-2006, 02:23 AM
  3. Freebsd
    By George5 in forum cPanel and WHM Discussions
    Replies: 5
    Last Post: 06-22-2005, 08:29 AM
  4. Freebsd and trojans, does CP for freebsd has the trojans scaner?
    By Jedia in forum cPanel and WHM Discussions
    Replies: 1
    Last Post: 05-11-2004, 08:49 AM
  5. SuSE and FreeBSD support [was: FreeBSD or Debian Support?]
    By bdraco in forum cPanel and WHM Discussions
    Replies: 29
    Last Post: 12-06-2001, 12:39 PM
Linkedin       Facebook       Twitter       RSS       Flickr       YouTube