You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Noting this here because I need it on the record and hopefully the next person to get in there (probably me?) will be reminded of this and see if it's fixable.
I upgraded ci-release today and Jenkins stopped working. Standard apt-get dist-upgrade which pulled in a new kernel as well as the new Jenkins. I did a reboot to get the new kernel. But it turns out that the kernel isn't happy with java -jar jenkins.war, it does an immediate Killed with syslog showing it was killed for an oom, which is absurd since both these CI machines have plenty of RAM.
Downgrading from the new kernel to the previous one fixed it. The problem version is linux-image-3.13.0-155-generic, the one it's running now is linux-image-3.13.0-153-generic. In /boot/grub/menu.lst I put default 2 to make it boot to the second one. This needs to be undone at the next kernel upgrade.
On ci things are different. It has grub2 (probably different because it's on a different hosting provider and they have different setups), but it's pinned to an even older kernel for some reason. It's running linux-tools-3.13.0-57 and changing defaults in /etc/defaults/grub has no impact even though it's doing proper updates to /boot/grub/grub.cfg. I don't know, but I'm going to leave it for now because I just don't want 3.13.0-155. So we can figure this one out later.
The text was updated successfully, but these errors were encountered:
Noting this here because I need it on the record and hopefully the next person to get in there (probably me?) will be reminded of this and see if it's fixable.
I upgraded ci-release today and Jenkins stopped working. Standard
apt-get dist-upgrade
which pulled in a new kernel as well as the new Jenkins. I did a reboot to get the new kernel. But it turns out that the kernel isn't happy withjava -jar jenkins.war
, it does an immediateKilled
with syslog showing it was killed for an oom, which is absurd since both these CI machines have plenty of RAM.Downgrading from the new kernel to the previous one fixed it. The problem version is
linux-image-3.13.0-155-generic
, the one it's running now islinux-image-3.13.0-153-generic
. In /boot/grub/menu.lst I putdefault 2
to make it boot to the second one. This needs to be undone at the next kernel upgrade.On ci things are different. It has grub2 (probably different because it's on a different hosting provider and they have different setups), but it's pinned to an even older kernel for some reason. It's running
linux-tools-3.13.0-57
and changing defaults in /etc/defaults/grub has no impact even though it's doing proper updates to /boot/grub/grub.cfg. I don't know, but I'm going to leave it for now because I just don't want 3.13.0-155. So we can figure this one out later.The text was updated successfully, but these errors were encountered: