Why this rhnsd service is showing error in SuSE server?
This is using SuSE SLES 12 servers. Every once in a while, expect to see the following errors logged in the /var/log/messages,
serverA rhn_check[14513]: XMLRPC ProtocolError: <ProtocolError for susemanager01.abc.corp /XMLRPC: 500 Internal Server Error>
serverA systemd[1]: rhnsd.service: Unit entered failed state.
serverA systemd[1]: rhnsd.service: Failed with result 'exit-code'.
rhnsd is Spacewalk Server daemon. Look like it has to coordinates with rhnsd.timer and SuSE Manager.
What's went wrong with this service? could it be the SuSE Manager problem/
Thanks in advance.
serverA rhn_check[14513]: XMLRPC ProtocolError: <ProtocolError for susemanager01.abc.corp /XMLRPC: 500 Internal Server Error>
serverA systemd[1]: rhnsd.service: Unit entered failed state.
serverA systemd[1]: rhnsd.service: Failed with result 'exit-code'.
rhnsd is Spacewalk Server daemon. Look like it has to coordinates with rhnsd.timer and SuSE Manager.
What's went wrong with this service? could it be the SuSE Manager problem/
Thanks in advance.
ASKER
Hi David,
Did this service trys to contact susemgr?
Did this service trys to contact susemgr?
The docs are unclear.
Your best action will likely be to either dig into the entire rhnsd config files + docs.
Or ask your question in the SUSE forums.
It's unclear what the purpose is of this daemon, over CRON... rhnsd appears to be a scaled down/hobbled version of CRON.
Your best action will likely be to either dig into the entire rhnsd config files + docs.
Or ask your question in the SUSE forums.
It's unclear what the purpose is of this daemon, over CRON... rhnsd appears to be a scaled down/hobbled version of CRON.
ASKER
Hi David,
We already contacted SuSE support. They said that ONLY rhnsd.timer is working. We also provide the supportconfig to them to analyse. So, just sit back to wait for the updates.
We already contacted SuSE support. They said that ONLY rhnsd.timer is working. We also provide the supportconfig to them to analyse. So, just sit back to wait for the updates.
https://superuser.com/questions/1448871/rhnsd-service-not-working-after-upgrade-from-5-0-37-to-5-0-44 provides some detail about this service.
My next question to SUSE would be, "If I remove rhnsd does this actually break anything?"
If the answer is no, remove this service.
Each time I've read over the docs, rhnsd appears to provide no value, while opening a potential security holes in the system.
Good Guideline: If you don't need it, deinstall it...
My next question to SUSE would be, "If I remove rhnsd does this actually break anything?"
If the answer is no, remove this service.
Each time I've read over the docs, rhnsd appears to provide no value, while opening a potential security holes in the system.
Good Guideline: If you don't need it, deinstall it...
ASKER
Hi David,
We already contacted SuSE support. They said that ONLY rhnsd.timer is working. We also provide the supportconfig to them to analyse. So, just sit back to wait for the updates.
We already contacted SuSE support. They said that ONLY rhnsd.timer is working. We also provide the supportconfig to them to analyse. So, just sit back to wait for the updates.
SUSE dev question to pose.
"Describe problems, if I just delete the entire rhnsd service."
Since no other Distro (to my knowledge) ever installs this service, likely just deleting it will suffice.
And, best to ask SUSE dev before you delete this service.
"Describe problems, if I just delete the entire rhnsd service."
Since no other Distro (to my knowledge) ever installs this service, likely just deleting it will suffice.
And, best to ask SUSE dev before you delete this service.
ASKER
At the end, the root cause is the SuSE manager server runs out of hard disk space + other config problem. After solving the hard disk space problem, found no more rhnsd errors in /var/log/messages.
rhnsd besides rhnsd.timer is needed, can not remove
rhnsd besides rhnsd.timer is needed, can not remove
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The docs are terse.
No real information about what this daemon truly does in background.
Docs suggest a CRON-like facility... although... I'm wondering, why not just use CRON.