Greetings
I'm wondering whatever Bitfolk has made any preliminary plans in regards
to the still embargoed XSA-108 Xen security issue? If it turns out to be
something sufficiently bad, can we expect short notice patching-reboots?
Asking since at least both Amazon EC2 and Rackspace have scheduled
reboots, presumably XSA-108 related.
On that note, has Bitfolk made any attempts to get on the Xen
pre-disclosure list? I see that prgmr.com recently got added to it, and
they kind of appear to be in the same category as Bitfolk.
// Andreas
Hi guys,
I seem to be having a bit of trouble with my VPS at present...
It's CentOS 6.5, running ZPanel and Wordpress... That's it.
When I hit "Post" on a Wordpress post, the httpd falls over saying,
something like:
Out of memory: Kill process 11946 (httpd) score 28 or sacrifice child
Killed process 11946, UID 48, (httpd) total-vm:85420kB, anon-rss:6864kB,
file-rss:56kB
It has 480MiB RAM.
I can't understand why submitting a Wordpress post is making the httpd
use so much memory that it falls over.
Having to reboot the VPS each time I make a Wordpress post isn't ideal.
Has anyone seen anything like this before?
Hello, I'm trying to get to grips with IPv6 and have signed up for the
course at https://ipv6.he.net/certification/.
The next step is to be able to serve a page from my VPS. To check the IPv6
is configured OK I'm trying to ping the google IPv6 test host from my
(Ubuntu 14.04) VPS but it times out. Tracert6 output below.
To start with I'm using auto configuration in /etc/network/interfaces:
auto eth0
iface eth0 inet static
address 85.119.82.179
netmask 255.255.248.0
gateway 85.119.80.1
iface eth0 inet6 auto
I've echoed "1" to all the accept_ra / autoconf addresses.
I have
# ip -6 addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 2001:ba8:1f1:f379:455c:abb3:fd77:5e32/64 scope global temporary
dynamic
valid_lft 86272sec preferred_lft 14272sec
inet6 2001:ba8:1f1:f379:216:5eff:fe00:7db/64 scope global dynamic
valid_lft 86272sec preferred_lft 14272sec
inet6 fe80::216:5eff:fe00:7db/64 scope link
valid_lft forever preferred_lft forever
Where the network part of the inet6 address matches the address for my VPS
on the panel (although I've changed the host part for the email).
# ip6tables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all fe80::/10 anywhere
ACCEPT ipv6-icmp anywhere anywhere ipv6-icmp
router-advertisement
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT ipv6-icmp anywhere anywhere ipv6-icmp
router-solicitation
Extra info
# ip -6 route show dev eth0
2001:ba8:1f1:f379::/64 proto kernel metric 256 expires 86350sec
fe80::/64 proto kernel metric 256
default via fe80::fcff:ffff:feff:ffff proto ra metric 1024 expires
1750sec
# ip -6 neighbor show dev eth0
2001:ba8:1f1:f379::1 lladdr fe:ff:ff:ff:ff:ff router REACHABLE
fe80::fcff:ffff:feff:ffff lladdr fe:ff:ff:ff:ff:ff router REACHABLE
# tracert6 ipv6.google.com
traceroute to ipv6.l.google.com (2a00:1450:4013:c00::66) from
2001:ba8:1f1:f379:455c:abb3:fd77:5e32, 30 hops max, 60 bytes/packet
1 2001:ba8:1f1:f379::1 (2001:ba8:1f1:f379::1) 0.401 ms 0.292 ms 0.391
ms
2 * * *
3 * * *
4 * * *
5 * * *
etc.
Thank you for any pointers as to where to look.
Chris
