Msan
-
Posts
321 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Msan
-
-
Which version of unraid are you running?
6.3.0-rc2
-
If anyone wants me to test something, let me know.. I have no problem with deleting/modding my smokeping install..
I did suggest to chmod -R 755 /mnt/user/docker/smokeping.
Nope, didnt work.. tried 777 as well.. if I docker exec into the container, I can see the files and directories in /data just fine..
-
If anyone wants me to test something, let me know.. I have no problem with deleting/modding my smokeping install..
-
No problem using a cache only share on a cache pool through /mnt/user.
Not sure what is different on my system then..
-
Yup, after changing /data to point back to /mnt/user/docker/smokeping/ I get the errors again...
FPing: probing 20 targets with step 300 s and offset 48 s. RRDs::update ERROR: mmaping file '/data/USA/Sun.rrd': No such device RRDs::update ERROR: mmaping file '/data/USA/IU.rrd': No such device RRDs::update ERROR: mmaping file '/data/USA/UCB.rrd': No such device RRDs::update ERROR: mmaping file '/data/USA/MIT.rrd': No such device RRDs::update ERROR: mmaping file '/data/USA/UCSD.rrd': No such device RRDs::update ERROR: mmaping file '/data/Europe/Germany/TelefonicaDE.rrd': No such device
changing /data back to /mnt/cache/docker/smokeping/ now..
-
All cache only shares are also seen under /mnt/user. The only possibility I see and it doesn't make any sense is the format of the cache drive itself. Mine is XFS, what's yours?My docker share that also is seen on /mnt/user/docker is set to "Use cache disk only".. that might be why..
I have 2 drives as the cache drive.. it's using btrfs
@CHBMB - I just checked all the disk shares and there is no stray /mnt/diskX/docker/smokeping/ directory anywhere.
I'll try and revert my /data entry again to see if the issue comes back..
-
Seems to work fine mapping both /data and /config to /mnt/user/.... running 6.3RC3 ie: No fault found, and since I don't believe there have been any changes since 6.2 RC4 (since the support for special unix files came into effect), I don't know what the issue may be...Can you try mapping /data to the cache disk rather than the array?
Sent from my LG-H815 using Tapatalk
So setting the /data path to /mnt/cache/docker/smokeping/ worked..
This is strange, as /mnt/user/docker/smokeping/ points to the same place and when inside the docker I could see /data and the files just fine?
It's not really strange. /mnt/cache is a disk share and /mnt/user is a fuse (or how it's called) share. Support for hardlinking in user share is still new, so there might be some bugs still.
My docker share that also is seen on /mnt/user/docker is set to "Use cache disk only".. that might be why..
-
Can you try mapping /data to the cache disk rather than the array?
Sent from my LG-H815 using Tapatalk
So setting the /data path to /mnt/cache/docker/smokeping/ worked..
This is strange, as /mnt/user/docker/smokeping/ points to the same place and when inside the docker I could see /data and the files just fine?
-
Yes I used fresh folders.. my /mnt/docker is actually on the cache drive, but I'll try setting the path directly..
-
Please post a screenshot of the advanced settings also. I suspect you map the same host folder for both data and config.
Then you'd be wrong
-
Anybody?
I just tested my container on unRaid, then forced upgrade, and then pulled the container on my workstation and can't reproduce the issue.
Have you tried removing the container and re-adding? As long as you don't delete the apps folder for the container, your data won't be lost.
I just deleted and reinstalled the container.. all at defaults.. same error
No errors here either. You are sure you used new folders for both config and data and deleted the image also?
Please post screenshot of your template and post the log from the docker.
Docker log:
ErrorWarningSystemArrayLogin [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.io We gratefully accept donations at: https://www.linuxserver.io/index.php/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... './Alerts' -> '/config/./Alerts' './Database' -> '/config/./Database' './General' -> '/config/./General' './Presentation' -> '/config/./Presentation' './Probes' -> '/config/./Probes' './Slaves' -> '/config/./Slaves' './Targets' -> '/config/./Targets' './pathnames' -> '/config/./pathnames' './smtp.conf' -> '/config/./smtp.conf' [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.7. Set the 'ServerName' directive globally to suppress this message Smokeping version 2.006011 successfully launched. Not entering multiprocess mode for just a single probe. FPing: probing 20 targets with step 300 s and offset 297 s. RRDs::update ERROR: mmaping file '/data/USA/MIT.rrd': No such device RRDs::update ERROR: mmaping file '/data/USA/Sun.rrd': No such device RRDs::update ERROR: mmaping file '/data/USA/UCSD.rrd': No such device RRDs::update ERROR: mmaping file '/data/USA/IU.rrd': No such device RRDs::update ERROR: mmaping file '/data/USA/UCB.rrd': No such device RRDs::update ERROR: mmaping file '/data/InternetSites/Facebook.rrd': No such device RRDs::update ERROR: mmaping file '/data/InternetSites/Youtube.rrd': No such device RRDs::update ERROR: mmaping file '/data/InternetSites/linuxserverio.rrd': No such device RRDs::update ERROR: mmaping file '/data/InternetSites/JupiterBroadcasting.rrd': No such device RRDs::update ERROR: mmaping file '/data/InternetSites/GoogleSearch.rrd': No such device RRDs::update ERROR: mmaping file '/data/DNS/OpenDNS2.rrd': No such device RRDs::update ERROR: mmaping file '/data/DNS/GoogleDNS2.rrd': No such device RRDs::update ERROR: mmaping file '/data/DNS/GoogleDNS1.rrd': No such device RRDs::update ERROR: mmaping file '/data/DNS/OpenDNS1.rrd': No such device RRDs::update ERROR: mmaping file '/data/Europe/Germany/TelefonicaDE.rrd': No such device RRDs::update ERROR: mmaping file '/data/Europe/Switzerland/CernIXP.rrd': No such device RRDs::update ERROR: mmaping file '/data/Europe/Switzerland/SBB.rrd': No such device RRDs::update ERROR: mmaping file '/data/Europe/UK/IBNorwich.rrd': No such device RRDs::update ERROR: mmaping file '/data/Europe/UK/UEA.rrd': No such device RRDs::update ERROR: mmaping file '/data/Europe/UK/CambridgeUni.rrd': No such device
Template shot attached..
-
Anybody?
I just tested my container on unRaid, then forced upgrade, and then pulled the container on my workstation and can't reproduce the issue.
Have you tried removing the container and re-adding? As long as you don't delete the apps folder for the container, your data won't be lost.
I just deleted and reinstalled the container.. all at defaults.. same error
-
-
I just installed this to try out, but I am getting these kind of errors after a few minutes:
RRDs::update ERROR: mmaping file '/data/InternetSites/Facebook.rrd': No such device RRDs::update ERROR: mmaping file '/data/InternetSites/JupiterBroadcasting.rrd': No such device RRDs::update ERROR: mmaping file '/data/InternetSites/Youtube.rrd': No such device RRDs::update ERROR: mmaping file '/data/InternetSites/GoogleSearch.rrd': No such device
I checked inside the docker and these files exist..
root@a1737459c8c7:/data/InternetSites$ ls -al total 14600 drwxr-xr-x 1 abc abc 158 Oct 17 13:21 . drwxrwxrwx 1 abc abc 76 Oct 17 13:24 .. -rw-r--r-- 1 abc abc 2986808 Oct 17 13:21 Facebook.rrd -rw-r--r-- 1 abc abc 2986808 Oct 17 13:21 GoogleSearch.rrd -rw-r--r-- 1 abc abc 2986808 Oct 17 13:21 JupiterBroadcasting.rrd -rw-r--r-- 1 abc abc 2986808 Oct 17 13:21 Youtube.rrd -rw-r--r-- 1 abc abc 2986808 Oct 17 13:21 linuxserverio.rrd
Am I missing something?
-
How about having the ability to have a custom script run when it's triggered?
This way folks could have extra/special things happen without having to have it hardcoded into the plugin..
I think this is a good idea. It lets anyone customize the response as they wish, and add extra warnings and special notifications, beyond the standard ones. And perhaps start file integrity tools running to begin identifying what's changed.
Yes, thats what I had in mind.. for me it could tell my router to cut off access to the net for the unraid server so it doesnt "leak" any info..
-
How about having the ability to have a custom script run when it's triggered?
This way folks could have extra/special things happen without having to have it hardcoded into the plugin..
-
ok, i feel stupid. Thanks!
LOL... any time
-
How can I get the release candidate without having unRAID already installed? How do I open the *.plg file? I tried downloading the zip from S3 but got an access denied error.
https://lime-technology.com/download/
-
I just did a clean install of the emby docker but it seems to crash when trying to start up..
I left everything at defaults on install.
Running on unraid 6.2 mainline
Some logs are attached..
-
Thanks for the update! Everything is working perfectly now for me!
-
Updated. It should show events as readings for OEM Reserved. The footer will take a bit more work.
Thanks, it shows up properly in the sensor report now, but still shows N/A in the dashboard..
Updated. Should work for dash and footer.
Thanks! It shows up properly in all places now.. Just a small request for your next update, can you remove the ' from the display.. Right now it shows as 'Low' everywhere instead of Low
Thanks again!
Can you run this command for me and post the output?
/usr/sbin/ipmi-sensors --output-sensor-thresholds --comma-separated-output --output-sensor-state --no-header-output --interpret-oem-data
Sure, here 'ya go..
root@Tower:~# /usr/sbin/ipmi-sensors --output-sensor-thresholds --comma-separated-output --output-sensor-state --no-header-output --interpret-oem-data 4,CPU Temp,OEM Reserved,Nominal,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,'Low' 5,Sys Temp,Temperature,Nominal,34.00,C,N/A,N/A,N/A,76.00,78.00,80.00,'OK' 6,CPU Vcore,Voltage,Nominal,1.16,V,0.86,0.88,0.90,1.62,1.63,1.64,'OK' 7,DIMM Volt,Voltage,Nominal,1.82,V,1.57,1.58,1.60,2.00,2.02,2.03,'OK' 8,3.3V,Voltage,Nominal,3.30,V,2.91,2.93,2.94,3.65,3.66,3.68,'OK' 9,5V,Voltage,Nominal,4.80,V,4.42,4.44,4.46,5.52,5.54,5.57,'OK' 10,12V,Voltage,Nominal,11.81,V,10.46,10.56,10.66,13.34,13.44,13.54,'OK' 11,-12V,Voltage,Nominal,-12.10,V,-10.50,-10.60,-10.70,-13.30,-13.40,-13.50,'OK' 12,5VSB,Voltage,Nominal,4.85,V,4.42,4.44,4.46,5.52,5.54,5.57,'OK' 13,VBAT,Voltage,Nominal,3.22,V,2.91,2.93,2.94,3.65,3.66,3.68,'OK' 14,Fan1,Fan,Nominal,3000.00,RPM,200.00,300.00,400.00,N/A,N/A,N/A,'OK' 15,Fan2,Fan,Nominal,1000.00,RPM,200.00,300.00,400.00,N/A,N/A,N/A,'OK' 16,Fan3,Fan,Nominal,1000.00,RPM,200.00,300.00,400.00,N/A,N/A,N/A,'OK' 17,Fan4,Fan,Nominal,900.00,RPM,200.00,300.00,400.00,N/A,N/A,N/A,'OK' 18,Fan5,Fan,Nominal,3000.00,RPM,200.00,300.00,400.00,N/A,N/A,N/A,'OK' 19,Fan6/CPU,Fan,Nominal,1500.00,RPM,200.00,300.00,400.00,N/A,N/A,N/A,'OK' 20,Intrusion,Physical Security,Nominal,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,'OK' 21,Power Supply,Power Supply,Nominal,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,'OK' 22,Thermal Trip,Module/Board,Nominal,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,'OK' 23,BIOS,System Firmware Progress,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A
-
Updated. It should show events as readings for OEM Reserved. The footer will take a bit more work.
Thanks, it shows up properly in the sensor report now, but still shows N/A in the dashboard..
Updated. Should work for dash and footer.
Thanks! It shows up properly in all places now.. Just a small request for your next update, can you remove the ' from the display.. Right now it shows as 'Low' everywhere instead of Low
Thanks again!
-
Updated. It should show events as readings for OEM Reserved. The footer will take a bit more work.
Thanks, it shows up properly in the sensor report now, but still shows N/A in the dashboard..
-
root@Tower:/mnt/user/system/libvirt# ipmi-sensors --interpret-oem-data ID | Name | Type | Reading | Units | Event 4 | CPU Temp | OEM Reserved | N/A | N/A | 'Low' 5 | Sys Temp | Temperature | 35.00 | C | 'OK' 6 | CPU Vcore | Voltage | 1.16 | V | 'OK' 7 | DIMM Volt | Voltage | 1.82 | V | 'OK' 8 | 3.3V | Voltage | 3.30 | V | 'OK' 9 | 5V | Voltage | 4.82 | V | 'OK' 10 | 12V | Voltage | 11.81 | V | 'OK' 11 | -12V | Voltage | -12.10 | V | 'OK' 12 | 5VSB | Voltage | 4.85 | V | 'OK' 13 | VBAT | Voltage | 3.22 | V | 'OK' 14 | Fan1 | Fan | 3000.00 | RPM | 'OK' 15 | Fan2 | Fan | 1000.00 | RPM | 'OK' 16 | Fan3 | Fan | 1000.00 | RPM | 'OK' 17 | Fan4 | Fan | 900.00 | RPM | 'OK' 18 | Fan5 | Fan | 3100.00 | RPM | 'OK' 19 | Fan6/CPU | Fan | 1400.00 | RPM | 'OK' 20 | Intrusion | Physical Security | N/A | N/A | 'OK' 21 | Power Supply | Power Supply | N/A | N/A | 'OK' 22 | Thermal Trip | Module/Board | N/A | N/A | 'OK' 23 | BIOS | System Firmware Progress | N/A | N/A | N/A
Board is in my signature..
Oh ok. So does it show low in the sensor readings page or did you want it for the footer? I already have --interpret-oem-data in the command string so it should show up in readings.
It shows up as N/A in the sensor reading.. It would be great to have in the footer as well..
Let me know if you need me to test anything..
[Support] Linuxserver.io - SmokePing
in Docker Containers
Posted
Didn't work under 6.3.0-rc1 either..