Log messages related to microservice health.
| Log ID | Level | Message | Cause | Remedy | Impact |
|---|---|---|---|---|---|
| 4001 | Info | Health monitoring port not configured | The port of health monitoring for this services is not configured | None | Health monitoring for this services is not supported |
| 4002 | Info | Starting health monitoring on port %v | Health monitoring started on this port | None | None |
| 4003 | Fatal | Failed to process microservice configuration file | File does not exist, or has errors | Contact support | This service will not start |
| 4004 | Info | Go Version: [%s], OS/Arch: [%s/%s] | Go version and Architecture information | None | None |
| 4005 | Info | Starting microservice [%s] | A microservice is being started | None | None |
| 4006 | Info | [%s]: Worker Shutdown started | As part of a service shutdown each worker thread is stopped | None | This service will be unavailable until restarted |
| 4007 | Info | [%s]: Worker Shutdown done | This worker thread has successfully stopped | None | This service will be unavailable until restarted |
| 4008 | Info | Starting Shutdown of Microservice, received signal | A Microservice is being shut down | None | This service will be unavailable until restarted |
| 4009 | Error | Completed shutting down all worker threads, exiting | Microservice shutdown completed | None | This service will be unavailable until restarted |
| 4010 | Info | [%s]: Worker Started | A new worker thread was started for this service | None | None |
| 4011 | Info | Starting Watchdog processing | The watchdog thread is started for this service | None | None |
| 4012 | Error | [%s]: Microservice is dead | The microservice is not responding to the watchdog | The service is stopping or may be malfunctioning. Restart the service | The service may no longer be responding |
| 4013 | Warning | [%s]: Service already dead | The service was already stopped | None | None |
| 4014 | Warning | [%s]: Watchdog state unknown | Incorrect value received in message | Retry the command or configuration, contact support if persistent | Command or config failed to apply and was ignored |
| 4015 | Info | Watchdog Starting | The watchdog worker thread is started | None | None |
| 4016 | Error | K3S Liveliness check failed | The microservice seems to not be responding | If this issue persists, restart the service | The service is not available |
| 4017 | Error | K3S Readiness check failed | The service is still coming up or has failed | If this issue persists, restart the service | The service is not available |
| 4018 | Panic | Panic | The service encountered an unrecoverable error | Contact customer Support | The service will be restarted |
| 4019 | Fatal | Fatal error | The service encountered an unrecoverable error | Contact customer Support | The service will be restarted |
| 4020 | Error | Failed to resolve host IP: %s | A configuration file may be missing | Contact Customer Support | The service may not function correctly |
| 4021 | Info | Completed setting up pprof for %v with %v interval, %v allowed archives | Profiling started for service | None | Periodic pprof collection for service |
| 4022 | Error | Failed to set up pprof for %v with %v interval, %v allowed archives | Profiling started for service | Contact customer support | Periodic prof collection for service will not available |
| 4023 | Error | Failed to process gNMI/gRPC notification | The notification may have unexpected or invalid data | Contact customer support | The service may not function as expected |
| 4024 | Error | Memory read failure | Virtual memory issue | Contact customer support | Inconsistent memory information |
| 4025 | Warning | High memory usage | Memory consumption above threshold | Contact customer support | Service may recover or fail after sometime |
| 4026 | Error | File read failure | Invalid or inaccessible path/file | Contact customer support | Inconsistent file or disk information |
| 4027 | Error | Platform component property processing failed | Invalid or Unexpected platform component key/path | Contact customer support | Service may not function as expected |
| 4028 | Fatal | Requisite flags for db migration app not set; cannot proceed, exiting. | Requisite flags for db migration app is not set | Report the issue to Extreme Networks support | DB migration service launch will fail |
| 4029 | Fatal | Fatal error | DB migration encountered error | Contact customer support. | Service may not function as expected |