readonly file system - apache fails to start

Discussion in 'General' started by Toucan, Jul 11, 2013.

  1. Toucan

    Toucan Member

    (Debian Lenny) ISPConfig Slave

    Today, apache2 has gone offline and is refusing to start complaining:
    Restarting web server: apache2rm: cannot remove `/var/run/apache2/*ssl_scache*': Read-only file system
    (30)Read-only file system: apache2: could not open error log file /var/log/apache2/error.log.
    Unable to open logs
    The server is a VM in a datacentre and this is the file system I'm mounted on, so i don't think i'm able to run fsck on it.

    If I open fstab I first get prompted with:
    Error detected while processing /usr/share/vim/vim71/debian.vim:
    line   51:
    E483: Cannot get temp file name
    Press ENTER or type command to continue
    and then see:
    # /etc/fstab: static file system information.
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    proc            /proc           proc    defaults        0       0
    /dev/sda2       /               ext3    errors=remount-ro,usrquota,grpquota 0       1
    # /dev/sdb2     /mnt/oldfs      ext3    ro              0       0
    /dev/sda1       none            swap    sw              0       0
    /dev/hda        /media/cdrom0   udf,iso9660 user,noauto     0       0
    /dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0
    /dev/sda3       /storage        ext3    defaults        0       0
    /var/log/ispconfig/httpd/ /var/www/clients/client0/web183/log    none    bind,nobootwait    0 0
    /var/log/ispconfig/httpd/ /var/www/clients/client19/web137/log    none    bind,nobootwait    0 0
    I've never seen the last two entries in there, so i'm very confused.

    I'd really appreciate some help to get the server back on line again please. I'm not really sure where to start.

  2. till

    till Super Moderator Staff Member ISPConfig Developer

    The last entrys are fine, they get created for each website log dir since ispconfig 3.0.5.
  3. Toucan

    Toucan Member

    Cheers till, looks like the problem was at san level. Emergency maintenance plus an ungraceful shutdown of the vm was to blame.

    More reason for me bringing this server to the home office.

Share This Page