Xymon Mailing List Archive search

rrd file will not recreate

3 messages in this thread

list Paul Root · Wed, 18 Apr 2018 18:32:42 +0000 ·
Hi all,
                I'm writing a custom script to monitor a group of run away java scripts memory hog.

                Anyway, I'm trying to create a graph, which I'm never good at.

                Anyway, the rrd file was created immediately, when I first put in the entry to TEST2RRD and a NCV_Testname line in xymonserver.cfg.

                A couple of iterations of the data,  changing names etc. I deleted the rrd file (which was updating some data), killed the rrd processes to the xymon server. It didn't recreate the file. So I restarted xymon completely on the server.

                All I could think of is a process holding on to that old file.

                So does anyone know the magic to get an RRD file to recreate on the server?

                BTW, a second server that also has the test, does have the rrd file, and it updates the current data, but no historical data.

Thanks
Paul.

Paul Root
Lead Engineer
XXX Commerce Dr
Woodbury, Mn 55125
XXX-XXX-XXXX
user-76fdb6883669@xymon.invalid

This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
list Jeremy Laidman · Fri, 20 Apr 2018 10:15:32 +1000 ·
Try using this magic incantation of lsof:

sudo lsof -nP +L1

This will list all filenames that have been deleted but have filehandles
still being held open by a process. The "+L1" means to show all files with
a link count less than 1. Deleted files have a link count of zero.

However, I suspect this cannot be your problem, because a new xymond_rrd
process would simply create a new file with the same filename. A
deleted-but-still-present file has no filename on the filesystem and so
cannot block the creation of a new file with the same name.

Cheers
Jeremy
quoted from Paul Root


On 19 April 2018 at 04:32, Root, Paul T <user-76fdb6883669@xymon.invalid> wrote:
Hi all,

                I’m writing a custom script to monitor a group of run
away java scripts memory hog.


                Anyway, I’m trying to create a graph, which I’m never
good at.


                Anyway, the rrd file was created immediately, when I
first put in the entry to TEST2RRD and a NCV_Testname line in
xymonserver.cfg.


                A couple of iterations of the data,  changing names etc.
I deleted the rrd file (which was updating some data), killed the rrd
processes to the xymon server. It didn’t recreate the file. So I restarted
xymon completely on the server.


                All I could think of is a process holding on to that old
file.


                So does anyone know the magic to get an RRD file to
recreate on the server?


                BTW, a second server that also has the test, does have
the rrd file, and it updates the current data, but no historical data.


Thanks

Paul.


Paul Root

Lead Engineer

XXX Commerce Dr

Woodbury, Mn 55125

XXX-XXX-XXXX

user-76fdb6883669@xymon.invalid


This communication is the property of CenturyLink and may contain
confidential or privileged information. Unauthorized use of this
communication is strictly prohibited and may be unlawful. If you have
received this communication in error, please immediately notify the sender
by reply e-mail and destroy all copies of the communication and any
attachments.

list Paul Root · Fri, 20 Apr 2018 00:33:37 +0000 ·
Yeah, that was a good idea. But it wasn’t there.

I’ll keep looking.
quoted from Jeremy Laidman


From: Jeremy Laidman <user-0608abae5e7c@xymon.invalid>
Sent: Thursday, April 19, 2018 7:16 PM
To: Root, Paul T <user-76fdb6883669@xymon.invalid>
Cc: xymon at xymon.com
Subject: Re: [Xymon] rrd file will not recreate

Try using this magic incantation of lsof:

sudo lsof -nP +L1

This will list all filenames that have been deleted but have filehandles still being held open by a process. The "+L1" means to show all files with a link count less than 1. Deleted files have a link count of zero.

However, I suspect this cannot be your problem, because a new xymond_rrd process would simply create a new file with the same filename. A deleted-but-still-present file has no filename on the filesystem and so cannot block the creation of a new file with the same name.

Cheers
Jeremy


On 19 April 2018 at 04:32, Root, Paul T <user-76fdb6883669@xymon.invalid<mailto:user-76fdb6883669@xymon.invalid>> wrote:
Hi all,
                I’m writing a custom script to monitor a group of run away java scripts memory hog.

                Anyway, I’m trying to create a graph, which I’m never good at.

                Anyway, the rrd file was created immediately, when I first put in the entry to TEST2RRD and a NCV_Testname line in xymonserver.cfg.

                A couple of iterations of the data,  changing names etc. I deleted the rrd file (which was updating some data), killed the rrd processes to the xymon server. It didn’t recreate the file. So I restarted xymon completely on the server.

                All I could think of is a process holding on to that old file.

                So does anyone know the magic to get an RRD file to recreate on the server?

                BTW, a second server that also has the test, does have the rrd file, and it updates the current data, but no historical data.

Thanks
Paul.

Paul Root
Lead Engineer
XXX Commerce Dr
Woodbury, Mn 55125
XXX-XXX-XXXX

user-76fdb6883669@xymon.invalid<mailto:user-76fdb6883669@xymon.invalid>
quoted from Jeremy Laidman

This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.


This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.