Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SYNX failure to launch #37

Open
DiCE1904 opened this issue Jan 3, 2018 · 1 comment
Open

SYNX failure to launch #37

DiCE1904 opened this issue Jan 3, 2018 · 1 comment

Comments

@DiCE1904
Copy link

DiCE1904 commented Jan 3, 2018

After the latest update to the script this error shows up:

last but not least, run /usr/local/bin/activate_masternodes_synx as root to activate your nodes.
root@SYNX:~/vps# /usr/local/bin/activate_masternodes_synx
Created symlink from /etc/systemd/system/multi-user.target.wants/synx_n1.service to /etc/systemd/system/synx_n1.service.
Job for synx_n1.service failed because the control process exited with error code. See "systemctl status synx_n1.service" and "journalctl -xe" for details.

@mikhail5555
Copy link

I believe this has something to do with the IPV6, SYNX doesn't need a different IP for each masternode and (from the client) I see only IPV4's and Onion ips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants