I have found one more specialty of the system in question: All PHP applications running on the box have their own apache instance, all using mod-php, and are running under different UIDs. However, the php instances are all writing their session files to the default directory /var/lib/php5. I don't ...

Hi, I have found one more specialty of the system in question: All PHP applications running on the box have their own apache instance, all using mod-php, and are running under different UIDs. However, the php instances are all writing their session files to the default directory /var/lib/php5. I don...

I hope that you'll accept header traces from the live system with suhosin after I have tried in the test system and saw the issue there as well, since I am very very reluctant to break the production system where I'd have to exchange the PHP for about a dozen of other PHP apps to satisfy your debug...

What about suhosin? Disabled that already? The Debian maintainers of PHP 5.2.5 have assured me that suhosin does - in the default configuration - only add more verbose logs and all "active" things are disabled by default. IMHO working on this without trying to eradicate suhosin could be u...

Hi, while I haven't been awfully successful in reproducing the error in my lab setup, the followig perl code might help in keeping a watch on the PHP session directory. #!/usr/bin/perl -w use strict; use File::Find::Rule; use File::stat; use IO::File; use English; $OUTPUT_AUTOFLUSH=1; my $dir="...

Is it OK that _eight_ new sess_*-Files appear in /var/lib/php5 when I just call up the blog home page? Which file am I supposed to track? No, that's not OK. There should be a maximum of 3 session files created with the method I described in the earlier posting. Ok, that had something to do with the...

5. After each step you now perform, check the contents of your php session file. Is it OK that _eight_ new sess_*-Files appear in /var/lib/php5 when I just call up the blog home page? Which file am I supposed to track? attention to the time you spend on the site; if it reaches your PHP session garb...

Zugschlus wrote: No, that didn't help. However, after truncating and logging in to s9y, the table still had 0 rows. Shouldn't the login process create a row there?

And a full mysql server log shows that the table is not accessed when somebody logs in to the blog.

Greetings
Marc

This can only happen if serendipity_authenticate_author fails. Hm. s9y stores its cookie toknes in the serendipity_options table. Check if the layout of your options table is the one that comes with the default sql/db.sql layout? Maybe your tokens cannot be matched because this table is garbaged or...

Freudi wrote:Well, I don't know whether different s9y versions may be playing a role in here, but since rince's blog shows Serendipity 1.2 and Marc's a (yet unknown to me version) Serendipity 1.2.2...

My s9y is tracking stable svn.

Greetings
Marc

Just for the record, kazehakase has just joined the not-so-exclusive club where the issue shows - I get thrown back to the login screen as soon as I try do to something in the admin frontend. You know that there are a multitude of other possible ways this can happen? No, how could I? I do not have ...

Just for the record, kazehakase has just joined the not-so-exclusive club where the issue shows - I get thrown back to the login screen as soon as I try do to something in the admin frontend.

I'll find myself blogging with SQL statements in phpmyadmin soon, I fear.

I'd really love to help, but to me this issue is not reproducable neither with my own install nor with your vmware image using the browsers I have at hand... Would it probably help to have some strategically placed debug log output calls in the appropriate parts of s9y source code? I mean, somewher...

What exactly does Set-Cookie: serendipity[author_information]=deleted; expires=Sun, 18-Mar-2007 23:06:48 GMT; path=/; domain=127.0.0.1 Set-Cookie: serendipity[author_information_iv]=deleted; expires=Sun, 18-Mar-2007 23:06:48 GMT; path=/; domain=127.0.0.1 mean in the response to a POST /serendipity_...

What exactly does Set-Cookie: serendipity[author_information]=deleted; expires=Sun, 18-Mar-2007 23:06:48 GMT; path=/; domain=127.0.0.1 Set-Cookie: serendipity[author_information_iv]=deleted; expires=Sun, 18-Mar-2007 23:06:48 GMT; path=/; domain=127.0.0.1 mean in the response to a POST /serendipity_a...