ljm42
-
Posts
4,469 -
Joined
-
Last visited
-
Days Won
32
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by ljm42
-
-
Are you saying the /var/log/unraid-api/stdout.log continues to grow after uninstalling the plugin? It should not.
If so, please show me the output of this command
ps -ef | grep unraid-apiEdit: actually, please upload your current diagnostics too
-
1
-
-
4 minutes ago, craigr said:
I logged out of and then uninstalled Unraid Connect. I cannot sign back in. This can't be affecting the log, can it? Should I reinstall the plugin?
Sorry, I'm confused. If you uninstall the Unraid Connect plugin then the sign in box will be removed from the upper right corner of the page and you won't be able to sign in to Unraid Connect from within the webgui. Uninstalling the Unraid Connect plugin will have no effect on logging in to the webgui as root.
If that doesn't answer your question, please show a screen shot to help me understand the issue
-
1 hour ago, craigr said:
I didn't know healthcheck was enabled by default in unRAID Docker containers.
It is actually up to the container, depends on whether it has code to run healthchecks.
I don't know if the other containers you mentioned have code to run healthchecks, don't think I have seen anyone suggest disabling it on them. But it shouldn't hurt to disable it.
I don't yet know if everyone should disable healthchecks on Plex, but if they are having issues with containers not being able to restart I will suggest it.
For anyone else reading this, if you have the NVIDIA plugin installed be sure it is up to date. Plex healthchecks with older versions versions of the NVIDIA plugin will definitely cause issues.52 minutes ago, craigr said:I am seeing this in stdout.log.
Unraid-api will log activity to help with troubleshooting, the logging shouldn't be a problem (just to repeat for anyone else who stumbles on this - the unraid-api currently logs up to 10MB before rolling the log, in the future that limit will be reduced. Alone it is not enough to fill the 128MB log partition on Unraid)
Based on that log snippet I'd suggest signing out of Unraid Connect and then signing back in. If you have further questions about the actual contents of the log, please go to Settings -> Management Access -> Unraid Connect and see the section about Unraid-api logs. They could have confidential information so I'd suggest not posting them publicly.
-
1
-
-
1 hour ago, namida said:
You can access the webui just after booting up, but you can’t access it after a few hours after booting up.
We are working on issues related to ipv6. For now I'd recommend going to Settings -> Network and configuring the system for ipv4 only
Also, it looks like you might be having issues when stopping the array. See https://forums.unraid.net/topic/141479-6122-array-stop-stuck-on-retry-unmounting-disk-shares/#comment-1281063
-
11 hours ago, craigr said:
Is this the My Server plugin or whatever it's called that now seems to be integrated into unRAID? I've had loads of issues with it in the past.
The unraid-api/stdout.log grows to 10MB and then is rolled. In the next Connect plugin release we're going to reduce the size it can grow to, but even so there is no way that by itself it will fill the 128MB log partition. But why don't you go ahead and uninstall the Unraid Connect plugin for now, just to rule it out
TBH if there are any other plugins you can live without, it may help to simplify the system by removing as many as you can.
You run Plex right? Go into your Plex Docker container settings, switch to advanced view, and add this to the Extra Params
--no-healthcheck-
1
-
-
When you run losetup, does /dev/loop1 point to /boot/bzfirmware? If so, that does *not* need to be unmounted to stop the array (and it shouldn't be). Same with /boot/bzmodules.
The one loopback that does need to be unmounted is docker.img
-
10 hours ago, craigr said:
I am also having an issue with 6.12.x where every time I shutdown it is not clean and when my system starts back up a parity check begins.
-
1
-
-
This test will be improved. But you can prevent the warning in the meantime by deleting config/vsftpd.user_list from your flash drive.
-
1
-
-
-
Unrelated to the release, you can turn help on/off by clicking the question mark icon in the upper right corner of the page.
-
So the system is on 6.11.5 now right? Is the delayed bootup a new problem on that version or has it always been that way?
-
udev is what detects your hardware. For whatever reason this system is slow to respond about what hardware is connected.
It might(?) help to go in your bios and disable things you aren't using, like bluetooth, wifi, serial ports. You could try messing with USB settings, like enable/disable legacy mode. Just some ideas, no guarantees : )
-
So at this point is everything good?
-
Unraid Connect doesn't yet support reverse proxies. To use Unraid Connect you need to access the server through one of the URLs listed on Settings -> Management Access.
-
Think of Unraid as an appliance, you want to modify the OS as little as possible. You should run apps like this in a Docker container, PiHole is a pretty popular one. We generally recommend that Unraid use public DNS servers like 8.8.8.8 to reduce issues with accidental blocking and increase stability when the container isn't running.
-
50 minutes ago, comet424 said:
and none of the dockers work... is it because i had upgraded to 6.12.2
Yes, but there is a quick fix. This is from the 6.12.0 release notes:
Quotehttps://docs.unraid.net/unraid-os/release-notes/6.12.0
If you revert back from 6.12 to 6.11.5 or earlier, you have to force update all your Docker containers and start them manually after downgrading. This is necessary because of the underlying change to cgroup v2 starting with 6.12.0-rc1.
-
10 hours ago, eggman9713 said:
So now it seems to be behaving itself on my server.
That is what makes it difficult to track this down : ) but we're working on a solution.
15 minutes ago, wicked_qa said:I've been struggling with this issue, and this solved my problem. Thank you!
Thanks for confirming this resolved the issue with the stopping the array, we're working on a solution
-
1
-
-
The API looks good.
If you are still seeing a message that says "disconnected from Unraid API" then it is likely you have ad blockers or extreme privacy settings getting in the way. Try a different browser or a clean browser profile.
-
We are working on a fix for nginx with IPv6 but for now you should go to Settings -> Network Settings and change eth0 to "IPv4 only" if that works in your environment.
Also, please see my comment here about browsers potentially causing issues with backgrounded tabs:
-
wanip4.unraid.net doesn't respond to ping, so no errors there.
Your screenshot is cutoff, is there a "restart API" option? If so, go ahead and click that. If you don't have that option, open a web terminal and type:
unraid-api startwait two minutes, then:
unraid-api reportand paste the results back here
-
UPDATE! please see my comment further down in this thread https://forums.unraid.net/topic/141479-6122-array-stop-stuck-on-retry-unmounting-disk-shares/#comment-1283203
-------------------------------
Original message:
-------------------------------
I hit this today when stopping my array.
Here is what worked for me, would appreciate if someone hitting this would confirm it works for them too.
To get into this state, stop the array. If you are having this issue you will see "retry unmounting shares" in the lower left corner. Note: There are other reasons this message could happen (like if you left an SSH terminal open while cd'd into the array). This discussion assumes none of the usual suspects apply.
In a web terminal or SSH type 'losetup'. In my case it showed:
root@Tower:/etc/rc.d# losetup NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC /dev/loop1 0 0 1 1 /boot/bzfirmware 0 512 /dev/loop2 0 0 1 0 /mnt/cache/system/docker/docker.img 0 512 /dev/loop0 0 0 1 1 /boot/bzmodules 0 512The problem is that docker.img is still mounted. Note that in my case is it on /dev/loop2
Then run `/etc/rc.d/rc.docker status` to confirm that docker has stopped:
# /etc/rc.d/rc.docker status status of dockerd: stopped(It should be stopped, since you were in the process of stopping the array. But if Docker is still running, you can type `/etc/rc.d/rc.docker stop` and wait a bit, then run status again until it has stopped.)
Then to fix the problem, type:
umount /dev/loop2(use whatever /dev/loopX docker.img is on, as noted above)
Once that is unmounted, the array will automatically finish stopping.
We are looking into a fix for this, but it would help if we could reliably reproduce the problem (it has only happened to me once). If anyone is able to identify what it takes to make this happen I'd appreciate it.
-
4
-
9
-
5
-
-
Do you have any Docker containers running on port 80 or port 443?
nginx is refusing to start because something is already on port 80:
Jul 5 18:15:20 PLEXBOXX nginx: 2023/07/05 18:15:20 [emerg] 1797#1797: bind() to [::1]:80 failed (99: Cannot assign requested address)The usual cause is a port conflict with a Docker container. However, a conflict with port 80 should also affect 6.9.2 so I'm somewhat confused.
I'd suggest carefully editing config/docker.cfg on the flash drive and change this:
DOCKER_ENABLED="yes"to this:
DOCKER_ENABLED="no"
Then reboot. The webgui should load after this. Then you can try starting Docker and probably one of your containers won't be able to load.You can either change the port that container uses, or go to Settings -> Management Access and change the port that Unraid uses for HTTP and HTTPS. We recommend you pick high numbers between 1000 and 64000.
-
Are you intentionally using a non-standard netmask for your network?
NETMASK[0]="255.255.254.0"If that isn't intentional, edit config/network.cfg on the flash drive and change that to:
NETMASK[0]="255.255.255.0"then reboot. If there are still issues please provide updated diagnostics.
-
What version of Unraid are you currently running?
We improved the killswitch in 6.11.2 (after your previous thread) but it does require you to make a dummy change to the tunnel and apply.
Please follow the first post of this guide closely to setup the tunnel and container:
https://forums.unraid.net/topic/84316-wireguard-vpn-tunneled-access-to-a-commercial-vpn-provider/
If you are able to bypass the kill switch using a tunnel created/modified in 6.11.5 or 6.12.2 please provide details on how to reproduce the issue
No space left on device (28) on login attempt.
in General Support
Posted
Why does a Plex Docker container have access to the server's /tmp directory?