TelegramMessenger / MTProxy

4.86k stars 806 forks source link

Assertion `!(p & 0xffff0000)' failed #508

Closed rafaelsupport closed 1 year ago

rafaelsupport commented 1 year ago

Hey

I got this error but i have no idea what can be. I'm running: ./mtproto-proxy -u nobody -p 8888 -H 10443 -S aae98325a97fa6e59d23a9f91b965ef9 --aes-pwd proxy-secret proxy-multi.conf -M 1 -v

And i got this error:

[97126][2023-04-29 15:45:24.039170 local] Invoking engine mtproxy-0.01 compiled at Apr 29 2023 15:36:57 by gcc 7.5.0 64-bit after commit dc0c7f3de40530053189c572936ae4fd1567269b
[97126][2023-04-29 15:45:24.039260 local] config_filename = 'proxy-multi.conf'
[97126][2023-04-29 15:45:24.039280 local] /etc/hosts changed, reloaded
[97126][2023-04-29 15:45:24.039360 local] config loaded!
[97126][2023-04-29 15:45:24.039379 local] creating 1 workers
[97126][2023-04-29 15:45:24.039507 local] loaded 128 bytes from password file proxy-secret
[97127][2023-04-29 15:45:24.039563 local] loaded 128 bytes from password file proxy-secret
[97126][2023-04-29 15:45:24.041383 local] using main IP 10.10.0.1/16 at interface wg0
mtproto-proxy: common/pid.c:42: init_common_PID: Assertion `!(p & 0xffff0000)' failed.
[97127][2023-04-29 15:45:24.041414 local] using main IP 10.10.0.1/16 at interface wg0
mtproto-proxy: common/pid.c:42: init_common_PID: Assertion `!(p & 0xffff0000)' failed.
[pid 97126] [time 1682775924]
------- Stack Backtrace -------
./mtproto-proxy(print_backtrace+0x2c)[0x5568557f534c]
./mtproto-proxy[pid 97127] [time 1682775924]
------- Stack Backtrace -------
(extended_debug_handler+0x10)[0x5568557f54d0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12980./mtproto-proxy)(print_backtrace[0x+0x2c7f685f79b980)]
[0x5568557f534c]
./mtproto-proxy(/lib/x86_64-linux-gnu/libc.so.6extended_debug_handler+0x10()gsignal[0x5568557f54d0+0x]
c7)[0x7f685f3d6fb7]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12980)[0x7f685f79b980]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f685f3d8921]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f685f3d6fb7]
/lib/x86_64-linux-gnu/libc.so.6(+0x3048a)[0x7f685f3c848a]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f685f3d8921]
/lib/x86_64-linux-gnu/libc.so.6(+0x30502)[0x7f685f3c8502]
/lib/x86_64-linux-gnu/libc.so.6(+0x3048a)[0x7f685f3c848a]
./mtproto-proxy(+0x533b1)[0x5568557f93b1]
/lib/x86_64-linux-gnu/libc.so.6(+0x30502)[0x7f685f3c8502]
./mtproto-proxy(engine_init+0xe5)[0x5568557ef735]
./mtproto-proxy(+0x533b1)[0x5568557f93b1]
./mtproto-proxy(default_main+0x113)[0x5568557f0573]
./mtproto-proxy(engine_init+0xe5)[0x5568557ef735]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f685f3b9bf7]
./mtproto-proxy(default_main+0x113)./mtproto-proxy[0x(5568557f0573_start]
+0x2a)[0x5568557b782a]
[pid 97126] [time 1682775924] -------------------------------
[pid 97126] [time 1682775924] mtproxy-0.01 compiled at Apr 29 2023 15:36:57 by gcc 7.5.0 64-bit after commit dc0c7f3de40530053189c572936ae4fd1567269b[pid 97126] [time 1682775924]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f685f3b9bf7]
./mtproto-proxy(_start+0x2a)[0x5568557b782a]
[pid 97127] [time 1682775924] -------------------------------
[pid 97127] [time 1682775924] mtproxy-0.01 compiled at Apr 29 2023 15:36:57 by gcc 7.5.0 64-bit after commit dc0c7f3de40530053189c572936ae4fd1567269b[pid 97127] [time 1682775924]

Is there some solution or workaround to fix this?