Serendipity Forums

I discovered this on one of two serendipity blogs I run on my home system.
The blog with this problem was s9y.8.5 which I upgraded to 9.1. I thought maybe this might fix the problem, but it did not.

The other blog which is still running s9y_8.5 does not have this problem.

Neither blogs seemed to have any problems. They have both been running version 8.5 for close to 2.5 months.

When I select "create new user" the operation just seems to go into a continuous loop trying to connect.

I have both of these blogs setup as "VertialHosts". They are two unique URL's. These do not share serendipity code. Each has it's own s9y installation.

I running Apache 2.0.53; PHP-5.0.5; MYSQL 5.0.13-rc

Is the database corrupted?

The two serendipity versions have a completely different way of the "Add User" interface, so it can't be compared that easy.

Your error can be because of a corrupted user database, but also because of plugins or corrupted PHP files. You should enable your PHPs and Apache's ErrorLog/error_log settings and look for any errors or segfaults.

Best regards,
Garvin

appreciate your comments.
I have two logs running for the blog
the "Access log" and "error.log"

[Wed Oct 19 22:50:04 2005] [error] [client 64.21.248.11] File does not exist: /var/www/weweartights/fav

There are 5 repetitions of this error for that date. I think that was the date I setup this blog.

I looked at and compared my two supporting databases for my two blog sites
The sy9 blog 8.5 version as 22 tables (without the problem)
The newly created 9.1 blog which had the problem prior to the update has 29 tables

I'm using phpMyAdmin to view the databases. It doesn't report any errors with either databases.

Is there a plugin that runs the serendipity.author table ?
This is not a critical situation. I could easly just reinstall a fresh new database if I thought this would fix the problem. I just want to know I've tried everything before I do this.

Craig: Actually your Apache error log does not contain the errors I'm referring to - PHP errors are usually logged in a different file. That can be configured in the php.ini file, section "display_errors" and "error_log". You should also be able to see the current settings with a simple <?php phpinfo(); ?> script.

I actually don't think that it's a problem with the database, but a problem with either your PHP setup, or memory outage or another coredump issue...?!

Best regards,
Garvin