Okay. Good news is PANIC is running fine. The bad news is that I think you might want to add more RAM to accommodate for the nodes you are monitoring.
Читать полностью…Check if you have any component of panic stopping + restarting constantly please
Читать полностью…The mongo containers are split to promote load balancing. What I wish to see are your panic-alerter-1
logs.
@lolpelsh run sudo docker logs -f alerter
for me please, and send the output in a txt file to avoid spam
Hmm… it should work fine with that number.
Читать полностью…9 cosmos based nodes + 3 nodes in GENERAL chain
Читать полностью…Hey, what is the recommended server configuration for panic service? Seems that t3.large isn't enough for me, insufficient RAM
Читать полностью…Hello everyone, who do i talk to about integrating a flashbots-like product for parachain validators to earn MeV revenue?
Читать полностью…Leave a react on the message to make it more visible to others
Читать полностью…runing this bash scripts/reset_redis.sh
Try the following. This practically resets everything, but keeps your database intact:docker-compose kill
bash scripts/reset_redis.sh
bash scripts/reset_rabbit.sh
docker-compose up --build -d
Then access https://localhost:9000
and you should see the api docs. If the browser warns for certificate purposes, just accept it. It allows the API, DB and UI to interact with one another.
After that, access the UI and all should work.
Not sure if we should pin this message because it is quite useful to follow should most of the errors occur. If you find this useful, react with an emoji to make it more visible to others with similar issues.
on cosmos network do we get delegation and undelegation alert?
Читать полностью…@frenkrina try this & let me know how it goes. Another validator had a similar issue and I think it should work.
Читать полностью…Hello everybody. Anyone having problems with node_exporter on panic? I get notifications that the node is down and then it comes back up. The node works normally I only have these fake notifications. I tried to update the node_exporter but nothing changes. Does the same happen to you? Thanks
Читать полностью…after message about successfully initialized System, Node, Network, etc monitors there are also some messages about Network Alerter and Node Alerter resets (PANIC INTERNAL - Component: Cosmos Network Alerter has been reset for cosmos chain_name
).
After that, there are only several PANIC WARNING
messages
I got it, but I can't share it unfortunately.
If it helps, you can share with me messages you're looking for
Otherwise seems that I'll need to handle it by myself 🙂
nothing suspicious in the logs, to be honest
I thing that the main reason is in the mongo containers (replication or something)
However might not be a bad idea to add more RAM
Читать полностью…And this is only 2 hours after restarting :)
`
free -h
total used free shared buff/cache available
Mem: 7.7Gi 7.0Gi 121Mi 30Mi 510Mi 331Mi
Swap: 0B 0B 0B
`
Usually it’s 6GB RAM. How many nodes are you monitoring?
Читать полностью…Best to send an email on info@simply-vc.com.mt or staking@simply-vc.com.mt
Читать полностью…Hello, I wanted to let you know that the problem has since been resolved. Thank you very much 😃😃
Читать полностью…Hi @ordel0ne , currently no however we’ll keep you posted in the case that it’s added in the future
Читать полностью…Ok thanks Ciccio. I'll let you know in the next few hours if the problem recurs.
Читать полностью…If I restart node_exporter the problem is solved but then after a few hours it comes back.
Читать полностью…A good old fashioned restart sometimes works magic :)
Читать полностью…