I did not perform any operations and did not set any auto-stop, but the compute engine stopped on its own.
The logs for the day, which can be viewed from GCP, are as follows.
----------Log below----------
{
"insertId": "0",
"jsonPayload": {
"bootCounter": "4",
"shutdownEvent": {},
"@type": "type.googleapis.com/cloud_integrity.IntegrityEvent"
},
"resource": {
"type": "gce_instance",
"labels": {
"zone": "asia-northeast1-b",
"project_id": "fx-automation-370801",
"instance_id": "4300555567021339914"
}
},
"timestamp": "2023-03-16T09:37:14.912286897Z",
"severity": "NOTICE",
"logName": "projects/fx-automation-370801/logs/compute.googleapis.com%2Fshielded_vm_integrity",
"receiveTimestamp": "2023-03-16T09:37:16.933823931Z"
}
-----------------------------
The result of the last command is as follows
The reboot was performed on 3/24, and the target server was started from the GCP web console on that day.
----------last command below----------
hajime pts/0 35.235.240.240 Sun Mar 26 01:02 still logged in
reboot system boot 4.18.0-408.el8.x Fri Mar 24 11:49 still running
yykk pts/0 175.177.44.184 Tue Mar 14 23:16 - 23:27 (00:11)
--------------------------------------
----------kernel varsion is below----------
4.18.0-408.el8.x86_64
-------------------------------------------
The syslogs immediately before and after the shutdown and startup are as follows.
----------syslog below----------
Mar 16 17:51:52 ea-mura NetworkManager[794]: <info> [1678956712.8858] dhcp4 (eth0): state changed new lease, address=10.146.0.2
Mar 16 18:21:52 ea-mura NetworkManager[794]: <info> [1678958512.8863] dhcp4 (eth0): state changed new lease, address=10.146.0.2
Mar 24 11:49:38 ea-mura kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/boot/vmlinuz-4.18.0-408.el8.x86_64 root=UUID=d318418b-e5ad-455d-ac97-594fc62160d8 ro net.ifnames=0 biosdevname=0 scsi_mod.use_blk_mq=Y crashkernel=auto console=ttyS0,38400n8
-------------------------------
Please let me know if you know what caused the server to shut down on its own.
