jsmith89

I'm having the exact same problem.

Did a complete clean install of the smokeping docker with new appdata and new data folders. Still not getting any data population. I did find something in the logs that is coming up every time I restart the smokeping docker: Jun 24 11:26:10 Tower kernel: docker0: port 7(vethc611f8a) entered disabled state Jun 24 11:26:10 Tower kernel: veth7b15c01: renamed from eth0 Jun 24 11:26:10 Tower kernel: docker0: port 7(vethc611f8a) entered disabled state Jun 24 11:26:10 Tower kernel: device vethc611f8a left promiscuous mode Jun 24 11:26:10 Tower kernel: docker0: port 7(vethc611f8a) entered disabled state Jun 24 11:26:44 Tower kernel: docker0: port 7(vetheff99df) entered blocking state Jun 24 11:26:44 Tower kernel: docker0: port 7(vetheff99df) entered disabled state Jun 24 11:26:44 Tower kernel: device vetheff99df entered promiscuous mode Jun 24 11:26:44 Tower kernel: docker0: port 7(vetheff99df) entered blocking state Jun 24 11:26:44 Tower kernel: docker0: port 7(vetheff99df) entered forwarding state Jun 24 11:26:44 Tower kernel: docker0: port 7(vetheff99df) entered disabled state Jun 24 11:26:44 Tower kernel: eth0: renamed from veth0f06c01 Jun 24 11:26:44 Tower kernel: docker0: port 7(vetheff99df) entered blocking state Jun 24 11:26:44 Tower kernel: docker0: port 7(vetheff99df) entered forwarding state

I'm having the same issue. Nothing on any of the graphs. Was working fine before. Tried removing image and reinstalling still having same issue. Attached are settings and logs Logs: [s6-init] making user provided files available at /var/run/s6/etc...exited 0.[s6-init] ensuring user provided files have correct perms...exited 0.[fix-attrs.d] applying ownership & permissions fixes...[fix-attrs.d] done.[cont-init.d] executing container initialization scripts...[cont-init.d] 10-adduser: executing...-------------------------------------_ _ _| |___| (_) ___| / __| | |/ _ \| \__ \ | | (_) ||_|___/ |_|\___/|_|Brought to you by linuxserver.ioWe gratefully accept donations at:https://www.linuxserver.io/donations/-------------------------------------GID/UID-------------------------------------User uid: 99User gid: 100-------------------------------------[cont-init.d] 10-adduser: exited 0.[cont-init.d] 30-config: executing...[cont-init.d] 30-config: exited 0.[cont-init.d] done.[services.d] starting services[services.d] done.AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 172.17.0.8. Set the 'ServerName' directive globally to suppress this message### assuming you are using an fping copy reporting in millisecondsSmokeping version 2.006011 successfully launched.Not entering multiprocess mode for just a single probe.FPing: probing 23 targets with step 300 s and offset 295 s. SmokePing.tiff

I'm having an issue with the smokeping docker where when I try and modify the Targets file in the appdata folder I get a permissions error that won't let me modify it. Here are my settings:

Not sure if this is worth noting on my end, however, I'm also experiencing the exact same issue after update 2016.10.17 with one major difference. I'm running IPMI Tools in unRAID 6.2.1 on two servers but only one server is having the issue. Server A with this board: SUPERMICRO MBD-X11SSL-F-O is having the issue and I keep getting this error in my syslog: Oct 19 22:54:17 Tower kernel: ipmi_si IPI0001:00: Error clearing flags: cc. Also, "IPMI-SENSORS" will not run from the command line. There is an error that states that the ipmi.sensors.config file cannot be found. I've attached the log for more details. Server B with board: SUPERMICRO MBD-X10SLL-F-O is working just fine after update 2016.10.17. The SUPERMICRO IPMI admin tools shows all sensors green and active I was helping someone with 6.1 but initially set the Max for freeipmi to 6.1 which didn't work because it's 6.1.9. So I changed it to Min 6.1 but forgot the Max which then installed the wrong version on 6.2. I only updated the plg file. So it's possible depending when you updated one server got the broken 10.17 plg. Anyway I pushed an update for the plugin and it should work now. That fixed it. Thanks.

What version of unRAID? I'm on 6.2.1

I have been using this plugin for nearly a year and it was running wonderfully after the last update I am having an issue. I can only see one sensor (a HDD temp). I can access all my sensor reading through the IPMI interface on the board but they won't load in the plugin either trying to access locally or over the network although it does return a positive login message. Anyone have any idea how to get it running again? Already tried deleting and reinstalling. The only thing in the logs that pops up is "Tower kernel: IPMI System Interface driver." Thanks