Posted by mrbog on 03/06/07 04:23

On Mar 4, 11:28 pm, Rik <luiheidsgoe...@hotmail.com> wrote:
> mrbog <dterr...@hotmail.com> wrote:
>
> > My server was working fine (no one else changes it but me, it's a
> > local server on my lan), and all of a sudden I get:
>
> > Fatal error: session_start(): Failed to initialize storage module:
> > user...
>
> > It didn't even happen after like a reboot or something, it just
> > happened one morning.
>
> > I fixed it by changing:
>
> > session.save_handler = user
>
> > to
>
> > session.save_handler = files
>
> > But my question is- why did I have to do that? What could've
> > happened? How do I make it work with "user" again?
>
> Correct me if I'm wrong here, but AFAIK, 'user' is not a deault handler.
> If there are problems saving sessions with the 'user' session handler,
> you'd have to check that logic. In many custom handlers it's done in
> combination with a database, so you might check wether that database is
> reachable, not at it's limits (either by primary/unique index or size
> enforced by hoster).
> --
> Rik Wasmus

It's not saving to a database, it's creating a session file.

And as stated in my question there is no "hoster", it's my lan server,
and I'm the only one that touches it.

[Back to original message]