hi! I have a question: It happened to me several times that panic breaks and I have to restart it. I get the message Node monitor (blah) could not reach Substrate API at https://172.18.0.14:8080.
this was via telegram, I also got an alert on opsgenie but it was not critical . is there a way to customise it? How is it called in the config page? is it there?
Yeah, in this iteration we are just using 3333 and 9000
Читать полностью…So two issues: Rename didn't take effect, and the error doesn't go away
Читать полностью…But I re-added everything by hand, although I named "Chain name" Juno at first and then renamed to Evmos, it keeps using "JUNO" in the alert names
Читать полностью…It is important that while doing the migration panic is stopped
Читать полностью…Using the last version I have the same issue with Evmos RPC
Читать полностью…Creating migration ... doneЧитать полностью…
Traceback (most recent call last):
File "/opt/panic/scripts/config_to_database_migration.py", line 638, in <module>
configs += process_channels()
File "/opt/panic/scripts/config_to_database_migration.py", line 577, in process_channels
channels_processed = process_channel_config(channels_config)
File "/opt/panic/scripts/config_to_database_migration.py", line 565, in process_channel_config
generate_mongo_channel_config(channel_data, channel_type))
File "/opt/panic/scripts/config_to_database_migration.py", line 398, in generate_mongo_channel_config
mongo_config['configs'].append(subchain_old_new_ids[chain])
KeyError: 'chihuahua'
Its already there actually. You cann add the panic repo to the github monitor
Читать полностью…By the way, you don't need to restart anything when updating the configs as this is detected by the alerter automatically
Читать полностью…Most probably there is a new Substrate API version that PANIC does not yet support.
Читать полностью…It seems that you cannot access the backend from where you are accessing the frontend
Читать полностью…Quick question, before I had a nginx proxy server pointing a domain to this panic server -- but now it doesn't work. Not sure, the frontend shows that "Error connecting to the db make sure API docker service is running"
Читать полностью…And I disabled all monitoring and keep getting spammed with these:
"PANIC ERROR: Could not retrieve cosmos-rest data for juno: Cosmos Network Monitor (juno) could not access any synced indirect Cosmos REST node."
it was stopped (I killed the docker containers)
Читать полностью…Also the migration did indeed fail, the new app is now running but re-adding all chains manually
Читать полностью…Nope there is the general section for that
Читать полностью…True. Would need to create some sort of "chain" for Panic I guess?
Читать полностью…Maybe as part of the alerter you guys could have an alert for when a new tag is released 💡 for panic that is
Читать полностью…New version you can edit the configs on the UI :)
Читать полностью…