Results 1 to 5 of 5
  1. #1
    Join Date
    May 2003
    Posts
    32

    RHE up2date problem.

    I've been managing my own box for a bout 1.5 years with no problems (knock on wood).

    I've got RHE and Cpanel running over on a box at The Planet. Two days ago there was a standard nightly update that ended up crashing Apache and syslogd. Both were restared automatically and I didn't think anything of it.

    So the next day I notice that I did not get my usual cpanel backup and nightly update e-mails. I went poknig around and started looking for rootkits. Didn't find any. All things are normal.

    I tried to use up2date and I get this error

    Code:
    up2date: error while loading shared libraries: libwnck-1.so.4: cannot open shared object file: No such file or directory
    I'm not sure what to do but I would like to try to figrue it out on my own before I bug tech support. Do you guys have any ideas?

    Thank you

    -A

  2. #2
    Join Date
    Mar 2005
    Location
    NY USA
    Posts
    839
    Disclaimer: I'm no Linux Guru, so take this as what it is, free advice from a non-expert

    But it looks like you are missing a package, I did a google search for the package and found (what I think is) what you need

    rpm -i ftp://ftp.freshrpms.net/pub/dag/pack...3.dag.i386.rpm
    EZZI.net - A Service of Access Integrated Technologies Inc
    Running data centers, nationwide data network, and world-wide VoIP network.
    http://www.EZZI.net sales@ezzi.net

  3. #3
    Join Date
    May 2003
    Posts
    32
    That got my up2date working. Thank you Take-IT-EZZI

  4. #4
    Join Date
    Mar 2005
    Location
    NY USA
    Posts
    839
    Originally posted by Altheon
    That got my up2date working. Thank you Take-IT-EZZI
    Glad I could help.
    EZZI.net - A Service of Access Integrated Technologies Inc
    Running data centers, nationwide data network, and world-wide VoIP network.
    http://www.EZZI.net sales@ezzi.net

  5. #5
    Join Date
    Dec 2004
    Posts
    256
    except it may very well have broken something else that was updated and had a dependency... the proper thing to do would've been to grab an updated version of up2date first :/

Posting Permissions

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