dazzathewiz

Members
  • Posts

    14
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

dazzathewiz's Achievements

Noob

Noob (1/14)

5

Reputation

  1. Thanks very much - I will order another drive to replace that one and then play with those tests. The docker is great - the reason I used it was because I am seeing very high CPU IO Wait times when copy operations to the Array are happening and I couldn't pin down the cause. I suspect the issue will be this drive. So thanks for your efforts developing this one.
  2. I was having the same problem, noticed it updated over night and now doesn't work. TL;DR this happens in the new version because the docker no longer runs under root and I had some extra parameters that's running `apk` which isn't allowed by the new telegraf user. Longer explain: A google lead me to info about it being a user permission issue: https://stackoverflow.com/questions/50727783/alpine-docker-error-unable-to-lock-database-permission-denied-error-failed-to Then looked at the dockerfile in github, it seems prior to Oct 15, the telegraf docker was running as root. They changed this to use 'telegraf' user, see commit here: https://github.com/influxdata/influxdata-docker/commit/83520188be87cbee6edb3ac995c647cf99acdf51 The error in my case was happening becuase I add some apk pakages by docker settings -> advanced -> Post Arguments /bin/sh -c 'apk update && apk add lm_sensors lm-sensors-detect perl && apk add smartmontools && apk add nvme-cli && telegraf' After removing those argument, I simply get an error in the log because it can't find smart (which was removed): After commenting out inputs.smart in my config I could start telegraf again. In my case, the graphs and data I use actually wasn't affected by not having inputs.smart, so I didn't reconfigure it. But this may help others if they don't want to pin telegraf to an older/specific tag.
  3. Oh awesome, thanks! Can confirm adding options i915 force_probe=4c8a to /boot/config/modprobe.d/i915.conf worked a treat and I now have the /dev/dri device
  4. Have an i7-11700 and same issue. It doesn't look like it's updated in the Kernel for support yet. Just have to wait - I have tried 6.9.2 and still not updated.
  5. Hmmm... I prefer not to post my whole config, but here is the relevant parts I've pulled out of my config... this one is part of my default domain so it's not in a separate subdomain conf like yours is... Are you getting an nginx error, or is it just not working when you hit https://yourdomain/guacamole/ ? It may have to do with needing some of those variables configured... I can never remember every time I look at the file fresh it takes some time to remember what it does... proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $server_name; # main server block server { listen 443 ssl default_server; root /config/www; index index.html index.htm index.php; server_name _; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; client_max_body_size 0; # Krusader # -> https://guacamole.apache.org/doc/gug/proxying-guacamole.html location /krusader/ { include /config/nginx/proxy.conf; proxy_pass http://192.168.0.218:8088/; proxy_buffering off; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; access_log off; } }
  6. If I can just 'pile on' to this thread... I have a MB with integrated Bluetooth (uses Intel 8260 communication module, which is connected via PCIE) and I want to pass that through to a docker. If I was using a VM instead, I'm sure I could just pass this IOMMU group: IOMMU group 17:[8086:24f3] 06:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) But I would prefer to use the docker so would need the kernel module. Is the correct module called 'btintel'? I guess it's not supported in the current kernel given: modprobe btintel modprobe: FATAL: Module btintel not found in directory /lib/modules/4.18.17-unRAID
  7. I'm a month late, but the docker Console function is super handy... I didn't even know this improvement existed until I did an upgrade today!
  8. I've looked into this myself in recent months. TLDR; No but personally I have a custom script which works for my setup, but there some inconvenience in setting it up and maintaining it... I also noticed someone has recently made a request for this in telegraf (https://github.com/influxdata/telegraf/issues/4169) If you put this code into a script called nvmetemp.sh in your /mnt/user/appdata/telegraf: #!/bin/sh for device in /dev/nvme[0-9]; do temp=`smartctl -a $device | grep Temperature | awk '{print $2}'` serial=`smartctl -a $device | grep Serial | awk '{print $3}'` percent=`smartctl -a $device | grep Percentage | awk '{print $3}' | sed 's/.$//'` echo "disk,device=$device,serial=$serial temperature=$temp,percent_used=$percent" done Then you need to change a couple of things inside the docker (which you get a shell to by typing "docker exec -it telegraf /bin/sh" without quotes): (**Note comments about adding smartmontools package below) apk add smartmontools chmod 755 /config/nvmetemp.sh **Note smartmontools won't be installed the next time your docker updates to a new version. So if you have auto-update dockers it disappears and your temp is no longer recorded. You have to do the same process of adding the package inside the docker (apk add smartmontools) every time the docker updates. Then un-comment in your telegraf.conf [[inputs.exe]] so it should look something like this: [[inputs.exec]] commands = ["sh /config/nvmetemp.sh"] timeout = "10s" data_format = "influx" The actual problem is the method used to get disk temperatures by Telegraf - I think it grep's the string from the smartctl -a /dev/*** command output. NVME devices have a different text format in smartctl, thus Telegraf doesn't find the NVME temp. It seems to me like the plugins [[inputs.sensors]] and [[inputs.smart]] use the same method of getting the disk temperatures.
  9. So my thoughts didn't involve any moving of data from array to cache - I think that's a different thing altogether and not a feature currently existing in Unraid. Really what I'm talking about is a way of targeting files to delay their move off the cache to the array. IE: currently the mover moves all files on all shares that use cache indiscriminately - it would be cool to filter what gets moved at the time the mover is scheduled to run so that some stuff stays on the cache if it is new, but old stuff gets moved. 100%! I can write these scripts for my own use. I guess in my searching around forums I've seen a few ideas thrown around about what people think are good improvements to cache moves, but a lot of them are more complex under the surface. I was just trying to think of more simple changes to existing functionality that (it seems) might be useful to others. And generally I think it would be a better solution if implemented by the Unraid team than my own thinking off the top of my head, not to mention it could just be put in as options in the web GUI.
  10. It would be nice to see the mover script be more configurable from the UI. I'd also like to see the mover settings configurable per share also - basically have a 'default' mover configuration and for shares (which use cache) can overwrite the defaults. These features would only apply to "protected" cache volumes (more than 1 cache disk) since the idea of the mover on a single disk cache volume is to get data off ASAP (although an over-ride for advanced users is probably nice!). These options would change when the data moves off the cache volume: - Only move off cache files of a certain age (file created date). I think the mover uses rsync (?) so this could be implemented via rsync options. - Similar to above, if possible to only move files which have not been modified/added to within a defined timeframe. Not sure if possible with timestamps/rsync without further investigation. - Only move files when cache volume usage is at a defined level (% or GB free I guess) On my own server I would modify the mover script to accommodate some of these functions, but it would be much better not to maintain through upgrades and be done properly from source. Use cases I guess a lot of my thinking is more around tiering of data... PLEX If you have share where users consume content within a typical period after the file is first put on the share (and are able to provide large enough cache disk volume) then files could sit on the cache for when the majority of users will access it without the need to spinning up/keeping spinning array drives. Office Shares Again where content is created and worked on frequently for a few weeks and then once finished is not viewed with any regularity unless required, it would be good to keep on the cache
  11. So for Krusader - I got it to work (fixed the rolling gear) copying the settings under Nginx section in https://guacamole.apache.org/doc/gug/proxying-guacamole.html (Note the docker runs guacamole) location /guacamole/ { proxy_pass http://HOSTNAME:8080/guacamole/; proxy_buffering off; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; access_log off; }