sloppycoffee

Results 17 comments of sloppycoffee

Have this same issue on rinkeby trying to approve an erc20

I used your new install script and I saw it created config.json but in the logs I am getting this error: Jul 17 18:48:34 mn1 systemd[1]: Started Zen Secnodetracker Container....

I noticed that a directory called "local" was created in /mnt/zen/secnode. Is that correct? Tried many different things but all still come back to the error listed about about config.piv....

Yes. There is config.json in that folder.

{ "active": "", "secure": { "nodetype": "", "nodeid": null, "servers": [ "ts2.eu", "ts1.eu", "ts3.eu", "ts4.eu", "ts4.na", "ts3.na", "ts2.na", "ts1.na" ], "stakeaddr": "x", "email": "x", "fqdn": "snode1.convergegroup.tech", "ipv": "4", "region": "na",...

new parameter? I don't think the install.sh asked for that I did pop into the container and run setup.js which I completed successfully but the error was still present.

Yup, systemctl restart both zen-node and zen-secnodetracker. Multiple reboots. Nothing seemed to fix it.. There is a local directory inside secnode dir. Not sure if that is normal or not.

I got this error: Jul 18 03:20:30 mn1 docker[11549]: No secure node config found. exiting Jul 18 03:20:30 mn1 systemd[1]: zen-secnodetracker.service: Main process exited, code=exited, status=1/FAILURE Jul 18 03:20:30 mn1...

root@mn1:/mnt/zen/secnode# pwd /mnt/zen/secnode root@mn1:/mnt/zen/secnode# ls config.json root@mn1:/mnt/zen/secnode#

Outside the container. Ran it sitting inside /mnt/zen/secnode