Hi Andy.
I'm asking this on the mailing list so it can benefit anyone else that
needs to know, but contact me directly if needed.
One of my customers had an issue with data protection recently (not
website or IT related) and have had to review everything (a right PITA!).
This covers me as I host the their website with a database of registered
users.
I understand you have access to my server, both to the file system, and
root on the server itself with the backup SSH key.
While I trust you and accept that you won't do anything malicious,
Could you give something "official" or update your DPA page covering any
access you have to the VPS and its associated data?
http://www.bitfolk.com/policy/dpa.html
Much appreciated.
--
Dee Earley (dee(a)earlsoft.co.uk)
irc: irc://irc.blitzed.org/
web: http://www.earlsoft.co.uk
phone: +44 (0)780 8369596
Hello,
I have just upgraded my VM from etch to lenny, and things look good overall.
One annoyance however is that on a reboot, the clock is ~30 mins in the
future and this is only fixed by a CRON @reboot job of "ntpdate", which
adjusts this correctly (offset -1935.350400 sec). However, this large
adjustment causes dovecot to kill itself.
On boot (via console) I can see :
..
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
..
Waiting for /dev to be fully populated...done.
Setting the system clock.
Unable to set System Clock to: Thu Jan 21 15:01:46 UTC 2010 (warning).
..
Setting the system clock.
Unable to set System Clock to: Thu Jan 21 15:01:49 UTC 2010 (warning).
Cleaning up ifupdown....
...
This is using lenny kernel 2.6.26-2-xen-686.
I tried setting "xen.independent_wallclock = 1" in /etc/sysctl.conf but this
does not make a difference.
hwclock --show
returns nothing.
Any idea why the clock needs such a large adjustment on reboot?
Cheers,
--
Alastair Sherringham
Hi,
If you're running Debian testing (squeeze) then you may have noticed
complaints from the install scripts of udev saying that your kernel
still has CONFIG_DEPRECATED_SYSFS enabled and you need to turn it
off before upgrading udev.
Don't force udev to be upgraded if this happens to you. It *will*
result in an unbootable system.
You can instead switch to the upstream kernel package which now has
support for running under Xen. The package you want is
linux-image-2.6.32-trunk-686-bigmem.
Before booting though, check some other things. Firstly, be sure
that you haven't upgraded to grub 2 (the current version of the
grub-pc package in testing is grub 2). The config format is not yet
supported by pygrub which BitFolk uses, so you would end up getting
the old kernel list from your /boot/grub/menu.lst. Instead make
sure you have grub-legacy for now. Run "update-grub" to see which
kernels it finds.
Next, the upstream kernels don't need the clocksource=jiffies kernel
command line any more either. In fact it can make things break. So
check in your menu.lst that that isn't there. Do an update-grub if
you changed anything.
After booting into 2.6.32-trunk-686-bigmem you can safely upgrade
udev.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
Hello,
The most common support request is to reset BitFolk account
password. I have therefore implemented a password reset feature to
the web panel at https://panle.bitfolk.com/.
It works as you would expect:
- Someone follows the "reset password" link on the login screen.
- They are invited to put in an account name. If the account exists
and reset is enabled for that account, then an email is generated
with an authorisation key in it. The email is sent to the email
address on record for that account.
The email also contains the IP address of the client that
requested the reset, together with their browser's user agent and
the time stamp.
- Following the link in the email within 12 hours will randomly
generate a new password. Nothing will happen if the link is not
followed.
When this was last discussed, there were a few people who didn't
like the idea of their passwords being able to be reset by email and
potentially being exposed to an attacker who already has control of
their email account. Therefore I have also added the option to
disable the feature.
I will put the feature live on Wednesday 27th January, so if you
don't like the idea of the above being possible please go to
https://panel.bitfolk.com/account/security/ and disable it.
In the near future I shall also add a third option for PGP encrypted
emails, which should allay most people's concerns about that
feature, but I am keen to get a basic version of this deployed
before the weekend of 6th February as I'll be at FOSDEM and support
will be emergencies only.
Clearly forms to change other personal details such as email
and postal addresses are also required, and also will be coming
soon.
On the security link above you will also find a password change
form for those who prefer a web page vs. logging in to the Xen Shell
and typing "passwd".
As always I'm keen to hear what people's priorities are for other
features to be added to the panel. I'm also open to ideas about
software for managing such feature requests, as RT probably isn't
best suited to it.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
"Whoever is responsible for this stunning design failure deserves continuous
cockpunches." -- jwz
Me again!
I'm slightly confused about one thing. Still trying to follow the
instructions here http://flurdy.com/docs/postfix.
I trying to get my head around a slight conflict. The server is
delivering email to /var/mail/virtual/graeme. Definitely arriving. But
my mail clients appear to be looking in a different directory,
/home/graeme/Maildir.
How does it move across? Am I missing something blindingly obvious?
Many thanks,
Graeme
Hi Bitfolks,
I've been using the very comprehensive instructions I found here
http://flurdy.com/docs/postfix/ to set up my shiny new VPS box. I
'think' I've got it mostly working now, but I'm not sure how to get my
box talking to the bitfolk central spamassassin box.
I realise I have to specify a username and the servername, but I don't
know the syntax. Could someone point me in the right direction? I assume
it's just a line in master.cf I need.
Many thanks,
Graeme
Hi,
Aside from the known issues with newer Ubuntu kernels not working on
the Xen hypervisor from Debian Lenny (which is what BitFolk uses),
there also appears to be a lack of compatibility between newer
releases of Ubuntu and older kernels:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/447747
This will leave you in the position of not being able to boot with
the supplied kernel and not being able to revert to a kernel from
Hardy or Lenny.
There may be a workaround, I'm not sure yet, but at the moment I
wouldn't recommend trying to do this unless you know you can make it
work (or know you can fix it from the rescue env.).
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
"I'd be happy to buy all variations of sex to ensure I got what I wanted."
-- Gary Coates (talking about cabling)
Hi everyone,
I could do with a bit of advice.
I've set up bind with the following in named.conf.local for each domain:
----------------------------------------------------------
zone "polyvisual.co.uk" {
type master;
file "/etc/bind/db.polyvisual.co.uk";
};
----------------------------------------------------------
and the following db file for each domain:
----------------------------------------------------------
;
; BIND data file for local loopback interface
;
$TTL 86400
@ SOA ns1.polyvisual.co.uk. hostmaster.polyvisual.co.uk. (
2 ; Serial
14400 ; Refresh (4 hrs)
900 ; Retry (15 mins)
1209600 ; Expire (2 weeks)
3600 ) ; Negative Cache TTL (1 hr)
NS ns1.polyvisual.co.uk.
NS a.authns.bitfolk.com.
NS b.authns.bitfolk.com.
NS c.authns.bitfolk.com.
MX 5 mail.polyvisual.co.uk.
A 212.13.195.149
ns1 A 212.13.195.149
www CNAME polyvisual.co.uk.
mail A 212.13.195.149
----------------------------------------------------------
To make things easy, if I wanted to just use ns1.polyvisual.co.uk as the
nameserver for each domain [rather than ns1.whateverthedomainis.co.uk]
should I change the SOA to ns1.polyvisual.co.uk in each of the db files
[leaving the domain name correct in the rest of the db file?]
Cheers,
Matt
I have just started working at a new office.
I just re-installed a windows box to have Lenny on it.
The box works fine.
I noticed that my SSH sessions to computers within the company were
hanging, then eventually timing out with a reset by peer message. It is
actually afecting all networking, that's just what made me realise that
the network sometimes "goes away".
No one else is having these problems.
To make progress I bought in my laptop and tried to use that, then
suddenly found the same issue.
I have plugged my laptop into a different port, one next to someone
elses workstation with no effect.
I have since been playing with things, looking through the internet and
playing with ping.
There are no entries in syslog/messages/dmesg about the NIC or network
stack at, or around, the time when the network "disappears".
Basically I lose all connectivity in terms of send/recv but ifconfig
reports that the adapter is up and working.
Both machines are running Lenny. My laptop has been stable for
aaaaaaages, has never had problems with wired ethernet on multiple
networks it's been hooked up to...and is even running a newer kernel to
get some fixes for the wifi driver (not used, I'm on wired ethernet here)
The box I just installed is a beast of a dell server and is using a
vanilla Lenny install from CD with only a base system + Gnome so far.
I have searched the interwebs and found the advice regarding tcp window
scaling, this does not get rid of the problem on my laptop.
I'm having a hard time finding anything that seems relevant to me.
If anyone has seen this, or has an idea where to look I'd appreciate it.
n
Hi,
At approximately 1106Z today, suite TFM1 in Telehouse lost power for
around 2 minutes. The only live BitFolk server in TFM1 at present
is dunkel.
Servers are set to not automatically start every VPS, as if they have
been rebooted it is usually for maintenance purposes. What should
have happened is that I should have been alerted, and then I would
have sorted things out.
A significant part of the internal monitoring is currently running
on a VPS on dunkel, but there is external monitoring for situations
such as this.
However, this has not worked and it wasn't until I received a phone
call on the urgent support number that I was aware of the problem.
As I type this, all VPSes on dunkel have now been restarted -- some
may still be fscking.
I am waiting on Telehouse for more information on the power outage
but obviously the real failing here is one of BitFolk's monitoring.
This is the second time there has been a monitoring failure; the
system had actually been changed since the first time, although that
was a different class of failure. I will be looking into why the
external monitoring failed, and changing how it's done if necessary.
In the meantime I will be adding a day of free service to all those
on dunkel who were affected.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
"I'd be happy to buy all variations of sex to ensure I got what I wanted."
-- Gary Coates (talking about cabling)
