shwa87

Members
  • Posts

    21
  • Joined

  • Last visited

Recent Profile Visitors

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

shwa87's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. noticing this in my logs as well. This is related to winbond and samba... so i think it's when using AD integration? Will UR change to a different samba plugin to avoid this error or possible future SMB issues?
  2. idrac6 issue here. I am experiencing this issue as raised on github: Server disconnected : Code 1006 · Issue #34 · DomiStyle/docker-idrac6 · GitHub I tried searching the UR forums (this thread and the whole forum) and couldn't find any resolution. Maybe I missed it, and if I did, I apologize. Does anyone know what the solution is for this?
  3. So DelugeVPN had been working fine until sometime in the last week. Now the UI won't load because the VPN isn't coming up... but the VPN isn't coming but because the wg0 interface won't create: 2021-10-07 19:44:32,093 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'up'... 2021-10-07 19:44:32,102 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2021-10-07 19:44:32,109 DEBG 'start-script' stderr output: [#] ip link add wg0 type wireguard 2021-10-07 19:44:32,121 DEBG 'start-script' stderr output: Error: Unknown device type. 2021-10-07 19:44:32,134 DEBG 'start-script' stderr output: Unable to access interface: Protocol not supported 2021-10-07 19:44:32,135 DEBG 'start-script' stderr output: [#] ip link delete dev wg0 2021-10-07 19:44:32,138 DEBG 'start-script' stderr output: Cannot find device "wg0" 2021-10-07 19:44:32,139 DEBG 'start-script' stdout output: [warn] WireGuard interface failed to come 'up', exit code is '1' Specifically looks like its having an issue with: ip link add wg0 type wireguard as it errors out with Unknown device type. Any assistance here would be appreciated. I've searched several times on these forums, general googlefu, read the FAQ on github, and some reddit posts as well but nothing seems to be quite what I'm experiencing. Thank You!
  4. I just updated to 6.10.0-rc1 and on my Dell r610 where virtualization had been working, I am now getting a message that It currently has 160GB RAM and 2x Xeon X5675s, and all virtualization is enabled in the BIOS. It has the latest available BIOS and firmware for everything as well. Searching this thread and the forums in general I couldn't find anything that applied to it working previously, but then stopping after an update.
  5. Running 6.8.3 and the latest nerdpack and for a few months now par2cmdline has been showing there's an update, and i see it on the github repo, but when I go to update it within the nerdpack UI it says the package is missing. Is there an alternate way to get it updated?
  6. That did it. Changed values and it populated before I even saved. I saved, then changed them back, and we're good. THANK YOU! Excellent product/design and amazing support.
  7. Hey @falconexe. First off - thanks for the lesson on doing the cpu information the "old" way. I explored doing that, but then I took the time to dive into the regex and it was ridiculously simple. I also finally got back to the UPS portion and I did figure some things out with the UPS stats. It seems that any panel that utilizes a variable is not getting parsed. The variable doesn't seem to get included in the query.. for example in this query: SELECT last("load_percent") * .01 * $upsmaxwatt/1000 FROM "apcupsd" WHERE $timeFilter GROUP BY time($__interval) the "$upsmaxwatt" isn't getting passed, the query inspector shows "error parsing query: found /, expected identifier, string, number, bool at line 1, char 37". This error is happening with each variable and I cannot for the life of me figure out why the variable isn't getting passed - they are all filled out. For giggles I installed a different panel that includes UPS stats (Unraid System Dashboard v2 from @GilbN) and the UPS data on his works out of the box, and other than the variable names they appear identical in query structure. Thoughts? Anything else I can supply or look at to help figure this out? Thanks!
  8. Thanks @falconexe - I'll check out that regex stuff and hopefully figure it out. As for the telegraph setup - how I am setup matches post #1/your screenshot - I verified in the config, I am using the GUS config from @testdasi. I did delete both telegraph and influx configs and got default ones before checking everything lined up with the above as well. Any other thoughts or information I can provide to help diagnose? Thanks!
  9. I am loving GUS + UUD! Thanks to both @testdasi and @falconexe for your amazing work! I am experiencing a couple of hurdles. First, I cannot figure out the CPU regexes. I have 2 CPU's each with 4 cores. (quad core Xeons). So they all show up in the CPU01 graph, which I am fine with just removing the 2nd one and having them all in one graph, but I'd prefer two graphs. If anyone can get the regex for that (or point me in the right direction) I would be very grateful. Secondly, I am trying to get UPS data and I'm getting query errors. I set my UPS db variable correctly, apcupsd is running on unraid and it can connect to my UPS. { "request": { "method": "GET", "url": "api/datasources/proxy/9/query", "params": { "db": "apcupsd", "q": "SELECT last(\"load_percent\") AS \"UPS Load\", last(\"load_percent\") * .01 * AS \"Watts\" FROM \"apcupsd\" WHERE time >= now() - 12h GROUP BY time(30s)", "epoch": "ms" }, "data": null, "precision": "ms", "hideFromInspector": false }, "response": { "error": "error parsing query: found AS, expected identifier, string, number, bool at line 1, char 74", "message": "error parsing query: found AS, expected identifier, string, number, bool at line 1, char 74" } }
  10. I am loving GUS - I imported UUD - does your implementation of telegraph include ipmi tools? (https://selfhosters.net/docker/telegraf/ipmi/) Just trying to figure out if I need to do that or not. Also - does your influxdb have any default credentials? Please forgive me if you have documentation somewhere with this, I can't find it.
  11. So now I'm back to npm presenting a locally signed cert instead of the LE cert and I can't proceed. This is making no sense to me. Anyone have any insight?
  12. After running this for a good long while now, I started out having the same issue that many folks are posting about - Internal Server Error when trying to add a new proxy host and request a new SSL Cert. However, I deleted and recreated the docker and it's appdata and now that part works. However - the Access List functionality doesn't seem to be working - instead of prompting to enter a username / password, instead it just goes 403 forbidden. If I disable the access list on a host and change to publicly accessible it works. I don't show anything in the logs of the container - is there another place I can look to see why its just tossing me right to a 403 instead of prompting for credentials like it always had? Note that I am using Brave primarily for my browser, but the same thing occurs in Firefox, Chrome, Edge, and Safari. Thank You!
  13. I am trying to update par2cmdline and I am getting "par2cmdline-0.8.0 package missing!" Am I doing something wrong?
  14. This is now resolved. So I found this post regarding my NIC and I also realized it was also about my exact system board. So I did what worked for them - powered down and unplugged. Powered back up and BOTH NICs were dead with -2 error code. I looked at the back of the machine and one of the ports lights were solid. So I unplugged from power again, and pulled the cables out of both, powered back on. And BOOM - both eth0 and eth1 are present. The (apparent) issue: BOTH of my patch cables. Neither one would allow either port to link up after both eth0 and eth1 were back. Replaced both, and I'm back in business on BOTH. I am so happy. Lesson: It's (almost) always a simple and (sometimes) stupid solution.
  15. I know for certain it worked under 6.8.0, and am fairly certain it worked under 6.8.1 as well. Have tried both, although I did not do 6.8.0 as a fresh USB build. In your opinion might that make a difference?