LittleMike
-
Posts
54 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by LittleMike
-
-
Just now, ljm42 said:
At the time of the diagnostics, resolve.conf was broken, which led to the My Servers error message because DNS did not work.
I don't know what caused the issue but it wasn't My Servers. My Servers was simply alerting you to the problem.
6.11.5 is the best stable version of Unraid currently available.
At the time of those diagnostics there was a problem with the resolve.conf file. Checking for plugin updates likely would have failed during this time, probably other things as well. If nothing you care about fails then simply ignore the message. Or you can troubleshoot further as mentioned above, up to you.
That would make sense. If local DNS is broken, then it can't resolve anything, not just *unraid.net. Why would container lookups succeed, though? That's the part I don't understand. Like trackers, indexers, etc that are all reaching out to DNS all the time.
Another question - how could resolv.conf even break? Doesn't dnsmasq run on startup and that's it? Nothing should be writing to resolv.conf (or overwriting) for it to break in the first place.
Strange, normally when there's a new version, I get a banner across the top of the web GUI (I always have a tab open in my browser to it). I have no issue doing the upgrade to 6.11.5, I was just completely unaware of it.
-
On 11/29/2022 at 3:50 PM, ljm42 said:
So looking at logs/syslog.txt, early on I do see that DNS looks like it was setup correctly:
Nov 9 22:36:22 BlackPearl dnsmasq[11285]: reading /etc/resolv.conf Nov 9 22:36:22 BlackPearl dnsmasq[11285]: using nameserver 192.168.1.1#53 Nov 9 22:36:22 BlackPearl dnsmasq[11285]: read /etc/hosts - 2 addressesBut then yesterday, the DNS configuration broke:
Nov 28 07:27:34 BlackPearl dnsmasq[11285]: no servers found in /etc/resolv.conf, will retryI don't know what would cause that, but it would mean the server could not do DNS lookups which explains the error message from My Servers. I also can't tell if it was fixed? What do you get if you open a web terminal and run:
cat /etc/resolv.conf
Looking at system/plugins.txt, we can see that at the time diagnostics were taken, the system was not able to download the list of current plugin versions for comparison:Could not download current plugin versionsSo something was going on with your server's networking (likely the broken DNS) and the error message from My Servers is another symptom of it.
My recommendation would be to upgrade to 6.11.5 (not much point in troubleshooting an older version). Then if you see the error message again, try checking for plugin updates, I imagine it will fail. Grab a fresh diagnostic and post to General Support asking for help with a networking/dns issue. Feel free to tag me, but I'm hoping someone else will see something that I don't.Resolve conf looks just fine to me. I am also not currently having the My Servers plugin issue, so it's kind of a chicken and egg thing right now. Is 6.11.5 stable? I've only run the stable editions. Strangely enough, I don't think I had these problems on 6.8. They only started with either 6.9 or 6.10.
~# cat /etc/resolv.conf # Generated by dhcpcd from br0.dhcp nameserver 192.168.1.1
I did see an "unavailable" message in the Docker tab next to all the dockers now that I've looked. I had no reason to check previously because I saw no other symptoms related to DNS. Like I said, all my external facing front ends work, all my docker container lookups worked (like the Arrs, etc). So as far as I'm aware, only unraid.net related things broke. Which still could point to an unraid issue, not a networking issue. Does community apps filter through *unraid.net? -
2 hours ago, ljm42 said:
It sounds like there was an intermittent problem, either on our end or on your end or somewhere in between.
We haven't widely announced it, but you are welcome to check our new status page when you are having issues:
https://status.unraid.net/
I don't see any evidence of a problem on our end, so that means it was likely on your end or somewhere in between.This is a DNS error. It likely means that the network connection between your server and your DNS server was down.
If the only thing that is affected is this error message then you can probably just ignore it. However, if your whole server has network connectivity issues during this time then this is a symptom and not the cause.
The whole diagnostics would have been helpful because I could have looked for other evidence that DNS was having issues. I assume everything is back to normal at this point? If it happens again, please grab diagnostics while the problem is happening.
Just to be clear, when you say "the My Servers plugin fails" what exactly do you mean? Is this error message in the upper right corner of the page the only evidence of a problem or is there something more? I just want to be sure I am understanding the issue.
No the server is not pingable. The status website mentioned above would be a good way to see if the problems on our end.
Again, nothing on my network is having an issue. The server itself did not appear to be having any issues other than DNS lookups to unraid.net failing. I took a diagnostics snapshot, I just didn't upload it. You can find it here. I didn't do a deep dive, but like I said, everything else is working just fine as far as I can tell. All my containers and VMs are running, including outside facing frontends with external URLs
-
On 11/10/2022 at 6:21 PM, ljm42 said:
Sorry you're having trouble. There are several error messages discussed in this thread, can you please show a screenshot of the one you are currently getting along with a description of how long you've been seeing it, whether it is intermittent, etc? Please upload your diagnostics.zip as well (from Tools -> Diagnostics)
Note that we were having some issues yesterday which could have resulted in some error messages, but those have been resolved:
https://forums.unraid.net/topic/112073-my-servers-releases-and-announcements/#comment-1189788
Same issue as the other poster, like I mentioned. It resolved itself, but then just happened again today. I got this error:
ERROR [getaddrinfo ENOTFOUND mothership.unraid.net]Do you want the whole diagnostics file? Because everything else is working just fine. It's just the My Servers plugin that fails and every single time it appears mothership.unraid.net becomes unavailable. Is it normally pingable? Because it's not as I type this.
-
On 11/3/2022 at 4:29 PM, ljm42 said:
Thanks for the diagnostics. Your logs have a bunch of this:
Nov 3 13:36:26 BigBoss nmbd[19247]: [2022/11/03 13:36:26.642310, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Nov 3 13:36:26 BigBoss nmbd[19247]: Packet send failed to 192.168.122.255(137) ERRNO=Network is unreachable Nov 3 13:36:26 BigBoss nmbd[19247]: [2022/11/03 13:36:26.642361, 0] ../../source3/nmbd/nmbd_packets.c:1639(retransmit_or_expire_response_records) Nov 3 13:36:26 BigBoss nmbd[19247]: retransmit_or_expire_response_records: Failed to resend packet id 17179 to IP 192.168.122.255 on subnet 192.168.122.1 Nov 1 11:39:44 BigBoss kernel: TCP: request_sock_TCP: Possible SYN flooding on port 25871. Sending cookies. Check SNMP counters.
So something is causing your network to go offline. The My Servers messages are a symptom of the network going down, not the cause.I'd recommend opening a new thread in the General Support area of the forums, be sure to include your diagnostics:
https://forums.unraid.net/forum/55-general-support/
Before doing that you might want to uninstall the plugins marked as incompatible with Unraid 6.11.1. And if you want to rule out My Servers as the source of the issues feel free to uninstall it as well - although I hope you'll reinstall it once your underlying problems are resolved
Considering so many people are having this same issue, why would you think we are all having network issues? My network has been rock solid both on the LAN and WAN side and I'm getting this same error. Have been ever since the upgrade to 6.11.1.
-
Sorry if this is a dumb question, but the CA template shows the current version of Tdarr includes node. So do I still have to install the separate node container?
Reason I ask is I'm currently trying to set this up for the first time and even though docker run finishes successfully, the logs are showing me:
Please make sure the IP and Port are correct else it may be a firewall issue. �[91m[2022-04-09T12:54:42.350] [ERROR] Tdarr_Node - �[39mNode: 192.168.1.100:8267 - nodeID 'InternalNode1' could not be contacted by the server.Not sure what I'm doing wrong. I haven't installed the separate container yet, figuring I want to try to get this running as is first.
Okay, so I have a clue but not how to fix it. The port assignment in the error log entry says it's trying to reach the InternalNode1 on port 8267 but nowhere is that configured in the template, nor does it show up in the docker run. So something internal is trying to map that port.
EDIT 2:
So poking around paid off. There's definitely something wrong with the template/image. The Tdarr_Node_Config.json file that gets automatically created on startup configured the following:
"nodeID": "InternalNode1", "nodeIP": "192.168.1.100", "nodePort": "8267",I didn't set 8267 anywhere, so that's where it came from. Edited the json file, restarted the container, and all was well. So perhaps this is the issue a few posters above me had where they couldn't get the internal node working and had to set it to false and add the node container. Check the json file, edit it, ???, profit!
-
5 minutes ago, JonathanM said:
Your VPN login credentials.
Okay, good. That's a starting point. Though I'm at a loss as to how that could be because nothing has changed on my end other than the container updated.
*EDIT* That did it @JonathanM! All I did was go back to the container, put in my username and password (I noticed it was the older style one that PIA used) and then the UI came back up after a couple of minutes. Thank you.So next question is, what does the webui have to do with a wrong username/password for a VPN provider? Technically the container should still start, no?
-
8 minutes ago, JonathanM said:
That would be the first thing to fix.
I would if it gave any indication as to what it's failing auth on:
2021-11-17 20:49:21,991 DEBG 'start-script' stdout output: 2021-11-17 20:49:21 AUTH: Received control message: AUTH_FAILED -
11 minutes ago, wgstarks said:
Attach your supervisord log to your next post after redacting user/password info.
I don't even see a username or password in that log file. I do see some failed auth errors though. Think it's okay to still post it raw or should I dig deeper?
-
I noticed today that deluge had updated and now the web interface won't load. Any thoughts on how I can troubleshoot this? I can't make sense of the logs, but it looks fine to me.
-
3 hours ago, yogy said:
Just go to Settings >> Tools >> Export Vault and you are good to go
Thanks!
2 hours ago, JonathanM said:That assumes a single user only unless I missed something.
How would you go about it if you have many friends and family members each with their own vault?
In my case, I only have 1 vault, 1 user, myself. So my setup is simple enough that this should be enough.
-
4 hours ago, yogy said:
Looks normal, but missing some rows. For some reason it doesn't start or it's stuck. I'm out of ideas. I would make a passwords backup, delete current container and make a new one and then import your passwords.
That's the thing - it's running and working just fine. The only thing I can't do is edit it in the unRAID GUI. The container itself is otherwise normal.
What is the best procedure for backing up/importing passwords? I believe I had to do that once in the admin panel. Anything I should worry about?
-
11 hours ago, yogy said:
No worries, upload logs (left clink on bitwardenrs icon>>logs>>copy and paste here), maybe something is there that could help us solve this. In worst case scenario, you'll make a backup of your passwords, delete current container and make a new one and then just import your passwords.
So unfortunately, I don't think there's much here to go on:
/--------------------------------------------------------------------\ | Starting Vaultwarden | | Version 1.22.2 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Send usage/configuration questions or feature requests to: | | https://vaultwarden.discourse.group/ | | Report suspected bugs/issues in the software itself at: | | https://github.com/dani-garcia/vaultwarden/issues/new | \--------------------------------------------------------------------/ [INFO] No .env file found. [WARNING] The following environment variables are being overriden by the config file, [WARNING] please use the admin panel to make changes to them: [WARNING] SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, ADMIN_TOKEN [2021-10-28 22:13:43.893][parity_ws][INFO] Listening for new connections on 0.0.0.0:3012. [2021-10-28 22:13:43.895][start][INFO] Rocket has launched from http://0.0.0.0:80 [2021-10-28 22:13:50.440][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.31:60252. -
12 minutes ago, yogy said:
Hmm, can you access the log files. Post them here if you can.
I'm at work right now so unfortunately I won't be able to get to that till tonight. Do you want a screenshot of the left-click Show Logs or is there a particular log file you want me to upload? I can do either tonight.
-
3 minutes ago, ChatNoir said:
Other Unraid users experienced this, some managed to solve it :
And many others, if those topics don't directly help, try google i801_smbus unraid
Actually I never resolved it if you read through my post. I just uninstalled the plugins and gave up.
-
3 hours ago, yogy said:
OK, try to left click on the name of the container, not the icon. That should show you the template and try to change the repository there.
The name isn't clickable. Like if I go to the container above it, it will underline it showing it's a link and I can do that. Can't do that with the bitwarden one for some reason.
-
Okay, so I was checking out my docker containers and saw there was an update for my bitwarden_rs container. Tried to update it and got the message that basically told me something was wrong/usually a repository change.
Here's where I am now stuck. The instructions to upgrade said to stop the container, edit the repository, fix common problems, etc. Except I can't edit the container to update the repo. My guess is I need to basically start fresh. How can I do that without losing all my passwords?
-
38 minutes ago, trurl said:
Everything about your configuration is in the config folder on flash. Did none of it survive?
The config was busted. I copied templates over so I could redo my containers. When I tried to reassign my drives (I copied the super.dat file over), it was all messed up. Said my largest drive was part of the array and my second largest drive was the Parity and I had to do a Tools->New Config. It's currently rebuilding. Usually takes about 28 hours, so I'll have to mess with other stuff later.
Most everything is back up. Plex was the biggest problem. Kept getting bad parameter when trying to launch it. It didn't keep any of my IP settings. Nothing. A few of the others were like that as well. So something definitely got hosed and the backup just copied it over. -
Just an update - something must have broken during the outage and botched my config. Unfortunately the My Servers backup was broken as well. Formatted the original USB stick and did a clean install and the new NIC card worked. Now the fun process of reconfiguring things. I guess this can be marked solved.
-
Hello all,
I'm at a complete loss. I had an outage the other day in the overnight hours. When I woke up I had no internet. The cable company quickly restored that but then I noticed my unRAID server had no network connection. Not sure if it lost power or not. In either case, I took a look and I had no link light on the onboard NIC. Thinking maybe something blew out, I ordered an Intel 82576 based board. I'm currently running unRAID 6.9.2.
I installed the new card and while it's in the pre-boot environment, I have link light. Great! Except not great, because as soon as it gets into unRAID, it's like the card shuts off. No link light. I confirmed the cable is working by using it on a laptop. I confirmed the port on my switch is working as well. I even tried using the My Servers function to restore a recent backup to a different USB stick. All the same results. I have zero network connection on either the onboard as well as the Intel PCIe card no matter what I do. Anyone have any ideas? My server has been entirely down and I would like to get it back up. -
Okay, so I think there were some steps that were missing.
I deleted the pool, started, stopped the array, created a new pool, started the array and nothing had changed and it didn't give me the option to format. So I stopped the array, clicked on the cache pool and selected Erase. Restarted the array and it yelled at me "Unmountable: Unsupported partition layout"
Going to try messing around with trying to get it formatted.
*EDIT* A combination of deleting the pool. Start/stop array, create pool with no drive assigned, start/stop array, assign the drive, then the Format checkbox appeared. Now to copy my data back over and cross my fingers. -
1 minute ago, trurl said:
If you have more than one pool they must have different names so you can work with them separately. "Cache" is the name of the pool from pre 6.9 releases, so that is what your shares are likely configured to use and any path to cache you might have specified explicitly.
Ah that totally makes sense. Yeah, this is on 6.9.2 but was set up on whatever revision it was 3 years ago or so, so definitely pre 6.9. Okay, currently backing up the contents of /mnt/cache. I should just need appdata, domains, downloads, and system, right? Do I need to back up from anywhere else like /mnt/user0 or anything?
-
3 minutes ago, trurl said:
Changed the order for you.
You don't want a different pool (name) in the end or you will have to deal with reconfiguring some things to use a different pool.
Okay, so remove old pool first.
I didn't even realize you can name the pools. I should make the new one just "Cache" like the existing one. Is that why you suggest removing the old one first, because the defaults should do what I want? -
6 minutes ago, JorgeB said:
Depends on the state of the failing device, also and if using the array as destination make sure you rsync to a disk, or use /mnt/user0/share.
Make a new pool of the remaining device only and format it, you can wipe it first.
Okay. So let me see if I got this right:
Copy everything from /mnt/cache somewhere (rsync to /mnt/user0/share or to a disk, or WinSCP to another machine, whatever, correct?)
Create a new cache pool of 1 device using the new/working drive
Format new drive
Copy everything backed up to new drive
Remove old pool
Restart docker services/VM's etc.
Is that it? Just copying back all of the data will line everything up correctly? Is that because the configuration is on the OS drive? So is the profile information stored on the cache pool instead? I'm just trying to figure out how this happened in the first place so I can prevent it from happening again.
Failed resolving https://mothership.unraid.net
in Connect Plugin Support
Posted
I have them all on a custom bridge behind a Traefik reverse proxy, so they should all be using the host DNS. So yeah, definitely a mystery as to why they still worked while resolv.conf was broken.
I just updated to 6.11.5 and took a "clean" diagnostics file (everything is working, including the My Servers plugin, which immediately told me to update after the OS upgrade.)
Now I'm curious to see if the issue still happens. If resolv.conf is breaking, that would point to dnsmasq being broken. Otherwise nothing would be overwriting resolv.conf.
As far as mysteriously working again, I may have the answer to that - I rebooted the server because I was tired of the big red triangle staring at me. Stopped the array, performed a reboot, everything worked for like an hour, then the My Servers plugin complained again. I did not check resolv.conf, but it's quite possible it was also broken.
If it happens again, I'll make a new post with a new diagnostics file in the general forum. Thanks again.