全球主机交流论坛

标题: 大佬们，悬赏50解决个酸酸**后端错误 [打印本页]

作者: b956536180 时间: 2019-7-10 14:42
标题: 大佬们，悬赏50解决个酸酸**后端错误
本帖最后由 b956536180 于 2019-7-10 15:39 编辑

Traceback (most recent call last):
  File "/shadowsocks/server_pool.py", line 92, in _loop
loop.run()
  File "/shadowsocks/shadowsocks/eventloop.py", line 228, in run
callback()
  File "/soft/shadowsocks/shadowsocks/tcprelay.py", line 2049, in handle_periodic
self._eventloop.removefd(self._server_socket_fd)
  File "/soft/shadowsocks/shadowsocks/eventloop.py", line 181, in removefd
del self._fdmap[fd]

出现这个，进程还在，就是端口全部自动暂停了，后端用的shadowsocks-manyuser-nimaqu

端口暂停前的错误日志

2019-07-10 14:22:35 ERROR tcprelay.py:1612 can not parse header when handling connection from ::ffff:210.32.136.217:14862
2019-07-10 14:22:35 INFO    db_transfer.py:791 db stop server at port [39844] reason: config changed!
2019-07-10 14:22:35 INFO    server_pool.py:225 stopped server at 0.0.0.0:39844 already stop
2019-07-10 14:22:35 INFO    server_pool.py:249 stopped server at [::]:39844
2019-07-10 14:22:35 ERROR tcprelay.py:1519 [Errno 32] Broken pipe
2019-07-10 14:22:35 ERROR tcprelay.py:1523 exception from ::ffff:119.85.30.199:10880
2019-07-10 14:22:36 ERROR shell.py:50 [Errno 32] Broken pipe
2019-07-10 14:22:36 ERROR tcprelay.py:427 exception from ::ffff:221.177.253.134:8843
2019-07-10 14:22:36 WARNING  common.py:291 unsupported addrtype 209, maybe wrong password or encryption method
2019-07-10 14:22:36 WARNING  tcprelay.py:635 Protocol ERROR, TCP ogn data 160301021e0100021a03035d25842f2d26c1ca78074ffd6d18da2c89354d937254ad7eab75ad627fa361f720ff78362a87fbee3fa0ecf38b4d2fc8fade114d8e523d58ba928ce5d9df3b3ac5001cc02bc02fcca9cca8cc14cc13c00ac014c009c013009c0035002f000a010001b5ff010001000000001f001d00001a646f776e6c6f61642e77696e646f77737570646174652e636f6d00170000002300e06700fd593cb84ae92bc3c45cea285d35caf52b40467b4be054a043b558be7cedadade4d12be9350991c1f177ad21254407a0325ed9d6ab58060d81898bc90af65fad438780883daf8a265440e03d87185a079eb4ed22dd3a0c1948fe31555c93e1e2c507eac199e91c15b2946d83b490a1f1f7523efe115f03a393bcf32fe4f4febac00be3026158a6d59297dd0580393f14639796ec1dde073c31040d56e43e67229050ff1d6a6f1c833dceca2bdb5b23976b83b9b034b396f49a877ce00a3f987a2e769f65e924d42fc153f2552329fa6ea514120bb57ef6466515c2f934f6000d0016001406010603050105030401040303010303020102030005000501000000000012000075500000000b00020100000a000600040017001800150066000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 from ::ffff:210.32.136.217:22002 via port 26026
2019-07-10 14:22:36 ERROR tcprelay.py:1612 can not parse header when handling connection from ::ffff:210.32.136.217:22002
2019-07-10 14:22:37 INFO    auto_block.py:89 Read hosts.deny from line 17
2019-07-10 14:22:37 ERROR server_pool.py:99 25107
Traceback (most recent call last):
  File "shadowsocks/server_pool.py", line 92, in _loop
loop.run()
  File "/shadowsocks/shadowsocks/eventloop.py", line 228, in run
callback()
  File "/shadowsocks/shadowsocks/tcprelay.py", line 2049, in handle_periodic
self._eventloop.removefd(self._server_socket_fd)
  File "/shadowsocks/shadowsocks/eventloop.py", line 181, in removefd
del self._fdmap[fd]
KeyError: 25107
2019-07-10 14:22:37 INFO    db_transfer.py:822 db start server at port [41805] pass [jZ4OOtjK] protocol [origin] method [aes-256-cfb] obfs [http_simple_compatible]
2019-07-10 14:22:37 INFO    server_pool.py:146 starting server at [::]:41805
2019-07-10 14:22:37 WARNING  server_pool.py:161 IPV6 [Errno 98] Address already in use
2019-07-10 14:22:37 INFO    server_pool.py:176 starting server at 0.0.0.0:41805
2019-07-10 14:22:37 WARNING  server_pool.py:190 IPV4 [Errno 98] Address already in use
2019-07-10 14:22:40 INFO    db_transfer.py:822 db start server at port [39844] pass [0高墙vOAB] protocol [origin] method [aes-256-cfb] obfs [http_simple_compatible]
2019-07-10 14:22:40 INFO    server_pool.py:146 starting server at [::]:39844
2019-07-10 14:22:40 WARNING  common.py:334 You did't specify CIDR routing prefix size for 183.94.82.9, implicit treated as 183.94.82.9/32
2019-07-10 14:22:40 WARNING  common.py:334 You did't specify CIDR routing prefix size for 183.94.82.221, implicit treated as 183.94.82.221/32
2019-07-10 14:22:40 WARNING  common.py:334 You did't specify CIDR routing prefix size for 183.94.82.40, implicit treated as 183.94.82.40/32
2019-07-10 14:22:40 WARNING  common.py:334 You did't specify CIDR routing prefix size for 183.94.82.84, implicit treated as 183.94.82.84/32
2019-07-10 14:22:40 WARNING  common.py:334 You did't specify CIDR routing prefix size for 183.94.82.18, implicit treated as 183.94.82.18/32
2019-07-10 14:22:40 WARNING  common.py:334 You did't specify CIDR routing prefix size for 183.94.82.192, implicit treated as 183.94.82.192/32
2019-07-10 14:22:40 WARNING  common.py:334 You did't specify CIDR routing prefix size for 183.94.82.25, implicit treated as 183.94.82.25/32
2019-07-10 14:22:40 WARNING  server_pool.py:161 IPV6 [Errno 98] Address already in use
2019-07-10 14:22:40 INFO    server_pool.py:176 starting server at 0.0.0.0:39844
2019-07-10 14:22:40 WARNING  common.py:334 You did't specify CIDR routing prefix size for 183.94.82.9, implicit treated as 183.94.82.9/32
2019-07-10 14:22:40 WARNING  common.py:334 You did't specify CIDR routing prefix size for 183.94.82.221, implicit treated as 183.94.82.221/32
2019-07-10 14:22:40 WARNING  common.py:334 You did't specify CIDR routing prefix size for 183.94.82.40, implicit treated as 183.94.82.40/32
2019-07-10 14:22:40 WARNING  common.py:334 You did't specify CIDR routing prefix size for 183.94.82.84, implicit treated as 183.94.82.84/32
2019-07-10 14:22:40 WARNING  common.py:334 You did't specify CIDR routing prefix size for 183.94.82.18, implicit treated as 183.94.82.18/32
2019-07-10 14:22:40 WARNING  common.py:334 You did't specify CIDR routing prefix size for 183.94.82.192, implicit treated as 183.94.82.192/32
2019-07-10 14:22:40 WARNING  common.py:334 You did't specify CIDR routing prefix size for 183.94.82.25, implicit treated as 183.94.82.25/32
2019-07-10 14:22:40 WARNING  server_pool.py:190 IPV4 [Errno 98] Address already in use
2019-07-10 14:22:40 INFO    db_transfer.py:822 db start server at port [32213] pass [qas19881213_SF] protocol [origin] method [aes-256-cfb] obfs [http_simple_compatible]
2019-07-10 14:22:40 INFO    server_pool.py:146 starting server at [::]:32213
2019-07-10 14:22:40 INFO    server_pool.py:176 starting server at 0.0.0.0:32213
2019-07-10 14:23:37 INFO    auto_block.py:89 Read hosts.deny from line 17
2019-07-10 14:23:40 INFO    server_pool.py:225 stopped server at 0.0.0.0:32768 already stop
2019-07-10 14:23:40 INFO    server_pool.py:249 stopped server at [::]:32768
2019-07-10 14:23:40 INFO    server_pool.py:225 stopped server at 0.0.0.0:32771 already stop
2019-07-10 14:23:40 INFO    server_pool.py:249 stopped server at [::]:32771
2019-07-10 14:23:40 INFO    server_pool.py:225 stopped server at 0.0.0.0:25096 already stop
2019-07-10 14:23:40 INFO    server_pool.py:249 stopped server at [::]:25096
2019-07-10 14:23:40 INFO    server_pool.py:225 stopped server at 0.0.0.0:32775 already stop
2019-07-10 14:23:40 INFO    server_pool.py:249 stopped server at [::]:32775
2019-07-10 14:23:40 INFO    server_pool.py:225 stopped server at 0.0.0.0:32778 already stop
2019-07-10 14:23:40 INFO    server_pool.py:249 stopped server at [::]:32778
2019-07-10 14:23:40 INFO    server_pool.py:225 stopped server at 0.0.0.0:32781 already stop
2019-07-10 14:23:40 INFO    server_pool.py:249 stopped server at [::]:32781
2019-07-10 14:23:40 INFO    server_pool.py:225 stopped server at 0.0.0.0:10925 already stop
2019-07-10 14:23:40 INFO    server_pool.py:249 stopped server at [::]:10925

作者: casm 时间: 2019-7-10 14:43
这是多用户还是单用户，用的哪个脚本

作者: b956536180 时间: 2019-7-10 14:44

casm 发表于 2019-7-10 14:43
这是多用户还是单用户，用的哪个脚本

shadowsocks-manyuser-nimaqu

作者: 安好 时间: 2019-7-10 14:47
用docker版最快

作者: b956536180 时间: 2019-7-10 14:56

安好发表于 2019-7-10 14:47
用docker版最快

主要是现在换不了docker安装方式，

作者: zccyun 时间: 2019-7-10 14:57
没说异常是啥。。怎么定位

作者: b956536180 时间: 2019-7-10 15:40

zccyun 发表于 2019-7-10 14:57
没说异常是啥。。怎么定位

大佬我重新编辑了一下，您看看日志信息

作者: zccyun 时间: 2019-7-10 15:44
信息量不够。感觉那个异常可能不重要。
把进程kill掉，等5分钟再启动试试。
看日志像是这次启动的时候压根端口就没监听

作者: b956536180 时间: 2019-7-12 11:59

zccyun 发表于 2019-7-10 15:44
信息量不够。感觉那个异常可能不重要。
把进程kill掉，等5分钟再启动试试。
看日志像是这次启动的时候压根 ...

大佬，怎么打印更详细的错误日志。

作者: 宇宙无敌大帅锅 时间: 2019-7-12 12:36
提示: 作者被禁止或删除内容自动屏蔽

欢迎光临全球主机交流论坛 (https://fd.vvwvv.eu.org/)