Does redis itself keep a log somewhere? It must have been running at some point, but didn’t respond in time - is it stuck, slow, or dead?
Edit: again, FWIW, I see I have a log file at
/var/discourse/shared/standalone/log/var-log/redis/current
and it’s entirely repeats of reports like this:
47:M 03 Jan 2023 18:50:11.090 * 100 changes in 300 seconds. Saving...
47:M 03 Jan 2023 18:50:11.091 * Background saving started by pid 31156
31156:C 03 Jan 2023 18:50:11.234 * DB saved on disk
31156:C 03 Jan 2023 18:50:11.236 * RDB: 1 MB of memory used by copy-on-write
47:M 03 Jan 2023 18:50:11.293 * Background saving terminated with success
47:M 03 Jan 2023 18:52:05.937 * 10000 changes in 60 seconds. Saving...
47:M 03 Jan 2023 18:52:05.940 * Background saving started by pid 31313
31313:C 03 Jan 2023 18:52:09.787 * DB saved on disk
31313:C 03 Jan 2023 18:52:09.791 * RDB: 3 MB of memory used by copy-on-write
47:M 03 Jan 2023 18:52:09.809 * Background saving terminated with success
47:M 03 Jan 2023 18:53:29.246 * 10000 changes in 60 seconds. Saving...
47:M 03 Jan 2023 18:53:29.248 * Background saving started by pid 31423
31423:C 03 Jan 2023 18:53:30.856 * DB saved on disk
31423:C 03 Jan 2023 18:53:30.857 * RDB: 2 MB of memory used by copy-on-write
47:M 03 Jan 2023 18:53:30.958 * Background saving terminated with success
47:M 03 Jan 2023 18:58:31.042 * 100 changes in 300 seconds. Saving...
47:M 03 Jan 2023 18:58:31.044 * Background saving started by pid 31753
31753:C 03 Jan 2023 18:58:31.212 * DB saved on disk
31753:C 03 Jan 2023 18:58:31.213 * RDB: 1 MB of memory used by copy-on-write
47:M 03 Jan 2023 18:58:31.245 * Background saving terminated with success