Ansible playbook:
Redis/Service[redis-server]/ensure: change from 'stopped' to 'running' failed: Systemd start for redis-server failed!", "journalctl log for redis-server:", "Oct 18 09:25:09 zulip-sc systemd[1]: Starting Advanced key-value store...", "Oct 18 09:25:09 zulip-sc redis-server[22720]: *** FATAL CONFIG FILE ERROR (Redis 6.0.16) ***", "Oct 18 09:25:09 zulip-sc redis-server[22720]: Reading the configuration file, at line 260", "Oct 18 09:25:09 zulip-sc redis-server[22720]: >>> 'logfile /var/log/redis/redis-server.log'", "Oct 18 09:25:09 zulip-sc redis-server[22720]: Can't open the log file: Read-only file system", "Oct 18 09:25:09 zulip-sc systemd[1]: redis-server.service: Main process exited, code=exited, status=1/FAILURE", "Oct 18 09:25:09 zulip-sc systemd[1]: redis-server.service: Failed with result 'exit-code'."
/var/log/zulip/install.log
Oct 18 09:25:09 zulip-sc systemd[1]: Starting Advanced key-value store...
Oct 18 09:25:09 zulip-sc redis-server[22720]: *** FATAL CONFIG FILE ERROR (Redis 6.0.16) ***
Oct 18 09:25:09 zulip-sc redis-server[22720]: Reading the configuration file, at line 260
Oct 18 09:25:09 zulip-sc redis-server[22720]: >>> 'logfile /var/log/redis/redis-server.log'
Oct 18 09:25:09 zulip-sc redis-server[22720]: Can't open the log file: Read-only file system
Oct 18 09:25:09 zulip-sc systemd[1]: redis-server.service: Main process exited, code=exited, status=1/FAILURE
Oct 18 09:25:09 zulip-sc systemd[1]: redis-server.service: Failed with result 'exit-code'.
Oct 18 09:25:09 zulip-sc systemd[1]: Failed to start Advanced key-value store.
Seems to be a LXC issue: [SOLVED] Redis-server[xxx]: Can’t open the log file: Read-only file system - Support - YunoHost Forum
restic snapshotsrestic restore <snapshot_id> --target ./home/zulip/deployments/current/scripts/setup/restore-backup backup.tar.gz
Notice: /Stage[main]/Zulip::Profile::Postgresql/File[/etc/postgresql/14/main/postgresql.conf]/content: content changed '{md5}43f7b1452183cfaa20ad585e4b4f30e8' to '{md5}362a3e2684dbd1fa9a608a54fc2136bf'
Notice: /Stage[main]/Zulip::Profile::Postgresql/Exec[pg_ctlcluster 14 main restart]/returns: Job for postgresql@14-main.service failed because the service did not take the steps required by its unit configuration.
Notice: /Stage[main]/Zulip::Profile::Postgresql/Exec[pg_ctlcluster 14 main restart]/returns: See "systemctl status postgresql@14-main.service" and "journalctl -xeu postgresql@14-main.service" for details.
Error: /Stage[main]/Zulip::Profile::Postgresql/Exec[pg_ctlcluster 14 main restart]: Failed to call refresh: 'pg_ctlcluster 14 main restart' returned 1 instead of one of [0]
Error: /Stage[main]/Zulip::Profile::Postgresql/Exec[pg_ctlcluster 14 main restart]: 'pg_ctlcluster 14 main restart' returned 1 instead of one of [0]
Notice: /Stage[main]/Zulip::Supervisor/Service[supervisor]: Triggered 'refresh' from 3 events
Notice: Applied catalog in 13.66 seconds
Subcommand of /home/zulip/deployments/current/scripts/setup/restore-backup failed with exit status 2: /home/zulip/deployments/2024-10-18-09-36-08/scripts/zulip-puppet-apply -f
Actual error output for the subcommand is just above this.
Restart postgres service
2024-10-18 09:45:26,699 restart-server: Restarting zulip_deliver_scheduled_emails
zulip_deliver_scheduled_emails: started
2024-10-18 09:45:27,979 restart-server: Restarting zulip_deliver_scheduled_messages
zulip_deliver_scheduled_messages: ERROR (spawn error)
Traceback (most recent call last):
File "/home/zulip/deployments/2024-10-18-09-36-08/scripts/restart-server", line 166, in <module>
restart_or_start(worker)
File "/home/zulip/deployments/2024-10-18-09-36-08/scripts/restart-server", line 150, in restart_or_start
subprocess.check_call(["supervisorctl", our_verb, service])
File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['supervisorctl', 'start', 'zulip_deliver_scheduled_messages']' returned non-zero exit status 7.
Subcommand of /home/zulip/deployments/current/scripts/setup/restore-backup failed with exit status 1: /home/zulip/deployments/2024-10-18-09-36-08/scripts/restart-server
Actual error output for the subcommand
su zulip
/home/zulip/deployments/current/manage.py migrate
sudo supervisorctl restart all
zulip-workers:zulip_events_missedmessage_mobile_notifications: ERROR (spawn error) Traceback (most recent call last): File "/home/zulip/deployments/2024-10-18-09-36-08/scripts/restart-server", line 166, in <module> restart_or_start(worker) File "/home/zulip/deployments/2024-10-18-09-36-08/scripts/restart-server", line 150, in restart_or_start subprocess.check_call(["supervisorctl", our_verb, service]) File "/usr/lib/python3.10/subprocess.py", line 369, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['supervisorctl', 'start', 'zulip-workers:zulip_events_missedmessage_mobile_notifications']' returned non-zero exit status 7. Subcommand of /home/zulip/deployments/current/scripts/setup/restore-backup failed with exit status 1: /home/zulip/deployments/2024-10-18-09-36-08/scripts/restart-server Actual error output for the subcommand is just above this.