Hi.
I installed Serendipity 1.0.1 and it seemed to work properly. However it has having problems loading pages.
- Sometimes it fails and shows "DATABASE_ERROR".
- Sometimes is loads page without CSS.
- And sometimes is loads the whole page perfectly.
Anyone have this problem or have a suggestion for fixing it?
Thanks
Bill
Random DATABASE_ERROR
Uhhh, weird. As a computer scientist, I despise inconsistency.
I assume you're using the same browser every time. If you've got FireFox, I recommend the EditCSS extension, because it lets you look at your CSS and modify it (for testing) directly. At least when the problem occurs, you can see *how* your CSS is mangled and decide if there's anything you can do about it.
The DATABASE_ERROR is probably the culprit, though. It sounds like the database server is overloaded, and you're lucky enough to get occasional good connections. (However, I don't think this should affect your CSS.) Do you get any more specific data, or just DATABASE_ERROR?
I assume you're using the same browser every time. If you've got FireFox, I recommend the EditCSS extension, because it lets you look at your CSS and modify it (for testing) directly. At least when the problem occurs, you can see *how* your CSS is mangled and decide if there's anything you can do about it.
The DATABASE_ERROR is probably the culprit, though. It sounds like the database server is overloaded, and you're lucky enough to get occasional good connections. (However, I don't think this should affect your CSS.) Do you get any more specific data, or just DATABASE_ERROR?
Hi Judebert,
I think that it may be caused by a permissions problem with my ISP. They have load-balancing which switches between two servers. One server had permission to access the database, other didn't. Therefore it worked 50% of the time. They are going to fix this shortly.
Thanks for your help!
Bill
I think that it may be caused by a permissions problem with my ISP. They have load-balancing which switches between two servers. One server had permission to access the database, other didn't. Therefore it worked 50% of the time. They are going to fix this shortly.
Thanks for your help!
Bill