[pmwiki-users] Problems/Warnings after implementing passwords in config.php

Joachim Durchholz jo at durchholz.org
Tue May 9 23:49:28 CDT 2006


Andrew schrieb:
> *Warning*: session_write_close(): 
> open(/hsphere/local/home/easterns/tmp/sess_0e44bc3f5703840ba202c60038bf8774, 
> O_RDWR) failed: No such file or directory (2) in 
> */hsphere/local/home/easterns/easternsailplane.com/pmwiki/pmwiki.php* on line *1568*
> 
> *Warning*: session_write_close(): Failed to write session data (files). Please 
> verify that the current setting of session.save_path is correct 
> (/hsphere/local/home/easterns/tmp) in 
> */hsphere/local/home/easterns/easternsailplane.com/pmwiki/pmwiki.php* on line *1568
> =========
> 
> *The path given in the error is correct and I have all the directory permissions 
> set to 777 in my pmwiki directory, my field directory and all sub 
> directories/files in these directories and still no joy.  I even made sure that 
> the 'tmp' directory exists and also set it with 777 permissions.  When I comment 
> out the $DefaultPasswords line every thing goes back to normal, but of course no 
> edit password.

Most likely cause: A typo somewhere in the file name. Look for stray blanks.

You can verify whether the file/directory that the script is trying to 
access actually exists. Simply copy the file name from the error message 
and try to touch is via ssh.
(Obviously, you need shell access to do that. If you're restricted to 
FTP, you can't check that easily - FTP paths tend to be different from 
the filesystem paths. You could upload a script that does nothing but 
<?php print is_writable('directory_name_from_error_message')); ?> 
though. Given your description, it should print a 0 and exit; to make 
session handling work, you'll need a 1.)
Copying the file name from the error message to an editor with a 
monospaced font might help spot typos.

Second-likely cause: a corrupted PHP binary (rare but happens).

For further analysis, we might have to look at some phpinfo output from 
your site (the easiest thing would be posting a URL).


Note that this is most likly not related to PmWiki. The error points to 
a PHP issue/misconfiguration wrt. the session directory. PmWiki just 
happens to trigger the problem when it tries to remember the user's 
session data (which is created on user logins).
You can verify this. Edit a page, enter something in the Author: field, 
and save. PmWiki should try to store the author name in the session data 
and fail with the same error.

HTH
Jo




More information about the pmwiki-users mailing list