Issue with varnish on onionoo-frontends
I have been receiving every few hours alerts from nagios about onionoo backend not updating the index. But I have checked and the service has been running every hour and updating the statuses (summary from the logs pasted below). I wonder if we are having some issues with Varnish caching the results?
The nagios check is triggered if at least one index has not been updated for a few hours. @gk has hourly snapshots from onionoo so we can check what has been served in the last few days.
I have checked our configs in puppet and I can't spot anything that would cause an issue. I have also been looking at requests on the frontends and it seems varnish is querying the backend correctly.
2022-12-17 00:07:15,827 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
1 hours of bridge uptimes processed
8,702 uptime status files updated
--
2022-12-17 01:06:52,137 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
1 hours of bridge uptimes processed
8,692 uptime status files updated
--
2022-12-17 02:07:26,965 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
1 hours of bridge uptimes processed
8,739 uptime status files updated
--
2022-12-17 03:06:36,807 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
0 hours of bridge uptimes processed
6,109 uptime status files updated
--
2022-12-17 04:08:06,285 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
2 hours of relay uptimes processed
2 hours of bridge uptimes processed
8,765 uptime status files updated
--
2022-12-17 05:07:02,203 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
1 hours of bridge uptimes processed
8,698 uptime status files updated
--
2022-12-17 06:06:34,321 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
1 hours of bridge uptimes processed
8,697 uptime status files updated
--
2022-12-17 07:06:29,204 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
1 hours of bridge uptimes processed
8,715 uptime status files updated
--
2022-12-17 08:07:45,006 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
1 hours of bridge uptimes processed
8,706 uptime status files updated
--
2022-12-17 09:06:27,389 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
0 hours of bridge uptimes processed
6,083 uptime status files updated
--
2022-12-17 10:06:39,656 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
2 hours of bridge uptimes processed
8,697 uptime status files updated
--
2022-12-17 11:07:11,588 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
1 hours of bridge uptimes processed
8,702 uptime status files updated
--
2022-12-17 12:07:09,905 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
1 hours of bridge uptimes processed
8,705 uptime status files updated
--
2022-12-17 13:06:34,323 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
1 hours of bridge uptimes processed
8,671 uptime status files updated
--
2022-12-17 14:06:47,110 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
1 hours of bridge uptimes processed
8,688 uptime status files updated
--
2022-12-17 15:07:03,315 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
0 hours of bridge uptimes processed
6,086 uptime status files updated
--
2022-12-17 16:06:42,723 INFO o.t.m.o.u.StatusUpdateRunner:51 UptimeStatusUpdater
1 hours of relay uptimes processed
2 hours of bridge uptimes processed
8,696 uptime status files updated