"service rhn-satellite status" unrecognized service.
I have installed RHN Satellite on my server and am at the stage where I can log in and beggin adding systems etc... At the moment I have no systems to be managed by Satellite but I had completed the installation and configuration of sat as described in Redhats installation guide, so it is now installed.
However when I enter "service rhn-satellite status" on the command line it results that rhn-satellite is an unrecognized service. Has the command changed or something?
It doesn't say what version of RHN Satellite you have installed, but I will guess that you have 5.4.x or 5.5 installed. Yes, the command has changed and it's available as /usr/sbin/rhn-satellite now, so you can just run "rhn-satellite status".
Hope this helps,
Thanks, yes it is version 5.4.1 and that worked, thanks a lot.
by the way do you know of any reason why you can't run RHN Satellite and RHEV-M on the same server? I know Redhat don't advise it, but in my case niether are going to be heavy or critical workloads...
Glad to hear that the initial question is resolved. :)
Running RHN Satellite and RHEV-M on the same server. Good question, and not one that I immediately know the answer to (if the question is really important, I would suggest getting this raised via your Red Hat Support representative in an issue). However, I would advise against it. Just looking at the installed Java packages from a Satellite and a RHEV-M, it looks like there could be collisions there, and that is just one set of packages.
I do not think that the workload as such would be a problem (scale the hardware to suit), but more that RHN Satellite have dependencies on specific packages, like Java among other things, and RHEV-M have other dependencies. If the two sets of dependencies contain something that is mutually exclusive, it simply would not work.
If you want to utilise the same physical machine for running both RHN Satellite and RHEV-M, I would advise to use virtualisation via KVM and run the two systems as virtual guests as they then run in their own instances and you can still use KSM to save some memory if the two guests are running the same major-minor of RHEL. Maybe that is a solution that would work for you?
I don't know specifically why you can not (or should not) run the Satellite and RHEVM products on the same host. Both have particular database requirements, specific package dependencies (java, jboss), and different authentication methods - so there may potentially be conflicts there. The Satellite installation is rather strict in recommending a basic installation and then allowing the satellite installation to install the remaining packages and dependencies.
If I was in your position, I would look into running RHEVM and Satellite as separate Virtual Machines using KVM/Qemu. Depending on your subscription, the additional guests may be included.
Also - managing the Satellite via the service command is not recommended.
/usr/sbin/rhn-satellite is the preferred method to manage the Satellite suite. This is due to all the service dependencies (i.e. oracle, apache/tomcat, osa-dispatcher, cobblerd, etc...) you need to make sure that the services are stopped and started in a particular order and are all functional.
I have not tried RHEV-M and RHN Satellite on the same server.
I have tried SAM and RHN Satellite on the same server this does not work.
I am afraid that RHEV-M and RHN Satellite have the same issues, the incompatible java needs.
As James Radtke suggests I would go for a combination of different guests on the same KVM/Qemu host.
Jan Gerrit Kootstra
While I have never tried this, I would not recommend such a configuration, the RHN Satellite service includes items such as Hibernate (and other JBoss/java origin packages) that Satellite has been thoroughly tested with to ensure compatibility, it's possible that the process of adding the relevant JBoss may install incompatible packages.
In addition, even though one particularly configuration may work (lets say Satellite 5.4.1 & RHEV 3.0), an upgrade of one of the two components could break the other, for instance an upgrade from RHEV 3.0 to 3.1, will require a move from JBoss AP 5 to JBoss AP 6 (this move has already caused issues for the compatibilty of having IPA services and RHEV installed on the same server, to the point that I believe it is no longer recommended).
As I've seen mentioned, you are likely going to be better off installing Satellite & RHEV-M onto two QEMU/KVM based virtual machines and configuring them side-by-side this way.
Thanks Anders, certainly something to think about, I may well have to go the KVM route if I can't have my Satellite and RHEVM it too.
Thank you all, that's a great help. A little dissapointing but there you go.