-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/26/2011 10:28 AM, Kevin Holmes wrote: > I can confirm the Mongo directory problem happens with CentOS 5.5 - however > that was fixed quickly thanks to your FAQ :) > > Another problem is the lack of a suitable CentOS repository for > qpid-cpp-server* packages. I believe the CERN distribution includes them, but > CentOS does not. > > I haven't made any progress on this, looking forward to seeing what Jay finds.
I don't want to leave you hanging on this, so as a quick status update we're working on some information on how to get these packages on CentOS. We'll let you know as soon as we're done. > - Kevin > > ----- Original Message ----- > From: "Jay Dobies" <[email protected]> > To: [email protected] > Sent: Wednesday, January 26, 2011 8:14:33 AM > Subject: Re: [Pulp-list] New Pulp installation - unknown errors > > What Christian mentioned is a potential problem; some packagings of > Mongo do not correctly install. Check out this entry on the FAQ: > http://pulpproject.org/ug/UGFAQ.html#MongodwontstartwheninstalledfromEL5 > > I'm going to set up a CentOS guest this morning and see if there are any > steps specific to CentOS that need to be taken. > > > On 01/25/2011 05:56 PM, Kevin Holmes wrote: > >> For Python: > >> Python 2.4.3 (#1, Nov 11 2010, 13:30:19) >> [GCC 4.1.2 20080704 (Red Hat 4.1.2-48)] on linux2 > >> Operating system is CentOS: > >> Linux blueberry 2.6.18-194.32.1.el5 #1 SMP Wed Jan 5 17:52:25 EST 2011 >> x86_64 x86_64 x86_64 GNU/Linux > >> I just updated to the testing repository and ran a yum update. That was >> successful, the error has changed now: > >> [root@blueberry log]# pulp-admin auth login -u admin -p admin >> error: operation failed: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >> <html><head> >> <title>500 Internal Server Error</title> >> </head><body> >> <h1>Internal Server Error</h1> >> <p>The server encountered an internal error or >> misconfiguration and was unable to complete >> your request.</p> >> <p>Please contact the server administrator, >> root@localhost and inform them of the time the error occurred, >> and anything you might have done that may have >> caused the error.</p> >> <p>More information about this error may be available >> in the server error log.</p> >> <hr> >> <address>Apache/2.2.3 (CentOS) Server at blueberry Port 443</address> >> </body></html> > >> Apache Logs: > >> ==> ssl_access_log <== >> 127.0.0.1 - - [25/Jan/2011:17:31:22 -0500] "GET >> /pulp/api//users/admin_certificate/ HTTP/1.1" 500 609 > >> ==> ssl_error_log <== >> [Tue Jan 25 17:33:22 2011] [error] [client 127.0.0.1] Premature end of >> script headers: webservices.wsgi > >> ==> ssl_request_log <== >> [25/Jan/2011:17:31:22 -0500] 127.0.0.1 TLSv1 DHE-RSA-AES256-SHA "GET >> /pulp/api//users/admin_certificate/ HTTP/1.1" 609 > >> ==> access_log <== >> 127.0.0.1 - - [25/Jan/2011:17:34:01 -0500] "GET / HTTP/1.1" 200 1301 "-" >> "check_http/v1.4.15 (nagios-plugins 1.4.15)" > >> Just using curl gives me the same outcome: > >> [root@blueberry pulp]# curl -k -u admin:admin >> https://blueberry/pulp/api/repositories >> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >> <html><head> >> <title>500 Internal Server Error</title> >> </head><body> >> <h1>Internal Server Error</h1> >> <p>The server encountered an internal error or >> misconfiguration and was unable to complete >> your request.</p> >> <p>Please contact the server administrator, >> root@localhost and inform them of the time the error occurred, >> and anything you might have done that may have >> caused the error.</p> >> <p>More information about this error may be available >> in the server error log.</p> >> <hr> >> <address>Apache/2.2.3 (CentOS) Server at blueberry Port 443</address> >> </body></html> > >> Apache logs: > >> ==> ssl_access_log <== >> 127.0.0.1 - - [25/Jan/2011:17:41:14 -0500] "GET /pulp/api/repositories >> HTTP/1.1" 500 609 > >> ==> ssl_error_log <== >> [Tue Jan 25 17:43:14 2011] [error] [client 127.0.0.1] Premature end of >> script headers: webservices.wsgi > >> ==> ssl_request_log <== >> [25/Jan/2011:17:41:14 -0500] 127.0.0.1 TLSv1 DHE-RSA-AES256-SHA "GET >> /pulp/api/repositories HTTP/1.1" 609 > > >> So it's looking like that probably fixed the original problem. But now I may >> have hit some kind of configuration issue? The errors here are not very >> descriptive. Your help is appreciated. I've gone through the install page >> and followed the directions as closely as possible. > >> - Kevin > >> ----- Original Message ----- >> From: "Jay Dobies" <[email protected]> >> To: [email protected] >> Sent: Tuesday, January 25, 2011 4:06:19 PM >> Subject: Re: [Pulp-list] New Pulp installation - unknown errors > >> This looks like a python version issue. What version of python are you >> using? What operating system? > >> If it's python 2.4, we've only just sorted these issues out in our >> testing build (built yesterday, as compared to the community release >> which does not contain the fixes). > >> The testing repository is hosted along side the community release (be >> sure to append the appropriate os/arch to the following URL): >> http://repos.fedorapeople.org/repos/pulp/pulp/testing/ > >> And the installation instructions: >> https://fedorahosted.org/pulp/wiki/UGInstallation > >> Please let me know if you keep running into issues. > > > >> On 01/25/2011 04:01 PM, Kevin Holmes wrote: >>> Hi everyone, > >>> New Pulp install and I'm having a problem. > >>> I cannot seem to issue any commands with the pulp cli tools. > >>> For instance: > >>> [root@blueberry pub]# pulp-admin auth login -u admin -p admin >>> Traceback (most recent call last): >>> File "/usr/bin/pulp-admin", line 147, in ? >>> admin.main() >>> File "/usr/lib/python2.4/site-packages/pulp/client/cli/base.py", line >>> 98, in main >>> command.main(args[1:]) >>> File "/usr/lib/python2.4/site-packages/pulp/client/core/base.py", line >>> 118, in main >>> action.main(args[1:]) >>> File "/usr/lib/python2.4/site-packages/pulp/client/core/base.py", line >>> 229, in main >>> self.run() >>> File "/usr/lib/python2.4/site-packages/pulp/client/core/auth.py", line >>> 47, in run >>> cert_dict = self.authconn.admin_certificate() >>> File "/usr/lib/python2.4/site-packages/pulp/client/connection.py", >>> line 671, in admin_certificate >>> return self.conn.request_get(method) >>> File "/usr/lib/python2.4/site-packages/pulp/client/connection.py", >>> line 126, in request_get >>> return self._request("GET", method) >>> File "/usr/lib/python2.4/site-packages/pulp/client/connection.py", >>> line 114, in _request >>> self.validateResponse(response) >>> File "/usr/lib/python2.4/site-packages/pulp/client/connection.py", >>> line 122, in validateResponse >>> raise RestlibException(response.status, response.read()) >>> File "/usr/lib/python2.4/site-packages/pulp/client/connection.py", >>> line 50, in __init__ >>> super(RestlibException, self).__init__(code, msg) >>> TypeError: super() argument 1 must be type, not classobj > >>> Corresponding Apache logs: > >>> ==> ssl_access_log <== >>> 127.0.0.1 - - [25/Jan/2011:15:46:47 -0500] "GET >>> /pulp/api//users/admin_certificate/ HTTP/1.1" 500 609 > >>> ==> ssl_error_log <== >>> [Tue Jan 25 15:48:47 2011] [error] [client 127.0.0.1] Premature end of >>> script headers: webservices.wsgi > >>> ==> ssl_request_log <== >>> [25/Jan/2011:15:46:47 -0500] 127.0.0.1 TLSv1 DHE-RSA-AES256-SHA "GET >>> /pulp/api//users/admin_certificate/ HTTP/1.1" 609 > > >>> Running user update also fails, but nothing shows up in my Apache logs. > >>> [root@blueberry pub]# pulp-admin user update >>> Traceback (most recent call last): >>> File "/usr/bin/pulp-admin", line 147, in ? >>> admin.main() >>> File "/usr/lib/python2.4/site-packages/pulp/client/cli/base.py", line >>> 98, in main >>> command.main(args[1:]) >>> File "/usr/lib/python2.4/site-packages/pulp/client/core/base.py", line >>> 118, in main >>> action.main(args[1:]) >>> File "/usr/lib/python2.4/site-packages/pulp/client/core/base.py", line >>> 228, in main >>> self.setup_connections() >>> File "/usr/lib/python2.4/site-packages/pulp/client/core/user.py", line >>> 37, in setup_connections >>> system_exit(-1, ce.message) >>> AttributeError: CredentialError instance has no attribute 'message' > >>> So far this seems like a really cool project. I hope to get it working >>> on our systems in the future. > >>> - Kevin > > > >>> _______________________________________________ >>> Pulp-list mailing list >>> [email protected] >>> https://www.redhat.com/mailman/listinfo/pulp-list > > > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list > > _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list - -- Jay Dobies RHCE# 805008743336126 Freenode: jdob http://pulpproject.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNQHRaAAoJEOMmcTqOSQHCGHMH/R5ZBtlJtRjKRCRHOvgbzsj+ 9awzGD3WlK5+S4sl/62Pyc13K6l5NNofekeS1cpXH7u+bDQa7keb5LVITqKmcyvX SLC+ObFpt8lZg2hVKj7AmXAh0DrAy/7hKx3wc1WWcTd80kpcl21Uqpeo7jc+WpAI rgu8W8nFxCdPGacn+0DWeLoOawOJF9e+PTBocYkaM7tPhumsZgbojJG5MMn3FRGu qBcEWdWOIiOFzsv7anAVWd9Pgq3WovgZ9JZuf+gS2+y4lDOCQI+aaA3ARZJj23pT HkgnBImD0XS1LUZaVGy5DoDKqAKa989NSpj6VrDO8DE24pACwetXe3HwT58MBVc= =2aJZ -----END PGP SIGNATURE----- _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
