-
Hi all, i updated komodo from 1.17.1 to 1.18.3 and now see in my server overview the message "pherivery version mismatch". How do i fix this? I could not find any information in the doc or in the release notes. ...thanks for your support micha |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
It's a version mismatch, nothing to worry about as Komodo is backwards compatible. To fix this, simply updating the images and redeploying your periphery should suffice, e.g., running the following in the periphery directory (where the
|
Beta Was this translation helpful? Give feedback.
-
@OKok-3 |
Beta Was this translation helpful? Give feedback.
-
Hi, I pull komodo core and periphery image with the 'latest' tag to run as new containers. But when I add new server and enable it, I get this "Periphery version is unknown" message, the core cannot connect to the periphery and the server state is 'NOT OK'. When I disable the server, the message becomes "Pherivery version mismatch. Expected 1.18.3" and server state is 'DISABLED'. I did not add COMPOSE_KOMODO_IMAGE_TAG in my environment variables.
Core log: Periphery log: What went wrong? Are the images correct? Thank you for your support. |
Beta Was this translation helpful? Give feedback.
It's a version mismatch, nothing to worry about as Komodo is backwards compatible. To fix this, simply updating the images and redeploying your periphery should suffice, e.g., running the following in the periphery directory (where the
compose.yaml
and.env
file lives) on your periphery host: