Simply Staking Community

07 Dec 2022 16:11

Yeah try access PANIC UI, remove the node, and then re-add it

Simply Staking Community

07 Dec 2022 16:09

instead of hard-resetting all PANIC, I think it is worth a try, no?

Simply Staking Community

07 Dec 2022 16:08

When all else fails, this usually does the trick

Simply Staking Community

07 Dec 2022 16:08

Also it worked for months

Simply Staking Community

07 Dec 2022 16:07

could be a firewall issue with the node...

Simply Staking Community

07 Dec 2022 16:07

In the UI I also see the same error

Simply Staking Community

07 Dec 2022 16:05

if you Test via PANIC UI, does it raise an error?

Simply Staking Community

07 Dec 2022 16:04

It's saying it can't reach it through the UI? or through PANIC logs?

Simply Staking Community

07 Dec 2022 11:04

How long has PANIC been running for?

Simply Staking Community

07 Dec 2022 10:37

I have it all setup but for some reason i get this alert from the bot in telegram. looks like its pulling the wrong data but i double checked all the urls and ports. node shows that it's fully sync'd

Node Jackal is now 2994783 blocks behind the node with the highest block height. Value has INCREASED above WARNING threshold.

Simply Staking Community

07 Dec 2022 08:59

im not sure i just installed from docker website. i'll try with the script

Simply Staking Community

07 Dec 2022 08:57

Mmm… I’m thinking it’s definitely an issue due to the docker version. What gives it away is that the migration container isn’t meant to stay ‘up’ after build. Can you try upgrade the version?

Simply Staking Community

07 Dec 2022 08:55

Well, not sure because this bug has never occurred before.

Simply Staking Community

07 Dec 2022 08:47

Looks like PANIC wasn’t set up well. Can you run docker ps?

Simply Staking Community

06 Dec 2022 15:43

Give it a try and let us know if you do so 😁

Simply Staking Community

07 Dec 2022 16:10

You mean instead of
docker-compose kill
bash scripts/reset_redis.sh
bash scripts/reset_rabbit.sh
docker-compose up --build -d

Simply Staking Community

07 Dec 2022 16:08

What if you remove the node (obviously taking down all the data), and re add it?

Simply Staking Community

07 Dec 2022 16:08

Without changing anything it "suddenly" started

Simply Staking Community

07 Dec 2022 16:08

I have it configured like all other nodes

Simply Staking Community

07 Dec 2022 16:07

and if u try access it in browser, ok?

Simply Staking Community

07 Dec 2022 16:06

07/12/2022 03:05:08 PM - SystemMonitor - ERROR - Error when retrieving data from http://IP:9100/metrics
07/12/2022 03:05:08 PM - SystemMonitor - ERROR - ('System OmniFlix Validator is unreachable', 5004)
Traceback (most recent call last):
...
...

Simply Staking Community

07 Dec 2022 16:04

TG notification, but I also checked log/monitors/system monitors

Simply Staking Community

07 Dec 2022 16:03

Hi, so I have 1 node that has been giving me headages. Panic keeps saying the system is down and it can't reach the ip:9100/metrics, but when I do it in the browser, there is no issue

Simply Staking Community

07 Dec 2022 10:38

where is it pulling the comparison data from?

Simply Staking Community

07 Dec 2022 09:14

Looks like installing from the script instead of the docker repo's on their website solved it. Thank you

Simply Staking Community

07 Dec 2022 08:57

this was a fresh install

Docker Compose version v2.12.2

Simply Staking Community

07 Dec 2022 08:55

Can you try access https://localhost:9000 ?

Simply Staking Community

07 Dec 2022 08:54

does it have anything to do with the docker version? i had to modify the scripts to use docker compose instead of docker-compose

Simply Staking Community

07 Dec 2022 08:37

Hey, trying to install panic but stuck on this step. For some reason there are no base chains available?

Simply Staking Community

06 Dec 2022 15:43

yes, probably you're right 🙂