strahd_zarovich

I am seeing this on 6.9.0rc2 as well.

Is this docker still supported? Mine say's "not available" under the docker tab.

I would like this one too. I need to move from one cache pool to another. I prefer to not use rsync if I could.

Yes, that is what was happening for me. I just skipped that one file.

This is the log. it see's the movie in the Watch Folder, but does nothing after that. Test Watch Folder.txt

Before I start a big conversion I turn Auto Update off. I typically do 4 to 5 movies at a time.

It is a download of a movie I own. I do not have a BlueRay reader for a computer. The Big Lebowski is the movie. Yes, once I add the .m2ts to Handbrake it freezes. Also, added it to the Watch folder and it doesn't seem to see it. The movie plays fine through Plex. I just want to shrink it down.

I am having some issues with .m2ts files. I have the movie parts pulled out, but when I try to load them into handbrake it is like everything just freezes. It stays at scanning for minutes and never moves. Is there something that should be done before bringing it into handbrake? I looked in this thread and only see people scanning the entire disk. I just have the movie file.

Is anyone seeing a memory suck going on. if I let this run for a couple of hours i will see my UnRAID server lockup with memory maxed out.

Thank you. I finally found something about the 1006 error and changing browsers. I just got in when you posted this.

The red X has this when you hover over it.: Server Disconnected (code: 1006)

I do not use Handbreak a lot, but today when trying to spin up the docker I keep getting the attached error. The VNC comes up, but in the VNC window next to Handbreak name is a red X and I get nothing else on the screen. I tried removing the docker and deleting the appdata files. HandbrakeError.txt

That is a great question. Let me fix that now.

Well dang. I saw the issue after I posted the screen shot. It helps when you mount the drive.

That is strange. I am using 50.6GB out of 256GB of space.

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-plexpass' --net='host' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'TRANS_DIR'='/tmp' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/Multimedia/':'/media':'rw' -v '/mnt/disks/appdata_SSD/binhex-plexpass/':'/config':'rw,slave' 'binhex/arch-plexpass' f1ef519e06d20866224aa7e67fcc55648ac31caaf38607bfe069abd3deccea04 The command finished successfully! Log: https://hub.docker.com/u/binhex/ tee: /config/supervisord.log: No space left on device 2020-05-09 10:59:45.957673 [info] System information Linux Tower 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux 2020-05-09 10:59:45.995993 [info] OS_ARCH defined as 'x86-64' 2020-05-09 10:59:46.033279 [info] PUID defined as '99' 2020-05-09 10:59:50.523404 [info] PGID defined as '100' 2020-05-09 10:59:57.579623 [info] UMASK defined as '000' 2020-05-09 10:59:57.616532 [info] Permissions already set for volume mappings 2020-05-09 10:59:57.652300 [info] TRANS_DIR defined as '/tmp' 2020-05-09 10:59:57.751197 [info] Deleting files in /tmp (non recursive)... 2020-05-09 10:59:57.785750 [info] Starting Supervisor... 2020-05-09 10:59:58,037 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2020-05-09 10:59:58,038 INFO Set uid to user 0 succeeded 2020-05-09 10:59:58,041 INFO supervisord started with pid 6 2020-05-09 10:59:59,043 INFO spawned: 'plexmediaserver' with pid 68 2020-05-09 10:59:59,044 INFO reaped unknown pid 7 2020-05-09 10:59:59,181 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140194285723024 for <Subprocess at 140194285723312 with name plexmediaserver in state STARTING> (stdout)> 2020-05-09 10:59:59,182 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140194285723168 for <Subprocess at 140194285723312 with name plexmediaserver in state STARTING> (stderr)> 2020-05-09 10:59:59,182 INFO exited: plexmediaserver (exit status 255; not expected) 2020-05-09 10:59:59,182 DEBG received SIGCHLD indicating a child quit 2020-05-09 11:00:00,184 INFO spawned: 'plexmediaserver' with pid 73 2020-05-09 11:00:00,251 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140194286601024 for <Subprocess at 140194285723312 with name plexmediaserver in state STARTING> (stdout)> 2020-05-09 11:00:00,252 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140194284950960 for <Subprocess at 140194285723312 with name plexmediaserver in state STARTING> (stderr)> 2020-05-09 11:00:00,252 INFO exited: plexmediaserver (exit status 255; not expected) 2020-05-09 11:00:00,252 DEBG received SIGCHLD indicating a child quit 2020-05-09 11:00:02,255 INFO spawned: 'plexmediaserver' with pid 78 2020-05-09 11:00:02,320 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140194285428688 for <Subprocess at 140194285723312 with name plexmediaserver in state STARTING> (stdout)> 2020-05-09 11:00:02,320 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140194285723168 for <Subprocess at 140194285723312 with name plexmediaserver in state STARTING> (stderr)> 2020-05-09 11:00:02,321 INFO exited: plexmediaserver (exit status 255; not expected) 2020-05-09 11:00:02,321 DEBG received SIGCHLD indicating a child quit 2020-05-09 11:00:05,325 INFO spawned: 'plexmediaserver' with pid 83 2020-05-09 11:00:05,391 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140194286601024 for <Subprocess at 140194285723312 with name plexmediaserver in state STARTING> (stdout)> 2020-05-09 11:00:05,391 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140194284950768 for <Subprocess at 140194285723312 with name plexmediaserver in state STARTING> (stderr)> 2020-05-09 11:00:05,392 INFO exited: plexmediaserver (exit status 255; not expected) 2020-05-09 11:00:05,392 DEBG received SIGCHLD indicating a child quit 2020-05-09 11:00:06,393 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

I just started having the same issues last night after a server restart. Did you ever find a solution?

Thank you so much. Fixed and started right up.

I cannot seem to get my Bitwarden to restart after a server restart. Any help would be awesome. /--------------------------------------------------------------------\ | Starting Bitwarden_RS | | Version 1.13.1-8a5450e8 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Report URL: https://github.com/dani-garcia/bitwarden_rs/issues/new | \--------------------------------------------------------------------/ [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 thread 'main' panicked at 'valid URL: RelativeUrlWithoutBase', src/config.rs:468:15 stack backtrace: 0: 0x55c5f1cced34 - backtrace::backtrace::libunwind::trace::h4c2cc0e2e6ab3962 at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88 1: 0x55c5f1cced34 - backtrace::backtrace::trace_unsynchronized::hea6bde8e7134fd0e at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66 2: 0x55c5f1cced34 - std::sys_common::backtrace::_print_fmt::he7d4732f58e6db0f at src/libstd/sys_common/backtrace.rs:77 3: 0x55c5f1cced34 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hf701bbc56fde8d3e at src/libstd/sys_common/backtrace.rs:59 4: 0x55c5f1cf4e3c - core::fmt::write::he594986618f675c1 at src/libcore/fmt/mod.rs:1052 5: 0x55c5f1cc69f7 - std::io::Write::write_fmt::hd70ac90f82ab1700 at src/libstd/io/mod.rs:1428 6: 0x55c5f1cd0f65 - std::sys_common::backtrace::_print::h25a36b234ec491c1 at src/libstd/sys_common/backtrace.rs:62 7: 0x55c5f1cd0f65 - std::sys_common::backtrace::print::h62a7683f84bc3186 at src/libstd/sys_common/backtrace.rs:49 8: 0x55c5f1cd0f65 - std::panicking::default_hook::{{closure}}::h768d56ec1648bf19 at src/libstd/panicking.rs:204 9: 0x55c5f1cd0c51 - std::panicking::default_hook::h1b45fc6f2d3bc4d1 at src/libstd/panicking.rs:224 10: 0x55c5f1cd15ca - std::panicking::rust_panic_with_hook::h4280c0e24899f0dd at src/libstd/panicking.rs:472 11: 0x55c5f1cd11b0 - rust_begin_unwind at src/libstd/panicking.rs:380 12: 0x55c5f1cf3651 - core::panicking::panic_fmt::hd08789ca336a1e3e at src/libcore/panicking.rs:85 13: 0x55c5f1cf3473 - core::option::expect_none_failed::h5f7476254e94cf79 at src/libcore/option.rs:1199 14: 0x55c5f14813f0 - bitwarden_rs::config::ConfigBuilder::build::h9cb995d9b2e4de93 15: 0x55c5f146f961 - bitwarden_rs::config::Config::load::hc92698509b101da7 16: 0x55c5f159dfa7 - std::sync::once::Once::call_once::{{closure}}::h41770cf18adb5a8c 17: 0x55c5f1cce441 - std::sync::once::Once::call_inner::h53918a41f1388da8 at src/libstd/sync/once.rs:417 18: 0x55c5f170adfe - bitwarden_rs::main::h37edf665a219ea51 19: 0x55c5f16079a3 - std::rt::lang_start::{{closure}}::h474530925c77fdb6 20: 0x55c5f1cd1093 - std::rt::lang_start_internal::{{closure}}::h146e16f41944d428 at src/libstd/rt.rs:52 21: 0x55c5f1cd1093 - std::panicking::try::do_call::h3f5225ae73a228e1 at src/libstd/panicking.rs:305 22: 0x55c5f1cdb0d7 - __rust_maybe_catch_panic at src/libpanic_unwind/lib.rs:86 23: 0x55c5f1cd1b30 - std::panicking::try::h51b6356779bfebde at src/libstd/panicking.rs:281 24: 0x55c5f1cd1b30 - std::panic::catch_unwind::h5160e22d94ba4502 at src/libstd/panic.rs:394 25: 0x55c5f1cd1b30 - std::rt::lang_start_internal::hbe3c5736d32d3fde at src/libstd/rt.rs:51 26: 0x55c5f171c5f2 - main 27: 0x1473dace009b - __libc_start_main 28: 0x55c5f133256a - _start 29: 0x0 - <unknown>

I was having this issue. I noticed I had Strict Port Forward on and once I turned it off everything started working great again.

I am having a problem over the last two weeks with SAB "Cannot read Watched Folder /data/watch" The was working for roughly the last 6 months, but not recently. I have completely removed SAB and reinstalled and the issue came back. If I restart SAB in UnRAID everything will work correctly for a couple of hours. What am I missing? I do not see anything in the logs.