running cobbler inside a CT [message #40160] |
Fri, 23 July 2010 13:58 |
olojoh1977
Messages: 6 Registered: July 2010 Location: Sthlm Sweden
|
Junior Member |
|
|
Hi,
I'm having problem setting up a cobbler-server inside a container.
When I run cobbler check, I get an ouput:
[root@localhost ~]# cobbler check
httpd does not appear to be running and proxying cobbler
httpd is running and SELinux is disabled on CT0. On CTxxx /etc/selinux is not present.
On a physical server I have no problem setting up cobbler.
Thankful for any input.
Kind regards Olof
|
|
|
Re: running cobbler inside a CT [message #40164 is a reply to message #40160] |
Fri, 23 July 2010 14:39 |
maratrus
Messages: 1495 Registered: August 2007 Location: Moscow
|
Senior Member |
|
|
It seems that I was able to reproduce exactly the same problem:
# cobbler check
httpd does not appear to be running and proxying cobbler
restarting httpd service seems to help me
# service httpd stop
Stopping httpd: [ OK ]
# cobbler check
httpd does not appear to be running and proxying cobbler
# service httpd start
Starting httpd: [ OK ]
# cobbler check
The following are potential configuration items that you may want to fix:
1 : The 'server' field in /etc/cobbler/settings must be set to something other than localhost, or kickstarting features will not work. This should be a resolvable hostname or IP for the boot server as reachable by all machines that will use it.
2 : For PXE to be functional, the 'next_server' field in /etc/cobbler/settings must be set to something other than 127.0.0.1, and should match the IP of the boot server on the PXE network.
3 : some network boot-loaders are missing from /var/lib/cobbler/loaders, you may run 'cobbler get-loaders' to download them, or, if you only want to handle x86/x86_64 netbooting, you may ensure that you have installed a *recent* version of the syslinux package installed and can ignore this message entirely. Files in this directory, should you want to support all architectures, should include pxelinux.0, menu.c32, elilo.efi, and yaboot. The 'cobbler get-loaders' command is the easiest way to resolve these requirements.
4 : change 'disable' to 'no' in /etc/xinetd.d/tftp
5 : change 'disable' to 'no' in /etc/xinetd.d/rsync
6 : since iptables may be running, ensure 69, 80, and 25151 are unblocked
7 : debmirror package is not installed, it will be required to manage debian deployments and repositories
8 : The default password used by the sample templates for newly installed machines (default_password_crypted in /etc/cobbler/settings) is still set to 'cobbler' and should be changed, try: "openssl passwd -1 -salt 'random-phrase-here' 'your-password-here'" to generate new one
Restart cobblerd and then run 'cobbler sync' to apply changes.
|
|
|
|
|
|
|
|
|
|
Re: running cobbler inside a CT [message #40727 is a reply to message #40212] |
Fri, 24 September 2010 19:37 |
pasencorelui
Messages: 1 Registered: September 2010 Location: Montreal
|
Junior Member |
|
|
Inside or outside...
I did the installation of Spacewalk and i get exactly the same issue as what you described...
Did you find any solution from your side. I did a lot of research without finding a working solution.
Thank you,
Pasencorelui
|
|
|