I have the following packages on my ks profile.
@Base
rhn-setup
osad
rhncfg
rhncfg-actions
rhncfg-client
wget
perl
with spacewalk-client and epel as child channels to solve the deps.
Hth,
Lupin
On Wed, Nov 13, 2013 at 12:19 AM, Net Warrior wrote:
> That's what I did, still getting the same
hello every one
I know I can create a virtual machine in spacewalk fairly easily in
Ovrt but what I would like to do is create an initial image for RDO
(OpenStack).
I've been thinking of a few possible ways like using the p2v tool on
an machine which was initially built by spacewalk then re-regist
On 12/11/13 11:51, Justin Edmands wrote:
On Tue, Nov 12, 2013 at 11:29 AM, Cliff Perry mailto:cpe...@redhat.com>> wrote:
Hi Spacewalk community,
today, a Critical security issue was announced within the Spacewalk
code base.
This is covered by CVE:
https://access.redhat.com/
- Original Message -
> I was about to take mine offline and update. The link no longer works. Is
> this not a CVE?
It is most certainly a CVE - what does "no longer works" look like to you?
What link are you trying, and what are the results you're getting from your
spacewalk install?
On Tue, Nov 12, 2013 at 11:29 AM, Cliff Perry wrote:
> Hi Spacewalk community,
> today, a Critical security issue was announced within the Spacewalk code
> base.
>
> This is covered by CVE:
>
> https://access.redhat.com/security/cve/CVE-2013-4480
>
> We have just committed into the Spacewalk git
Hi Spacewalk community,
today, a Critical security issue was announced within the Spacewalk code
base.
This is covered by CVE:
https://access.redhat.com/security/cve/CVE-2013-4480
We have just committed into the Spacewalk git repo the fixes and
building packages for Spacewalk 2.0 and 1.9. Th
hello
I've increased the log level on the proxy server (in rhn.conf -> debug =
9) and the /var/log/rhn/rhn_proxy_broker.log file includes more but I
didn't find the answer.
Could it be the problem when I've run the /usr/sbin/configure-proxy.sh
script and it's asked the ssl-build directory, t
try clearing jabbers database
service jabberd stop
rm -f /var/lib/jabberd/db/*
service jabberd start
Its a shot in the dark but usually when jabberd has a problem its
because the database is has been trashed. keep in mind there is
nothing in the database thats really is needed by spacewalk so its
hello
Silly idea but, SELinux or rights?
On 12/11/13 13:26, Sebastian Trebitz wrote:
Hello,
I used strace on the jabber/c2s process and this is what is suspect to me:
stat("/var/lib/jabberd/db/authreg.db", {st_mode=S_IFREG|0640,
st_size=172032, ...}) = 0
open("/var/lib/jabberd/db/authreg.db
On Di, 2013-11-12 at 14:32 +0100, David Hrbáč wrote:
> Dne 12.11.2013 13:53, Sebastian Trebitz napsal(a):
>
> >
> > Hello,
> >
> > Since a few days (after upgrading spacewalk and the separate pgsql
> > server with CentOS patches + reboot) the jabber daemon on the
> > spacewalk server does not wo
hello
I've set up the proxy server
(https://fedorahosted.org/spacewalk/wiki/HowToInstallProxy). The proxy
can install from Spacewalk central/parent server's repo (with yum
install PackageName) but the clients which were registered via proxy
can't be updated itself by 'yum update' command and
On 11/11/13 12:23, Balint Szigeti wrote:
hello
I've tried to set up the MonitoringScout on a spacewalk proxy server
but I've got this error:
/'STEP MonitoringScout EXECUTION FAILED: Can't open config file
'/usr/share/rhn/config-defaults/rhn_web.conf'/
I've found this bugzilla entry:
https:/
Dne 12.11.2013 13:53, Sebastian Trebitz napsal(a):
> Hello,
>
> Since a few days (after upgrading spacewalk and the separate pgsql
> server with CentOS patches + reboot) the jabber daemon on the
> spacewalk server does not work anymore.
>
> I get a lot of these messages in the system log:
> jabberd
Hello,
I used strace on the jabber/c2s process and this is what is suspect to
me:
stat("/var/lib/jabberd/db/authreg.db", {st_mode=S_IFREG|0640,
st_size=172032, ...}) = 0
open("/var/lib/jabberd/db/authreg.db", O_RDWR|O_CREAT, 0) = 239
fcntl(239, F_GETFD) = 0
fcntl(239, F_SETFD,
Hello,
Since a few days (after upgrading spacewalk and the separate pgsql
server with CentOS patches + reboot) the jabber daemon on the spacewalk
server does not work anymore.
I get a lot of these messages in the system log:
jabberd/c2s[4569]: db: couldn't open db for realm '': Cannot allocate
me
That's what I did, still getting the same error.
In the profile, under operating system I check the spacewalk repository
only which is a child channel of the main Centos-x64 channel, left
unchecked the other child channels, to the profile there is also
associated the activation key which has t
samuel_su...@mcafee.com wrote:
% Hi all,
%
% In one of my channels I have the EPEL "erlang" RPMs. If I do a
"channel.software.listLatestPackages" call those RPMs are not listed.
%
% I suspect it's got something to do with the way the erlang RPMs are
versioned. Below a dump of what "package.getD
17 matches
Mail list logo
