[Spacewalk-list] copr-be.cloud.fedoraproject.org is down？

[Zhou, Rui A. (NSB - CN/Shanghai)]

This copr-be.cloud.fedoraproject.org seems to be down:

curl 
https://copr-be.cloud.fedoraproject.org/results/%40spacewalkproject/spacewalk-2.8-client/epel-7-x86_64/repodata/repomd.xml
curl: (7) Failed connect to copr-be.cloud.fedoraproject.org:443; Connection 
timed out

if it is true？
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Antwort: Re: Antwort: Re: Antwort: Re: Any chance to get "Schedule"-Jobs running on SW-Server?

[Matthias Gruber]

Hi Phil

okay cool, I'll do the same thanks, was in doubt if its okay.

cheers
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:  23.01.2019 15:11
Betreff:Re: [Spacewalk-list] Antwort: Re: Antwort: Re: Any chance 
to  get "Schedule"-Jobs running on  SW-Server?
Gesendet von:   spacewalk-list-boun...@redhat.com



Yes, I’ve registered my Spacewalk server with itself, to get updates etc, 
and installed OSAD on it.
 
Regards
Phil
 
From: spacewalk-list-boun...@redhat.com 
 On Behalf Of mgru...@metzler.com
Sent: 23 January 2019 12:46
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Antwort: Re: Antwort: Re: Any chance to get 
"Schedule"-Jobs running on SW-Server?
 
Hi Phil 

Ohh.. thanks a lot for your notices, they are quite helpfull, but :-) 

can I install an osad on the spacewalk-server, so that he can schedules 
tasks on "himself"? 

I tried the following, on the SW-Web-Gui: 

Systems -> Seeking my Spacewalk-Server (swmain) -> Details -> Remote 
Command 
As skript just a "ls" or something like that and schedule in 5 mins. 

Got a "Remote Command has been scheduled successfully at 1/23/19 1:34:00 
PM CET. " 

A look into Schedule tells me "Pending", afai understand, and I will see 
it tomorrow, in max 4h he will/should execute my simple ls, and now the 
part I am seeking for... 
Again thats not scheduled on any client, but on the Spacewalk-Server, 
where Spacewalk is running solely, pgsql, the webgui, osa-dispatcher and 
all the stuff.. 

As I learned, the osa-dispatcher -> osad communication does the trick to 
schedule it and run it at the designated time, not the 4h cycle, since the 
osad runs on SW-clients, there is no trouble, (well sometimes with the 
communication of osad, but thats a different topic), now the question, 
could I riskfree install a osad on my swmain, there would be running 
osa-dispatcher and osad on the same machine, and would he (swmain) pick 
the job correctly? 

Thanks again for your time 
cheers 
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:23.01.2019 13:03 
Betreff:Re: [Spacewalk-list] Antwort: Re: Any chance to get 
"Schedule"-JobsrunningonSW-Server? 
Gesendet von:spacewalk-list-boun...@redhat.com 




Hi Matthias 
  
No problem, I have NO ability to write as much as you have in a foreign 
language so you’re still doing far better than meJ 
  
When Spacewalk is installed on the server osa-dispatcher will be running 
automatically. Scheduled tasks (including scripts initiated from Remote 
Command) will only be picked up every 4 hours, as mentioned below. You 
could possibly reduce this to minutes, rather than hours, by amending the 
setting in /etc/sysconfig/rhn/rhnsd. Alternatively, you can install OSAD 
on registered client systems and then scheduled tasks should be picked up 
almost immediately. 
  
If you want to install OSAD my notes, below, may help? 
  
osa-dispatcher 
Server-side service written in Python that determines when an osad client 
instance needs to be pinged or run rhn_check and sends a message telling 
them to do so. 
  
Open Source Architecture Daemon (OSAD) 
Client-side service written in Python that responds to pings and runs 
rhn_check when told to by osa-dispatcher. 
  
Install OSAD and related RHN/Spacewalk packages 
# yum -y install osad rhncfg rhncfg-actions rhncfg-client 
  
Spacewalk Actions Control - Enable Scheduled Actions 
# rhn-actions-control --enable-all 
  
Spacewalk Actions Control - Show Status 
# rhn-actions-control --report 
  
Start OSAD 
# systemctl start osad.service OR service osad start 
  
Enable OSAD 
# systemctl enable osad.service OR chkconfig osad on 
  
OSAD Log File 
/var/log/osad 
  
Regards 
Phil 
  
From: spacewalk-list-boun...@redhat.com  On Behalf Of mgru...@metzler.com
Sent: 23 January 2019 11:21
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Antwort: Re: Any chance to get "Schedule"-Jobs 
running on SW-Server? 
  
Hi Phil, 

thanks for your explanation, sorry, as non native english person, I had 
some trouble to formulate it correct 

Yes thats the way, as you describe with client systems, the way I also do 
it or via spacecmd, 

[Spacewalk-list] Repo syncs in Spacewalk 2.9 ERROR: 'NoneType' object has no attribute 'isdigit'

[Kalchik, Jeffery]

Good morning, all

I upgraded my spacewalk host from 2.8 to 2.9 on Monday morning, Jan. 21 (CentOS 
6.10 64bit hosted,) I thought completely successfully.  However, 17 of my 
download channels/repositories are now showing the following error:

ERROR: 'NoneType' object has no attribute 'isdigit'

I haven't found a pattern, as multiple sources and EL5, EL6 and EL7 
repositories are all showing the issue.  Not all are, just 17.  Manually 
executing spacewalk-repo-sync with a '-vvv' option isn't giving any more detail 
in the reposync channel logs, unfortunately.  The errors are displayed after 
the errata count with no more detail.  I also haven't found anything suspicious 
or smoking anywhere else.

Just to get even more odd, it looks like the first reposync on at least a 
couple of these completed successfully after the upgrade, but has been falling 
since.

I'm at a loss on how to proceed at this point.  None of the log files I've spun 
through seem to have any other bearing on this, and I'm definitely not a Python 
type to begin debugging the internals.

Is anyone else experiencing this?

Jeff Kalchik
Server Support Managed Resources
Land O'Lakes
This message may contain confidential material from Land O'Lakes, Inc. (or its 
subsidiary) for the sole use of the intended recipient(s) and may not be 
reviewed, disclosed, copied, distributed or used by anyone other than the 
intended recipient(s). If you are not the intended recipient, please contact 
the sender by reply email and delete all copies of this message.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Antwort: Re: Antwort: Re: Any chance to get "Schedule"-Jobs running on SW-Server?

[p.cook...@bham.ac.uk]

Yes, I’ve registered my Spacewalk server with itself, to get updates etc, and 
installed OSAD on it.

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of mgru...@metzler.com
Sent: 23 January 2019 12:46
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Antwort: Re: Antwort: Re: Any chance to get 
"Schedule"-Jobs running on SW-Server?

Hi Phil

Ohh.. thanks a lot for your notices, they are quite helpfull, but :-)

can I install an osad on the spacewalk-server, so that he can schedules tasks 
on "himself"?

I tried the following, on the SW-Web-Gui:

Systems -> Seeking my Spacewalk-Server (swmain) -> Details -> Remote Command
As skript just a "ls" or something like that and schedule in 5 mins.

Got a "Remote Command has been scheduled 
successfully
 at 1/23/19 1:34:00 PM CET. "

A look into Schedule tells me "Pending", afai understand, and I will see it 
tomorrow, in max 4h he will/should execute my simple ls, and now the part I am 
seeking for...
Again thats not scheduled on any client, but on the Spacewalk-Server, where 
Spacewalk is running solely, pgsql, the webgui, osa-dispatcher and all the 
stuff..

As I learned, the osa-dispatcher -> osad communication does the trick to 
schedule it and run it at the designated time, not the 4h cycle, since the osad 
runs on SW-clients, there is no trouble, (well sometimes with the communication 
of osad, but thats a different topic), now the question, could I riskfree 
install a osad on my swmain, there would be running osa-dispatcher and osad on 
the same machine, and would he (swmain) pick the job correctly?

Thanks again for your time
cheers
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" 
mailto:p.cook...@bham.ac.uk>>
An:"spacewalk-list@redhat.com" 
mailto:spacewalk-list@redhat.com>>
Datum:23.01.2019 13:03
Betreff:Re: [Spacewalk-list] Antwort: Re: Any chance to get
"Schedule"-JobsrunningonSW-Server?
Gesendet von:
spacewalk-list-boun...@redhat.com




Hi Matthias

No problem, I have NO ability to write as much as you have in a foreign 
language so you’re still doing far better than me☺

When Spacewalk is installed on the server osa-dispatcher will be running 
automatically. Scheduled tasks (including scripts initiated from Remote 
Command) will only be picked up every 4 hours, as mentioned below. You could 
possibly reduce this to minutes, rather than hours, by amending the setting in 
/etc/sysconfig/rhn/rhnsd. Alternatively, you can install OSAD on registered 
client systems and then scheduled tasks should be picked up almost immediately.

If you want to install OSAD my notes, below, may help?

osa-dispatcher
Server-side service written in Python that determines when an osad client 
instance needs to be pinged or run rhn_check and sends a message telling them 
to do so.

Open Source Architecture Daemon (OSAD)
Client-side service written in Python that responds to pings and runs rhn_check 
when told to by osa-dispatcher.

Install OSAD and related RHN/Spacewalk packages
# yum -y install osad rhncfg rhncfg-actions rhncfg-client

Spacewalk Actions Control - Enable Scheduled Actions
# rhn-actions-control --enable-all

Spacewalk Actions Control - Show Status
# rhn-actions-control --report

Start OSAD
# systemctl start osad.service OR service osad start

Enable OSAD
# systemctl enable osad.service OR chkconfig osad on

OSAD Log File
/var/log/osad

Regards
Phil

From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of mgru...@metzler.com
Sent: 23 January 2019 11:21
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Antwort: Re: Any chance to get "Schedule"-Jobs 
running on SW-Server?

Hi Phil,

thanks for your explanation, sorry, as non native english person, I had some 
trouble to formulate it correct

Yes thats the way, as you describe with client systems, the way I also do it or 
via spacecmd, but I would like to schedule this way on my SpaceWalk-Server, not 
the client.
As far as I noticed there is the osa-dispatcher running but not an osad 
(client) therefore he (my spacewalk-server) doesnt pick the job

This was my question... (still have trouble to put it in propper english 
sentences ;->)

cheers
Matthias


-

Re: [Spacewalk-list] Any chance to get "Schedule"-Jobs running on SW-Server?

[Kevin Olbrich]

Hi Matthias,

I did not try it but you could add / register the SW server itself to
the inventory.
This would give you the same features on the server that the clients can use.

Kind regards
Kevin

Am Mi., 23. Jan. 2019 um 10:57 Uhr schrieb Matthias Gruber
:
>
> Hi!
>
> Is there any chance to Schedule-Jobs via "system_runscript" working on a 
> SpaceWalk-Server like it works on any Client?
> I know taskomatic is the "scheduler" within SpaceWalk, but that is not 
> configurable.
>
> At the moment I use at to schedule dynamic processes, but thats a bit "tricky"
>
> Perhaps someone has a better solution, and not using something like obsidian 
> or Automic?
>
> cheers
> 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
>
>
> Persönlich haftende Gesellschafter: Harald Illy, Michael Klaus, Friedrich von 
> Metzler, Emmerich Müller, Gerhard Wiesheu
> Vorsitzender des Aufsichtsrats: Dr. Christoph Schücking
> Sitz der Gesellschaft: Frankfurt am Main, Handelsregister-Nr. HRB 27 515
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfänger 
> sein, so bitten wir Sie höflich, dies unverzüglich dem Absender mitzuteilen 
> und die Nachricht zu löschen. Es ist unzulässig, die Nachricht unbefugt 
> weiterzuleiten oder zu kopieren. Da wir nicht die Echtheit oder 
> Vollständigkeit der in dieser Nachricht enthaltenen Informationen garantieren 
> oder zusichern können, sind die vorstehenden Ausführungen rechtlich nicht 
> bindend. Eine Haftung hierfür wird ausgeschlossen.
> This message is confidential. If you are not the intended recipient, we 
> kindly ask you to inform the sender and delete the information. Any 
> unauthorised dissemination or copying hereof is prohibited. As we cannot 
> guarantee or assure the genuineness or completeness of the information 
> contained in this message, the statements set forth above are not legally 
> binding. Accordingly we cannot accept any liability for their contents. 
> ___
> 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] Antwort: Re: Antwort: Re: Any chance to get "Schedule"-Jobs running on SW-Server?

[Matthias Gruber]

Hi Phil

Ohh.. thanks a lot for your notices, they are quite helpfull, but :-)

can I install an osad on the spacewalk-server, so that he can schedules 
tasks on "himself"?

I tried the following, on the SW-Web-Gui:

Systems -> Seeking my Spacewalk-Server (swmain) -> Details -> Remote 
Command
As skript just a "ls" or something like that and schedule in 5 mins.

Got a "Remote Command has been scheduled successfully at 1/23/19 1:34:00 
PM CET. " 

A look into Schedule tells me "Pending", afai understand, and I will see 
it tomorrow, in max 4h he will/should execute my simple ls, and now the 
part I am seeking for...
Again thats not scheduled on any client, but on the Spacewalk-Server, 
where Spacewalk is running solely, pgsql, the webgui, osa-dispatcher and 
all the stuff..

As I learned, the osa-dispatcher -> osad communication does the trick to 
schedule it and run it at the designated time, not the 4h cycle, since the 
osad runs on SW-clients, there is no trouble, (well sometimes with the 
communication of osad, but thats a different topic), now the question, 
could I riskfree install a osad on my swmain, there would be running 
osa-dispatcher and osad on the same machine, and would he (swmain) pick 
the job correctly?

Thanks again for your time
cheers
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:  23.01.2019 13:03
Betreff:Re: [Spacewalk-list] Antwort: Re: Any chance to get 
"Schedule"-Jobs running on  SW-Server?
Gesendet von:   spacewalk-list-boun...@redhat.com



Hi Matthias
 
No problem, I have NO ability to write as much as you have in a foreign 
language so you’re still doing far better than meJ
 
When Spacewalk is installed on the server osa-dispatcher will be running 
automatically. Scheduled tasks (including scripts initiated from Remote 
Command) will only be picked up every 4 hours, as mentioned below. You 
could possibly reduce this to minutes, rather than hours, by amending the 
setting in /etc/sysconfig/rhn/rhnsd. Alternatively, you can install OSAD 
on registered client systems and then scheduled tasks should be picked up 
almost immediately.
 
If you want to install OSAD my notes, below, may help?
 
osa-dispatcher
Server-side service written in Python that determines when an osad client 
instance needs to be pinged or run rhn_check and sends a message telling 
them to do so.
 
Open Source Architecture Daemon (OSAD)
Client-side service written in Python that responds to pings and runs 
rhn_check when told to by osa-dispatcher.
 
Install OSAD and related RHN/Spacewalk packages
# yum -y install osad rhncfg rhncfg-actions rhncfg-client
 
Spacewalk Actions Control - Enable Scheduled Actions
# rhn-actions-control --enable-all
 
Spacewalk Actions Control - Show Status
# rhn-actions-control --report
 
Start OSAD
# systemctl start osad.service OR service osad start
 
Enable OSAD
# systemctl enable osad.service OR chkconfig osad on
 
OSAD Log File
/var/log/osad
 
Regards
Phil
 
From: spacewalk-list-boun...@redhat.com 
 On Behalf Of mgru...@metzler.com
Sent: 23 January 2019 11:21
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Antwort: Re: Any chance to get "Schedule"-Jobs 
running on SW-Server?
 
Hi Phil, 

thanks for your explanation, sorry, as non native english person, I had 
some trouble to formulate it correct 

Yes thats the way, as you describe with client systems, the way I also do 
it or via spacecmd, but I would like to schedule this way on my 
SpaceWalk-Server, not the client. 
As far as I noticed there is the osa-dispatcher running but not an osad 
(client) therefore he (my spacewalk-server) doesnt pick the job 

This was my question... (still have trouble to put it in propper english 
sentences ;->) 

cheers 
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:23.01.2019 11:43 
Betreff:Re: [Spacewalk-list] Any chance to get "Schedule"-Jobs 
runningonSW-Server? 
Gesendet von:spacewalk-list-boun...@redhat.com 




Hi Matthias 
  
I’m not entirely sure what you’re asking but you can schedule scripts from 
the Spacewalk Web UI in the following way: 
  
Systems > Click on system name > Remote Command - Add script details then 
c

Re: [Spacewalk-list] Antwort: Re: Any chance to get "Schedule"-Jobs running on SW-Server?

[p.cook...@bham.ac.uk]

Hi Matthias

No problem, I have NO ability to write as much as you have in a foreign 
language so you’re still doing far better than me☺

When Spacewalk is installed on the server osa-dispatcher will be running 
automatically. Scheduled tasks (including scripts initiated from Remote 
Command) will only be picked up every 4 hours, as mentioned below. You could 
possibly reduce this to minutes, rather than hours, by amending the setting in 
/etc/sysconfig/rhn/rhnsd. Alternatively, you can install OSAD on registered 
client systems and then scheduled tasks should be picked up almost immediately.

If you want to install OSAD my notes, below, may help?

osa-dispatcher
Server-side service written in Python that determines when an osad client 
instance needs to be pinged or run rhn_check and sends a message telling them 
to do so.

Open Source Architecture Daemon (OSAD)
Client-side service written in Python that responds to pings and runs rhn_check 
when told to by osa-dispatcher.

Install OSAD and related RHN/Spacewalk packages
# yum -y install osad rhncfg rhncfg-actions rhncfg-client

Spacewalk Actions Control - Enable Scheduled Actions
# rhn-actions-control --enable-all

Spacewalk Actions Control - Show Status
# rhn-actions-control --report

Start OSAD
# systemctl start osad.service OR service osad start

Enable OSAD
# systemctl enable osad.service OR chkconfig osad on

OSAD Log File
/var/log/osad

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of mgru...@metzler.com
Sent: 23 January 2019 11:21
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Antwort: Re: Any chance to get "Schedule"-Jobs 
running on SW-Server?

Hi Phil,

thanks for your explanation, sorry, as non native english person, I had some 
trouble to formulate it correct

Yes thats the way, as you describe with client systems, the way I also do it or 
via spacecmd, but I would like to schedule this way on my SpaceWalk-Server, not 
the client.
As far as I noticed there is the osa-dispatcher running but not an osad 
(client) therefore he (my spacewalk-server) doesnt pick the job

This was my question... (still have trouble to put it in propper english 
sentences ;->)

cheers
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" 
mailto:p.cook...@bham.ac.uk>>
An:"spacewalk-list@redhat.com" 
mailto:spacewalk-list@redhat.com>>
Datum:23.01.2019 11:43
Betreff:Re: [Spacewalk-list] Any chance to get "Schedule"-Jobs running  
  onSW-Server?
Gesendet von:
spacewalk-list-boun...@redhat.com




Hi Matthias

I’m not entirely sure what you’re asking but you can schedule scripts from the 
Spacewalk Web UI in the following way:

Systems > Click on system name > Remote Command - Add script details then click 
on Schedule

Click on Schedule top menu item to see progress of Action

Note, by default, the rhnsd daemon on a client system connects to the Spacewalk 
server every 4 hours (see /etc/sysconfig/rhn/rhnsd) and performs any updates or 
actions that you have scheduled. However, if you install the Open Source 
Architecture Daemon (OSAD), on the client system, updates and actions should be 
picked up almost immediately from the Spacewalk server.

Regards
Phil

From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of mgru...@metzler.com
Sent: 23 January 2019 09:56
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Any chance to get "Schedule"-Jobs running on 
SW-Server?

Hi!

Is there any chance to Schedule-Jobs via "system_runscript" working on a 
SpaceWalk-Server like it works on any Client?
I know taskomatic is the "scheduler" within SpaceWalk, but that is not 
configurable.

At the moment I use at to schedule dynamic processes, but thats a bit "tricky"

Perhaps someone has a better solution, and not using something like obsidian or 
Automic?

cheers
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


Persönlich haftende Gesellschafter: Harald Illy, Michael Klaus, Friedrich von 
Metzler, Emmeric

[Spacewalk-list] Antwort: Re: Any chance to get "Schedule"-Jobs running on SW-Server?

[Matthias Gruber]

Hi Phil,

thanks for your explanation, sorry, as non native english person, I had 
some trouble to formulate it correct

Yes thats the way, as you describe with client systems, the way I also do 
it or via spacecmd, but I would like to schedule this way on my 
SpaceWalk-Server, not the client.
As far as I noticed there is the osa-dispatcher running but not an osad 
(client) therefore he (my spacewalk-server) doesnt pick the job

This was my question... (still have trouble to put it in propper english 
sentences ;->)

cheers
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:  23.01.2019 11:43
Betreff:Re: [Spacewalk-list] Any chance to get "Schedule"-Jobs 
running on  SW-Server?
Gesendet von:   spacewalk-list-boun...@redhat.com



Hi Matthias
 
I’m not entirely sure what you’re asking but you can schedule scripts from 
the Spacewalk Web UI in the following way:
 
Systems > Click on system name > Remote Command - Add script details then 
click on Schedule
 
Click on Schedule top menu item to see progress of Action
 
Note, by default, the rhnsd daemon on a client system connects to the 
Spacewalk server every 4 hours (see /etc/sysconfig/rhn/rhnsd) and performs 
any updates or actions that you have scheduled. However, if you install 
the Open Source Architecture Daemon (OSAD), on the client system, updates 
and actions should be picked up almost immediately from the Spacewalk 
server.
 
Regards
Phil
 
From: spacewalk-list-boun...@redhat.com 
 On Behalf Of mgru...@metzler.com
Sent: 23 January 2019 09:56
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Any chance to get "Schedule"-Jobs running on 
SW-Server?
 
Hi! 

Is there any chance to Schedule-Jobs via "system_runscript" working on a 
SpaceWalk-Server like it works on any Client? 
I know taskomatic is the "scheduler" within SpaceWalk, but that is not 
configurable. 

At the moment I use at to schedule dynamic processes, but thats a bit 
"tricky" 

Perhaps someone has a better solution, and not using something like 
obsidian or Automic? 

cheers 
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


Persönlich haftende Gesellschafter: Harald Illy, Michael Klaus, Friedrich 
von Metzler, Emmerich Müller, Gerhard Wiesheu
Vorsitzender des Aufsichtsrats: Dr. Christoph Schücking
Sitz der Gesellschaft: Frankfurt am Main, Handelsregister-Nr. HRB 27 515

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene 
Empfänger sein, so bitten wir Sie höflich, dies unverzüglich dem Absender 
mitzuteilen und die Nachricht zu löschen. Es ist unzulässig, die Nachricht 
unbefugt weiterzuleiten oder zu kopieren. Da wir nicht die Echtheit oder 
Vollständigkeit der in dieser Nachricht enthaltenen Informationen 
garantieren oder zusichern können, sind die vorstehenden Ausführungen 
rechtlich nicht bindend. Eine Haftung hierfür wird ausgeschlossen.
This message is confidential. If you are not the intended recipient, we 
kindly ask you to inform the sender and delete the information. Any 
unauthorised dissemination or copying hereof is prohibited. As we cannot 
guarantee or assure the genuineness or completeness of the information 
contained in this message, the statements set forth above are not legally 
binding. Accordingly we cannot accept any liability for their contents. 
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list



 

Persönlich haftende Gesellschafter: Harald Illy, Michael Klaus, Friedrich von 
Metzler, Emmerich Müller, Gerhard Wiesheu
Vorsitzender des Aufsichtsrats: Dr. Christoph Schücking
Sitz der Gesellschaft: Frankfurt am Main, Handelsregister-Nr. HRB 27 515

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfänger 
sein, so bitten wir Sie höflich, dies unverzüglich dem Absender mitzuteilen und 
die Nachricht zu löschen. Es ist unzulässig, die Nachricht unbefugt 
weiterzuleiten oder zu kopieren. Da wir nicht die Echtheit oder Vollständigkeit 
der in dieser Nachricht enthaltenen Informationen garantieren oder zusichern 
können, sind die vorstehenden Ausführungen rechtlich nicht bindend. Eine 
Haftung hierfür wird ausgeschlossen.
This message is confidential. If you are not the intended recipient, we kin

[Spacewalk-list] FW: Spacewalk Provisioning

[p.cook...@bham.ac.uk]

I know it hasn't been too long, but does anyone have any information for me 
please, as I really do want to get started with provisioning?

Many thanks
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of p.cook...@bham.ac.uk
Sent: 22 January 2019 13:30
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Spacewalk Provisioning

Hi all

I've recently built a SW 2.8 environment on a RHEL 7 server, added 
Channels/Repositories for RHEL/Oracle Linux 6/7 and successfully patched 
relevant client systems. I now want to look at provisioning RHEL/Oracle Linux 
6/7
systems - I won't be using a DHCP server. Can anyone supply simple instructions 
for doing this as I can't seem to get a proper angle on it? I was envisaging 
using the newly created repositories created for patching but when I look in 
Systems > Kickstart > Create Kickstart Profile I see this:

Base Channel: No Kickstartable Channels found.
Kickstartable Tree: No trees were found for the selected channel

I learnt that this was because I need to "enable" the repositories to be 
kickstartable by re-syncing with relevant option but this give message 
"Kickstartable tree not detected (no valid treeinfo file)" for bot Red Hat and 
Oracle Linux channels (see below). Do I need to sync from different base 
channels perhaps?

[root@ ~]# spacewalk-repo-sync -c rhel7_x86_64 --sync-kickstart
12:23:10 ==
12:23:10 | Channel: rhel7_x86_64
12:23:10 ==
12:23:10 Sync of channel started.
12:23:10
12:23:10   Processing repository with URL: 
https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os
Repository group_spacewalkproject-java-packages is listed more than once in the 
configuration
12:23:13
12:23:13   Importing comps file 
fef86aafcac04474fa71d40322b4b81bab738f67-comps.xml.
12:23:22 Packages in repo: 23382
12:24:06 No new packages to sync.
12:24:07
12:24:07   Errata in repo: 3449.
12:24:07 No new errata to sync.
12:24:07
12:24:07   Importing kickstarts.
12:24:10 Kickstartable tree not detected (no valid treeinfo file)
12:24:10 Sync of channel completed in 0:01:00.
12:24:10 Total time: 0:01:00
[root@ ~]#

[root@ ~]# spacewalk-repo-sync -c ol7_x86_64 --sync-kickstart
12:56:10 ==
12:56:10 | Channel: ol7_x86_64
12:56:10 ==
12:56:10 Sync of channel started.
12:56:11
12:56:11   Processing repository with URL: 
http://public-yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64/
Repository group_spacewalkproject-java-packages is listed more than once in the 
configuration
12:56:12
12:56:12   Importing comps file comps.xml.
12:56:18 Packages in repo: 11799
12:56:36 No new packages to sync.
12:56:36
12:56:36   Errata in repo: 1360.
12:56:37 No new errata to sync.
12:56:37
12:56:37   Importing kickstarts.
12:56:39 Kickstartable tree not detected (no valid treeinfo file)
12:56:40 Sync of channel completed in 0:00:28.
12:56:40 Total time: 0:00:28
[root@ ~]#

Regards
Phil

___
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] Any chance to get "Schedule"-Jobs running on SW-Server?

[p.cook...@bham.ac.uk]

Hi Matthias

I’m not entirely sure what you’re asking but you can schedule scripts from the 
Spacewalk Web UI in the following way:

Systems > Click on system name > Remote Command - Add script details then click 
on Schedule

Click on Schedule top menu item to see progress of Action

Note, by default, the rhnsd daemon on a client system connects to the Spacewalk 
server every 4 hours (see /etc/sysconfig/rhn/rhnsd) and performs any updates or 
actions that you have scheduled. However, if you install the Open Source 
Architecture Daemon (OSAD), on the client system, updates and actions should be 
picked up almost immediately from the Spacewalk server.

Regards
Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of mgru...@metzler.com
Sent: 23 January 2019 09:56
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Any chance to get "Schedule"-Jobs running on 
SW-Server?

Hi!

Is there any chance to Schedule-Jobs via "system_runscript" working on a 
SpaceWalk-Server like it works on any Client?
I know taskomatic is the "scheduler" within SpaceWalk, but that is not 
configurable.

At the moment I use at to schedule dynamic processes, but thats a bit "tricky"

Perhaps someone has a better solution, and not using something like obsidian or 
Automic?

cheers
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


Persönlich haftende Gesellschafter: Harald Illy, Michael Klaus, Friedrich von 
Metzler, Emmerich Müller, Gerhard Wiesheu
Vorsitzender des Aufsichtsrats: Dr. Christoph Schücking
Sitz der Gesellschaft: Frankfurt am Main, Handelsregister-Nr. HRB 27 515

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfänger 
sein, so bitten wir Sie höflich, dies unverzüglich dem Absender mitzuteilen und 
die Nachricht zu löschen. Es ist unzulässig, die Nachricht unbefugt 
weiterzuleiten oder zu kopieren. Da wir nicht die Echtheit oder Vollständigkeit 
der in dieser Nachricht enthaltenen Informationen garantieren oder zusichern 
können, sind die vorstehenden Ausführungen rechtlich nicht bindend. Eine 
Haftung hierfür wird ausgeschlossen.
This message is confidential. If you are not the intended recipient, we kindly 
ask you to inform the sender and delete the information. Any unauthorised 
dissemination or copying hereof is prohibited. As we cannot guarantee or assure 
the genuineness or completeness of the information contained in this message, 
the statements set forth above are not legally binding. Accordingly we cannot 
accept any liability for their contents.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Any chance to get "Schedule"-Jobs running on SW-Server?

[Matthias Gruber]

Hi!

Is there any chance to Schedule-Jobs via "system_runscript" working on a 
SpaceWalk-Server like it works on any Client?
I know taskomatic is the "scheduler" within SpaceWalk, but that is not 
configurable.

At the moment I use at to schedule dynamic processes, but thats a bit 
"tricky"

Perhaps someone has a better solution, and not using something like 
obsidian or Automic?

cheers
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
 

Persönlich haftende Gesellschafter: Harald Illy, Michael Klaus, Friedrich von 
Metzler, Emmerich Müller, Gerhard Wiesheu
Vorsitzender des Aufsichtsrats: Dr. Christoph Schücking
Sitz der Gesellschaft: Frankfurt am Main, Handelsregister-Nr. HRB 27 515

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfänger 
sein, so bitten wir Sie höflich, dies unverzüglich dem Absender mitzuteilen und 
die Nachricht zu löschen. Es ist unzulässig, die Nachricht unbefugt 
weiterzuleiten oder zu kopieren. Da wir nicht die Echtheit oder Vollständigkeit 
der in dieser Nachricht enthaltenen Informationen garantieren oder zusichern 
können, sind die vorstehenden Ausführungen rechtlich nicht bindend. Eine 
Haftung hierfür wird ausgeschlossen.
This message is confidential. If you are not the intended recipient, we kindly 
ask you to inform the sender and delete the information. Any unauthorised 
dissemination or copying hereof is prohibited. As we cannot guarantee or assure 
the genuineness or completeness of the information contained in this message, 
the statements set forth above are not legally binding. Accordingly we cannot 
accept any liability for their contents.


PGP.sig
Description: PGP signature
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list