Messaging Gateway

 View Only
  • 1.  Cron

    Posted Feb 25, 2010 03:22 AM

    Where are getting this error every hour :


    /etc/cron.hourly/logrotate:

    error: Ignoring named.rpmnew, because of .rpmnew ending

    We had  problems after  the update from version 7.7 to 8.0.3-11 on this machine (Loopback was not active, DNS not working , a second machine wich was excatly the same is upgraded  without any problem)

    Anyone familiar with this problem?



  • 2.  RE: Cron

    Posted Feb 25, 2010 03:46 AM

    Please go through the notes regarding upgrade in the following link. It also has a list of errors that can be ignored.

    Software update notes for Symantec Brightmail Gateway 8.0.2


    http://service1.symantec.com/support/ent-gate.nsf/854fa02b4f5013678825731a007d06af/5bf9769d7b3f56a9882575b60080754f?OpenDocument



  • 3.  RE: Cron

    Posted Feb 25, 2010 07:34 AM
    We are using an appliance (8360), none of the issue from the Software update notes for Symantec Brightmail Gateway 8.0.2 seem to be applicable in our situation

    Regrads

    Paul


  • 4.  RE: Cron

    Posted Feb 25, 2010 10:30 AM
    Hi Paul,

    Yes, I am faimiiar with this issue.  The alerts are due to duplicate cron jobs present in the cron directory after FAILED upgrade attempt.  I think you may have error similar to the following in update.log:

    E: Sub-process /bin/rpm returned an error code (27)

    Since you have encountered upgrade failure, the best course of action is to perform an OSRESTORE.

    Regards,

    Adnan



  • 5.  RE: Cron

    Posted Feb 26, 2010 11:38 AM
    Hi Adnan,


    an OS restore is performed by a CD wich we don't have (anymore), also we lose all settings then I Think.
    Is there no other way to solve this problem, the appliance is running fine now except the message we receive ervey hour

    Regards
    Paul


  • 6.  RE: Cron

    Posted Feb 26, 2010 12:19 PM
    Hi Paul,

    The cron alerts that you are getting every hour are just one symptom of the upgrade failure that is visible.  There may be other issues with the system that are not visible or obvious that may prevent further upgrads or cause other problems later on. 

    If you call support, they may be able to assist you in removing the duplicate cron job, but most likely they will also advise you against using the appliance in the current state after a failed upgrade.

    As for the OSRESTORE CD, you can download the ISO image from Symantec FileConnect website and burn a CD.  Yes, you will have to create the settings from scratch after an OSRESTORE unless you had a good backup and restore data from the backup, but if you take a backup now, I won't consider it clean and reliable due to the current state of the appliance.

    Regards,

    Adnan