I found the bug on RedHat's site that said this was due to an update in the
initscripts* package. Apparently it's just cosmetic, and all the services
start and run as expected.
See Ya'
Howard
John 3:16!
-Original Message-
From: spacewalk-list-boun...@redhat.com
Sorry, meant to include the link to the Bugzilla page:
https://bugzilla.redhat.com/show_bug.cgi?id=1153677
See Ya'
Howard
John 3:16!
-Original Message-
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Andy Ingham
Sent: Thursday,
I just recently installed Spacewalk on a CentOS 6.6 server. I created a
6.5 channel and repository and I just stood up a CentOS 6.5 client server
and registered it on to the Spacewalk server.
When I initially stood up the 6.5 client, I looked to see how many how many
updated packages it needed
Did you setup a 6.5 updates channel and repo, or just the base? When showing
updates, Spacewalk is showing you what packages updates it has available for
the client, which won’t be the same as a ‘yum list updates’ if you have
external repos defined directly on the client.
-- kevin
On Nov
Daryl Rose wrote:
% I just recently installed Spacewalk on a CentOS 6.6 server. I created a
% 6.5 channel and repository and I just stood up a CentOS 6.5 client server
% and registered it on to the Spacewalk server.
%
% When I initially stood up the 6.5 client, I looked to see how many how many
Daryl, good afternoon
Have you checked your log files looking for some error ?! When you create
your environment, you create a repo, after a base channel, after ?!
Have you registered the servers directly to your base channel or before did
a cloned channel and them register the server to the
Kevin,
Oh, so I have to add an update channel as well. Okay. This is my first
look at Spacewalk and just added the one channel.
I'll add in an update channel and see how that works.
Thank you for the feedback Kevin
Daryl
On Thu, Nov 6, 2014 at 9:39 AM, Kevin Sandy ke...@digitallotus.com
@daryl
did you use relative path for specifically centos 6.5 like:
/mirrors/CentOS/6.5
or you use generic 6 version? like:
/mirrors/CentOS/6
both for base and updates, because centos repos when release new minor
release will empty updates directory on the last one
best
Michael,
I'm not sure that I understand your response. The client is CentOS 6.5,
not 6.6. Yes, the Spacewalk server is 6.6, but the client is 6.5. I
purposefully chose 6.5 because its an older release and I know there are a
number of packages that would be out of date.
Thank you
Daryl
On
Amedeo,
For the 6.5 base I used the URL path:
http://mirror.centos.org/centos-6/6.5/os/x86_64/
I am in the process of adding an update channel, and I am using URL:
http://mirror.centos.org/centos-6/6.5/updates/x86_64/
Are these not correct? Should I use only
Daryl
I sent a email to list last month about it (
https://www.redhat.com/archives/spacewalk-list/2014-October/msg00222.html),
take a look, the idea is the same.
Tell me if is ok to you, about understanding, case not, I can create a post
about it in my blog.
B'Regards
__
if you use the frozen 6.5 you wont get any more updates, unless you
reay need to pointing to the symlink ones better. Also rather than
using the web interface in future you can use
/usr/bin/spacewalk-common-channels -v -u admin -p pass -a x86_64 -k
unlimited 'centos7*' 'spacewalk-client*'
Waldirio,
Thank you for the information, but I'm still a bit confused on how to
configure the channel and repositories.
If I read your post correctly, I should create a CentOS 6.5 channel with a
CentOS 6.5
Base repository with a 6.5 update child repository? Is that correct?
Thank you.
Daryl
Ever since updating from CentOS 6.5 6.6, my servers (which are all at
spacewalk client version 2.1) are showing:
+
SELinux is preventing /usr/bin/python from name_connect access on the
tcp_socket .
* Plugin catchall (100. confidence) suggests
I’ve been seeing this as well. Clients are on CentOS 6.6 with Spacewalk 2.2.
I’ve had to put SELinux in permissive mode for now.
-- kevin
On Nov 6, 2014, at 12:48 PM, Andy Ingham andy.ing...@duke.edu wrote:
Ever since updating from CentOS 6.5 6.6, my servers (which are all at
spacewalk
Daryl
You can do like this
Repo
repo: repo_centos6.5
url: http://mirror.globo.com/centos/6.5/os/x86_64/
Channel
base channel: centos6.5_x86-64_base
After this you will create a child channel
Repo
repo: repo_centos6.5_update
url:
Waldirio,
I believe that is how I now have this setup.
I have a CentOS 6.5 Channel setup and under it, I have two repositories
setup, 6.5 Base and 6.5 update.
Now that I have the update repository setup, the client that I'm setting up
now show's that there are 128 packages that need to be
Enjoy!
;-)
__
Atenciosamente
Waldirio
msn: waldi...@gmail.com
Skype: waldirio
Site: www.waldirio.com.br
Blog: blog.waldirio.com.br
LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646
PGP: www.waldirio.com.br/public.html
On Thu, Nov 6, 2014 at 5:33 PM, Daryl Rose
Hello
Sure, you can do that using spacewalk-clone-by-date, although if you know
this command, probably you use RHN Satellite and there is like this (all
minor releases in just one base channel), and the clone-by-date is to do
what you have (different's minor releases), so you can do by different
Okay, now that I have a system setup and registered, I'm trying to do an
update.
I picked one package and selected it to update. The package is queued, but
the update has not run.
In a past life, I've used Satellite Server to update Red Hat servers. I
used the rhn_check command to force the
Daryl
Answers bellow
__
Atenciosamente
Waldirio
msn: waldi...@gmail.com
Skype: waldirio
Site: www.waldirio.com.br
Blog: blog.waldirio.com.br
LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646
PGP: www.waldirio.com.br/public.html
On Thu, Nov 6, 2014 at 6:55 PM, Daryl
Waldirio,
Yes, the client is registered with SW. Here is the output from yum
repolist:
[root@daryl-centos65-demo01 ~]# yum repolist
Loaded plugins: fastestmirror, rhnplugin, security
This system is receiving updates from RHN Classic or Red Hat Satellite.
Loading mirror speeds from cached
Humm
The sync of your channel had concluded ??
If not, this is the prob.
You can see in your server in /var/log/rhn/* files.
B'regards
Em 06/11/2014 19:55, Daryl Rose rosed...@gmail.com escreveu:
Waldirio,
Yes, the client is registered with SW. Here is the output from yum
repolist:
Daryl Rose wrote:
% Okay, now that I have a system setup and registered, I'm trying to do an
% update.
%
% I picked one package and selected it to update. The package is queued, but
% the update has not run.
%
% In a past life, I've used Satellite Server to update Red Hat servers. I
% used the
I got the latest spacewalk 2.2 installed. It was working fine. I can register a
rhel6 client to oraclelinux6-x86_64 channel and did yum update without issue.
Then one day i found out yum update is broken.
this is message I see when I try to yum check-update:
[root@yangli-test ~]# yum
25 matches
Mail list logo
