On 04/04/2018 05:09 AM, Michael Mraka wrote:
> Michael Watters:
>>> You can check the path with
>>>
>>> select * from rhnpackage where id = 11570;
>>>
>>> But the message indicates some sort of error while you were synchronizing
>>> your repos. I would try to locate this problem "package" within
On 03/29/2018 06:48 AM, Paschedag, Robert wrote:
> You can check the path with
>
> select * from rhnpackage where id = 11570;
>
> But the message indicates some sort of error while you were synchronizing
> your repos. I would try to locate this problem "package" within SW in the
> "Channels" ->
Hi!
I've created a channel, added a repository, then started to sync this
newly created channel. Worked so far, but: only 15 packages are
synced. The repository holds 125!
Now I have tried to download missing packages using
# /usr/bin/spacewalk-repo-sync -c ol6-i386-winswitch -t yum
15:24:28 ===
> Gesendet: Montag, 09. April 2018 um 15:17 Uhr
> Von: "Michael Watters"
> An: spacewalk-list@redhat.com
> Betreff: [Spacewalk-list] Cannot install updates on spacewalk client
>
>
> On 04/04/2018 05:09 AM, Michael Mraka wrote:
> > Michael Watters:
> >>> You can check the path with
> >>>
> >>>
Oh..just saw, that the spacewalk-data-fsck tool does not clean the DB.
Hmm...
> Gesendet: Montag, 09. April 2018 um 15:26 Uhr
> Von: "Michael Watters"
> An: spacewalk-list@redhat.com
> Betreff: Re: [Spacewalk-list] Cannot install updates on spacewalk client
>
>
> On 03/29/2018 06:48 AM, Pasch
Please go to
Channels -> manage software channels -> manage software packages
Select your channel with problematic packages
Can you find the packages in there?
If yes, remove the packages from the channel. If that works, go to the same view
and search for "packages in no channels". Your previou
Just as FYI --> To avoid running the spaceawalk-hostname-rename scripts in
the future and easily migrate from one server to another, you can use a
cname for all of the details.
IE You can have a standby server with spacewalk installed on. Then
all you have to do is flip the cname and so
Hello!
I'm currently have a problem with erratas deployments. While I'm trying to
deploy an errata I get the following error:
*Details:*
This action will be executed after 4/9/18 12:16:00 PM GMT
This action's status is: Failed.
The client picked up this action on 4/9/18 8:23 AM
The client comple