Desligamento Aleatório do Google Compute Engine

1

Nosso Compute Engine, que executa o back-end de um jogo para dispositivos móveis encerrado aleatoriamente hoje (03/8/18), e os registros não podem me informar qual usuário ou endereço IP o iniciou.

Estou pesquisando e entrando nos Syslogs, que exibem o seguinte:

Mar  8 10:58:10 redis-prod-vm systemd[1]: Started Synchronise Hardware Clock to System Clock.
    Mar  8 10:58:10 redis-prod-vm systemd[1]: Stopping Session 5 of user redis.
    Mar  8 10:58:10 redis-prod-vm systemd[1]: Stopping User Manager for UID 999...
    Mar  8 10:58:10 redis-prod-vm systemd[7558]: Stopping Default.
    Mar  8 10:58:10 redis-prod-vm systemd[1]: Stopping Graphical Interface.
    Mar  8 10:58:10 redis-prod-vm systemd[1]: Stopped target Graphical Interface.
    Mar  8 10:58:10 redis-prod-vm systemd[1]: Stopping Entropy daemon using the HAVEGE algorithm...
    Mar  8 10:58:10 redis-prod-vm haveged[369]: haveged: Stopping due to signal 15
    Mar  8 10:58:10 redis-prod-vm haveged[369]: haveged starting up
    Mar  8 10:58:10 redis-prod-vm systemd[1]: Stopping Multi-User System.
    Mar  8 10:58:10 redis-prod-vm systemd[1]: Stopped target Multi-User System.
    Mar  8 10:58:10 redis-prod-vm systemd[7558]: Stopped target Default.
    Mar  8 10:58:10 redis-prod-vm systemd[7558]: Stopping Basic System.
    Mar  8 10:58:10 redis-prod-vm systemd[7558]: Stopped target Basic System.
    Mar  8 10:58:10 redis-prod-vm systemd[7558]: Stopping Paths.
    Mar  8 10:58:10 redis-prod-vm systemd[7558]: Stopped target Paths.
    Mar  8 10:58:10 redis-prod-vm systemd[7558]: Stopping Timers.
    Mar  8 10:58:10 redis-prod-vm systemd[7558]: Stopped target Timers.
    Mar  8 10:58:10 redis-prod-vm systemd[7558]: Stopping Sockets.
    Mar  8 10:58:10 redis-prod-vm systemd[7558]: Stopped target Sockets.
    Mar  8 10:58:10 redis-prod-vm systemd[7558]: Starting Shutdown.
    Mar  8 10:58:10 redis-prod-vm systemd[7558]: Reached target Shutdown.
    Mar  8 10:58:10 redis-prod-vm systemd[1]: Stopping Deferred execution scheduler...
    Mar  8 10:58:10 redis-prod-vm systemd[1]: Stopping vsftpd FTP server...
    Mar  8 10:58:10 redis-prod-vm systemd[1]: Stopping LSB: bitnami init script...
    Mar  8 10:58:10 redis-prod-vm systemd[1]: Stopping Regular background program processing daemon...
    Mar  8 10:58:10 redis-prod-vm systemd[7558]: Starting Exit the Session...
    Mar  8 10:58:10 redis-prod-vm systemd[1]: Stopping Google Compute Engine user shutdown scripts...
    Mar  8 10:58:10 redis-prod-vm systemd[1]: Stopping OpenBSD Secure Shell server...

Isso continua até que a VM termine de desligar, aqui está o log:

2018-03-08 10:59:46.073 GMT compute.instances.stop
{"event_timestamp_us":"XXX","actor":{"user":""},"resource":{"name":"redis-prod-vm","type":"instance","zone":"us-central1-f","id":"XXX"},"event_type":"GCE_OPERATION_DONE","trace_id":"XXX","operation":{"type":"operation",…

Eu substituí alguns números potencialmente importantes por XXX para estarem seguros. Alguém por favor pode ajudar a esclarecer o que aconteceu?

    
por Dean Day 09.03.2018 / 01:20

0 respostas