Hi Waldirio

Yes, it is. When using local ‚yum update‘ we haven’t seen this issue so far.
Thank you very much for your Help!

Cheers,
Rolf

Von: Waldirio Manhães Pinheiro [mailto:waldi...@gmail.com]
Gesendet: Donnerstag, 12. Februar 2015 12:26
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] anyone else unable to update clients since 
bugzilla #1182337

Rolf, good morning

If you kickstart a new machine (same as you told) and execute yum update 
manually, works fine ?!

Take Care

______________
Atenciosamente
Waldirio
msn: waldi...@gmail.com<mailto:waldi...@gmail.com>
Skype: waldirio
Site: www.waldirio.com.br<http://www.waldirio.com.br>
Blog: blog.waldirio.com.br<http://blog.waldirio.com.br>
LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646
PGP: www.waldirio.com.br/public.html<http://www.waldirio.com.br/public.html>

On Thu, Feb 12, 2015 at 8:26 AM, Linder, Rolf 
<rolf.lin...@united-security-providers.ch<mailto:rolf.lin...@united-security-providers.ch>>
 wrote:
Dear spacewalkers

In the last time (after the issue from “nss-softokn” updates? 
https://bugzilla.redhat.com/show_bug.cgi?id=1182337 / 
https://www.centos.org/forums/viewtopic.php?p=214791&f=13#p214791 ) we keep 
having issues with spacewalk-nodes being kickstarted and then updated via 
spacewalk.

State is as follows (reproducible):


1.       Kickstart centos 6.6 node (x86_84, spacewalk 2.2 client & server)

2.       Schedule update via Spacewalk WebUI

3.       After some running time, “rhn_check” is still there but not doing any 
work and spacewalk will never complete the update action.

From our last run, we just could catch the strace-output prior to the rhn_check 
on the node just before it stopped working:

….
pwrite(48, 
"\0\0\0\0\1\0\0\0b\2\0\0\332\0\0\0\0\0\0\0\24\0T\16\0\r\337\17\326\17\265\17"...,
 4096, 2498560) = 4096
pwrite(48, 
"\0\0\0\0\1\0\0\0c\2\0\0\256\0\0\0\0\0\0\0\16\0\272\16\0\r\337\17\326\17\265\17"...,
 4096, 2502656) = 4096
pwrite(48, 
"\0\0\0\0\1\0\0\0n\2\0\0\253\0\0\0\0\0\0\0.\0\"\f\0\r\337\17\316\17\255\17"..., 
4096, 2547712) = 4096
pwrite(48, 
"\0\0\0\0\1\0\0\0~\2\0\0\345\0\0\0\0\0\0\0\24\0004\16\0\r\337\17\326\17\265\17"...,
 4096, 2613248) = 4096
fdatasync(48)                           = 0
rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], ~[KILL STOP RTMIN RT_1], 8) = 0
rt_sigprocmask(SIG_SETMASK, ~[KILL STOP RTMIN RT_1], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
dup(1)                                  = 51
rt_sigprocmask(SIG_SETMASK, NULL, [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, NULL, [CHLD], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigaction(SIGCHLD, NULL, {SIG_DFL, [], SA_RESTORER, 0x7f18a9084710}, 8) = 0
rt_sigaction(SIGCHLD, {0x7f189cb67de0, [], SA_RESTORER|SA_SIGINFO, 
0x7f18a9084710}, {SIG_DFL, [], SA_RESTORER, 0x7f18a9084710}, 8) = 0
pipe([52, 53])                          = 0
rt_sigprocmask(SIG_SETMASK, NULL, [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, 
child_tidptr=0x7f18a984c9d0) = 2072
rt_sigprocmask(SIG_SETMASK, NULL, [CHLD], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, NULL, [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0
close(52)                               = 0
close(53)                               = 0
rt_sigprocmask(SIG_SETMASK, NULL, [CHLD], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
futex(0x3e281d8, FUTEX_WAIT_PRIVATE, 2, NULL) = ? ERESTARTSYS (To be restarted)
--- SIGCHLD (Child exited) @ 0 (0) ---
wait4(0, 0x7fff570e950c, WNOHANG, NULL) = -1 EACCES (Permission denied)
rt_sigreturn(0)                         = -1 EINTR (Interrupted system call)
futex(0x3e281d8, FUTEX_WAIT_PRIVATE, 2, NULL


at this time there won’t be any progress.
Anyone have an idea why this is happening?

Thank you very much!

Cheers,
Rolf

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com<mailto:Spacewalk-list@redhat.com>
https://www.redhat.com/mailman/listinfo/spacewalk-list

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to