Tag Info

New answers tagged

1

We had a similar problem where one service checked via NRPE in a container returned an expected WARNING, then after some minutes the same service returned CRITICAL with the 141/SIGPIPE error. On the next check it returned WARNING then CRITICAL, then WARNING and so on. I performed a traffic capture for the error and found Nagios issue #305 to quite precisely ...


1

I've actually had this problem for a while myself. It looks like the ca-certificates package is damaged in the Ubuntu container template from the OpenVZ project. I got it working by purging the package and re-installing as per this answer: http://askubuntu.com/a/428152/134756 It worked out to this: sudo dpkg --purge --force-depends ca-certificates sudo ...


0

You have a dedicated server with OVH. By default these boot an OVH-provided kernel from the network, not the kernel installed on your server. You need to change the configuration of your server, in your OVH account management web pages, to boot from the hard drive.


0

/proc/partitions does not exist under OpenVZ. The container isn't a "true" Linux system, so a lot of things don't appear.


0

It's a little harsh, but the best way I've found to stop a stubborn container is to forcefully kill the container's processes. Command vzpid with grep makes it easy to find: ps ax | awk '{print $1}' | xargs vzpid | grep <container ID> | awk '{print $1}' | xargs kill -9 Now when you run a vzlist -a it should show the container as "stopped". Better ...



Top 50 recent answers are included