Shailesh Sutar's questions

I am trying to install the Docker enterprise edition on CIS AMI of windows 2016 server using ansible. I am using PowerShell module for this installation. The code is as below for the docker installation task.

- name: Install Docker for windows.
  win_shell: >
    [Net.ServicePointManager]::SecurityProtocol = "tls12";
    Install-Module -Name DockerMsftProvider -confirm:$false -Force;
    Install-Package Docker -ProviderName DockerMsftProvider -confirm:$false –Force
  when: ecs_docker == True

This is inside CI-CD and code get executed on circleci docker image. Above task fails giving below message.

Install-Module : NuGet provider is required to interact with NuGet-based repositories.

To install Nuget package manager, I have included below task.

- name: Install Nuget repository.
  win_chocolatey:
    name: nugetpackagemanager
    state: present

Still message is same. Above task completes installation of Nuget package manager. There is another message which is as below.

Windows PowerShell is in NonInteractive mode. Read and \r\nPrompt functionality is not available

I added -force parameter as well for forceful installation of docker however it fails the build. I am building windows based docker images which I am going to host on this 2016 server.

We have windows servers that do application initialization which takes almost 3-4 hours for servers to be online. So to avoid downtime we use autoscaling group lifecycle hooks. Now we want to shut down all the servers at night and start them in the morning for cost optimization. Is it possible to run the PowerShell user-data script on the restart of the server? I followed link here however, cloud-init does not support Windows PowerShell user-data format as per this link.

Any suggestions would be a great help. Thank you.

I am using ssm login for logging into my windows server 2016 data center edition. When I make a RDP connection and run PowerShell from RDP, All the system environment variables are loded correctly however the same fails to load when using a aws ssm session. And I have to run command like below to load the variables.

$env:PATH=$env:PATH+';C:\Program Files\Amazon\AWSCLI\bin;C:\ProgramData\chocolatey\bin;C:\Program Files\Java\jre1.8.0_221\bin'

And it is weird that it sometimes load the variable and sometime it doesn't load the variables. Is there any way to load environment variables permanently for ssm session. Unfortunately, I couldn't generate the error now when I am posting this issue here but will update once I come across this issue again.

Hi I am able to get the desired output in my playbook below where I am using 2 tasks as follows aws-create-rds and aws-create-route53-record

---
# Playbook for creating aws rds instance and then creating route53 dns record.

- name: setup aws-rds-instances
  hosts: localhost
  roles:
     - aws-create-rds

task definition for the aws-create-rds is as below.

---

- name: create an rds instance
  rds:
    command: create
    aws_access_key: "{{ aws_create_rds.access_key }}"
    aws_secret_key: "{{ aws_create_rds.secret_key }}"
    db_name: "{{ aws_create_rds.db_name }}"
    instance_name: "{{ aws_create_rds.name }}"
    db_engine: "{{ aws_create_rds.db_engine }}"
    size: "{{ aws_create_rds.db_size }}"
    instance_type: "{{ aws_create_rds.instance_type }}"
    username: "{{ aws_create_rds.username }}"
    password: "{{ aws_create_rds.password }}"
    subnet: "{{ aws_create_rds.subnet }}"
    region: "{{ aws_create_rds.region }}"
    zone: "{{ aws_create_rds.zone }}"
    publicly_accessible: "{{ aws_create_rds.access }}"
    backup_retention: "{{ aws_create_rds.retention }}"
    vpc_security_groups: "{{ aws_create_rds.aws_sg_name }}"
    port: "{{ aws_create_rds.port }}"
    wait: yes
    wait_timeout: 900
    tags:
      created_by: ansible
  register: rds



 - name: Create a route53 record for RDS instance.
      route53:
        state: present
        aws_access_key: "{{ aws_create_route53_record.access_key }}"
        aws_secret_key: "{{ aws_create_route53_record.secret_key }}"
        zone: "{{ aws_create_route53_record.zone }}"
        hosted_zone_id: "{{ aws_create_route53_record.id }}"
        type:  "{{ aws_create_route53_record.type }}"
        value: "{{ rds.instance.endpoint }}"
        record: "{{  aws_create_route53_record.record }}"
        private_zone: "{{  aws_create_route53_record.private_zone }}"
        ttl: 30

Now since the there are 2 task in this task I want them to split into 2 different roles. 1st as aws-create-rds and 2nd as aws-create-route53-record I would want to use them as independent roles in ansible in future however I am not sure how I can pass endpoint value coming from aws-create-rds task and pass it to aws-create-route53-record and use it as value in route53 dns record. I've checked rds module documentation and there is no return value for endpoint in it. Also there are 2 use cases for this given as below.

 1. route53 record value can be passed through group_vars OR
 2. route53 record value can be passed from any previous ansible task executed.

I want to handle both the condition in aws-create-route53-record task. Any clue how this can be achieved. Environment variable or anything. Thanks in advance.

I want to use my cloudwatch logs which are basically website access logs. Need to use these cloudwatch logs for data analytics with kinesis stream since firehose and analytics service is not available in that region. Is there any way to get this done and store analyzed logs on s3 bucket as backup. a

Hi I am using git for a while now however I am new to enterprise git. here Is what I did with my test-repo I created a ssh key pair and added public key to my test repo as deploy key. Now I can clone my test-repo from ssh and https however when I add someone as collabrator they're able to clone repo from https but not from ssh

ssh-keygen -b 4096 -t rsa -f example_rsa -P "" -C ""

$ ls
example_rsa     example_rsa.pub

$ git clone [email protected]:star/test-repo.git
Cloning into 'test-repo'...
Warning: Permanently added the ECDSA host key for IP address '10.0.1.100' to the list of known hosts.
warning: You appear to have cloned an empty repository.

Same git repo can't be accessed by user even after granting access via ssh however user can git clone the repo using https.

git clone [email protected]:star/test-repo.git
Cloning into 'test-repo'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

git clone https://git.example-private.com/star/test-repo.git
Cloning into 'test-repo'...
warning: You appear to have cloned an empty repository.

I am running multiple unicorn processes on my production server. Now I want to check the individual service uptime of my services. For instance if any unicorn process restart automatically, it should start recording its uptime. By this means I want to calculate what is the uptime of the service since its last start/restart/reload Note: Here I am not talking about the server uptime which can be known by using uptime command like below.

$ uptime
 19:11:25 up 2 days, 21:28,  1 user,  load average: 0.11, 0.09, 0.11

I would like to know the uptime of individual service like uptime of nginx

Is it possible to know it somehow?

I have a production system on which there are multiple nginx apps hosted. those are nginx applications servers. Now for each of these nginx app servers a logrotate config file is configured in /etc/logrotate.d/ folder. one of the example of logrotate config file is given below.

/var/www/example/current/log/example.log {
  daily
  missingok
  rotate 1
  delaycompress
  compress
  notifempty
  copytruncate
}

I checked following Logrotate not working and checked my config and didn't find any duplicate entries for application servers or nginx as well. below is the definition of my nginx logrotate file.

/var/log/nginx/*.log {
    daily
    missingok
    rotate 3
  compress
  delaycompress
    notifempty
    create 0640 www-data adm
    sharedscripts
    postrotate
    if [ -s /var/run/nginx.pid ]; then
      kill -USR1 `cat /var/run/nginx.pid`
    fi
    endscript
}

My logs are still getting written in *.log.1 and not in *.log Can anyone help with this? I am trying to understand what is wrong here. Below is the logrotate command output in debug mode.

logrotate --force -d /etc/logrotate.d/nginx
reading config file /etc/logrotate.d/nginx

Handling 1 logs

rotating pattern: /var/log/nginx/*.log  forced from command line (3 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/nginx/access.log
  log does not need rotating
considering log /var/log/nginx/elasticsearch.access.log
  log does not need rotating
considering log /var/log/nginx/error.log
  log does not need rotating
considering log /var/log/nginx/grafana.access.log
  log does not need rotating
considering log /var/log/nginx/example-admin.access.log
  log needs rotating
considering log /var/log/nginx/example-admin.error.log
  log does not need rotating
considering log /var/log/nginx/example-administrators.access.log
  log needs rotating
considering log /var/log/nginx/example-administrators.error.log
  log does not need rotating
considering log /var/log/nginx/example-alot.access.log
  log does not need rotating
considering log /var/log/nginx/example-alot.error.log
  log does not need rotating
considering log /var/log/nginx/example-api_clients.access.log
  log does not need rotating
considering log /var/log/nginx/example-api_clients.error.log
  log does not need rotating
considering log /var/log/nginx/example-assets.access.log
  log does not need rotating
considering log /var/log/nginx/example-backgrounds.access.log
  log does not need rotating
considering log /var/log/nginx/example-backgrounds.error.log
  log does not need rotating
considering log /var/log/nginx/example-blog.access.log
  log does not need rotating
considering log /var/log/nginx/example-blog.error.log
  log does not need rotating
considering log /var/log/nginx/example-blog-service.access.log
  log does not need rotating
considering log /var/log/nginx/example-blog-service.error.log
  log does not need rotating
considering log /var/log/nginx/example-boards.access.log
  log does not need rotating
considering log /var/log/nginx/example-boards.error.log
  log does not need rotating
considering log /var/log/nginx/example-bolt.access.log
  log does not need rotating
considering log /var/log/nginx/example-bolt.error.log
  log does not need rotating
considering log /var/log/nginx/example-bonobo.access.log
  log does not need rotating
considering log /var/log/nginx/example-bonobo.error.log
  log does not need rotating
considering log /var/log/nginx/example-boss.access.log
  log does not need rotating
considering log /var/log/nginx/example-boss.error.log
  log does not need rotating
considering log /var/log/nginx/example-callbacks.access.log
  log does not need rotating
considering log /var/log/nginx/example-callbacks.error.log
  log does not need rotating
considering log /var/log/nginx/example-cashier.access.log
  log does not need rotating
considering log /var/log/nginx/example-cashier.error.log
  log does not need rotating
considering log /var/log/nginx/example-dashboard-old.access.log
  log does not need rotating
considering log /var/log/nginx/example-dcl_shipments.access.log
  log does not need rotating
considering log /var/log/nginx/example-dcl_shipments.error.log
  log does not need rotating
considering log /var/log/nginx/example-device-registry.access.log
  log does not need rotating
considering log /var/log/nginx/example-device-registry.error.log
  log does not need rotating
considering log /var/log/nginx/example-docs.access.log
  log does not need rotating
considering log /var/log/nginx/example-exports.access.log
  log does not need rotating
considering log /var/log/nginx/example-exports.error.log
  log does not need rotating
considering log /var/log/nginx/example-fake-api.access.log
  log does not need rotating
considering log /var/log/nginx/example-fake-api.error.log
  log does not need rotating
considering log /var/log/nginx/example-fashion-police.access.log
  log does not need rotating
considering log /var/log/nginx/example-fashion-police.error.log
  log does not need rotating
considering log /var/log/nginx/example-flight-recorder.access.log
  log does not need rotating
considering log /var/log/nginx/example-flight-recorder.error.log
  log does not need rotating
considering log /var/log/nginx/example-gone.access.log
  log does not need rotating
considering log /var/log/nginx/example-gone.error.log
  log does not need rotating
considering log /var/log/nginx/example-go-portal.access.log
  log does not need rotating
considering log /var/log/nginx/example-go-portal.error.log
  log does not need rotating
considering log /var/log/nginx/example-help-service.access.log
  log does not need rotating
considering log /var/log/nginx/example-help-service.error.log
  log does not need rotating
considering log /var/log/nginx/example-kfc.access.log
  log does not need rotating
considering log /var/log/nginx/example-kfc.error.log
  log does not need rotating
considering log /var/log/nginx/example-kredits.access.log
  log does not need rotating
considering log /var/log/nginx/example-kredits.error.log
  log does not need rotating
considering log /var/log/nginx/example-login.access.log
  log does not need rotating
considering log /var/log/nginx/example-login.error.log
  log does not need rotating
considering log /var/log/nginx/example-manual-activations.access.log
  log does not need rotating
considering log /var/log/nginx/example-manual-activations.error.log
  log does not need rotating
considering log /var/log/nginx/example-maps.access.log
  log does not need rotating
considering log /var/log/nginx/example-mobile-api.access.log
  log does not need rotating
considering log /var/log/nginx/example-mobile-api.error.log
  log does not need rotating
considering log /var/log/nginx/example-mqttproxy.access.log
  log does not need rotating
considering log /var/log/nginx/example-mqttproxy.error.log
  log does not need rotating
considering log /var/log/nginx/example-network-coverage.access.log
  log does not need rotating
considering log /var/log/nginx/example-network-coverage.error.log
  log does not need rotating
considering log /var/log/nginx/example-package_tracker.access.log
  log does not need rotating
considering log /var/log/nginx/example-package_tracker.error.log
  log does not need rotating
considering log /var/log/nginx/example-people.access.log
  log needs rotating
considering log /var/log/nginx/example-people.error.log
  log does not need rotating
considering log /var/log/nginx/example-postman-pat.access.log
  log does not need rotating
considering log /var/log/nginx/example-postman-pat.error.log
  log does not need rotating
considering log /var/log/nginx/example-premium.access.log
  log does not need rotating
considering log /var/log/nginx/example-premium.error.log
  log does not need rotating
considering log /var/log/nginx/example-push-notifications.access.log
  log does not need rotating
considering log /var/log/nginx/example-push-notifications.error.log
  log does not need rotating
considering log /var/log/nginx/example-referrific.access.log
  log does not need rotating
considering log /var/log/nginx/example-referrific.error.log
  log does not need rotating
considering log /var/log/nginx/example-services.access.log
  log does not need rotating
considering log /var/log/nginx/example-services.error.log
  log does not need rotating
considering log /var/log/nginx/example-store.access.log
  log does not need rotating
considering log /var/log/nginx/example-store.error.log
  log does not need rotating
considering log /var/log/nginx/example-subs.access.log
  log does not need rotating
considering log /var/log/nginx/example-subs.error.log
  log does not need rotating
considering log /var/log/nginx/example-updates.access.log
  log does not need rotating
considering log /var/log/nginx/example-updates.error.log
  log does not need rotating
considering log /var/log/nginx/example-website.access.log
  log does not need rotating
considering log /var/log/nginx/example-wildcard-redirect.access.log
  log does not need rotating
considering log /var/log/nginx/example-zendesk-proxy.access.log
  log does not need rotating
considering log /var/log/nginx/example-zendesk-proxy.error.log
  log does not need rotating
considering log /var/log/nginx/kibana.access.log
  log does not need rotating
considering log /var/log/nginx/prometheus.access.log
  log does not need rotating
considering log /var/log/nginx/prometheus_alertmanager.access.log
  log does not need rotating
considering log /var/log/nginx/prometheus_statsd_bridge.access.log
  log does not need rotating
rotating log /var/log/nginx/example-admin.access.log, log->rotateCount is 3
dateext suffix '-20170104'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
compressing log with: /bin/gzip
renaming /var/log/nginx/example-admin.access.log.3.gz to /var/log/nginx/example-admin.access.log.4.gz (rotatecount 3, logstart 1, i 3), 
renaming /var/log/nginx/example-admin.access.log.2.gz to /var/log/nginx/example-admin.access.log.3.gz (rotatecount 3, logstart 1, i 2), 
renaming /var/log/nginx/example-admin.access.log.1.gz to /var/log/nginx/example-admin.access.log.2.gz (rotatecount 3, logstart 1, i 1), 
renaming /var/log/nginx/example-admin.access.log.0.gz to /var/log/nginx/example-admin.access.log.1.gz (rotatecount 3, logstart 1, i 0), 
rotating log /var/log/nginx/example-administrators.access.log, log->rotateCount is 3
dateext suffix '-20170104'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
compressing log with: /bin/gzip
renaming /var/log/nginx/example-administrators.access.log.3.gz to /var/log/nginx/example-administrators.access.log.4.gz (rotatecount 3, logstart 1, i 3), 
renaming /var/log/nginx/example-administrators.access.log.2.gz to /var/log/nginx/example-administrators.access.log.3.gz (rotatecount 3, logstart 1, i 2), 
renaming /var/log/nginx/example-administrators.access.log.1.gz to /var/log/nginx/example-administrators.access.log.2.gz (rotatecount 3, logstart 1, i 1), 
renaming /var/log/nginx/example-administrators.access.log.0.gz to /var/log/nginx/example-administrators.access.log.1.gz (rotatecount 3, logstart 1, i 0), 
rotating log /var/log/nginx/example-people.access.log, log->rotateCount is 3
dateext suffix '-20170104'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
compressing log with: /bin/gzip
renaming /var/log/nginx/example-people.access.log.3.gz to /var/log/nginx/example-people.access.log.4.gz (rotatecount 3, logstart 1, i 3), 
renaming /var/log/nginx/example-people.access.log.2.gz to /var/log/nginx/example-people.access.log.3.gz (rotatecount 3, logstart 1, i 2), 
renaming /var/log/nginx/example-people.access.log.1.gz to /var/log/nginx/example-people.access.log.2.gz (rotatecount 3, logstart 1, i 1), 
renaming /var/log/nginx/example-people.access.log.0.gz to /var/log/nginx/example-people.access.log.1.gz (rotatecount 3, logstart 1, i 0), 
renaming /var/log/nginx/example-admin.access.log to /var/log/nginx/example-admin.access.log.1
creating new /var/log/nginx/example-admin.access.log mode = 0640 uid = 33 gid = 4
renaming /var/log/nginx/example-administrators.access.log to /var/log/nginx/example-administrators.access.log.1
creating new /var/log/nginx/example-administrators.access.log mode = 0640 uid = 33 gid = 4
renaming /var/log/nginx/example-people.access.log to /var/log/nginx/example-people.access.log.1
creating new /var/log/nginx/example-people.access.log mode = 0640 uid = 33 gid = 4
running postrotate script
running script with arg /var/log/nginx/*.log : "
    if [ -s /var/run/nginx.pid ]; then
      kill -USR1 `cat /var/run/nginx.pid`
    fi
"
removing old log /var/log/nginx/example-admin.access.log.4.gz
error: error opening /var/log/nginx/example-admin.access.log.4.gz: No such file or directory

And when i do force logrotate, I end up having errors below.

sudo logrotate -f /etc/logrotate.conf
logrotate_script: 2: logrotate_script: /etc/init.d/example-admin: not found
error: error running non-shared postrotate script for /var/www/admin/current/log/example-admin.log of '/var/www/admin/current/log/example-admin.log '
logrotate_script: 2: logrotate_script: /etc/init.d/example-administrators: not found
error: error running non-shared postrotate script for /var/www/administrators/current/log/example-administrators.log of '/var/www/administrators/current/log/example-administrators.log '
logrotate_script: 2: logrotate_script: /etc/init.d/example-alot: not found
error: error running non-shared postrotate script for /var/www/alot/current/log/example-alot.log of '/var/www/alot/current/log/example-alot.log '
logrotate_script: 2: logrotate_script: /etc/init.d/example-bonobo: not found
error: error running non-shared postrotate script for /var/www/bonobo/current/log/example-bonobo.log of '/var/www/bonobo/current/log/example-bonobo.log '
logrotate_script: 2: logrotate_script: /etc/init.d/example-cashier: not found
error: error running non-shared postrotate script for /var/www/cashier/current/log/example-cashier.log of '/var/www/cashier/current/log/example-cashier.log '
logrotate_script: 2: logrotate_script: /etc/init.d/example-dcl-shipments: not found
error: error running non-shared postrotate script for /var/www/dcl_shipments/current/log/example-dcl_shipments.log of '/var/www/dcl_shipments/current/log/example-dcl_shipments.log '
logrotate_script: 2: logrotate_script: /etc/init.d/example-people: not found
error: error running non-shared postrotate script for /var/www/people/current/log/example-people.log of '/var/www/people/current/log/example-people.log '
logrotate_script: 2: logrotate_script: /etc/init.d/example-store: not found
error: error running non-shared postrotate script for /var/www/store/current/log/example-store.log of '/var/www/store/current/log/example-store.log '
logrotate_script: 2: logrotate_script: /etc/init.d/example-storefront: not found
error: error running non-shared postrotate script for /var/www/storefront/current/log/example-storefront.log of '/var/www/storefront/current/log/example-storefront.log '
logrotate_script: 2: logrotate_script: /etc/init.d/example-subs: not found
error: error running non-shared postrotate script for /var/www/subs/current/log/example-subs.log of '/var/www/subs/current/log/example-subs.log '

Below is the logrotate command ouput in debug mode.

sudo logrotate -dv /etc/logrotate.d/example-alot
reading config file /etc/logrotate.d/example-alot

Handling 1 logs

rotating pattern: /var/www/alot/current/log/example-alot.log  after 1 days (1 rotations)
empty log files are not rotated, old logs are removed
considering log /var/www/alot/current/log/example-alot.log
  log needs rotating
rotating log /var/www/alot/current/log/example-alot.log, log->rotateCount is 1
dateext suffix '-20170105'
glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
compressing log with: /bin/gzip
renaming /var/www/alot/current/log/example-alot.log.1.gz to /var/www/alot/current/log/example-alot.log.2.gz (rotatecount 1, logstart 1, i 1),
renaming /var/www/alot/current/log/example-alot.log.0.gz to /var/www/alot/current/log/example-alot.log.1.gz (rotatecount 1, logstart 1, i 0),
copying /var/www/alot/current/log/example-alot.log to /var/www/alot/current/log/example-alot.log.1
truncating /var/www/alot/current/log/example-alot.log
running postrotate script
running script with arg /var/www/alot/current/log/example-alot.log: "
      echo "Appending to" example-alot > /var/www/alot/current/log/example-alot.log
      /etc/init.d/example-alot reload >> /dev/null
"
removing old log /var/www/alot/current/log/example-alot.log.2.gz


sudo logrotate -dv /etc/logrotate.d/example-subs
reading config file /etc/logrotate.d/example-subs

Handling 1 logs

rotating pattern: /var/www/subs/current/log/example-subs.log  after 1 days (1 rotations)
empty log files are not rotated, old logs are removed
considering log /var/www/subs/current/log/example-subs.log
  log does not need rotating

I am using chef for provisioning a vpn-server in my infrastructure. Below is the code which is used to install few components of libreswan-ipsec vpn.

%w( libnss3-dev libnspr4-dev pkg-config libpam0g-dev libcap-ng-dev
    libcap-ng-utils libselinux1-dev libcurl4-nss-dev libgmp3-dev
    flex bison gcc make libunbound-dev libnss3-tools wget vim traceroute ).each do |pkg|
      package pkg do
        action :install
      end
    end

Now I need to add more components to this list for installation however I need to install them to after all above components are install. Below is the code for those 2 packages for installations.

%w( libevent-dev xmlto ).each do |pkg|
      package pkg do
        action :install
      end
    end

But when I run recipe it takes all of them together and installs and breaks things on server on debian package manager. Basically all I want is to fix the installation flow cause when I install those packages manually, it works. how can i achieve this? Below is log of package manager which is broken now.

[2016-12-26T15:59:11+00:00] INFO: Starting Chef Run for ip-10-0-10-19
[2016-12-26T15:59:11+00:00] INFO: Running start handlers
[2016-12-26T15:59:11+00:00] INFO: Start handlers complete.
[2016-12-26T15:59:11+00:00] INFO: Application light-weight resource already initialized -- overriding!
[2016-12-26T15:59:11+00:00] INFO: Preparing removal of dependency: dpkg landscape-common
[2016-12-26T15:59:11+00:00] INFO: Preparing removal of dependency: dpkg landscape-client
[2016-12-26T15:59:11+00:00] INFO: Preparing removal of dependency: dpkg popularity-contest
[2016-12-26T15:59:11+00:00] INFO: Preparing installation of dependency: dpkg htop
[2016-12-26T15:59:11+00:00] INFO: Preparing installation of dependency: dpkg lynx
[2016-12-26T15:59:11+00:00] INFO: Preparing installation of dependency: dpkg vim-nox
[2016-12-26T15:59:11+00:00] INFO: Preparing installation of dependency: dpkg git
[2016-12-26T15:59:11+00:00] INFO: Preparing installation of dependency: dpkg curl
[2016-12-26T15:59:11+00:00] INFO: Preparing installation of dependency: dpkg libcurl3-dev
[2016-12-26T15:59:11+00:00] INFO: Preparing installation of dependency: dpkg tree
[2016-12-26T15:59:11+00:00] INFO: Preparing installation of dependency: dpkg screen
[2016-12-26T15:59:11+00:00] INFO: Preparing installation of dependency: dpkg traceroute
[2016-12-26T15:59:12+00:00] INFO: Preparing installation of dependency: dpkg libpq-dev
[2016-12-26T15:59:12+00:00] INFO: Preparing installation of dependency: gem bundler
[2016-12-26T15:59:12+00:00] INFO: Preparing installation of dependency: gem ruby-shadow
[2016-12-26T15:59:12+00:00] INFO: Preparing installation of dependency: gem pg
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for service[postfix] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous service[postfix]: /var/chef/vendor/cookbooks/postfix/recipes/default.rb:30:in `from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  service[postfix]: /var/chef/vendor/cookbooks/postfix/recipes/default.rb:63:in `from_file'
[2016-12-26T15:59:12+00:00] WARN: require_recipe is deprecated and will be removed in a future release, please use include_recipe
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for group[sudo] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous group[sudo]: /var/chef/vendor/cookbooks/user/recipes/data_bag.rb:46:in `block (2 levels) in from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  group[sudo]: /var/chef/vendor/cookbooks/user/recipes/data_bag.rb:46:in `block (2 levels) in from_file'
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for group[sudo] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous group[sudo]: /var/chef/vendor/cookbooks/user/recipes/data_bag.rb:46:in `block (2 levels) in from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  group[sudo]: /var/chef/vendor/cookbooks/user/recipes/data_bag.rb:46:in `block (2 levels) in from_file'
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for group[sudo] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous group[sudo]: /var/chef/vendor/cookbooks/user/recipes/data_bag.rb:46:in `block (2 levels) in from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  group[sudo]: /var/chef/vendor/cookbooks/user/recipes/data_bag.rb:46:in `block (2 levels) in from_file'
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for group[sudo] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous group[sudo]: /var/chef/vendor/cookbooks/user/recipes/data_bag.rb:46:in `block (2 levels) in from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  group[sudo]: /var/chef/vendor/cookbooks/user/recipes/data_bag.rb:46:in `block (2 levels) in from_file'
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for group[sudo] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous group[sudo]: /var/chef/vendor/cookbooks/user/recipes/data_bag.rb:46:in `block (2 levels) in from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  group[sudo]: /var/chef/vendor/cookbooks/user/recipes/data_bag.rb:46:in `block (2 levels) in from_file'
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for group[sudo] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous group[sudo]: /var/chef/vendor/cookbooks/user/recipes/data_bag.rb:46:in `block (2 levels) in from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  group[sudo]: /var/chef/vendor/cookbooks/user/recipes/data_bag.rb:46:in `block (2 levels) in from_file'
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for group[sudo] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous group[sudo]: /var/chef/vendor/cookbooks/user/recipes/data_bag.rb:46:in `block (2 levels) in from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  group[sudo]: /var/chef/vendor/cookbooks/user/recipes/data_bag.rb:46:in `block (2 levels) in from_file'
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for package[vim-nox] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous package[vim-nox]: /var/chef/cookbooks/initial_setup/recipes/install_packages.rb:3:in `block in from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  package[vim-nox]: /var/chef/cookbooks/vim/recipes/default.rb:29:in `from_file'
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for directory[/etc/logstash] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous directory[/etc/logstash]: /var/chef/cookbooks/logstash/recipes/default.rb:24:in `from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  directory[/etc/logstash]: /var/chef/cookbooks/logstash/definitions/logstash_file.rb:8:in `block in from_file'
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for service[logstash] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous service[logstash]: /var/chef/cookbooks/logstash/definitions/logstash_file.rb:3:in `block in from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  service[logstash]: /var/chef/cookbooks/logstash/recipes/shipper.rb:18:in `from_file'
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for package[wget] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous package[wget]: /var/chef/cookbooks/newrelic/recipes/default.rb:1:in `from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  package[wget]: /var/chef/cookbooks/ipsec/recipes/default.rb:18:in `block in from_file'
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for package[traceroute] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous package[traceroute]: /var/chef/cookbooks/initial_setup/recipes/install_packages.rb:3:in `block in from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  package[traceroute]: /var/chef/cookbooks/ipsec/recipes/default.rb:18:in `block in from_file'
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for service[ipsec] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous service[ipsec]: /var/chef/cookbooks/ipsec/recipes/default.rb:9:in `from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  service[ipsec]: /var/chef/cookbooks/karma_ipsec/recipes/default.rb:4:in `from_file'
[2016-12-26T15:59:12+00:00] INFO: ohai plugins will be at: /etc/chef/ohai_plugins
[2016-12-26T15:59:12+00:00] INFO: Processing remote_directory[/etc/chef/ohai_plugins] action create (ohai::default line 30)
[2016-12-26T15:59:12+00:00] INFO: Processing cookbook_file[/etc/chef/ohai_plugins/README] action create (dynamically defined)
[2016-12-26T15:59:12+00:00] INFO: Processing ohai[custom_plugins] action reload (ohai::default line 44)
[2016-12-26T15:59:12+00:00] INFO: ohai[custom_plugins] reloaded
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for service[nginx] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous service[nginx]: /var/chef/vendor/cookbooks/nginx/recipes/default.rb:42:in `from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  service[nginx]: /var/chef/vendor/cookbooks/nginx/recipes/default.rb:54:in `from_file'
[2016-12-26T15:59:12+00:00] WARN: Cloning resource attributes for service[nginx] from prior resource (CHEF-3694)
[2016-12-26T15:59:12+00:00] WARN: Previous service[nginx]: /var/chef/vendor/cookbooks/nginx/recipes/default.rb:54:in `from_file'
[2016-12-26T15:59:12+00:00] WARN: Current  service[nginx]: /var/chef/cookbooks/karma_dante/recipes/default.rb:17:in `from_file'
[2016-12-26T15:59:12+00:00] INFO: Processing execute[apt-get-update] action run (apt::default line 22)
[2016-12-26T15:59:12+00:00] INFO: Processing execute[apt-get update] action nothing (apt::default line 29)
[2016-12-26T15:59:12+00:00] INFO: Processing execute[apt-get autoremove] action nothing (apt::default line 36)
[2016-12-26T15:59:12+00:00] INFO: Processing execute[apt-get autoclean] action nothing (apt::default line 42)
[2016-12-26T15:59:12+00:00] INFO: Processing package[update-notifier-common] action install (apt::default line 48)
[2016-12-26T15:59:12+00:00] INFO: Processing execute[apt-get-update-periodic] action run (apt::default line 52)
[2016-12-26T15:59:12+00:00] INFO: Processing directory[/var/cache/local] action create (apt::default line 62)
[2016-12-26T15:59:12+00:00] INFO: Processing directory[/var/cache/local/preseeding] action create (apt::default line 62)
[2016-12-26T15:59:12+00:00] INFO: Processing package[landscape-common] action purge (initial_setup::remove_packages line 3)
[2016-12-26T15:59:12+00:00] INFO: Processing package[landscape-client] action purge (initial_setup::remove_packages line 3)
[2016-12-26T15:59:12+00:00] INFO: Processing package[popularity-contest] action purge (initial_setup::remove_packages line 3)
[2016-12-26T15:59:12+00:00] INFO: Processing package[htop] action install (initial_setup::install_packages line 3)
[2016-12-26T15:59:12+00:00] INFO: Processing package[lynx] action install (initial_setup::install_packages line 3)
[2016-12-26T15:59:12+00:00] INFO: Processing package[vim-nox] action install (initial_setup::install_packages line 3)
[2016-12-26T15:59:12+00:00] INFO: Processing package[git] action install (initial_setup::install_packages line 3)
[2016-12-26T15:59:12+00:00] INFO: Processing package[curl] action install (initial_setup::install_packages line 3)
[2016-12-26T15:59:12+00:00] INFO: Processing package[libcurl3-dev] action install (initial_setup::install_packages line 3)
[2016-12-26T15:59:13+00:00] INFO: package[libcurl3-dev] is a virtual package, actually acting on package[libcurl4-openssl-dev]

================================================================================
Error executing action `install` on resource 'package[libcurl3-dev]'
================================================================================

Chef::Exceptions::Exec
----------------------
apt-get -q -y install libcurl3-dev returned 100, expected 0

Resource Declaration:
---------------------
# In /var/chef/cookbooks/initial_setup/recipes/install_packages.rb

  3:   package pkg do
  4:     action :install
  5:   end
  6: end

Compiled Resource:
------------------
# Declared in /var/chef/cookbooks/initial_setup/recipes/install_packages.rb:3:in `block in from_file'

package("libcurl3-dev") do
  action [:install]
  retries 0
  retry_delay 2
  package_name "libcurl3-dev"
  version "7.35.0-1ubuntu2.10"
  cookbook_name :initial_setup
  recipe_name "install_packages"
end

[2016-12-26T15:59:15+00:00] ERROR: Running exception handlers
[2016-12-26T15:59:15+00:00] ERROR: Exception handlers complete
[2016-12-26T15:59:15+00:00] FATAL: Stacktrace dumped to /var/cache/chef-solo/chef-stacktrace.out
[2016-12-26T15:59:15+00:00] FATAL: Chef::Exceptions::Exec: package[libcurl3-dev] (initial_setup::install_packages line 3) had an error: Chef::Exceptions::Exec: apt-get -q -y install libcurl3-dev returned 100, expected 0
ssutar@i-production-base:~$ sudo apt-get -q -y install libcurl3-dev 
Reading package lists...
Building dependency tree...
Reading state information...
libcurl4-openssl-dev is already the newest version.
The following package was automatically installed and is no longer required:
  libcurl3-nss
Use 'apt-get autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 96 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up dante-server (1.4.1-1) ...
Starting Dante SOCKS daemon: invoke-rc.d: initscript danted, action "start" failed.
dpkg: error processing package dante-server (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 dante-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
ssutar@i-production-base:~$ sudo apt-get autoremove
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  libcurl3-nss
0 upgraded, 0 newly installed, 1 to remove and 96 not upgraded.
1 not fully installed or removed.
After this operation, 563 kB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 97703 files and directories currently installed.)
Removing libcurl3-nss:amd64 (7.35.0-1ubuntu2.10) ...
Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
Setting up dante-server (1.4.1-1) ...
Starting Dante SOCKS daemon: invoke-rc.d: initscript danted, action "start" failed.
dpkg: error processing package dante-server (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 dante-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
ssutar@i-production-base:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 96 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up dante-server (1.4.1-1) ...
Starting Dante SOCKS daemon: invoke-rc.d: initscript danted, action "start" failed.
dpkg: error processing package dante-server (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 dante-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have deployed SSL certificates on various websites however this wildcard SSL certificate is totally new to me. I have question that If I am buying a SSL certificate *.example-private.com, Will it work for *.staging.example-private.com Or Do I have to buy a different wild card SSL for staging site. I am going to implement this on new sites.

My server's inode usage has gone up to 100% due to which I am not able to uninstall extra linux-kernel-headers and linux-kernel-images

$ df -i
Filesystem     Inodes  IUsed  IFree IUse% Mounted on
/dev/xvda1     524288 523970    318  100% /
none           481856      2 481854    1% /sys/fs/cgroup
udev           480561    396 480165    1% /dev
tmpfs          481856    317 481539    1% /run
none           481856      1 481855    1% /run/lock
none           481856      1 481855    1% /run/shm
none           481856      3 481853    1% /run/user
/dev/xvdb      262144     11 262133    1% /mnt

Also HDD usage are up to only 78%

$ sudo df -kh
Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1      7.8G  5.7G  1.7G  78% /
none            4.0K     0  4.0K   0% /sys/fs/cgroup
udev            1.9G   12K  1.9G   1% /dev
tmpfs           377M  368K  377M   1% /run
none            5.0M     0  5.0M   0% /run/lock
none            1.9G     0  1.9G   0% /run/shm
none            100M     0  100M   0% /run/user
/dev/xvdb       3.9G  8.1M  3.7G   1% /mnt

When I try to remove headers and images using sudo apt-get autoremove command, It gives me below error.

$ sudo apt-get autoremove
Reading package lists... Done
Building dependency tree       
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 linux-headers-3.13.0-83-generic : Depends: linux-headers-3.13.0-83 but it is not installed
E: Unmet dependencies. Try using -f.

When I do sudo apt-get -f install, It gives me below error.

dpkg: error processing archive /var/cache/apt/archives/linux-headers-3.13.0-83_3.13.0-83.127_all.deb (--unpack):
 unable to create `/usr/src/linux-headers-3.13.0-83/arch/sh/include/asm/sparsemem.h.dpkg-new' (while processing `./usr/src/linux-headers-3.13.0-83/arch/sh/include/asm/sparsemem.h'): No space left on device
No apport report written because the error message indicates a disk full error
                                                                              dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/linux-headers-3.13.0-83_3.13.0-83.127_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

When I do $ sudo dpkg --configure -a, It gives me below error.

    libpostfix-dns.so.1 -> libpostfix-dns.so.1.0.1
/sbin/ldconfig.real: Can't create temporary cache file /etc/ld.so.cache~: No space left on device
dpkg: error processing package libc-bin (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: error: unable to create new file '/var/lib/dpkg/status-new': No space left on device

Now I am not sure how to tackle this issue. Any experts advice would be a great input. I am not sure from where should I start deleting files. Here is description of filesystem.

/$ sudo du -sh *
9.6M    bin
418M    boot
12K dev
6.9M    etc
216K    home
0   initrd.img
0   initrd.img.old
789M    lib
4.0K    lib64
16K lost+found
4.0K    media
28K mnt
684M    opt
du: cannot access ‘proc/21817/task/21817/fd/4’: No such file or directory
du: cannot access ‘proc/21817/task/21817/fdinfo/4’: No such file or directory
du: cannot access ‘proc/21817/fd/4’: No such file or directory
du: cannot access ‘proc/21817/fdinfo/4’: No such file or directory
0   proc
23M root
372K    run
9.4M    sbin
4.0K    srv
0   sys
19M tmp
2.9G    usr
669M    var
0   vmlinuz
0   vmlinuz.old

Note: I have already deleted log files older than 20 days. It didn't help to minimise inode usage and I am stuck now.

I have installed nginx,php7.0-fpm and mysql on my ubuntu 16.04 server. Everything works fine however It doesn't load a setup page of phpmyadmin. Below is my phpmyadmin nginx block.

location /phpmyadmin {
        root /usr/share/;
            index index.php index.html index.htm;
            location ~ ^/phpmyadmin/(.+\.php)$ {
                try_files $uri =404;
                #fastcgi_pass 127.0.0.1:9000;   
                fastcgi_pass unix:/run/php/php7.0-fpm.sock;
            include fastcgi_params;
            }
    }

Below are my nginx access logs

/usr/share# tail -f /var/log/nginx/access.log 
127.0.0.1 - - [15/Oct/2016:17:13:06 +0530] "GET /phpmyadmin/setup/index.php HTTP/1.1" 200 31 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
127.0.0.1 - - [15/Oct/2016:17:13:06 +0530] "GET /phpmyadmin/setup/index.php HTTP/1.1" 200 31 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
127.0.0.1 - - [15/Oct/2016:17:13:41 +0530] "GET /phpmyadmin/setup/index.php HTTP/1.1" 200 31 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
127.0.0.1 - - [15/Oct/2016:17:13:44 +0530] "GET /phpmyadmin/setup/index.php HTTP/1.1" 200 31 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
127.0.0.1 - - [15/Oct/2016:17:13:46 +0530] "GET /phpmyadmin/setup/index.php HTTP/1.1" 200 31 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
127.0.0.1 - - [15/Oct/2016:17:13:46 +0530] "GET /phpmyadmin/setup/index.php HTTP/1.1" 200 31 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
127.0.0.1 - - [15/Oct/2016:17:13:47 +0530] "GET /phpmyadmin/setup/index.php HTTP/1.1" 200 31 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
127.0.0.1 - - [15/Oct/2016:17:13:47 +0530] "GET /phpmyadmin/setup/index.php HTTP/1.1" 200 31 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
127.0.0.1 - - [15/Oct/2016:17:21:26 +0530] "GET /phpmyadmin/setup/index.php HTTP/1.1" 200 31 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"
127.0.0.1 - - [15/Oct/2016:17:21:28 +0530] "GET /phpmyadmin/setup/index.php HTTP/1.1" 200 31 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0"

I do not have anything in nginx error log. php7.0-fpm is also running normally below is the log extract of the same.

 tail -f /var/log/php7.0-fpm.log 
[15-Oct-2016 17:09:48] NOTICE: fpm is running, pid 17062
[15-Oct-2016 17:09:48] NOTICE: ready to handle connections
[15-Oct-2016 17:09:48] NOTICE: systemd monitor interval set to 10000ms
[15-Oct-2016 17:21:10] NOTICE: Terminating ...
[15-Oct-2016 17:21:10] NOTICE: exiting, bye-bye!
[15-Oct-2016 17:21:11] NOTICE: configuration file /etc/php/7.0/fpm/php-fpm.conf test is successful

[15-Oct-2016 17:21:11] NOTICE: fpm is running, pid 17297
[15-Oct-2016 17:21:11] NOTICE: ready to handle connections
[15-Oct-2016 17:21:11] NOTICE: systemd monitor interval set to 10000ms

I need expert advice on this as I tried to change php-fpm listen mode from localhost port 9000 to php.sock. Same can observed in phpmyadmin nginx block config.

I am new to nomad. We are using nomad in production along with docker, consul, vault, ansible. When I run a nomad job from my local machine, Job registers successfully but show status as dead.

Roadrunner-2:nomad Shailesh$ nomad run -detach -address=http://nomad.example-private.com:4646 production/router.hcl 
Job registration successful
Evaluation ID: c9e77cb5-ef69-1c63-e926-f131b331d800

When I do nomad status

Roadrunner-2:nomad Shailesh$ nomad status
ID        Type     Priority  Status
metrics   system   50        running
registry  service  50        running
router    system   50        dead

And particularly when I check status of the job it gives error.

Roadrunner-2:nomad Shailesh$ nomad status router
ID          = router
Name        = router
Type        = system
Priority    = 50
Datacenters = us-east-1
Status      = dead
Periodic    = false
Error querying job summary: Unexpected response code: 404 (job not found)

I would highly appreciate any direction for troubleshooting above. Thanks

Recently apple has imposed IPv6 support as mandatory for all its vendors who use its mobile-api and aws vpc doesn't provide IPv6 support. How can I achieve this. I have checked https://aws.amazon.com/blogs/aws/elastic-load-balancing-ipv6-zone-apex-support-additional-security/ however I am not sure what to do.

I would need expert advise here.

I am working on chef and vagrant. I am trying to configure nginx with php-fpm and spin-up new server using chef-solo. Here is the configuration of my vagrant file.

Vagrant.configure(2) do |config|
  config.vm.box = "ubuntu-15.10"
  config.vm.box_url = 'https://cloud-images.ubuntu.com/vagrant/wily/current/wily-server-cloudimg-amd64-vagrant-disk1.box'

  config.vm.network "private_network", ip: "182.217.46.65"
  config.vm.provision :chef_solo do |chef|
    chef.run_list = [
      "recipe[nginx-php-fpm]"
    ]
  end

When I run vagrant up everything runs perfect but nginx do not install and in stacktrace of vagrant instance I get below exceptions.

Chef::Exceptions::CookbookNotFound: Cookbook nginx not found. If you're loading nginx from another cookbook, make sure you configure the dependency in your metadata
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/cookbook/cookbook_collection.rb:38:in `block in initialize'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/ohai-8.10.0/lib/ohai/mash.rb:77:in `yield'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/ohai-8.10.0/lib/ohai/mash.rb:77:in `default'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/ohai-8.10.0/lib/ohai/mash.rb:77:in `default'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/run_context/cookbook_compiler.rb:275:in `[]'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/run_context/cookbook_compiler.rb:275:in `each_cookbook_dep'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/run_context/cookbook_compiler.rb:254:in `add_cookbook_with_deps'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/run_context/cookbook_compiler.rb:255:in `block in add_cookbook_with_deps'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/run_context/cookbook_compiler.rb:276:in `each'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/run_context/cookbook_compiler.rb:276:in `each_cookbook_dep'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/run_context/cookbook_compiler.rb:254:in `add_cookbook_with_deps'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/run_context/cookbook_compiler.rb:88:in `block in cookbook_order'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/run_context/cookbook_compiler.rb:86:in `each'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/run_context/cookbook_compiler.rb:86:in `cookbook_order'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/run_context/cookbook_compiler.rb:98:in `compile_libraries'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/run_context/cookbook_compiler.rb:71:in `compile'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/run_context.rb:167:in `load'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/policy_builder/expand_node_object.rb:93:in `setup_run_context'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/client.rb:509:in `setup_run_context'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/client.rb:277:in `run'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/application.rb:270:in `block in fork_chef_client'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/application.rb:258:in `fork'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/application.rb:258:in `fork_chef_client'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/application.rb:223:in `block in run_chef_client'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/local_mode.rb:44:in `with_server_connectivity'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/application.rb:211:in `run_chef_client'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/application/solo.rb:297:in `block in interval_run_chef_client'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/application/solo.rb:286:in `loop'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/application/solo.rb:286:in `interval_run_chef_client'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/application/solo.rb:265:in `run_application'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/application.rb:58:in `run'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/bin/chef-solo:25:in `<top (required)>'
/usr/bin/chef-solo:50:in `load'
/usr/bin/chef-solo:50:in `<main>'

While nginx is already defined as dependency in my metadata.rb file. I got these errors in /var/chef/cache/chef-stacktrace.out of vagrant instance. I would highly appreciate any help for where to look in.

Thanks

I have installed Icinga for monitoring my azure infrastructure. I want to monitor my DB Servers using python script which is here

Now it is making connection to DB server but mode options are not working properly.

giving error which is below.

 ./check_mssql_server.py -H some-host -p 1433  -U some-user -P some-password --bufferhitratio -w 95: -c 90:
Traceback (most recent call last):
  File "./check_mssql_server.py", line 469, in <module>
    main()
  File "./check_mssql_server.py", line 435, in main
    execute_query(mssql, options, host)
  File "./check_mssql_server.py", line 448, in execute_query
    mssql_query.do(mssql)
  File "./check_mssql_server.py", line 285, in do
    self.calculate_result()
  File "./check_mssql_server.py", line 294, in calculate_result
    if self.query_result[1] != 0:
IndexError: list index out of range

Here is the output of the connection it is making on the same command.

./check_mssql_server.py -H some-host -p 1433  -U some-user -P some-password
OK: Time to connect was 0.262902975082s|time=0.262902975082s;;;;

I am not a python expert. I would highly appreciate any suggestions here.

Hi I have Elastic Load Balancer on which I've deployed my ssl certificates and when i check on the web it say site is vulnerable because of SSLv3 is enabled on the site. So my question is What exactly needs to be done in my environment so that it stops reporting about POODLE Vulnerablity.

I do know that i need to make changes in

/etc/httpd/conf.d/ssl.conf on line "SSLProtocol All -SSLv2 -SSLv3"

I would highly appreciate any comment from experts.

Thank you.

My Ec2 instance configured with apache2 was running fine and all of a sudden web-server stopped serving pages. I checked all the logs but it didn't help or may i am missing something here. Below are the error logs of apache2

[Mon Jan 12 18:15:49 2015] [error] [client 76.164.202.114] PHP Notice:  Undefined index: categoryname in /data/html/judaism.php on line 11
[Mon Jan 12 18:15:49 2015] [error] [client 76.164.202.114] PHP Notice:  Undefined index: title in /data/html/judaism.php on line 18
[Mon Jan 12 18:16:29 2015] [error] [client 114.124.39.172] PHP Notice:  Undefined variable: link in /data/html/article_emailconfig.php on line 37
[Mon Jan 12 18:16:29 2015] [error] [client 114.124.39.172] PHP Notice:  Undefined variable: link in /data/html/article_emailconfig.php on line 37
[Mon Jan 12 18:16:46 2015] [error] [client 5.44.217.87] File does not exist: /data/html/old
[Mon Jan 12 18:16:56 2015] [error] [client 114.124.39.172] PHP Notice:  Undefined variable: link in /data/html/article_emailconfig.php on line 37
[Mon Jan 12 18:16:56 2015] [error] [client 114.124.39.172] PHP Notice:  Undefined index: urlid in /data/html/friend.php on line 67
[Mon Jan 12 18:16:56 2015] [error] [client 114.124.39.172] PHP Notice:  Undefined variable: link in /data/html/article_emailconfig.php on line 37
[Mon Jan 12 18:17:27 2015] [error] [client 188.165.15.117] PHP Notice:  Undefined index: categoryname in /data/html/judaism.php on line 11
[Mon Jan 12 18:17:27 2015] [error] [client 188.165.15.117] PHP Notice:  Undefined index: title in /data/html/judaism.php on line 18
[Mon Jan 12 18:17:36 2015] [error] [client 120.40.144.203] PHP Notice:  Undefined index: categoryname in /data/html/judaism.php on line 11
[Mon Jan 12 18:17:36 2015] [error] [client 120.40.144.203] PHP Notice:  Undefined index: title in /data/html/judaism.php on line 18
[Mon Jan 12 18:17:39 2015] [error] [client 12.218.42.6] PHP Notice:  Undefined index: categoryname in /data/html/judaism.php on line 11, referer: http://search.pch.com/frontpagesearch?q=shovavim
[Mon Jan 12 18:17:39 2015] [error] [client 12.218.42.6] PHP Notice:  Undefined index: title in /data/html/judaism.php on line 18, referer: http://search.pch.com/frontpagesearch?q=shovavim
[Mon Jan 12 18:17:45 2015] [error] [client 66.249.67.27] script '/data/html/go.php' not found or unable to stat
[Mon Jan 12 18:17:57 2015] [error] [client 46.165.222.7] PHP Notice:  Undefined index: categoryname in /data/html/judaism.php on line 11
[Mon Jan 12 18:17:57 2015] [error] [client 46.165.222.7] PHP Notice:  Undefined index: title in /data/html/judaism.php on line 18
[Mon Jan 12 18:18:31 2015] [error] [client 66.249.67.35] script '/data/html/go.php' not found or unable to stat
[Mon Jan 12 18:18:36 2015] [error] [client 171.113.243.6] PHP Notice:  Undefined index: categoryname in /data/html/judaism.php on line 11
[Mon Jan 12 18:18:36 2015] [error] [client 171.113.243.6] PHP Notice:  Undefined index: title in /data/html/judaism.php on line 18
[Mon Jan 12 19:05:14 2015] [notice] caught SIGTERM, shutting down
[Mon Jan 12 19:05:33 2015] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.14 with Suhosin-Patch configured -- resuming normal operations
[Mon Jan 12 19:05:33 2015] [error] [client 87.253.132.202] script '/data/html/virtualjerusalem_rss.php' not found or unable to stat
[Mon Jan 12 19:05:33 2015] [error] [client 87.253.132.202] script '/data/html/virtualjerusalem_rss.php' not found or unable to stat
[Mon Jan 12 19:05:51 2015] [error] [client 66.249.67.27] script '/data/html/food/MOVED/Soup_minestrone.php' not found or unable to stat
[Mon Jan 12 19:06:09 2015] [error] [client 87.253.132.203] script '/data/html/virtualjerusalem_rss.php' not found or unable to stat
[Mon Jan 12 19:06:10 2015] [error] [client 87.253.132.203] script '/data/html/virtualjerusalem_rss.php' not found or unable to stat
[Mon Jan 12 19:06:10 2015] [error] [client 66.249.67.133] script '/data/html/virtualjerusalem_rss.php' not found or unable to stat

I have lost logs of almost 45-47 Minutes. Can someone help me with this?

I am working on PsExec but i get error as "Access Denied " Firewall is disabled on both machine. Ports are also open at both machine.

C:\PSTOOLS>PsExec \\192.168.1.232 -u Administrator "c:\test\sample.bat Shailesh"

PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com

Password:

Couldn't access 192.168.1.232:
Access is denied.

I am developing a shell script which actually stops aws running instances in a particular region & start them again as a part of schedule maintenance. but as ec2-api tools are heavy, takes time to execute the ec2 command. I want my system to hold up till the last ec2 command executes entirely and show its O/P. Like if i am executing

ec2-stop-instances some-id --region us-west-1

It should wait for completion of execution of ec2-stop. I didn't find any solution for this hence posting here.

Let me know if any one have any idea about how it should be done.