I had a perfectly functional GoDaddy website (under development) before Christmas break. It has not been changed. Today, I logged on and I have all these strange errors regarding sessions that weren't there before.

在圣诞节之前，我有一个功能完善的谷歌爸爸网站(正在开发中)。它没有被改变。今天，我登录了，我遇到了所有关于以前没有的会话的奇怪错误。

To investigate, I made a new file and threw it on the site with the contents:

为了进行调查，我制作了一个新文件，并将其与内容一起放在网站上：

<?PHP
    session_start();
    echo "HELLO WORLD!";
?>

Navigating to this page in a freshly opened browser gives the following output:

在新打开的浏览器中导航到此页面会显示以下输出：

Warning: session_start() [function.session-start]: open(/var/chroot/home/content/05/8547705/tmp/sess_m3uikb1qe6v5hsjir8ilsfa811, O_RDWR) failed: Permission denied (13) in /home/content/05/8547705/html/try.php on line 2

Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at /home/content/05/8547705/html/try.php:2) in /home/content/05/8547705/html/try.php on line 2

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/content/05/8547705/html/try.php:2) in /home/content/05/8547705/html/try.php on line 2
HELLO WORLD!
Warning: Unknown: open(/var/chroot/home/content/05/8547705/tmp/sess_m3uikb1qe6v5hsjir8ilsfa811, O_RDWR) failed: Permission denied (13) 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 () in Unknown on line 0

I don't even know where to start with this - does anyone know what could have changed to make this basic file not work?

我甚至不知道从哪里开始--有人知道是什么原因导致这个基本文件无法工作吗？

Haven't seen the first warning, but the others happen if the script sends headers or data before the call to session_start(). You can fix that by either:

我没有看到第一个警告，但如果脚本在调用Session_Start()之前发送标头或数据，则会出现其他警告。您可以通过以下任一方式进行修复：

1) making sure that there's no HTML or whitespace before session_start(), or,
2) using output buffering (see ob_start() and ob_end_flush().

1)确保SESSION_START()之前没有HTML或空格，或者，2)使用输出缓冲(参见ob_start()和ob_end_flush())。

With (2) you can start the session anytime during script execution; the buffering makes sure headers and response data are sent to the browser in the right order.

使用(2)可以在脚本执行期间的任何时间启动会话；缓冲确保头和响应数据以正确的顺序发送到浏览器。

Get rid of any white space before session_start()

在SESSION_START()之前清除所有空格

I know this post is very old, but maybe this will help someone.
I was getting the same type session errors. The session path in the errmsg did not exist. Yet, the session path in the CPanel configuration existed.
If you've had a old website at godaddy that's been migrated or updated to CPanel, you may have an old .user.ini file that is incorrectly setting the path for session that will conflict/override the one you can specify in CPanel.
Suggest commenting out the one in .user.ini and using the one in Cpanel.
The problem can also happen when you change versions of PHP as the session save path may have the php version in it. That is why you want to use the one in CPanel.
Probably good idea to examine the other settings in .user.ini and remove ones that are no longer necessary/can be set in CP.

我知道这篇文章很老了，但也许这篇文章会对某些人有所帮助。我收到了相同类型的会话错误。Errmsg中的会话路径不存在。然而，cPanel配置中的会话路径仍然存在。如果你有一个已经迁移或更新到cPanel的旧网站，你可能有一个旧的.user.ini文件，它错误地设置了会话的路径，这将冲突/覆盖你可以在cPanel中指定的路径。建议注释掉.user.ini中的那个，并使用Cpanel中的那个。当你改变php的版本时，这个问题也会发生，因为会话保存路径中可能有php版本。这就是为什么要使用cPanel中的那个。检查.user.ini中的其他设置并删除不再需要/可以在CP中设置的设置可能是个好主意。