This section lists the most frequent errors that users may encounter while running the software. Their meaning is detailed and possible fixes or workaround are suggested when possible.
genom::incompatible_digest
exceptionThis exception is raised when loading a genom client that does not match the version of the component that it is supposed to control. This most often means that the client is loaded from a different installation prefix from that of the component (thus possibly mixing different versions).
The exception details contains the version number and the build date of both
the client and the component. Inspecting this information can help in
determining the cause of the error. Note that version
is the number of
the last released version though, so if you built a not-yet-released version of
the software, this information will only be partial.
For instance, this python exception shows that the client was built on January 31, while the component was built on February 28. This indicates that the client is probably too old for the new version of the component:
>>> g.load('demo')
[...]
genomix.event.GenoMError: ::genom::incompatible_digest: {'client': {'version': 'demo-1.4', 'date': 'Fri Jan 31 17:29:51 CET 2025'}, 'server': {'version': 'demo-1.4', 'date': 'Fri Feb 28 12:06:30 CET 2025'}}
In order to fix this error, first check if the path from which the client is
loaded matches what you expect. When using genomixd
, running genomixd -v -v
will print out the path that is used. You can also explicit the path when
loading a component, e.g. by loading /path/to/plugin/component.so
instead of
just loading component
. If the path seems correct, also check that the
component and the client were built from the same sources.