Update 1.13.2 to 1.14.11 - strange error

104 views
Skip to first unread message

Stefan Winter

unread,
Mar 28, 2017, 5:36:00 AM3/28/17
to SimpleSAMLphp
Hi,

after upgrading from 1.13 to 1.14, copying over all config files, I get server errors with something rather weird in the logs:

[28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Warning: Erroneous data format for unserializing 'SimpleSAML_Session' in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/SessionHandlerPHP.php on line 263
[28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Notice: unserialize(): Error at offset 30 of 4067 bytes in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/SessionHandlerPHP.php on line 263
[28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Notice: Trying to get property of non-object in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 335
[28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Catchable fatal error: Argument 1 passed to SimpleSAML_Session::load() must be an instance of SimpleSAML_Session, boolean given, called in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 266 and defined in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 378
[28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Catchable fatal error: Argument 1 passed to SimpleSAML_Session::load() must be an instance of SimpleSAML_Session, boolean given, called in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 266 and defined in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 378

So... something went wrong during an unserialize() ? That doesn't look like something I could have done wrong myself.

The setup is mildly special in that the www subfolder is in the webroot while the rest of the installation is outside; I have adapted the "autoloader" loading (line 32) for it to find itself.

It used to be working like that for many SSP versions, so I don't suspect the error to be there?

Greetings,

Stefan Winter

--
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche
2, avenue de l'Université
L-4365 Esch-sur-Alzette

Tel: +352 424409 1
Fax: +352 422473

PGP key updated to 4096 Bit RSA - I will encrypt all mails if the recipient's key is known to me

http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0DE6A358A39DC66
0x8A39DC66.asc
signature.asc

Jaime Perez Crespo

unread,
Mar 28, 2017, 6:02:08 AM3/28/17
to SimpleSAMLphp
Hi Stefan,

On 28 Mar 2017, at 11:35 AM, Stefan Winter <stefan...@restena.lu> wrote:
> Hi,
>
> after upgrading from 1.13 to 1.14, copying over all config files, I get server errors with something rather weird in the logs:
>
> [28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Warning: Erroneous data format for unserializing 'SimpleSAML_Session' in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/SessionHandlerPHP.php on line 263
> [28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Notice: unserialize(): Error at offset 30 of 4067 bytes in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/SessionHandlerPHP.php on line 263
> [28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Notice: Trying to get property of non-object in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 335
> [28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Catchable fatal error: Argument 1 passed to SimpleSAML_Session::load() must be an instance of SimpleSAML_Session, boolean given, called in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 266 and defined in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 378
> [28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Catchable fatal error: Argument 1 passed to SimpleSAML_Session::load() must be an instance of SimpleSAML_Session, boolean given, called in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 266 and defined in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 378
>
> So... something went wrong during an unserialize() ? That doesn't look like something I could have done wrong myself.
>
> The setup is mildly special in that the www subfolder is in the webroot while the rest of the installation is outside; I have adapted the "autoloader" loading (line 32) for it to find itself.
>
> It used to be working like that for many SSP versions, so I don't suspect the error to be there?

That’s “normal”.

In the latest versions of SimpleSAMLphp we addressed an issue with eduPersonTargetedID. Basically, its value was lost when serializing the session if the value was a NameID (as it should be, on the other hand). This was due to the NameID not being parsed in older versions of the SAML2 library, and therefore an unserializable DOM object being returned. In any case, in order to fix this we had to change slightly the way we serialize the session object (basically, intercept serialization so that we could dump to string any DOM objects, and the other way around). This change had the unwanted side effect of errors like the ones you are seeing.

Luckily, errors are temporary and happen only for those users who already had a session before the update, and then load it again after the update. If I’m not mistaken, the errors do not invalidate the session (so the users shouldn’t note anything), and they should happen only once, as saving the session again will solve the problem.

So to summarize: nothing to worry about.

--
Jaime Pérez
UNINETT / Feide

jaime...@uninett.no
jaime...@protonmail.com
9A08 EA20 E062 70B4 616B 43E3 562A FE3A 6293 62C2

"Two roads diverged in a wood, and I, I took the one less traveled by, and that has made all the difference."
- Robert Frost

Michael Dondrup

unread,
Mar 28, 2017, 6:16:18 AM3/28/17
to simple...@googlegroups.com, Stefan Winter
Hi,

which version of PHP are you running. It seems that newer version of simpleSAMLphp >= 1.14 are incompatible with
PHP 5.3.

Michael

Michael Dondrup
Researcher
Sea Lice Research Centre
Department of Informatics
University of Bergen
Thormøhlensgate 55, N-5008 Bergen,
Norway
> --
> You received this message because you are subscribed to the Google Groups "SimpleSAMLphp" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to simplesamlph...@googlegroups.com.
> To post to this group, send email to simple...@googlegroups.com.
> Visit this group at https://groups.google.com/group/simplesamlphp.
> For more options, visit https://groups.google.com/d/optout.
> <0x8A39DC66.asc>

signature.asc

Jaime Perez Crespo

unread,
Mar 28, 2017, 6:29:35 AM3/28/17
to simple...@googlegroups.com
Hei Michael,

On 28 Mar 2017, at 12:16 PM, Michael Dondrup <michael...@ii.uib.no> wrote:
> Hi,
>
> which version of PHP are you running. It seems that newer version of simpleSAMLphp >= 1.14 are incompatible with
> PHP 5.3.

Why do you say that?

SimpleSAMLphp has never dropped support for PHP 5.3 (yet), not even in master.

Michael Dondrup

unread,
Mar 28, 2017, 7:07:52 AM3/28/17
to simple...@googlegroups.com
Hei Jaime,


> On Mar 28, 2017, at 12:29 PM, Jaime Perez Crespo <jaime...@uninett.no> wrote:
>
> Hei Michael,
>
> On 28 Mar 2017, at 12:16 PM, Michael Dondrup <michael...@ii.uib.no> wrote:
>> Hi,
>>
>> which version of PHP are you running. It seems that newer version of simpleSAMLphp >= 1.14 are incompatible with
>> PHP 5.3.
>
> Why do you say that?
>
> SimpleSAMLphp has never dropped support for PHP 5.3 (yet), not even in master.



I was recalling a discussion we had last year:

> On Jun 13, 2016, at 11:54 AM, Jaime Perez Crespo <jaime...@uninett.no> wrote:

> Hi Michael,
>
> Were you using 1.14.3? If that’s the case, that file hasn’t changed in the last release. In fact, line 31 in that file hasn’t changed since 2008.
>
> Could it be that you were using 1.13.X before upgrading to 1.14.4, and you are running PHP 5.3? SimpleSAMLphp requires now at least PHP 5.4 to run.
>

I will test the update again.

Michael



On 13 Jun 2016, at 11:07 AM, 'Michael Dondrup' via SimpleSAMLphp <simple...@googlegroups.com> wrote:
> Hi,
> I am facing a problem after the update: The Idp select list doesn’t have entries and I get:
>
> PHP Fatal error: Using $this when not in object context in simplesamlphp/templates/selectidp-dropdown.php on line 31
>
> This doesn’t happen with the previous version.







>
> --
> Jaime Pérez
> UNINETT / Feide
>
> jaime...@uninett.no
> jaime...@protonmail.com
> 9A08 EA20 E062 70B4 616B 43E3 562A FE3A 6293 62C2
>
> "Two roads diverged in a wood, and I, I took the one less traveled by, and that has made all the difference."
> - Robert Frost
>
signature.asc

Stefan Winter

unread,
Mar 28, 2017, 8:52:02 AM3/28/17
to Michael Dondrup, simple...@googlegroups.com
Hi,

well, I for one was on 5.6 (and anyone using less should be mindful of
the discontinued state of those versions!).

Jaime's explanation was spot-on; a simple "did you try turning your
browser off and on again" fixed the issue. Now everyone in the office
has a fresh browser session and the update is history :-)

Stefan
0x8A39DC66.asc
signature.asc

Jaime Perez Crespo

unread,
Mar 28, 2017, 9:31:53 AM3/28/17
to simple...@googlegroups.com
Hi again Michael,

On 28 Mar 2017, at 13:07 PM, Michael Dondrup <michael...@ii.uib.no> wrote:
> Hei Jaime,
>
> I was recalling a discussion we had last year:
>
>> On Jun 13, 2016, at 11:54 AM, Jaime Perez Crespo <jaime...@uninett.no> wrote:
>> Hi Michael,
>>
>> Were you using 1.14.3? If that’s the case, that file hasn’t changed in the last release. In fact, line 31 in that file hasn’t changed since 2008.
>>
>> Could it be that you were using 1.13.X before upgrading to 1.14.4, and you are running PHP 5.3? SimpleSAMLphp requires now at least PHP 5.4 to run.
>
> I will test the update again.

That’s weird indeed! I don’t have any clue why I said so at the time, but in any case it wasn’t true…

My bad!
Reply all
Reply to author
Forward
0 new messages