Hi, I am am using kitchen-dokken to do local chef cookbook testing, but I am getting an error ssh: Could not resolve hostname : Name or service not known I ran kitchen login via debug mode and got this. kitchen login --log-level=debug D Login command: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o LogLevel=VERBOSE -p 22 root@ (Options: {}) ssh: Could not resolve hostname : Name or service not known

Can anyone help with this? Tried to curl to https://localhost when I received this error. I setup nginx ssl as follows. # Listen on port 443 using SSL and make it the default server listen 443 default_server ssl; # Specify the path of your .crt and .key files ssl on; ssl_certificate /etc/ssl/private/localhost.crt; ssl_certificate_key /etc/ssl/private/localhost.key; # Enable session caching, increase session timeout ssl_session_cache shared:SSL:20m; ssl_session_timeout 60m; # Disable SSL in favor of TLS (safer) ssl_protocols TLSv1 TLSv1.1 TLSv1.2; $ curl https://localhost curl: (7) Failed to connect to localhost port 443: Connection refused

To install ansible keep this link handy along side this article http://docs.ansible.com/ansible/intro_installation.html For Redhat Install the EPEL repo, Extra Packages for Enterprise Linux $ sudo yum install wget $ wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm $ sudo yum install epel-release-latest-7.noarch.rpm Install ansible $ sudo yum install ansible $ ansible --version Additional Information Ansible is a Redhat company. There is a blog on installation, which show how to install using the source code as well. https://developers.redhat.com/blog/2016/08/15/install-ansible-on-rhel/

semanage(8) semanage(8) NAME semanage - SELinux Policy Management tool SYNOPSIS semanage {import,export,login,user,port,interface,module,node,fcon‐ text,boolean,permissive,dontaudit} ... positional arguments: import Import local customizations export Output local customizations login Manage login mappings between linux users and SELinux confined users user Manage SELinux confined users (Roles and levels for an SELinux user) port Manage network port type definitions interface Manage network interface type definitions module Manage SELinux policy modules node Manage network node type definitions fcontext Manage file context mapping definitions boolean Manage booleans to selectively enable functionality permissive Manage process type enforcement mode dontaudit Disable/Enable dontaudit rules in policy DESCRIPTION semanage is used to configure certain elements of SELinux policy with‐ out requiring modification to or recompilation from policy sources. This includes the mapping from Linux usernames to SELinux user identi‐ ties (which controls the initial security context assigned to Linux users when they login and bounds their authorized role set) as well as security context mappings for various kinds of objects, such as network ports, interfaces, and nodes (hosts) as well as the file context map‐ ping. Note that the semanage login command deals with the mapping from Linux usernames (logins) to SELinux user identities, while the semanage user command deals with the mapping from SELinux user identities to authorized role sets. In most cases, only the former mapping needs to be adjusted by the administrator; the latter is principally defined by the base policy and usually does not require modification. OPTIONS -h, --help List help information SEE ALSO selinux (8), semanage-boolean (8), semanage-dontaudit (8), semanage- export (8), semanage-fcontext (8), semanage-import (8), semanage-inter‐ face (8), semanage-login (8), semanage-module (8), semanage-node (8), semanage-permissive (8), semanage-port (8), semanage-user (8) AUTHOR This man page was written by Daniel Walsh <dwalsh@redhat.com> and Russell Coker <rcoker@redhat.com>. Examples by Thomas Bleher <ThomasBleher@gmx.de>. usage: semanage [-h] 20100223 semanage(8)

Hi, when I run the following, it errors, any help would be appreciated. $ packer build dev_ami.json My json looks like this: { "variables": { "aws_access_key": "", "aws_secret_key": "" }, "builders": [{ "type": "amazon-ebs", "access_key": "user `aws_access_key`", "secret_key": "user `aws_secret_key`", "region": "eu-west-1", "source_ami": "ami-ca0135b3", "instance_type": "t2.micro", "ssh_username": "ubuntu", "ami_name": "packer-dev-master timestamp | clean_ami_name" }] } Error: ==> Some builds didn't complete successfully and had errors: --> amazon-ebs: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

$ VBoxManage unregistervm myvm8 --delete VBoxManage: error: Cannot unregister the machine 'myvm8' while it is locked Hi all, I'm getting this trying to delete a VM, tried vagrant destroy as well.

Hi, I am getting this error when running my script. $ ./forloop.sh ./forloop.sh: line 10: [: =: unary operator expected #!/bin/bash for i in * do [ -d "$i" ] || continue Dirname="$i" echo $Dirname is a directory [ $i = rootfs ] && break done if [ $Dirname = rootfs ];then echo "Cannot continue processing rootfs found" fi

Hi, Can anybody help me, I'm getting this error when trying to run the following: $ systemd --version bash: systemd: command not found...

I have a wordpress installation and trying to get to http://localhost and it gives me this error: My wordpress config file is as follows: server { # Listen on all network interfaces on port 80 listen 80; # Listen on port 443 using SSL and make it the default server listen 443 default_server ssl; # Specify the path of your .crt and .key files ssl on; ssl_certificate /etc/ssl/private/localhost.crt; ssl_certificate_key /etc/ssl/private/localhost.key; # Enable session caching, increase session timeout ssl_session_cache shared:SSL:20m; ssl_session_timeout 60m; # Disable SSL in favor of TLS (safer) ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Specify the host name(s) that will match the site # The following value allows both www. and no subdomain server_name geeky; # Set the path of your WordPress files root /home/wordpress/www; # Automatically load index.php index index.php; # Saves client request body into files, cleaning up afterwards client_body_in_file_only clean; client_body_buffer_size 32K; # Allow uploaded files up to 300 megabytes client_max_body_size 300M; # Automatically close connections if no data is # transmitted to the client for a period of 10 seconds send_timeout 10s; # The rest of the configuration (location blocks) # is found below # The following applies to static files: # images, CSS, javascript location ~* ^.+.(jpg|jpeg|png|gif|ico|css|js)$ { access_log off; # Disable logging # Allow client browsers to cache files # for a long period of time expires 180d; } # The following applies to every request location / { # Try serving the requested URI: # - If the file does not exist, append / # - If the directory does not exist, # redirect to /index.php forwarding the request URI # and other request arguments try_files $uri $uri/ /index.php?q=$uri&$args; } # The following applies to every PHP file location ~ .php$ { # Ensure file really exists if (!-e $request_filename) { return 404; } # Pass the request to your PHP-FPM backend fastcgi_pass 127.0.0.1:9000; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME /home/wordpress/www$fastcgi_script_name; include fastcgi_params; } } The /var/log/nginx/error.log is empty. btw, https://localhost works fine.

This article makes assumptions that you know how to create an AWS instance, or have seen the AWS article on this site on how to create an instance. This is a monolithic install meaning all puppet components are install onto one server, the master, console, and puppet DB. Pre-reqs Ensure no previous puppet files are on the server if reinstalling. Ensure DNS or /etc/hosts is configured with right hostnames. Ensure port 3000 is open Ensure the OS/Architecture is the same for all components. The sudo installer does no support Defaults targetpw or Defaults rootw, comment them out in /etc/sudoers Import the puppet labs public GPG key $ wget -O - https://downloads.puppetlabs.com/puppetlabs-gpg-signing-key.pub | gpg --import Verify the fingerprint of the GPG key $ gpg --fingerprint 0x1054b7a24bd6ec30 Verify the signature of the tarball $ gpg --verify puppet-enterprise-<version>-<platform>.tar.gz.asc Extract the tarball, under /opt for example, in the extracted tarball you will see the installer file puppet-enterprise-install Create a puppet server answers file using the tarball # ./puppet-enterprise-install -s puppetserver.install.answers Install puppet master = y Install puppet DB and console = y Install the cloud provisioner = y Install cert unique name default = cnames Install postgres used by puppet = y Port 443 = default Admin Email = admin@yourdomain.com Password = Enter twice SMTP host = localhost Additional vendor packages = y Conveinient Links = y Edit the answers file # vi puppetserver.install.answers Change DNS name to AWS endpoint URL Append to Altname Install puppet using the answers file # ./puppet-enterprise-installer -a puppetserver.install.answers ..output.

I see this error when running. A new cloudformation template. An error occurred (ValidationError) when calling the CreateStack operation: Template format error: unsupported structure. I am running the following $ aws cloudformation create-stack --stack-name stack1 --template-body s3sample.json I have checked that the JSON is valid. Thanks.

I am getting this error while editing a node. sudo knife node edit trainer-vm ERROR: RuntimeError: Please set EDITOR environment variable. See https://docs.chef.io/knife_setup.html for details. Has anyone see this error?

WARNING: Ignoring APKINDEX.aee5641b.tar.gz: No such file or directory WARNING: Ignoring APKINDEX.cc30ea1d.tar.gz: No such file or directory I am seeing these kind of errors when trying out a docker example. My Dockerfile contains: cat Dockerfile FROM gliderlabs/alpine:latest RUN apk info docker build -t moothoot . Sending build context to Docker daemon 2.048kB Step 1/2 : FROM gliderlabs/alpine:latest ---> dd0abbe5ed7d Step 2/2 : RUN apk info ---> Running in 66626b61c2a8 musl busybox alpine-baselayout alpine-keys libressl2.5-libcrypto libressl2.5-libssl zlib apk-tools scanelf musl-utils libc-utils WARNING: Ignoring APKINDEX.aee5641b.tar.gz: No such file or directory WARNING: Ignoring APKINDEX.cc30ea1d.tar.gz: No such file or directory Removing intermediate container 66626b61c2a8 ---> ef3cc62b14a2 Successfully built ef3cc62b14a2 Successfully tagged moothoot:latest can anyone help?

Hi I am getting this warning on running an apply? $ kubectl apply -f kuard-pod.yml Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply

Hello, When I run the any kubectl command I get this error, it was working then it stopped all of a sudden. $ kubectl get error: yaml: line 9: mapping values are not allowed in this context $ kubectl get nodes error: yaml: line 9: mapping values are not allowed in this context

Add logging to HP-APA Edit /etc/rc.config.d/hp_apaconf Add the following: HP_APA_USE_SYSLOG=1

This can be useful to compare root and root mirror disks. # lifls -l /dev/rdsk/c1t0d0s2 volume ISL10 data size 7984 directory size 8 06/10/27 14:23:07 filename type start size implement created ================================================= ISL -12800 584 242 0 06/04/19 14:02:34 AUTO -12289 832 1 0 06/04/19 14:02:34 HPUX -12928 840 1024 0 06/04/19 14:02:34 PAD -12290 1864 1468 0 06/04/19 14:02:34 LABEL BIN 3336 8 0 07/11/14 13:19:23

Here is the contents of the EFI (Extensible Firmware Interface) directory, it's a data file not text. # efi_ls -d /dev/rdsk/c1t0d0s1 FileName Last Modified Size EFI/ 12/22/2007 STARTUP.NSH 12/22/2007296 total space 523251712 bytes, free space 519856128 bytes

To check the root boot path and root mirror path on hp-ux run the following command: # setboot Primary bootpath : 0/4/1/0.0.0.7.0 HA Alternate bootpath : 0/4/2/0 Alternate bootpath : 0/4/1/0.0.0.0.0