tickets #157708
closed
pagure01 runs out of disk space
Added by crameleon about 2 months ago.
Updated about 2 months ago.
Description
I removed some log files and lowered the fail2ban and nginx logrotate limits as an intermediary measure.
Needs to be solved properly.
- Category set to Pagure
- Assignee set to Pharaoh_Atem
- Private changed from Yes to No
Moved /srv/gitolite and /var/lib/redis underneath /data and bind mounted the directories back. Now pagure_web does not start:
pagure01 (pagure):~ # tail -f /var/log/pagure/error_web.log
[2024-03-22 03:31:12 +0000] [10006] [ERROR] Retrying in 1 second.
[2024-03-22 03:31:13 +0000] [10006] [ERROR] Retrying in 1 second.
[2024-03-22 03:31:14 +0000] [10006] [ERROR] Can't connect to /srv/gitolite/.pagure_web.sock
[2024-03-22 03:31:14 +0000] [10017] [INFO] Starting gunicorn 19.7.1
[2024-03-22 03:31:14 +0000] [10017] [ERROR] Retrying in 1 second.
[2024-03-22 03:31:15 +0000] [10017] [ERROR] Retrying in 1 second.
[2024-03-22 03:31:16 +0000] [10017] [ERROR] Retrying in 1 second.
[2024-03-22 03:31:17 +0000] [10017] [ERROR] Retrying in 1 second.
[2024-03-22 03:31:18 +0000] [10017] [ERROR] Retrying in 1 second.
[2024-03-22 03:31:19 +0000] [10017] [ERROR] Can't connect to /srv/gitolite/.pagure_web.sock
[2024-03-22 03:31:20 +0000] [10023] [INFO] Starting gunicorn 19.7.1
[2024-03-22 03:31:20 +0000] [10023] [ERROR] Retrying in 1 second.
Does not make sense to me, I thought pagure_web is what is supposed to create /srv/gitolite/.pagure_web.sock.
- Status changed from New to Resolved
- Assignee changed from Pharaoh_Atem to crameleon
Solved, maybe lasts a bit longer now.
Also available in: Atom
PDF