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.

Backup and the infinite tar run...

Discussion in 'General Discussion' started by JustinK, Sep 11, 2002.

  1. JustinK

    JustinK Well-Known Member

    Joined:
    Sep 4, 2001
    Messages:
    251
    Likes Received:
    0
    Trophy Points:
    16
    Around the same time as our main server upgraded to cpanel5 (and I'm not saying that did it, I just noticed this around the same time period), I noticed the main server with just the company site on it was at a constant load of 1-2 (one time it stayed at 1 and another at 2). The load is usually around nothing, so I figured &hey, probably just the backups and cpanel update.&

    I left it be for about 1 1/2 hours, came back and noticed it was still right at 1 (and the other time it stayed at 2). I login via ssh, type in top and see there's a tar process stuck running at 99% CPU. Ok, well if it's stuck, I'll kill it right? Wrong. I kill it and the darn thing pops back up as a brand new process. I then do an strace on the process on it and this scrolls infinitely down the screen until I stop it:
    --- SIGPIPE (Broken pipe) ---
    write(4, &etc/valiases/\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0&..., 10240) = -1 EPIPE (Broken pipe)

    I don't see anything wrong with the valiases directory or anything in it, but the process keeps insisting on running and scrolling that. Each time it happens the directory varies. The only way to stop it is to rename tar to something else and kill the process so it can't restart. Not the best solution, but it works for now. So now I have to ask, does anyone know what the heck is doing that and possibly how to fix it?
     
  2. JustinK

    JustinK Well-Known Member

    Joined:
    Sep 4, 2001
    Messages:
    251
    Likes Received:
    0
    Trophy Points:
    16
    Just incase anyone runs into this, it turned out to be a faulty backup drive. Just thankful it wasn't on one of the customer servers. :)
     
Loading...

Share This Page