Oops! We removed busybox
-
Hey gang,
We have a security trainee that we directed to remove busybox from one of our xcp-ng servers and now the server will not not bring up any xcp-ng services. When we run xsconsole we are getting a
Traceback (most recent call last):
File "/usr/lib64/xsconsole/XSConsole.py", line 21, in <module>
from XSConsoleLang import *
File "/usr/lib64/xsconsole/XSConsoleLang.py", line 19, in <module>
import XenAPI # For XenAPI.Failure
ImportError: No module named XenAPIWe've attempted to install busybox back on the machine but it still gives us this error. 8.2 has been working really great for us so we don't have a lot of experience digging around on the server trying to fix things.
Any help would be appreciated.
-
Your best option is probably to "upgrade" the existing install using the ISO.
-
I suggest using this as a learning opportunity. Look at the RPM log and see what depends on busybox, and therefore what (else) got uninstalled in order to keep the dependencies satisfied.
(Hint: you uninstalled all of Xapi, hence why nothing works)
-
Thanks for the feedback folks. I upgraded using the installation media and it worked like a charm but, I suspect this machine was fated to EOL. As soon as we got the machine back up the raid volume corrupted. I'll take a look as suggested about how busybox is related to the xapi. The vulnerability scanners are screaming about the cve's associated with the the package so we've been removing the package from other machines it's not required on. This was simply an administrative faux pas on our part for sure. We've been very happy with xcp-ng and still consider it a rock solid solution.
Thanks again for responding!
-
Interpreting vulnerability scanners is a hard task. They are often screaming for "common cases", but remember XCP-ng is an appliance, so there are many cases where things do not apply. Happy to help you further via our pro support to answer in details your concerns
