Dear Chris,
This server is configured via proxy server inorder to access internet
[root@pocserver ~]# more /etc/profile.d/rhn_proxy.sh
export http_proxy=http://xsRHNsatellite:username@proxyserver:8080/
export https_proxy=http://xsRHNsatellite:username@proxyserver:8080/
export HTTP_PROXY=http:
Hi,
I've just performed an in-place upgrade from mongodb 2.6.8 to 3.0.0 for
pulp 2.6.0-0.9.rc. Everything went seamlessly.
If you elect to move from the original mmapv1 backend to the new
wiredtiger backend, you will need to do a mongodump/mongorestore dance -
but that too should be straigh
An updated Pulp 2.6.0 RC is available at
https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.6/. Happy testing!
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
Dear Sandro,
Thanks for your assistance.
with the following steps, now the sync is started working.
# pulp-admin rpm repo update --repod-id rhel-6 --proxy-host
http://proxyserver --proxy-port 8080 --proxy-user username --proxy-pass
yourpassword
# pulp-admin rpm repo sync run --repo-id rhel-6
On 03/19/2015 04:42 PM, Vijayabalan Balakrishnan wrote:
> Dear Sandro,
>
> Thanks for your assistance.
>
> with the following steps, now the sync is started working.
>
> # pulp-admin rpm repo update --repod-id rhel-6 --proxy-host
> http://proxyserver --proxy-port 8080 --proxy-user username --p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Heyo!
I think we have a task to formally document this, but in the meantime
I wanted to send out a quick note about a Redmine feature I've noticed
that we're missing out on so far, that I think is pretty neat.
There are three special keywords you c
Hi all,
I've filled up the filesystem in /var/lib/pulp. I can't find any
instructions on how to recover from this situation. I tried just deleting
all the RPMs that I had downloaded but there's evidently some corruption
relating to the filesystem filling.
I just see this
# pulp-admin -u admin
OK - I got past this by deleting the RPMs and then restarting all the
services. Still, it would be good to know how to recover from a full
filesystem in general, without deleting RPMs and then deleting a repository.
On 20 March 2015 at 12:03, Alex Harvey wrote:
> Hi all,
>
> I've filled up the
Alex,
I'm glad you were able to get things back up and running. So would you
summarize your path to success as 1) free up some space, 2) restart services,
and then everything was fine? Did you have to do anything with mongodb?
FWIW, my favorite way to quickly free up space and inodes is "yum cl
Alan,
Thanks for the feedback! It's great to have help testing that sort of thing.
Michael
- Original Message -
From: "Alan Milligan"
To: pulp-list@redhat.com
Sent: Thursday, March 19, 2015 9:43:54 AM
Subject: [Pulp-list] MongoDB 3.x support
Hi,
I've just performed an in-place upgrade
10 matches
Mail list logo