Usergroup: Customer
Joined: Apr 03, 2007
Total Topics: 22
Total Posts: 86
1 of 1 people found this post helpful Posted 02/05/08 - 09:14 PM:
#16
Actually, you've been helping my partner with that problem. She's been working on a different site than I am which is on a completely different server & different host. Although, I just checked and I'm running mysql 5 and php 4.3.11 and I haven't had nearly any of the problems she's had and vice versa.
Now, here's a thought. Just a thought so if it sounds like it's coming from left field it actually is. If it's the cron table that's causing these problems and since I didn't create any new crons and you said there are only 3 to begin with is there any way for me to completely remove them and then basically recreate the table?
Yes, I know I'm grabbing at straws here, but at least I tried.
Usergroup: Administrator
Joined: Dec 21, 2001
Location: Northern California
Total Topics: 49
Total Posts: 5510
Posted 02/06/08 - 10:23 AM:
#17
That's an odd combination, MySQL 5 was released long after PHP 4.3 so its support for it may have issues. I don't think the mysqli extension existed back then, which is intended for use with MySQL 4.1+.
Usergroup: Customer
Joined: Apr 03, 2007
Total Topics: 22
Total Posts: 86
Posted 02/10/08 - 09:59 AM:
#18
That fixed it! I removed all the crons and haven't had a single error.
I even put all the categories back on one page to try seeing if it would make the error reappear and it's been error free ever since. Hopefully, removing the crons won't eventually give me residual problems, but I guess I'll deal with those if they ever happen.
Usergroup: Customer
Joined: Apr 03, 2007
Total Topics: 22
Total Posts: 86
Posted 02/11/08 - 06:49 PM:
#20
None right now that I know of. Since I'm not sure what exactly those crons controlled I won't know until I notice something not working as it should or someone complains. As of now the site works and loads like a dream.
Usergroup: Administrator
Joined: Dec 21, 2001
Location: Northern California
Total Topics: 49
Total Posts: 5510
Posted 02/13/08 - 11:14 AM:
#21
You may never notice, but your users will, and they'll just go away without complaining. All expirations, sponsorships, daily digests, static page exports, email log trimming, autopromotions, birthday emails, cache size management, letter rotation sorting, temporary hits, and automated backups are 100% dead.
Even the resetting of failed login attempts is dead, so the first person to mistype a login enough times will be effectively banned forever and you'll have long forgotten why. Old attachments that somebody decided not to upload a year ago will continue showing on the 'suggest' page. Suspended users will never get unspuspended.
Usergroup: Customer
Joined: Apr 03, 2007
Total Topics: 22
Total Posts: 86
Posted 02/14/08 - 07:48 AM:
#22
Hey, sometime you just have to live life on the edge!
Plus it's not really a revenue generating site, basically a hobby site for my husband and a place for us to have access his music collection. Obviously, I don't want to annoy any users whether they're our friends or people stumbling across the site, but my options are limited.
Anyway, thanks for that list of items that the crons affect at least I now know what to look for. I've actually started re-adding them one at a time to see if it's just one causing the error or just the combination of having all three.
Usergroup: Customer
Joined: Apr 03, 2007
Total Topics: 22
Total Posts: 86
Posted 03/06/08 - 07:27 PM:
#23
Well, after running a bunch of different scenarios I figured out that there are slightly more cron jobs than the site can take. It loads fine with 2 crons, but as soon as I add the third (whichever one that happens to be) it starts giving me errors. So I ended up trying to combine 2 of the crons into 1 file just as a test, but that gave me errors as well.
Finally, I looked through the php files, and commented out any jobs that I am not using. For example, the job that checks for expired links. None of my links will ever expire so I commented that one out as well as a couple others like member birthdays as another example. So far it looks like that did the trick. I'm keeping my fingers crossed.
Anyway, I just thought I'd update the thread with my findings. Thanks again for all your help.
Usergroup: Customer
Joined: Apr 03, 2007
Total Topics: 22
Total Posts: 86
Posted 03/09/08 - 09:27 AM:
#24
Sigh, so much for thinking this was a done deal. Just when I thought I found my problem and had a decent solution I've apparently made it worse, so it's back to the drawing board.
Just wanted to post so that anyone reading this wouldn't think my solution fixed it. If I find anything else I will update this again.
Usergroup: Administrator
Joined: Dec 21, 2001
Location: Northern California
Total Topics: 49
Total Posts: 5510
Posted 03/09/08 - 04:56 PM:
#25
That doesn't really make much sense -- they're supposed to run at different times, so when one runs it doesn't even know there are others as they aren't used for another 1/12/24 hours. Did you schedule them all for the same time?
Usergroup: Customer
Joined: Apr 03, 2007
Total Topics: 22
Total Posts: 86
Posted 03/09/08 - 08:08 PM:
#26
Nope schedule them as they're named, 1/12/24. Actually, I even tried starting them at odd intervals just to make sure they don't run at the same time. I agree 100% with you it doesn't make sense.
Currently, I have taken the only jobs from 12hour.php that I need (since it is the smallest one) and added them to daily.php and have completely removed the 12hour file. Logically, I know it shouldn't make a difference, but I'm keeping my fingers crossed anyway.
Usergroup: Customer
Joined: Apr 03, 2007
Total Topics: 22
Total Posts: 86
Posted 03/22/08 - 01:40 PM:
#27
Well, the site has been loading error free since my last post so I am finally considering this matter closed.
Thanks for all you help and suggestions. I still can't really pinpoint a logical reason for the errors or lack of them now, but as long as everything works I'm happy.
Print
my sql error when page loads
