Problem launching in Crux. #41

New Issue

Ghost · 2019-12-12T16:48:04+02:00

Ghost commented

2019-12-12 16:48:04 +02:00

Hi! I try to made a package for Crux Linux but I have the following error and nothing happens.
Can you guide me?

["ThreadId(3)"] ui/src/workers.rs:178_21:	Waiting for work
["ThreadId(4)"] ui/src/workers.rs:178_21:	Waiting for work
["ThreadId(5)"] ui/src/workers.rs:178_21:	Waiting for work
["ThreadId(2)"] ui/src/workers.rs:178_21:	Waiting for work
["ThreadId(7)"] ui/src/state.rs:251_21:	unparked
                                                thread '<unnamed>' panicked at 'cannot access stderr during shutdown', src/libcore/option.rs:1190:5i/src/workers.rs:181_29:	received thread_end_rx, quitting
["ThreadId(4)"] ui/src/workers.rs:181_29:	thread '<unnamed>' panicked at 'cannot access stderr during shutdown', src/libcore/option.rs:1190:5
["ThreadId(6)"] ui/src/workers.rs:224_25:	thread '<unnamed>' panicked at 'cannot access stderr during shutdown', src/libcore/option.rs:1190:5
["ThreadId(2)"] ui/src/workers.rs:181_29:	thread '<unnamed>' panicked at 'cannot access stderr during shutdown', src/libcore/option.rs:1190:5
["ThreadId(3)"] ui/src/workers.rs:203_17:	thread '<unnamed>' panicked at 'cannot access stderr during shutdown', src/libcore/option.rs:1190:5

Hi! I try to made a package for Crux Linux but I have the following error and nothing happens. Can you guide me? ``` ["ThreadId(3)"] ui/src/workers.rs:178_21: Waiting for work ["ThreadId(4)"] ui/src/workers.rs:178_21: Waiting for work ["ThreadId(5)"] ui/src/workers.rs:178_21: Waiting for work ["ThreadId(2)"] ui/src/workers.rs:178_21: Waiting for work ["ThreadId(7)"] ui/src/state.rs:251_21: unparked thread '<unnamed>' panicked at 'cannot access stderr during shutdown', src/libcore/option.rs:1190:5i/src/workers.rs:181_29: received thread_end_rx, quitting ["ThreadId(4)"] ui/src/workers.rs:181_29: thread '<unnamed>' panicked at 'cannot access stderr during shutdown', src/libcore/option.rs:1190:5 ["ThreadId(6)"] ui/src/workers.rs:224_25: thread '<unnamed>' panicked at 'cannot access stderr during shutdown', src/libcore/option.rs:1190:5 ["ThreadId(2)"] ui/src/workers.rs:181_29: thread '<unnamed>' panicked at 'cannot access stderr during shutdown', src/libcore/option.rs:1190:5 ["ThreadId(3)"] ui/src/workers.rs:203_17: thread '<unnamed>' panicked at 'cannot access stderr during shutdown', src/libcore/option.rs:1190:5 ```

Manos Pitsidianakis commented

2019-12-12 16:55:22 +02:00

Hello! Thank you for your report.

Can you post an anonymised version of the configuration file you used?
Is this log the entire output?
Is this one of the tagged releases or did you checkout the master branch?

Hello! Thank you for your report. - Can you post an anonymised version of the configuration file you used? - Is this log the entire output? - Is this one of the tagged releases or did you checkout the master branch?

Manos Pitsidianakis added the

bug

label 2019-12-12 16:55:28 +02:00

Manos Pitsidianakis commented

2019-12-12 17:18:19 +02:00

@jollupa can you try the master branch? There's no information in your logs but I have pushed some IMAP-related changes that might change something for you.

Manos Pitsidianakis commented

2019-12-13 16:16:36 +02:00

@jollupa anything in the debug logs?

cargo run --features=debug-tracing 2> debug.log

@jollupa anything in the debug logs? > cargo run --features=debug-tracing 2> debug.log

Manos Pitsidianakis commented

2019-12-14 01:40:03 +02:00

@jollupa Hm I'm at a loss here.. Perhaps the IMAP thread gets stuck somewhere because the output was not what it expected and waits for bytes. I had this problem on early dev. Your server doesn't require anything special to log in from what I can see. If you control the server, would you be willing to give me a test account with zero quota just to log in?

Manos Pitsidianakis commented

2019-12-14 17:52:43 +02:00

@jolupa thank you! You can remove the account now.

The problem was the certificate couldn't be verified:

error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1915: (Hostname mismatch)

Didn't checkout the certificates further, but I did test danger_accept_invalid_certs=true and it connected successfully.

The error should have been displayed in the UI, and I have some patches that do this almost ready to push.

If you confirm this is the error on your end as well, we can close the issue.

@jolupa thank you! You can remove the account now. The problem was the certificate couldn't be verified: > error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1915: (Hostname mismatch) Didn't checkout the certificates further, but I did test `danger_accept_invalid_certs=true` and it connected successfully. The error should have been displayed in the UI, and I have some patches that do this almost ready to push. If you confirm this is the error on your end as well, we can close the issue.

Manos Pitsidianakis commented

2019-12-15 08:54:20 +02:00

Alright we're getting somewhere. :)

Try to rerun the first config but with the RUST_BACKTRACE=1 env var set, that is RUST_BACKTRACE=1 cargo run --features=debug-tracing 2> debug.log. This will print the backtrace in the debug.log.

The second config fails because port 993 is for imaps and your server doesn't let you use STARTTLS most probably. (STARTTLS uses the 143 port)

Alright we're getting somewhere. :) Try to rerun the first config but with the `RUST_BACKTRACE=1` env var set, that is `RUST_BACKTRACE=1 cargo run --features=debug-tracing 2> debug.log`. This will print the backtrace in the debug.log. The second config fails because port `993` is for imaps and your server doesn't let you use STARTTLS most probably. (STARTTLS uses the `143` port)

Manos Pitsidianakis referenced this issue from a commit

2019-12-15 08:55:22 +02:00

melib/backends: MailBackend::refresh() returns Result Handle cases were refresh() would fail properly. Fixes a crash reported in #13

Manos Pitsidianakis commented

2019-12-15 16:05:30 +02:00

redefinition of table accounts.imap means you have named both accounts imap and they need unique names!

`redefinition of table accounts.imap` means you have named both accounts `imap` and they need unique names!

Ghost closed this issue

2019-12-15 17:10:55 +02:00

Manos Pitsidianakis commented

2019-12-15 17:11:55 +02:00

Thank you!