Re: [Pulp-list] pulp mongodb upgrade

Fri, 28 May 2021 08:34:05 -0700

 
Hi Brian,
 
Please find attached  MongoDB logs from /var/log/mongodb/. There are no logs in /var/log/pulp. Please let us know if any other logs required . Thanks a lot for your reply!


Sincerely,
Ramana Bora
 
 
----- Original message -----
From: Donal Keane/Ireland/IBM
To: bmbou...@redhat.com
Cc: pulp-list@redhat.com, Venkataramana Bora/India/IBM@IBM
Subject: Re: [EXTERNAL] Re: [Pulp-list] pulp mongodb upgrade
Date: Fri, May 28, 2021 2:19 AM
 
Hi Brian,
 
Thank you kindly for your response.
 
The plan here originally was to move to Pulp 3 - and definitely still is. However, our brand within IBM has recently been sold off and it is happening sooner rather than later. As part of this acquisition we are losing a good proportion of expertise around our Linux operating systems. We have been tasked as a high priority to make sure all of our open source tools are patched to the latest security level before the acquisition goes through. This is why Ramana is attempting to get us to 2.21.x asap and from there, concentrate on getting to 3 when time and resources allow. I hope this explains our current situation and why any help would be graciously accepted!
 
Ramana can you post relevant log info when you get a chance tomorrow?
 
Thanks,
 
Donal
 
----- Original message -----
From: Brian Bouterse <bmbou...@redhat.com>
To: Venkataramana Bora <venkb...@in.ibm.com>
Cc: pulp-list <pulp-list@redhat.com>, Donal Keane <donal.ke...@ie.ibm.com>
Subject: [EXTERNAL] Re: [Pulp-list] pulp mongodb upgrade
Date: Thu, May 27, 2021 8:12 PM
 
I don't have ready advice, but it might be helpful to post a snippet of the logs. Without that, all we know is there is a 500 server error, not what the cause could be. Have you considered migrating to Pulp3? Pulp2 is in maintenance mode, ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
I don't have ready advice, but it might be helpful to post a snippet of the logs. Without that, all we know is there is a 500 server error, not what the cause could be.
 
Have you considered migrating to Pulp3? Pulp2 is in maintenance mode, and likely has had its terminal release. Pulp3 is at 3.13 and has been out since Dec 2019. Here's more information on how to upgrade https://pulpproject.org/migrate-to-pulp-3/  We would be very interested in helping you do that.
 
On Thu, May 27, 2021 at 12:03 PM Venkataramana Bora <venkb...@in.ibm.com> wrote:
 
Hi team,
We are using pulp-server-2.21.5-1.el7 with mongodb-server-2.6.12-6.el7.x86_64 , this version of mongodb 2.6.12-16 got installed from our config manage server puppet .
Time and again pulp-admin commands run, throwing below errors , I think it is due to old version of mongodb. After running /var/lib/mongodb --repair able to access pulp-admin commands for some time/few days as shown here below.
Some one kindly help us on how to upgrade mongodb-server-2.6.12-6 to higher mongodb version that is compatible with pulp-server-2.21.5-1 ? This specific pulp-server we are using instead of higher versions due to some internal dependencies. Thanks a lot in advance.
 
[root@drtp1opsndbx04 ~]# pulp-admin tasks list
+----------------------------------------------------------------------+
                                 Tasks
+----------------------------------------------------------------------+
There was an internal server error while trying to access the Pulp application.
One possible cause is that the database needs to be migrated to the latest
version. If this is the case, run pulp-manage-db and restart the services. More
information may be found in Apache's log.
root@drtp1opsndbx04 ~]# pulp-admin repo list
+----------------------------------------------------------------------+
                              Repositories
+----------------------------------------------------------------------+
There was an internal server error while trying to access the Pulp application.
One possible cause is that the database needs to be migrated to the latest
version. If this is the case, run pulp-manage-db and restart the services. More
information may be found in Apache's log.
 
After running /var/lib/mongodb --repair working a little while:
 
[root@drtp1opsndbx04 ~]# pulp-admin tasks list
+----------------------------------------------------------------------+
                                 Tasks
+----------------------------------------------------------------------+
No tasks found

[root@drtp1opsndbx04 ~]# pulp-admin repo list
+----------------------------------------------------------------------+
                              Repositories
+----------------------------------------------------------------------+
Id:                  virtualbox
Display Name:        virtualbox
Description:         virtualbox
Content Unit Counts:
  Rpm: 107
.....
 
 
 

Sincerely,
Venkataramana Bora
IBM - TMS cloud operations
Plot #1, Hill # 3, Apiic & Ites Sez, Rishikonda, Madhuravada
Visakhapatnam, AP  530045, India.

_______________________________________________
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list
 
 

Attachment: mongodb.log
Description: Binary data

Attachment: mongodb.log-20210527
Description: Binary data

Attachment: mongodb.log-20210425
Description: Binary data

Attachment: mongodb.log-20210418
Description: Binary data

_______________________________________________
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list

Reply via email to