[TYPO3-v4] No BE login?
Ernesto Baschny [cron IT]
ernst at cron-it.de
Wed Jan 26 10:12:36 CET 2011
Xavier Perseguers schrieb am 26.01.2011 10:07:
> Hi,
>
> Am I the only one having (again) the timeout problem on backend login
> form? I have this:
>
> 2011/01/26 05:15:19 [error] 2978#0: *634 FastCGI sent in stderr:
> "http://www2.paroisse.ch/ - cms: Locking
> [simple::8751f40896865888b95c87b7eba229e8]: Lock aquired
> http://www2.paroisse.ch/ - cms: Locking
> [simple::8751f40896865888b95c87b7eba229e8]: Acquired lock
> http://www2.paroisse.ch/ - cms: Locking
> [simple::8a87aaf611350a5fd4143e98e5692aac]: Lock aquired
> http://www2.paroisse.ch/ - cms: Locking
> [simple::8a87aaf611350a5fd4143e98e5692aac]: Acquired lock
> http://www2.paroisse.ch/ - cms: Locking
> [simple::8751f40896865888b95c87b7eba229e8]: Released lock
> http://www2.paroisse.ch/ - cms: Locking
> [simple::8a87aaf611350a5fd4143e98e5692aac]: Released lock" while reading
> response header from upstream, client: 10.0.0.10, server:
> www2.paroisse.ch, request: "GET /evangile/ HTTP/1.1", upstream:
> "fastcgi://127.0.0.1:9000", host: "www2.paroisse.ch", referrer:
> "http://www2.paroisse.ch/societes/choeurs-mixtes/marly-saints-pierre-et-paul/"
>
>
> After restarting the web server and manually removing the locks, I see
> the login form again but I wonder if there still not some remaining
> problem with the CSRF protection...
This has been fixed in RC3 (after RFC #17305, rev. 10306). Are you sure
your typo3_src is up-to-date?
Cheers,
Ernesto
More information about the TYPO3-project-v4
mailing list