<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> Hi Dennis,<o:p></o:p> <o:p> </o:p> Thanks for the help. You got me over the hump. I feel more than a little silly...<o:p></o:p> <o:p> </o:p> systemctl -l status mongod.service showed that mongodb was not running.<o:p></o:p> Looking at /var/log/mongodb/mongod.log showed that it failed with insufficient space for journal files, and gave the path.<o:p></o:p> Increasing space on the /var fs and restarting things fixed it.<o:p></o:p> <o:p> </o:p> I will certainly try and be more vigilant next time in my troubleshooting. I can see this was pretty simple, and that I may have annoyed some. I don't know what my problem was (Is there a deer in the headlights syndrome?) but I was just stuck. Thanks again for your help, grace, and patience. <o:p></o:p> <o:p> </o:p> Don Wolfe<o:p></o:p> Office: (925) 948-2829<o:p></o:p> Mobile: (925) 239-5941<o:p></o:p> <o:p> </o:p> From: Dennis Kliban [mailto:dkliban@redhat.com] Sent: Friday, October 13, 2017 7:56 AM To: Donald Wolfe <dwolfe@central.com> Cc: pulp-list@redhat.com Subject: Re: [Pulp-list] Pulp issue -- RHEL cert related?<o:p></o:p> <o:p> </o:p> <div> It looks like mongodb is not running. Pulp can't operate without the database.<o:p></o:p> </div> <div> <o:p> </o:p> <div> On Thu, Oct 12, 2017 at 3:08 PM, Donald Wolfe <<a href="mailto:dwolfe@central.com" target="_blank">dwolfe@central.com</a>> wrote:<o:p></o:p> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"> <div> <div> Hi all,<o:p></o:p> <o:p></o:p> Any help would be greatly appreciated.<o:p></o:p> <o:p></o:p> I had Pulp working fine with CentOS and RHEL 6 repositories, but ran into issues when installing RHEL 7 repos which, on the surface, would not seem to be related, but who's timing is suspect.<o:p></o:p> <o:p></o:p> I copied certs from our RHEL 7 system so pulp could log in and sync repos from RH network. I ran into an issue with the repo sync, and somewhere along the line when I ran: subscription-manager refresh on the rhel 7 client system, copied the new certs over to the pulp server, removed those they replaced, and now nothing works.<o:p></o:p> <o:p></o:p> root@sacpulp:/root # pulp-admin rpm repo list<o:p></o:p> +----------------------------------------------------------------------+<o:p></o:p> RPM Repositories<o:p></o:p> +----------------------------------------------------------------------+<o:p></o:p> <o:p></o:p> There was an internal server error while trying to access the Pulp application.<o:p></o:p> One possible cause is that the database needs to be migrated to the latest<o:p></o:p> version. If this is the case, run pulp-manage-db and restart the services. More<o:p></o:p> information may be found in Apache's log.<o:p></o:p> <o:p></o:p> root@sacpulp:/root # su - apache<o:p></o:p> Last login: Thu Oct 12 10:53:43 PDT 2017 on pts/1<o:p></o:p> $ pulp-manage-db<o:p></o:p> Attempting to connect to localhost:27017<o:p></o:p> Database initialization failed: localhost:27017: [Errno 111] Connection refused<o:p></o:p> Cannot connect to the database, please validate that the database is online and accessible.<o:p></o:p> <o:p></o:p> root@sacpulp:/root # pulp-admin status<o:p></o:p> +----------------------------------------------------------------------+<o:p></o:p> Status of the server<o:p></o:p> +----------------------------------------------------------------------+<o:p></o:p> <o:p></o:p> There was an internal server error while trying to access the Pulp application.<o:p></o:p> One possible cause is that the database needs to be migrated to the latest<o:p></o:p> version. If this is the case, run pulp-manage-db and restart the services. More<o:p></o:p> information may be found in Apache's log.<o:p></o:p> <o:p></o:p> Any help would be appreciated.<o:p></o:p> <o:p></o:p> Thank you, and best regards,<o:p></o:p> <o:p></o:p> Don<o:p></o:p> <o:p></o:p> Email: <a href="mailto:dwolfe@central.com" target="_blank">dwolfe@central.com</a><o:p></o:p> Office: <a href="tel:(925)%20948-2829" target="_blank">(925) 948-2829</a><o:p></o:p> <o:p></o:p> </div> Disclaimer: This communication and any attachments contain private, confidential, privileged and/or proprietary information intended solely for the Recipient(s) named above. If you are not the intended Recipient, any use, dissemination, distribution or copying of the communication is strictly prohibited. If received in error, we apologize and ask that you please notify the Sender by returning this e-mail and permanently deleting this communication from your computer, including destruction of any printed copies. Any views expressed herein are not necessarily those of the Company represented by this e-mail source. No contracts, agreements or legally binding understandings may be entered into solely by an e-mail communication. <o:p></o:p> </div> _______________________________________________ Pulp-list mailing list <a href="mailto:Pulp-list@redhat.com">Pulp-list@redhat.com</a> <a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.redhat.com%2Fmailman%2Flistinfo%2Fpulp-list&data=01%7C01%7Cdwolfe%40central.com%7C40ce88ec7e99488b62ec08d5124a9268%7Ce74cdc7911bd414daebbee7befc02409%7C1&sdata=85qpQqROK59AgnOuMaczxbzFy7aRa14rtOs1U7BNIQs%3D&reserved=0" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-list</a><o:p></o:p> </blockquote> </div> <o:p> </o:p> </div> </div> Disclaimer: This communication and any attachments contain private, confidential, privileged and/or proprietary information intended solely for the Recipient(s) named above. If you are not the intended Recipient, any use, dissemination, distribution or copying of the communication is strictly prohibited. If received in error, we apologize and ask that you please notify the Sender by returning this e-mail and permanently deleting this communication from your computer, including destruction of any printed copies. Any views expressed herein are not necessarily those of the Company represented by this e-mail source. No contracts, agreements or legally binding understandings may be entered into solely by an e-mail communication. </body> </html>