Re: [Spacewalk-list] Spacewalk API CURL examples
Strahil, If you find yourself outgrowing spacecmd and want to explore the API, there is some great documentation and examples available right on your Spacewalk web portal. Login to it and to go "Help (black navigation bar) > API (left side menu)". Bill Howe howe.b...@gmail.com <http://www.linkedin.com/in/whowe> On Mon, Jun 3, 2019 at 4:06 AM Strahil Nikolov wrote: > On June 3, 2019 11:44:29 AM GMT+03:00, Michael Mraka < > michael.mr...@redhat.com> wrote: > >Strahil Nikolov: > >> Hello Community, > >> > >> I'm trying to find an examples for accessing the API via curl > >(xml/json) ,as I do not have experience with perl/python/rubi . > > > >Hello Strahil, > > > >Using curl for API is possible but creating XML responses is tedious. > >If you want to use API from command line try either spacewalk-api (from > >spacewalk-utils package) or spacecmd (from spacecmd package). > > > >> Can someone provide a link to examples via curl, as I want to play a > >little bit with my Uyuni system. > >> > >> Thanks in advance. > >> > >> Best Regards, > >> Strahil Nikolov > > > >Regards, > > > >-- > >Michael Mráka > >System Management Engineering, Red Hat > > > >___ > >Spacewalk-list mailing list > >Spacewalk-list@redhat.com > >https://www.redhat.com/mailman/listinfo/spacewalk-list > > Hi Michael, > > Thanks for the suggestions. > I have just tried 'spacecmd' and it suits my needs. > > Best Regards, > Strahil Nikolov > > ___ > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Errata...purpose?
Take a look at Steve's scripts and you can get the errata added to Spacewalk for all the CentOS repos. Excellent scripts, been using them to get errata into Spacewalk for years. Thanks Steve! Wish CentOS would just provide the errata in the repos like red hat, fedora, oracle. Bill Howe howe.b...@gmail.com On Fri, Jan 25, 2019, 02:54 Steve Meier wrote: > Hi Dave, > > Errata can be provided by any RPM/YUM repository. The Red Hat > repositories > have them, while CentOS does not. The popular EPEL repository also has > Errata (with IDs like FEDORA-EPEL...). > > When you use spacewalk-repo-sync, Spacewalk will import any Errata from > the repository automatically. > > I am not aware of any open-source project repositories providing Errata. > > Kind regards, >Steve > > Am 2019-01-25 00:50, schrieb Dave Thoms: > > Steve, > > > > Thank you so much for the overview. I'm surprised most people don't > > ask this question...or maybe they are just smarter than me. > > > > So errata is official which mean it only comes from Red Had? Or do > > others (python, etc.) release official errata? > > > > Dave T > > - > > > > FROM: spacewalk-list-boun...@redhat.com > > on behalf of Steve Meier > > > > SENT: Tuesday, January 22, 2019 1:47:18 PM > > TO: spacewalk-list@redhat.com > > SUBJECT: Re: [Spacewalk-list] Errata...purpose? > > ___ > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Antwort: FW: List of patched/to patched systems by commandline
The API has excellent documentation if you don't quite find what you are
looking for.
Bill Howe
howe.b...@gmail.com
On Mon, Feb 18, 2019, 09:41 Matthias Gruber wrote:
> Hi!
>
> Oh... thats sound good... I am back in that stuff tomorrow
> Thanks a lot
>
> Matthias
>
>
>
>
> METZLER
> Informationstechnologie
>
> Matthias Gruber
> IT-Infrastruktur & -Betrieb
>
> B. Metzler seel. Sohn & Co.
> Kommanditgesellschaft auf Aktien
> Untermainanlage 1
> 60329 Frankfurt am Main
> Telefon (0 69) 21 04 - 43 30
> Telefax (0 69) 21 04 - 40 40
> mgru...@metzler.com
> www.metzler.com
>
>
>
> Von:"p.cook...@bham.ac.uk"
> An:"spacewalk-list@redhat.com"
> Datum:18.02.2019 16:32
> Betreff:[Spacewalk-list] FW: List of patched/to patched systems
> by commandline
> Gesendet von:spacewalk-list-boun...@redhat.com
> --
>
>
>
> Hi Matthias
>
> I’ve come across a “spacecmd” report called “report_outofdatesystems”
> which may be of interest to you as it produces a very simple list of
> systems with the number of outstanding patches?
>
> spacecmd {SSM:0}> *report_outofdatesystems*
> System Packages
> --
> server 19
> server 22
> server 3590
> server 4592
> spacecmd {SSM:0}>
>
> Regards
> Phil
>
> *From:* Philip Cookson (IT Services)
> * Sent:* 12 February 2019 15:27
> * To:* 'spacewalk-list@redhat.com'
> * Subject:* RE: [Spacewalk-list] List of patched/to patched systems by
> commandline
>
> Hi Matthias
>
> Have you looked at the standard Spacewalk reports or “spacecmd” command at
> all?
>
> The “*spacewalk-report*” tool outputs information in a CSV format.
>
> The related package needs to be installed from the Spacewalk repository:
>
> # *yum -y install spacewalk-reports*
>
> The man page for spacewalk-report is in the usual format and there is also
> an option "--list-fields-info" that is helpful:
>
> # *spacewalk-report --list-fields*
>
> See report descriptions below – the “*system-currency*” report might be
> useful for what you’re after?
> · channel-packages - Packages in channels
> · channels - Channel report
> · custom-info - Display system custom info
> · entitlements - Entitlement and channel list and usage
> · errata-channels - List of errata in channels
> · errata-list - Errata information based upon compliance checks
> against systems
> · errata-list-all - List of all erratas
> · errata-systems - Listing of each errata applicable to each
> affected system
> · inactive-systems - Inactive systems in Satellite
> · inventory - Inventory report
> · kickstartable-trees - List of kickstartable trees
> · packages-updates-all - List of packages that can be upgraded
> · packages-updates-newest - List of packages that can be upgraded
> · scap-scan - Results of OpenSCAP xccdf evaluation
> · scap-scan-results - Results of OpenSCAP xccdf evaluation
> · system-crash-count - Crash count for systems
> · system-crash-details - Crash details for systems
> · *system-currency - System currency list *
> · system-groups - System groups in Satellite
> · system-groups-keys - Activation keys for system groups
> · system-groups-systems - Systems in system groups
> · system-groups-users - System groups users report
> · system-history - System event history
> · system-history-channels - Channel event history
> · system-history-configuration - Configuration event history
> · system-history-entitlements - System entitlement event history
> · system-history-errata - Errata event history
> · system-history-kickstart - Kickstart event history
> · system-history-packages - Package event history
> · system-history-scap - OpenSCAP event history
> · system-packages-installed - Packages installed on systems
> · users - Users in the system
> · users-systems - Systems administered by individual users
>
> The output could be piped through awk to get just the columns of info
> you’re interested in perhaps - see example command below:
>
> # *spacewalk-report inventory | awk -F"," '{print $4, $3,
> $8}' > inventor
Re: [Spacewalk-list] registering servers to specific repositories
You could use activation keys that map to certain base/child channels. Then just run a registration script on the system (shameless plug example: https://gitlab.com/whowe/spacewalk/blob/master/spacewalk-register.sh) You may also be able to use distribution channel mappings, but I haven't used those, so can't speak much on that. Good luck. Bill Howe howe.b...@gmail.com On Tue, Feb 26, 2019, 13:42 oogiej...@yahoo.com wrote: > We are trying to figure out how to automate registering our servers with > specific repositories. Currently, we kickstart new servers and have them > register to spacewalk using a universal activation key that has no channels > associated with it. We did this so that when we create new frozen channels > every month we can just associate the servers with that specific channel - > for instance all our rhel7 servers were just patched with our Feb1_2019 set > of channels, and next week they will all be patched with March1_2019 > channels. Would it be possible to automate attaching channels to a server > using spacecmd? > ___ > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] How to create local repo on Spacewalk
>From what I understand, you are trying to create a custom local repo and make it available in Spacewalk. To do that: - Follow the normal createrepo procedures - Populate your repo with the packages, sign them with a GPG key (rpmsign) - In the Spacewalk portal, go to: Channels > Manage Software Channels > Manage Software Reposotories - Click "Create Repository" and define it similar to the following: - Label: - URL: file:///var/repos/custom/el7/x86_64 - Type: yum - Create a new channel and link it to your newly created repo. - All clients will need the GPG key imported into rpm (rpm --import GPGKEYFILE) Bill Howe howe.b...@gmail.com <http://www.linkedin.com/in/whowe> On Thu, Sep 27, 2018 at 10:27 AM Jérôme Meyer wrote: > Thanks for your reply. > > I don’t have a local repo or how can I find it? > > > > Regards, > > Jérôme > > > > *From:* spacewalk-list-boun...@redhat.com [mailto: > spacewalk-list-boun...@redhat.com] * On Behalf Of *Harshal Lakare > *Sent:* Donnerstag, 27. September 2018 16:17 > *To:* spacewalk-list@redhat.com > *Subject:* [Spacewalk-list] How to create local repo on Spacewalk > > > > You can simple run script to add your local repo in kickstart file. > > > > > Regards, > > > > Harshal Lakare > ___ > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] rhn_check
Check to see if your rhnplugin is enabled here:
/etc/yum/pluginconf.d/rhnplugin.conf
[main]
enabled = 1
Bill Howe
howe.b...@gmail.com <http://www.linkedin.com/in/whowe>
On Wed, Oct 24, 2018 at 1:11 PM Irwin, Jeffrey <
jeffrey.ir...@rivertechllc.com> wrote:
> I think I got it...or at least got rid of that error. Are the
> highlighted lines of concern? Should I enable those and how?
>
>
> I deleted the system from the gui
>
> I deleted the systemid file from /etc/sysconfig/rhn/
>
> Edited the /etc/sysconfig/up2date file
>
> -changed serverURL=https://spacewalk.example.com/XMLRPC from the default
>
> -changed sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
> from sslCACert=/usr/share/rhn/RHNS-CA-CERT
>
> Ran rhn_register using spacewalk username/password
>
>
> Now output of rhn_check is
> rhn_check -v -v -v
> D: opening db environment /var/lib/rpm cdb:mpool:joinenv
> D: opening db index /var/lib/rpm/Packages rdonly mode=0x0
> D: locked db index /var/lib/rpm/Packages
> D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/*.key
> D: couldn't find any keys in /var/lib/rpm/pubkeys/*.key
> D: loading keyring from rpmdb
> D: opening db index /var/lib/rpm/Name rdonly mode=0x0
> D: added key gpg-pubkey-fd431d51-4ae0493b to keyring
> D: added key gpg-pubkey-2fa658e0-45700c69 to keyring
> D: added key gpg-pubkey-2cefacb7-53da50b4 to keyring
> D: Using legacy gpg-pubkey(s) from rpmdb
> D: opening db index /var/lib/rpm/Providename rdonly mode=0x0
> D: do_call packages.checkNeedUpdate('rhnsd=1',){}
> D: opening db environment /var/lib/rpm cdb:mpool:joinenv
> D: opening db index /var/lib/rpm/Packages rdonly mode=0x0
> D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/*.key
> D: couldn't find any keys in /var/lib/rpm/pubkeys/*.key
> D: loading keyring from rpmdb
> D: opening db index /var/lib/rpm/Name rdonly mode=0x0
> D: added key gpg-pubkey-fd431d51-4ae0493b to keyring
> D: added key gpg-pubkey-2fa658e0-45700c69 to keyring
> D: added key gpg-pubkey-2cefacb7-53da50b4 to keyring
> D: Using legacy gpg-pubkey(s) from rpmdb
> D: opening db index /var/lib/rpm/Providename rdonly mode=0x0
> D: closed db index /var/lib/rpm/Providename
> D: closed db index /var/lib/rpm/Name
> D: closed db index /var/lib/rpm/Packages
> D: closed db environment /var/lib/rpm
> Not loading "rhnplugin" plugin, as it is disabled
> Not loading "search-disabled-repos" plugin, as it is disabled
> Not loading "verify" plugin, as it is disabled
> Loaded plugins: product-id, subscription-manager
> Updating Subscription Management repositories.
> Config time: 0.532
> rpmdb time: 0.000
> repo time: 0.000
> Setting up Package Sacks
> pkgsack time: 0.089
> D: local action status: (0, 'rpm database not modified since last update
> (or package list recently updated)', {})
> D: rpcServer: Calling XMLRPC registration.welcome_message
> D: closed db index /var/lib/rpm/Providename
> D: closed db index /var/lib/rpm/Name
> D: closed db index /var/lib/rpm/Packages
> D: closed db environment /var/lib/rpm
>
>
>
>
> --
> *From:* spacewalk-list-boun...@redhat.com <
> spacewalk-list-boun...@redhat.com> on behalf of Andy Warring <
> kazo...@gmail.com>
> *Sent:* Wednesday, October 24, 2018 12:33 PM
> *To:* spacewalk-list@redhat.com
> *Subject:* Re: [Spacewalk-list] rhn_check
>
> Hi Jeffrey,
>
> what is the output of
>
> rhn_check -v -v -v
>
> ?
>
> regards
>
> Andy
>
>
> On Wed, 24 Oct 2018 at 15:52, Irwin, Jeffrey <
> jeffrey.ir...@rivertechllc.com> wrote:
>
>> Thank you Robert, that made the machine active again. Still can't get
>> rhn_check to work.
>>
>> From: Robert Paschedag
>> Sent: Wednesday, October 24, 2018 3:03 AM
>> To: spacewalk-list@redhat.com; Irwin, Jeffrey; spacewalk-list@redhat.com
>> Subject: Re: [Spacewalk-list] rhn_check
>>
>> Am 23. Oktober 2018 21:09:32 MESZ schrieb "Irwin, Jeffrey" <
>> jeffrey.ir...@rivertechllc.com>:
>> >I am getting the following error:
>> >
>> >
>> >ERROR: unable to read system id.?
>>
>> In the GUI, create a re-registration key for that system. Then
>> re-register that system with that key
>>
>> rhnreg_ks --force --activationkey yourkey
>> --serverUrl=url_to_your_server/XMLRPC
>>
>> Robert
>> >
>> >
>> >
>> >no idea what is going on here, the system is showing up in the gui
>>
>>
>> --
>> sent from my mobile device
>>
>> ___
>> Spacewalk-list mailing list
>> Spacewalk-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] CLI to determine registration?
You could run this on a system with spacecmd configured: spacecmd system_details SYSTEMNAME You could also pull the system details via the Spacewalk API. Bill Howe howe.b...@gmail.com <http://www.linkedin.com/in/whowe> On Thu, Oct 25, 2018 at 10:59 AM Guy Matz wrote: > Hi! Is there a command I can run on a spacewalk client to get the > activation key that was used to register to spacewalk? > ___ > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] spacecmd invalid password issue on spacewalk 2.7
Try clearing your spacecmd cache. spacecmd clear_caches Bill On Tue, Aug 28, 2018 at 1:46 AM wrote: > HI, > > > > I facing issue while running spacecmd command it always say invalid > password . when I restart spacewalk service it working fine 2 or attempts > after the same issue occurred. Please help how to fix it I am running with > spacewalk 2.7 on centos > > > > WARNING: Cached credentials are invalid > > INFO: Spacewalk Username: admin > > Spacewalk Password: > > ERROR: Invalid credentials > > > > Best Regards, > > *Suhail Siddiqui* > > -- > Please note. The information contained in this message is confidential and > is intended only for the use of the individual named above and others who > have been specially authorized to receive it. If you are not the intended > recipient, you are hereby notified that any dissemination, distribution or > copying of this communication is strictly prohibited. The attachments have > been scanned for viruses prior to leaving our E-mail system. UPM-Kymmene > Corporation shall not be liable for any consequences of any virus being > passed on. > ___ > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] server says client should be updated, but nothing happens
We use cron to run a "date checker" type script. The date checker script
can add the functionality you describe (first Monday).
The script will determine whether or not to execute a python scheduler
script. (this uses the python API to schedule updates)
The example below executes a date checker script every Monday.
The date checker script then determines if the next day is the first,
second, or third Tuesday of the month.
If so, it runs the scheduler python script to actually schedule the updates
in either Dev, Test, or Prod.
* Cron Job *
/etc/cron.d/os-updates-checker
#-Target: Run on the Mon before 1st,2nd,3rd Tues of month (Dev,Test,Prod
Patch Days)
00 08 * * mon root /scripts/os-updates/schedule-updates-check.sh
--* Date Check Script: schedule-updates-check.sh* --
#!/bin/bash
# Title: schedule-updates-check.sh
# Description: Determine if Schedule Updates should be run
# The scheduler should run on the Monday before each environment patch
day.
# The updates should be scheduled to deploy on Tuesday at 0800.
# Script to execute (environment is filled in during the if block)
script="/scripts/os-updates/schedule-updates.py --days 1 --group all_"
# Log file
log_file="/var/log/os-updates/schedule-updates-check.log"
echo " Log Started: $(date) " >> ${log_file}
# If today is Monday AND 1 day from now is >=1 and <=21(1st,2nd,3rd Tue)
if [[ "$(date '+%a')" == "Mon" ]] && [[ $(date +%-d -d "+1 day") -ge 1 ]];
then
# First Tue: Development
if [[ $(date +%-d -d "+1 day") -le 7 ]]; then
echo ">> OK: One day from now is the first Tue of the Month; execute
script(${script}dev)." >> ${log_file}
${script}dev 2>&1 >> ${log_file}
# Second Tue: System Test
elif [[ $(date +%-d -d "+1 day") -le 14 ]]; then
echo ">> OK: One day from now is the second Tue of the Month; execute
script(${script}test)." >> ${log_file}
${script}systest 2>&1 >> ${log_file}
# Third Tue: Production
elif [[ $(date +%-d -d "+1 day") -le 21 ]]; then
echo ">> OK: One day from now is the third Tue of the Month; execute
script(${script}prod)." >> ${log_file}
${script}prod 2>&1 >> ${log_file}
else
echo ">> NO-EXEC: One day from now is NOT the first,second, or third
Tue of the Month. Will NOT execute script(${script})." >> ${log_file}
fi
else
echo ">> NO-EXEC: One day from now is NOT the first,second, or third Tue
of the Month. Will NOT execute script(${script})." >> ${log_file}
fi
echo -e " Log Ended: $(date) \n" >> ${log_file}
---
Bill Howe
howe.b...@gmail.com <http://www.linkedin.com/in/whowe>
On Tue, Aug 14, 2018 at 4:42 PM Guy Matz wrote:
> So there's no easy way to schedule all machines to update, say once a
> month on the first Monday, or something like that? How do you folks
> generally schedule and kick off your updates?
>
> On Mon, Aug 13, 2018 at 5:25 PM David Rock wrote:
>
>>
>> > On Aug 13, 2018, at 16:09, Guy Matz wrote:
>> >
>> > Hi! In the Spacewalk UI I see:
>> > Software Updates AvailablePackages: 6
>> >
>> > rhnsd is running on the client but the client does not get updated.
>> Running 'yum update' on the client would get it to update, but I think
>> rhnsd is supposed to take care of this for me . . .
>>
>> No. That’s not what rhnsd does. That just checks into the environment
>> and looks for tasks that have been assigned to the client; it doesn’t
>> automatically apply anything. You have to explicitly schedule tasks so
>> when rhnsd connects, it runs the tasks that are waiting for it.
>>
>> > what do I need to do to have the client automatically update?
>>
>> Short of putting something in cron, not much. You might be able to
>> create a scheduled event, or use the API to set up a task that the client
>> will pick up.
>>
>> > One more question: Is it possible to have a post-update script run?
>>
>> You could set up a remote execution script as a wrapper that runs your
>> yum update and then afterward have it run something else. I have often
>> used that and applied to a group of systems under SSM in satellite.
>>
>>
>> —
>> David Rock
>> da...@graniteweb.com
>>
>>
>>
>>
>>
>> ___
>> Spacewalk-list mailing list
>> Spacewalk-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] configuration file question
To answer the channel question; you should create a new config channel that deploys that file to the sub-set of systems you are targeting. The following general guidelines for config channel organization work well for our company: - base config channel (generic system config you want applied to ALL systems no matter what and that are NOT OS specific) - os specific channels (ie: centos 6 and centos 7 channels that deploy files that are specific to the respective OS's) - server role channels (ie: web servers, processing nodes, etc) - Additionally, it can be helpful to split the server role config channels into your environments such as a Dev, Testing, and Production version of the channel (ie: web servers dev, web servers testing, web servers prod). This can help with change management and ensuring you don't push out mass changes to production that breaks it. Order their precedence so that the more specific they get, the config channels can over ride the ones below it. Have registration keys auto subscribe systems to their base and os specific channels. You will then need to provide your own method of subscribing systems to role specific channels. (either manually or using some sort of automation with the APIs) Good luck! Bill Howe howe.b...@gmail.com <http://www.linkedin.com/in/whowe> On Tue, Sep 26, 2017 at 5:16 PM, Konstantin Raskoshnyi <konra...@gmail.com> wrote: > Hi Elizabeth, > You need to deploy files manually to specific machines/groups. > > On Tue, Sep 26, 2017 at 1:56 PM, Elizabeth Jones <oogiej...@yahoo.com> > wrote: > >> I started using configuration files from my spacewalk server and it is >> awesome. Got a question though - >> >> I have a channel called channel1 and I have 2 files in it that are >> syncing out to 50 servers. If I add a new file to this channel but only >> want it to go to a subset of servers, will this work? Or will my nightly >> check say hey this file hasn't been deployed to these servers I'd better >> push it out to all 50? >> >> ___ >> Spacewalk-list mailing list >> Spacewalk-list@redhat.com >> https://www.redhat.com/mailman/listinfo/spacewalk-list >> > > > ___ > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list > ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
Re: [Spacewalk-list] Where are Spacewalk logs when applying patches?
Avi, Thanks for the info...I'll have to give that a shot. Bill Howe howe.b...@gmail.com <http://www.linkedin.com/in/whowe> On Sun, Apr 30, 2017 at 4:33 PM, Avi Miller <avi.mil...@oracle.com> wrote: > Hi, > > On 1 May 2017, at 7:10 am, Bill <howe.b...@gmail.com> wrote: > > >- osad -> Constant issues with that daemon...found myself writing >auto-healing health checks for it and constantly baby sitting it. > > You might want to consider switching the jabberd database from the default > Berkeley DB to either SQLite or PostgreSQL: > > https://omg.dje.li/2017/02/configuring-spacewalks- > jabberd-to-use-an-sqlite-backend/ > https://omg.dje.li/2017/03/configuring-spacewalks- > jabberd-to-use-a-postgresql-backend/ > > Since doing this I’ve had zero problems with osad on both small and very > large implementations. All the issues with osad seem to be caused by the > default DB driver. > > FYI, you’ll need to reapply this configuration after upgrading Spacewalk > (e.g. from 2.5 to 2.6) as the spacewalk-setup tool resets the configuration > back to the default during an upgrade. > > Cheers, > Avi > > > -- > Oracle <http://www.oracle.com> > Avi Miller | Product Management Director | +61 (3) 8616 3496 > <+61%203%208616%203496> > Oracle Linux and Virtualization > 417 St Kilda Road, Melbourne, Victoria 3004 Australia > > > ___ > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list > ___ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
