I don't think this is a permission problem, because "rhn_check" command or yum 
works perfectly.

I'll keep searching.

----- Mail original -----
De: "Robert Paschedag" <robert.pasche...@web.de>
À: "Thomas Foster" <thomas.foste...@gmail.com>
Cc: "spacewalk-list" <spacewalk-list@redhat.com>
Envoyé: Vendredi 16 Septembre 2016 14:15:18
Objet: Re: [Spacewalk-list] Schedule kernel upgrade result in kernel panic

I also never had problems with SLES or Debian systems.

Robert
Am 16.09.2016 13:48 schrieb Thomas Foster <thomas.foste...@gmail.com>:
>
> I've seen that happened when yum install couldn't write to /boot (either 
> because of security rules in place..cis comes to mind).
>
>
> On Sep 16, 2016 7:37 AM, "Robert Paschedag" <robert.pasche...@web.de> wrote:
>>
>> I don't think, that rhnsd is causing this. Seems more related to yum.
>>
>> Am 16.09.2016 08:52 schrieb Lionel Caignec <caig...@cines.fr>:
>> >
>> > Perhaps this is a bug of the rhnsd agent for Rhel7 which is timing out 
>> > during kernel update process (which is long).
>> > Is it a config file which can defer between Rhel7 and Rhel6?
>> >
>> > ----- Mail original -----
>> > De: "Lionel Caignec" <caig...@cines.fr>
>> > À: "spacewalk-list" <spacewalk-list@redhat.com>
>> > Envoyé: Vendredi 16 Septembre 2016 08:43:32
>> > Objet: Re: [Spacewalk-list] Schedule kernel upgrade result in kernel panic
>> >
>> > Ok thank you i understand now why initramfs missing, i will look in "yum 
>> > debug" log if it exists.
>> >
>> > ----- Mail original -----
>> > De: "William H. ten Bensel" <whten...@up.com>
>> > À: "spacewalk-list" <spacewalk-list@redhat.com>
>> > Envoyé: Jeudi 15 Septembre 2016 21:09:37
>> > Objet: Re: [Spacewalk-list] Schedule kernel upgrade result in kernel panic
>> >
>> > - Schedule a kernel update from Web GUI, let spacewalk agent do it's job 
>> > and get kernel update (/boot/initramfs.... missing)
>> >
>> > Just saw something similar today.
>> > Issue: Timed out (+2 hours) in the middle of the yum upgrade process.
>> > Solution: Reboot to previous kernel, run yum-complete-transaction, and 
>> > reinstall the new kernel rpms.
>> >
>> > - Thanks and good luck
>> >
>> >
>> > From: Lionel Caignec <caig...@cines.fr>
>> > To: spacewalk-list <spacewalk-list@redhat.com>
>> > Date: 09/15/2016 04:34 AM
>> > Subject: Re: [Spacewalk-list] Schedule kernel upgrade result in kernel 
>> > panic
>> > Sent by: spacewalk-list-boun...@redhat.com
>> >
>> >
>> > This email originated from outside of the company. Please use discretion 
>> > if opening attachments or clicking on links.
>> >
>> > Hi,
>> >
>> > i'm still stuck, i cannot schedule a kernel update from spacewalk (web 
>> > gui) to my CentOS 7 client, because at reboot my server go into "kernel 
>> > panic"
>> >
>> > I don't understand the difference between this 2 way of doing :
>> > - Schedule a kernel update from Web GUI, let spacewalk agent do it's job 
>> > and get kernel update (/boot/initramfs.... missing)
>> > - Schedule a kernel update from Web GUI, launch on client "rhn_chek" --> 
>> > reboot with no problem on the newest kernel.
>> >
>> > All kernel version give this result, my spacewalk is in version 2.5, but i 
>> > already have this bug in 2.4.
>> >
>> > How can i get debug log from spacewalk agent, perhaps there is something 
>> > interisting in.
>> >
>> > Thank for helping
>> >
>> > --
>> > Lionel
>> >
>> > ----- Mail original -----
>> > De: "Lionel Caignec" <caig...@cines.fr>
>> > À: "spacewalk-list" <spacewalk-list@redhat.com>
>> > Envoyé: Mardi 23 Août 2016 11:43:12
>> > Objet: Re: [Spacewalk-list] Schedule kernel errata upgrade result in 
>> > kernel panic
>> >
>> > Hi,
>> >
>> > i use the webUI to schedule update. It's not related to one specific 
>> > update, but all kernel update (it's a bug i've for months now.). When a 
>> > new kernel is released i schedule update and reboot --> Result in "kernel 
>> > panic".
>> >
>> > All my clients os are Centos 7 and RedHat 7.
>> >
>> > Lionel.
>> >
>> > ----- Mail original -----
>> > De: "Tomas Lestach" <tlest...@redhat.com>
>> > À: "spacewalk-list" <spacewalk-list@redhat.com>
>> > Envoyé: Mardi 23 Août 2016 11:16:52
>> > Objet: Re: [Spacewalk-list] Schedule kernel errata upgrade result in 
>> > kernel panic
>> >
>> > Hello, please, help me understand your problem.
>> > You write:
>> > * if you "schedule a kernel errata update at reboot", there's an issue
>> > with initramfs, grub.cfg ...
>> > * if you "schedule upgrade with gui", everything's ok
>> >
>> > Does it mean the 1st case isn't via WebUI? Is it via API?
>> >
>> > Can you be more specific? What OS do you use on the client, what erratum
>> > are you scheduling for update? What way? ...
>> >
>> > Thanks,
>> > --
>> > Tomas Lestach
>> > Red Hat Satellite Engineering
>> >
>> > On 08/23/2016 10:54 AM, Lionel Caignec wrote:
>> > > Hi,
>> > >
>> > > i've a annoying bug with spacewalk. When i schedule a kernel errata 
>> > > update at reboot my server is going into kernel panic.
>> > >
>> > > After some time i've found that initramfs was not generated during 
>> > > update phase. Moreover in grub.cfg the line "initrd ..." is missing.
>> > > If i boot with an old kernel and i launch "yum reinstall kernel" server 
>> > > will boot without problem on new kernel.
>> > >
>> > >
>> > > But if i schedule upgrade with gui, and then use "rhn_check -vvv" on my 
>> > > server there is no problem.
>> > >
>> > > Someone could help me? What do i missing?
>> > >
>> > >
>> > > Thanks,
>> > >
>> > > --
>> > > Lionel Caignec
>> > >
>> > > Centre Informatique National de l' Enseignement Supérieur
>> > > 950 rue de Saint Priest
>> > > 34097 MONTPELLIER Cedex 5
>> > > Tel : (33) 04 67 14 14 14
>> > > Fax : (33)04 67 52 37 63
>> > > http://www.cines.fr
>> > >
>> > > _______________________________________________
>> > > 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
>> >
>> > _______________________________________________
>> > Spacewalk-list mailing list
>> > Spacewalk-list@redhat.com
>> > https://www.redhat.com/mailman/listinfo/spacewalk-list
>> >
>> > **
>> >
>> > This email and any attachments may contain information that is 
>> > confidential and/or privileged for the sole use of the intended recipient. 
>> > Any use, review, disclosure, copying, distribution or reliance by others, 
>> > and any forwarding of this email or its contents, without the express 
>> > permission of the sender is strictly prohibited by law. If you are not the 
>> > intended recipient, please contact the sender immediately, delete the 
>> > e-mail and destroy all copies.
>> >
>> > **
>> >
>> > _______________________________________________
>> > 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
>>
>> _______________________________________________
>> 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

Reply via email to