Issues with excessive CPU usage continue...

[ilove2rock]

ok done... lets see what happens. Ive also restarted the server

[kh99]

See anything in your log file yet? There should be something there, even if it's not showing the problem yet.

[ilove2rock]

no, its still empty. I am not the best with this stuff but I did remember to change the file permissions to read and write. One thing though, the file belongs to root, not home. Is that ok?

[kh99]

Well, I'm not really an admin person, but if the file doesn't belong to the same owner or group as the user the web server runs as, then you'd have to make it writable to everyone. I know on our server (not the one for vbullein.org but the one I'm licensed under) they've got it set up so that any files in the web server's directory are set to read only. So when I want to log stuff to a file like you're doing, I create a directory under my home directory and set it to 0x777 (which is still a little dangerous, I guess, but at least it's not available through the web server).

Anyway, I know it's annoying. I had trouble getting it to work before posting it, and when you don't have any error messages it's hard to know why it's failing. If you decide to abandon this and go a different route I'd understand.

[ilove2rock]

ok, I changed to 7's. Might as well let it run for 24 hours incase its something that is set for midnight or after that is the error....

Thanks again for your help

[kh99]

I figured it was too soon to be sure what's causing the excess cpu time, but I think there are scheduled tasks that run every hour, so I think there should be something in the file after an hour or else there's a problem.

One thought I had: do you have a mod to backup the database via scheduled task? That seems like something that could potentially cause problems.

I also noticed that cron.php calls set_time_limit(0) at the beginning, so those scripts won't time out. But it seems like you could pick some reasonable upper limit and set that instead of having no limit. Of course it won't tell you what the problem is (which would be nice to know because it might be something important), but it would at least limit the cpu usage.

[ilove2rock]

Well its been about 48 hours now and that file is still empty.

I guess we either have something wrong here or I managed to turn off the cron job that was causing the error.

After I had a look through them I did disable 2 or 3. I wont know for sure for about 3 more days if the emails start coming in again.

Also you mentioned the backup script which is something that we installed in root, it is not a vBulletin function.

Thanks KH99 for your advice I will keep you posted

[kh99]

Hmm...unless you turned off all cron jobs then you should have seen things being logged, so I guess there's still some persmission problem or something. If you still want to fool around with it you could try creating a php file with code like this:

<?php
            if (($fp = fopen('cronlog.txt', 'a')) !== NULL)
            {
               fwrite($fp, date(DATE_ATOM)." PID:".getmypid()." start \n");
               fclose($fp);
            }

Then when you run that from your browser you should see any errors and you can try it until you get the file thing worked out. But it's up to you of course.

One thing I probably should have mentioned, if for some reason there's an error (lke a function used in that code does't exist for some reason) then none of your cron jobs will run, so if you don't want to mess with it any more you should remove that code.

You should be able to go to Statistics & Logs > Schedule Task Log and see if anything has run in the past few days. BTW, the reason I didn't suggest that you just use that log is because I don't think every tasks logs something, and I'm pretty sure most don't log their start and end times.

[ilove2rock]

ok thanks again, I have a house full of company for the next couple of days so I cant focus on this till after christmas.

I did check and scheduled tasks are running in the log.

Thanks again, will post back soon

Happy Holidays everyone