<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">This really looks like a permissions issue, but I just can’t find it. In desperation, I made all the red files and directories that hold them 777, just to see what would happen. It did not change anything. <div class=""><br class=""></div><div class="">It is almost like the process that moves the data from the slave.cache files into the rrd file is not running. If I reboot the master, all the backlogged slave_cache data is added to the rrd and you can see it on the graphs.</div><div class=""><br class=""></div><div class="">Really is a crazy thing with the secrets file, the error is on the slave, not the master.</div><div class=""><br class=""></div><div class="">I will can the whole thing and restart from scratch if I can’t get it fixed by noon tomorrow. </div><div class=""><br class=""></div><div class=""><br class=""><div class="">
~KEM</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On Jun 1, 2016, at 15:44, Gregory Sloop <<a href="mailto:gregs@sloop.net" class="">gregs@sloop.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><title class="">Re: [smokeping-users] RRD files being created, but the graphs are not updating</title>
<div class="">
<br class=""><br class="">
<table class="">
<tbody class=""><tr class="">
<td width="2" bgcolor="#0000ff" class=""><br class="">
</td>
<td class=""><span style=" font-family:'courier new'; font-size: 9pt;" class="">This was a working distributed environment with 8 slaves, all running on 14.04 with smokeping 2.006008.<br class="">
<br class="">
Had a reboot of the smokeping master this am and have had crazy problems ever since. As part of the troubleshooting for this, we upgraded the master to 2.006011<br class="">
<br class="">
Cannot display graphs, even the master tests. In the directories, the .slave_cache files are being created. But, the corresponding rrd files are not being updated. <br class="">
<br class="">
The smokeping_secrets file is really strange now. Before it was 600 smokeping:smokeping and everything worked. After the update, once the master process is up, I have to set it to 640 smokeping:www-data to get the slaves to connect. Otherwise I get this error on the slave:<br class="">
<br class="">
<b class="">* Starting latency logger daemon smokeping<br class="">
WARNING: Opening secrets file /etc/smokeping/smokeping_secrets: Permission denied<br class="">
<br class="">
ERROR: we did not get config from the master. Maybe we are not configured as a slave for any of the targets on the master ?<br class="">
...done.<br class="">
<br class="">
</b>Any ideas what is going on, or where I can look? The lack of graphs from the master is really confusing<br class="">
<br class="">
Apache is Apache/2.4.7<br class="">
RRDTool is 1.5.5</span></td>
</tr>
</tbody></table>
<br class=""><br class="">
<span style=" font-family:'Courier New'; font-size: 9pt;" class="">It sounds like a permissions issue.<br class="">
How much time have you spent trying to make sure permissions are correct?<br class="">
<br class="">
[It sounds like you know what you're doing, but this is a common issue and virtually always it runs down as a permission issue. My apologies if that doesn't fit your case, but it sure sounds likely.]<br class="">
<br class="">
The master RRD's need to be able to write to the files/directory as whomever smokeping is running as.<br class="">
The slave RRD's need to be writeable as whatever web-server you're using is running as. [Apache]<br class="">
[To *write* the data from smokeping/fping et al.]<br class="">
<br class="">
Both need read access for the web-server/apache. [To *display* the graph data.]<br class="">
<br class="">
I don't recall exactly what users those typically are for Ubuntu 14 - but double check.<br class="">
<br class="">
---<br class="">
Quick, note if the RRD's are getting their time-stamps updated as new data should get written. If not, you've got a write problem.<br class="">
If they are, you've got a read problem.<br class="">
<br class="">
I have no idea why the permissions would have changed though.<br class="">
<br class="">
-Greg<br class=""><br class=""></span></div></div></blockquote></div><br class=""></div></body></html>