v20.5.1 Doesnt boot

[hdiass]

🐛 Bug Report

📝 Description

After having issues with v20.1.0 i tried to update to v20.4.0 and it crashed.. then i updated to v20.5.1 and it doesn't even boot External node image version v20.5.1 doesnt boot or throw any logs

🔄 Reproduction Steps

Steps to reproduce the behaviour

🤔 Expected Behavior

Start external node normally

😯 Current Behavior

Gets stuck and doesn't throw any log

🖥️ Environment

matterlabs/external-node:v20.5.1

📋 Additional Context

Add any other context about the problem here. If applicable, add screenshots to help explain.

📎 Log Output

Paste any relevant log output here.

[gathecageorge]

Same thing happened when we upgraded from 20.4.0 to 20.5.1, a table was deleted resulting in error log shown below and continuous restart. Creating the table and restarting node resolved the issue.

thread 'main' panicked at /usr/src/zksync/core/lib/dal/src/transactions_dal.rs:855:14: called Result::unwrap() on an Err value: Database(PgDatabaseError { severity: Error, code: "42P01", message: "relation "call_traces" does not exist", detail: None, hint: None, position: Some(Original(30)), where: None, schema: None, table: None, column: None, data_type: None, constraint: None, file: Some("parse_relation.c"), line: Some(1449), routine: Some("parserOpenTable") })

create table call_traces ( tx_hash bytea not null primary key references transactions on delete cascade, call_trace bytea not null )

[sarkic20]

Great project

[raymonredington]

Interesting, I'll look at that

[EmilLuta]

Hello folks. We've recently had a few bumpy releases with respect to database manipulations. There have been discussions and we have a temporary solution to double check such changes (can be seen here). @Deniallugo, @RomanBrodetski do you happen to know what is the correct version for ENs to run?

[Deniallugo]

@hdiass Thanks for the report. You have to run the latest possible version, now it's 20.5.2 and it's expected that boot time is higher, because we are performing relatively high migration at the start.

[hdiass]

I think there are some better ways to approach release management on this project too..in last 5 days there were 5 releases, can't they been joint together in one release ?

[RomanBrodetski]

in last 5 days there were 5 releases, can't they been joint together in one release ?

@hdiass in theoery they could, but we have our internal deployment system using those releases, and we needed to deploy. We can have a separate pipeline/links for releases that should be public. @Deniallugo I think you gave it a thought - did we decided against it?

[RomanBrodetski]

I think @githubdoramon raised it on our call

[patapata24]

Great project

[dzhamilrustamov]

describe your problem in more detail

[jcarlo-vs]

have u resolved this issue sir?

[EmilLuta]

ENs are working fine on the latest releases. I will close this issue, but feel free to comment/reopen if you feel the problem is not addressed.