I have two Cobbler Servers - one old one I set up almost two years ago, and another one I am currently trying to build from scratch.
The problem is that I cannot get the new one started up properly. Cobbler 2.2.3 on 64 bit RHEL 5 Here are some of the problems : I am not using RHEL's httpd due to local practice of having multiple "stove-pipe" web stacks on each server. The apache instance is in /opt/site/cobbler/data/apache instead of /var/www On the old Cobbler, I used RHEL-httpd and sym-linked /var/www/(cobbler/ cobbler_webui_content) to another partition. On the old one, I was running everything from the hardware IP On the new one, I am using a vhost On the old one, netstat says I have one httpd listening on <host-ip>:80, and one listening on 0.0.0.0:443 On the new one, I have one httpd listening on <host-ip>:80, and one listening on <host-ip>:443 Both have a listener on 127.0.0.1:25151 (python) The first problem is that everything works on the old one and on the new one, I get this: [root ~]# cobbler sync httpd does not appear to be running and proxying cobbler, or SELinux is in the way. Original traceback: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/cobbler/cli.py", line 184, in check_setup s.ping() File "/usr/lib64/python2.4/xmlrpclib.py", line 1096, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.4/xmlrpclib.py", line 1383, in __request verbose=self.__verbose File "/usr/lib64/python2.4/xmlrpclib.py", line 1137, in request headers ProtocolError: <ProtocolError for 10.1.1.134:80/cobbler_api: 302 Found> >From the other end, the Web UI comes up but I cannot get past the login screen >and I see no errors in the logs. “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes)
_______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler
