subject:"\[Pulp\-list\] pulp mongodb upgrade"

Re: [Pulp-list] pulp mongodb upgrade

2021-06-07 Thread Brian Bouterse

Hi Venkataramana,

Thanks for the logs. In there, I only see one error, but I see it a huge
number of times:   ServerSelectionTimeoutError: localhost:27017: [Errno
111] Connection refusedTo me that means environmentally celery and/or
the WSGI environments cannot connect to your mongod. Unfortunately, I don't
have more info than that.

All the best,
Brian


On Fri, Jun 4, 2021 at 2:29 PM Venkataramana Bora 
wrote:

> Hi Brian, here have attached "pulp:"  logs from /var/log/messages .Sorry
> for attaching bit lengthy text files.
> Other than those, I did not find  any other pulp logs . Thank you !
>
>
>
> Sincerely,
> Ramana Bora
>
>
>
> - Original message -
> From: Brian Bouterse 
> To: Venkataramana Bora 
> Cc: pulp-list , Donal Keane 
> Subject: [EXTERNAL] Re: [Pulp-list] pulp mongodb upgrade
> Date: Wed, Jun 2, 2021 9:29 PM
>
> Hi Venkataramana and Donal, I looked at the logs, but unfortunately I
> don't see any exceptions related to Pulp's use of Mongo. Mostly I just see
> a mongodb error:  `FileRenameFailed Renaming file
> /var/log/mongodb/mongodb.log to
> /var/log/mongodb/mongodb.log.2021-05-27T07-33-08 ZjQcmQRYFpfptBannerStart
> This Message Is From an External Sender
> This message came from outside your organization.
> ZjQcmQRYFpfptBannerEnd
> Hi Venkataramana and Donal,
>
> I looked at the logs, but unfortunately I don't see any exceptions related
> to Pulp's use of Mongo. Mostly I just see a mongodb error:
> `FileRenameFailed Renaming file /var/log/mongodb/mongodb.log to
> /var/log/mongodb/mongodb.log.2021-05-27T07-33-08 failed; Cannot verify
> whether destination already exists`.
>
> I believe the pulp logs themselves would be needed.
>
> -Brian
>
>
> On Fri, May 28, 2021 at 12:18 PM Venkataramana Bora 
> wrote:
>
>
> 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: [email protected]
> Cc: [email protected], 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 
> To: Venkataramana Bora 
> Cc: pulp-list , Donal Keane 
> 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 
> 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
&g

Re: [Pulp-list] pulp mongodb upgrade

2021-06-02 Thread Brian Bouterse

Hi Venkataramana and Donal,

I looked at the logs, but unfortunately I don't see any exceptions related
to Pulp's use of Mongo. Mostly I just see a mongodb error:
`FileRenameFailed Renaming file /var/log/mongodb/mongodb.log to
/var/log/mongodb/mongodb.log.2021-05-27T07-33-08 failed; Cannot verify
whether destination already exists`.

I believe the pulp logs themselves would be needed.

-Brian


On Fri, May 28, 2021 at 12:18 PM Venkataramana Bora 
wrote:

>
> 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: [email protected]
> Cc: [email protected], 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 
> To: Venkataramana Bora 
> Cc: pulp-list , Donal Keane 
> 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 
> 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 cas

Re: [Pulp-list] pulp mongodb upgrade

2021-05-28 Thread Venkataramana Bora

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/IBMTo: [email protected]: [email protected], Venkataramana Bora/India/IBM@IBMSubject: Re: [EXTERNAL] Re: [Pulp-list] pulp mongodb upgradeDate: 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 To: Venkataramana Bora Cc: pulp-list , Donal Keane Subject: [EXTERNAL] Re: [Pulp-list] pulp mongodb upgradeDate: 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 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 latestversion. If this is the case, run pulp-manage-db and restart the services. Moreinformation 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 latestversion. If this is the case, run pulp-manage-db and restart the services. Moreinformation 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: virtualboxDisplay Name: virtualboxDescription: virtualboxContent Unit Counts: Rpm: 107
.
Sincerely,Venkataramana Bora
IBM - TMS cloud operations
Plot #1, Hill # 3, Apiic & Ites Sez, Rishikonda, MadhuravadaVisakhapatnam, AP 530045, India.___Pulp-list mailing [email protected]://listman.redha

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 
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
> [email protected]
> https://listman.redhat.com/mailman/listinfo/pulp-list
___
Pulp-list mailing list
[email protected]
https://listman.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] pulp mongodb upgrade

2021-05-27 Thread Venkataramana Bora

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 latestversion. If this is the case, run pulp-manage-db and restart the services. Moreinformation 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 latestversion. If this is the case, run pulp-manage-db and restart the services. Moreinformation 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: virtualboxDisplay Name: virtualboxDescription: virtualboxContent Unit Counts: Rpm: 107
.
Sincerely,Venkataramana Bora
IBM - TMS cloud operations
Plot #1, Hill # 3, Apiic & Ites Sez, Rishikonda, MadhuravadaVisakhapatnam, AP 530045, India.

___
Pulp-list mailing list
[email protected]
https://listman.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] pulp mongodb upgrade

Re: [Pulp-list] pulp mongodb upgrade

Re: [Pulp-list] pulp mongodb upgrade

Re: [Pulp-list] pulp mongodb upgrade

Re: [Pulp-list] pulp mongodb upgrade

Re: [Pulp-list] pulp mongodb upgrade

Re: [Pulp-list] pulp mongodb upgrade

[Pulp-list] pulp mongodb upgrade

8 matches

Site Navigation

Mail list logo

Footer information