服务器Nginx代理了Docker中的seafile
昨天下午出现 502 bad gate way错误,重启docker依旧
进入docker容器seafile中,ps aux | grep seafile查不到任何进程
我另外搭了一个测试服务器,安装了干净的docker的seafile环境。在测试服务器中,进入docker容器seafile中,ps aux | grep seafile可以看到正常的服务进程
root@d1e7b39efe25:/opt/seafile# ps aux | grep seafile
root 68 0.0 0.0 72628 1192 ? Ss 15:25 0:00 /opt/seafile/seafile-server-8.0.3/seafile/bin/seafile-controller -c /opt/seafile/ccnet -d /opt/seafile/seafile-data -F /opt/seafile/conf
root 70 0.0 0.1 1214760 4960 ? Ssl 15:25 0:00 seaf-server -F /opt/seafile/conf -c /opt/seafile/ccnet -d /opt/seafile/seafile-data -l /opt/seafile/logs/seafile.log -P /opt/seafile/pids/seaf-server.pid -p /opt/seafile/seafile-server-8.0.3/runtime
root 104 5.7 1.2 164568 46980 ? S 15:25 0:00 python3 /opt/seafile/seafile-server-8.0.3/seahub/thirdpart/bin/gunicorn seahub.wsgi:application -c /opt/seafile/conf/gunicorn.conf.py --preload
root 108 0.0 1.1 164568 43144 ? S 15:25 0:00 python3 /opt/seafile/seafile-server-8.0.3/seahub/thirdpart/bin/gunicorn seahub.wsgi:application -c /opt/seafile/conf/gunicorn.conf.py --preload
root 109 0.0 1.1 164568 43144 ? S 15:25 0:00 python3 /opt/seafile/seafile-server-8.0.3/seahub/thirdpart/bin/gunicorn seahub.wsgi:application -c /opt/seafile/conf/gunicorn.conf.py --preload
root 110 0.0 1.1 164568 43144 ? S 15:25 0:00 python3 /opt/seafile/seafile-server-8.0.3/seahub/thirdpart/bin/gunicorn seahub.wsgi:application -c /opt/seafile/conf/gunicorn.conf.py --preload
root 111 0.0 1.1 164568 43140 ? S 15:25 0:00 python3 /opt/seafile/seafile-server-8.0.3/seahub/thirdpart/bin/gunicorn seahub.wsgi:application -c /opt/seafile/conf/gunicorn.conf.py --preload
root 112 0.0 1.1 164568 43136 ? S 15:25 0:00 python3 /opt/seafile/seafile-server-8.0.3/seahub/thirdpart/bin/gunicorn seahub.wsgi:application -c /opt/seafile/conf/gunicorn.conf.py --preload
root 138 0.0 0.0 14724 996 pts/0 S+ 15:25 0:00 grep --color=auto seafile
求救!