I've been putting this off, but really should get it done (yes I know 12.04LTS
isn't far off). Partly this is due to wanting to support IPv6 on the server
better (Apache isn't happy).
Is it safe to do an in place upgrade now (I remember it didn't alway go
smoothly early on) or would a clean install be better (OK, likely always better
in some ways, but if I can do an in place now and think about a clean install
for 12.04 later that would be easier - hopefully!).
--
Paul Tansom | Aptanet Ltd. | http://www.aptanet.com/ | 023 9238 0001
Registered in England | Company No: 4905028 | Registered Office:
Crawford House, Hambledon Road, Denmead, Waterlooville, Hants, PO7 6NU
Does CTRL+L (force a redraw) help?
--
Deanna Earley
----- Reply message -----
From: "Mathew Newton" <bitfolklist(a)newtonnet.co.uk>
Date: Mon, Jan 16, 2012 09:44
Subject: [bitfolk] Lenny-to-Squeeze Upgrade Plan - 2nd opinions sought!
To: <users(a)lists.bitfolk.com>
Hi Ian,
On Sun, January 15, 2012 8:59 pm, Ian wrote:
> 4. Doing the upgrade via the console had an issue with some of the alert
> boxes ('you've made changes to this file - do you want to keep them or
> install the package maintainer's version' sort of thing) staying on
> screen. Towards the end, I had one viewable line of text.
That's interesting - I see that all the time in the console and assumed it
was something to do with the configuration at my end (accessing via
Putty).
For normal scrolling text I don't have any problems with the console,
however when editing in-situ e.g. with nano/emacs the screen often starts
to freeze and the effective text window decreases until I have no choice
but to disconnect and try again.
It is little more than a pain at the moment, however I was planning an
Lenny-to-Squeeze upgrade and am concerned now as I really don't want any
issues like this mid way.
Has anyone else seen this and/or got any ideas how to resolve it?
Mathew
P.S. I could probably take a video of the problem if it helps show what
the issue is...
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
Hi,
Today we discovered that the ability to specify a custom kickstart
URL when doing a CentOS or Scientific Linux install was broken. It
just used the default kickstart anyway.
It's now fixed, so if you had tried to do that in the past and
failed, it wasn't your fault - apologies.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
Hi everyone,
I thought I'd post this here in case any responses might be useful for the
archives should anyone else come across similar...
Following a recent IPv4 numbering update I removed my old IPv4 address
today and shutdown/boot(ed) my VPS from the console. I noticed a few
warnings/errors in the boot log which I don't recall having seen before:
Setting the system clock.
Unable to set System Clock to: Sat Jan 14 16:11:03 UTC 2012 (warning).
[... non-related output removed ...]
Not activating swap on swapfile. (warning).
[... non-related output removed ...]
Will now check root file system:fsck 1.41.3 (12-Oct-2008)
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0 /dev/xvda
/ primary superblock features different from backup, check forced.
/: ***** REBOOT LINUX *****
/: 138212/1310720 files (10.2% non-contiguous), 3340623/5242880 blocks
fsck died with exit status 3
failed!
The file system check corrected errors on the root partition but requested
that the system be restarted. failed!
The system will be restarted in 5 seconds. (warning).
Will now restart.
[ 126.850328] xenbus_dev_shutdown: device/console/0: Initialising !=
Connected, skipping
[ 127.413907] Restarting system.
I recently increased the size of my VPS disk storage (successfully) and so
I'm wondering if the fsck check was as a result of that? The subsequent
boot completed successfully so I'm not overly concerned... or should I be?
Any thoughts about the system clock setting failure and not activating the
swapfile?
Mathew
Hello,
Effective immediately our base data transfer quota is increasing
from 100GB/month to 200GB/month. All existing accounts have had
100GB extra data transfer quota added to their current quota.
If you were paying for additional data transfer quota over and above
100GB then you may now be paying for more than you need. If that is
the case then please contact support to ask for what you don't need
to be removed (down to a minimum of 200GB) before your next payment
is due.
Also, the overage charge has been reduced from £0.75 per GB to £0.25
per GB. It is still *much* cheaper to commit to additional data
transfer than to go into overage[1].
If you have any questions, just reply, or open a support ticket.
All prices exclude VAT.
Cheers,
Andy
[1] Committing to an extra 10GB/month is £0.50. Using 10GB of
overage will now be £2.50.
--
"I never wanted to be a comedian. When I was very young I wanted to be a
writer […] But then, at the age of 16, I saw a comedian called Ted
Chippington open for The Fall in Birmingham in October 1984 and
literature's loss became stand-up comedy's loss also." — Stewart Lee
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
Hello,
As you may be aware, we operate a referral scheme:
http://bitfolk.com/referrals.html
For a long time there has been an open feature request for
panel.bitfolk.com to display a list of referrals:
https://tools.bitfolk.com/redmine/issues/9
There is a potential privacy concern since any such list will reveal
some amount of information about one customer to another, but I find
it difficult to quantify as there has been little feedback.
I've therefore decided that a reasonable amount of information to
reveal to a referrer would be:
* New customer's account name
* Referral amount
* New customer's payment schedule (monthly / quarterly / yearly)
* The date the new customer's service started, and whether they are
still a customer or not.
I have updated our privacy policy to this effect, and intend to put
this feature live in not less than 30 days (Saturday 11th February
2012 or later).
If you can't remember who (if anyone) referred you to us, go to:
https://panel.bitfolk.com/account/
If you were referred by anyone then it will now say:
You were referred to us by <account>.
in the "Referrals" section of the page, under "Billing". If there's
nothing there then this does not affect you.
If you have strong feelings about your referrer seeing this
information then I would encourage you to leave feedback in redmine
(your usual BitFolk credentials) so we can try to come to a
consensus over what is appropriate.
If we can't come to a consensus that you're happy with then you can
of course ask support to remove the referral.
So, provided this does not prove controversial, this email is your
30 day notice of a modification to our privacy policy:
http://bitfolk.com/policy/dpa.html
Disclosure of personal information
[...]
If you nominate an existing customer as a referrer then you give
consent for some details regarding your account with us to be
disclosed to your referrer. You can find full information about
this in our referral scheme. If you would prefer that these
details were not disclosed, do not nominate a referrer.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
Hello,
Starting around 2339Z and still ongoing, we experienced network
instability. High latency, high packet loss, occasional complete
lack of connectivity. I am currently in contact with our transit
provider to investigate and will provide more info when I have it.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
Hi all,
I have just flatenered my VPS install and installed debian wheezy. Upon
first boot I found out that my / partion was only mounting as read-only.
Found this in the logs;
> Starting NFS common utilities: statd[ 17.998558] blkfront: barrier:
>> empty write xvda op failed
>
> [ 17.998573] blkfront: xvda: barrier or flush: disabled
>
> [ 18.079912] end_request: I/O error, dev xvda, sector 9968016
>
> [ 18.079933] end_request: I/O error, dev xvda, sector 9968016
>
> [ 18.079946] Buffer I/O error on device xvda1, logical block 1245746
>
> [ 18.079954] lost page write due to I/O error on xvda1
>
> [ 18.080006] Aborting journal on device xvda1.
>
> [ 18.084929] journal commit I/O error
>
> [ 18.085021] EXT3-fs (xvda1): error: ext3_journal_start_sb: Detected
>> aborted journal
>
> [ 18.085033] EXT3-fs (xvda1): error: remounting filesystem read-only
>
>
After a quick google search [1]. For it to mount as rw you need to disable
barrier by setting "barrier=0" in fstab options.
Just for a reference incase anyone finds this to be a problem.
Happy New Year,
Thanks,
Neil
[1] -
http://xen.1045712.n5.nabble.com/xvda-I-O-errors-in-linux-3-1-under-XCP-1-0…
Hello,
It would be nice to meet up for some drinks in London before
Christmas. If you'd be up for that, please help pick a date:
http://doodle.com/adpr6eznzam43cfv
I'll close it probably in the next day or two and then we'll pick a
venue.
Cheers,
Andy