tjb_altf4
Members
-
Joined
-
Last visited
Everything posted by tjb_altf4
-
Sounds like the same issue Ive mentioned before a few times, but my issue occurs using deluge's scheduler
-
Give your network equipment a reboot, and make sure if you had setup DHCP reservation that you also updated the MAC address for the new mobo/nic.
-
I had this briefly this morning, I only saw the logs this afternoon. Coincided with shares not being reachable temporarily, which eventually resolved itself, but I've never seen this in logs before.
-
Yep, I've had this setup for a few years now, works easily with both API and black hole methods.
-
For docker, It still needs a (display) driver installed on the host. if it worked with XBMC, you could try installing the DVB plugin and installing the LibreELEC driver pack, a good chance the driver is included there already.
-
OK lots of movement in the last few days. 12U rack build and rails attached to rack + cases Unraid server migrated over to RSV-L4500 case CPU cooler changed to the previously mentioned U9 to fit in the 4U form factor... its comically smaller than the U14S, but seems to keep up for now. With only 8 of 15 bays populated, I can already see the advantages of a backplane loi... maybe the next project. Have some more additions for the server coming, but for today I wanted to stay at the same baseline as much as possible in case I needed to troubleshoot problems.
-
Would have happened around the time I upgraded from RC1 to RC2, but don't recall any issues on first boot... but may have appeared in subsequent reboots. FYI Nvidia plugin had no issues
-
A third tab appeared in the Plugins page called Plugins with Errors, or something to that effect. May have been like that since the last reboot, not sure. These were already installed plugins without issue at the time of install and I happened across them in this error state by chance, a delete and reinstall fixed up the issue.
-
Yes RC2. I've got about a week uptime, so not after a restart... I have however updated my BIOS in the day or so prior to last reboot. Only thing of note happening on the system in the last 24 hrs was a scheduled monthly parity check. No pfsense or pihole (running a Unifi USG as edge router).
-
Not sure if something screwy with my system, CA changes or something else, but the ISCSI, Mellanox & DVB plugins all went into an error state and I had to delete and reinstall to restore.
-
Sorry if it has already been raised as a request, but could CA Auto Update be updated to replicate (or trigger) the network rebuild functionality as added to Unraid as per this thread?
-
Piecing a couple of threads together on the subject, and after a quick test on what the docker run command gets build as, it looks like you can create the network once (via CLI) and then select it in network type from the container template. This would be instead of needing to add custom args on each container. docker network create container:vpn Seems like a neater solution. @bonienl will this still get picked up by the auto rebuild updates you've implemented?
-
I fixed this on my system, it seems ProxyConnection has been deprecated (as per the logs) As soon as I removed RUN_OPTS for ProxyConnection my container worked again. Jackett v0.17.159 : Option 'ProxyConnection' is unknown. EDIT: Didn't see someone else had already pointed this out 😛
-
Based on recommendations and now that I've found stock I've ordered a pair of iStarUSA TC-RAIL-26, and a StarTech Open Rack 12U. That should be enough to finish migrating to a rackmount setup. Transferred my workstation to the RSV-L4500, that has an AIO + 7700K, so no issues with height on this one. Hope to transfer the 1950X server over the xmas break when I've got time off.
-
Not in 6.9.0-rc1
-
Are you running a modern Intel system that natively support thunderbolt, or just using the add in card on something else? Because your board should have a header pin for TB and it should be connected? Without that TB can't reset the hardware.
-
Great plugin! Thanks for your effort! Would just request a future enhancement for a download meter of some kind, thats my only (minor) feedback
-
@ich777 I've just moved to 6.9.0-rc1 and it looks like iSCSI support has been added to the unraid kernel. Is your iSCSI Target plugin still compatible with rc1, or should I wait for the new iSCSI GUI plugin to be complete?
-
Ok so the upgrade to 6.9.0-rc1 has been mostly smooth, however I'm seeing 2 cores stuck on 100% Noticed there are some call traces in logs, which never appeared in 6.8.3 100% usage happens in safe mode also, so not related to plugins. The actual cores in use are rotating. I have rolled back and forward to ensure that it was a clean upgrade, tried uninstalling plugins etc with no change. Usage is irrespective of VM and Docker services running or not, so is something related to core OS. Fresh diagnostics attached fortytwo-diagnostics-20201212-1456.zip
-
Docker page has PHP errors when Docker service stopped. Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 682 Couldn't create socket: [2] No such file or directory Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 866
-
Might be the same issue I see if you are scheduling stop/paused time. Only way to fix is to restart container if thats the case.
-
Request to enhance the docker template editor by adding the ability to disable variables, devices etc and for authors to be able to set the state as default on or off. Use cases: troubleshooting (temporary enable/disable) better templating i.e. author can provide optional variables that might not be used by all users, such as hardware acceleration faster switching between similar configurations
-
So I can consistently get this no connectivity situation to occur now, all I need to do is schedule a pause. BUT, if I schedule it near the end of the hour, or I change the schedule midway through the hour (so it pauses for less than an hour), all connectivity resumes normally. I really believe the connection is being dropped on PIA side due to inactivity, but is staying open (or similar) on the docker side so watchdog scripts aren't kicking in. If there is a way I can check or log this theory, let me know..
-
I think I've found the cause I've my intermitant issues. I've noticed if I schedule "off" time with deluge, when it resumes there is no connection (or rather, torrents cant connect). Maybe PIA killing the connection if no activity? Or a Deluge bug of some kind?
-
The drivers are very new to the Linux kernel, only the 6.9 beta has the newer kernel that supports these.
