We have installed an update of Git last Friday and since, all our deliveries failed.
Best Answer
A
Audric Frey
said
about 1 month ago
Hello,
Looking in the com.indy.engine.46000.rdbmsLog.log, we see the following error:
It means that the H2 logs database is probably corrupted (maybe due to a crash or disk saturation?)
To find the use of this Runtime:
- stop the runtime
- rename the "sessions" directory to "sessions.old"
- restart the runtime
=> It will start by recreating a new blank log base
If you need to access the content of this log base (consultation of the sessions it contains):
- you can try to copy it in a Runtime dedicated to this consultation in order to see if the consultation is possible
- the H2 database editor provides a restore attempt utility but we have never tested it
Useful recommendations:
- the H2 log base is provided in the Runtime to allow a quick start of a Runtime
- for a sensitive environment (pre-production, production...) it is recommended to configure the runtime to use a more robust database equipped with better monitoring and recovering tools (sql server, oracle, db2, postgresql....)
1 Comment
A
Audric Frey
said
about 1 month ago
Answer
Hello,
Looking in the com.indy.engine.46000.rdbmsLog.log, we see the following error:
It means that the H2 logs database is probably corrupted (maybe due to a crash or disk saturation?)
To find the use of this Runtime:
- stop the runtime
- rename the "sessions" directory to "sessions.old"
- restart the runtime
=> It will start by recreating a new blank log base
If you need to access the content of this log base (consultation of the sessions it contains):
- you can try to copy it in a Runtime dedicated to this consultation in order to see if the consultation is possible
- the H2 database editor provides a restore attempt utility but we have never tested it
Useful recommendations:
- the H2 log base is provided in the Runtime to allow a quick start of a Runtime
- for a sensitive environment (pre-production, production...) it is recommended to configure the runtime to use a more robust database equipped with better monitoring and recovering tools (sql server, oracle, db2, postgresql....)
Audric Frey
Hello,
Stambia Designer Version 20.5.1.20210930_075624
We have installed an update of Git last Friday and since, all our deliveries failed.
Hello,
Looking in the com.indy.engine.46000.rdbmsLog.log, we see the following error:
It means that the H2 logs database is probably corrupted (maybe due to a crash or disk saturation?)
To find the use of this Runtime:
- stop the runtime
- rename the "sessions" directory to "sessions.old"
- restart the runtime
=> It will start by recreating a new blank log base
If you need to access the content of this log base (consultation of the sessions it contains):
- you can try to copy it in a Runtime dedicated to this consultation in order to see if the consultation is possible
- the H2 database editor provides a restore attempt utility but we have never tested it
Useful recommendations:
- the H2 log base is provided in the Runtime to allow a quick start of a Runtime
- for a sensitive environment (pre-production, production...) it is recommended to configure the runtime to use a more robust database equipped with better monitoring and recovering tools (sql server, oracle, db2, postgresql....)
Audric Frey
Hello,
Looking in the com.indy.engine.46000.rdbmsLog.log, we see the following error:
It means that the H2 logs database is probably corrupted (maybe due to a crash or disk saturation?)
To find the use of this Runtime:
- stop the runtime
- rename the "sessions" directory to "sessions.old"
- restart the runtime
=> It will start by recreating a new blank log base
If you need to access the content of this log base (consultation of the sessions it contains):
- you can try to copy it in a Runtime dedicated to this consultation in order to see if the consultation is possible
- the H2 database editor provides a restore attempt utility but we have never tested it
Useful recommendations:
- the H2 log base is provided in the Runtime to allow a quick start of a Runtime
- for a sensitive environment (pre-production, production...) it is recommended to configure the runtime to use a more robust database equipped with better monitoring and recovering tools (sql server, oracle, db2, postgresql....)