Hi Cor,

will revert asap with info.

At least I can tell already that the behaviour is pretty inconsistent. Sometimes the session is staying alive for a while, sometimes it's terminated within seconds or minutes.

I just encountered the situation while composing a message and doing an addressbook lookup by typing a name in the Cc: field, all of a sudden I got a "Forbidden 500.". Hmmm.

Cheers,

Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany

Am 08.03.2015 01:25, schrieb Cor Bosman:

...

On 07 Mar 2015, at 19:53, Michael Heydekamp listuser@freexp.de wrote:

Hi,

currently my Roundcube session is being terminated every few minutes, so I have to type this message pretty fast. ;)

Roundcube Webmail 1.2-git [GIT 20150306.1906]

Ist this a (known) Roundcube issue...?

If you're running the latest master as of yesterday, it's probably something in my session PR. Could you explain a bit about your configuration with regards to sessions? What session storage? session_lifetime? Refresh interval?

The PR was quite a bit of code, so could very well have a bug someplace. Ive been using that code myself for a few weeks without problems but it could be some set of options I didnt check,

Cor

---

Roundcube Development discussion mailing list dev@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/dev

Am 08.03.2015 22:23, schrieb Cor Bosman:

...

On 08 Mar 2015, at 16:34, Michael Heydekamp listuser@freexp.de wrote:

...

I just encountered the situation while composing a message and doing an addressbook lookup by typing a name in the Cc: field, all of a sudden I got a "Forbidden 500.". Hmmm.

Hi Michael, the 500 error is probably because you dont have all the components that roundcube requires. As of 1.1.0 (and thus 1.2-git) you need to install a bunch of dependancies using composer. Check out the composer.json-dist, and make sure you have everything thats in there in your own composer.json. Then do a 'composer update'.

That will probably take care of the 500 server errors, as you're most likely missing the PEAR libs,

We'll certainly check this again, but AFAIR we have all required components installed.

Just did the same with another message (doing an addressbook lookup by typing a name in the Cc: field), and now it worked. :/

Cheers,

Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany

I can copy this. When the session garbage collector kicks in, I see this error logged:

PHP Warning: Missing argument 1 for rcube_session::gc() in /www/roundcube/master/program/lib/Roundcube/rcube_session.php on line 225

And the DB driver deletes all records with DELETE FROM session WHERE changed < now();

I'll investigate that later when I have more time to spend on it.

~Thomas

On Sun, Mar 8, 2015 at 10:32 PM, Cor Bosman cor@xs4all.nl wrote:

...

On 08 Mar 2015, at 17:30, Michael Heydekamp listuser@freexp.de wrote:

Am 08.03.2015 22:23, schrieb Cor Bosman:

...

...

On 08 Mar 2015, at 16:34, Michael Heydekamp listuser@freexp.de wrote:

...

...

I just encountered the situation while composing a message and doing an addressbook lookup by typing a name in the Cc: field, all of a sudden I got a "Forbidden 500.". Hmmm.

Hi Michael, the 500 error is probably because you dont have all the components that roundcube requires. As of 1.1.0 (and thus 1.2-git) you need to install a bunch of dependancies using composer. Check out the composer.json-dist, and make sure you have everything thats in there in your own composer.json. Then do a 'composer update'.

That will probably take care of the 500 server errors, as you're most likely missing the PEAR libs,

We'll certainly check this again, but AFAIR we have all required components installed.

Just did the same with another message (doing an addressbook lookup by typing a name in the Cc: field), and now it worked. :/

Anyways, if you're getting 500 errors that are not caused by missing libs, your logfile should tell you the actual error. That would be useful to know :)

Cor

---

Roundcube Development discussion mailing list dev@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/dev

Fixed in https://github.com/roundcube/roundcubemail/commit/87ff88d55 https://github.com/roundcube/roundcubemail/commit/87ff88d55

Thanks Thomas, duh. That was that last change I did, and didnt pay attention :)

Cor

On 09 Mar 2015, at 18:06, Michael Heydekamp listuser@freexp.de wrote:

Am 09.03.2015 19:27, schrieb Cor Bosman:

...

...

Fixed in https://github.com/roundcube/roundcubemail/commit/87ff88d55 https://github.com/roundcube/roundcubemail/commit/87ff88d55

Thanks Thomas, duh. That was that last change I did, and didnt pay attention :)

Cor

So, are we done now or is more information from our side still required...?

Currently I'm not encountering any terminated sessions anymore.

But, Cor: If you do such a code change, shouldn't you (or anybody else) encounter the same problem whilst using Roundcube? I'm wondering why it is just me...

I did not encounter it, and ive been using that code for a while. It probably has something to do with php.ini settings with regards to session lifetime/divisor/probability etc. My usage pattern on my dev vagrant box probably causes an extremely low probability of actual garbage collection happening.

Anyways, we are done yes. Unless you notice any other problems, in which case let us know and post some error logs.

thanks for reporting,

Cor