[smokeping-users] empty graph for DNS.pm and TCPPing.pm

[Xuefer]

the fix is by replacing "%.10e" into ".10f" in TCPPing.pm and it
works, and it is the only thing i change. graph no longer empty using
".10f". i've double check suid permission, and chmod +s o+r `which
tcptraceroute`, fping graph work  without changing anything. i wonder
if anyone can reproduce the problem, i sure can but not able to read
the perl code, let alone tracing the problem down

> +1 I'll just emphasize that the *vast* majority of the problems in smokeping reduce to about two sets of errors - all related to file/directory permissions. The problems boil down to; 1) Smokeping itself [or more clearly, the user smokeping is running as - and remember it may run as root at the CLI, but as something different when started by the system] can't write to the RRDs or the directory where the RRD's are to be stored. 2) The web-server can't *read* the RRD's because it doesn't have rights. [far less common, but the same base issue] 3) In master/slave setups - the slaves [via the web-server] can't write to the RRD's - because the web-server doesn't have rights to the RRDs. In short: Smokeping master/stand-alone uses the smokeping user to write to the RRDs Smokeping master/stand-alone; web-server user has to *read* the RRD's to produce graphs. In slave setups, the slaves *write* their data to the RRD's via the web-server user. --- Having just skimmed this thread - I will note that it *appears* as though the RRD's _are_ getting written to. And the complaint is that the web graphs are blank. So, that almost always points to the user the web-server is running as, as not having the proper rights to read the RRD's. Check the web-server logs. Make sure the RRD's have permissions that will allow the web-server you're using [the user it's running as] to read the RRDs If that doesn't resolve things - and you're sure you've got it right... Search the archives - it seems like someone recently grabbed a tcpping from somewhere on the net [but it might have been one of the other probes - I can't recall] and it wasn't compatible with smokeping, essentially. IIRC, they found the version smokeping was built for, and things started working again. [Sorry for the vague recall, but that's what I've got in my head.] -Greg GF> hmm I don't see any indication that probing has any issue in your output. GF> I'm also not sure what you mean by "BEFORE fix" and "AFTER fix". what GF> fix do you mean? and does the fix make things work? GF> otherwise, to pursue things with very general and unguided advice: maybe GF> the probe is actually able to create rrd files, but then the files are GF> not accessible to the web interface? check out their permissions to be GF> sure they let your web interface access them. tobi at oetiker.ch> gabster at lelutin.ca> wrote: