Sign-in failing with “session expired”
Inicio de sesión y área de cliente
Cronología
-
Resuelto
Resolved at 22:42 UTC. Duration: 14 minutes. Existing sessions were preserved; only new sign-ins during the window failed.
-
Causa identificada
The session store restarted and came back with an empty dataset; every sign-in attempt was being rejected as stale. It has been restored from its snapshot.
-
Investigando
Signing in to the customer area fails with a “session expired” message since 22:28 UTC. Already-open sessions are unaffected. Payments and machines are unaffected.
Revisión posterior al incidente ·
Qué ocurrió y qué cambió
Causa
The session store was restarted during routine patching and its persistence file was on a volume that had not yet been mounted at start-up, so it started empty.
Impacto
New sign-ins to the customer area failed for 14 minutes. Open sessions, payments, provisioning and machines were unaffected.
Qué cambiamos
- The service now refuses to start if its persistence volume is absent, rather than starting empty.
- Patching of that host was moved into the announced maintenance windows.
Las horas se muestran en su zona horaria ().
Páginas relacionadas
- Estado del servicioEstado en vivo de gpuserver.io: componentes y centros de datos sondeados cada 60 s desde 5 ciudades, con disponibilidad de 90 días e incidentes desde 2022.
- Historial de incidentesTodos los incidentes y ventanas de mantenimiento de gpuserver.io desde septiembre de 2022, mes a mes, con cronología y revisión posterior al incidente.
- Acuerdo de nivel de servicioEl compromiso del 99,9 %: qué cuenta como inactividad, cómo se mide desde fuera, cinco minutos de plazo por cada minuto perdido, y las exclusiones completas.
- RedPuertos sin contador hasta 25 Gbit/s, dos operadores y un IX por sede, filtrado DDoS permanente, IPv6 enrutado — y las cuatro cosas que no ofrecemos, dichas ya.