蜘蛛池redis不能链接



本地127测试是正常的可以连接但是在蜘蛛池程序中显示连接失败,扩展和组件都安装了 不知道为什么连接不上

这说明 redis 应用自身没有问题,可以正常使用。

看你的截图信息,Redis 主机地址输入的和 1Panel 提示的地址不一样,你先确认一下。

127也试过连接不上


现在有点小问题 今天多放了几十个域名进去,然后整个服务器就挂了一次,再次重启后访问就报错502,防火墙的功能能不优化一下,针对蜘蛛和爬虫还有正常访问这些
以下是服务的界面:什么都正常也没有报错但是就是不访问后台

unable to open database file (14)
出现这个错误


新的错误已经出现
这个是自带的数据库问题 还是?其他什么问题

重启服务器以后,面板正常了但是docker 又启动不了,期间本人未做任何操作

应该是 sqlite3 数据库锁库了,遇到这种情况只能是重启 1Panel 服务了。

用下面的命令来查看 docker 运行日志:

journalctl -u docker.service -exf


大佬 你看看

麻烦再看一下,还有没有更详细的 error 字样日志

下面是我刚刚启动的时候的报错:
月 10 16:01:40 HKSRV3478 dockerd[31463]: time=“2024-01-10T16:01:40.620709827+08:00” level=info msg=“Starting up”
1月 10 16:01:40 HKSRV3478 dockerd[31463]: time=“2024-01-10T16:01:40.631218925+08:00” level=error msg=“mkdir /var/lib/docker/overlay2/check-overlayfs-support4291492997/upper: no space left on device” storage-driver=overlay2
1月 10 16:01:40 HKSRV3478 dockerd[31463]: time=“2024-01-10T16:01:40.631261301+08:00” level=error msg=“[graphdriver] prior storage driver overlay2 failed: driver not supported”
1月 10 16:01:40 HKSRV3478 dockerd[31463]: failed to start daemon: error initializing graphdriver: driver not supported
1月 10 16:01:40 HKSRV3478 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
1月 10 16:01:40 HKSRV3478 systemd[1]: Failed to start Docker Application Container Engine.
– Subject: Unit docker.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit docker.service has failed.

– The result is failed.
1月 10 16:01:40 HKSRV3478 systemd[1]: Unit docker.service entered failed state.
1月 10 16:01:40 HKSRV3478 systemd[1]: docker.service failed.
1月 10 16:01:42 HKSRV3478 systemd[1]: docker.service holdoff time over, scheduling restart.
1月 10 16:01:42 HKSRV3478 systemd[1]: Stopped Docker Application Container Engine.
– Subject: Unit docker.service has finished shutting down
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit docker.service has finished shutting down.
1月 10 16:01:42 HKSRV3478 systemd[1]: Starting Docker Application Container Engine…
– Subject: Unit docker.service has begun start-up
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit docker.service has begun starting up.
1月 10 16:01:42 HKSRV3478 dockerd[31520]: time=“2024-01-10T16:01:42.779968653+08:00” level=info msg=“Starting up”
1月 10 16:01:42 HKSRV3478 dockerd[31520]: time=“2024-01-10T16:01:42.788329065+08:00” level=error msg=“mkdir /var/lib/docker/overlay2/check-overlayfs-support680397880/merged: no space left on device” storage-driver=overlay2
1月 10 16:01:42 HKSRV3478 dockerd[31520]: time=“2024-01-10T16:01:42.788359614+08:00” level=error msg=“[graphdriver] prior storage driver overlay2 failed: driver not supported”
1月 10 16:01:42 HKSRV3478 dockerd[31520]: failed to start daemon: error initializing graphdriver: driver not supported
1月 10 16:01:42 HKSRV3478 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
1月 10 16:01:42 HKSRV3478 systemd[1]: Failed to start Docker Application Container Engine.
– Subject: Unit docker.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit docker.service has failed.

– The result is failed.
1月 10 16:01:42 HKSRV3478 systemd[1]: Unit docker.service entered failed state.
1月 10 16:01:42 HKSRV3478 systemd[1]: docker.service failed.
1月 10 16:01:44 HKSRV3478 systemd[1]: docker.service holdoff time over, scheduling restart.
1月 10 16:01:44 HKSRV3478 systemd[1]: Stopped Docker Application Container Engine.
– Subject: Unit docker.service has finished shutting down
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit docker.service has finished shutting down.
1月 10 16:01:44 HKSRV3478 systemd[1]: Starting Docker Application Container Engine…
– Subject: Unit docker.service has begun start-up
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit docker.service has begun starting up.
1月 10 16:01:45 HKSRV3478 dockerd[31583]: time=“2024-01-10T16:01:45.032244610+08:00” level=info msg=“Starting up”
1月 10 16:01:45 HKSRV3478 dockerd[31583]: time=“2024-01-10T16:01:45.041249597+08:00” level=error msg=“mkdir /var/lib/docker/overlay2/check-overlayfs-support2032550085/merged: no space left on device” storage-driver=overlay2
1月 10 16:01:45 HKSRV3478 dockerd[31583]: time=“2024-01-10T16:01:45.041279916+08:00” level=error msg=“[graphdriver] prior storage driver overlay2 failed: driver not supported”
1月 10 16:01:45 HKSRV3478 dockerd[31583]: failed to start daemon: error initializing graphdriver: driver not supported
1月 10 16:01:45 HKSRV3478 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
1月 10 16:01:45 HKSRV3478 systemd[1]: Failed to start Docker Application Container Engine.
– Subject: Unit docker.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit docker.service has failed.

– The result is failed.
1月 10 16:01:45 HKSRV3478 systemd[1]: Unit docker.service entered failed state.
1月 10 16:01:45 HKSRV3478 systemd[1]: docker.service failed.
1月 10 16:01:47 HKSRV3478 systemd[1]: docker.service holdoff time over, scheduling restart.
1月 10 16:01:47 HKSRV3478 systemd[1]: Stopped Docker Application Container Engine.
– Subject: Unit docker.service has finished shutting down
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit docker.service has finished shutting down.
1月 10 16:01:47 HKSRV3478 systemd[1]: start request repeated too quickly for docker.service
1月 10 16:01:47 HKSRV3478 systemd[1]: Failed to start Docker Application Container Engine.
– Subject: Unit docker.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page

– Unit docker.service has failed.

– The result is failed.
1月 10 16:01:47 HKSRV3478 systemd[1]: Unit docker.service entered failed state.
1月 10 16:01:47 HKSRV3478 systemd[1]: docker.service failed.

你这是因为服务器磁盘空间不足导致的

上面提到的 SQLite 锁库问题也是磁盘空间不足导致的。

image
我没把ipanel安装到默认的位置安装www的位置了
服务器 是新开的。
前段时间还正常的,我也看到这个问题了 但是我查看我所有的磁盘都没有存慢,也不知道是哪里问题,是不是需要卸载面板重装到默认路径

可以卸载重装(安装过程会提示用户自定义安装目录)

直接使用默认安装目录还会出现这种情况吗,我之前使用的是宝塔

1Panel 默认目录是 /opt/1panel,不是 /www

那我之前的网站的配置是不是全没了?能直接修复或者什么其他方案吗?

首先考虑手动给磁盘扩容吧