[error] PHP Fatal error: session_start(): Failed to initialize storage module

[ricardom]

No sucess!

Ill downgrade to the 4.3.1 now.

Everything is ok now in the sites, so i must think that this is a bug or some issue in the 4.4.0 version of the php.

[Miquel]

I run PHP/4.3.11 on FreeBSD and still have this issue which I solved with the following solution:

added a .htaccess file in the public_html directory of the cpanel3-skel rootdir from the reseller account. In .htaccess I added the following line:

php_flag register_globals on

Now every new account automatically gets this .htaccess file with the right php settings. I use this for several months now and it works. However, I know it's not the right solution but since php admitted it's a bug in their programming it's a good alternative.

[jonathanalia]

any definitely solution for this problem?

[Shazan]

I had this problem with PHP 4.4.0. After downgrading it to 4.3.11 it went away...

[Shazan]

Unfortunately I was wrong... it worked for a while but now the error appears again...

[Shazan]

For everyone that is experiencing the problem, could you post the result of:

lsof | wc -l

and

sysctl -a | grep fs.file-max

?

I believe it could be connected to the open files in the system.

[ezztro]

Hello,

same Prob since 4 Days.
PHP 4.3.11 and the last cPanel Release

[HostIt]

Hello,

same Prob since 4 Days.
PHP 4.3.11 and the last cPanel Release

I would suggest at least upgrading to PHP 4.4.0, as you're using a very outdated version.

[anton_latvia]

We have found simple solution that works for us:
chown nobody.nobody /tmp

(We have this problem with PHP 4.3.10 and it doesn't look like they (PHP) did anything in 4.4.0, at least according to changelog)

[ezztro]

I would suggest at least upgrading to PHP 4.4.0, as you're using a very outdated version.

This is not the prob.

Same Error with 4.4.0

/tmp is nobody:nobody and 777

[bjarne]

I run PHP/4.3.11 on FreeBSD and still have this issue which I solved with the following solution:

added a .htaccess file in the public_html directory of the cpanel3-skel rootdir from the reseller account. In .htaccess I added the following line:

php_flag register_globals on

Now every new account automatically gets this .htaccess file with the right php settings. I use this for several months now and it works. However, I know it's not the right solution but since php admitted it's a bug in their programming it's a good alternative.

Why not just put register_globals on i php.ini?

[FijianTribe]

I was having this same issue, do not know why. I've also been having troubles rebuilding Apache from WHM. I had to replace the .htaccess file with an older one that was named .htaccess.11... something.

[Miquel]

Why not just put register_globals on i php.ini?

Because setting this on is a wellknown security risk. The safest way to program PHP is to set it off and program without register_globals. I found it somewhere a while ago on www.php.net. If you want to know more about this I suggest to search for it on www.php.net

In short: With register_globals on it means that variables used in the script can be manipulated from de browsers-adressbar resulting in unwanted output or when someone is really smart or lucky he might find a way to log into members-areas.