Index: [Article Count Order] [Thread]

Date:  Sat, 3 Mar 2007 08:16:27 -0800
From:  "Adam Crews" <adam.crews (at mark) gmail.com>
Subject:  [coba-e:08980] Re: /var/lock/subsys/proftpd': Read-only file system
To:  coba-e (at mark) bluequartz.org
Message-Id:  <1486c6440703030816q21795bc0xf2414070dd6ec3f3 (at mark) mail.gmail.com>
In-Reply-To:  <45E98C84.8060400 (at mark) ontarioweb.ca>
References:  <057501c75d2a$50d31990$0601a8c0 (at mark) systemax>	 <45E98C84.8060400 (at mark) ontarioweb.ca>
X-Mail-Count: 08980

Run the command "mount"  without any arguments and look for a "ro"
(read only) file system.

If you find any then run dmesg, or look in /var/log/messages for clues
to why the filesystem was marked read only.

If the kernel detects an error on the file system, it will sometimes
mark it as read-only to prevent damage to the files.  This could
indicate a failing disk, or dirty file system.  dmesg or
/var/log/messages should help determine what is happening.

-Adam

On 3/3/07, Jon McCauley <jmccauley (at mark) ontarioweb.ca> wrote:
> Gerald Waugh wrote:
> > You wrote;
> >
> >  Hello everyone,
> >
> >> Today I had an power outage that the battery backups where
> >> not able to
> >> keep all the BQ servers running.
> >>
> >> I now have a name server that is reporting "The FTP server is
> >> not running", I have tried to restart from CLI and GUI and no luck.
> >>
> >>  #> proftpd -n -d9
> >> [root@ns1 log]# proftpd -n -d9
> >>
> >> ns1.domain.com - opening scoreboard
> >> '/var/run/proftpd/proftpd.scoreboard'
> >> ns1.domain.com - RELINQUISH PRIVS at main.c:2262
> >> ns1.domain.com - error opening scoreboard: Read-only file system
> >>
> >>
> >> [root (at mark) ns1 log]# /etc/init.d/proftpd restart
> >> Shutting down proftpd:                                     [FAILED]
> >> Starting proftpd:                                          [  OK  ]
> >> touch: cannot touch `/var/lock/subsys/proftpd': Read-only file system
> >>
> >> Any help would be appreciated as I am nervous to reboot
> >>
> >
> > Are you not running proftpd from xinetd???
> > Which is the standard method...
> > If so;
> >       /etc/rc.d/init.d/xinetd restart
> >
> > Gerald
> >
> Hi Gerald,
> My mistake....but when I run xinetd I still receive a read only error
>
> [root (at mark) ns1 ~]# /etc/rc.d/init.d/xinetd restart
> rm: cannot remove `/var/run/xinetd.pid': Read-only file systemOK  ]
>
> rm: cannot remove `/var/lock/subsys/xinetd': Read-only file system
> Starting xinetd:                                           [  OK  ]
> touch: cannot touch `/var/lock/subsys/xinetd': Read-only file system
>
>
> >
> >
>
>


-- 
-----------------------------------------------------------------
Shroom.net Donation Based Web Hosting
http://www.shroom.net/
-----------------------------------------------------------------