Jump to content


This topic is now archived and is closed to further replies.


Wierd errors

Recommended Posts

I get the following errors on any .php page on my website, regardless of whether there is any php code on the page or not.  They first appeared when I was trying to get sessions to work on my login system, but don't seem to affect the code in any way.  The only thing is I still can't get the sessions to work. :(
[u]The Errors[/u]
[code]Warning: Unknown(): open(c:/windows/temp/sess_79674f4cff818c4f5b53f302d68a25e6, O_RDWR) failed: No such file or directory (2) in Unknown on line 0

Warning: Unknown(): Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:/windows/temp) in Unknown on line 0[/code]

Any ideas?

Share this post

Link to post
Share on other sites
Have you tried to clean out your browser cache?

Also maybe your website hosting provider does not support sessions? Stupid question to say but it may be true.

Share this post

Link to post
Share on other sites
Cleaned out the browser cache - makes no difference.
Checked for a cookie - apparently I had one.  Deleted it to see if it made any difference.  No such luck.

Can a hosting provider NOT support sessions?  PHP works fully, and I can edit the php.ini file.

Still stumped...

Share this post

Link to post
Share on other sites
Yes it is possible for a host to disable sessions.

If so just test to see if this is the case:
$_SESSION["test"] = "hello im test data";
echo (isset($_SESSION["test"]) ? ("Session set &amp; contains: " . $_SESSION["test"]) : ("Session was not set"));

Share this post

Link to post
Share on other sites
i don't think that will prove if sessions are enabled or not.  i don't think a session actually starts until you go to a new page. For example, you can remove the session_start() (or comment it out) and your ternary will still return true. at the very least you would have to break that up into 2 scripts.

Share this post

Link to post
Share on other sites
The page doesn't have to be reloaded to read/write sessions... (Sessions are server side...)

I fixed up my example above, thanks for pointing out the void logic :D
$test = "my data";
echo "Session was set";
echo "session was not set";

Share this post

Link to post
Share on other sites
Firstly, thanks for the help...

Right.  Using the first script you posted, the session was set, but when I tried to split it, the session was not set.  Using your second script gave me session was set as well.

Both cases are still producing the errors.  I'm trying to remember what I changed prior to them appearing...

EDIT:  Found the problem.  It was my php.ini file that was causing them, although I don't know why.  I've posted the sessions section below to see if you can see the problem.
; Handler used to store/retrieve data.
session.save_handler = files

; Argument passed to save_handler.  In the case of files, this is the path
; where data files are stored. Note: Windows users have to change this
; variable in order to use PHP's session functions.
; As of PHP 4.0.1, you can define the path as:
;    session.save_path = "N;/path"
; where N is an integer.  Instead of storing all the session files in
; /path, what this will do is use subdirectories N-levels deep, and
; store the session data in those directories.  This is useful if you
; or your OS have problems with lots of files in one directory, and is
; a more efficient layout for servers that handle lots of sessions.
; NOTE 1: PHP will not create this directory structure automatically.
;        You can use the script in the ext/session dir for that purpose.
; NOTE 2: See the section on garbage collection below if you choose to
;        use subdirectories for session storage
; The file storage module creates files using mode 600 by default.
; You can change that by using
;    session.save_path = "N;MODE;/path"
; where MODE is the octal representation of the mode. Note that this
; does not overwrite the process's umask.
session.save_path = "C:/temp"

; Whether to use cookies.
session.use_cookies = 1

; This option enables administrators to make their users invulnerable to
; attacks which involve passing session ids in URLs; defaults to 0.
; session.use_only_cookies = 1

; Name of the session (used as cookie name).
session.name = PHPSESSID

; Initialize session on request startup.
session.auto_start = 1

; Lifetime in seconds of cookie or, if 0, until browser is restarted.
session.cookie_lifetime = 0

; The path for which the cookie is valid.
session.cookie_path = /

; The domain for which the cookie is valid.
session.cookie_domain =

; Handler used to serialize data.  php is the standard serializer of PHP.
session.serialize_handler = php

; Define the probability that the 'garbage collection' process is started
; on every session initialization.
; The probability is calculated by using gc_probability/gc_divisor,
; e.g. 1/100 means there is a 1% chance that the GC process starts
; on each request.

session.gc_probability = 1
session.gc_divisor    = 100

; After this number of seconds, stored data will be seen as 'garbage' and
; cleaned up by the garbage collection process.
session.gc_maxlifetime = 1440

; NOTE: If you are using the subdirectory option for storing session files
;      (see session.save_path above), then garbage collection does *not*
;      happen automatically.  You will need to do your own garbage
;      collection through a shell script, cron entry, or some other method.
;      For example, the following script would is the equivalent of
;      setting session.gc_maxlifetime to 1440 (1440 seconds = 24 minutes):
;          cd /path/to/sessions; find -cmin +24 | xargs rm

; PHP 4.2 and less have an undocumented feature/bug that allows you to
; to initialize a session variable in the global scope, albeit register_globals
; is disabled.  PHP 4.3 and later will warn you, if this feature is used.
; You can disable the feature and the warning seperately. At this time,
; the warning is only displayed, if bug_compat_42 is enabled.

session.bug_compat_42 = 1
session.bug_compat_warn = 1

; Check HTTP Referer to invalidate externally stored URLs containing ids.
; HTTP_REFERER has to contain this substring for the session to be
; considered as valid.
session.referer_check =

; How many bytes to read from the file.
session.entropy_length = 0

; Specified here to create the session id.
session.entropy_file =

;session.entropy_length = 16

;session.entropy_file = /dev/urandom

; Set to {nocache,private,public,} to determine HTTP caching aspects
; or leave this empty to avoid sending anti-caching headers.
session.cache_limiter = nocache

; Document expires after n minutes.
session.cache_expire = 180

; trans sid support is disabled by default.
; Use of trans sid may risk your users security.
; Use this option with caution.
; - User may send URL contains active session ID
;  to other person via. email/irc/etc.
; - URL that contains active session ID may be stored
;  in publically accessible computer.
; - User may access your site with the same session ID
;  always using URL stored in browser's history or bookmarks.
session.use_trans_sid = 0

; Select a hash function
; 0: MD5  (128 bits)
; 1: SHA-1 (160 bits)
session.hash_function = 0

; Define how many bits are stored in each character when converting
; the binary hash data to something readable.
; 4 bits: 0-9, a-f
; 5 bits: 0-9, a-v
; 6 bits: 0-9, a-z, A-Z, "-", ","
session.hash_bits_per_character = 4

; The URL rewriter will look for URLs in a defined set of HTML tags.
; form/fieldset are special; if you include them here, the rewriter will
; add a hidden <input> field with the info which is otherwise appended
; to URLs.  If you want XHTML conformity, remove the form entry.
; Note that all valid entries require a "=", even if no value follows.
url_rewriter.tags = "a=href,area=href,frame=src,input=src,form=,fieldset="

EDIT2: Right.  I've managed to get it to work, although I'm now using setcookie() instead of $_SESSION. 

Share this post

Link to post
Share on other sites


Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.