Page 1 of 1

Errors on Session Start

Posted: 14 Jan 2012, 23:29
by Bob Hunter
I just moved my gallery on Godaddy to a different server, and the gallery doesn't work. I put 777 permissions on the content, admin, IV-includes. When I log into the gallery, I get:
Warning: session_start() [function.session-start]: open(/var/chroot/home/content/97/4314097/tmp/sess_d1ce6v732trqugctonebiff2j0, O_RDWR) failed: No such file or directory (2) in /home/content/97/4314097/html/vue1/admin/index.php on line 30
You can see the error at http://littletsquares.com/vue1/admin/.

Any idea on how to fix this?

Thanks,

Bob

Re: Errors on Session Start

Posted: 15 Jan 2012, 03:40
by Nick
You need to create this folder: /var/chroot/home/content/97/4314097/tmp/

It is probably /tmp in your root folder on the same level as /html folder where you keep your html stuff. This is used by the web server to keep the sessions temporary data. You have deleted it probably or maybe it wasn't there to begin with.

Re: Errors on Session Start

Posted: 15 Jan 2012, 13:03
by Bob Hunter
There was no /tmp directory, so I created it and gave it 777 permissions. Still the same problem :cry:

Could this be some php setting that is different on the new server?

Re: Errors on Session Start

Posted: 16 Jan 2012, 12:55
by Bob Hunter
I also tried reinstalling the imagevue folders and files. Still same problem. These errors ultimately result in the picture gallery menu displaying "Undefined."

Re: Errors on Session Start

Posted: 17 Jan 2012, 11:19
by Nick
I can guarantee that this issue is caused by the missing tmp folder. Could it be that you have created it on the wrong depth? It should be in the same parent folder where the html folder is.

In any case, please contact your hosting support and inform then about the missing folder, they should be able to fix this in no time.

Re: Errors on Session Start

Posted: 17 Jan 2012, 14:06
by Bob Hunter
Turned out there was a file became corrupted in the process of moving the folders and files from one server to another. Godaddy support was able to identify the problem from the logs and fixed it.

Thanks