doublesharp.com/sysmasternode Script

[johnp1954]

If you use this script to update your VPS and ask for sentinel to upgrade too it seems to break sentinel. Using the script amended by Alex does not break it when updating Sentinel. It has been like this for 1.5 hours now.

[sidhujag]

need more details.. hows it break sentinel

[johnp1954]

If i knew that i could fix it :-)

[doublesharp]

Not enough info to debug

[johnp1954]

Let me know what i can do to give you that info

[johnp1954]

I can give you access to the VPS if that would help

[doublesharp]

Is the sentinel folder created under the syscoin use home? What's in the debug log? Are the cron jobs for the syscoin user set up? If you are running other scripts are they doing anything that might conflict especially permissions? Can you run the ping manually?

[johnp1954]

Just FYI this worked fine before the upgrade

1. Yes
2. Isnt one
3. • • • • • /usr/local/bin/sentinel-ping
4. No

[johnp1954]

Others say
*/10 * * * * /usr/local/bin/sentinel-ping
Is this the issue?

[johnp1954]

Ok well i have to reinstall now before i have to go through the grace period again

[doublesharp]

The Sentinel log is in ~/sentinel/sentinel-cron.log under the syscoin user. Cronjob will run once per minute (people were impatient) but */10 should work fine too, but will take longer to update from ping expired. Nothing in your setup seems off, so check the log and try to run the ping as the syscoin user sudo su -c "sentinel-ping" syscoin.

[johnp1954]

Had to rebuild will try again when things calm down, there was no ~/sentinel/sentinel-cron.log

[doublesharp]

Then the ping is never running but I suspect you are looking in the wrong place - did you check as the syscoin user? When you use ~ it means "home" so you have to run it as that user - sudo su -c "tail ~/sentinel/sentinel-cron.log" syscoin.

I also checked out @einalexes script and it does not work properly, it updates sentinel in the wrong location (current user home). It will have no effect on the sentinel/ping/crontab running as the syscoin user.

[jvlugoinv]

Sorry to interject the conversation, but I am in the same boat. Applied Justin's script to upgrade 3.0.5 (which was working perfectly fine) to 3.0.6, used the script to upgrade with the option to also update Sentinel, and now the mn is down for a whole day with SENTINEL_PING_EXPIRED status. Any solution on this?

…

On Tue, Jun 26, 2018 at 10:44 AM Justin Silver ***@***.***> wrote: The Sentinel log is in ~/sentinel/sentinel-cron.log under the syscoin user. Cronjob will run once per minute (people were impatient) but */10 should work fine too, but will take longer to update from ping expired. Nothing in your setup seems off, so check the log and try to run the ping as the syscoin user sudo su -c "sentinel-ping" syscoin. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#231 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AkjTE3noDdzI5_nWPXxy99bwHohmo0R4ks5uAnL5gaJpZM4U4JFP> .

[jvlugoinv]

Working with @einalex. He found that the /usr/local/bin/sentinel-ping file was empty. He guided me to add this to the file:

…

--- #!/bin/bash /home/syscoin/sentinel/venv/bin/python /home/syscoin/sentinel/bin/sentinel.py 2>&1 >> /home/syscoin/sentinel/sentinel-cron.log ----

On Tue, Jun 26, 2018 at 2:16 PM Vladimir Lugo ***@***.***> wrote: Sorry to interject the conversation, but I am in the same boat. Applied Justin's script to upgrade 3.0.5 (which was working perfectly fine) to 3.0.6, used the script to upgrade with the option to also update Sentinel, and now the mn is down for a whole day with SENTINEL_PING_EXPIRED status. Any solution on this? On Tue, Jun 26, 2018 at 10:44 AM Justin Silver ***@***.***> wrote: > The Sentinel log is in ~/sentinel/sentinel-cron.log under the syscoin > user. Cronjob will run once per minute (people were impatient) but */10 > should work fine too, but will take longer to update from ping expired. > Nothing in your setup seems off, so check the log and try to run the ping > as the syscoin user sudo su -c "sentinel-ping" syscoin. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#231 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AkjTE3noDdzI5_nWPXxy99bwHohmo0R4ks5uAnL5gaJpZM4U4JFP> > . >

[doublesharp]

Thanks @jvlugoinv - I re-ordered commands in the script and it should work now.

[doublesharp]

@jvlugoinv @johnp1954 you can rerun the script and it will update the file correctly.

[johnp1954]

Rerun with no issues Thanks