StorageService-backed RelayState mechanism did not return a state value.

[Dan McLaughlin]

I don't see any other errors, just:

2018-11-19 13:02:18 ERROR Shibboleth.SessionInitiator.SAML2 [9416]
shib_handler [default]: StorageService-backed RelayState mechanism did
not return a state value.
2018-11-19 13:02:33 ERROR Shibboleth.SessionInitiator.SAML2 [9416]
shib_handler [default]: StorageService-backed RelayState mechanism did
not return a state value.
2018-11-19 13:02:35 ERROR Shibboleth.SSO.SAML2 [9416] shib_handler
[default]: StorageService-backed RelayState mechanism did not return a
state value.
2018-11-19 13:03:03 ERROR Shibboleth.SessionInitiator.SAML2 [9416]
shib_handler [default]: StorageService-backed RelayState mechanism did
not return a state value.
2018-11-19 13:03:49 ERROR Shibboleth.SessionInitiator.SAML2 [9416]
shib_handler [default]: StorageService-backed RelayState mechanism did
not return a state value.

This is how I have the StorageService configured...

<StorageService type="Memory" id="mem" cleanupInterval="900"/>
    <DataSealer type="Versioned" path="sealer.keys" />
    <SessionCache type="StorageService" StorageService="mem"
cacheAssertions="false"
                  cacheAllowance="3600" inprocTimeout="900"
cleanupInterval="900"
  persistedAttributes="shibb_agency_id shibb_email shibb_first_name
shibb_guid shibb_idp_user_id shibb_last_name shibb_phone_number
shibb_district_division"/>
    <ReplayCache StorageService="mem"/>
    <ArtifactMap artifactTTL="180"/>


--

Thanks,

Dan
On Mon, Nov 19, 2018 at 1:05 PM Dan McLaughlin
<dmclaughlin at tech-consortium.com> wrote:
>
> We see in the apache access logs the user id being logged, then all of
> the sudden the user id is logged as a "-" so I'm assuming that means
> they are no longer logged in.
>
> --
>
> Thanks,
>
> Dan
>
> On Mon, Nov 19, 2018 at 1:01 PM Cantor, Scott <cantor.2 at osu.edu> wrote:
> >
> > On 11/19/18, 1:57 PM, "users on behalf of Dan McLaughlin" <users-bounces at shibboleth.net on behalf of dmclaughlin at tech-consortium.com> wrote:
> >
> > > We recently moved to SP 3.0.2, we tested fine in our test environment,
> > > but after moving into production where we have a much larger user base
> > > we started seeing the following error in logs.
> >
> > Can't be the only thing in the log, whatever's wrong with the database or memcache is certainly there.
> >
> > > It also seems as if users are losing their login session because of it.
> >
> > That's not sessions, that's on session creation. They'll end up at the home URL. If they're losing sessions then you have more errors specific to session storage, and I would expect that if it's the same service.
> >
> > -- Scott
> >
> >
> > --
> > For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
> > To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net