Joomla and Linux Session Save path / session.save_path

I'm not sure what I did wrong, but I tried to change session.save_path settings to Y;/path
when I did that I started to have big problems on my website and when I tried to put it back to N;/path, the problems are still there...
it used to show :N;/path **DEFAULT**, Click to Edit (with a line crossing the N'/path)
now if i only put N'/path, my website is still not back to normal, i cant' even login
is there a way to come back to what it was before? what did I do wrong?

Posted On: 06 Feb 2009 09:17 AM
What we can do is restore either your entire domain, or just your public_html from a backup.
I noticed on your server there is a backup file from
in your cprestore directory.
and then there are the follwoing backups in your /home/hotelboo directory

and also on our own nas servers there are the follwoing backups
This email address is being protected from spambots. You need JavaScript enabled to view it.
This email address is being protected from spambots. You need JavaScript enabled to view it.

Please let us know if this is how you would like us to proceed, if so, do you want us to restore the entire account, or just the public_html for the account and also if you want us to restore we require you answer our secuity challenge.

Can you verify the last 4 digits of your credit card? This is to verify you are the account holder.

If you pay with paypal, please provide your paypal email address, date of last payment, and the amount you paid.

Posted On: 06 Feb 2009 09:28 AM
1. really? by typing that "Y" I damaged the whole thing? there's no other way than to reload a backup?

2. I thought that the system was making backups every day, every week and every month... but I don't see them here

3. i can see that the most recent backup is the one from the server dating 02.02.09 is that correct?

my cc is 6291
Posted On: 06 Feb 2009 09:31 AM
We can check to see if you have any other backups of this domain on your server, however we would need to know where you have your backups configured to save at
do you know what the directory path to you backups are?
also do you want us to restore the entire domain or just public_html ( mysql is not part of public_html, neither are your mail directories )

Posted On: 06 Feb 2009 09:35 AM
I don't think there are more recent backups.
but usually hfw keeps daily/weekly/monthly backups isn't it?
if not, can that feature be enabled again please... or is that only for shared accounts?
(next point in next message)
Posted On: 06 Feb 2009 09:39 AM
We keep daily/weekly/ and monthly in our shared servers. On vps in whm you can configure it to create backups of your accounts in regular intervals. We also keep backups of the vps's on our nas servers but those backups normally run every 3 or 4 days.
Posted On: 06 Feb 2009 09:50 AM
but please tell me why when I put "Y" in there I destroyed the whole thing
why isnt' there way to reverse that setting?
... coz i'm very confused over what just happened
thanks if u can take time to tell me (now i'm still downloading files)
Posted On: 06 Feb 2009 10:05 AM
You broke your apache doing something.

Warning: DocumentRoot [/home/hodfghoo/public_html/hofghfghned] does not exist

i saw that you made alterations to php.ini You also made changes to apache witch is why the script is not working
I could restore these however before you altered them you did not make any backups of their current version.
I have no way of really knowing what is wrong. Its starting to look like to repair your server were going to need to restore the backup of the entire server from our nas locations.

Let us know if you would like us to proceed.
Posted On: 06 Feb 2009 10:17 AM
(now I'm still downloading some backup in order to see what i can save of the previous script)
so no need to restore yet
but if that can help to understand:
there's only 1 thing that I did,

in WHM/ Main >> Service Configuration >> PHP Configuration Editor (advanced)
Session Handling session.save_path

setting was N;/path **DEFAULT**, Click to Edit (with a line crossing the N;/path)
and I clicked on it and changed it to Y;/path

That's all I did...
but when i tried to put it back to N;/path, the whole site was still out
... does that help you understand what happened?
or is that unrelated?
Posted On: 06 Feb 2009 10:35 AM
I understand that this is what broke it. However fixing it is not going to be simple as trying to undo the change you made. Scripts are sensitive and when your script found that there was a different modifier for the session save variable, it began, it appears, trying to use that.
That is just my opinoin, im not a script coder or learned in php, just an educated guess.
In order to get the script to run again more than likely its going to need to be reloaded. Let us know when you want us to start working on it.
My advice would be to have us restore httpd.conf ( apache ) php.ini and the public_html of your domain from one of the backups from before the alterations where made.
Posted On: 06 Feb 2009 10:51 AM
yes please try that first
thanks a lot
Posted On: 06 Feb 2009 01:27 PM
sorry, I was wondering why I don't get replies anymore
Posted On: 06 Feb 2009 03:20 PM

Extracting the requested configuration files from NAS backup now (although these might not be necessary, cPanel keeps versioned copies of both files). We'll let you know once this is complete.

Posted On: 06 Feb 2009 03:31 PM

Both httpd.conf and php.ini reverted to one earlier revision.


I had to restore httpd.conf to the last revision: in between it looks like you installed (or had installed) suPHP, which requires particular directives to run properly. The 500 error is cured, now.

Posted On: 06 Feb 2009 04:55 PM
thanks a lot really
but please tell me, was it just that "Y" that did it all? next time I try something like that (I'll backup) do you think I should try to edit directly on the file? I mean... was it the interface that bugged and did it? or my "Y" ?
and thanks again

Well, session.save_path should really be set to /tmp. Other than that, I'm not sure why you'd want to change it in the first place (let alone to something starting with a letter, that's not a UNIX-style filesystem path, so it essentially makes it an invalid path).

This website uses Cookies