Ubuntu – /var/log/upstart/docker.log Boot2Docker – /var/log/docker.log Debian, GNU/Linux – /var/log/daemon.log CentOS6 – /var/log/daemon.log | grep docker Fedora – journalctl -u docker.service OpenSuSE – journalctl -u docker.service on Centos 7 journalctl -u docker.service nJoy 😉
After installing Docker on CentOS we need to Docker remote API port on CentOS. $ cat /etc/sysconfig/docker other_args="" Edit the file /etc/sysconfig/docker as below. other_args="-H tcp://0.0.0.0:4243 -H unix:///var/run/docker.sock" After that, restart docker and try to access the host from another host. $ sudo /etc/init.d/docker restart … $ curl $hostname:4243/images/json … For a systemd based Distro…
Assuming you have AWS cli installed : aws iam upload-server-certificate –server-certificate-name www.site.tld-cf –certificate-body file://public.key –private-key file://private.key –certificate-chain file://bundle.pem –path /cloudfront/ nJoy 😉
Basically it’s all over-engineered and does not work well. responses are out of alignment and though text-wise they are the same bit wise everything is all over the place : curl http://phpimpl.domain.com/testhex.php | xxd 00000000: de56 a735 4739 c01d f2dc e14b ba30 8af0 .Q.%G9…..;.0.. curl http://nodejs.domain.com/ | xxd 00000000: c39e 56c2 a725 4739 c380 c3ad…
openssl verify -verbose -x509_strict -CAfile gd_bundle-g2-g1.crt 39aaf24e9f2b1f6f.crt nJoy;-)
Sometimes you have a multi threaded / multi processed application and you need to see where are things hanging. ps auxw | grep sbin/apache | awk '{print"-p " $2}' | xargs strace nJoy 😉
You could add the sysctl line to the system or in the /etc/init.d/
Full access for specific IAM user/role Type: bucket { "Version":"2012-10-17", "Statement":[ { "Action":[ "s3:*" ], "Effect":"Allow", "Principal":{ "AWS":[ "arn:aws:iam::ACCOUNT_ID:user/USERNAME_A", "arn:aws:iam::ACCOUNT_ID:user/USERNAME_B", "arn:aws:iam::ACCOUNT_ID:user/USERNAME_C", "arn:aws:iam::ACCOUNT_ID:role/ROLE_A", "arn:aws:iam::ACCOUNT_ID:role/ROLE_B", "arn:aws:iam::ACCOUNT_ID:role/ROLE_C" ] }, "Resource":[ "arn:aws:s3:::BUCKET_NAME", "arn:aws:s3:::BUCKET_NAME/*" ] } ] }
Epel’s yum install does not cut it anymore at time of writing installing node.js causes a mass of 404s and file not found. current best approach : Enterprise Linux and Fedora Including Red Hat® Enterprise Linux® / RHEL, CentOS and Fedora. Node.js is available from the NodeSource Enterprise Linux and Fedora binary distributions repository….
This is a simple sample configuration for the impatient. Compress only a few types AddOutputFilterByType DEFLATE text/html text/plain text/xml The following configuration, while resulting in more compressed content, is also much more complicated. Do not use this unless you fully understand all the configuration details. Compress everything except images <Location /> # Insert filter SetOutputFilter…
