rrdcached plugin: failed to connect

[gaetan25]

Hello everyone,

Sorry if my english is not perfect, I'm french;)
I have a problem with Freenas since yesterday. My CPU runs between 80 and 90% and the Ram is almost full when I'm not doing anything. I wanted to restart my server and it is very slow to stop. I also have an error message "rrdcached plugin: failed to connect". An image is with the message.
I even planted my boot, I had to reinstall Freenas and use a USB backup key but still the same problem.

For information, I switched to the 11.2-U4.1 few days ago, but I had no problem before yesterday.

My configuration:
Xeon E3-1230 V2 processor
2 GB ECC RAM (I'm still testing) There will be 32GB
2 ssd boot 16GB
12 HDD 2TB

Do you have an idea ? Thank you so much.

gaetan25

 

[Snow]

Well lets start with the 2Gb of ram there is a reason that the min is set to 8Gb. If you are not going to make the effort to read the most basic of guide's! That's why most if not all are not going to respond to your post on here. As you have broken numerous unus golden rule. What happens when you put 8Gb of ram in?

 

[feca23]

Hi guys. I have the same problem.

In this ver. 11.2 u3 if i checked all options in system dataset, no problem, if i didn`t check syslog or reporting database , this message came up if i shutdown or restart the system.

in 11.2 u4.1 allways do this message, what ever i check or choose.

hardwer

supermicro mobo
opteron 6276
72 gb ecc
64 gb ssd system
64gb ssd jail
8tb segate hdd

I hope we can find the solution.
thanks.

 

[garypib]

Same problem here during shutdown or shutdown before reboot. Also, the system rarely shuts down or reboots cleanly, I wonder if this is impacting that.

Version:
FreeNAS-11.2-U4.1

Processor:
AMD FX(tm)-6350 Six-Core Processor

Memory:
32 GB

Boot Pool:
2 - 120 GB SSD (redundant)

ZFS Pool
4 - 2 TB ZFS2 (6TB)


Any ideas?

Thanks

 

[feca23]

Check all of logging in system dataset menu.

 

[garypib]

daemon.log entry:
Jun 18 07:18:39 {servername} collectd[3374]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect to rrdcached: No such file or directory (status=2)

... (repeated multiple times within 1 second)

Jun 18 07:18:40 {servername} collectd[3374]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect to rrdcached: No such file or directory (status=2)

The file /var/run/rrdcached.sock does exist.

 

[proto]

is collectd daemon running?
if not try to restart it from command line.

 

[garypib]

yes, collectd is running

 

[feca23]

Same problem here during shutdown or shutdown before reboot. Also, the system rarely shuts down or reboots cleanly, I wonder if this is impacting that.

Version:
FreeNAS-11.2-U4.1

Processor:
AMD FX(tm)-6350 Six-Core Processor

Memory:
32 GB

Boot Pool:
2 - 120 GB SSD (redundant)

ZFS Pool
4 - 2 TB ZFS2 (6TB)


Any ideas?

Thanks

This is the solution!

 

[garypib]

Interesting. Apparently, checking and unchecking then saving fixed the issue.

Thanks

 

[feca23]

Interesting. Apparently, checking and unchecking then saving fixed the issue.

Thanks

You're welcome buddy.

 

[trolllception]

I am also getting this error and unchecking the logging hitting apply and then checking the boxes again and hitting apply doesn't seem to resolve the issue for me. So I can't seem to fix it for me.

 

[Silvan Burch]

me neither ... anybody found a solution?

 

[protious]

I have started to have this issue and it is seems to be starting to cause my system to reboot from what I can see. I attempted the fix about and does not seem to have worked.

Ryzen 2200g
32gb DDR4
6x 3tb HD in Raid z2
1x 120gb boot SSD
More info if needed.

 

[Silvan Burch]

there is a file called "rrdcached.sock=" in /var/run belonging to root:wheel
so it seems to be there ...

anyone made some progress on this?

 

[systemofapwne]

I lately had the same issue. No idea, what made it happen, but rrdcached was not running anyomore. The solution for me was to delete /var/run/rrdcached.pid and run system rrdcached start. If it still does not work, run system rrdcached stop and then system rrdcached start again.

 

[Havard79]

I have the same issue but my status is (status=61) and no reports shows in the webgui

HP proliant ml350 g6
32gb ram
2 times 8core cpu 2 ghz
SAS drives 300gb freenas boot
3tb zfs pool as beginning.

Doesn't anyone have a clue about this problem?

 

[Havard79]

I lately had the same issue. No idea, what made it happen, but rrdcached was not running anyomore. The solution for me was to delete /var/run/rrdcached.pid and run system rrdcached start. If it still does not work, run system rrdcached stop and then system rrdcached start again.

It didn't work for me

 

[systemofapwne]

I figured out, what the actual root cause was for me. (Sidenote: Despite I wrote system rrdcached start earlier, the right command to restart the daemon is service rrdcached start, yet this was not the root-cause for me).
My freenas-boot pool was degraded (and continued to rapidly degrade). The SSD I installed it on simply was bad so I switched it. Never got this error again but it kept on reappearing even when reinstalling FreeNAS from scratch to the bad SSD.
My suggestion: Try zpool scrub freenas-boot and check, if your boot-pool also is degraded. If so: Swap the drives. If not, the problem has not the same cause as for me. Either way: Take a backup of your FreeNAS config, reinstall FreeNAS and upload your config (make sure to backup your encryption keys too and also set an encryption passwords, or importing encrypted pools will fail!). This should hopefully fix it.

 

[captclearleft]

This is the solution!

I just upgraded my FreeNas system from 9.10.2U6 to 11.0 Then to 11.2. Everything went fine.
After shutting down after last upgrade is when I saw the errors mentioned in this thread: "rrdcached plugin: failed to connect". After reading through this thread - I checked the "System / System Dataset" And the "Reporting Database" was not checked. I checked it, clicked save... Then shutdown. Have not seen that error since. Just thought I would add my experience to the thread. Thanks All...