Stories
Slash Boxes
Comments

Slash Open Source Project

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Handling logging issues 6 Comments More | Login /

 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • On a slightly different note, I've been checking my logs lately and in the past several weeks I've had to keep restarting slashd as it has been hanging during freshenup.pl (usually the last line in slashd.log is something like "Updating 03/04/22/1551213". Anyone else have this happen? It happens at least once a day now, I have had to schedule a cron job to restart slashd every hour. Slash 2.2.6

    I've been running the same code for about a year, the only thing I did recently was upgrade the kernel (RedHat):
    2.
    • What version of slash? We're not seeing that, but we're using the most recient T tag (I think it's the most recient anyway - T2_3_0_85).
      --


      "How about you interface with my ass? By biting it!" --Bender
      • slash 2.2.6 ... I haven't touched the code in about a year so that's why it's a bit mysterious. It's probably a sign I should start the move to the T tags.
        • I honnestly wouldn't reccomend it. We had no real choice, but if I had to do it all over again, I'd have waited for the upgrade stuff to be done. Seriously. It took us 6 days to migrate 15 sites, and much longer to iron out all the major bugs that resulted from the process - we're still killing minor ones.
          --


          "How about you interface with my ass? By biting it!" --Bender

          • Re:Yikes (Score:2)

            by davidt (71) on Wednesday April 23 2003, @11:41PM (#5970) Homepage
            Thanks for the tip, I'll definitely hold off, since it's not urgent. 2.2.6 has been extremely stable for the most part.

            I heard about this upgrade script a few weeks ago I think. I'll be looking for it!
            • I for one can't wait. :-) After what we went thru last time, I'll never do that again. The only reason we did it this time was because a new customer needed features only available in current CVS, so we upgraded. Going from CVS to the latest T tag wasn't so bad - it look less than an hour, and basically no one noticed. We still have some run away perl problems, Jamie was going to take a look at them, don't know if he ever did.
              --


              "How about you interface with my ass? By biting it!" --Bender