Am 19.02.2016 um 13:47 schrieb Ian B :
> We currently do all security updates at short notice (as opposed to
> everything), via a script. I've amended the grub config and rebooted to
> make sure it will reboot into the correct kernel now, and yes
> /etc/sysconfig/kernel was different to production
> Date: Friday, February 19, 2016 12:47:54 +
> From: Ian B
>
> On Fri, Feb 19, 2016 at 12:33 PM, Richard wrote:
>
>> > Date: Friday, February 19, 2016 11:08:48 +
>> > From: Ian B
>> >
>> > On Fri, Feb 19, 2016 at 10:56 AM, Ian B
>> > wrote:
>> >
>> >> Hi all,
>> >>
>> >> We have a
Thanks Richard,
We currently do all security updates at short notice (as opposed to
everything), via a script. I've amended the grub config and rebooted to
make sure it will reboot into the correct kernel now, and yes
/etc/sysconfig/kernel was different to production servers. We may try all
packag
> Date: Friday, February 19, 2016 11:08:48 +
> From: Ian B
>
> On Fri, Feb 19, 2016 at 10:56 AM, Ian B
> wrote:
>
>> Hi all,
>>
>> We have a development server we have just tried updating the
>> kernel & glibc after recent recommendations. Its been stable
>> previously for a few years wit
Just noticed that in the trace, it shows an old kernel, so I don't think
grub was automatically selecting the latest kernel. Just wondering what
process updates the default to be the latest kernel, and if a problem could
be an update but grub selecting an older kernel, but other packages updated
?
Hi all,
We have a development server we have just tried updating the kernel & glibc
after recent recommendations. Its been stable previously for a few years
with only scheduled reboots.
Its running
Centos 6.6(final)
2.6.32-573.18.1.el6.x86_64
GNU libc 2.12
Upgraded via YUM, rebooted, all fine fo
6 matches
Mail list logo
