DieFalse

Members
  • Posts

    422
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by DieFalse

  1. Definitely start a support thread and post your diagnostics in it.
  2. VNSTAT is needed for Network Statistics to function correctly and it is not currently startable on my servers: "vnstat service must be running STARTED to view network stats." Please keep it. "root@Arcanine:~# vnstat Error: Database "/var/lib/vnstat//vnstat.db" contains 0 bytes and isn't a valid database, exiting." root@Arcanine:~# vnstat Error: Failed to open database "/var/lib/vnstat//vnstat.db" in read-only mode. The vnStat daemon should have created the database when started. Check that it is configured and running. See also "man vnstatd". root@Arcanine:~# vnstatd -d Error: Not enough free diskspace available in "/var/lib/vnstat/", exiting.
  3. Ok, After some research, I have acquired 4x MD32 controllers (MD3200 is dual link). To benefit now as well as future upgradability to 12Gb/s; A. I will likely configure as follows: 1x 9300-8E HBA to 1x MD3200 to MD1200 1x 9300-8E HBA to 1x MD3200 to MD1200 So my server will have two 8E cards, with 2x SFF-8644 to SFF-8088 cables connecting the HBA to the MD3200 and one SFF-8088 connecting the MD3200 to the MD1200. B. My alternative would be all 4 MD's connected to the LSI-SAS-6160, and then HBA's connecting to the 6160 also. This would keep any device from being chained, and allow dual link to the switch, dual links to the md3200's and single link to the md1200's. The LSI-SAS-6160 is basically an external expander in simple terms, that has multi-path and can even connect multiple hosts to multiple DAS/SAN's. At this point I am looking for 2x 9300-8e cards. (I don't think a 16e would benefit and from my understanding two 8e's would eliminate bottlenecking, especially when I later upgrade to a 12Gb/s chassis). If you confirm that my options are good, and if you think B is better than A, let me know. I trust your judgement way more than my own and your help was invaluable to my last build (42bay chassis).
  4. Thanks for looking into this. The MD1200's do daisy chain, up to 10 in a chain. and right now I think the way it works is 6 drives per port on controller. My current H800 P1 would be drives 1-6 on md1200(1) and 1-6 on MD1200(2) and then P2 would be drives 7-12 on each. Im thinking stacking the two new ones would not benefit me, and I would need a different card / cards. My R720XD can handle PCIe3 x8/x16 easily with multiple cards. Do you have a PCIe3 HBA card / cards recommendation? With my risers I can have 3x full height and 3x low profile. only one low profile is populated with a GPU right now. (FC16 HBA Full Height) Also - have you any thoughts on using a SAS Switch as the intermediary between HBAs? LSI SAS 6160?
  5. Sorry, should have added this, the drives may be 12gbs but the controller and md1200s are 6gbs. So my max bandwidth will be controlled by the card(s) and chassis. Would it be best to have 2xmd1200 on one card and 2x on the other or all 4 on one card?
  6. Background, I currently have 2x MD1200's with 2TB drives - connected to an R720XD via Perc H800 I am replacing the drives and adding two more MD1200s to the chain. Drives will all be 12TB 12GB/s SAS3. (48 drives total) 1. Would I be better off replacing the H800 with a different controller or adding a second card? 2. What would be the optimal connection method/card to enable max speed capable out of the 12Gb/s drives? Most will be the array, the others split between unassigned and cache pools.
  7. Ok - I found a MUCH easier way..... After making the changes to goaccess.conf to be: time-format %T date-format %d/%b/%Y log_format [%d:%t %^] %^ %^ %s - %m %^ %v "%U" [Client %h] [Length %b] [Gzip %^] [Sent-to %^] "%u" "%R" log-file /opt/log/proxy_logs.log Simply add the following line to each proxy host in NGINX Proxy Manager - Official "advanced" access_log /data/logs/proxy_logs.log proxy; like so: (if you already have advanced stuff here, add the line to the VERY top) Now they all log to the same file, and same format, simply add the line to all proxy_hosts and remember to add it to any new ones.
  8. Nevermind, I got it: goaccess.conf: comment out the existing time/date/log formats and add this: time-format %T date-format %d/%b/%Y log_format [%d:%t %^] %^ %^ %s - %m %^ %v "%U" [Client %h] [Length %b] [Gzip %^] [Sent-to %^] "%u" "%R" Then add under the log file your list of proxy-host-log files like so: (note this is my list and is not the same as your list, find this in your NGINX Proxy Manager - Official appdata logs and add each you want to track. log-file /opt/log/proxy-host-12_access.log log-file /opt/log/proxy-host-13_access.log log-file /opt/log/proxy-host-14_access.log log-file /opt/log/proxy-host-15_access.log log-file /opt/log/proxy-host-3_access.log log-file /opt/log/proxy-host-4_access.log log-file /opt/log/proxy-host-5_access.log log-file /opt/log/proxy-host-6_access.log log-file /opt/log/proxy-host-8_access.log log-file /opt/log/proxy-host-9_access.log
  9. Here is the log format that NGINX Proxy Manager - Official uses for: Proxy hosts: '[$time_local] $upstream_cache_status $upstream_status $status - $request_method $scheme $host "$request_uri" [Client $remote_addr] [Length $body_bytes_sent] [Gzip $gzip_ratio] [Sent-to $server] "$http_user_agent" "$http_referer"' standard: '[$time_local] $status - $request_method $scheme $host "$request_uri" [Client $remote_addr] [Length $body_bytes_sent] [Gzip $gzip_ratio] "$http_user_agent" "$http_referer"' Someone that knows the variables for goaccess, will need to convert the "proxy" one.
  10. This is a great thought - I shall try that! thanks!
  11. I don't need to add additional rules, the log_format is invalid for Argo Tunnel I can not modify the log_format via advanced. I was able to find the files in console shell for the container (which will retain changes until I update the docker). debian-buster slim is nice.
  12. where is nginx.conf and tun.domain.com.ssl.con files for NginxProxyManager-Official? I would like to modify the log_format for it, but can not find it.
  13. I spent time with this and got several things to work, but it seems with the Nginx Proxy Manager - Official container, the log files are different between fallback_access.log and the proxy host logs. Adding them all will not work and missing info will occur since you can have either all the proxy host logs OR fallback_access since they're formatted differently. As for the permissions, use a folder or share not in NginxProxyManager/GoAccess'es appdata and it will allow it to read correctly. I made a share called Logs that I use for various logging and mapped to /mnt/user/Logs/NPM/
  14. I have been up for 24 hours on Version: 6.10.0-rc2g without the issue so far. Will report any changes. This still occurs in rc2g
  15. I have the same issue as above however if you fix: https://raw.githubusercontent.com/xthursdayx/docker-templates/master/xthursdayx/whoogle-search.xml it wants https://raw.githubusercontent.com/FoxxMD/unraid-docker-templates/master/foxxmd/whoogle-search.xml and if you fix that it wants the other and is stuck in a cyclic loop.
  16. Problem still exists in Version: 6.10.0-rc2f and still resolves by issuing the conntrack max command.
  17. Within Settings - Docker with it disabled/stopped, with advanced ticked. I believe you can set default network there.
  18. I am having a problem with Argo Tunnel and NPM. Any client connecting to my environment, through https- gets logged as the Docker Network IP and not the CF Connecting IP. Has anyone gotten the Real IP to come through both Argo Tunnel into NPM? Its a config issue in NPM that I can not ascertain.
  19. Note to all that come here for help with Argo Tunnel config. You should not use "noTLSVerify: true" for anything other than troubleshooting in your config.yaml. It is less safe to leave this way. If you are having issues that this resolves in troubleshooting, It is fixable to be secure, don't stop there and use it just because it works. Tips: originServerName: domain.com ^ rarely works correctly, instead use: originServerName: subdomain.domain.com ^ use this that has a VALID CNAME record pointed to the root of the domain "@" In my example config here: tunnel: XXX credentials-file: XXX.json ingress: - service: https://proxysdockerip:18443 originRequest: originServerName: service.domain.ext proxydockerip can be the docker name if you are using a custom docker network, or the IP of the docker that serves as your reverse proxy, like SWAG or NPM. service.domain.dom is a valid CNAME of "service" pointed to "@" in the DNS of "domain.dom". This allows cloudflared / CF Argo Tunnel to validate correctly.
  20. SMART checkes drives health - not data health. You have corruption and will need to repair the corruption.
  21. @mkono87 you have XFS corruption, hopefully @JorgeB can assist with that. Thats the last entry before the crash: Sep 7 14:22:55 NAS kernel: XFS (sdb1): Metadata corruption detected at xfs_dinode_verify+0xa7/0x567 [xfs], inode 0xe997421 dinode Sep 7 14:22:55 NAS kernel: XFS (sdb1): Unmount and run xfs_repair Sep 7 14:22:55 NAS kernel: XFS (sdb1): First 128 bytes of corrupted metadata buffer: Sep 7 14:22:55 NAS kernel: 00000000: 49 4e 81 a4 03 02 00 00 00 00 00 63 00 00 00 64 IN.........c...d Sep 7 14:22:55 NAS kernel: 00000010: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................ Sep 7 14:22:55 NAS kernel: 00000020: f0 be 68 03 81 88 ff ff 60 d6 04 ab 27 03 36 41 ..h.....`...'.6A Sep 7 14:22:55 NAS kernel: 00000030: 60 d6 04 ab 27 03 36 41 00 00 00 00 00 08 de c1 `...'.6A........ Sep 7 14:22:55 NAS kernel: 00000040: 00 00 00 00 00 00 00 8e 00 00 00 00 00 00 00 01 ................ Sep 7 14:22:55 NAS kernel: 00000050: 00 00 00 02 00 00 00 00 00 00 00 00 5f 57 70 8c ............_Wp. Sep 7 14:22:55 NAS kernel: 00000060: ff ff ff ff be bc 40 17 00 00 00 00 00 00 00 06 ......@......... Sep 7 14:22:55 NAS kernel: 00000070: 00 00 1d dd 00 00 f5 f6 00 00 00 00 00 00 00 00 ................ Sep 7 16:13:34 NAS kernel: XFS (sdb1): Metadata corruption detected at xfs_dinode_verify+0xa7/0x567 [xfs], inode 0xe997421 dinode Sep 7 16:13:34 NAS kernel: XFS (sdb1): Unmount and run xfs_repair Sep 7 16:13:34 NAS kernel: XFS (sdb1): First 128 bytes of corrupted metadata buffer: Sep 7 16:13:34 NAS kernel: 00000000: 49 4e 81 a4 03 02 00 00 00 00 00 63 00 00 00 64 IN.........c...d Sep 7 16:13:34 NAS kernel: 00000010: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................ Sep 7 16:13:34 NAS kernel: 00000020: f0 be 68 03 81 88 ff ff 60 d6 04 ab 27 03 36 41 ..h.....`...'.6A Sep 7 16:13:34 NAS kernel: 00000030: 60 d6 04 ab 27 03 36 41 00 00 00 00 00 08 de c1 `...'.6A........ Sep 7 16:13:34 NAS kernel: 00000040: 00 00 00 00 00 00 00 8e 00 00 00 00 00 00 00 01 ................ Sep 7 16:13:34 NAS kernel: 00000050: 00 00 00 02 00 00 00 00 00 00 00 00 5f 57 70 8c ............_Wp. Sep 7 16:13:34 NAS kernel: 00000060: ff ff ff ff be bc 40 17 00 00 00 00 00 00 00 06 ......@......... Sep 7 16:13:34 NAS kernel: 00000070: 00 00 1d dd 00 00 f5 f6 00 00 00 00 00 00 00 00 ................ Sep 7 17:25:13 NAS kernel: XFS (sdb1): Metadata corruption detected at xfs_dinode_verify+0xa7/0x567 [xfs], inode 0xe997421 dinode Sep 7 17:25:13 NAS kernel: XFS (sdb1): Unmount and run xfs_repair Sep 7 17:25:13 NAS kernel: XFS (sdb1): First 128 bytes of corrupted metadata buffer: Sep 7 17:25:13 NAS kernel: 00000000: 49 4e 81 a4 03 02 00 00 00 00 00 63 00 00 00 64 IN.........c...d Sep 7 17:25:13 NAS kernel: 00000010: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................ Sep 7 17:25:13 NAS kernel: 00000020: f0 be 68 03 81 88 ff ff 60 d6 04 ab 27 03 36 41 ..h.....`...'.6A Sep 7 17:25:13 NAS kernel: 00000030: 60 d6 04 ab 27 03 36 41 00 00 00 00 00 08 de c1 `...'.6A........ Sep 7 17:25:13 NAS kernel: 00000040: 00 00 00 00 00 00 00 8e 00 00 00 00 00 00 00 01 ................ Sep 7 17:25:13 NAS kernel: 00000050: 00 00 00 02 00 00 00 00 00 00 00 00 5f 57 70 8c ............_Wp. Sep 7 17:25:13 NAS kernel: 00000060: ff ff ff ff be bc 40 17 00 00 00 00 00 00 00 06 ......@......... Sep 7 17:25:13 NAS kernel: 00000070: 00 00 1d dd 00 00 f5 f6 00 00 00 00 00 00 00 00 ................
  22. Hi @danioj I wanted to check in and see if you still had zero traces