Unfamiliar sessions error

[Schraalhans Keukenmeester]

I never saw it before, but today I got several:

Fatal error: session_start() [function.session-start]: Failed to
initialize storage module: user (path: /tmp) in
/usr/local/psa/home/vhosts/mydomain/httpdocs/test/script.php

In the few docs I found related to this msg problems with a custom
session handler are mentioned as the source of the problem, but I don't
even have a custom session handler. I use the default one, the default
path for session files etc etc.

The server is not my own, but my host's. The script hasn't changed for
weeks, and it worked before. All it does is test if a certain session
var exists. If not it opens a new session and sets the variable.

Apache2 server, PHP 5.0.4), the settings for sessions as copied from
phpinfo():
Session Support enabled
Registered save handlers files user sqlite
Registered serializer handlers php php_binary wddx

Directive Local Value Master Value
session.auto_start Off Off
session.bug_compat_42 Off Off
session.bug_compat_warn On On
session.cache_expire 180 180
session.cache_limiter nocache nocache
session.cookie_domain no value no value
session.cookie_lifetime 0 0
session.cookie_path / /
session.cookie_secure Off Off
session.entropy_file no value no value
session.entropy_length 0 0
session.gc_divisor 1000 1000
session.gc_maxlifetime 1440 1440
session.gc_probability 1 1
session.hash_bits_per_character 5 5
session.hash_function 0 0
session.name PHPSESSID PHPSESSID
session.referer_check no value no value
session.save_handler files files
session.save_path /tmp /tmp
session.serialize_handler php php
session.use_cookies On On
session.use_only_cookies Off Off
session.use_trans_sid 0 0

Any clues? Thanks in advance!
Sh.

[Erwin Moller]

Schraalhans Keukenmeester wrote:

I never saw it before, but today I got several:

Fatal error: session_start() [function.session-start]: Failed to
initialize storage module: user (path: /tmp) in
/usr/local/psa/home/vhosts/mydomain/httpdocs/test/script.php

In the few docs I found related to this msg problems with a custom
session handler are mentioned as the source of the problem, but I don't
even have a custom session handler. I use the default one, the default
path for session files etc etc.

The server is not my own, but my host's. The script hasn't changed for
weeks, and it worked before. All it does is test if a certain session
var exists. If not it opens a new session and sets the variable.

Apache2 server, PHP 5.0.4), the settings for sessions as copied from
phpinfo():
Session Support enabled
Registered save handlers files user sqlite
Registered serializer handlers php php_binary wddx

Directive Local Value Master Value
session.auto_start Off Off
session.bug_compat_42 Off Off
session.bug_compat_warn On On
session.cache_expire 180 180
session.cache_limiter nocache nocache
session.cookie_domain no value no value
session.cookie_lifetime 0 0
session.cookie_path / /
session.cookie_secure Off Off
session.entropy_file no value no value
session.entropy_length 0 0
session.gc_divisor 1000 1000
session.gc_maxlifetime 1440 1440
session.gc_probability 1 1
session.hash_bits_per_character 5 5
session.hash_function 0 0
session.name PHPSESSID PHPSESSID
session.referer_check no value no value
session.save_handler files files
session.save_path /tmp /tmp
session.serialize_handler php php
session.use_cookies On On
session.use_only_cookies Off Off
session.use_trans_sid 0 0

Any clues? Thanks in advance!
Sh.

Hi,

I don't get it. What is your seve hadler? file AND user?
I never saw that before.

I wrote userdefined session sava handlers too, but I changed the:
session.save_handler = files
to
session.save_handler = user

Seems like you use both.
Which one should PHP use?
Could that be the source of the problem?
Regards,
Erwin Moller

[Jerry Stuckle]

Schraalhans Keukenmeester wrote:

I never saw it before, but today I got several:

Fatal error: session_start() [function.session-start]: Failed to
initialize storage module: user (path: /tmp) in
/usr/local/psa/home/vhosts/mydomain/httpdocs/test/script.php

In the few docs I found related to this msg problems with a custom
session handler are mentioned as the source of the problem, but I don't
even have a custom session handler. I use the default one, the default
path for session files etc etc.

The server is not my own, but my host's. The script hasn't changed for
weeks, and it worked before. All it does is test if a certain session
var exists. If not it opens a new session and sets the variable.

Apache2 server, PHP 5.0.4), the settings for sessions as copied from
phpinfo():
Session Support enabled
Registered save handlers files user sqlite
Registered serializer handlers php php_binary wddx

Directive Local Value Master Value
session.auto_start Off Off
session.bug_compat_42 Off Off
session.bug_compat_warn On On
session.cache_expire 180 180
session.cache_limiter nocache nocache
session.cookie_domain no value no value
session.cookie_lifetime 0 0
session.cookie_path / /
session.cookie_secure Off Off
session.entropy_file no value no value
session.entropy_length 0 0
session.gc_divisor 1000 1000
session.gc_maxlifetime 1440 1440
session.gc_probability 1 1
session.hash_bits_per_character 5 5
session.hash_function 0 0
session.name PHPSESSID PHPSESSID
session.referer_check no value no value
session.save_handler files files
session.save_path /tmp /tmp
session.serialize_handler php php
session.use_cookies On On
session.use_only_cookies Off Off
session.use_trans_sid 0 0

Any clues? Thanks in advance!
Sh.

It looks like you don't have write access to /tmp. This could be
because the permissions on /tmp are wrong, /tmp is filled (disk quota), etc.

You need to be talking to your host.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attglobal.net
==================

[Schraalhans Keukenmeester]

Erwin Moller wrote:

Schraalhans Keukenmeester wrote:

>I never saw it before, but today I got several:

Fatal error: session_start() [function.session-start]: Failed to
initialize storage module: user (path: /tmp) in
/usr/local/psa/home/vhosts/mydomain/httpdocs/test/script.php

In the few docs I found related to this msg problems with a custom
session handler are mentioned as the source of the problem, but I don't
even have a custom session handler. I use the default one, the default
path for session files etc etc.

The server is not my own, but my host's. The script hasn't changed for
weeks, and it worked before. All it does is test if a certain session
var exists. If not it opens a new session and sets the variable.

Apache2 server, PHP 5.0.4), the settings for sessions as copied from
phpinfo():
Session Support enabled
Registered save handlers files user sqlite
Registered serializer handlers php php_binary wddx

Directive Local Value Master Value
session.auto_start Off Off
session.bug_compat_42 Off Off
session.bug_compat_warn On On
session.cache_expire 180 180
session.cache_limiter nocache nocache
session.cookie_domain no value no value
session.cookie_lifetime 0 0
session.cookie_path / /
session.cookie_secure Off Off
session.entropy_file no value no value
session.entropy_length 0 0
session.gc_divisor 1000 1000
session.gc_maxlifetime 1440 1440
session.gc_probability 1 1
session.hash_bits_per_character 5 5
session.hash_function 0 0
session.name PHPSESSID PHPSESSID
session.referer_check no value no value
session.save_handler files files
session.save_path /tmp /tmp
session.serialize_handler php php
session.use_cookies On On
session.use_only_cookies Off Off
session.use_trans_sid 0 0

Any clues? Thanks in advance!
Sh.

Hi,

I don't get it. What is your seve hadler? file AND user?
I never saw that before.

I wrote userdefined session sava handlers too, but I changed the:
session.save_handler = files
to
session.save_handler = user

Seems like you use both.
Which one should PHP use?
Could that be the source of the problem?
Regards,
Erwin Moller

The problem (or lack thereof) is I don't have no steenkin' custom
handler, at all. It's just PHP suddenly shouting I do. So either
something really odd is going on in my host's setup, or.... Well, I dunno.

I've asked them about the problem. No reports on /tmp being full or
inaccessible, no recent changes they could link to this situation.

I can't force the bahaviour in any way I could think off, it just pops
up now and then. I'll have another browse through the bug list, maybe
something I missed is there after all.

Thx for the input guys