testlog_4u, it appears your /tmp directory is mounted read-only. Note the message:
Warning: session_start() [function.session-start]: open(/tmp/sess_37394d8b5a1dd541d59c9f95805df474, O_RDWR) failed: Read-only file system (30)
YOu can check this by studying the output of the mount command. Example:
Code:
root@squash [/usr/local/apache/conf]# mount
/dev/sda1 on / type ext3 (rw,usrquota)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)
none on /dev/shm type tmpfs (rw)
/dev/sda3 on /tmp type ext3 (rw,noexec,nosuid)
/dev/sdb1 on /home34y69da type ext3 (rw,usrquota)
/dev/hda3 on /usr/local type ext3 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
/tmp on /var/tmp type none (rw,noexec,nosuid,bind)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
If [b]/tmp/b] appears like:
/tmp on /var/tmp type none (ro,noexec,nosuid,bind)
with ro in the parentheses (the other items can be ignored for now), then that is your problem. To fix it, this *should* work:
Code:
umount /tmp
mount /tmp
Or you could even simplify it to:
Code:
mount -o remount /tmp
However, the real issue is to know why /tmp is mounted read-only. If your OS did it, it may indicate a failing hard drive. You should be able to find more information in /var/log/dmesg and /var/log/messages. Also check the /tmp entry in /etc/fstab to make certain it's not defined as ro in there.