[SUPPORT] testdasi repo


Recommended Posts

59 minutes ago, Kloudz said:

In regards to the Grafana Unraid Stack. After install, it seems to keep all my disks (SATA) active.

If you notice the last 5 are not doing anything. The last 5 drives are SAS drives. It's weird that the app is keeping the other drives busy.

 

Is there a way to fix this?

 

It's probably the smartctl call in telegraf.

 

Check your config:

vi /mnt/user/appdata/Grafana-Unraid-Stack/telegraf/telegraf.conf

 

Do you have nocheck = "standby" in inputs.smart?

 

[[inputs.smart]]
#   ## Optionally specify the path to the smartctl executable
   path = "/usr/sbin/smartctl"
#
#   ## On most platforms smartctl requires root access.
#   ## Setting 'use_sudo' to true will make use of sudo to run smartctl.
#   ## Sudo must be configured to to allow the telegraf user to run smartctl
#   ## without a password.
#   # use_sudo = false
#
#   ## Skip checking disks in this power mode. Defaults to
#   ## "standby" to not wake up disks that have stoped rotating.
#   ## See --nocheck in the man pages for smartctl.
#   ## smartctl version 5.41 and 5.42 have faulty detection of
#   ## power mode and might require changing this value to
#   ## "never" depending on your disks.
   nocheck = "standby"
#

          

Otherwise I don't know SAS but I remember some forum discussions of SAS and spindown, maybe you have to customize the call. Worst case you can comment out the whole block which should resolve spindown but will disable SMART stats in grafana.

Link to comment
14 minutes ago, CS01-HS said:

 

It's probably the smartctl call in telegraf.

 

Check your config:

vi /mnt/user/appdata/Grafana-Unraid-Stack/telegraf/telegraf.conf

 

Do you have nocheck = "standby" in inputs.smart?

 

[[inputs.smart]]
#   ## Optionally specify the path to the smartctl executable
   path = "/usr/sbin/smartctl"
#
#   ## On most platforms smartctl requires root access.
#   ## Setting 'use_sudo' to true will make use of sudo to run smartctl.
#   ## Sudo must be configured to to allow the telegraf user to run smartctl
#   ## without a password.
#   # use_sudo = false
#
#   ## Skip checking disks in this power mode. Defaults to
#   ## "standby" to not wake up disks that have stoped rotating.
#   ## See --nocheck in the man pages for smartctl.
#   ## smartctl version 5.41 and 5.42 have faulty detection of
#   ## power mode and might require changing this value to
#   ## "never" depending on your disks.
   nocheck = "standby"
#

          

Otherwise I don't know SAS but I remember some forum discussions of SAS and spindown, maybe you have to customize the call. Worst case you can comment out the whole block which should resolve spindown but will disable SMART stats in grafana.

 

Yep, I have nocheck = "standby". This is installed fresh from the App Store so not sure it would be different.

 

That said, commented the whole block and nope, it did not resolve the issue.

 

Link to comment
3 minutes ago, Kloudz said:

 

Yep, I have nocheck = "standby". This is installed fresh from the App Store so not sure it would be different.

 

That said, commented the whole block and nope, it did not resolve the issue.

 

 

Did you restart the container after (and verify your commenting out the block persisted through restart) ?

 

Can't imagine with no calls to the drives how it would keep them awake.

Edited by CS01-HS
Link to comment
2 hours ago, CS01-HS said:

 

Did you restart the container after (and verify your commenting out the block persisted through restart) ?

 

Can't imagine with no calls to the drives how it would keep them awake.

Yep, restarted the container and verified that the inputs.smart block was commented out

Link to comment
On 11/29/2021 at 4:00 AM, CS01-HS said:

 

And you're sure they sleep with the container stopped?

Maybe you have USE_HDDTEMP set to yes?

1183204964_ScreenShot2021-11-29at6_54_30AM.thumb.png.73e3b89e6c7a9cf885b0567cb8b771b1.png

 

If not I don't know what could be causing it.

 

I'm positive and USE_HDDTEMP does not help. It's OK, I just created a VM that just runs Grafana. Thank's for answering my questions.

  • Like 1
Link to comment
  • 3 weeks later...
  • 2 weeks later...
  • 1 month later...

is there a terminal command that can be run to update telegraf, influx, ect within this docker?

 

nevermind....

 

sudo apt-get install telegraf
Reading package lists... Done
Building dependency tree        
Reading state information... Done
telegraf is already the newest version (1.18.3-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

 

huh? hmmm.....

 

image.png.f20a1f6adfaf0fa14e0dd82c237536ef.png

 

i think this is something.....

 

Post Arguments   - /bin/sh -c 'apk update && apk upgrade && apk add ipmitool && apk add smartmontools && telegraf'

 

does this mean it updates on install?

 

Edited by TRusselo
Link to comment
  • 2 weeks later...

Re : GUS

@testdasi -  there have been 2 unraid docker updates in the past month that i have noticed, no commits in github since 2020, but shows multiple updates since 2020, as soon as 2 hours ago on dockerhub.

What was updated? 

is it not required by GPL/GNU licencing to post all source changes?

 

https://registry.hub.docker.com/r/testdasi/grafana-unraid-stack

https://github.com/testdasi/grafana-unraid-stack

Edited by TRusselo
Link to comment
2 hours ago, TRusselo said:

is it not required by GPL/GNU licencing to post all source changes?

 

Highly unlikely the maintainer here is actually changing the source code.  Rather he's pulling automatically from another source (the official repos?)  and the container gets built and updated as things change.  Most apps operate like this, which is why you pretty much never see any change logs for the container within CA.

  • Thanks 1
Link to comment
  • 1 month later...

I finally got around to installing this to replace my Grafana stack. This is really well put together man. Awesome work!

 

I'm a big fan of AIO containers on NAS devices. It takes the effort out of setting up the application. We are not here using Unraid so we can pretend that its an EC2 instance or VPS. This is a home NAS and your Docker image along with Unraid template has made this setup stupid simple and really clean on my Unraid dashboard.

 

Thanks!

Link to comment

Is there any chance to get rid of these errors while using your pihole container?

 

Quote

2022-04-15T08:15:12Z INF Adding DNS upstream url=https://dnsforge.de/dns-query
2022-04-15T08:15:12Z INF Adding DNS upstream url=https://dns.adguard.com/dns-query
2022-04-15T08:15:12Z INF Starting DNS over HTTPS proxy server address=dns://127.1.1.1:5153
2022-04-15T08:15:12Z INF cloudflared will not automatically update if installed by a package manager.
2022-04-15T08:20:19Z ERR failed to connect to an HTTPS backend "https://dnsforge.de/dns-query" error="failed to perform an HTTPS request: Post \"https://dnsforge.de/dns-query\": unexpected EOF"

 

stubby.yml:

Quote

## digitale-gesellschaft
   - address_data: 185.95.218.42
     tls_auth_name: "dns.digitale-gesellschaft.ch"
   - address_data: 185.95.218.43
     tls_auth_name: "dns.digitale-gesellschaft.ch"

 

cloudflare.yml:

Quote

proxy-dns: true
proxy-dns-port: 5153
proxy-dns-address: 127.1.1.1
proxy-dns-upstream:
  - https://dnsforge.de/dns-query
  - https://dns.adguard.com/dns-query

Link to comment
  • 2 months later...

I am using the DNS-DoT-DoH docker container.

 

I am curious to know. What DNS am I using?

 

These are my settings for the PiHole (I left the custom DNS IPs alone in the container config but I did enbale DNSSEC):

 

1438457833_Screenshotfrom2022-06-1518-07-23.thumb.png.d530695742f3d28b696e606bc3919800.png

 

Here are my router settings (the router is using PiHole IP address, and if that fails it uses AdGuard DNS):

 

37670435_Screenshotfrom2022-06-1518-09-47.png.87d16c235e502b35d335155344988696.png

 

Here are my DNS leak test results (I am not in Germany, not even close to it):

 

420336788_Screenshotfrom2022-06-1518-11-12.png.b1ab633fd2bb149ab369dea02fb8f746.png

 

Going by this, I can assume that DNSSEC is working fine? But what is my actual DNS, that is. What server am I using?

 

Router points to PiHole, but what is the PiHole pointing to?

 

Also, how do I know that DoT/DoH is working?

Edited by plantsandbinary
Link to comment
  • 3 weeks later...

Hello, first, thank you for your work, I am very happy with the OpenVPN-AIO-Client, however, I have an issue that worries me a bit, in the application log it shows the following

Quote

[warn] You specified a public address 0.0.0.0: 9119 (screenshot)

it is normal Or do I have a security breach?, and how could I mitigate it? Thank you very much for everything and greetings

image.png.47ccc8405eb47ce4407abb70262ce7e2.png

Link to comment
  • 1 month later...

I have some trouble with the open-client-aio Docker.
The SOCKS5 Proxy seemed to work when I put the container on the br0 network with an own IP and make it privileged, but that doesn't seem to work anymore. The Logs on startup look devastating:

 

text  error  warn  system  array  login  

kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
[11:30:41.350876] STUBBY: Read config from file /config/stubby/stubby.yml
RTNETLINK answers: File exists
/nftables.rules:11:27-31: Error: syntax error, unexpected sport
add rule ip filter INPUT  sport 1195 counter accept
                          ^^^^^
/nftables.rules:18:28-32: Error: syntax error, unexpected dport
add rule ip filter OUTPUT  dport 1195 counter accept
                           ^^^^^
Error: Could not process rule: No such file or directory
add rule ip filter INPUT tcp sport 853 counter accept
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error: Could not process rule: No such file or directory
add rule ip filter OUTPUT tcp dport 853 counter accept
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error: Could not process rule: No such file or directory
add rule ip filter INPUT tcp sport 53 counter accept
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error: Could not process rule: No such file or directory
add rule ip filter OUTPUT tcp dport 53 counter accept
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error: No such file or directory
list table filter
           ^^^^^^
Error: syntax error, unexpected newline, expecting number
delete rule filter INPUT handle
                               ^
Error: No such file or directory
list table filter
           ^^^^^^
Error: syntax error, unexpected newline, expecting number
delete rule filter OUTPUT handle
                                ^
Error: No such file or directory
list table filter
           ^^^^^^
Error: syntax error, unexpected newline, expecting number
delete rule filter INPUT handle
                               ^
Error: No such file or directory
list table filter
           ^^^^^^
Error: syntax error, unexpected newline, expecting number
delete rule filter OUTPUT handle
                                ^
Error: Could not process rule: No such file or directory
add rule ip filter INPUT ip saddr 192.168.178.201 tcp sport 53 ct state established counter accept
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error: Could not process rule: No such file or directory
add rule ip filter OUTPUT ip daddr 192.168.178.201 tcp dport 53 ct state new,established counter accept
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error: Could not process rule: No such file or directory
add rule ip filter INPUT ip saddr 192.168.178.201 udp sport 53 ct state established counter accept
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error: Could not process rule: No such file or directory
add rule ip filter OUTPUT ip daddr 192.168.178.201 udp dport 53 ct state new,established counter accept
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[info] Creation complete
[info] stubby fixed.
[info] danted fixed.
[info] tinyproxy fixed.
[info] torsocks fixed.
[info] privoxy fixed.
[info] Initialisation complete

[info] Run stubby in background on port 53
[warn] Your ISP public IP is 91.32.51.222

[info] Setting up nftables rules...
[info] Flusing ruleset
[info] Added route 192.168.178.0/24 via 192.168.178.1 dev eth0 
[info] Apply rules
[info] Quick block test. Expected result is time out. Actual result is 91.32.51.222
[info] All rules created

[info] Setting up OpenVPN tunnel...
[info] Create tunnel device
[info] Allow DnS for openvpn to lookup VPN server
[info] Connecting to VPN on port 1195 with proto ...
[info] Your VPN public IP is 91.32.51.222
[info] Block DnS to force traffic through tunnel
[info] Change DNS servers to 192.168.178.201
[info] Adding 192.168.178.201 to /etc/resolv.conf
[info] Allowing DNS lookups (tcp, udp port 53) to server '192.168.178.201'
[info] Tunnel created

[info] Enabling healthcheck...
[info] Healthcheck enabled

[info] Runing apps...

** Press ANY KEY to close this window ** 

 

Maybe my openvpn.ovpn is interfering somehow?

dev tun
fast-io
persist-key
persist-tun
nobind
remote usa-newyork-ca-version-2.expressnetw.com 1195
#remote uk-1-docklands-ca-version-2.expressnetw.com 1195
#remote uk-east-london-ca-version-2.expressnetw.com 1195
#remote uk-london-ca-version-2.expressnetw.com 1195
#remote germany-frankfurt-1-ca-version-2.expressnetw.com 1195

remote-random
pull
comp-lzo no
tls-client
verify-x509-name Server name-prefix
ns-cert-type server
key-direction 1
route-method exe
route-delay 2
tun-mtu 1500
fragment 1300
mssfix 1200
verb 3
cipher AES-256-CBC
keysize 256
auth SHA512
sndbuf 524288
rcvbuf 524288
auth-user-pass login

script-security 2
#dhcp-option DNS 192.168.178.11
#dhcp-option DOMAIN .lan

#up /etc/openvpn/update-resolv-conf
#down /etc/openvpn/update-resolv-conf

<cert>
-----BEGIN CERTIFICATE-----
---snipsnapp---


Any Ideas?

Link to comment
  • 1 month later...
On 10/21/2022 at 2:24 AM, Tom Sealey said:

Hi,
I've been using GUS for a while. 

However, since updating to UnRAID 6.11, whenever the docker restarts, the services crash.

If I manually console into the docker and restart them, they will run fine, but they don't run when the container starts.

Any ideas?

 

What commands do you use to get them up and running?  

  • Upvote 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.