Simply Staking Community

06 Feb 2023 17:04

Hey! Sure thing you can dm me or drop an email at staking@simply-vc.com.mt if it is related to our validator operations

Simply Staking Community

26 Jan 2023 16:32

No, reason why here.

Simply Staking Community

26 Jan 2023 16:27

Yep highly likely that it is no longer compatible

Simply Staking Community

26 Jan 2023 16:20

Stride was upgraded and I guess it has the same issue as Evmos now

Simply Staking Community

25 Jan 2023 12:00

sec its rebuilding now, will send another screenshot when its done

Simply Staking Community

25 Jan 2023 11:59

Hold on, the containers are tagged with v1.3.0 here

Simply Staking Community

25 Jan 2023 11:57

any logs i should look into?

Simply Staking Community

25 Jan 2023 11:57

i think this happened to me on 1.3.0 as well which is why i reverted last time

Simply Staking Community

25 Jan 2023 11:53

I’ve never encountered that issue

Simply Staking Community

25 Jan 2023 11:51

A restart (as I explained in the pinned message) usually solves these minor errors

Simply Staking Community

25 Jan 2023 11:49

when trying to update alert settings i get this error:

{"status":536,"messages":[{"name":"could_not_save_data","description":"Could not save data to Database.","type":"error"}]}

Simply Staking Community

25 Jan 2023 11:34

ok after resetting and doing the steps in the 1.3.0 release notes i still had to edit the .env file and update the ip address, it seems it gets overwritten when fetching and changing branches

Simply Staking Community

25 Jan 2023 11:08

will reset and try again

Simply Staking Community

25 Jan 2023 11:07

i think i will reset and try again

Simply Staking Community

25 Jan 2023 11:06

is there an easy way to import them?

Simply Staking Community

06 Feb 2023 16:44

Hello , Could I speak with someone from the team please ?

Simply Staking Community

26 Jan 2023 16:32

is a fix in the works?

Simply Staking Community

26 Jan 2023 16:20

x: PANIC cannot obtain Rest data for x either due to Cosmos SDK or Tendermint incompatibility issues in the node used as data source. Please check the logs of x to detect which node is incompatible and disable it from being a data source. If no other compatible data source can be given (not even x), please disable Rest monitoring altogether for x.

Simply Staking Community

25 Jan 2023 12:02

@Quilamir will contact you privately

Simply Staking Community

25 Jan 2023 11:59

are you sure you correctly upgraded?

Simply Staking Community

25 Jan 2023 11:58

Like that you’d help us confirm if it is an issue caused by the new release

Simply Staking Community

25 Jan 2023 11:57

Mmm… I’d ask you to revert to v1.3.0, restart, and try it again.

Simply Staking Community

25 Jan 2023 11:53

just kill the docker-compose and run it again?

Simply Staking Community

25 Jan 2023 11:52

i was able to disable and enable sending of alerts, but not edit existing alert settings

Simply Staking Community

25 Jan 2023 11:51

Can you check if all containers are running correctly?

Simply Staking Community

25 Jan 2023 11:35

but it works and i have all the configs imported

Simply Staking Community

25 Jan 2023 11:12

yeah that did the trick

Simply Staking Community

25 Jan 2023 11:08

i moved the old installation to a differnt folder as backup and then copied the config directory, i assume the old database is probably needed as well

Simply Staking Community

25 Jan 2023 11:07

Did you run the migration script as per the upgrade instructions in the release notes?

Simply Staking Community

25 Jan 2023 11:06

however it did not import the settings from the config directory