Done! After deleting some rows present in command_entities table (those that hadn't a job with a correlationId in job table) the engine restarted. I'll file a bugzilla for this issue. Thank you Benny. Ciao, gc On 13/07/2022 15:29, Benny Zlotnik wrote:
I will very carefully say yes, but please backup the engine before you do that
On Wed, Jul 13, 2022 at 1:59 PM Giulio Casella <giulio@di.unimi.it> wrote:
On 13/07/2022 12:54, Benny Zlotnik wrote:
On Wed, Jul 13, 2022 at 1:48 PM Giulio Casella <giulio@di.unimi.it> wrote:
Thanks Benny,
On 13/07/2022 12:20, Benny Zlotnik wrote:
Thanks, is the operation complete? If yes, you can remove the rows referencing command_id 6ae544f6-b608-4d8d-9f99-eabd5d5db0ad from command_entities
How can I know if the operation is completed? I've no access to admin portal anymore...
Right, I forgot about this...
The only things I know are: - there are 2 command in command_entities referencing command_id 6ae544f6-b608-4d8d-9f99-eabd5d5db0ad: the 6ae544f6-b608-4d8d-9f99-eabd5d5db0ad itself and another one referencing it as a parent - both of them are marked as ENDED_SUCCESSFULLY in the status field - other commands in table exists, 3 of them marked as active (none of them references 6ae544f6-b608-4d8d-9f99-eabd5d5db0ad)
You can check in the job table,
select * from job where correlation_id = 'd19c0b79-76dd-40df-af41-fc18e59bb536';
No job returned from job query. Can I proceed to remove 2 rows from command_entities referencing 6ae544f6-b608-4d8d-9f99-eabd5d5db0ad?
Thanks, gc