-
Notifications
You must be signed in to change notification settings - Fork 40
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
Forward compatibility fix for CentOS 7.x platform and nmap-ncat issues. #37
Open
hookbot
wants to merge
21
commits into
moocowmoo:master
Choose a base branch
from
hookbot:master
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 13 commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
cf13427
Forward compatibility fix for CentOS 7.x platform.
979218c
Convert funding txn and address to use "dash-cli masternode status" i…
8fe8405
Get rid of WEB_NINJA_MN_ADDY
8227a26
Compatibility fixes to allow dashman to run on CentOS 6.x platform.
f98f9fc
Stop saying this ugly spewage:
86c492e
Fix argparse problems to work on CentOS 6.x
9025634
Fix STDERR redirection
6b655ee
Fix MN_STARTED setting to be compatible with the new DashCore v0.12.2…
4f1447a
Merging in recent moocowmoo changes.
907fea2
Merging in recent moocowmoo changes.
68825d7
Fix sentinel cron to avoid spewing stderr into $MAIL
24a9d12
Fix sentinel cron to avoid spewing stderr into $MAIL
01a4c45
More compatibility fixes:
77d2bc8
Adjust VERSION sniffer to itself.
f9639da
Merge 0.1.27 from 'moocowmoo/master'
a950c0c
For bash < 4.2.x, prevent the following crashing spewage:
19890aa
When dashd is offline, prevent this warning spewage:
b9a2d5c
Merge branch 'master' of ssh://ssh.github.com.:443/moocowmoo/dashman
d0be3f7
Fix this crashing spewage:
e465a01
Fix this crashing spewage:
fe363aa
Fix this crashing spewage:
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm guessing the wrapper is because the cron run doesn't have LD_LIBRARY_PATH set?
Instead, is there a way to set it in the initial virtualenv install at line 1219
virtualenv venv 2>/dev/null >/dev/null;
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, it MIGHT be possible to move that line up closer to line 1252 way up closer to line 1219, but I was scared of possible infinite grinding the "pip install" and "py.test" stuff when they attempt to run the "bin/python2" which never requires any LD_LIBRARY_PATH dancing around.
This wrapper is ONLY for CentOS 6.x where that new-fangled Python 2.7 requirement is nearly impossible to find. The only way I was able to get sentinel to work on CentOS 6.x was using the "scl" wrapper:
$ time scl enable python27 "~/dashman/dashman install sentinel"
And yes, no matter how hard I tried to fix the crontab entry to run the correct "scl" wrapper properly on CentOS 6.x platform, every time I accidentally update dashman, she keeps bricking over my goodness with that nasty stock "sentinel" crontab entry, then my node would fall into WATCHDOG_EXPIRED and I'd lose all my beans. I couldn't stand it anymore, so I added that patch to buttwag around all the frustrations. Now everything works great again on CentOS 6.x.
Basically, this just ensures that if there is any "$LD_LIBRARY_PATH" existing during the commandline installation, that same environment will exist when the cron runs too.
Fortunately, in the other 99% of the cases, this "$LD_LIBRARY_PATH" is already naked, so this line just doesn't do anything at all.
OH! What would be REALLY cool would be if dashman could automagically detect the version of python running and do all the "scl" wrapper stuff if that's the only way to reach python2.7 on the current system.
Yes, I realize this is ugly, but I'm open to any suggestions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NOTE: I've also found that CentOS 6.x runs more efficiently than CentOS 7.x (and other Platforms) on VMs with less memory resources, which is what really makes this patch so much more valuable to people who care about how much money it costs each month to keep a masternode up and running.