Check the shell of the xymon user. If you’re not sure how to do that:
grep xymon /etc/users. The last field should be the shell. It’s likely
set to nologin or some such. SU has a command line switch to specify a
shell, that would be the easiest and most secure way to work around it.
*Scot Kreienkamp | Senior Systems Engineer | La-Z-Boy Corporate*
One La-Z-Boy Drive | Monroe, Michigan 48162 | Office: XXX-XXX-XXXX | |
Mobile: XXXXXXXXXX | Email: user-9678697f1438@xymon.invalid
*From:* Michael Resnick [mailto:user-7fba2d5d51fe@xymon.invalid]
*Sent:* Monday, November 30, 2015 9:10 AM
*To:* xymon at xymon.com
*Subject:* rclient on new xymon install via rpms
I am trying to set up monitoring for about 2,000 servers, and
unfortunately, it is going to take a while to get a port open, so I want to
use rclient via ssh.
Normally I would su into the xymon user, create the ssh keys and push
them out. On this new server via terabith rpms ( RHEL 6.6 ), I get
# su - xymon
This account is currently not available.
What is a workaround for this so that I can use rclient ?
Thanks !
This message is intended only for the individual or entity to which it is
addressed. It may contain privileged, confidential information which is
exempt from disclosure under applicable laws. If you are not the intended
recipient, you are strictly prohibited from disseminating or distributing
this information (other than to the intended recipient) or copying this
information. If you have received this communication in error, please
notify us immediately by e-mail or by telephone at the above number.
Thank you.