saifster

Thanks, i'll look into CUPS. Setting up a VM is my last resort solution. Hoping to avoid any unnecessary overhead on the server if I can avoid it.

Hi all, I'm looking on ideas to find out if a setup is even possible via Unraid. I have a Ricoh C261SFnW - a network capable MFC which is presently connected to my local Wi-Fi network and all my local devices, computers/phones are connected and able to print without any issues. However, I run into trouble when anyone else visiting me tries to connect and use the printer since Ricoh drivers aren't natively available on Windows OS and anyone else needs to download the drivers from Ricoh and install it on their local computer before using my printer. I would like to setup a local print server using Unraid (which I already have setup as a media server/pihole/piVPN etc.) and connect my printer to this (preferably still on Wifi - however, hard wiring it is also possible) so that anyone on my local network can print without needing to install drivers locally on every computer. Any suggestions are greatly apprecaited.

Hello All, I am seeking some information on an MCE error that UNRAID has been throwing out for the past few days now. I was advised to post my diagnostic data and seek assistance here. Any help will be much appreciated. osman-server-diagnostics-20220601-0808.zip

I second this. Works perfectly for me as well

Thank you! I downloaded this and it is working perfectly!

I tried everything and couldn't fix it, so, I ended up switching to a different version of lidarr. Looked up an alternative on the Apps page, installed it and set it back up in a few mins. The sucky part was, the saved configs couldn't be saved, but, since I also have Sonarr/Radarr, I just copied/pasted the indexer/download client info from there... Once pointed to the root folder I let it search and add all my organized media automatically. Took a little bit, but, it's automated, just requires patience.

Hi All, Just discovered lidarr, I was able to install and configure it last night, and it worked great. This morning, there was an update available, after updating, the app will no longer load. If this helps anyone.. here is my log: 2021-04-18 13:29:53.978324 [info] Host is running unRAID 2021-04-18 13:29:54.005206 [info] System information Linux 9c4458b65e49 5.10.21-Unraid #1 SMP Sun Mar 7 13:39:02 PST 2021 x86_64 GNU/Linux 2021-04-18 13:29:54.042859 [info] OS_ARCH defined as 'x86-64' 2021-04-18 13:29:54.142068 [info] PUID defined as '99' 2021-04-18 13:29:54.217478 [info] PGID defined as '100' 2021-04-18 13:29:54.334392 [info] UMASK defined as '000' 2021-04-18 13:29:54.366554 [info] Permissions already set for volume mappings 2021-04-18 13:29:54.409620 [info] Deleting files in /tmp (non recursive)... 2021-04-18 13:29:54.515643 [info] Starting Supervisor... 2021-04-18 13:29:54,992 INFO Included extra file "/etc/supervisor/conf.d/lidarr.conf" during parsing 2021-04-18 13:29:54,992 INFO Set uid to user 0 succeeded 2021-04-18 13:29:55,000 INFO supervisord started with pid 6 2021-04-18 13:29:56,001 INFO spawned: 'lidarr' with pid 56 2021-04-18 13:29:56,003 INFO spawned: 'shutdown-script' with pid 57 2021-04-18 13:29:56,004 INFO reaped unknown pid 7 (exit status 0) 2021-04-18 13:29:56,018 DEBG 'lidarr' stderr output: Cannot open assembly '/usr/lib/lidarr/Lidarr.exe': No such file or directory. 2021-04-18 13:29:56,018 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-04-18 13:29:56,023 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23247292520384 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stdout)> 2021-04-18 13:29:56,024 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23247293014992 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stderr)> 2021-04-18 13:29:56,024 INFO exited: lidarr (exit status 2; not expected) 2021-04-18 13:29:56,024 DEBG received SIGCHLD indicating a child quit 2021-04-18 13:29:57,026 INFO spawned: 'lidarr' with pid 62 2021-04-18 13:29:57,039 DEBG 'lidarr' stderr output: Cannot open assembly '/usr/lib/lidarr/Lidarr.exe': No such file or directory. 2021-04-18 13:29:57,049 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23247292567408 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stdout)> 2021-04-18 13:29:57,049 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23247292567456 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stderr)> 2021-04-18 13:29:57,049 INFO exited: lidarr (exit status 2; not expected) 2021-04-18 13:29:57,050 DEBG received SIGCHLD indicating a child quit 2021-04-18 13:29:59,054 INFO spawned: 'lidarr' with pid 66 2021-04-18 13:29:59,069 DEBG 'lidarr' stderr output: Cannot open assembly '/usr/lib/lidarr/Lidarr.exe': No such file or directory. 2021-04-18 13:29:59,076 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23247292567216 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stderr)> 2021-04-18 13:29:59,077 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23247293016240 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stdout)> 2021-04-18 13:29:59,077 INFO exited: lidarr (exit status 2; not expected) 2021-04-18 13:29:59,077 DEBG received SIGCHLD indicating a child quit 2021-04-18 13:30:02,081 INFO spawned: 'lidarr' with pid 70 2021-04-18 13:30:02,097 DEBG 'lidarr' stderr output: Cannot open assembly '/usr/lib/lidarr/Lidarr.exe': No such file or directory. 2021-04-18 13:30:02,105 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23247292567312 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stdout)> 2021-04-18 13:30:02,105 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23247292567264 for <Subprocess at 23247293016720 with name lidarr in state STARTING> (stderr)> 2021-04-18 13:30:02,105 INFO exited: lidarr (exit status 2; not expected) 2021-04-18 13:30:02,105 DEBG received SIGCHLD indicating a child quit 2021-04-18 13:30:03,107 INFO gave up: lidarr entered FATAL state, too many start retries too quickly 2021-04-18 13:33:20,307 WARN received SIGTERM indicating exit request 2021-04-18 13:33:20,321 DEBG killing shutdown-script (pid 57) with signal SIGTERM 2021-04-18 13:33:20,321 INFO waiting for shutdown-script to die 2021-04-18 13:33:20,364 DEBG 'shutdown-script' stdout output: [info] Initialising shutdown of process(es) 'lidarr' ... 2021-04-18 13:33:21,366 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23247292567504 for <Subprocess at 23247292520480 with name shutdown-script in state STOPPING> (stdout)> 2021-04-18 13:33:21,366 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 23247292641440 for <Subprocess at 23247292520480 with name shutdown-script in state STOPPING> (stderr)> 2021-04-18 13:33:21,366 INFO stopped: shutdown-script (exit status 0) 2021-04-18 13:33:21,366 DEBG received SIGCHLD indicating a child quit