Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:0

Runaway Slashd Task

posted by Krow on 02:10 PM February 13th, 2002   Printer-friendly   Email story
Since upgrading to the latest version of slash (2.2.5?), I am seeing that the slashd task p2f_cheesy.pl floods my slashd.log with perl in free(): warning: recursive call messages. I've been running the same server setup for about 2 years, and this hasn't happened before. Any ideas what could be the cause of this problem?
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.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • I do have 512 megs of ram in the server, it is running FreeBSD 4.5. Typical top shows about 200 megs of free ram.
    --

    --
    It's either on the beat or off the beat, it's that easy.
    • Switch some of your tables over to Inno and use its pool feature to keep disk reads down.

      --

      --
      You can't grep a dead tree.
      • Do you guys suggest using Inno? It would make sense but following default installation, I think I am still using Isam tables
        • That is what I would suggest. The only thing you need to watch for is calls to select count(). They are fairl expensive. Also, you will want to play around with your pool size a bit to get maximum use of your memory. If you are running Linux look at changing the fsync() call that is used for writes (the Inno manual talks about this).
          --

          --
          You can't grep a dead tree.
      • How do you switch SOME of the tables? Gotta link to it?
        --

        --
        It's either on the beat or off the beat, it's that easy.
        • I just pick table that can take advantage of it and do a:
          ALTER TABLE table_name TYPE=innodb

          For slashdot the only tables which are not inno are comments, formkeys, and the accesslog.
          --

          --
          You can't grep a dead tree.
          • then I get this message from mysql Error 1024: the used table type doesn't support FULLTEXT indexes

            Ideas?

            --

            --
            It's either on the beat or off the beat, it's that easy.
            • I keep two databases for slashdot for this reason. I figure if you are large enough that you need to use Inno then you would move to multiple databases.

              Replicate to another set of table on the same DB and search from those?
              --

              --
              You can't grep a dead tree.
  • Sorry for the "me too" post but for those FreeBSD users out there - you might want to know the problem doesn't appear to be unique to Eric. I'm seeing it here on a vanilla FreeBSD 4.5 box with the latest slashcode, apache & mod_perl. Not being a perl programmer, any clues from the slashcode folks on how we might possibly begin to debug this problem would be extremely helpful. This one is unfortunately a show stopper.
    • I switch on Inno in MySQL and haven't seen the problem since tuesday......you might try enabling Inno. It's painless.
      --

      --
      It's either on the beat or off the beat, it's that easy.