[smokeping-users] Empty graphs after reboot

[Andy Hoogeland]

Good suggestion!

Indeed, when running the service in standard mode, the service shows as
running and owned by user Smokeping; once I started the service in
debug-daemon mode it shows as running and owned by Root...

What is the best way to solve this? Tried to add user smokeping to the root
group but that didn't do the trick yet...

Op 14 okt. 2017 02:34 schreef "Greg Sloop <gregs at sloop.net>" <
gregs at sloop.net>:

> For me this immediately raises the question; what user is the debug being
> run as versus what user is the service being run as.
>
> ...And are you sure the service is actually running, when not in debug
> mode?
>
>
>
> On Oct 13, 2017 3:44 PM, "Andy Hoogeland" <ajh1999 at gmail.com> wrote:
>
>> Hi,
>>
>> Just checked:
>> - in debug-daemon mode smokeping runs normal. Graphs are updated, until
>> reboot or service restart. After that, the previously plotted data is still
>> shown but no more updates. The graph still updates in time.
>> - the .rrd files are still updated, according to the file's timestamp.
>> - the apache2 logs don't show any (recent) errors.
>>
>> Does this help?
>>
>> Op 12 okt. 2017 18:24 schreef "Gregory Sloop" <gregs at sloop.net>:
>>
>>> You're sure the debug showed the RRD's getting updated?
>>> [And the dates on the RRD files are updated? (Second check if the RRD's
>>> are actually getting data.)]
>>>
>>> If they [the RRDs] are getting the data, then it's a *read* problem
>>> getting the data out.
>>> Apache logs would be the place to look then.
>>>
>>> -Greg
>>>
>>>
>>> Thanks for the suggestion!
>>>
>>> The pi doesn't have a hardware clock, so I assume this depends on the
>>> start-up sequence.
>>>
>>> To see if that would be the cause I tried to take Smokeping out of the
>>> boot-up sequence and start it manually after everything started (and the pi
>>> learned the actual time).
>>>
>>> Unfortunately the graphs are still empty.
>>>
>>> Was this a good test to rule this out as the cause of my problem? Or is
>>> there something else I could try...
>>>
>>>
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20171014/3e31d1ca/attachment.html>