We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1、我在vps上部署server后,在本地虚拟机部署worker无法连接上vps的server,服务器端面板也无法检测到worker。(配置文件都按照安装手册修改过了)。问题快照(worker日志,跟昨天的日志报错不一样):
[root@localhost nemo]# docker compose -f docker-compose.worker.yml up WARN[0000] /root/security/nemo/docker-compose.worker.yml: `version` is obsolete [+] Running 1/0 ✔ Container nemo-worker-1 Created 0.0s Attaching to worker-1 worker-1 | ==> log/access.log <== worker-1 | worker-1 | worker-1 | ==> log/runtime.log <== worker-1 | worker-1 | Warning:honeypot.toml file does not exist!!!!!! worker-1 | Warning:rabbish.toml file does not exist!!!!!! worker-1 | Warning:honeypot.toml file does not exist!!!!!! worker-1 | Warning:rabbish.toml file does not exist!!!!!! worker-1 | 2024/04/23 08:57:16 common config info honeypot: 0 rabbish: 0 rabbish-md5: 0 worker-1 | 2024/04/23 08:57:16 common config info honeypot: 0 rabbish: 0 rabbish-md5: 0 worker-1 | time="2024-04-23 08:57:16" level=info msg="start file sync..." worker-1 | 2024/04/23 08:57:16 init repleace log regex len: 3 worker-1 | 2024/04/23 08:57:16 Grab version: grab_version_1.9.1.0 worker-1 | 2024/04/23 08:57:16 Support 347 protocols, 807 ports worker-1 | 2024/04/23 08:57:17 [DEBUG] runtime.NumCPU():2, runtime.GOMAXPROCS():1 worker-1 | 2024/04/23 08:57:17 try to load user products rules: /opt/nemo/thirdparty/goby/rules/user/rule.json worker-1 | 2024/04/23 08:57:17 load json dir /opt/nemo/thirdparty/goby/4f7240174b449fa5 error: stat /opt/nemo/thirdparty/goby/4f7240174b449fa5: no such file or directory worker-1 | 2024/04/23 08:57:17 load archive dir /opt/nemo/thirdparty/goby/83504e548641ae18 error: open /opt/nemo/thirdparty/goby/83504e548641ae18: no such file or directory worker-1 | 2024/04/23 08:57:17 Version: v2.8.8 beta worker-1 | 2024/04/23 08:57:17 BuildTime: 2024-01-11 10:43:39 worker-1 | 2024/04/23 08:57:17 144 `POC` were successfully loaded worker-1 | 2024/04/23 08:57:19 API Server listen at 127.0.0.1:8361 worker-1 | 2024/04/23 08:57:19 pcap version: libpcap version 1.9.1 (with TPACKET_V3) worker-1 | 2024/04/23 08:57:19 found device from route table for 8.8.8.8: eth0 worker-1 | 2024/04/23 08:57:19 [DEBUG] get adapter of device eth0 worker-1 | 2024/04/23 08:57:19 [DEBUG] devices: [{eth0 22 [{172.22.0.2 ffff0000 172.22.255.255 <nil>} {fe80::42:acff:fe16:2 ffffffffffffffff0000000000000000 <nil> <nil>}]} {lo 55 [{127.0.0.1 ff000000 <nil> <nil>} {::1 ffffffffffffffffffffffffffffffff <nil> <nil>}]} {any Pseudo-device that captures on all interfaces 54 []} {nflog Linux netfilter log (NFLOG) interface 48 []} {nfqueue Linux netfilter queue (NFQUEUE) interface 48 []}] worker-1 | 2024/04/23 08:57:19 [DEBUG] getGatewayMac: eth0 8.8.8.8 worker-1 | 2024/04/23 08:57:20 find router mac is 02:42:64:7e:6e:bb worker-1 | 2024/04/23 08:57:21 [DEBUG] fetch mac address: eth0 02:42:64:7e:6e:bb worker-1 | 2024/04/23 08:57:21 [DEBUG] close pcap handler for getGatewayMac worker-1 | 2024/04/23 08:57:21 select adapter of to send packets: &{eth0 172.22.0.2 [] {172.22.0.2 ffff0000} ffff0000 02:42:ac:16:00:02 02:42:64:7e:6e:bb} worker-1 | 2024/04/23 08:58:00 auto-select the fastest DNS server: 8.8.8.8:53 100ms
2、服务端执行 docker compose -f docker-compose.server.yml up -d 无法直接访问,必须再 restart 一次才可以访问,我看了日志,问题位置出在pkg.db.conn.go,第一次启动时数据库连接会error,作者可以自测一下。
docker compose -f docker-compose.server.yml up -d
The text was updated successfully, but these errors were encountered:
No branches or pull requests
1、我在vps上部署server后,在本地虚拟机部署worker无法连接上vps的server,服务器端面板也无法检测到worker。(配置文件都按照安装手册修改过了)。问题快照(worker日志,跟昨天的日志报错不一样):
2、服务端执行
docker compose -f docker-compose.server.yml up -d
无法直接访问,必须再 restart 一次才可以访问,我看了日志,问题位置出在pkg.db.conn.go,第一次启动时数据库连接会error,作者可以自测一下。The text was updated successfully, but these errors were encountered: