Hi I've checked the PHP ini and session.auto_start is off (0) [snip] Looks like your Session ID that you are trying to insert into the database in your session_start_handler function is a duplicate of an existing session. [/snip] It IS the existing session... I've verified this by being the only person that knows where the site is :) (and matching IDs in the DB, natch) This has stumped my hosting company as well as me Successful conclusion rewards a night out :) http://chrome.me.uk/snippets/ << to view the issue (may need a few refreshes) Use admin/admin to log in on this site (it's in dev :) ) Ooo at this point I should mention I'm replying to this from my home address, not work (yeah, I have no life...) Thanks all Dan ------------------- http://chrome.me.uk -----Original Message----- From: Richard Lynch [mailto:ceo@xxxxxxxxx] Sent: 16 February 2006 21:26 To: Dan Parry Cc: php-general@xxxxxxxxxxxxx Subject: Re: Session problems On Thu, February 16, 2006 3:50 am, Dan Parry wrote: > I've been getting an error while using a custom session handler > utilising a > MySQL database > > The error I receive is: > > Duplicate entry '<<PHPSESSID_REMOVED>>' for key 1 Looks like your Session ID that you are trying to insert into the database in your session_start_handler function is a duplicate of an existing session. > Warning: Unknown(): A session is active. You cannot change the session > module's ini settings at this time. in Unknown on line 0 This to me sounds like you have php.ini setting sessions to 'file' and then you try to change it in, say, .htaccess but php.ini has session.auto_start turned on, so you've already got an active 'file' session going, and PHP ain't gonna let you change horses in mid-stream to 'user' sessions... Just a Wild Guess. If you have .htaccess changing the session to 'user', try turning off session.auto_start as well, and it may fix it. You may also have to remove all cookies from your browser (and all user's browsers) to clear out all old session data... Or, perhaps, you could get away with changing the session ID name of the Cookie, which might resolve the situation enough that the old session data hanging around is a non-issue. > I've contacted my hosting company regarding this but currently they > don't > seem to know the cause -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php __________ NOD32 1.1412 (20060216) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
