Possibly the NFS server was set to use LDAP or some other authentication
method? Dose the NFS serer have a same uid/gid user account as the
hobbit account on the monitoring server? Is the NFS set up to allow
"777" and root-level permissions for the monitoring server (when
accessing the NFS share)? This is starting to sound more and more like
an NFS authentication conflict.
Dean
-----Original Message-----
From: Robin Wood [mailto:dninja (at) gmail.com]
Sent: Monday, June 25, 2007 12:59 PM
To: hobbit (at) hswn.dk
Subject: Re: [hobbit] I'm getting the error "could not lock RRD"
Hobbit definitely wasn't being ran as root and the rrd directories
were created either by hobbit or by the install script. The version
I'm running at the moment is on a test system, when I roll it out to
the new live box I'll see if it happens again.
Robin
On 6/25/07, Galen Johnson <Galen.Johnson (at) sas.com> wrote:
> I thought the hobbit startup script already checked for being run as
root (I know if I try to run as root it tells me to run it as the hobbit
user)...unless it was configured to do so at compile time. NFS
generally can't handle being updated as root unless you explicitly
configure the server to allow it in the mount config (this varies from
system to system so check out the manpage). This would explain the
behavior you're seeing when running hobbiut as root.
>
> =G=
>
> -----Original Message-----
> From: Dean Casey [mailto:dcasey (at) pathfire.com]
> Sent: Monday, June 25, 2007 10:44 AM
> To: hobbit (at) hswn.dk
> Subject: RE: [hobbit] I'm getting the error "could not lock RRD"
>
> Seymour makes a good point. I also get similar errors when running
Hobbit as root... doing that often changes file permissions and "breaks"
> Hobbit afterward.
>
> The solution was to set up a very simple startup file that looks
something like this (on RedHat, other Linuxes will vary but should be
pretty close), based on the old BB startup script:
>
> ###
> ###
> #!/bin/bash
> #
> # hobbit-server This shell script takes care of starting and
stopping
> # hobbit monitoring server.
> #
> # chkconfig: - 99 45
> # description: Hobbit monitoring server is\ # used to monitor
Pathfire's systems.
> # probe: true
>
> # Source function library.
> . /etc/rc.d/init.d/functions
>
> # Source networking configuration.
> . /etc/sysconfig/network
>
> # Check that networking is up.
> [ "${NETWORKING}" = "no" ] && exit 0
>
>
> PATH=$PATH:/bin:/usr/bin # FOR su
> BBHOME=/home/hobbit
> BBUSER=hobbit
>
> case "$1" in
> start)
> su - $BBUSER -c "cd $BBHOME;./server/hobbit.sh start"
> ;;
> restart)
> su - $BBUSER -c "cd $BBHOME;./server/hobbit.sh restart"
> ;;
> stop)
> su - $BBUSER -c "cd $BBHOME;./server/hobbit.sh stop"
> ;;
> status)
> su - $BBUSER -c "cd $BBHOME;./server/hobbit.sh status"
> ;;
> *)
> echo "Usage: $0 {start|stop|restart|status}"
> exit 1
> ;;
> esac
>
> exit 0
> ###
> ###
>
> I then set permissions on the startup file so:
> -rwxr-xr-x 1 root root 954 Jun 19 11:49 hobbit-server
>
> I then ran:
> "chkconfig --345 hobbit-server on"
>
>
> Now, on RedHat, I can run hobbit server without worrying about "su -
hobbit" first, using commands:
> "service hobbit-server (start|stop|restart|status)"
>
>
> You can do something similar for the hobbit client on RedHat or other
Linux variants. Solaris would use a truncated version of this startup
script.
>
> Dean Casey
>
>
> -----Original Message-----
> From: Brown, Seymour [mailto:Seymour.Brown (at) WJMC.ORG]
> Sent: Monday, June 25, 2007 10:19 AM
> To: hobbit (at) hswn.dk
> Subject: RE: [hobbit] I'm getting the error "could not lock RRD"
>
> Indeed, we get this when something in our MRTG process gets an error,
and the rrd data files then become owned by root instead of hobbit. We
also get it if we start hobbit as root instead of hobbit. I think the
lock is a red herring - it simply could not open the file.
>
> My fix has been to do cd /var/lib/hobbit/rrd (or wherever you keep
your rrd data) and then chown hobbit * -R
>
> As far as the MRTG causing it, the MRTG logs generally point the way.
>
> The key seems to be to configure and operate hobbit as the hobbit
user.
>
> =Seymour=
>
> Seymour J. Brown
> Network Analyst
> CCNA, CFS, CWNA, Network+
> West Jefferson Medical Center
> 1101 Medical Center Blvd.
> Marrero, LA 70072
> 504-349-2396
>
>
> -----Original Message-----
> From: Dean Casey [mailto:dcasey (at) pathfire.com]
> Sent: Saturday, June 23, 2007 12:08 AM
> To: hobbit (at) hswn.dk
> Subject: RE: [hobbit] I'm getting the error "could not lock RRD"
>
> I've seen this rrd error in the past when rrd libraries, binaries, or
data files had incorrect permissions or were missing (unavailable).
>
> Dean Casey
>
>
>
> -----Original Message-----
> From: Robin Wood [mailto:dninja (at) gmail.com]
> Sent: Friday, June 22, 2007 4:59 PM
> To: hobbit (at) hswn.dk
> Subject: Re: [hobbit] I'm getting the error "could not lock RRD"
>
> Hi
> The directory is a nfs share. I'll try moving the data directory to a
local disk and see if that fixes it.
>
> Robin
>
> On 6/22/07, Henrik Stoerner <henrik (at) hswn.dk> wrote:
> > On Fri, Jun 22, 2007 at 07:27:27PM +0100, Robin Wood wrote:
> > > 2007-06-22 19:24:55 RRD error updating
> > > /var/sites/hobbit/non-secure//data/rrd/xxx/procs.rrd from
> 192.168.0.2:
> > > could not lock RRD
> >
> > It's an error from the rrdtool library. I honestly have no idea what
> > could be causing this.
> >
> > Is the /var/sites/hobbit/non-secure//data/rrd an NFS filesystem?
> > Perhaps there's some issue with locking on networked filsystems.
> >
> >
> > Regards,
> > Henrik
> >
> >
> > To unsubscribe from the hobbit list, send an e-mail to
> > hobbit-unsubscribe (at) hswn.dk
> >
> >
> >
>
> To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk
>
>
>
> To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk
>
>
>
>
> This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you should
not disseminate, distribute or copy this e-mail. Please notify the
sender immediately by e-mail if you have received this e-mail by mistake
and delete this e-mail from your system. E-mail transmission cannot be
guaranteed to be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
contain viruses. The sender therefore does not accept liability for any
errors or omissions in the contents of this message, which arise as a
result of e-mail transmission. If verification is required please
request a hard-copy version. West Jefferson Medical Center, 1101 Medical
Center Blvd., Marrero, USA, www.wjmc.org.
>
> To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk
>
>
>
> To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk
>
>
>
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe (at) hswn.dk
>
>
>
To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk
To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk