Блог

Является ли это проблемой, с которой все просто должны мириться? Для отображения сообщений журнала в облачном журнале требуется не менее 12-18 часов. Мы никогда не имели ни малейшего представления о том, что делают наши виртуальные машины Google. Большую часть времени мы вообще не видим наших сообщений в журнале, только миллионы строк этого материала:

 2021-11-09T18:52:38.887509624Z Unable to export to Monitoring service because: GaxError RPC failed, caused by 3:Field timeSeries[0].points[0].interval.end_time had an invalid value of "2021-10-30T16:09:38.770613-07:00": Data points cannot be written more than 24h in the past.. debug_error_string:{"created":"@1636483958.886243136","description":"Error received from peer ipv4:172.217.11.202:443","file":"src/core/lib/surface/call.cc","file_line":1062,"grpc_message":"Field timeSeries[0].points[0].interval.end_time had an invalid value of "2021-10-30T16:09:38.770613-07:00": Data points cannot be written more than 24h in the past.","grpc_status":3}
 A 
2021-11-09T18:52:38.903761Z 2021-11-09T18:52:38.903512137Z container kill 714e6b93c8c67b5a54569aed3bd4a5985591600230af8ed860b5789e686e77aa (image=gcr.io/stackdriver-agents/stackdriver-logging-agent:1.8.9, name=stackdriver-logging-agent, signal=23) A 
2021-11-09T18:52:38.917711Z 2021-11-09T18:52:38.917505171Z container kill 714e6b93c8c67b5a54569aed3bd4a5985591600230af8ed860b5789e686e77aa (image=gcr.io/stackdriver-agents/stackdriver-logging-agent:1.8.9, name=stackdriver-logging-agent, signal=23) A 
2021-11-09T18:53:38.890751337Z Unable to export to Monitoring service because: GaxError RPC failed, caused by 3:Field timeSeries[0].points[0].interval.end_time had an invalid value of "2021-10-30T16:09:38.770613-07:00": Data points cannot be written more than 24h in the past.. debug_error_string:{"created":"@1636484018.889384555","description":"Error received from peer ipv4:172.217.11.202:443","file":"src/core/lib/surface/call.cc","file_line":1062,"grpc_message":"Field timeSeries[0].points[0].interval.end_time had an invalid value of "2021-10-30T16:09:38.770613-07:00": Data points cannot be written more than 24h in the past.","grpc_status":3}
 A 
2021-11-09T18:54:38.879268968Z Unable to export to Monitoring service because: GaxError RPC failed, caused by 3:Field timeSeries[0].points[0].interval.end_time had an invalid value of "2021-10-30T16:09:38.770613-07:00": Data points cannot be written more than 24h in the past.. debug_error_string:{"created":"@1636484078.878076512","description":"Error received from peer ipv4:172.217.11.202:443","file":"src/core/lib/surface/call.cc","file_line":1062,"grpc_message":"Field timeSeries[0].points[0].interval.end_time had an invalid value of "2021-10-30T16:09:38.770613-07:00": Data points cannot be written more than 24h in the past.","grpc_status":3}
 A 
2021-11-09T18:55:38.889891450Z Unable to export to Monitoring service because: GaxError RPC failed, caused by 3:Field timeSeries[0].points[0].interval.end_time had an invalid value of "2021-10-30T16:09:38.770613-07:00": Data points cannot be written more than 24h in the past.. debug_error_string:{"created":"@1636484138.888728523","description":"Error received from peer ipv4:172.217.11.202:443","file":"src/core/lib/surface/call.cc","file_line":1062,"grpc_message":"Field timeSeries[0].points[0].interval.end_time had an invalid value of "2021-10-30T16:09:38.770613-07:00": Data points cannot be written more than 24h in the past.","grpc_status":3}
 

Если наши сообщения журнала действительно появляются, их всегда значительно больше, чем этих сообщений об ошибках.

Инструкции Google по устранению неполадок (https://cloud.google.com/logging/docs/agent/logging/troubleshooting) бесполезны; сразу же я получаю «sudo: служба: команда не найдена», используя их стандартный «оптимизированный для контейнеров» образ виртуальной машины.

Пожалуйста, проверьте это.

Они упоминают об исправлении в следующем выпуске (упомянутом 4 дня назад), и обходной путь заключается в использовании ops-агента.