Component Manager Containers in OBP are Blocked and do not Produce any Logs
(Doc ID 2682444.1)
Last updated on FEBRUARY 12, 2024
Applies to:
Oracle Blockchain Platform Enterprise Edition - Version 19.3.2 and laterInformation in this document applies to any platform.
Symptoms
IP subnet mask is changed on all OBPEE instances.Post that the Linux system process journalctl cannot work.Also CM(Component manager) containers seems to be blocked as it cannot output any logs
After subnet mask changes, no matter the Virtual Machine was restarted or not restarted, they started facing 2 issues:
1. Console (on each, one instance was created) can be accessed.The created instance can be listed but the details of instance cannot be fetched due to 3 kinds of issue:
a. component manager connection timeout.
b. component manager connection refused.
c. component manager host unreachable.
2. All instance console cannot be accessed at all.
Changes
The subnet mask is changed from /24 to /25 (from 255.255.255.0 to 255.255.255.128), meanwhile VM(Virtual Machine) hostname, VM IP and default gateway were not changed.The subnet mask changes were made by Linux system config on each VM.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |