Simply Staking Community

14 Nov 2022 22:37

11/11/2022 12:53:37 PM - SystemMonitor.RabbitMQApi - ERROR - RabbitMQ error in connect_unsafe

Simply Staking Community

14 Nov 2022 22:34

Yep, same as all the other ones that do work

Simply Staking Community

14 Nov 2022 22:33

This is a testnet validator, the other one is mainnet

Simply Staking Community

14 Nov 2022 22:32

Particularly for the missing nodes

Simply Staking Community

14 Nov 2022 22:31

Mmm… not sure what’s wrong.

Simply Staking Community

14 Nov 2022 22:30

Can you see erros with the latest logs?

Simply Staking Community

14 Nov 2022 22:29

sudo docker-compose logs -f alerter

Simply Staking Community

14 Nov 2022 22:27

Hi Dylan, again 2 nodes are not showing up on the UI System metrics. I've done these steps, but this time it did not fix the issue

Simply Staking Community

11 Nov 2022 16:33

#!/usr/bin/python3
# EASY-INSTALL-ENTRY-SCRIPT: 'docker-compose==1.25.0','console_scripts','docker-compose'
__requires__ = 'docker-compose==1.25.0'
import re
import sys
from pkg_resources import load_entry_point

if __name__ == '__main__':
if(sys.argv[1] == 'down'):
sys.exit("don't run docker-compose down or you will remove the whole Panic configuration!")
sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])
sys.exit(
load_entry_point('docker-compose==1.25.0', 'console_scripts', 'docker-compose')()
)

Simply Staking Community

11 Nov 2022 16:26

oh, it's because I didn't run upgrade_to_1_3_0.sh 😂

Simply Staking Community

11 Nov 2022 16:17

@Eleuname84 yes, that helped me, thank you!

Simply Staking Community

11 Nov 2022 15:58

if you check the console of the browser (F12) you will see an error, if you google it , you will find out you need to install CORS (addon for chrome or firefox) and whitelist the IP of panic. then it loads nicely

Simply Staking Community

11 Nov 2022 15:27

Great stuff. Will do that instead. Thank you!

Simply Staking Community

10 Nov 2022 21:43

Hi Simply Staking team. Whom may I contact in regards to proposals? :)

Simply Staking Community

08 Nov 2022 10:14

true, do you know how to make a copy of the mongodb? are there any credentials to use? can you imagine if you enter 100 validators and mistakenly run docker-compose down, and have to insert them 1 by 1 from the beginning? 😣🔫

Simply Staking Community

14 Nov 2022 22:34

Go on alerter/logs/monitors and opem the log file for the specific monitor

Simply Staking Community

14 Nov 2022 22:34

Lets have a look at the component logs

Simply Staking Community

14 Nov 2022 22:33

[node_6390a64c-780e-4c15-a64a-7fa0197201c3]
id=node_6390a64c-780e-4c15-a64a-7fa0197201c3
parent_id=chain_name_0196b352-f56b-409c-9d02-c540631a80d3
name=OmniFlix Testnet Validator
cosmos_rest_url=
monitor_cosmos_rest=false
prometheus_url=
monitor_prometheus=false
exporter_url=http://IP:9100/metrics
monitor_system=true
is_validator=true
monitor_node=true
is_archive_node=false
use_as_data_source=true
monitor_network=false
operator_address=
monitor_tendermint_rpc=true
tendermint_rpc_url=http://IP:26657

Simply Staking Community

14 Nov 2022 22:31

Can you send us a snippet of the configs (without exposing the IP)

Simply Staking Community

14 Nov 2022 22:30

Were the nodes you added, validator nodes?

Simply Staking Community

14 Nov 2022 22:29

wow that showed a lot

Simply Staking Community

14 Nov 2022 22:28

Can you please investigate the docker logs maybe there is something there

Simply Staking Community

11 Nov 2022 16:47

yes agree, now it looks like there are more chances to get that "surprise"
I should say that I liked the previous way of storing configs more. Just because you could backup config files and reset everything in case of any issues. Now it may require more debug steps, cause you can't just reset everything with docker system prune -a --volumes

anyway, after upgrade stript it loaded my previous configs and seems to be working fine 🙂
Thanks @Eleuname84 and SimplyVC team!

Simply Staking Community

11 Nov 2022 16:33

when I ran it, then I had to reinstall it from scratch, not sure if it works. another important thing is, once you'll be running 1.3.0, if you create your configuration and then stop the docker-compose with docker-compose down, then your config is gone forever, you should run dc kill instead. I've disabled the down option in /usr/bin/docker-compose to avoid surprises

Simply Staking Community

11 Nov 2022 16:20

but now it says "no configuration detected" 🙂

Simply Staking Community

11 Nov 2022 16:04

it's called Allow CORS: Access-Control-Allow-Origin for chrome, once installed, to activate it there's the toggle ON OFF on the bottom left of the popup window, it took me a moment to figure it out 😅

Simply Staking Community

11 Nov 2022 15:35

same for me after updating from 1.2.1 to 1.3.0. Did you solve it?

Simply Staking Community

10 Nov 2022 22:30

Hey, our preferred way is to reach out to info@simply-vc.com.mt, and it can be forwarded internally. Thanks!

Simply Staking Community

08 Nov 2022 10:16

Yeah, I agree. This is a feature in our backlog however we are not planing on another release for the time being, however we’ll keep you posted in that case. Thanks for the feedback 😉

Simply Staking Community

08 Nov 2022 10:00

In the mean time I found more info in the medium, so it is a little bit clearer now