On Tue, 3 Apr 2012 17:42:05 -0500, James Cammarata wrote:
On Tue, Apr 3, 2012 at 4:51 PM, Michael Hughes <[email protected]> wrote:
Hi Cobblers :)

I followed the steps on

https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/UbuntuServerGuide
to install a functional Orchestra system and brought up two servers
(yea!) I am running Precise x86_64.

I'm trying to understand Cobbler and ran 'cobbler check' which
returned two anomalies. I don't recall the exact problems and they've
long scrolled out of the buffer, but one suggestion was to restart
cobblerd, which I did, and the other suggested running 'cobbler sync'.
I did so and received this error:

$ sudo cobbler-sync
Traceback (most recent call last):
 File "/usr/bin/cobbler", line 35, in <module>
   sys.exit(app.main())
 File "/usr/lib/python2.7/dist-packages/cobbler/cli.py", line 543, in main
   rc = cli.run(sys.argv)
 File "/usr/lib/python2.7/dist-packages/cobbler/cli.py", line 197, in run
   self.token         = self.remote.login("", self.shared_secret)
 File "/usr/lib/python2.7/xmlrpclib.py", line 1224, in __call__
   return self.__send(self.__name, args)
 File "/usr/lib/python2.7/xmlrpclib.py", line 1578, in __request
   verbose=self.__verbose
 File "/usr/lib/python2.7/xmlrpclib.py", line 1264, in request
   return self.single_request(host, handler, request_body, verbose)
 File "/usr/lib/python2.7/xmlrpclib.py", line 1297, in single_request
   return self.parse_response(response)
 File "/usr/lib/python2.7/xmlrpclib.py", line 1473, in parse_response
   return u.close()
 File "/usr/lib/python2.7/xmlrpclib.py", line 793, in close
   raise Fault(**self._stack[0])
xmlrpclib.Fault: <Fault 1: "<class 'cobbler.cexceptions.CX'>:'login failed'">
$

Now when I attempt to run 'cobbler check' I get a similar error to the
above rather than the sane response I got the first time.

As a side note, I am unable to log into the new nodes. I tried several
variants of passwords, (root/cobbler, etc.) but am not able to.

Any hints appreciated!

It would seem to be an incorrect authn module, or maybe selinux
blocking access to the session directory for apache.

If it's on ubuntu, SELinux is unlikely to be the culprit - I'd be looking at the authn settings as JC suggests.

look at the apache error logs too, to rule out permissions issues.

Stuart
--
Stuart Sears RHCA etc.
"It's today!" said Piglet.
"My favourite day," said Pooh.
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler

Reply via email to