[Owncloud] Login impossible since update from 4.0.6 to 4.5beta2

[auipga]

I renamed the old OC folder to "owncloud406" and uploaded the owncloud
folder to the same path where it has been before. The database was
completely flushed.

In the error_log I saw following:

[Fri Sep 21 13:26:34 2012] [warn] [client 91.2.214.250] mod_fcgid: stderr:
PHP Warning:  session_start():
open(/var/lib/php5/sess_tl2jk3his45s97sp8041f1grvokf8g05, O_RDWR) failed:
Permission denied (13) in
/srv/www/vhosts/***.de/subdomains/cloud/httpdocs/lib/base.php on line 262,
referer: https://cloud.***.de/
[Fri Sep 21 13:26:34 2012] [warn] [client 91.2.214.250] mod_fcgid: stderr:
PHP Warning:  Unknown:
open(/var/lib/php5/sess_tl2jk3his45s97sp8041f1grvokf8g05, O_RDWR) failed:
Permission denied (13) in Unknown on line 0, referer: https://cloud.***.de/
[Fri Sep 21 13:26:34 2012] [warn] [client 91.2.214.250] mod_fcgid: stderr:
PHP Warning:  Unknown: Failed to write session data (files). Please verify
that the current setting of session.save_path is correct (/var/lib/php5) in
Unknown on line 0, referer: https://cloud.***.de/



2012/9/18 Christian Reiner <foss at christian-reiner.info>

> Hi...
>
> > > > On Wednesday 12 September 2012 21:08:22 auipga wrote:
> > > > a few days ago I updated my ownCloud from version 4.0.6 to 4.5beta2.
> > > Since then I can't login anymore, regardless which account I use.
>
> > > 2012/9/12 Christian Reiner <foss at christian-reiner.info>
> > > Try disabling the enabled apps one by one in the database.
> > > Each app has a setting called 'enabled' with value 'yes' in table
> > > oc_appconfig.
> > > Change the 'yes' to 'no' one by one and try to login after each change.
> > >
> > > Some users reported success using this strategy.
> > > Sadly it appears to be some other app each time :-(
>
> On Sunday 16 September 2012 17:42:08 you wrote:
> > I made a fresh installation, new database. Same behaviour. Cannot explain
> > why...
>
> em... since this is indeed strange I want to ask if that really is a
> complete
> fresh install. Or if there are any "old" files left over. That means:
> - "only" a new database or really all files deleted and feshly installed?
> I ask this because there are incidents with cached scripts (server side
> cached). There is a workaround to get these refreshed, afterwards some
> people
> reported to be able to login again. However this obviously cannot be the
> case
> in a real fresh install. That sounds more like a general setup problem.
>
> My suggestion: make a _really_ fresh install somewhere in the filesystem
> where
> OC was not installed before. Publish that installation as a URL not used
> for
> OC before. Same behaviour? Then you have a setup problem outside OC.
>
>
> --
> Christian Reiner (arkascha)
> [ foss at christian-reiner.info ]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/owncloud/attachments/20120921/b8fe0770/attachment.html>