Chockomonkey's questions

I've ran the initial replication process over LAN multiple times with these exact two servers.

When I start the initial replication, typically I see my network adapters get floored with sending at like 500-600 mbps, and receiving the same on the replica server.

For reasons unknown to me, and the purpose of my question here, is that for some reason when I started a new initial replication a couple nights ago, the speed which it was transmitting the initial replica was bouncing between 50 and 60 mbps. Is there something I've missed or accidently enabled which is capping this?

Both Hypervisors are running Windows Server 2008 R2.

Thanks for any insight you can give me!

I've seen other posts say that either file permissions or the lack of an index directive are the cause. However, my Flask application does not have an index file at all, and most of the site works like a charm.

nginx.conf

server {
    listen      80;
    server_name localhost;
    charset     utf-8;
    client_max_body_size 5M;
    root /srv/www/cc/app;

    location / { 
        try_files $uri $uri/ @cc; 
    }
    location /uploads/ {
#       root /srv/www/cc/app;
        expires max;
    }
    location /static/ {
#       root /srv/www/cc/app;
        expires max;
    }
    location @cc {
        include uwsgi_params;
        uwsgi_pass unix:/tmp/uwsgi.sock;
    }
}

snippet from views.py

@app.route('/', methods = ['GET'])
def client():

    return render_template("/client/index.html")


#-----------------CLIENT ABOVE, ADMIN BELOW------------------#


@app.route('/admin/', methods = ['GET'])
@login_required
def admin():

    submissions = Campaign.query.all()

    return render_template("admin.html",
        title = 'Admin',
        submissions = submissions)

So I basically have a single views.py with a ton of routes. All the ones which are /admin/ work like a charm, but the one which is just /, doesn't.

As I said, I do not have an index. I tried setting the index directive in nginx.conf to "app" as that's where the magic happens... but no dice.

Here's my file structure:

/cc/
    app/
        __init__.py
        views.py
        etc
        uploads/
        static/
    config.py

From the nginx logs:

directory index of "/srv/www/cc/app/" is forbidden

I've found similar issues from other folks online and I've verified that nginx runs with user www-data, and that this use is owner of the directory.

Where do Docker containers get their time information? I've created some containers from the basic ubuntu:trusty image, and when I run it and request 'date', I get UTC time.

For awhile I got around this by doing the following in my Dockerfile:

RUN sudo echo "America/Los_Angeles" > /etc/timezone

However, for some reason that stopped working. Searching online I saw the below suggested:

docker run -v /etc/timezone:/etc/timezone [image-name]

Both these methods correctly set the timezone though!

$ cat /etc/timezone
America/Los_Angeles
$ date
Tue Apr 14 23:46:51 UTC 2015

Anyone know what gives?

I have a Ubuntu VM that I'm turning into a web server. I don't want this on the domain so it doesn't automatically get a DNS entry.

As such I've created one for it in the Forward Lookup Zone, but alas it only sometimes works. Half the time I ping the machine by name it will work. Then I'll come into work the next morning and find that the DNS lookup is no longer working.

Anyone have any ideas why this might be?

I tried nslookup:

>nslookup cc
5.1.168.192.in-addr.arpa
    primary name server = localhost
    responsible mail addr = nobody.invalid
    serial = 1
    refresh = 600 (10 mins)
    retry = 1200 (20 mins)
    expire = 604800 (7 days)
    default TTL = 10800 (3 hours)
Server: UnKnown
Address: 192.168.1.5

Name: cc.AD1.local
Address: 192.168.1.66

>ping cc
Ping request could not find host cc. Please check the name and try again.