Closed hsaidc closed 5 months ago
@hsaidc thanks so much indeed for submitting this issue with such great detail!
I'm suggesting a naïve enhancement that would mitigate this problem.
I could not replicate it. I've tried it many times, with databases bigger than 3GB and it worked well.
Is there a guide or instruction to delete the public.messages_backup table?
Is there a guide or instruction to delete the public.messages_backup table? Follow these:
You would need to install psql client (https://askubuntu.com/questions/1040765/how-to-install-psql-without-postgres)
Then, open a terminal and run the following to enter the database:
PGPASSWORD=test123 psql -U postgres -h 127.0.0.1 -p 5432 -w
Then, remove the table:
DROP TABLE messages_backup;
PGPASSWORD=test123 psql -U postgres -h 127.0.0.1 -p 5432 -w
ser after command it says wrong password for me.
root@nirnaegen:~# PGPASSWORD=test123 psql -U postgres -h 127.0.0.1 -p 5432 -w
psql: error: connection to server at "127.0.0.1", port 5432 failed: FATAL: password authentication failed for user "postgres"
connection to server at "127.0.0.1", port 5432 failed: FATAL: password authentication failed for user "postgres"
I updated my node installed using the
nwaku-compose
repository to version 0.26.0. After stopping the containers, I pulled commit #74 and restarted them usingdocker-compose up -d
(New version of nwaku image is downloaded). However, upon checking Grafana, I noticed no connected peers. Attempting to restart the containers again, I reviewed the nwaku logs and found the following errorsThen, I had to manually remove
public.messages_backup
table to make my node running again (I connected to docker and removed that table.). I wanted to let you know about the issue. You can access my Grafana dashboard via: http://35.199.170.55:3000/d/yns_4vFVk/nwaku-monitoring?orgId=1&refresh=1m