Error updating could not lock rrd Sex chat camera russian

Posted by / 30-Jan-2017 00:28

Error updating could not lock rrd

I did a fresh install of Free NAS 9.10.1-U3 to a VM with a 32GB boot device and a 50GB hard drive. Saw that "tank" was the system dataset pool and syslog was checked.3. Now the system scrolls tons of these every few seconds: Nov 9 freenas collectd: check_create_dir: `/var/db/collectd/rrd/freenas.local' exists but is not a directory!After installation I logged into the Web GUI and did the following: 1. I tried unchecking the reporting database, saving, then rechecking, but it doesn't seem to fix the issue.Found PCRE include files in /usr/include Found PCRE libraries in /usr/lib Checking for Open SSL ...

Pretty sure I updated first, then did the rest, but I'm afraid I don't recall the particular order. I have already added the directory manually, and reporting works fine now from what I can tell.I read some messages in the mailinglist that there are problems running the rrdtool over nfs.The rrd files are on a file server, and a processing server is connected to this file server through nfs to get the rrd files to process.Please see the INSTALL file for complete and updated requirements.The last message in is: "Insecure dependency in exec while running with -T switch". This problem occurs when you try to run munin-node as the munin user. (Note that the munin master should run as munin, but munin-node as root).

error updating could not lock rrd-71error updating could not lock rrd-82error updating could not lock rrd-13

I've got all of those: (from ./configure) Checking for RRDtool ...