rdagitz

Went back to 6.11.3. I had changed my cache pool to zfs so BEFORE the downgrade, I moved everything off of cache, formatted the drives to btrfs and then recreated the cache pool AFTER the downgrade. Maybe that was overcautious ... but I had no problems. Here are the instructions I followed for the downgrade: https://docs.unraid.net/unraid-os/manual/upgrade-instructions/#manual-upgrade-or-downgrade

Anyone know how to downgrade to a version of Unraid to avoid this issue until someone gets this figured out?

This server is still behaving strangely, even after changing to ipvlan. Upon one restart I noticed this in a section of a log: These are the only "errors" on the syslog (and these appear to be something for which the kernel is looking and moving on). The log is cleared upon reboot. Are there no persistent logs that I can use to figure out what is going on?

I found the following directions on another posting and walked through them: Will let you know how things go.

I did a little more digging and found a warning one time from Fix Common Problems If I rescan the system, the warning is not there. Thoughts?

About every 24 to 48 hours one of my Unraid servers keeps locking up. I cannot access it via web, ssh or anything. There is also no output to a connected monitor. I have to force shut down the server. When restarted, the log is recreated and I have no information to track down the problem. This problem began when I upgraded to 6.12, but in doing so I also updated some plugins updated dockers and had to recreate the cache drives (The btrfs partitions corrupted so I switched them to a zfs raid1 and restored the appdata from a backup.) With all of these changes, I cannot tell if the issue is hardware, a memory leak of a docker app, the upgrade to 6.12 or what. Is there some other log that I can dive into to find the issue? I am attaching the diagnostics just in case there is something I am missing from them. server-diagnostics-20230627-0802.zip

I will check that and get back to you.

So ... can anyone help me? I have one Unraid server that is still not able to "connect to Mothership?" I am running the latest version of the plugin. <-----UNRAID-API-REPORT-----> SERVER_NAME: ciserver ENVIRONMENT: production UNRAID_VERSION: 6.11.5 UNRAID_API_VERSION: 3.1.1 UNRAID_API_STATUS: running API_KEY: invalid MY_SERVERS: authenticated MY_SERVERS_USERNAME: rdagitz CLOUD: STATUS: [error] MINI-GRAPH: STATUS: [PRE_INIT] ERROR: [API Disconnected] SERVERS: ONLINE: OFFLINE: ciserver[owner="rdagitz"] ALLOWED_ORIGINS: </----UNRAID-API-REPORT----->

Of the 6 servers I have on my account, now 3 of them "cannot connect to mothership." Is there some log file or something that can be analyzed to find out what is going on?

BTW: I have signed out and signed back into MyServers on that server, rebooted the server and still get the error.

I have multiple servers connected to my MyServers account. One of them is not connecting correctly. I ran the following: unraid-api report -v Here is the results: <-----UNRAID-API-REPORT-----> SERVER_NAME: ciserver ENVIRONMENT: production UNRAID_VERSION: 6.11.5 UNRAID_API_VERSION: 2.57.0 UNRAID_API_STATUS: running API_KEY: valid MY_SERVERS: authenticated MY_SERVERS_USERNAME: rdagitz CLOUD: STATUS: [error] ERROR [Unable to connect to https://mothership.unraid.net] MINI-GRAPH: STATUS: [ERROR] ERROR: [API Disconnected] TIMEOUT: [29.333s] SERVERS: ONLINE: OFFLINE: ALLOWED_ORIGINS: http://localhost, https://localhost, https://ciserver.local, https://IPV4ADDRESS, https://ciserver, https://IPV4ADDRESS.HASH.myunraid.net, https://2001-0470-c44d-c001--2.HASH.myunraid.net </----UNRAID-API-REPORT----->

Well, I don't know if this is a "solution" but it worked. I changed to the linuxserver/emby:4.8.0-beta and the problem went away. What I don't know is if the switch to beta or the switch to the linuxserver version did the trick.

OK, so I am slow. Actually goes under "Extra Parameters." For those who do not know, Click on Emby in Docker list Choose Edit Toggle the Basic View switch to change to Advanced View Add the code on the Extra Parameters line. All of that said, I made the change and still Emby is crashing with an "out of memory" error. Anyone?

I did find this post: https://forums.unraid.net/topic/120837-out-of-memory-on-v692/ and tried adding a variable in Emby's docker with the value: --mount type=tmpfs,destination=/tmp,tmpfs-size=8589934592 Made no difference

The error just started happening and keeps happening with Emby. I think I have been able to use Emby for about 20 minutes before the error happens again and shuts down the Emby docker. Any suggestions on how I can discern what started the problem?

My main server keeps giving an "out of memory" error and shutting down Emby. Thoughts? jonesserver-diagnostics-20230409-2231.zip

OK, true confessions. It was operator error (and dredge999, you were right on target). I have been working on two different Unraid servers. I had the specs in mind of the other server when working on this one. It turns out that I need to add RAM to this server to get more power. Problem solved.

OK, this is weird. If I leave the RAM allocation at the minimum setting in the VM template (4GB for Windows 11), the machine boots and runs. The moment I increase the RAM at all, I get the error, even after the installation is complete.

I am running into this error just trying to install the first VM. I have tried multiple browsers and get the same error each time. Community Apps is up to date. How can I even connect to the VM if setup will not finish? Ideas?

Discord chat for Unraid is amazing. From terminal I ran ssh-keygen -t dsa -f /boot/config/ssh/ssh_host_dsa_key and set no password. Reboot the server. The most important lesson to learn from my folly: BACK UP YOUR USB DRIVES!

While creating a backup between 2 Unraid servers, I deleted "ssh_host_dsa_key" and "ssh_host_dsa_key.pub" in /boot/config/ssh/ on one of the servers. I was setting up an SSH connection between the two machines and could not get my own key to work. (Turns out I had just missed a step.) While deleting what I had created, I misread something and deleted those files by mistake. Thoughts?

I have two servers: Primary and Offsite. (Offsite is a backup server for Primary.) Both Primary and Offsite were using Duckdns. A few weeks ago I switched Primary to use Cloudflare with my own domain. Primary, Offsite and my laptop are connected to my Zerotier network via the shared Zerotier Nework ID. Before making the change to Cloudflare for Primary, I could turn on the Zerotier client on my laptop and connect to Primary and Offsite without a problem. Now I can only reach Offsite. Primary is not accessible. Any ideas why?

+1

To clarify, I do not know if the ssh key needs to be re-approved any other time, but I can confirm that I do have to confirm it after a restart of the Primary Unraid server.

Just today I had to renew the "approval" for the ssh key. Once I said "yes" I ran the rsync backup without any hesitation. Just now I restarted my Primary Unraid server, ran the rsync command and had to confirm "approval" again. So would I be right to say that ssh keys are not persistent over reboot? How do I fix this?