Hmm I tried deleting a particular rrd file, for instance netscaler-stats-tcp.rrd file and letting the system re-create?   Error temporarily changed to the file not existing but ultimately still in the same spot with the Unable to parse header `DSName'.  After it recreated it on the next cycle.

 

Something else?

 

Thanks,

 

 

----------------------------
This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient of this e-mail (even if the e-mail address above is yours), (i) you may not use, copy or retransmit it, (ii) please delete this message and (iii) please notify the sender immediately. Any disclosure, copying, or distribution of this message or the taking of any action based on it, is strictly prohibited.
----------------------------

From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong
Sent: Friday, March 03, 2017 11:57 AM
To: observium@observium.org
Subject: Re: [Observium] Unable to parse header `DSName' rrdtool

 

This is likely because your rrd local files are corrupted.

 

adam.

On 03/03/2017 16:52:05, Sam Hernandez-gill <sam.hernandez-gill@qvc.com> wrote:

I have a few different rrdtool graphs that are outputting “RRDTool Output: ERROR: rrdc_fetch: Unable to parse header `DSName'”

 

So far I’ve only noticed it on specific Citrix Netscaler graphs, the Netscaler SSL ones nsSslHandshakes, nsSslSessions, etc and TCP Connections and TCP Packets for the netscalers are all in the same state with Unable to parse header `DSName'.

 

 

Sadly I didn’t notice when, I did recently upgrade to revision 8417, however these aren’t graphs I frequently look at.  Anybody else with netscalers in their environment at the same revision?

Thanks,
Sam

 

 

 

----------------------------
This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient of this e-mail (even if the e-mail address above is yours), (i) you may not use, copy or retransmit it, (ii) please delete this message and (iii) please notify the sender immediately. Any disclosure, copying, or distribution of this message or the taking of any action based on it, is strictly prohibited.
----------------------------