@mountaing thanks for the help! sorry should have looked closer.

@giraffelife Also the following way using pip $ sudo easy_install pip $ sudo pip install ansible

@hawksbill Help on individual commands: $ semanage login -h usage: semanage login [-h] [-n] [-N] [-S STORE] [ --add -s SEUSER -r RANGE LOGIN | --delete LOGIN | --deleteall | --extract | --list -C | --modify -s SEUSER -r RANGE LOGIN ] positional arguments: login login_name | %groupname optional arguments: -h, --help show this help message and exit -C, --locallist List login local customizations -n, --noheading Do not print heading when listing login object types -N, --noreload Do not reload policy after commit -S STORE, --store STORE Select an alternate SELinux Policy Store to manage -r RANGE, --range RANGE MLS/MCS Security Range (MLS/MCS Systems only) SELinux Range for SELinux login mapping defaults to the SELinux user record range. -a, --add Add a record of the login object type -d, --delete Delete a record of the login object type -m, --modify Modify a record of the login object type -l, --list List records of the login object type -E, --extract Extract customizable commands, for use within a transaction -D, --deleteall Remove all login objects local customizations -s SEUSER, --seuser SEUSER SELinux user name

@mountaing : yep, that was the error, thanks a lot for the help! :)

@mountaing nice work! that did the trick thanks!

@petulia3478 Downloading the latest enterprise version tarball and running the pupper-enterprise-installer, allows you to run a guided install via a web interface. Go to: https://<yourhost>:3000 Follow option for the type of installation you require, Monolithic or Split.

@hawksbill the validation of the JSON may be ok, even if the error is a little misleading, but the command line syntax is wrong, try this command: $ aws cloudformation create-stack --stack-name stack1 --template-body file://s3sample.json

@hawksbill In your knife.rb set the editor value to the editor of choice like this: knife[:editor]="vi"

@hawksbill The message displayed is a warning to say the no cache entries exist, if the build is new. and nothing has been installed, no cache entries will exist, adding package fetches the repo cache and put it under /var/cache/apk/*

@petulia3478 Hi have a read of this link: https://kubernetes.io/docs/concepts/overview/object-management-kubectl/overview/, this happens when mixing up imperative & declarative commands. Use one or the other.

I have seen this when using GCP, and gcloud cli, if the credentials or endpoints are not configured properly, for me running this fixed it: $ gcloud container clusters get-credentials spaceboy Fetching cluster endpoint and auth data. kubeconfig entry generated for spaceboy.

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

The boot and root disk information is useful when trying to determine which disk is your original root and boot disk and which disk is your mirror. The BDRA is the boot disk reserved area. Display boot information BDRA # lvlnboot -v Boot Definitions for Volume Group /dev/vg00: Physical Volumes belonging in Root Volume Group: /dev/dsk/c1t7d0s2 (0/4/1/0.0.0.7.0) -- Boot Disk /dev/dsk/c1t0d0 (0/4/1/0.0.0.0.0) /dev/dsk/c1t0d0s2 (0/4/1/0.0.0.0.0) -- Boot Disk Boot: lvol1 on: /dev/dsk/c1t7d0s2 /dev/dsk/c1t0d0s2 Root: lvol3 on: /dev/dsk/c1t7d0s2 /dev/dsk/c1t0d0s2 Swap: lvol2 on: /dev/dsk/c1t7d0s2 /dev/dsk/c1t0d0s2 Dump: lvol2 on: /dev/dsk/c1t7d0s2, 0

Run the following command: # ioscan -fun -C disk Class I H/W Path Driver S/W State H/W Type Description --------------------------------------------------------------------- disk 0 0/0/2/1.0.16.0.0 sdisk CLAIMED DEVICE _NEC DVD+-RW ND-6650A /dev/dsk/c0t0d0 /dev/rdsk/c0t0d0 disk 1 0/4/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP DG072A9BB7 /dev/dsk/c1t0d0 /dev/rdsk/c1t0d0 disk 2 0/4/1/0.0.0.1.0 sdisk CLAIMED DEVICE HP DG072A9BB7 /dev/dsk/c1t1d0 /dev/rdsk/c1t1d0 disk 3 0/4/1/0.0.0.2.0 sdisk CLAIMED DEVICE HP DG072A8B54 /dev/dsk/c1t2d0 /dev/rdsk/c1t2d0 disk 4 0/4/1/0.0.0.3.0 sdisk CLAIMED DEVICE HP DG072A9BB7 /dev/dsk/c1t3d0 /dev/rdsk/c1t3d0 disk 5 0/4/1/0.0.0.4.0 sdisk CLAIMED DEVICE HP DG072A9BB7 /dev/dsk/c1t4d0 /dev/rdsk/c1t4d0 disk 6 0/4/1/0.0.0.5.0 sdisk CLAIMED DEVICE HP DG072A8B54 /dev/dsk/c1t5d0 /dev/rdsk/c1t5d0 disk 7 0/4/1/0.0.0.6.0 sdisk CLAIMED DEVICE HP DG072A9BB7 /dev/dsk/c1t6d0 /dev/rdsk/c1t6d0 disk 8 0/4/1/0.0.0.7.0 sdisk CLAIMED DEVICE HP DG072A9BB7 /dev/dsk/c1t7d0 /dev/dsk/c1t7d0s2 /dev/rdsk/c1t7d0 /dev/rdsk/c1t7d0s2 /dev/dsk/c1t7d0s1 /dev/dsk/c1t7d0s3 /dev/rdsk/c1t7d0s1 /dev/rdsk/c1t7d0s3

This command is the replacement for sam, in hp-ux 11.31. It invokes a browser based menu to administer the hp-ux operating system. To check the start-up options run the following # cd /opt/hpsmh/bin # ls hpsmh smhstartconfig # ./smhstartconfig HPSMH 'autostart url' mode.........: ON HPSMH 'start on boot' mode.........: OFF Start Tomcat when HPSMH starts.....: OFF url and boot mode cannot both be ON. Turn on in boot mode, use OFF to turn off # ./smhstartconfig -b ON Turn on in url mode # ./smhstartconfig -a ON To start hpsmh run the following, again under /opt/hpsmh/bin # ./hpsmh autostart Starting the System Management HomePage server ... The System Management HomePage server has been started successfully. The System Management HomePage timeout monitor is currently enabled (30 minutes You should see the following processes running. # ps -ef | grep hpsmh root 2102 1 0 Feb 25 ? 0:00 /opt/hpsmh/lbin/smhstartd hpsmh 8876 8873 0 11:54:22 ? 0:00 /opt/hpws/apache/bin/httpd -k start -DSSL -f /opt/hpsmh/conf/smhpd.conf root 8873 1 0 11:54:21 ? 0:00 /opt/hpws/apache/bin/httpd -k start -DSSL -f /opt/hpsmh/conf/smhpd.conf root 8981 1800 1 11:55:11 pts/0 0:00 grep hpsmh root 8874 1 0 11:54:21 pts/0 0:00 /usr/bin/sh /opt/hpsmh/lbin/timeoutmonitor 30 root 8875 8874 0 11:54:21 pts/0 0:00 /opt/hpsmh/lbin/time_out /opt/hpsmh/logs/smh.timestamp 30

To list files in human readable sizes use the "-h" option of the ls command: $ ls -lh

The sftp command is normally on all linux operating systems. $ sftp username@hostname.com or sftp username@ip_address