You get SLES 11 updates from Novell. SLES12 from SuSE.
Regards
Robert
Am 08.08.2016 17:58 schrieb Bernd Helber :
>
> Dear Jinesh,
>
> there are no URLS, like we had it in the Past.
> You have to register a System at
>
> SuSE Customer Center, select all Repo's you're in need of.
>
> SuSE Custom
Strip the /rpm/x86_64 from the URL. Should run then.
Regards
Robert
Am 08.08.2016 19:01 schrieb jineesh.kot...@accenture.com:
>
> Hi Daryl,
>
>
>
> I have created the channel with the URL retrieved from the yast with username
> and password. The syncing is failing with below message in logs,
>
Hi Avi
I am not combining any channels in fact in another email thread, i have shared
the screens for the Space-Walk repo and Oracle repo. both are not matching. If
the channel has 11942 packages it's really great to hear and it's almost 70%
lesser than from what we have currently with our spac
Thank you very much Avi
Of course, I will wait for your reply.
Best RegardsMalla
On Tuesday, August 9, 2016 4:06 AM, Avi Miller
wrote:
On 8 Aug 2016, at 4:24 PM, Malla Reddy Madupu wrote:
I just wanted to confirm with you all. I can see the difference in the file
size where I have
I exported my spacewalk data with spacewalk-export
Just curious how to import all exported data to another server with the
same version of sp.
Thanks
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/space
Hi,
> On 8 Aug 2016, at 2:30 PM, Malla Reddy Madupu wrote:
>
> Actually this is a Oracle Enterprise Linux O/S not RHEL and the total number
> of packages are in this repository are 38916
> here's the URL:
> "http://public-yum.oracle.com/repo/OracleLinux/OL5/latest/x86_64/repodata/";
Note that
> On 8 Aug 2016, at 4:24 PM, Malla Reddy Madupu wrote:
>
> I just wanted to confirm with you all. I can see the difference in the file
> size where I have created a repo in my Space-Walk server using the same URL
> which is
> "http://public-yum.oracle.com/repo/OracleLinux/OL5/latest/x86_64/re
Hi,
You need an active CSI and ULN access to synchronise the Base/Patch channels. I
don't recommend combining them into a single channel. Rather, you link a parent
OL5U11 channel to the ol5_u11_base channel on ULN and then create a child
ol5_u11_patch channel.
This is discussing in the Concept
Jineesh,
Try removing the following from your string.
rpm/x86_64/
Daryl
From: spacewalk-list-boun...@redhat.com on
behalf of jineesh.kot...@accenture.com
Sent: Monday, August 8, 2016 12:01 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] cha
Try deleting the "rpm/x86_64/" from your url. Make sure you are using your
mirror credentials.
Chris Will
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of
jineesh.kot...@accenture.com
Sent: Monday, August 08, 2016 1:02 PM
To: spacewalk-list@redh
Hi Daryl,
I have created the channel with the URL retrieved from the yast with username
and password. The syncing is failing with below message in logs,
Sync started: Mon Aug 8 17:44:44 2016
['/usr/bin/spacewalk-repo-sync', '--channel', 'suse11sp3channel', '--type',
'yum']
Repo URL:
https://u
I've fixed everything, works fine now, here's the steps
1. Increase max_connections=600 /var/lib/pgsql/data/postgresql.conf
2. Increase java memory heap 4-24Gb /etc/sysconfig/tomcat6
3. Increase ulimit /etc/security/limits.conf
* soft nproc 65535
* hard nproc 65535
* soft nofile 65535
* hard n
Dear Jinesh,
there are no URLS, like we had it in the Past.
You have to register a System at
SuSE Customer Center, select all Repo's you're in need of.
SuSE Customer Center will generate URLS you have to use.
At example
spacecmd {SSM:0}> repo_details sles12-sdk
Repository Label: sles12-sdk
The URL will be found in the "Configured Software Repositories" in YAST. Open
up YAST find "Software Repositories" under the "Software" section. (I
personally uses yast2, and pull the GUI back to my desktop using X windows.)
In YAST you'll see the URL string(s) for the various repositories. C
Are you sure it's postgres causing the issue? I run an oracle backend, but
ran into similar performance issues when attempting actions on a few
hundred systems at a time. I was able to get around this by tweaking some
of the tomcat connector settings.. This works pretty well supporting 8000+
hosts.
Hi Daryl,
Thanks for the details.
We have the License for SuSE servers. What I am requesting here is, what is the
URL and where I have to put the credentials while creating the channels for
SuSE in SW.
Thanks & Regards,
Jineesh K
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-lis
Jineesh,
This is correct. You have to have properly licensed servers to be able to
access the repositories.
The reason why I am using SW is because I have both RHEL and SLES servers in my
environment. I evaluated purchasing Red Hat Satellite server and SuSE Package
Management Server. Howev
Hi,
I wanted to find out which user deleted a specific system from our Spacewalk
server (v2.2), I ran the following report and as expected it showed the system
whoever it didn't show the user that performed the operation.
# spacewalk-report audit-servers | grep 111451
111704,2016-08-03
Hello,
You should register systems in SP server via proxy, after this, you will see
logs in (on proxy machines):
1) Apache logs (all API calls)
2) Squid (package caching)
3) jabberd (for osad connections)
Here you can find some short description:
https://fedorahosted.org/spacewalk/wiki/proxy,
a
19 matches
Mail list logo