Internal Server Error

[sircolin]

I have just received this error nothing has changed in the last week or so, and no reboot has been done.

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, root and inform them of the time the error occurred, and anything you might have done that may have caused the error.
[24135]ERR: 24: Error in Perl code: Could not open dbm file /var/lib/libapache-sessionx-perl/DB_File/sessions.db: Read-only file system at /usr/share/perl5/Apache/Session/Store/DB_File.pm line 32.
Apache Embperl 2.2.0 [Sun Aug 29 22:54:57 2010]

also on other machines

jtablesession::Store Failed
DB function failed with error number 126
Incorrect key file for table './joomla/jos_session.MYI'; try to repair it SQL=INSERT INTO `jos_session` ( `session_id`,`time`,`username`,`gid`,`guest`,`client_id` ) VALUES ( 'e35f1978bf79b6a0dba7938aaf9b4e07','1283118629','','0','1','0' )

I also when i issue

# shorewall restart

i see

Compiling...
mktemp: cannot make temp dir /tmp/shorewall.afBjiv: Read-only file system
ERROR: Can't create a temporary directory

Im running proxmox 2.6.24-11-pve

 

[dietmar]

Why is your file system 'read-only'? Any hint in 'dmesg'?

 

[sircolin]

It looks like there was errors on the disk, i rebooted into the Vkvm, the system started to boot and then forced a disk check once finished i rebooted again to the hd and things are back to normal it seems.

md: md1 stopped.
md: bind<sdb1>
md: bind<sda1>
raid1: raid set md1 active with 2 out of 2 mirrors
md: md6 stopped.
md: bind<sdb6>
md: bind<sda6>
md6: setting max_sectors to 128, segment boundary to 32767
raid0: looking at sda6
raid0: comparing sda6(939894912) with sda6(939894912)
raid0: END
raid0: ==> UNIQUE
raid0: 1 zones
raid0: looking at sdb6
raid0: comparing sdb6(939894912) with sda6(939894912)
raid0: EQUAL
raid0: FINAL 1 zones
raid0: done.
raid0 : md_size is 1879789824 blocks.
raid0 : conf->hash_spacing is 1879789824 blocks.
raid0 : nb_zone is 1.
raid0 : Allocating 8 bytes for hash.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: md6: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 74637895
ext3_orphan_cleanup: deleting unreferenced inode 76965671
ext3_orphan_cleanup: deleting unreferenced inode 76965670
ext3_orphan_cleanup: deleting unreferenced inode 76965669
ext3_orphan_cleanup: deleting unreferenced inode 76964324
ext3_orphan_cleanup: deleting unreferenced inode 76964201
EXT3-fs: md6: 60 orphan inodes deleted
EXT3-fs: recovery complete.

Col

 

[sircolin]

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, root and inform them of the time the error occurred, and anything you might have done that may have caused the error.
[24304]ERR: 24: Error in Perl code: Could not open dbm file /var/lib/libapache-sessionx-perl/DB_File/sessions.db: Read-only file system at /usr/share/perl5/Apache/Session/Store/DB_File.pm line 32.
Apache Embperl 2.2.0 [Wed Sep 1 15:22:53 2010]

Ok were back here again i will start to run a full disk check as soon as my data has been move off site, any comments as to what could be causes this.

 

[dietmar]

any comments as to what could be causes this.

A damaged harddisk? If so, there should be a hint in syslog.

 

[sircolin]

could not find anything in syslog but i have found this in dmesg

md: md1 stopped.
md: bind<sdb1>
md: bind<sda1>
raid1: raid set md1 active with 2 out of 2 mirrors
md: md6 stopped.
md: bind<sdb6>
md: bind<sda6>
md6: setting max_sectors to 128, segment boundary to 32767
raid0: looking at sda6
raid0: comparing sda6(939894912) with sda6(939894912)
raid0: END
raid0: ==> UNIQUE
raid0: 1 zones
raid0: looking at sdb6
raid0: comparing sdb6(939894912) with sda6(939894912)
raid0: EQUAL
raid0: FINAL 1 zones
raid0: done.
raid0 : md_size is 1879789824 blocks.
raid0 : conf->hash_spacing is 1879789824 blocks.
raid0 : nb_zone is 1.
raid0 : Allocating 8 bytes for hash.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds

im not sure if this is from the disk cleanup two days ago i guess not.
im am gearing up to do a disk check then a reinstall if needed.

but i have a feeling this is due to ovh forcing the boot partion to be on a raid1 and my file sysytem i have put on raid0 and some related errors in unallocated space i saw when installing i will try to install debian lenny and the proxmox on top in a supported manner via kvm. im just not sure about how to add the second disk without raid.

 

[Teflonpo]

I have the same problems.

[5408]ERR: 24: Error in Perl code: Could not open dbm file /var/lib/libapache-sessionx-perl/DB_File/sessions.db: Permission denied at /usr/share/perl5/Apache/Session/Store/DB_File.pm line 32.

 

[dietmar]

I have the same problems.

what is the output of:

# ls -l /var/lib/libapache-sessionx-perl/DB_File/sessions.db

 

[Teflonpo]

Indeed I saw my mistake. I did chown www-data /var/lib/libapache-sessionx-perl/DB_File/sessions.db
It works