Re: dnscache: readproctitle service errors
On 5/21/05, Jacob S <stormspotter@6texans.net> wrote:
> On Sat, 21 May 2005 18:10:01 +0200
> Jacob Friis Larsen <webcom.dk@gmail.com> wrote:
> > On 5/21/05, Jacob S <stormspotter@6texans.net> wrote:
> > > On Sat, 21 May 2005 15:47:23 +0200
> > > Jacob Friis Larsen <webcom.dk@gmail.com> wrote:
> > > > On 5/20/05, Jacob S <stormspotter@6texans.net> wrote:
> > > > > On Fri, 20 May 2005 16:06:19 +0200
> > > > > Jacob Friis Larsen <webcom.dk@gmail.com> wrote:
> > > > > > On 5/20/05, Jacob S <stormspotter@6texans.net> wrote:
> > > > > > > On Fri, 20 May 2005 09:13:29 +0200
> > > > > > > Jacob Friis Larsen <webcom.dk@gmail.com> wrote:
> > > > > > >
> > > > > > > > > > Anyone know what I should do to fix this:
> > > > > > > > > >
> > > > > > > > > > root 878 0.0 0.0 1352 20 ? S
> > > > > > > > > > Feb25 0:00 \_ readproctitle service errors: ...:
> > > > > > > > > > warning: unable to wri te to ./main/current, pausing:
> > > > > > > > > > out of disk space?multilog: warning: unable to write
> > > > > > > > > > to ./main/current, pausing: out of disk sp
> > > > > > > > > > ace?multilog: warning: unable to write to
> > > > > > > > > > ./main/current, pausing: out of disk space?multilog:
> > > > > > > > > > warning: unable to write to ./m ain/current, pausing:
> > > > > > > > > > out of disk space?multilog: warning: unable to write
> > > > > > > > > > to ./main/current, pausing: out of disk space?
>
> > > It sounds like the errors are from a previous problem then. Try
> > > running the following:
> > >
> > > kill `pidof readproctitle`
> > > kill `pidof svscan`
> > >
> > > Then "ps ax | grep readproctitle" should look better.
> >
> > # kill `pidof readproctitle`
> > # kill `pidof svscan`
> > # ps ax | grep readproctitle
> > 11728 ? S 0:00 readproctitle service errors:
> > .....................................................................
> > .....................................................................
> > .....................................................................
> > ........................................supervise: fatal: unable to
> > acquire dnscache/supervise/lock: temporary failure?supervise: fatal:
> > unable to acquire log/supervise/lock: temporary failure?
> > 11764 pts/0 S+ 0:00 grep readproctitle
>
> Yes, mine did the same thing when I tested the kill commands. I think it
> is just dnscache complaining because svscan and readproctitle went down.
>
> To test it, wait 5 minutes or so (plenty long enough by the time you get
> this e-mail :-) and do another "ps ax | grep readproctitle" to make sure
> the errors aren't growing.
They don't seem to be growing.
$ ps ax | grep readproctitle
11728 ? S 0:00 readproctitle service errors:
.......................................................................................................................................................................................................................................................supervise:
fatal: unable to acquire dnscache/supervise/lock: temporary
failure?supervise: fatal: unable to acquire log/supervise/lock:
temporary failure?
27182 pts/0 S+ 0:00 grep readproctitle
Reply to: