7 Feb
2011
7 Feb
'11
1:24 p.m.
On 07/02/2011 10:30, Michael Stevens wrote:
I'm going to have a go at this soon, any chance
someone who succeeds can
write it up?
My upgrade is now finished and all working thanks to Andy.
Don't really have time just now to write up a wiki, but basically I
followed the upgrade section in the release notes.
Various bitfolk specific things I'm aware of
Before starting:
- make sure you know how to access your console before you start (you
shouldn't need it, but if anything goes wrong you'll need it)
- optionally, ask support to take a snapshot before starting
- check before you upgrade that if you have root partition on /dev/xvda1
that fdisk -l /dev/xvda works. If it doesn't you need your xvda1
renaming to xvda, contact support.
At the point where the release notes tell you to install a kernel then
udev and reboot:
- make sure grub-legacy is installed (or at least that grub2 is not
installed), as grub2 doesn't work at bitfolk yet and is likely to be
installed during the upgrade
- use the linux-image-686-bigmem kernel; check update-grub and/or
/boot/grub/menu.lst does point at the right kernel
- ensure grub kopts doesn't contain clocksource=jiffies
After upgrade:
- check again that grub-legacy is there and menu.lst still defaults to
the correct bigmem kernel
Joseph
7 Feb
7 Feb
1:55 p.m.
New subject: Lenny to Squeeze
On Mon, 07 Feb 2011 13:24:14 +0000
Joseph Heenan <joseph(a)heenan.me.uk> wrote:
On 07/02/2011 10:30, Michael Stevens wrote:
I have also done a lenny > squeeze upgrade on my local geneweb box
following the release notes.
I had no problems as such but I should have done an apt-get install
udev before running apt-get update but did it without any problems
after the initial upgrade was done and that pulled in an even newer
kernel plus other stuff.
Re Michael's Bitfolk tips I was asked if I wanted to install
grub2, so be sure to say no for a Bitfolk install. The other specific
things Michael mentions should be checked out to be on the safeside.
As for my Bitfolk VPS I think I need to wait before upgrading as I am
using a package (gallery2) from sid and even though it is marked
'hold' I don't want to risk anything going wrong as a 'Gallery' is an
essential part of my website.
I lost my Gallery during a Lenny update a few months back and had
unhappy users as a result! I had to use the repair facility in
gallery2 to get it back, a corrupted php file I think it was!
I presume that eventually gallery2 (or even gallery3) will migrate to
squeeze and that will be the time for me to upgrade.
--
John Lewis
Debian & the GeneWeb genealogical data server
I'm going to have a go at this soon, any
chance someone who
succeeds can write it up?
My upgrade is now finished and all working thanks to Andy.
Don't really have time just now to write up a wiki, but basically I
followed the upgrade section in the release notes. 
8 Feb
8 Feb
11:45 p.m.
New subject: Lenny to Squeeze
Joseph Heenan <joseph(a)heenan.me.uk> writes:
On 07/02/2011 10:30, Michael Stevens wrote:
Another succesful upgrade here, with comments below.
I'm going to have a go at this soon, any
chance someone who succeeds can
write it up?
My upgrade is now finished and all working thanks to Andy. Don't really have time just now to write up a
wiki, but basically I
followed the upgrade section in the release notes.
Various bitfolk specific things I'm aware of
Before starting:
- make sure you know how to access your console before you start (you
shouldn't need it, but if anything goes wrong you'll need it)
- optionally, ask support to take a snapshot before starting
- check before you upgrade that if you have root partition on
/dev/xvda1 that fdisk -l /dev/xvda works. If it doesn't you need your
xvda1 renaming to xvda, contact support.
Didn't encounter that problem.
At the point where the release notes tell you to
install a kernel then
udev and reboot:
- make sure grub-legacy is installed (or at least that grub2 is not
installed), as grub2 doesn't work at bitfolk yet and is likely to be
installed during the upgrade
grub2 is definitely installed, so don't allow it to write to your
partition (at some point in the upgrade you are asked to do that).
I had to switch back to grub-legacy before rebooting.
- use the linux-image-686-bigmem kernel; check
update-grub and/or
/boot/grub/menu.lst does point at the right kernel
Well, linux-image-2.6-xen-686 works also, and was offered by default in
the upgrade process:) I was able to switch back to a bigmem one.
- ensure grub kopts doesn't contain
clocksource=jiffies
After upgrade:
- check again that grub-legacy is there and menu.lst still defaults to
the correct bigmem kernel
I noticed that xen.independent_wallclock (set to 0 in /etc/sysctl.conf) was no
longer accessible after the upgrade.
/sys/devices/system/clocksource/clocksource0/current_clocksource
contains xen, so I am wondering if running ntpd now makes any sense?
Cheers.
--
Bernard Urban
9 Feb
9 Feb
7:53 a.m.
New subject: Lenny to Squeeze
I report successful upgrade too. Changed from xen to bigmem kernel.
MySQL upgrade was somewhat bumpy because of custom configuration,
which had some deprecated configuration paramaters.
Postgres server port has been changed, if you upgrade.
Otherwise all ran smoothly (no above-mentioned errors on dist-upgrade).
Now I have completely replaced obsolete software.
Cheers,
Taavi
On Wed, Feb 9, 2011 at 1:45 AM, <urb59(a)sfr.fr> wrote:
Joseph Heenan <joseph(a)heenan.me.uk> writes:
On 07/02/2011 10:30, Michael Stevens wrote:
Another succesful upgrade here, with comments below.
I'm going to have a go at this soon, any
chance someone who succeeds can
write it up?
My upgrade is now finished and all working thanks to Andy. Don't really have time just now to write up a
wiki, but basically I
followed the upgrade section in the release notes.
Various bitfolk specific things I'm aware of
Before starting:
- make sure you know how to access your console before you start (you
shouldn't need it, but if anything goes wrong you'll need it)
- optionally, ask support to take a snapshot before starting
- check before you upgrade that if you have root partition on
/dev/xvda1 that fdisk -l /dev/xvda works. If it doesn't you need your
xvda1 renaming to xvda, contact support.
Didn't encounter that problem.
At the point where the release notes tell you to
install a kernel then
udev and reboot:
- make sure grub-legacy is installed (or at least that grub2 is not
installed), as grub2 doesn't work at bitfolk yet and is likely to be
installed during the upgrade
grub2 is definitely installed, so don't allow it to write to your
partition (at some point in the upgrade you are asked to do that).
I had to switch back to grub-legacy before rebooting.
- use the linux-image-686-bigmem kernel; check
update-grub and/or
/boot/grub/menu.lst does point at the right kernel
Well, linux-image-2.6-xen-686 works also, and was offered by default in
the upgrade process:) I was able to switch back to a bigmem one.
- ensure grub kopts doesn't contain
clocksource=jiffies
After upgrade:
- check again that grub-legacy is there and menu.lst still defaults to
the correct bigmem kernel
I noticed that xen.independent_wallclock (set to 0 in /etc/sysctl.conf) was no
longer accessible after the upgrade.
/sys/devices/system/clocksource/clocksource0/current_clocksource
contains xen, so I am wondering if running ntpd now makes any sense?
Cheers.
--
Bernard Urban
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
3:13 p.m.
New subject: Lenny to Squeeze
Hi Bernard,
On Wed, Feb 09, 2011 at 12:45:32AM +0100, urb59(a)sfr.fr wrote:
How we've laid out the disks has changed several times over the last
3 years so some people will and some won't. Most customers installed
in the last 18 months have / directly on xvda (no partition table).
They won't experience this issue.
New customers have xvda partitioned and / on xvda1, and they also
won't see that problem.
It's only really customers from before this that had / on xvda1 but
with no actual xvda. Or even customers from a very long time ago
that have sda1 and no sda.
In any case I would recommend everyone boots and mounts things by
label or UUID. That is how we generally have set them up.
- check before
you upgrade that if you have root partition on
/dev/xvda1 that fdisk -l /dev/xvda works. If it doesn't you need your
xvda1 renaming to xvda, contact support.
Didn't encounter that problem. I noticed that xen.independent_wallclock (set to 0 in
/etc/sysctl.conf) was no
longer accessible after the upgrade.
/sys/devices/system/clocksource/clocksource0/current_clocksource
contains xen, so I am wondering if running ntpd now makes any sense?
On the -xen kernels, if xen.independent_wallclock is set to 0 (the
default without the sysctl we added) then you can't change your
system time. In that case time is supposed to be locked to that of
dom0 (host machine) and in theory you would not need to use ntp.
However, we found that there was often an offset or a drift which
could not be corrected because of xen.independent_wallclock being
set to 0.
So, we recommended it be set to 1 and everyone run ntp.
Under the new pvops kernels, xen.independent_wallclock doesn't exist
and you can change your time. I don't think it's meant to be locked
to that of the dom0, but even if it is I'd still recommend running
ntp.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
4838
days inactive
4840
days old
4 comments
5 participants
participants (5)
-
Andy Smith -
john lewis -
Joseph Heenan -
Taavi Ilves -
urb59＠sfr.fr