Bartek's questions

I am running an Arch Linux box and have setup a Python 3.4 virtualenv.

I have a uwsgi vassal being run by the emperor, which specifies the following ini: (some snipped for brevity)

[uwsgi]
virtualenv = /opt/lib/virtualenvs/bartek
socket = /tmp/bartek.sock
module = app
callable = app
plugins = python

When I run this and view the uwsgi log file, I consistently get this:

uwsgi socket 0 bound to UNIX address /tmp/bartek.sock fd 3
Python version: 3.4.1 (default, May 19 2014, 17:23:49)  [GCC 4.9.0 20140507 (prerelease)]
Set PythonHome to /opt/lib/virtualenvs/bartek
Fatal Python error: Py_Initialize: Unable to get the locale encoding
ImportError: No module named 'encodings'

This seems to be potentially related to the virtualenv? When I remove virtualenv from uwsgi config, it fails on missing packages instead of complaining about this encoding. I'd prefer to keep using a virtualenv, though!

Any ideas?

I have an Ubuntu Server I'm adding some interfaces for and I can't figure out what I am be missing.

Here's my /etc/network/interfaces/

auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
    address 10.100.60.54
    netmask 255.255.0.0
    network 10.100.0.0
    broadcast 10.100.255.255
    gateway 10.100.0.1

 iface eth0:0 inet static
    address 10.100.60.71
    netmask 255.255.0.0
    gateway 10.100.0.1

Then the following occurs:

sudo ifup eth0:0
RTNETLINK answers: File exists
Failed to bring up eth0:0.

Looked around for this issue and everyone seems to encounter it in different ways. Any ideas?

In what seemed to be a random occurrence, a site went down tonight and after taking a look at the Apache error logs it was this issue:

 (13)Permission denied: mod_wsgi (pid=2751): Unable to connect to WSGI daemon process 'mysite.com-ssl' on '/var/run/apache2/wsgi.2579.0.2.sock' after multiple attempts.

Now I read the ConfigurationIssues wiki for mod_wsgi, and the fix seems reasonable. Couldn't write to that directory so an alternative must be specified with WSGISocketPrefix

So I set:

WSGISocketPrefix /var/run/wsgi

It fixes the issue, and the site can load up after an Apache restart.

However, I'm very curious - Why did this dirctory stop being available for write? Am I missing something? The /var/run/apache2 directory is owned by root:root, but the new sockets that now run under /var/run/wsgi*.sock are www-data:root .. There was a server reboot, but that's it. Maybe something now takes over permissions on that directory on boot?

Any ideas? Thanks!

Your Linode, linodeXXXXX, has exceeded the notification threshold (1000) for disk io rate by averaging 1079.99 for the last 2 hours.

That's what I've been getting in my email for the past week, about 2-3 a day. I tried a few solutions, including finding other ServerFault posts on this issue, but they are not helping.

For example, I tried:

watch -n 1 "(ps aux | awk '\$8 ~ /D/  { print \$0 }')"

At various intervals, this will populate with an nginx process, or a kjournald process, etc but only for a few seconds. So it doesn't really help in figuring out what's causing it, it just tells me I keep getting high i/o.

Thus, the question becomes How can I identify what is causing this high i/o usage? Ideally, without starting at a process list for 6 hours.

Quick question but Gooling has not revealed an answer. When I do iptables -L, it seems to lag on displaying items in where I have limited the source to internal ips 192.168.0.0/24

The whole listing takes about 30 seconds to display.

I just want to know: Does this affect the speed of my incoming connections or is this simply a side effect of having all these ranges within my iptables rules?

Thanks!