-
Notifications
You must be signed in to change notification settings - Fork 3
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
whatsup not working, pdsh working minus whatsup #1
Comments
Typically "internal backend module error" means something has just been setup incorrectly. It's most likely the backend for whatsup. Do you know which one you're using? My assumption is the pingd daemon since this comes from RHEL. Are you using something to specify the nodes/hosts in your cluster? If what I'm talking about makes no sense, there's a summary in the README. https://github.com/chaos/whatsup/blob/master/README |
This readme doesn't show genders as an option. Somewhere I thought I read genders was okay and also saw the nodeupdown_clusterlist_genders.so file. So I assumed I was okay. find /usr -name "nodeup"/usr/lib64/pdsh/nodeupdown.so |
Genders is an option for listing hosts. Please see the README again. pingd is probably your best bet. You need to install the whatsup-pingd subpackage and update /etc/pingd.conf (and perhaps also chkconfig the pingd daemon on, unclear to me what RHEL does by default). |
I have whatsup installed on RHEL7 but it’s not working. I was hoping you could assist.
See attached trace log
whatsup
whatsup: _output_mode: nodeupdown_load_data(): internal backend module error
rpm -qa | egrep "pdsh|whats|nodeup" | sort
libnodeupdown-1.14-8.el7.x86_64
libnodeupdown-clusterlist-genders-1.14-8.el7.x86_64
pdsh-2.31-1.el7.x86_64
pdsh-mod-genders-2.31-1.el7.x86_64
pdsh-mod-nodeupdown-2.31-1.el7.x86_64
pdsh-rcmd-ssh-2.31-1.el7.x86_64
whatsup-1.14-8.el7.x86_64
Steven Fishback
System Administrator
ITS-Research Computing
University of North Carolina-CH
trace.txt
The text was updated successfully, but these errors were encountered: