It sounds to me like it's working right.

Rancid will update the timestamp on the file on a successful run, but will only commit changes that it find into the repository. If it doesn't find a change, it won't commit a new version.

If there are ports going up and down (but no actual administrative configuration change), you might see changes to things like vlan membership that will cause a new commit.

Michael

On 6 March 2016 5:45:22 AM AEDT, "Sathish.I" sathish.i@ctrls.in wrote:

Hello All,

I have integrated the rancid with observium. In the initial stage for 2 days it worked well, backup are pulled as per cronjob.

After some days, I observed backup are happening few devices rest are shown in GUI. However, when I checked the status in /var/lib/rancid/observium/configs/ the backup files are successfully taken

And when checked the rancid logs in /var/log/rancid/ I have seen for few devices (which shown in GUI) the

Sending configs/xxxx

Sending configs/yyyy

Transmitting file data ..

Committed revision 216.

NOTE: The list varies from time to time.

Please suggest what could be the issue and solution if any.

Regards,

sathish

---

---

observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium