thread 'main' panicked...`RUST_BACKTRACE=1` environment variable to display a backtrace about vaultwarden_ldap HOT 5 CLOSED

I'm also getting this error, below is my error output

ldap_sync_1 | thread 'main' panicked at 'broken pipe', src/main.rs:21:9
ldap_sync_1 | note: Run with RUST_BACKTRACE=1 environment variable to display a backtrace.
ldap_admin_1 | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message

from vaultwarden_ldap.

After adding

"environment:
RUST_BACKTRACE: 1
"
to my docker-compose.yaml under the ldap_sync container I get the following

ldap_sync_1 | stack backtrace:
ldap_sync_1 | 0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
ldap_sync_1 | at src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:39
ldap_sync_1 | 1: std::sys_common::backtrace::_print
ldap_sync_1 | at src/libstd/sys_common/backtrace.rs:70
ldap_sync_1 | 2: std::panicking::default_hook::{{closure}}
ldap_sync_1 | at src/libstd/sys_common/backtrace.rs:58
ldap_sync_1 | at src/libstd/panicking.rs:200
ldap_sync_1 | 3: std::panicking::default_hook
ldap_sync_1 | at src/libstd/panicking.rs:215
ldap_sync_1 | 4: std::panicking::rust_panic_with_hook
ldap_sync_1 | at src/libstd/panicking.rs:478
ldap_sync_1 | 5: std::panicking::continue_panic_fmt
ldap_sync_1 | at src/libstd/panicking.rs:385
ldap_sync_1 | 6: std::panicking::begin_panic_fmt
ldap_sync_1 | at src/libstd/panicking.rs:340
ldap_sync_1 | 7: bitwarden_rs_ldap::main
ldap_sync_1 | 8: std::rt::lang_start::{{closure}}
ldap_sync_1 | 9: std::panicking::try::do_call
ldap_sync_1 | at src/libstd/rt.rs:49
ldap_sync_1 | at src/libstd/panicking.rs:297
ldap_sync_1 | 10: __rust_maybe_catch_panic
ldap_sync_1 | at src/libpanic_unwind/lib.rs:92
ldap_sync_1 | 11: std::rt::lang_start_internal
ldap_sync_1 | at src/libstd/panicking.rs:276
ldap_sync_1 | at src/libstd/panic.rs:388
ldap_sync_1 | at src/libstd/rt.rs:48
ldap_sync_1 | 12: main
ldap_sync_1 | 13: __libc_start_main
ldap_sync_1 | 14: _start

from vaultwarden_ldap.

Same.

from vaultwarden_ldap.

This looks different than the issue on #1. A "panic" is just an unhandeled error.

@onggie, could you please run with RUST_BACKTRACE=1, as the error suggests? That will give me a trace that will point me to the right part in the project to look.

from vaultwarden_ldap.

This looks like it's the same issue that was reported in #3. I've got a fix for that I'm planning to deploy soon.

from vaultwarden_ldap.