Bug #47236

Error at offset 6279 of 6338

Added by Philipp Maier over 2 years ago. Updated over 1 year ago.

Status:Needs Feedback Start date:2013-04-15
Priority:Should have Due date:
Assigned To:- % Done:

0%
Category:-
Target version:-
PHP Version:5.3 Complexity:
Has patch:No Affected Flow version:Git master

Description

Hi,

each time I clear the cache with 

flow:cache:flush --force
and reload, I'm first redirected to the login page (good) but then following error is thrown.

#1: Notice: unserialize() [<a href='function.unserialize'>function.unserialize</a>]: Error at offset 6279 of 6338 bytes in /path/to/flow/Packages/Framework/TYPO3.Flow/Classes/TYPO3/Flow/Cache/Frontend/VariableFrontend.php line 84

After clearing the cache again, the error is gone and I can view the login page and continue.

I've absolutely no clue what causes this.

History

#1 Updated by Robert Lemke about 2 years ago

  • Status changed from New to Needs Feedback

Which Cache Backend(s) do you use? Anything else than FileBackend?

Can you provide a small package / setup / steps which reproduce this bug?

#2 Updated by Daniel Ostmann about 2 years ago

Exactly the same. On developement machine it runs pretty well without any errors. When mirror it to the live machine i get this error.

I think it is an issue regarding the machine.

PHP 5.3.2-1ubuntu4.19 with Suhosin-Patch (cli) (built: Mar 11 2013 15:23:48) 
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies

(I can't get more infos but phpinfo() if wanted)

#3 Updated by Jacob Floyd about 2 years ago

@Daniel

PHP 5.3.2 is really old. What version are you running in development?

#4 Updated by Daniel Ostmann about 2 years ago

Mmh... Very old indeed. My delevopment server is PHP 5.4.4.

#5 Updated by Daniel Ostmann about 2 years ago

Could it be a charset issue?

#6 Updated by Daniel Ostmann about 2 years ago

Seems like a session issue. After a while the session was deleted and now it works. I'll keep in track.

#7 Updated by Daniel Ostmann about 2 years ago

Mmh. I logged out and the error occurs again...

#8 Updated by Daniel Ostmann about 2 years ago

What about this:

It can also happen if you are only using cookies for storing session data and the (serialized) data exceeds the 4k max that cookies can store.  It breaks the serialized array being stored as the string gets truncated, so it can’t unserialize it.

Found in http://ellislab.com/forums/viewthread/134524/#1038212

#9 Updated by Daniel Ostmann almost 2 years ago

Please take a look at #45407.

Changing the database driver settings solved the problem for me!

#10 Updated by Daniel Ostmann almost 2 years ago

Sorry, it didn't solve my problem...

#11 Updated by Irene Höppner over 1 year ago

Seems to be a server settings topic. I have the same problem reproducable on my local machine, but not on the remote server.

#12 Updated by Irene Höppner over 1 year ago

I could isolate it a bit more: The problem occurs with the native php serialization, not with igbinary.

The mentioned position of the error is the reference (e.g. r:24) to the parentRequest object of the ActionRequest that is referenced somewhere inside the security context. I guess that referencing is causing problems...

#13 Updated by Philipp Maier over 1 year ago

I've not had this one in months now.

Also available in: Atom PDF