-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shadowsocks-rust failed to start after last update via snap #1438
Comments
The root cause was:
which is reported right here: https://github.com/tokio-rs/tokio/blob/master/tokio/src/runtime/blocking/pool.rs#L418-L437 . The So I highly suspect that there was a syscall that your system didn't support, because:
My built with cross running on Debian 11 with Linux 6.1.0 works quite well. So there must be something incompatible with your Linux Distribution environment. Here are some possible ways to help debug:
|
@zonyitoo , thank you for quick response and thoughtful explanation. I found several EPERM in strace, attached the output to the reply. You're absolutely right, my current system is almost obsolete Centos 7. And before upgrading to Centos 9 I was trying to find out if it is possible to use previous version of SSServer-rust. But it seems that snap repo switched hardly to v.1.18.0 providing no previous versions to install: Is there any possibility to get previous snap of shadowsocks-rust which I could revert to and use? Maybe you could provide me with that snap? In case the answer is 'no', then I will have to upgrade Distribution to the latest version and reconfigure everything once again (OpenSSL, OpenVPN, XRay, Nginx and other related services) . Welp, it was my strategic error to stay on Centos 7... |
Just looked through your strace log, why
Well, before v1.18.0, it only supports i386 architecture, it may not be able to run well on your system, too. I don't know if I downgrade the |
Since Kernel 3.10 was used in Ubuntu 13.04, which was released in 2013, far older than
|
Hi,
after last update via snap I'm unable to start shadowsocks-rust and getting errors, which I don't know how to solve. Please help.
$/usr/bin/snap run shadowsocks-rust.ssserver-daemon -c /root/shadowsocks.json
2024-02-16T13:07:46.519584293+03:00 INFO shadowsocks server 1.18.0 build 2024-02-07T18:36:11.165817751+00:00
thread 'main' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.36.0/src/runtime/scheduler/multi_thread/worker.rs:447:13:
OS can't spawn worker thread: Operation not permitted (os error 1)
stack backtrace:
0: 0x55beab41695c -
1: 0x55beab178e20 -
2: 0x55beab3e0182 -
3: 0x55beab4194fe -
4: 0x55beab418c70 -
5: 0x55beab419e32 -
6: 0x55beab41985c -
7: 0x55beab4197b6 -
8: 0x55beab4197a1 -
9: 0x55beab0512e4 -
10: 0x55beab3626ce -
11: 0x55beab0fbbaf -
12: 0x55beab0c5d53 -
13: 0x55beab0c64c9 -
14: 0x7f126c930d90 -
15: 0x7f126c930e40 - __libc_start_main
16: 0x55beab072da5 -
17: 0x0 -
Aborted
$ldd --version
ldd (GNU libc) 2.17
Copyright (C) 2012 Free Software Foundation, Inc.
$ snap list
Name Version Rev Tracking Publisher Notes
core 16-2.61.1 16574 latest/stable canonical✓ core
core18 20231027 2812 latest/stable canonical✓ base
core20 20231123 2105 latest/stable canonical✓ base
core22 20240111 1122 latest/stable canonical✓ base
shadowsocks-rust v1.18.0.r1.g65eb758a 661 latest/stable ducksoft held
snapd 2.61.1 20671 latest/stable canonical✓ snapd
uname -ai
Linux 3.10.0-1160.105.1.el7.x86_64 #1 SMP Thu Dec 7 15:39:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Config:
cat shadowsocks.json
{
"server": "0.0.0.0",
"mode":"tcp_and_udp",
"server_port":444,
"password":"*",
"timeout":300,
"method":"2022-blake3-aes-256-gcm"
}
The text was updated successfully, but these errors were encountered: