<html><head><title>Re: [smokeping-users] empty graph for DNS.pm and TCPPing.pm</title>
</head>
<body>
<span style=" font-family:'Courier New'; font-size: 9pt;">+1<br>
<br>
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.<br>
<br>
The problems boil down to;<br>
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. <br>
2) The web-server can't *read* the RRD's because it doesn't have rights.<br>
<br>
[far less common, but the same base issue]<br>
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.<br>
<br>
In short:<br>
Smokeping master/stand-alone uses the smokeping user to write to the RRDs<br>
Smokeping master/stand-alone; web-server user has to *read* the RRD's to produce graphs.<br>
In slave setups, the slaves *write* their data to the RRD's via the web-server user.<br>
<br>
---<br>
Having just skimmed this thread - I will note that it *appears* as though the RRD's _are_ getting written to. <br>
And the complaint is that the web graphs are blank.<br>
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.<br>
<br>
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<br>
<br>
If that doesn't resolve things - and you're sure you've got it right...<br>
<br>
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.]<br>
<br>
-Greg<br>
<br>
<span style=" color: #800000;"><b>GF> hmm I don't see any indication that probing has any issue in your output.<br>
<br>
GF> I'm also not sure what you mean by "BEFORE fix" and "AFTER fix". what<br>
GF> fix do you mean? and does the fix make things work?<br>
<br>
GF> otherwise, to pursue things with very general and unguided advice: maybe<br>
GF> the probe is actually able to create rrd files, but then the files are<br>
GF> not accessible to the web interface? check out their permissions to be<br>
GF> sure they let your web interface access them.<br>
<br>
GF> On 2019-02-21 12:32 a.m., Xuefer wrote:<br>
>> i did try --debug but failed to figure out what's wrong. i thought i<br>
>> copied pasted the output, LOL, must have been thinking too many<br>
>> things. here we go:<br>
<br>
>> ====================== BEFORE fix:<br>
>> # chpst -u smokeping smokeping --debug<br>
>> ### assuming you are using an tcpping copy reporting in milliseconds<br>
>> ### assuming you are using an tcpping copy reporting in milliseconds<br>
>> ### parsing /etc/smokeping/fast-cli output... OK (version 0.0.1)<br>
>> Smokeping version 2.006009 successfully launched.<br>
>> Not entering multiprocess mode with '--debug'. Use '--debug-daemon' for that.<br>
>> PingNormal: probing 0 targets with step 300 s and offset 181 s.<br>
>> Curl_fast_com: probing 0 targets with step 1200 s and offset 181 s.<br>
>> Curl_small: probing 0 targets with step 60 s and offset 181 s.<br>
>> PingFreq: probing 1 targets with step 10 s and offset 181 s.<br>
>> PingFreq: forks 5, timeout for each target 181<br>
>> PingFreq: Executing /etc/smokeping/tcpping -C -x 3 58.60.9.21<br>
>> PingFreq: Received: GLOB(0x1bbb6b8)<br>
>> PingFreq: 58.60.9.21: got 7.3530000000e-03 7.3670000000e-03 8.4730000000e-03<br>
>> Calling RRDs::update(/var/lib/smokeping/Global/qq-com.rrd --template<br>
>> uptime:loss:median:ping1:ping2:ping3<br>
>> 1550726988:U:0:7.3670000000e-03:7.3530000000e-03:7.3670000000e-03:8.4730000000e-03)<br>
<br>
>> ====================== AFTER fix:<br>
>> # chpst -u smokeping smokeping --debug<br>
>> ### assuming you are using an tcpping copy reporting in milliseconds<br>
>> ### assuming you are using an tcpping copy reporting in milliseconds<br>
>> ### parsing /etc/smokeping/fast-cli output... OK (version 0.0.1)<br>
>> Smokeping version 2.006009 successfully launched.<br>
>> Not entering multiprocess mode with '--debug'. Use '--debug-daemon' for that.<br>
>> Curl_small: probing 0 targets with step 60 s and offset 212 s.<br>
>> PingFreq: probing 1 targets with step 10 s and offset 212 s.<br>
>> PingNormal: probing 0 targets with step 300 s and offset 212 s.<br>
>> Curl_fast_com: probing 0 targets with step 1200 s and offset 212 s.<br>
>> PingFreq: forks 5, timeout for each target 181<br>
>> PingFreq: Executing /etc/smokeping/tcpping -C -x 3 58.60.9.21<br>
>> PingFreq: Received: GLOB(0x1bba328)<br>
>> PingFreq: 58.60.9.21: got 0.0070280000 0.0073690000 0.0080560000<br>
>> Calling RRDs::update(/var/lib/smokeping/Global/qq-com.rrd --template<br>
>> uptime:loss:median:ping1:ping2:ping3<br>
>> 1550727004:U:0:0.0073690000:0.0070280000:0.0073690000:0.0080560000)<br>
>> ====================== FPing don't need fix:<br>
>> # chpst -u smokeping smokeping --debug<br>
>> ### parsing /etc/smokeping/fast-cli output... OK (version 0.0.1)<br>
>> Smokeping version 2.006009 successfully launched.<br>
>> Not entering multiprocess mode with '--debug'. Use '--debug-daemon' for that.<br>
>> Curl_small: probing 0 targets with step 60 s and offset 292 s.<br>
>> PingNormal: probing 0 targets with step 300 s and offset 292 s.<br>
>> PingFreq: probing 1 targets with step 10 s and offset 292 s.<br>
>> Curl_fast_com: probing 0 targets with step 1200 s and offset 292 s.<br>
>> PingFreq: Executing /etc/smokeping/fping -C 3 -q -B1 -r1 -t60000 -i10 58.60.9.21<br>
>> PingFreq: Got fping output: '58.60.9.21 : 5.91 5.69 8.00'<br>
>> Calling RRDs::update(/var/lib/smokeping/Global/qq-com.rrd --template<br>
>> uptime:loss:median:ping1:ping2:ping3<br>
>> 1550727021:U:0:5.9100000000e-03:5.6900000000e-03:5.9100000000e-03:8.0000000000e-03)<br>
>> ======================<br>
<br>
>> %e a floating-point number, in scientific notation<br>
>> %f a floating-point number, in fixed decimal notation<br>
>> but i suppose rrdtool accept scientific notation<br>
<br>
>> # rrdtool --version<br>
>> RRDtool 1.6.01.6.0 Copyright by Tobias Oetiker <</b></span></span><a style=" font-family:'courier new'; font-size: 9pt;" href="mailto:tobi@oetiker.ch">tobi@oetiker.ch</a><span style=" font-family:'courier new'; font-size: 9pt; color: #800000;"><b>><br>
>> Compiled Feb 7 2019 00:14:34<br>
<br>
>> the above log were reproduced under system: gentoo<br>
>> i can also reproduce it in in openwrt<br>
<br>
>> On Thu, Feb 21, 2019 at 1:14 PM Gabriel Filion <</b></span><a style=" font-family:'courier new'; font-size: 9pt;" href="mailto:gabster@lelutin.ca">gabster@lelutin.ca</a><span style=" font-family:'courier new'; font-size: 9pt; color: #800000;"><b>> wrote:<br>
<br>
>>> On 2019-02-21 12:12 a.m., Gabriel Filion wrote:<br>
>>>> On 2019-02-20 12:52 p.m., Xuefer wrote:<br>
>>>>> FPing.pm works fine but DNS and TCPPing is producing empty graph. i<br>
>>>>> failed to find the actual clause since i'm not a perl guy, but i<br>
>>>>> manage to workaround it by changnig "%.10e" into ".10f", can any<br>
>>>>> developer take a look into this?<br>
<br>
>>>> you should start smokeping with the --daemon argument to get more<br>
<br>
>>> oops sorry I'm too tired to type :\ that should have been --debug (not<br>
>>> --daemon)<br>
<br>
>>>> information. it'll show you what commands it's running, but also the<br>
>>>> probe binary's output if it's erroring out.<br>
</body></html>