Create your netplan file

vi /etc/netplan/01-netcfg.yaml

network:

    version: 2

    renderer: networkd

    ethernets:

       ens3:

           dhcp4: no

           addresses: [192.50.1.157/24]

           gateway4: 192.50.1.1

           nameservers:

              addresses: [8.8.4.4,8.8.8.8]

Check our file to see if it is correct:

sudo netplan try

if you have an error in the file it will tell you.

Eg. formatting is important if you have the below you will get an error because all of the options under ens3n

/etc/netplan/01-netcfg.yaml:9:13: Error in network definition: expected mapping (check indentation)
       ens3:
            ^

Notice that under ens3 below that there is no indentation of dhcp4, addresses etc.. and that is incorrect (whereas the old interfaces file didn't care)

network:

    version: 2

    renderer: networkd

    ethernets:

       ens3:

       dhcp4: no

       addresses: [192.50.1.157/24]

       gateway4: 192.50.1.1

       nameservers:

          addresses: [8.8.4.4,8.8.8.8]

apply the new plan once try above succeeds (it means it will apply the network settings in the yaml file you created)

sudo netplan apply

Yes you have that right, the network service in CentOS 8 no longer exists.  So there is no more systemctl restart network

You can restart NetworkManager but it doesn't have the same effect or ifup/ifdown on all interfaces. 

To replicate that the best you can do is type the following commands to nmcli

nmcli networking off; nmcli networking on
 

*Don't forget the semi-colon otherwise you'll go offline if you are connecting to a remote Virtual or Dedicated Server

The cool thing here is that we only need 1 drive to make a RAID 10 or RAID 1 array, we just tell the Linux mdadm utility that the other drive is "missing" and we can then add our original drive to the array after booting into our new RAID array.

Step#1 Install tools we need

yum -y install mdadm rsync

Step #2 Create your partitions on the drive that will be our RAID array

Here I assume it is /dev/sdb

fdisk /dev/sdb

#I find that mdadm works fine with the default partition type Linux although the fd flag will make them easier to find (fd means Software RAID)

/dev/sdb1 (md0) = Partition #1=/boot size=1G
/dev/sdb2 (md1) = Partition #2=swap size=30G (or whatever is suitable for your RAM and disk space)
/dev/sdb3 (md2) = Partition #3=/ size = the remainder of the disk (unless you have other plans/requirements).

Step #3 - Make our RAID arrays

To make sure your RAID array is bootable we need to ALWAYS make our md0 or /boot this way.

#md0 /boot
#we use level = 1 and metadata=0.90 to ensure /boot is readable by grub otherwise boot will fail
mdadm --create /dev/md0 --level 1 --raid-devices 2 /dev/sdb1 missing --metadata=0.90

#md1 swap
mdadm --create /dev/md1 --level 10 --raid-devices 2 /dev/sdb2 missing

#md2 /
mdadm --create /dev/md2 --level 10 --raid-devices 2 /dev/sdb3 missing

Notice that we specified the second drive as "missing". We will re-add it after we are all done and have rebooted into our RAID array.  Still, with the degraded array and only a single drive you can convert a live system into RAID without reinstalling anything.

Step #4 - Make filesystems on RAID arrays

mkfs.ext4 /dev/md0

mkswap /dev/md1

mkfs.ext4 /dev/md2

Step #5 - Mount and stage our current system into new mdadm RAID arrays

We will use /mnt/md2 as out staging point but it could be anything technically.

#make our staging point
mkdir /mnt/md2


# mount our root into our staging point
mount /dev/md2 /mnt/md2

#we need to make our boot inside our staging point before we copy things over
mkdir /mnt/md2/boot

# mount our boot into our staging point
mount /dev/md0 /mnt/md2/boot

Step #6 - Copy our current environment to our new RAID

#we exclude /mnt/so we don't double copy what is in /mnt including our staging environment
# we also exclude the contents of proc, sys because it slows things down and proc and sys will be populated once our new array environment actually gets booted from
rsync -Phaz --exclude=/mnt/* --exclude=/sys/* --exclude=/proc/* / /mnt/md2

Step #7 - chroot into and configure our new environment

Here is how we chroot properly:
#remember I assume your staging point ins in /mnt/md2 change that part if yours is different
for mount in dev sys proc; do
 mount -o bind /$mount /mnt/md2/$mount
done

#now let's chroot

chroot /mnt/md2

Step #8 - Disable SELinux

#1 Let's disable selinux it causes lots of problems and if you don't update the selinux attributes you will not be able to login after you boot!
#you would get this error "Failed to create session: Start job for unit user@0.service failed with 'failed'"



sed -i s#SELINUX=enforcing#SELINUX=disabled#  /etc/selinux/config

#double check that /etc/selinux/config has SELINUX=disabled just to be sure

Step #9 - Modify grub default config

#2 Let's fix our default grub config, it will often have references to lvm and other hard coded partitions that we no longer have.  We also have to add "rd.auto" or grub will not assemble and boot from our array

vi /etc/default/grub

Find this line:

GRUB_CMDLINE_LINUX="crashkernel=auto resume=/dev/mapper/cl-swap rd.lvm.lv=cl/root rd.lvm.lv=cl/swap rhgb quiet"

change to

GRUB_CMDLINE_LINUX="crashkernel=auto rd.auto rhgb quiet"

rd.auto will automatically assemble our raid array otherwise if it's not assembled we can't mount and boot from it.

update grub

grub2-mkconfig > /etc/grub2.cfg

Make sure your grub entries are correct:

Centos grub would not boot because it was relative to /boot but that is wrong since we changed to an actual partition for /boot

cd /boot/loader/entries


ls


02bcb1988e6940a1bed64c61df98716a-0-rescue.conf
02bcb1988e6940a1bed64c61df98716a-4.18.0-147.5.1.el8_1.x86_64.conf
02bcb1988e6940a1bed64c61df98716a-4.18.0-80.el8.x86_64.conf


[root@localhost entries]# vi 02bcb1988e6940a1bed64c61df98716a-4.18.0-147.5.1.el8_1.x86_64.conf
title CentOS Linux (4.18.0-147.5.1.el8_1.x86_64) 8 (Core)
version 4.18.0-147.5.1.el8_1.x86_64
linux /boot/vmlinuz-4.18.0-147.5.1.el8_1.x86_64
initrd /boot/initramfs-4.18.0-147.5.1.el8_1.x86_64.img $tuned_initrd
options $kernelopts $tuned_params
id centos-20200205020746-4.18.0-147.5.1.el8_1.x86_64
grub_users $grub_users
grub_arg --unrestricted
grub_class kernel
 

Fix the lines in bold and remove the /boot because that will cause your system not to boot.  If you have the /boot above it means that your current system has no separate boot partition.

Fixing them would like this:


title CentOS Linux (4.18.0-147.5.1.el8_1.x86_64) 8 (Core)
version 4.18.0-147.5.1.el8_1.x86_64
linux /vmlinuz-4.18.0-147.5.1.el8_1.x86_64
initrd /initramfs-4.18.0-147.5.1.el8_1.x86_64.img $tuned_initrd
options $kernelopts $tuned_params
id centos-20200205020746-4.18.0-147.5.1.el8_1.x86_64
grub_users $grub_users
grub_arg --unrestricted
grub_class kernel


Step #10 - Update /etc/fstab

Modify /etc/fstab and give the UUID for /, boot and swap of your md devices.
md0=/boot
md1=swap
md2=/

#Let's get their block IDs/UUID

blkid /dev/md0
/dev/md0: UUID="f4dc88f5-90ea-4916-97d7-8d627935118" TYPE="ext4"
blkid /dev/md1
/dev/md1: UUID="3adf88f5-90ea-4916-97d7-8d6279871f18" TYPE="swap"
blkid /dev/md2
/dev/md2: UUID="45aa90ea-4916-97d7-8d6279871f18" TYPE="ext4"

vi /etc/fstab
It should look something like this with ONLY the RAID arrays we have and the old stuff commented out

UUID=45aa90ea-4916-97d7-8d6279871f18    /                       ext4     defaults        0 0
UUID=f4dc88f5-90ea-4916-97d7-8d627935118 /boot                   ext4    defaults        1 2
UUID=3adf88f5-90ea-4916-97d7-8d6279871f18     swap                    swap    defaults        0 0


Step #11 - Use dracut to update our initramfs otherwise we don't be able to boot still!

#the first part below after -f is the full path name to the initramfs that you will be booting.  The second part is just the raw kernel version
dracut -f /boot/initramfs-4.18.0-147.5.1.el8_1.x86_64.img 4.18.0-147.5.1.el8_1.x86_64

dracut -f alone will work IF you are on the same OS and kernel that is installed

Step#12 - Install grub to all bootable drives

This depends on how many drives you have but let's assume 2 then they are /dev/sda and /dev/sdb

grub2-install /dev/sda

grub2-install /dev/sdb

Step#13 - Cross fingers and reboot

It would be a good idea to go back through the steps and make sure everything is right, including your grub default conf, UUIDs in /etc/fstab etc..

I also recommend NOT doing this on a production machine and at least not without backups.  If you want to practice it is best to run through the steps on a Virtual Machine first to identify any mistakes you've made.

reboot

This is the reason that I don't like the new ADATA USB drives such as the UV128/64GB or 128GB drives and other ones that look to be the same style (the green sliding USB connector).

They just don't work well from new and never work properly at any point.

[  788.242463] usb 1-1.2: new high-speed USB device number 16 using ehci-pci
[  788.339816] usb 1-1.2: New USB device found, idVendor=125f, idProduct=db8a
[  788.339830] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  788.339838] usb 1-1.2: Product: ADATA USB Flash Drive
[  788.339845] usb 1-1.2: Manufacturer: ADATA
[  788.339852] usb 1-1.2: SerialNumber: 2982115170220001
[  788.341255] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[  788.341835] scsi host3: usb-storage 1-1.2:1.0
[  790.261722] scsi 3:0:0:0: Direct-Access     ADATA    USB Flash Drive  1100 PQ: 0 ANSI: 6
[  790.262888] sd 3:0:0:0: Attached scsi generic sg1 type 0
[  790.265307] sd 3:0:0:0: [sdb] 121241600 512-byte logical blocks: (62.1 GB/57.8 GiB)
[  790.266032] sd 3:0:0:0: [sdb] Write Protect is off
[  790.266045] sd 3:0:0:0: [sdb] Mode Sense: 43 00 00 00
[  790.266783] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  820.959391] usb 1-1.2: reset high-speed USB device number 16 using ehci-pci
[  826.047462] usb 1-1.2: device descriptor read/64, error -110
[  841.223952] usb 1-1.2: device descriptor read/64, error -110
[  841.399957] usb 1-1.2: reset high-speed USB device number 16 using ehci-pci
[  841.511860] usb 1-1.2: device descriptor read/64, error -71
[  841.727931] usb 1-1.2: device descriptor read/64, error -71
[  841.907980] usb 1-1.2: reset high-speed USB device number 16 using ehci-pci
[  842.331920] usb 1-1.2: device not accepting address 16, error -71
[  842.407950] usb 1-1.2: reset high-speed USB device number 16 using ehci-pci
[  842.831989] usb 1-1.2: device not accepting address 16, error -71
[  842.832383] usb 1-1.2: USB disconnect, device number 16
[  842.843999] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  842.844013] sd 3:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[  842.844019] blk_update_request: I/O error, dev sdb, sector 0
[  842.844027] Buffer I/O error on dev sdb, logical block 0, async page read
[  842.844129] ldm_validate_partition_table(): Disk read failed.
[  842.844207] Dev sdb: unable to read RDB block 0
[  842.844300]  sdb: unable to read partition table
[  842.844721] sd 3:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  842.844729] sd 3:0:0:0: [sdb] Sense not available.
[  842.844786] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[  842.995906] usb 1-1.2: new high-speed USB device number 17 using ehci-pci
[  843.107911] usb 1-1.2: device descriptor read/64, error -71
[  843.323899] usb 1-1.2: device descriptor read/64, error -71
[  843.499946] usb 1-1.2: new high-speed USB device number 18 using ehci-pci
[  843.611984] usb 1-1.2: device descriptor read/64, error -71
[  843.827907] usb 1-1.2: device descriptor read/64, error -71
[  843.932047] usb 1-1-port2: attempt power cycle
[  844.515938] usb 1-1.2: new high-speed USB device number 19 using ehci-pci
[  844.939941] usb 1-1.2: device not accepting address 19, error -71
[  845.011953] usb 1-1.2: new high-speed USB device number 20 using ehci-pci
[  845.435949] usb 1-1.2: device not accepting address 20, error -71
[  845.436120] usb 1-1-port2: unable to enumerate USB device

the exact same error on another computer (in both cases one is a laptop plugged into the motherboard and the other is a desktop plugged into the motherboard).  All other brands of USB drives work fine on these computers.  The same thing happens on several other computers and this has happened since the drive was new.

Feb 12 07:45:15 devtest kernel: [519601.178631] usb 1-2: new high-speed USB device number 3 using ehci-pci
Feb 12 07:45:15 devtest kernel: [519601.311774] usb 1-2: New USB device found, idVendor=125f, idProduct=db8a
Feb 12 07:45:15 devtest kernel: [519601.311780] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 12 07:45:15 devtest kernel: [519601.311785] usb 1-2: Product: ADATA USB Flash Drive
Feb 12 07:45:15 devtest kernel: [519601.311790] usb 1-2: Manufacturer: ADATA
Feb 12 07:45:15 devtest kernel: [519601.311794] usb 1-2: SerialNumber: 2982115170220001
Feb 12 07:45:15 devtest mtp-probe: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:02.1/usb1/1-2"
Feb 12 07:45:15 devtest mtp-probe: bus: 1, device: 3 was not an MTP device
Feb 12 07:45:15 devtest kernel: [519601.365746] usb-storage 1-2:1.0: USB Mass Storage device detected
Feb 12 07:45:15 devtest kernel: [519601.365969] scsi host9: usb-storage 1-2:1.0
Feb 12 07:45:15 devtest kernel: [519601.366146] usbcore: registered new interface driver usb-storage
Feb 12 07:45:15 devtest kernel: [519601.370666] usbcore: registered new interface driver uas
Feb 12 07:45:17 devtest kernel: [519603.287058] scsi 9:0:0:0: Direct-Access     ADATA    USB Flash Drive  1100 PQ: 0 ANSI: 6
Feb 12 07:45:17 devtest kernel: [519603.287818] sd 9:0:0:0: Attached scsi generic sg2 type 0
Feb 12 07:45:17 devtest kernel: [519603.288783] sd 9:0:0:0: [sdc] 121241600 512-byte logical blocks: (62.1 GB/57.8 GiB)
Feb 12 07:45:17 devtest kernel: [519603.290281] sd 9:0:0:0: [sdc] Write Protect is off
Feb 12 07:45:17 devtest kernel: [519603.290288] sd 9:0:0:0: [sdc] Mode Sense: 43 00 00 00
Feb 12 07:45:17 devtest kernel: [519603.291293] sd 9:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 12 07:45:48 devtest kernel: [519634.413045] usb 1-2: reset high-speed USB device number 3 using ehci-pci
Feb 12 07:46:09 devtest kernel: [519654.958540] usb 1-2: reset high-speed USB device number 3 using ehci-pci
Feb 12 07:46:10 devtest kernel: [519655.686587] usb 1-2: reset high-speed USB device number 3 using ehci-pci
Feb 12 07:46:10 devtest kernel: [519656.150613] usb 1-2: device not accepting address 3, error -71
Feb 12 07:46:10 devtest kernel: [519656.262628] usb 1-2: reset high-speed USB device number 3 using ehci-pci
Feb 12 07:46:11 devtest kernel: [519656.726661] usb 1-2: device not accepting address 3, error -71
Feb 12 07:46:11 devtest kernel: [519656.726903] usb 1-2: USB disconnect, device number 3
Feb 12 07:46:11 devtest kernel: [519656.734710] sd 9:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Feb 12 07:46:11 devtest kernel: [519656.734724] sd 9:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Feb 12 07:46:11 devtest kernel: [519656.734729] blk_update_request: I/O error, dev sdc, sector 0
Feb 12 07:46:11 devtest kernel: [519656.734890] Buffer I/O error on dev sdc, logical block 0, async page read
Feb 12 07:46:11 devtest kernel: [519656.735065] ldm_validate_partition_table(): Disk read failed.
Feb 12 07:46:11 devtest kernel: [519656.735096] Dev sdc: unable to read RDB block 0
Feb 12 07:46:11 devtest kernel: [519656.735223]  sdc: unable to read partition table
Feb 12 07:46:11 devtest kernel: [519656.735560] sd 9:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Feb 12 07:46:11 devtest kernel: [519656.735567] sd 9:0:0:0: [sdc] Sense not available.
Feb 12 07:46:11 devtest kernel: [519656.735627] sd 9:0:0:0: [sdc] Attached SCSI removable disk
Feb 12 07:46:11 devtest kernel: [519656.906670] usb 1-2: new high-speed USB device number 4 using ehci-pci
Feb 12 07:46:11 devtest kernel: [519657.634720] usb 1-2: new high-speed USB device number 5 using ehci-pci
Feb 12 07:46:12 devtest kernel: [519658.250781] usb usb1-port2: attempt power cycle
Feb 12 07:46:13 devtest kernel: [519658.670801] usb 1-2: new high-speed USB device number 6 using ehci-pci
Feb 12 07:46:13 devtest kernel: [519659.134820] usb 1-2: device not accepting address 6, error -71
Feb 12 07:46:13 devtest kernel: [519659.246830] usb 1-2: new high-speed USB device number 7 using ehci-pci
Feb 12 07:46:14 devtest kernel: [519659.710862] usb 1-2: device not accepting address 7, error -71
Feb 12 07:46:14 devtest kernel: [519659.711041] usb usb1-port2: unable to enumerate USB device
Feb 12 07:46:14 devtest systemd-udevd[27309]: inotify_add_watch(9, /dev/sdc, 10) failed: No such file or directory
Feb 12 07:46:14 devtest kernel: [519660.026890] usb 2-2: new full-speed USB device number 3 using ohci-pci
Feb 12 07:46:15 devtest kernel: [519660.774945] usb 2-2: new full-speed USB device number 4 using ohci-pci
Feb 12 07:46:15 devtest kernel: [519661.343029] usb usb2-port2: attempt power cycle
Feb 12 07:46:16 devtest kernel: [519661.827031] usb 2-2: new full-speed USB device number 5 using ohci-pci
Feb 12 07:46:16 devtest kernel: [519662.235058] usb 2-2: device not accepting address 5, error -62
Feb 12 07:46:16 devtest kernel: [519662.411069] usb 2-2: new full-speed USB device number 6 using ohci-pci
Feb 12 07:46:17 devtest kernel: [519662.819101] usb 2-2: device not accepting address 6, error -62
Feb 12 07:46:17 devtest kernel: [519662.819242] usb usb2-port2: unable to enumerate USB device



This should work but the key thing is having the "-cpu host" flag.

Once you add the correct -cpu host flag then it should boot just fine on KVM.

qemu-system-x86_64 --enable-kvm -cpu host -smp 8 -m 8192 -drive format=raw,file=the-file.img

Examples can be found here on how to boot Windows properly with KVM.

sudo vi /etc/lightdm/lightdm.conf.d/70-linuxmint.conf
 

Change this:

[SeatDefaults]
user-session=mate
allow-guest=false

To this:

[SeatDefaults]
user-session=mate
allow-guest=false
greeter-hide-users=true
greeter-show-manual-login=true

To see and apply your changes just restart lightdm:

sudo systemctl restart lightdm

If you want it to hide your username when the screen is locked (which you probably do since otherwise if you are away from your computer with a locked screen, it would display your username) then follow this guide to disable lock-screen usernames from showing in Linux Mint

The problem is that by default ssh-keygen loves to generate an easy to crack 2048 bit key (RSA).  Supposedly having a larger keysize helps such as 4096 or 8096 but it is thought to be useless still against Quantum computing.

How can I check my existing keysize and type?

ssh-keygen -lf /path/to/your/id_rsa.pub

The output will be something like below followed by the hash.  The first number is the key size and the second part will be the type eg RSA, SHA256 etc..

2048 RSA

How can I create an ssh key?

-t = the type of key

-b = the key size (you probably shouldn't use that many 9s!)

ssh-keygen -t ed25519 -b 9999999999999

How can I see what types of keys my ssh version supports?

Don't use dsa it is weak and now deprecated in the latest ssh versions and many recommend ed25519 (EdDSA)

ssh-keygen -t
option requires an argument -- t
usage: ssh-keygen [-q] [-b bits] [-t dsa | ecdsa | ed25519 | rsa | rsa1]


A lot of times this is actually caused by simply not having Firefox installed at all.

selenium.common.exceptions.WebDriverException: Message: Can not connect to the Service geckodriver

https://github.com/mozilla/geckodriver/issues/270

In this case I am executing using "python3" but what you find in cases like this can be surprising.

The most common issues are that someone has a module for python 2 "pip" and doesn't realize they need "pip3" to install it for python3, but this is not one of those cases.

ModuleNotFoundError: No module named 'bs4'

OK maybe we didn't install it for python3?

[user@host]# pip3 install bs4

No, we did install it for python3 because below it says it is already installed "Requirement already satisfied"

Requirement already satisfied: bs4 in /usr/lib/python3.4/site-packages (0.0.1)
Requirement already satisfied: beautifulsoup4 in /usr/lib/python3.4/site-packages (from bs4) (4.6.3)
You are using pip version 18.1, however version 19.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

But wait look carefully that it is installed for "python3.4".  Let's see what python3 actually refers to (since python3 is really a symlink to a specific 3.x version).

python3: /usr/bin/python3.6 /usr/bin/python3.6m /usr/bin/python3.4m /usr/bin/python3.4m-config /usr/bin/python3 /usr/bin/python3.4m-x86_64-config /usr/bin/python3.4 /usr/bin/python3.4-config /usr/lib/python3.6 /usr/lib/python3.4 /usr/lib64/python3.6 /usr/lib64/python3.4 /usr/include/python3.6m /usr/include/python3.4m /usr/share/man/man1/python3.1.gz

[user@host]# ls -al /usr/bin/python3

OK so we see that python3 really points to python3.6


lrwxrwxrwx 1 root root 9 Sep 12 11:33 /usr/bin/python3 -> python3.6

There are a few ways to resolve this, one of the easiest ones may be to symlnk python3 back to python3.4 or to uninstall python3.6

In my case of Centos there is no pip3.6 installed nor is it available as a package so I am electing to remove python3.6 to solve this issue.

In my case here is what you need to type:

yum remove python36-*


ln -s --force /usr/bin/python3.4m /usr/bin/python3

This is not about using ssh as a proxy, but rather, using a proxy when you are SSHing to another host and using ProxyCommand (where we normally use nc as our proxy tool).

In newer versions of nc the syntax has changed to the following:

ssh -o ProxyCommand="nc  -x 127.0.0.1:1234" %h %p user@host

The format must be like above in newer nc versions.

Just be sure to change the 1234 to the port of your SOCKS server and also 127.0.0.1 to the IP of the socks server

And of course user@host to the right info (eg. the username of your server and host = hostname or IP of your server)

If you try the old format you will get an ssh exchange identification error:

ssh -o ProxyCommand='nc --proxy-type socks5 --proxy 127.0.0.1:3000 %h %p' user@someserver.com
nc: invalid option -- '-'
This is nc from the netcat-openbsd package. An alternative nc is available
in the netcat-traditional package.
usage: nc [-46bCDdhjklnrStUuvZz] [-I length] [-i interval] [-O length]
      [-P proxy_username] [-p source_port] [-q seconds] [-s source]
      [-T toskeyword] [-V rtable] [-w timeout] [-X proxy_protocol]
      [-x proxy_address[:port]] [destination] [port]
ssh_exchange_identification: Connection closed by remote host
 

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.cik_support=1 amdgpu.si_support=1 radeon.si_support=0 radeon.cik_support=0 radeon.dpm=1"
 

Symbolic link not allowed or link target not accessible: /path/httpdocs/news.html

There are a few reasons that can cause this message and this is for people who have ruled out the basics, eg. your symlinks are enabled and the right permissions are applied (but read on to learn about ownership requirements above the directory in question).

So there are a few key things here that cause Apache not to follow symlinks:

1. One directory up for your vhost eg if you have /var/www/html/vhost then html MUST be owned by the httpd/apache user who runs the process.  Otherwise even though access is technically allowed, it will be denied. (even if the files and dirs involved have the right ownership).
2. Make sure you actually have Options +Symlinks in your vhost and/or htaccess
3. Make sure the permissions are correct, you will need read and execute permissions on the file/dir of the symlink or you could get that message

The other solution is to use this option in your vhost or htaccess:

Options -SymLinksIfOwnerMatch

#but be warned the above doesn't seem to work sometimes

 

If you just do a normal chown user.user somedir it won't work.  You will see the ownership is still the previous owner.

How To Change Ownership Of Symlink:

The simplest part is just adding the -h which means no dereference so it applies the ownership on the symlink and does not try (and fail) to change ownership of the dereferenced symlink destination.

chown -h user.user somedir

It is fairly simple to use once you know how to use it.  However, the tricky thing is that by default it doesn't seem to be active or listen on any interface on manually specified.

How To Install ifplugd

First we install ifplugd

sudo apt install ifplugd

Let's enable it on our desired device(s)

vi /etc/default/ifplugd

set this line as so:


INTERFACES="enp0s8"
 

*Obviously change enp0s8 to the name of the NIC you want ifplugd to be active on, you can also enable it on multiple NICs by specifying a space. eg:

INTERFACES="eth0 eth1"

Let's create a sample script at first which is always placed in /etc/ifplugd/action.d/


touch /etc/ifplugd/action.d/yourscript.sh
chmod +x /etc/ifplugd/action.d/yourscript.sh
 

Remove /etc/ifplugd/action.d/ifupdown

I find this script can break other things you are trying to do so I recommend moving or removing it.  A good example is that it ended up interferring with my script below, where to make a NIC work it had to be brought up and down.  But then the ifupdown script would run and bring the NIC up again or down again.

So use the command below to move ifupdown into /etc/ifplugd so it doesn't get executed but you could always put it back into action.d if you wanted it again.

sudo mv /etc/ifplugd/action.d/ifupdown /etc/ifplugd/

An example of what yourscript.sh can be

In Unix/Linux there are often weird situations or even bugs in NICs that prevent them from working properly.  I have encountered some NICs that give you an uplink light and also show in ethttool that a 1gbit link is established.

Even ethttool looks good:

Settings for enp1s0:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Supported pause frame use: No
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Advertised pause frame use: Symmetric Receive-only
    Advertised auto-negotiation: Yes
    Speed: 1000Mb/s
    Duplex: Full
    Port: Twisted Pair
    PHYAD: 0
    Transceiver: internal
    Auto-negotiation: on
    MDI-X: Unknown
Cannot get wake-on-lan settings: Operation not permitted
    Current message level: 0x00000033 (51)
                   drv probe ifdown ifup
    Link detected: yes

However it is often the case that an ifdown and ifup is required to make the NIC work even though it is already configured with an IP (due to a driver bug especially in some NVIDIA based NICs):

Here is a script "yourscript.sh" that fixes that:


#!/bin/bash

#echo "in ifplugd" >> /tmp/ifplugd.txt
if [ "$2" == "up" ]; then
 /sbin/ifdown $1
 /sbin/ifup $1
 echo "executing state $2 ifdown ifup on :: $1 :: `date`" >> /tmp/ifplugdlog.txt
fi
 

dd is a very handy tool and there are some more practical things we can do.  For example if we want to dump a 3TB drive and want to preserve it and only 200GB are being used on the 3TB we can save a lot of space with gzip.

Backing Stuff up with dd

How to Use dd to backup a raw hard drive and tar gzip at once

• Change /dev/sda to the drive you want to backup
• Change /mnt/extraspace to the path you want to backup to

sudo dd if=/dev/sda bs=20M| gzip -c > /mnt/extraspace/backup.img.gz
 

How to use dd to backup a raw hard drive WITHOUT compression:

sudo dd if=/dev/sda of=/mnt/extraspace/backup.img.gz bs=20M

Restoring Stuff with dd

Restoring is just the opposite.

How to restore a raw image with dd with compression:

change the /dev/sdX to the drive you want to restore to (be careful and understand /dev/sdX will be totally wiped out and erased with this operation or at least as much data as the image contains)

gunzip -c /mnt/yourddimage.img.gz | dd of=/dev/sdX

How to restore a raw image with dd WITHOUT compression:

change the /dev/sdX to the drive you want to restore to (be careful and understand /dev/sdX will be totally wiped out and erased with this operation or at least as much data as the image contains)

sudo dd if=/mnt/yourddimage.img of=/dev/sdX bs=10M

The easiest way to know if your videos are playing with GPU acceleration are to watch the process of xplayer, mpv or whatever you are playing.  The CPU usage should be no more than 10% for that process/program if it is using acceleration.

Let's manually play with vdpau to make sure it works before we make it permanent:

First make sure you have libvdpau installed:

sudo apt install vdpau-driver-all

If you run mpv and get an error like this it means you are missing libvdpau:

Playing: MVI_0822.MP4
 (+) Video --vid=1 (*) (h264)
 (+) Audio --aid=1 --alang=eng (*) (aac)
Failed to open VDPAU backend libvdpau_radeonsi.so: cannot open shared object file: No such file or directory
[vo/vdpau] Error when calling vdp_device_create_x11: 1
Error opening/initializing the selected video_out (-vo) device.
Video: no video
AO: [pulse] 48000Hz stereo 2ch float
A: 00:00:08 / 00:01:17 (11%)

 

To enable AMD VDPAU acceleration in mpv (the successor to mplayer) just add this file to make it permanent:

After making changes to the conf below if you open a video with mpv and only hear sound it means there is an issue with your config.  To see any error you can just manually run "mpv video.mp4"

vi ~/.config/mpv/mpv.conf

hwdec=vdpau
vo=vdpau                   # OR vo=vdpau
 

#you can also add this to the config file which may produce better quality/looking playback above but be warned it does not seem to work for some older cards like Kabini 8400:

profile=gpu-hq

vdpauinfo is a great way to see what is supported by your GPU acceleration:


sudo apt install vdpauinfo

vdpauinfo
display: :0   screen: 0
API version: 1
Information string: G3DVL VDPAU Driver Shared Library version 1.0

Video surface:

name   width height types
-------------------------------------------
420    16384 16384  NV12 YV12
422    16384 16384  UYVY YUYV
444    16384 16384  Y8U8V8A8 V8U8Y8A8

Decoder capabilities:

name                        level macbs width height
----------------------------------------------------
MPEG1                          --- not supported ---
MPEG2_SIMPLE                    3  9216  2048  1152
MPEG2_MAIN                      3  9216  2048  1152
H264_BASELINE                  41  9216  2048  1152
H264_MAIN                      41  9216  2048  1152
H264_HIGH                      41  9216  2048  1152
VC1_SIMPLE                      1  9216  2048  1152
VC1_MAIN                        2  9216  2048  1152
VC1_ADVANCED                    4  9216  2048  1152
MPEG4_PART2_SP                  3  9216  2048  1152
MPEG4_PART2_ASP                 5  9216  2048  1152
DIVX4_QMOBILE                  --- not supported ---
DIVX4_MOBILE                   --- not supported ---
DIVX4_HOME_THEATER             --- not supported ---
DIVX4_HD_1080P                 --- not supported ---
DIVX5_QMOBILE                  --- not supported ---
DIVX5_MOBILE                   --- not supported ---
DIVX5_HOME_THEATER             --- not supported ---
DIVX5_HD_1080P                 --- not supported ---
H264_CONSTRAINED_BASELINE       0  9216  2048  1152
H264_EXTENDED                  --- not supported ---
H264_PROGRESSIVE_HIGH          --- not supported ---
H264_CONSTRAINED_HIGH          --- not supported ---
H264_HIGH_444_PREDICTIVE       --- not supported ---
HEVC_MAIN                      --- not supported ---
HEVC_MAIN_10                   --- not supported ---
HEVC_MAIN_STILL                --- not supported ---
HEVC_MAIN_12                   --- not supported ---
HEVC_MAIN_444                  --- not supported ---

Output surface:

name              width height nat types
----------------------------------------------------
B8G8R8A8         16384 16384    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8
R8G8B8A8         16384 16384    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8
R10G10B10A2      16384 16384    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8
B10G10R10A2      16384 16384    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8

Bitmap surface:

name              width height
------------------------------
B8G8R8A8         16384 16384
R8G8B8A8         16384 16384
R10G10B10A2      16384 16384
B10G10R10A2      16384 16384
A8               16384 16384

Video mixer:

feature name                    sup
------------------------------------
DEINTERLACE_TEMPORAL             y
DEINTERLACE_TEMPORAL_SPATIAL     -
INVERSE_TELECINE                 -
NOISE_REDUCTION                  y
SHARPNESS                        y
LUMA_KEY                         y
HIGH QUALITY SCALING - L1        y
HIGH QUALITY SCALING - L2        -
HIGH QUALITY SCALING - L3        -
HIGH QUALITY SCALING - L4        -
HIGH QUALITY SCALING - L5        -
HIGH QUALITY SCALING - L6        -
HIGH QUALITY SCALING - L7        -
HIGH QUALITY SCALING - L8        -
HIGH QUALITY SCALING - L9        -

parameter name                  sup      min      max
-----------------------------------------------------
VIDEO_SURFACE_WIDTH              y        48     2048
VIDEO_SURFACE_HEIGHT             y        48     1152
CHROMA_TYPE                      y 
LAYERS                           y         0        4

attribute name                  sup      min      max
-----------------------------------------------------
BACKGROUND_COLOR                 y 
CSC_MATRIX                       y 
NOISE_REDUCTION_LEVEL            y      0.00     1.00
SHARPNESS_LEVEL                  y     -1.00     1.00
LUMA_KEY_MIN_LUMA                y 
LUMA_KEY_MAX_LUMA                y 

Useful resources:

https://ultra-technology.org/software_settings/mpv-nvidia-driver-with-high-quality/

The reason we use the command below is because we need the md5sum value hash of the password.  This means that we cannot use the md5sum

Change "yournewpass" to the pass you want to set

echo -n "yournewpass" | md5sum

Then you get the md5sum hash of whatever you entered eg. in this case "yournewpass"


5a9351ed00c7d484486c571e7a78c913  -

*Do not copy the " - " part just the md5sum sequence:

5a9351ed00c7d484486c571e7a78c913

If you don't mind your pass being set to "yournewpass" you could just copy the md5 hash as shown above and insert into the MySQL query further on below.

Copy the output above "5a9351ed00c7d484486c571e7a78c913"

Use MySQL To Change Your Password

You can connect with the root/admin user or just the user of your Wordpress database.

yourwordpressdbuser = The MySQL Database User for your Wordpress

yourwordpressdbname = The database name that you use for your Wordpress

5a9351ed00c7d484486c571e7a78c913 = The md5sum hash equivalent of "yournewpass"

mysql -u yourwordpressdbuser -p

use yourwordpressdbname;

UPDATE wp_users SET user_pass= "5a9351ed00c7d484486c571e7a78c913" WHERE user_login = "yourwordpressusername";

I find that the default settings for the radeon driver that is applied to most AMD cards is horrible.  For example by default TearFree is not enabled and it causes videos to have some kind of square artifacts.

Here are the settings I have found most suitable for AMD cards:

You need to create file in the following path and restart Xorg or your computer to apply it:

*Beware that making a mistake here will possibly make your computer unbooable or you will need to use a LiveCD to correct the problem.

sudo vi /usr/share/X11/xorg.conf.d/20-radeon.conf

Then paste the following and save it:

Section "Device"
    Identifier "Radeon"

    # Set Driver "radeon" because xorg now uses the modesetting driver by
    # default for Radeon HD GPUs and it causes a lot of triangular tearing.
    Driver "radeon"

    # We don't need TearFree to avoid tearing in Chrome and mpv; TearFree also
    # has the disadvantage of making switches to text VTs take 2 seconds.
    Option "TearFree" "on"

    # Use the default exa; glamor causes subtle but visible triangular tearing
    # when used without TearFree.
    Option "AccelMethod" "glamor"

    # DRI3 is not enabled by default on my Radeon HD 6470M
    # https://en.wikipedia.org/wiki/Direct_Rendering_Infrastructure#DRI3
    # https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-16.04-Enable-DRI3
    Option "DRI" "3"
EndSection
 

This is a gotcha but be aware sometimes iptables may be active and loaded by default.

Also make sure you don't just disable firewalld but also stop it otherwise it will still block stuff:

systemctl stop firewalld

If the above is not the issue then it is possible iptables is running and blocking stuff too, so you'll need to stop iptables.

So in addition to opening firewalld or disabling it, you would need to disable iptables too:

systemctl stop iptables


systemctl disable iptables

mysql reset root password.
 

Oops I can't remember my MySQL root password!

[root@centos7test etc]# mysql -u root -p
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)

First we need to stop mariadb:

systemctl stop mariadb

Now we need to restart it with skip-grant-tables which disables all authentication allowing us to login as root with no password.
mysqld_safe --skip-grant-tables &

[1] 1355
[root@centos7test etc]# 200108 15:34:30 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
200108 15:34:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql

Now login as root with no password:

[root@centos7test etc]# mysql -u root
Welcome to the MariaDB monitor.  Commands end with ; or g.
Your MariaDB connection id is 1
Server version: 5.5.64-MariaDB MariaDB Server

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or 'h' for help. Type 'c' to clear the current input statement.

Issue the following commands and queries:

Make sure you set "yournewpassword" to whatever you want the new password to be.

Don't forget the "flush privileges" at the end or the new password will not be applied.

MariaDB [(none)]> use mysql;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
MariaDB [mysql]> UPDATE user SET PASSWORD=PASSWORD("yournewpassword") WHERE USER='root';
Query OK, 3 rows affected (0.00 sec)
Rows matched: 3  Changed: 3  Warnings: 0

MariaDB [mysql]> flush privileges;
Query OK, 0 rows affected (0.00 sec)

MariaDB [mysql]> exit
Bye
 

Now login again with your new root password:

mysql -u root -p

yum -y install mariadb-server
 
systemctl start mariadb

mysql_secure_installation

Now we need to secure our install and set the MariaDB root password:

The lines you need to act on are marked in bold shown with the answer you need.

mysql_secure_installation

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
      SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!

In order to log into MariaDB to secure it, we'll need the current
password for the root user.  If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.

Enter current password for root (enter for none):
OK, successfully used password, moving on...

Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.

Set root password? [Y/n] y
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
 ... Success!


By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them.  This is intended only for testing, and to make the installation
go a bit smoother.  You should remove them before moving into a
production environment.

Remove anonymous users? [Y/n] y
 ... Success!

Normally, root should only be allowed to connect from 'localhost'.  This
ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n] y
 ... Success!

By default, MariaDB comes with a database named 'test' that anyone can
access.  This is also intended only for testing, and should be removed
before moving into a production environment.

Remove test database and access to it? [Y/n] y
 - Dropping test database...
 ... Success!
 - Removing privileges on test database...
 ... Success!

Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.

Reload privilege tables now? [Y/n] y
 ... Success!

Cleaning up...

All done!  If you've completed all of the above steps, your MariaDB
installation should now be secure.

Thanks for using MariaDB!


yum install centos-release-scl

yum install rh-php72 rh-php72-php rh-php72-php-mysqlnd

Symlink PHP binary:

ln -s /opt/rh/rh-php72/root/usr/bin/php /usr/bin/php

Symlink Apache and PHP module config:

ln -s /opt/rh/httpd24/root/etc/httpd/conf.d/rh-php72-php.conf /etc/httpd/conf.d/
ln -s /opt/rh/httpd24/root/etc/httpd/conf.modules.d/15-rh-php72-php.conf /etc/httpd/conf.modules.d/
ln -s /opt/rh/httpd24/root/etc/httpd/modules/librh-php72-php7.so /etc/httpd/modules/
 

Restart Apache:

systemctl restart httpd

This problem has been around forever, Linux seems to think it is fine to use the r8169 driver for an r8168 NIC but this often causes problems including the link not working at all.

In my case ethttool shows the link up and detected but it simply does not work especially on a laptop that has been resumed from suspension.  Sometimes it takes several minutes for it to work or to unplug and replug the ethernet.

Here is the solution:

Install the r8168 Driver:

sudo apt-get install r8168-dkms

Reading package lists... Done
Building dependency tree      
Reading state information... Done
The following NEW packages will be installed:
  r8168-dkms
0 upgraded, 1 newly installed, 0 to remove and 25 not upgraded.
Need to get 85.0 kB of archives.
After this operation, 1,109 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial/universe amd64 r8168-dkms all 8.041.00-1 [85.0 kB]
Fetched 85.0 kB in 0s (98.3 kB/s)  
Selecting previously unselected package r8168-dkms.
(Reading database ... 325617 files and directories currently installed.)
Preparing to unpack .../r8168-dkms_8.041.00-1_all.deb ...
Unpacking r8168-dkms (8.041.00-1) ...
Setting up r8168-dkms (8.041.00-1) ...
Loading new r8168-8.041.00 DKMS files...
First Installation: checking all kernels...
Building only for 4.4.0-170-generic
Building initial module for 4.4.0-170-generic
Done.

r8168:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.4.0-170-generic/updates/dkms/

depmod.....................................................

Backing up initrd.img-4.4.0-170-generic to /boot/initrd.img-4.4.0-170-generic.old-dkms
Making new initrd.img-4.4.0-170-generic
(If next boot fails, revert to initrd.img-4.4.0-170-generic.old-dkms image)
update-initramfs....

DKMS: install completed.


Blacklist the r8169 driver from loading on reboot:

echo "blacklist r8169"  > /etc/modprobe.d/blacklist-r8169.conf

Now to enable it right away:

*Note this will take down your network connection:

sudo rmmod r8169


sudo modprobe r8168


sudo systemctl restart networking


sudo systemctl restart network-manager

After that your network should come back up and work better.

You need to disable vsync like this when running glxgears:

vblank_mode=0 glxgears

Notice the higher than 59-60 fps results with vblank_mode=0:
ATTENTION: default value of option vblank_mode overridden by environment.
7919 frames in 5.0 seconds = 1583.704 FPS
8187 frames in 5.0 seconds = 1637.266 FPS
7441 frames in 5.0 seconds = 1488.072 FPS
7436 frames in 5.0 seconds = 1487.076 FPS
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 70679 requests (70679 known processed) with 0 events remaining.

Just running normal glxgears will only get you the screen vertical refresh which is a very silly default:


 ~ $ glxgearsRunning synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
296 frames in 5.0 seconds = 59.025 FPS
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 1205 requests (1205 known processed) with 0 events remaining.


Downloading and compiling from source to get the latest version of Asterisk is really simple with this guide.

apt install gcc make g++ libedit-dev uuid-dev libjansson-dev apt install libxml2-dev sqlite3 libsqlite3-dev
wget http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-16-current.tar.gz
tar -zxvf asterisk-16-current.tar.gz
cd asterisk-16.6.2/

./configure

If you get this error change you can change your configure line to this:
configure: *** Asterisk requires libjansson >= 2.11 and no system copy was found.
configure: *** Please install the 'libjansson' development package or
configure: *** use './configure --with-jansson-bundled'
root@metaspoit:~/asterisk-16.6.2# apt install libjansson-dev

./configure --with-jansson-bundled

#If you are lucky and all goes well:

configure: creating ./config.status
config.status: creating makeopts
config.status: creating autoconfig.h
configure: Menuselect build configuration successfully completed

               .$$$$$$$$$$$$$$$=..     
            .$7$7..          .7$$7:.   
          .$$:.                 ,$7.7  
        .$7.     7$$$$           .$$77 
     ..$$.       $$$$$            .$$$7
    ..7$   .?.   $$$$$   .?.       7$$$.
   $.$.   .$$$7. $$$$7 .7$$$.      .$$$.
 .777.   .$$$$$$77$$$77$$$$$7.      $$$,
 $$$~      .7$$$$$$$$$$$$$7.       .$$$.
.$$7          .7$$$$$$$7:          ?$$$.
$$$          ?7$$$$$$$$$$I        .$$$7
$$$       .7$$$$$$$$$$$$$$$$      :$$$.
$$$       $$$$$$7$$$$$$$$$$$$    .$$$. 
$$$        $$$   7$$$7  .$$$    .$$$.  
$$$$             $$$$7         .$$$.   
7$$$7            7$$$$        7$$$     
 $$$$$                        $$$      
  $$$$7.                       $$  (TM)    
   $$$$$$$.           .7$$$$$$  $$     
     $$$$$$$$$$$$7$$$$$$$$$.$$$$$$     
       $$$$$$$$$$$$$$$$.               

configure: Package configured for:
configure: OS type  : linux-gnu
configure: Host CPU : x86_64
configure: build-cpu:vendor:os: x86_64 : pc : linux-gnu :
configure: host-cpu:vendor:os: x86_64 : pc : linux-gnu :


make

#if all goes well you should see this

   [CC] res_musiconhold.c -> res_musiconhold.o
   [LD] res_musiconhold.o -> res_musiconhold.so
   [CC] res_adsi.c -> res_adsi.o
   [LD] res_adsi.o -> res_adsi.so
   [CC] res_limit.c -> res_limit.o
   [LD] res_limit.o -> res_limit.so
   [CC] res_rtp_multicast.c -> res_rtp_multicast.o
   [LD] res_rtp_multicast.o -> res_rtp_multicast.so
   [CC] res_smdi.c -> res_smdi.o
   [LD] res_smdi.o -> res_smdi.so
   [CC] res_pjsip_authenticator_digest.c -> res_pjsip_authenticator_digest.o
   [LD] res_pjsip_authenticator_digest.o -> res_pjsip_authenticator_digest.so
   [CC] res_pjsip_transport_websocket.c -> res_pjsip_transport_websocket.o
   [LD] res_pjsip_transport_websocket.o -> res_pjsip_transport_websocket.so
   [CC] res_ari_events.c -> res_ari_events.o
   [CC] ari/resource_events.c -> ari/resource_events.o
   [LD] res_ari_events.o ari/resource_events.o -> res_ari_events.so
Building Documentation For: third-party channels pbx apps codecs formats cdr cel bridges funcs tests main res addons
 +--------- Asterisk Build Complete ---------+
 + Asterisk has successfully been built, and +
 + can be installed by running:              +
 +                                           +
 +                make install               +
 +-------------------------------------------+


#if it still went well then install it!

make install

 +---- Asterisk Installation Complete -------+
 +                                           +
 +    YOU MUST READ THE SECURITY DOCUMENT    +
 +                                           +
 + Asterisk has successfully been installed. +
 + If you would like to install the sample   +
 + configuration files (overwriting any      +
 + existing config files), run:              +
 +                                           +
 + For generic reference documentation:      +
 +    make samples                           +
 +                                           +
 + For a sample basic PBX:                   +
 +    make basic-pbx                         +
 +                                           +
 +                                           +
 +-----------------  or ---------------------+
 +                                           +
 + You can go ahead and install the asterisk +
 + program documentation now or later run:   +
 +                                           +
 +               make progdocs               +
 +                                           +
 + **Note** This requires that you have      +
 + doxygen installed on your local system    +
 +-------------------------------------------+
 

Use fdisk on your USB drive to create a bootable NTFS partition (in my case /dev/sdb):

 sudo fdisk /dev/sdb

Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.



Command (m for help): n
Partition type
   p   primary (0 primary, 0 extended, 4 free)
   e   extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1):
First sector (2048-30218841, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-30218841, default 30218841):

Created a new partition 1 of type 'Linux' and of size 14.4 GiB.




Command (m for help): t

Command (m for help): t
Selected partition 1
Partition type (type L to list all types): 7
Changed type of partition 'NTFS volume set' to 'HPFS/NTFS/exFAT'.

Command (m for help): a

Selected partition 1
The bootable flag on partition 1 is enabled now.




Command (m for help): wq
The partition table has been altered.
Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Device or resource busy

The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).




Disk /dev/sdb: 14.4 GiB, 15472047104 bytes, 30218842 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x45b30652

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdb1  *     2048 30218841 30216794 14.4G  7 HPFS/NTFS/exFAT


Make an NTFS fs on /dev/sdb1

sudo mkfs -t ntfs /dev/sdb1
Cluster size has been automatically set to 4096 bytes.
Initializing device with zeroes: 100% - Done.
Creating NTFS volume structures.
mkntfs completed successfully. Have a nice day.
 

Now copy the iso to your partition (in my case /dev/sdb1)

sudo mount -o loop windows.iso mountpoint


cp -a mountpoint/* /mnt/sdb1/

Now put an MBR on it:

sudo dd if=/usr/lib/syslinux/mbr/mbr.bin of=/dev/sdb

There are many ways but a favorite way is to boot any Linux LiveCD and to use the syslinux package like so:

ssh -L 2222:192.168.1.17:22 -p 25000 -D 10000 root@154.20.103.246

Just change the "sdx" to your sd for example /dev/sda or whatever the drive is that is supposed to boot Windows.

 sudo dd if=/usr/lib/syslinux/mbr/mbr.bin of=/dev/sdx
0+1 records in
0+1 records out
440 bytes copied, 0.0197808 s, 22.2 kB/s


If you are using the default "Image Viewer" aka Xviewer it seems to die on very large resolution files.  It seems to understand to scale them but the printer will try to print and then fail.

Using "Pix" viewer seems to fix this and causes these larger files to print just fine.

If you can print other PDFs but not a particular one it is very likely that the PDF size is A4 (the longer, skinnier Asian paper size) instead of the North American letter size ( 8.5" x 11").  This breaks printing in most cases.  Or it may print if you find a program that ignores the size issue.

Here is an example of an A4 being rejected by a printer in Ubuntu Linux via CUPS

Cannot print PDF CUPS Samsung C460:

Processing - Remote host did not accept data file (104).

I tried ImageMagick's convert but it did not work properly., the resulting output was either too small and too fuzzy.  Increasing density also has the effect of making the PDF smaller and more distorted.  Eg. a density of 300 vs 72 produces a smaller file size.

convert thefile.pdf -density "300" -resize "2550x3300" thefile-lettersize.pdf

convert thefile.pdf -units pixelsperinch -density 72 -page letter thefile-lettersize.pdf

The Solution - gs ghostscript to the rescue

the gs binary (ghostscript) is what fixed it using the command below.

  gs -o outputfile.pdf -sDEVICE=pdfwrite -dPDFFitPage -r72x72 -g2550x3300 sourcethefile.pdf

All you need to change is the -o outputfile.pdf (to the path of your outputfile) and change "sourcethefile.pdf" to the pdf that you want to resize. 

-r72x72 means 72 dpi.  You can change it to whatever you like but 72 works best.  In fact just like with ImageMagick when working with PDFs, a higher DPI actually creates a distorted, small pixelated result.

Bash Script to resize all .pdf's in the current dir to 8.5x11

The script just appends the name -85x11 to the original to all  PDF files in the current directory. 

for sourcefile in `ls -1 *.pdf`; do
      gs -o $sourcefile-85x11.pdf -sDEVICE=pdfwrite -dPDFFitPage -r72x72 -g2550x3300 $sourcefile
done

This is all controlled by /etc/issue

You can basically enter anything in there that you like, but there are preset variables that are mentioned at the end of the page that discuss this.

Some examples of /etc/issue:

Centos 7:


S
Kernel r on an m
 

Ubuntu 16.04:

Ubuntu 16.04.6 LTS n l

You can also insert any of the characters below preceded by a blackslash and it will insert the relevant information.

b   Insert the baudrate of the current line. d   Insert the current date. s   Insert the system name, the name of the operating system. l   Insert the name of the current tty line. m   Insert the architecture identifier of the machine, e.g., i686. n   Insert the nodename of the machine, also known as the hostname. o   Insert the domainname of the machine. r   Insert the release number of the kernel, e.g., 2.6.11.12. t   Insert the current time. u   Insert the number of current users logged in. U   Insert the string "1 user" or "<n> users" where <n> is the     number of current users logged in. v   Insert the version of the OS, e.g., the build-date etc.

A lot of times busy servers will have this issue and you cannot even force kill -9 the apachectl or httpd process:

[root@apachebox stats]# ps aux|grep httpd
root      1547  0.0  0.2 495452 32396 ?        Ds   Sep08   3:23 /usr/sbin/httpd
root      3543  0.0  0.0   6448   724 pts/1    S+   13:11   0:00 grep httpd
[root@apachebox stats]# kill -9 1547
[root@apachebox stats]# kill -9 1547
[root@apachebox stats]# kill -9 1547
[root@apachebox stats]# kill -9 1547
[root@apachebox stats]# kill -9 1547
[root@apachebox stats]# ps aux|grep httpd
root      1547  0.0  0.2 495452 32396 ?        Ds   Sep08   3:23 /usr/sbin/httpd
root      3545  0.0  0.0   6448   720 pts/1    S+   13:11   0:00 grep httpd
[root@apachebox stats]# ps aux|grep httpd
root      1547  0.0  0.2 495452 32396 ?        Ds   Sep08   3:23 /usr/sbin/httpd
root      3547  0.0  0.0   6448   724 pts/1    S+   13:11   0:00 grep httpd
[root@apachebox stats]# kill 1547
[root@apachebox stats]# ps aux|grep httpd
root      1547  0.0  0.2 495452 32396 ?        Ds   Sep08   3:23 /usr/sbin/httpd
root      3549  0.0  0.0   6448   724 pts/1    S+   13:11   0:00 grep httpd

#these didn't help:
service httpd stop
service network restart

#this fixed it!
service mysqld restart
service httpd restart


Basically it turned out that MySQL was holding the process open so killing or restarting MySQL seems to allow Apache to release.

Most of us know the heredoc method but what if you need a basic query done repeatedly and manually while working from bash?  It is a pain to manually type mysql and login each time. 

With this command below you can semi-automate those queries:

echo "use somedb; select * from auctions" | mysql -u root --password="yourpassword"

Just modify the above to suit your needs and you can add more queries by adding a semi-colon ; after each and just typing a new query.  Of course on the mysql command you will need to edit the user and password to suit your username and password.

Here is the longer heredoc version that is more flexible:


mysql -u user --password='yourpassword' << eof
use somedb;


select * from auctions;
eof

If you want to make the above more dynamic you could do this:

query="CREATE database $db;GRANT ALL on $db.* to $user@localhost IDENTIFIED by '$password'
"
mysql -u user --password='yourpassword' << eof
$query
eof

If you want to do the same thing with the piping you could make it like this:

query="CREATE database $db;GRANT ALL on $db.* to $user@localhost IDENTIFIED by '$password'
"

echo "$query" | mysql -u root --password="yourpassword"

It is very silly but the default on the ifup-eth script tells dhclient ( the program that obtains a DHCP IP address if you have selected DHCP in your ifcfg-eth* config file) to EXIT / QUIT if the first attempt to obtain a lease fails.

No amount of dhclient.conf settings will fix this because if dhclient is started with -1 (which it is by default) then dhclient will quit.

This is obviously very bad for MOST cases.  Say for example you have a power outage or you initially power on the system, if for some reason the link takes a few more seconds to come up, dhclient has probably already quit being unable to obtain a lease the first time.

So the option to set in your ifcfg-eth0 config file to solve the dhclient persistent issue:

PERSISTENT_DHCLIENT=1

The difference in how dhclient is started now looks like this:

/sbin/dhclient -H hostname -q -lf /var/lib/dhclient/dhclient-eth0.leases -pf /var/run/dhclient-eth0.pid eth0

If you don't have the option above you will see a "-1" which indicates that it would quit if the first lease attempt fails:

/sbin/dhclient -H hostname -1 -q -lf /var/lib/dhclient/dhclient-eth0.leases -pf /var/run/dhclient-eth0.pid eth0

Oct 18 11:06:46 server systemd[529]: rc-local.service: Failed at step EXEC spawning /etc/rc.local: Exec format error
Oct 18 11:06:46 server systemd[1]: rc-local.service: Control process exited, code=exited status=203
Oct 18 11:06:46 server systemd[1]: Failed to start /etc/rc.local Compatibility.
Oct 18 11:06:46 server systemd[1]: rc-local.service: Unit entered failed state.
Oct 18 11:06:46 server systemd[1]: rc-local.service: Failed with result 'exit-code'.

If you get the "Exec format error" then it is probably because your rc.local is not formatted correctly.  Specifically, it must have #!/bin/sh -e at the top or it will not work.

Make sure you have this at the top of /etc/rc.local

#!/bin/sh -e

Also remember that for rc.local to be used you must start or enable the "rc-local" service:

systemctl enable rc-local

Create Database:

create database yourdbname;

Show All Databases:

show databases;

Change Database:

use mysql;

Drop / Delete a MySQL Database:

drop database nameofyourdatabase;

mysql> drop database cardb;
Query OK, 1 row affected (0.10 sec)
 

How To Dump The Table Structure SQL Code:

show create table yourtablename;

View tables in database:

show tables;

View table structure:

describe yourtablename;

How To Change a Column Field:

Make sure you edit what is in bold to suit your table name, column name and type (eg. int, varchar, text).

alter table yourtable modify column columname int;

Create a new user and password for your database:

myfirstdb is the name of your database and the .* grants the same privileges to all tables (you could fine tune this by replacing the * with a table name).

yourusername is the username

yourpassword is the password

After grant are the privileges, if you want to give them full access you could just use "GRANT ALL" or if you want to restrict them to only reading you could just use "GRANT SELECT" and any other number of options that meet your needs for security.

GRANT SELECT, INSERT, DELETE on myfirstdb.* to yourusername@localhost IDENTIFIED BY 'yourpassword';

Adjust to suit your needs.  Currently this would kill any whois process running for more than 30 seconds or more than 1 minute.

Add it as a cronjob.  The motivation is that some commands have no timeout and just end up using up CPU and memory for no reason while never exiting to free resources.

#!/bin/bash
IFS=$(echo -en "nb")
for pid in `ps aux|grep whois`; do

    echo "pid=::$pid::"
    id=`echo "$pid"|awk '{print $2}'`
     echo "id=$id"
    runningseconds=`echo "$pid"|awk '{print $10}'|cut -f 2 -d ":"`
    runningminutes=`echo "$pid"|awk '{print $10}'|cut -f 1 -d ":"`

    echo "running seconds=$runningseconds"

    if [ $runningseconds -gt 30 ] || [ $runningminutes -gt 1 ]; then
        echo "seconds running is greater than 30 or minutes greater than 1"
        echo "kill -9 $id"
        kill -9 $id
    fi

done


Just edit your tftp file for xinetd like this:

*Change the IP to be the IP of the interface you want to listen on.

To test if your tftp is available on a certain IP range use nc -u yourip 69 to see if you can still connect (/var/log/messages or /var/log/syslog) should show the connection if it is open.

Oct 13 23:20:34 01 xinetd[26631]: Started working: 1 available service
Oct 13 23:20:40 01 xinetd[26631]: START: tftp pid=26634 from=192.5.9.1
 

service tftp
{
        socket_type             = dgram
        protocol                = udp
        wait                    = yes
        user                    = root
        server                  = /usr/sbin/in.tftpd
        server_args             = -s /tftpboot
        disable                 = no
        bind                    = 10.10.10.1
        per_source              = 11
        cps                     = 100 2
        flags                   = IPv4
}


sudo pip3 install python-docx
[sudo] password for :
Downloading/unpacking python-docx
  Downloading python-docx-0.8.10.tar.gz (5.5MB): 5.5MB downloaded
  Running setup.py (path:/tmp/pip_build_root/python-docx/setup.py) egg_info for package python-docx
   
    no previously-included directories found matching 'docs/.build'
    warning: no previously-included files matching '.DS_Store' found anywhere in distribution
    warning: no previously-included files matching '__pycache__' found anywhere in distribution
    warning: no previously-included files matching '*.py[co]' found anywhere in distribution
Requirement already satisfied (use --upgrade to upgrade): lxml>=2.3.2 in /usr/lib/python3/dist-packages (from python-docx)
Installing collected packages: python-docx
  Running setup.py install for python-docx
    error: can't copy 'docx/templates/default-docx-template': doesn't exist or not a regular file
    Complete output from command /usr/bin/python3 -c "import setuptools, tokenize;__file__='/tmp/pip_build_root/python-docx/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('rn', 'n'), __file__, 'exec'))" install --record /tmp/pip-wih17ymp-record/install-record.txt --single-version-externally-managed --compile:
    running install

running build

running build_py

creating build

creating build/lib

creating build/lib/docx

copying docx/blkcntnr.py -> build/lib/docx

copying docx/settings.py -> build/lib/docx

copying docx/table.py -> build/lib/docx

copying docx/package.py -> build/lib/docx

copying docx/shared.py -> build/lib/docx

copying docx/exceptions.py -> build/lib/docx

copying docx/api.py -> build/lib/docx

copying docx/section.py -> build/lib/docx

copying docx/document.py -> build/lib/docx

copying docx/__init__.py -> build/lib/docx

copying docx/compat.py -> build/lib/docx

copying docx/shape.py -> build/lib/docx

creating build/lib/docx/styles

copying docx/styles/style.py -> build/lib/docx/styles

copying docx/styles/styles.py -> build/lib/docx/styles

copying docx/styles/latent.py -> build/lib/docx/styles

copying docx/styles/__init__.py -> build/lib/docx/styles

creating build/lib/docx/parts

copying docx/parts/settings.py -> build/lib/docx/parts

copying docx/parts/hdrftr.py -> build/lib/docx/parts

copying docx/parts/styles.py -> build/lib/docx/parts

copying docx/parts/story.py -> build/lib/docx/parts

copying docx/parts/document.py -> build/lib/docx/parts

copying docx/parts/__init__.py -> build/lib/docx/parts

copying docx/parts/numbering.py -> build/lib/docx/parts

copying docx/parts/image.py -> build/lib/docx/parts

creating build/lib/docx/oxml

copying docx/oxml/coreprops.py -> build/lib/docx/oxml

copying docx/oxml/settings.py -> build/lib/docx/oxml

copying docx/oxml/table.py -> build/lib/docx/oxml

copying docx/oxml/shared.py -> build/lib/docx/oxml

copying docx/oxml/exceptions.py -> build/lib/docx/oxml

copying docx/oxml/xmlchemy.py -> build/lib/docx/oxml

copying docx/oxml/styles.py -> build/lib/docx/oxml

copying docx/oxml/simpletypes.py -> build/lib/docx/oxml

copying docx/oxml/section.py -> build/lib/docx/oxml

copying docx/oxml/document.py -> build/lib/docx/oxml

copying docx/oxml/__init__.py -> build/lib/docx/oxml

copying docx/oxml/ns.py -> build/lib/docx/oxml

copying docx/oxml/shape.py -> build/lib/docx/oxml

copying docx/oxml/numbering.py -> build/lib/docx/oxml

creating build/lib/docx/dml

copying docx/dml/color.py -> build/lib/docx/dml

copying docx/dml/__init__.py -> build/lib/docx/dml

creating build/lib/docx/text

copying docx/text/parfmt.py -> build/lib/docx/text

copying docx/text/font.py -> build/lib/docx/text

copying docx/text/run.py -> build/lib/docx/text

copying docx/text/__init__.py -> build/lib/docx/text

copying docx/text/paragraph.py -> build/lib/docx/text

copying docx/text/tabstops.py -> build/lib/docx/text

creating build/lib/docx/image

copying docx/image/constants.py -> build/lib/docx/image

copying docx/image/gif.py -> build/lib/docx/image

copying docx/image/exceptions.py -> build/lib/docx/image

copying docx/image/bmp.py -> build/lib/docx/image

copying docx/image/png.py -> build/lib/docx/image

copying docx/image/__init__.py -> build/lib/docx/image

copying docx/image/tiff.py -> build/lib/docx/image

copying docx/image/helpers.py -> build/lib/docx/image

copying docx/image/jpeg.py -> build/lib/docx/image

copying docx/image/image.py -> build/lib/docx/image

creating build/lib/docx/opc

copying docx/opc/coreprops.py -> build/lib/docx/opc

copying docx/opc/constants.py -> build/lib/docx/opc

copying docx/opc/part.py -> build/lib/docx/opc

copying docx/opc/spec.py -> build/lib/docx/opc

copying docx/opc/pkgwriter.py -> build/lib/docx/opc

copying docx/opc/oxml.py -> build/lib/docx/opc

copying docx/opc/package.py -> build/lib/docx/opc

copying docx/opc/shared.py -> build/lib/docx/opc

copying docx/opc/exceptions.py -> build/lib/docx/opc

copying docx/opc/phys_pkg.py -> build/lib/docx/opc

copying docx/opc/rel.py -> build/lib/docx/opc

copying docx/opc/__init__.py -> build/lib/docx/opc

copying docx/opc/compat.py -> build/lib/docx/opc

copying docx/opc/pkgreader.py -> build/lib/docx/opc

copying docx/opc/packuri.py -> build/lib/docx/opc

creating build/lib/docx/enum

copying docx/enum/base.py -> build/lib/docx/enum

copying docx/enum/table.py -> build/lib/docx/enum

copying docx/enum/style.py -> build/lib/docx/enum

copying docx/enum/dml.py -> build/lib/docx/enum

copying docx/enum/text.py -> build/lib/docx/enum

copying docx/enum/section.py -> build/lib/docx/enum

copying docx/enum/__init__.py -> build/lib/docx/enum

copying docx/enum/shape.py -> build/lib/docx/enum

creating build/lib/docx/oxml/text

copying docx/oxml/text/parfmt.py -> build/lib/docx/oxml/text

copying docx/oxml/text/font.py -> build/lib/docx/oxml/text

copying docx/oxml/text/run.py -> build/lib/docx/oxml/text

copying docx/oxml/text/__init__.py -> build/lib/docx/oxml/text

copying docx/oxml/text/paragraph.py -> build/lib/docx/oxml/text

creating build/lib/docx/opc/parts

copying docx/opc/parts/coreprops.py -> build/lib/docx/opc/parts

copying docx/opc/parts/__init__.py -> build/lib/docx/opc/parts

creating build/lib/docx/templates

copying docx/templates/default-settings.xml -> build/lib/docx/templates

copying docx/templates/default-header.xml -> build/lib/docx/templates

copying docx/templates/default-footer.xml -> build/lib/docx/templates

copying docx/templates/default.docx -> build/lib/docx/templates

copying docx/templates/default-styles.xml -> build/lib/docx/templates

error: can't copy 'docx/templates/default-docx-template': doesn't exist or not a regular file

----------------------------------------
Cleaning up...
Command /usr/bin/python3 -c "import setuptools, tokenize;__file__='/tmp/pip_build_root/python-docx/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('rn', 'n'), __file__, 'exec'))" install --record /tmp/pip-wih17ymp-record/install-record.txt --single-version-externally-managed --compile failed with error code 1 in /tmp/pip_build_root/python-docx
Storing debug log for failure in /home//.pip/pip.log



sudo pip3 install -U setuptools
Downloading/unpacking setuptools from https://files.pythonhosted.org/packages/6a/9a/50fadfd53ec909e4399b67c74cc7f4e883488035cfcdb90b685758fa8b34/setuptools-41.4.0-py2.py3-none-any.whl#sha256=8d01f7ee4191d9fdcd9cc5796f75199deccb25b154eba82d44d6a042cf873670
  Downloading setuptools-41.4.0-py2.py3-none-any.whl (580kB): 580kB downloaded
Installing collected packages: setuptools
  Found existing installation: setuptools 3.3
    Not uninstalling setuptools at /usr/lib/python3/dist-packages, owned by OS
Successfully installed setuptools
Cleaning up...



sudo pip3 install python-docx
Downloading/unpacking python-docx
  Downloading python-docx-0.8.10.tar.gz (5.5MB): 5.5MB downloaded
  Running setup.py (path:/tmp/pip_build_root/python-docx/setup.py) egg_info for package python-docx
    /tmp/pip_build_root/python-docx/setup.py:12: PkgResourcesDeprecationWarning: Parameters to load are deprecated.  Call .resolve and .require separately.
      this file.
    no previously-included directories found matching 'docs/.build'
    warning: no previously-included files matching '.DS_Store' found anywhere in distribution
    warning: no previously-included files matching '__pycache__' found anywhere in distribution
    warning: no previously-included files matching '*.py[co]' found anywhere in distribution
Requirement already satisfied (use --upgrade to upgrade): lxml>=2.3.2 in /usr/lib/python3/dist-packages (from python-docx)
Installing collected packages: python-docx
  Running setup.py install for python-docx
    no previously-included directories found matching 'docs/.build'
    warning: no previously-included files matching '.DS_Store' found anywhere in distribution
    warning: no previously-included files matching '__pycache__' found anywhere in distribution
    warning: no previously-included files matching '*.py[co]' found anywhere in distribution
  Could not find .egg-info directory in install record for python-docx
Successfully installed python-docx
Cleaning up...
 

Getting started, let's enable ephones and DNs we can add a phone with a telephone number:

Router>en
Router#conf t
Router(config)#telephony-service

!this enables ephone registration otherwise phones cannot register
Router(config-telephony)#ephone-reg

!max-ephones 2 says we can have a maximum of 2 phones, change to your needs (or to the limit set by your IOS image)
Router(config-telephony)#max-ephones 2
 

!set the source address of the voice traffic which should be our router's IP address

Router(config-telephony)#ip source-address
192.168.5.1 port 2000

!let's include the following message on the phone for the user: change YourName VOIP to whatever you would like them to see such as your organization name etc..

Router(config-telephony)#system message YourName
VOIP

!this creates the conf files
Router(config-telephony)#create cnf-files
Post-init cnf creation is in progress, pls re-issue this command later

! set  your clock before  creating cnf-files
Router(config-telephony)#
CNF-FILES: Clock is not set or synchronized, retaining old versionStamps

CNF files update complete (post init)
 

!this below should happen if your CME and phone are setup right.  Take the SEP out of and use it as the MAC address later
*Sep 29 21:57:13.467: %IPPHONE-6-REGISTER_NEW: ephone-1:SEP525400123456 IP:192.168.1.199 Socket:1 DeviceType:Phone has registered.
 

!this creates our first telephone number (the 1 stands for the ID, not the number)
Router(config)#ephone-dn 1

!now we set the actual phone number or extension
Router(config-ephone-dn)#number 7871

!now we set a name that it shows on the phone and is also visible to people they call
Router(config-ephone-dn)#name Firstname Lastname

!now we create our first phone ID #1
Router(config-telephony)#ephone 1

!now we map our first button on the phone screen to ephone-dn 1 (actual number 7871) from earlier
Router(config-ephone)#button 1:1

!we will get the error below if we don't add the mac-address first
Need to configure ephone mac address or VM station-id

! add the mac address like below before you can map the button.  Mapping the MAC address is actually assigning the phone to ephone ID #1

Router(config-ephone)#mac-address 5254.0012.3456

restart a phone remotely:

r2(config)#ephone 1
r2(config-ephone)#restart
restarting 5254.0012.3456

figure out which phone number is assigned to which phone:

Router#show ephone telephone-number 7871   
DP tag: 0, primary
Tag 1, Normal or Intercom dn
  ephone 1, mac-address 5254.0012.3456, line 1
 

show summary of all ephones:

Router#show ephone summary

hairpin_block:
ephone-1[0] Mac:5254.0012.3456 TCP socket:[1] activeLine:0 whisperLine:0 REGISTERED
mediaActive:0 whisper_mediaActive:0 startMedia:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0  primary_dn: 1*
IP:192.168.5.6 CIPC  keepalive 1006   music 0  1:1

Max 2, Registered 1, Unregistered 0, Deceased 0 High Water Mark 3, Sockets 1
ephone_send_packet process switched 0


Max Conferences 4 with 0 active (4 allowed)
Skinny Music On Hold Status
Active MOH clients 0 (max 600), Media Clients 0, B-ACD Clients 0
No MOH file loaded

show registered ephones:

Router#show ephone registered


ephone-1[0] Mac:5254.0012.3456 TCP socket:[1] activeLine:0 whisperLine:0 REGISTERED in SCCP ver 20/12 max_streams=5
mediaActive:0 whisper_mediaActive:0 startMedia:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0 caps:11
IP:192.168.5.6 50786 CIPC  keepalive 1005 max_line 8 available_line 8
button 1: dn 1  number 7871 CH1   IDLE        
Preferred Codec: g711ulaw
 

show phones that tried to register (but probably couldn't for some reason):

show ephone attempted-registrations

show what phone a DN ID number is assigned to (in this case we use 1)

Router#show ephone dn 1
Tag 1, Normal or Intercom dn
  ephone 1, mac-address 5254.0012.3456, line 1
 

Voice Routing

show our dialpeer information/routing:

Router#show dial-peer voice summary
dial-peer hunt 0
             AD                                    PRE PASS                OUT
TAG    TYPE  MIN  OPER PREFIX    DEST-PATTERN      FER THRU SESS-TARGET    STAT PORT
20001  pots  up   down                              0                           50/0/2
20002  pots  up   up             7871$              0                           50/0/1

show detailed information about a dialpeer (eg. TAG 20002):

Router#show dial-peer voice 20002
VoiceEncapPeer20002
    peer type = voice, system default peer = FALSE, information type = voice,
    description = `',
    tag = 20002, destination-pattern = `',
    voice reg type = 0, corresponding tag = 0,
    allow watch = FALSE
    answer-address = `', preference=0,
    CLID Restriction = None
    CLID Network Number = `'
    CLID Second Number sent
    CLID Override RDNIS = disabled,
    rtp-ssrc mux = system
    source carrier-id = `',    target carrier-id = `',
    source trunk-group-label = `',    target trunk-group-label = `',
    numbering Type = `unknown'
    group = 20002, Admin state is up, Operation state is down,
    incoming called-number = `', connections/maximum = 0/unlimited,
    DTMF Relay = disabled,
    URI classes:
        Destination =
    huntstop = enabled,
    in bound application associated: 'DEFAULT'
    out bound application associated: ''
        dnis-map =
        permission :both
        incoming COR list:maximum capability
        outgoing COR list:minimum requirement
        Translation profile (Incoming):
        Translation profile (Outgoing):
        incoming call blocking:
        translation-profile = `'
        disconnect-cause = `no-service'
        advertise 0x40 capacity_update_timer 25 addrFamily 4 oldAddrFamily 4
        mailbox selection policy: none
        type = pots, prefix = `',
        forward-digits 0
        session-target = `', voice-port = `50/0/2',
        direct-inward-dial = disabled,
        digit_strip = enabled,
        register E.164 number with H323 GK and/or SIP Registrar = TRUE
        fax rate = system,   payload size =  20 bytes
        supported-language = ''
        dial tone generation after remote onhook = enabled
        mobility=0, snr=, snr_noan=, snr_delay=0, snr_timeout=0
        Time elapsed since last clearing of voice call statistics never
        Connect Time = 0, Charged Units = 0,
        Successful Calls = 0, Failed Calls = 0, Incomplete Calls = 0
        Accepted Calls = 0, Refused Calls = 0,
        Last Disconnect Cause is "",
        Last Disconnect Text is "",
        Last Setup Time = 0.
        Last Disconnect Time = 0.

enable dialpeer debugging:

Router#debug voip dialpeer  
voip dialpeer default debugging is on
 

create a voip dialpeer:

The below creates a dialpeer tag "7861" of type VOIP (IP-based and not analog port based)

It sets the destination pattern of 7861 (it means that for when we dial 7861 on the phone) it will be sent to a dial peer on IP 192.168.5.1

r2(config)#dial-peer voice 7861 voip
r2(config-dial-peer)#destination-pattern 7861
r2(config-dial-peer)#session target ipv4:192.168.5.1

dialpeers are two ways, so for calls to be successful between the parties, let's say we have another phone 7871 on router r2 192.168.5.99.  How can it reach back to 7861 if we don't tell it? 

This shows us how to reach 7871 by 192.168.5.99

r1(config)#dial-peer voice 7871 voip
r1(config-dial-peer)#destination-pattern 7871
r1(config-dial-peer)#session target ipv4:192.168.5.99

COR

1. Create COR Tags:

Eg. we are going to create 3 COR Tags, 911, Long Distance and Local Calling which enforces restrictions on the numbers associated with the COR rules.

r2(config)#dial-peer cor custom
r2(config-dp-cor)#name 911

r2(config-dp-cor)#name LongDistance
r2(config-dp-cor)#name Local

Let's view our COR tags:

r2#show dial-peer cor

Class of Restriction
  name: 911
  name: Local
  name: LongDistance
 

2. Create the outgoing COR Lists and associate them with the tags we created earlier as members.

!we assign our 911 tag to a COR list we call 911-OUT

r2(config-telephony)#dial-peer cor list 911-OUT
r2(config-dp-corlist)#member 911
 

!we assign our Local tag to a COR list we call Local-OUT

r2(config-dp-corlist)#dial-peer cor list Local-OUT
r2(config-dp-corlist)#member Local
 

!we assign our LongDistance tag to a COR list we call LongDistance-OUT

r2(config-dp-corlist)#dial-peer cor list LongDistance-OUT
r2(config-dp-corlist)#member LongDistance

3. Create the incoming COR Lists and associate them with the tags we created earlier as members.

Notice that this incoming COR list is more like a database with multiple members.  It is a logical way to name them with a - to include all of their member functionality
 

r2(config-dp-corlist)#dial-peer cor list 911-ONLY
r2(config-dp-corlist)#member 911
 

r2(config-dp-corlist)#dial-peer cor list 911-LOCAL
r2(config-dp-corlist)#member 911
r2(config-dp-corlist)#member Local

r2(config-dp-corlist)#dial-peer cor list 911-LOCAL-LONGDISTANCE
r2(config-dp-corlist)#member 911
r2(config-dp-corlist)#member Local
r2(config-dp-corlist)#member LongDistance

We have our cor tags and incoming and outgoing lists but we still have to associate them with actual dial-peers for them to take effect.

Keeping track of things let's look at our current cor tags and lists:

do show dial-peer cor

Class of Restriction
  name: 911
  name: Local
  name: LongDistance

COR list <911-OUT>
  member: 911

COR list
  member: Local

COR list
  member: LongDistance

COR list <911-ONLY>
  member: 911

COR list <911-LOCAL>
  member: 911
  member: Local

COR list <911-LOCAL-LONGDISTANCE>
  member: 911
  member: Local
  member: LongDistance
 

Now we have to assign outgoing call lists to the dial-peer of the phone numbers we want to have these COR restrictions

r2(config-dial-peer)#dial-peer voice 1
r2(config-dial-peer)#corlist outgoing 911-OUT

Now we have to assign incoming call lists to the relevant DNs:

r2(config)#ephone-dn 1
r2(config-ephone-dn)#corlist incoming 911-ONLY

 service sshd status
● ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
   Active: failed (Result: start-limit-hit) since Wed 2019-10-02 11:07:54 EDT; 36s ago
  Process: 476 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255)

Oct 02 11:07:54 box systemd[1]: Failed to start OpenBSD Secure Shell server.
Oct 02 11:07:54 box systemd[1]: ssh.service: Unit entered failed state.
Oct 02 11:07:54 box systemd[1]: ssh.service: Failed with result 'exit-code'.
Oct 02 11:07:54 box systemd[1]: ssh.service: Service hold-off time over, scheduling restart.
Oct 02 11:07:54 box systemd[1]: Stopped OpenBSD Secure Shell server.
Oct 02 11:07:54 box systemd[1]: ssh.service: Start request repeated too quickly.
Oct 02 11:07:54 box systemd[1]: Failed to start OpenBSD Secure Shell server.
Oct 02 11:07:54 box systemd[1]: ssh.service: Unit entered failed state.
Oct 02 11:07:54 box systemd[1]: ssh.service: Failed with result 'start-limit-hit'.

Oct  2 11:09:08 box sshd[511]: Missing privilege separation directory: /var/run/sshd
Oct  2 11:09:08 box systemd[1]: ssh.service: Control process exited, code=exited status=255
Oct  2 11:09:08 box systemd[1]: Failed to start OpenBSD Secure Shell server.
Oct  2 11:09:08 box systemd[1]: ssh.service: Unit entered failed state.
Oct  2 11:09:08 box systemd[1]: ssh.service: Failed with result 'exit-code'.
Oct  2 11:09:08 box systemd[1]: ssh.service: Service hold-off time over, scheduling restart.

Solution

mkdir -p /var/run/sshd
echo "mkdir -p /var/run/sshd" >> /etc/rc.local

This is just if we have an output line.  wc we know can count lines but the -w flag will count words:

echo "I have this line here" |wc -w



5

A common method in bash is to assign output to a variable like this:

somevar=`uptime`

That works too but it could be more efficient to do something like this:

if [[ $(uptime|awk '{print $3}') > 20 ]]; then


echo "uptime greater than 20 days";


fi


This often happens if you are adding a secondary route, especially with Linux source based routing.

ip route add default via 10.10.10.254 table 10
RTNETLINK answers: Network is unreachable

If that happens you will probably find that  it is unreachable because your NIC does not have an IP in the 10.10.10.0/24 range so just assign an IP in that range to your NIC and try again.

eg. ifconfig eth0 10.10.10.254 netmask 255.255.255.0 up

yum install iptables-services

systemctl enable iptables

service iptables save
iptables: Saving firewall rules to /etc/sysconfig/iptables:[  OK  ]


By default at least on Centos 7 nfs only allows 8 connections and starts 8 nfsd daemons. 

To fix this edit this file: /etc/sysconfig/nfs

Edit the line "RPCNFSDCOUNT"  (uncomment it so it looks like this:

RPCNFSDCOUNT=30
 

In the example above we are setting 30 nfsd daemons to run (or in other words 30 connections are possible this way).

Now older versions of qemu-kvm didn't throw this error say if you just had "-video cirrus" when starting qemu-kvm.  But newer versions do care.

And this probably only  applies to you if you are running from bash/terminal with remote kvm images.

What you need to do is remove the "-video" part and just add -vnc :5

eg. this would fix the error:

qemu-system-x86_64 -enable-kvm -boot order=cd,once=dc -m 1024 -drive file=/tmp/kvmuser786.img,if=virtio -vnc :5 -usbdevice tablet -net nic,macaddr=DE:AD:BE:EF:37:76 -net tap,ifname=tap0,script=no,downscript=no

eg. here is the command with the error:

qemu-system-x86_64 -enable-kvm -video cirrus -boot order=cd,once=dc -m 1024 -drive file=/root/kvmuser786/kvmuser786.img,if=virtio -usbdevice tablet -net nic,macaddr=DE:AD:BE:EF:37:76 -net tap,ifname=tap0,script=no,downscript=no

So the key is to remove the "-video cirrus" and then add the -vnc :5 (where 5 would be port 5905).

In Centos 7 tftpd will not work with selinux.  Clients will not be able to connect and this is all you'll see in the log (then nothing more):

Sep 18 14:39:15 localhost xinetd[4327]: START: tftp pid=4331 from=192.168.1.65

On the client/computer side you will see this:


TFTP.


PXE-M0F: Exiting Intel Boot Agent

Basically the client is being instantly connected and blocked by selinux.
 

The fix:

1.) disable selinux in /etc/selinux/config

2.) to instantly  (but temporarily disable) type setenforce 0
 

Having a network bridge allows you to bridge traffic under multiple devices so they can talk natively without using any special routing, iptables/firewall or other trickery.

To create your bridge you need the bridge-utils package for brctl and if you want to do things like bridge VMs that run on a tap   device you will need the uml-utilities which provides "tunctl".

Install the utilities to make our bridge

sudo apt-get install bridge-utils uml-utilities

Backup your interfaces file to your home dir

sudo cp /etc/network/interfaces ~/interfaces-`date +%Y-%m-%d-%s`

Edit your interfaces file like this:

In this case I have a public facing NIC enp0s9 which I do NOT want to bridge.

But I wanted to bridge my internal NIC enp0s8.  The first thing you do is set a line for the bridged NIC to just be manual (remove any IP config info whether static or DHCP from the NIC you want to bridge).

Disable the NIC you want to bridge

iface enp0s8 inet manual

Setup your bridge

For simplicity I am going to call it br0 but it could be called almost anything.

The key part is below in bold where I declare the br0:

iface br0 inet static
  bridge_ports enp0s8

Now of course I could use dhcp instead of static and that is where it would end (assuming you wanted to use DHCP). 

On the second line below indented you add "bridge_ports enp0s8" which defines enp0s8 as belonging to the br0 bridge.

Here is what it all looks like:

# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo enp0s9 br0
iface lo inet loopback
iface enp0s9 inet dhcp

iface enp0s8 inet manual
iface br0 inet static
  bridge_ports enp0s8
   address 192.168.1.1
   netmask 255.255.255.0
   gateway 192.168.1.1

By default your DHCP will often not work because it is not listening on any interfaces.

All you have to do is edit this file:

vi /etc/default/isc-dhcp-server

then find the "INTERFACES" line and add each interface that should listen:

INTERFACES="br0 enp0s10"




I think this is more so an issue with kernel modules not being included.  I had this issue on Linux Mint because a new kernel I upgraded to DID NOT have the "extra" modules and part of that reason is also because older kernels are named differently than new ones.

Take this example article below that shows it in action.
If you were previously able to type your password and a subsequent kernel update broke things here is the solution

Solution 1 - Install the "extra" kernel modules

Basically make sure that for your linux kernel that you have the "extra" or "modules-extra" additional kernel package installed if you have the problem that you cannot type your password at Boot to unlock LUKS.

The article above will show you what you need to do and this has resolved all of my issues with being unable to type my LUKS password at boot by adding the extra kernel modules.  I also found until i did this even my NIC did not work so really, I think all modules should be built into the kernel by default or the extras should be a depenency.

Solution 2 - grub quietboot option

In the kernel line in grub you could change "quiet" to "quietboot".  This will allow you to type the password.

I find this is not practical since often if you are lacking the modules to type your password, I found my NIC card didn't work too.

Solution 3 - hit Esc

Some report that hitting the Escape key will allow you to enter the password.  But once again I found for myself that you are probably going to have issues if other kernel modules for your device such as NIC are still missing.

This is something I've seen some run into.  Take an old install of Linux Mint 18.1

ii  linux-image-4.4.0-53-generic          4.4.0-53.74                                amd64        Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii  linux-image-extra-4.4.0-53-generic    4.4.0-53.74                                amd64        Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
 

The highlighted linux-image-extra-4.4.0-53-generic is the old naming convention of how we would make "our extra devices work".  Generally it includes extra drivers/kernel modules and for a lot of devices that I use (including often things like display drivers and especially NIC and Wifi cards).  So to be in the Debian/Mint/Buntu world these "extra" modules are not really optional.

Now take a look at a new 4.4.0 kernel if we try to use the same "extra" convention to get those modules:

sudo apt-get install linux-image-extra-4.4.0-150-generic

Reading package lists... Done
Building dependency tree      
Reading state information... Done
E: Unable to locate package linux-image-extra-4.4.0-150-generic
E: Couldn't find any package by glob 'linux-image-extra-4.4.0-150-generic'
E: Couldn't find any package by regex 'linux-image-extra-4.4.0-150-generic'


It can't find it as we can see above

Let's do a search of all kernel packages for the version 4.4.0-150-generic:

apt-cache search 4.4.0-150
linux-buildinfo-4.4.0-150-generic - Linux kernel buildinfo for version 4.4.0 on 64 bit x86 SMP
linux-buildinfo-4.4.0-150-lowlatency - Linux kernel buildinfo for version 4.4.0 on 64 bit x86 SMP
linux-cloud-tools-4.4.0-150 - Linux kernel version specific cloud tools for version 4.4.0-150
linux-cloud-tools-4.4.0-150-generic - Linux kernel version specific cloud tools for version 4.4.0-150
linux-cloud-tools-4.4.0-150-lowlatency - Linux kernel version specific cloud tools for version 4.4.0-150
linux-headers-4.4.0-150 - Header files related to Linux kernel version 4.4.0
linux-headers-4.4.0-150-generic - Linux kernel headers for version 4.4.0 on 64 bit x86 SMP
linux-headers-4.4.0-150-lowlatency - Linux kernel headers for version 4.4.0 on 64 bit x86 SMP
linux-image-4.4.0-150-generic - Signed kernel image generic
linux-image-4.4.0-150-lowlatency - Signed kernel image lowlatency
linux-image-unsigned-4.4.0-150-generic - Linux kernel image for version 4.4.0 on 64 bit x86 SMP
linux-image-unsigned-4.4.0-150-lowlatency - Linux kernel image for version 4.4.0 on 64 bit x86 SMP
linux-modules-4.4.0-150-generic - Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
linux-modules-4.4.0-150-lowlatency - Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
linux-modules-extra-4.4.0-150-generic - Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
linux-tools-4.4.0-150 - Linux kernel version specific tools for version 4.4.0-150
linux-tools-4.4.0-150-generic - Linux kernel version specific tools for version 4.4.0-150
linux-tools-4.4.0-150-lowlatency - Linux kernel version specific tools for version 4.4.0-150
 

The naming convention has changed and is now modules-extra "linux-modules-extra-4.4.0-150-generic" and this is what we need to install now.


sudo apt-get install linux-modules-extra-4.4.0-150-generic
Reading package lists... Done
Building dependency tree      
Reading state information... Done
The following NEW packages will be installed:
  linux-modules-extra-4.4.0-150-generic
0 upgraded, 1 newly installed, 0 to remove and 737 not upgraded.
Need to get 36.6 MB of archives.
After this operation, 156 MB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-modules-extra-4.4.0-150-generic amd64 4.4.0-150.176 [36.6 MB]
Fetched 36.6 MB in 3s (11.2 MB/s)                                
Selecting previously unselected package linux-modules-extra-4.4.0-150-generic.
(Reading database ... 252360 files and directories currently installed.)
Preparing to unpack .../linux-modules-extra-4.4.0-150-generic_4.4.0-150.176_amd64.deb ...
Unpacking linux-modules-extra-4.4.0-150-generic (4.4.0-150.176) ...
Setting up linux-modules-extra-4.4.0-150-generic (4.4.0-150.176) ...
Processing triggers for linux-image-4.4.0-150-generic (4.4.0-150.176) ...
/etc/kernel/postinst.d/dkms:
Error! echo
Your kernel headers for kernel 4.4.0-150-generic cannot be found at
/lib/modules/4.4.0-150-generic/build or /lib/modules/4.4.0-150-generic/source.
Error! echo
Your kernel headers for kernel 4.4.0-150-generic cannot be found at
/lib/modules/4.4.0-150-generic/build or /lib/modules/4.4.0-150-generic/source.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.4.0-150-generic
Warning: No support for locale: en_CA.utf8
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-4.4.0-150-generic
Found initrd image: /boot/initrd.img-4.4.0-150-generic
Found linux image: /boot/vmlinuz-4.4.0-53-generic
Found initrd image: /boot/initrd.img-4.4.0-53-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done


cat .htaccess
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . index.php [L]


I keep reading there is a "# BEGIN WordPress" and a "# END WordPress" in the wordpress htaccess above but there is clearly not.
Even more strange is that my permissions are just 444 (read only).


so i changed it to this (but it still gets wiped out)
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://areebyasir.com/$1 [R=301,L]

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . index.php [L]
</IfModule>
# END WordPress





RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://areebyasir.com/$1 [R=301,L]


#no matter what it just somehow replaces with this default file:

-r--r--r-- 1 apache apache 153 Jul  9  2017 .htaccess

Solution the format must be exactly like below:

Substitute your rules in bold below with whatever rules you want to add.

As you can see above if you don't do the ifmodule part it will not work.

<ifmodule mod_rewrite.c>
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://yourdomain.com/$1 [R=301,L]
</ifmodule>
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . index.php [L]
</IfModule>
# END WordPress

It is really simple using .htaccess with mod_rewrite.

Here is all you need:

RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://site.com/$1 [R=301,L]

Another more graceful way is to use the %{SERVER_NAME} variable to make it dynamic.  Just be careful that the server name will always match what you expect. (eg. if you are doing load balancing or clustering what if the server name may be something other than the public facing URL).

RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://%{SERVER_NAME}/$1 [R=301,L]

The above just detects that the user has connected with non-SSL by connecting to port 80.  When that condition is detected it just rewrites the url to the same thing only with https:// to "site.com" (make sure you change site.com to your domain)

python3 testserver.com-car-scraping.py html.txt
Traceback (most recent call last):
  File "testserver.com-car-scraping.py", line 5, in
    import mysql.connector
ImportError: No module named 'mysql'

For some reason it won't install properly even though I have the mysql client on this machine installed too.

Solution:

You need the mysqlclient-dev libraries for python mysql.


sudo apt-get install libmysqlclient-dev python3-dev

sudo pip3 install mysqlclient mysql mysql-connector-python

 pip3 install mysql
Downloading/unpacking mysql
  Downloading mysql-0.0.2.tar.gz
  Running setup.py (path:/tmp/pip_build_localuser/mysql/setup.py) egg_info for package mysql
    WARNING: `mysql` is a virtual package. Please use `%s` as a dependency directly.
   
   
Downloading/unpacking mysqlclient (from mysql)
  Downloading mysqlclient-1.4.4.tar.gz (86kB): 86kB downloaded
  Running setup.py (path:/tmp/pip_build_localuser/mysqlclient/setup.py) egg_info for package mysqlclient
    /bin/sh: 1: mysql_config: not found
    /bin/sh: 1: mariadb_config: not found
    /bin/sh: 1: mysql_config: not found
    Traceback (most recent call last):
      File "", line 17, in
      File "/tmp/pip_build_localuser/mysqlclient/setup.py", line 16, in
        metadata, options = get_config()
      File "/tmp/pip_build_localuser/mysqlclient/setup_posix.py", line 61, in get_config
        libs = mysql_config("libs")
      File "/tmp/pip_build_localuser/mysqlclient/setup_posix.py", line 29, in mysql_config
        raise EnvironmentError("%s not found" % (_mysql_config_path,))
    OSError: mysql_config not found
    Complete output from command python setup.py egg_info:
    /bin/sh: 1: mysql_config: not found

/bin/sh: 1: mariadb_config: not found

/bin/sh: 1: mysql_config: not found

Traceback (most recent call last):

  File "", line 17, in

  File "/tmp/pip_build_localuser/mysqlclient/setup.py", line 16, in

    metadata, options = get_config()

  File "/tmp/pip_build_localuser/mysqlclient/setup_posix.py", line 61, in get_config

    libs = mysql_config("libs")

  File "/tmp/pip_build_localuser/mysqlclient/setup_posix.py", line 29, in mysql_config

    raise EnvironmentError("%s not found" % (_mysql_config_path,))

OSError: mysql_config not found

----------------------------------------
Cleaning up...
Command python setup.py egg_info failed with error code 1 in /tmp/pip_build_localuser/mysqlclient
Storing debug log for failure in /tmp/tmp2bni2zx8

CPU: Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz

MOBO:         Manufacturer: ASUSTeK COMPUTER INC.
        Product Name: P8H61-M LX3 PLUS R2.0
 

qemu-kvm-0.12.1.2-2.506.el6_10.1.x86_64
 

This is weird but the only OS I've found this machine doesn't work with is Windows 2019 Server.  I have no idea, when 2008, 2012 work fine.  Windows 2019 also works with the same software (KVM version) on a different MOBO and CPU, so I suspect it is something CPU or MOBO related that is not playing nicely.

Solution:

Windows 2016+ (eg 2019) will NOT boot without using the "-cpu host" parameter which passes through the host CPU. 

On most machines I run, especially server hardware this doesn't seem to matter (eg. I normally just use the default QEMU-CPU and all is fine even on 2019 and 2016).

Here is an example:

qemu-system-x86_64 --enable-kvm -cpu host -smp 8 -m 8192 -drive format=raw,file=the-file.img

When booting my Windows 2019 template all I get is the Windows logo:

If you've just installed VBox and it is not starting or working, the most common problem is usually that you don't have your kernel source installed, which means there is no kernel driver for vbox so it can't work.

So the first thing you should do is install your kernel source by running this:

sudo apt-get install linux-headers-`uname -r`

Then install the dkms/kernel module for vbox

sudo apt-get install virtualbox-dkms

#overall solution if it doesn't work still

sudo apt-get update
sudo apt-get remove virtualbox virtualbox-qt virtualbox-dkms
sudo apt-get install linux-headers-`uname -r` virtualbox-qt
 

When things go wrong:

vboxweb.service is a disabled or a static unit, not starting it.
Job for virtualbox.service failed because the control process exited with error code. See "systemctl status virtualbox.service" and "journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
● virtualbox.service - LSB: VirtualBox Linux kernel module
   Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2019-07-20 15:01:39 PDT; 15ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 12405 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

Jul 20 15:01:39 areebuser-ZQ-Class systemd[1]: Starting LSB: VirtualBox Linux kernel module...
Jul 20 15:01:39 areebuser-ZQ-Class virtualbox[12405]:  * Loading VirtualBox kernel modules...
Jul 20 15:01:39 areebuser-ZQ-Class virtualbox[12405]:  * No suitable module for running kernel found
Jul 20 15:01:39 areebuser-ZQ-Class virtualbox[12405]:    ...fail!
Jul 20 15:01:39 areebuser-ZQ-Class systemd[1]: virtualbox.service: Control process exited, code=exited status=1
Jul 20 15:01:39 areebuser-ZQ-Class systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
Jul 20 15:01:39 areebuser-ZQ-Class systemd[1]: virtualbox.service: Unit entered failed state.
Jul 20 15:01:39 areebuser-ZQ-Class systemd[1]: virtualbox.service: Failed with result 'exit-code'.


-- Unit virtualbox.service has begun starting up.
Jul 20 15:01:39 areebuser-ZQ-Class virtualbox[12405]:  * Loading VirtualBox kernel modules...
Jul 20 15:01:39 areebuser-ZQ-Class virtualbox[12405]:  * No suitable module for running kernel found
Jul 20 15:01:39 areebuser-ZQ-Class virtualbox[12405]:    ...fail!
Jul 20 15:01:39 areebuser-ZQ-Class systemd[1]: virtualbox.service: Control

Reading package lists... Done
Building dependency tree      
Reading state information... Done
The following NEW packages will be installed:
  virtualbox-dkms
0 upgraded, 1 newly installed, 0 to remove and 85 not upgraded.
Need to get 0 B/651 kB of archives.
After this operation, 5,305 kB of additional disk space will be used.
Selecting previously unselected package virtualbox-dkms.
(Reading database ... 277724 files and directories currently installed.)
Preparing to unpack .../virtualbox-dkms_5.1.38-dfsg-0ubuntu1.16.04.3_all.deb ...
Unpacking virtualbox-dkms (5.1.38-dfsg-0ubuntu1.16.04.3) ...
Setting up virtualbox-dkms (5.1.38-dfsg-0ubuntu1.16.04.3) ...
Loading new virtualbox-5.1.38 DKMS files...
First Installation: checking all kernels...
Building only for 4.8.0-58-generic
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
Job for virtualbox.service failed because the control process exited with error code. See "systemctl status virtualbox.service" and "journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
● virtualbox.service - LSB: VirtualBox Linux kernel module
   Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2019-07-22 16:43:23 PDT; 12ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 3046 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

Jul 22 16:43:23 user-ZQ-Class systemd[1]: Starting LSB: VirtualBox Linu....
Jul 22 16:43:23 user-ZQ-Class virtualbox[3046]:  * Loading VirtualBox ke...
Jul 22 16:43:23 user-ZQ-Class virtualbox[3046]:  * No suitable module fo...
Jul 22 16:43:23 user-ZQ-Class virtualbox[3046]:    ...fail!
Jul 22 16:43:23 user-ZQ-Class systemd[1]: virtualbox.service: Control p...1
Jul 22 16:43:23 user-ZQ-Class systemd[1]: Failed to start LSB: VirtualB....
Jul 22 16:43:23 user-ZQ-Class systemd[1]: virtualbox.service: Unit
ente....
Jul 22 16:43:23 user-ZQ-Class systemd[1]: virtualbox.service: Failed wi....
Hint: Some lines were ellipsized, use -l to show in full.


 

By default bind will not respond to outside queries for security reasons.

In most distributions you will find the default in /etc/named.conf looks like this at the top under options:

      listen-on port 53 { 127.0.0.1; };
      listen-on-v6 port 53 { ::1; };
        directory       "/var/named";
        dump-file       "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
        memstatistics-file "/var/named/data/named_mem_stats.txt";
      allow-query     { localhost; };

The options above in bold are the reason you can't hit your DNS server from the outside:

A quick and dirty solution is to just comment out those lines and restart named.

After that you will be able to respond to queries from the outside.

You could also specify a certain IP range if this DNS server is only intended for your LAN users.

//      listen-on port 53 { 127.0.0.1; };
//      listen-on-v6 port 53 { ::1; };
        directory       "/var/named";
        dump-file       "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
        memstatistics-file "/var/named/data/named_mem_stats.txt";
//      allow-query     { localhost; };


The way of doing it in mint is different than gnome and ubuntu.

gsettings set org.mate.background picture-filename /path/to/file.jpg

*If you try to use the gnome way it will NOT work with Linux Mint:

gsettings set org.gnome.desktop.background picture-uri /some/pic.jpg

You'll have to edit the policy.xml file to fix this:

 convert -density 300 output.pdf agreement.jpg
convert.im6: not authorized `output.pdf' @ error/constitute.c/ReadImage/454.
convert.im6: no images defined `agreement.jpg' @ error/convert.c/ConvertImageCommand/3044.

sudo vi /etc/ImageMagick*/policy.xml

Change

policy domain="coder" rights="none" pattern="PDF"

# to

policy domain="coder" rights="read|write" pattern="PDF" After this conversion should work and it applies to other file types in policy.xml

Use these flags:

convert -alpha flatten -alpha remove "output.pdf" ljll.jpg
 

And even the pesky black backgrounds should be gone after converting to jpg

This is a security hole in my opinion and should be plugged by editing the lock screen ui layout:

vi /usr/share/mate-screensaver/lock-dialog-default.ui

#find these objects and set the visible property to false
object class="GtkLabel" id="note-tab-label"
object class="GtkLabel" id="auth-username-label>
object class="GtkLabel" id="auth-realname-label"

Actually I had to remove the entire child statement:

Basically just search for "vbox3" and delete the entire child object shown in the graphic below (or in otherwords everything you see below should be erased and removed from the file. (recommend making a backup in case you mess it up!)

If you want to hide the usernames on the login screen follow this guide.

By default printscreen or alt print screen will get the whole desktop or the application in focus, respectively.  But what if you want to select a portion of the screen?

gnome-screenshot:

ksnapshot

compiz

This is a nicely integrated solution

sudo apt-get install compizconfig-settings-manager

Then open the settings wizard and go to Extras and check off the "Screenshot" Option

You should be able to hold the Windows Key and drag to take a screenshot now (does not work on Linux Mint 18 though).

You can also change the initiate key by clicking on Screenshot in Compiz:

SSH helps keep us secure in many ways, one of those is the host-key fingerprint which is unique.  If you have been connecting to an SSH server that you've made no changes to and suddenly ssh warns that the key doesn't match then you have a problem.

But how about connecting to an existing server for the first time on a new machine or client?

A lot of new clients calculate it using an SHA256 hash but it is not as easy on your host machine to produce the same style hash without some hacking around.

The authenticity of host 'somehow (172.16.5.2)' can't be established.
RSA key fingerprint is SHA256:alalalalleieieieieiala.
Are you sure you want to continue connecting (yes/no)?


So we can get the MD5 hash by using this option:


ssh -o fingerprinthash=md5 user@host
The authenticity of host 'somehow (172.16.5.2)' can't be established.
RSA key fingerprint is MD5:aa:sldka;:ksdkjd::kala:kfdkls:1.
Are you sure you want to continue connecting (yes/no)?
 

How do we get the md5 hash on our host?

ssh-keygen -l -f /etc/ssh/ssh_host_key.pub
aa:sldka;:ksdkjd::kala:kfdkls:1 /etc/ssh/ssh_host_key.pub (RSA1)
 

On newer versions you will need to do it like this:

ssh-keygen -l -f /etc/ssh/ssh_host_key.pub -E md5

This would be crucial especially if the phone is hardened, not being able to reset or change settings could prevent a phone registering in a new environment or even when migrating from office to office.

Updated Guide

1.) Reboot phone and hold the "#" key.

2.) Once the headset and volume key are green release the "#" key.

3.) Immediately press 123456789*0# (if you are successful when you press 1 the headset button should go dark).  If it doesn't try again. Timing is key and being off by .25 seconds is too much.

Here is Cisco's guide (timing is everything and it is more tricky than trying to jail break your iPhone):

Step 1 -- While powering up the phone, press and hold #.

Step 2 -- When the light on the mute button and handset light strip turns off and all other lights (line button, headset button, speakerphone button and select button) stay green, press 123456789*0# in sequence.

When you press 1, the lights on the line buttons turn red. The light on the select button flash when a button is pressed.

If you press the buttons out of sequence, the lights on the line button, headset button, speakerphone button, and select button turn green. You will need to start over and press 123456789*0# in sequence again.

After you press these buttons, the phone goes through the factory reset process.

Do not power down the phone until it completes the factory reset process, and the main screen appears.

Here is an alternative description some have had better luck with:

*Just be forewarned again that it may take a few tries but it does work.

Sources: https://community.cisco.com/t5/ip-telephony-and-phones/cp-8945-factory-reset-not-working/td-p/2502278

The key thing is the "-d" flag and the */ at the end of the path. 

Just do this:

ls -d */

It would list all directories in the pwd

If you want a path do this:

ls -d /var/log/*/

/var/log/apt/         /var/log/hp/         /var/log/samba/
/var/log/ConsoleKit/  /var/log/installer/  /var/log/speech-dispatcher/
/var/log/cups/        /var/log/mdm/        /var/log/upstart/
/var/log/fsck/        /var/log/ntpstats/


ssh-keygen -p -f /path/to/your/id_rsa

Enter new passphrase (empty for no passphrase):

After that your rsa private key will be encrypted which is a layer of protection and security in the event that somehow someone acquires your key and tries to access servers that the key is authorized on.

Click "Administration" -> "Login Window"

Opening Firefox from the CLI reveals the following as the cause of the error:


Query failed: Error: Error(s) encountered during statement execution: no such table: moz_favicons


The symptoms of this issue are that in the address bar you cannot hit enter to browse to a site/url/address and your history cannot be accessed, nor does your history show up in the address bar when typing previously used addresses.

This usually happens because you've restored places.sqlite from a NEWER version of Firefox where the structure of the database has changed.  The solution is to upgrade to a newer version of Firefox.

Eg. your source browser is Firefox Version 65 and your destination was running Firefox 50 so this is why it happens.

Install Errors on Version 12:

This error happened on QEMU emulator version 2.11.1 pve-qemu-kvm_2.11.1-5
 on Proxmox/Debian but installing on QEMU .12 on Centos 6 did not produce the error.

*Update it is not related to the OS or QEMU version.  This happened in Centos 6 too after a second install. 

What really causes this even though you successfully installed already using the same settings and same machine?

The problem is related to IO, I believe there is some sort of timer on the database install portion and the install declares itself dead and stops if a certain amount of queries or files are not copied within a certain amount of time.  Don't believe me, take a normal HDD and load it up with a few VMs, see if CUCM installs.  Then add more CUCMs and try to install again and you will at some port have too little IOPS to successfully complete the install. 

I have installed successfully but CUCM seems picky about the order of steps (eg. if you configure the wizard later or now).  It also seems to need 4096MB of RAM at the most and a single CPU to avoid the error.  I am going to make a step-by-step guide as it seems very finicky to avoid this problem on the DB install process.

Critical Error

The installation has encountered a unrecoverable internal error.  For further assistance report the following information to your support provider.

"/usr/local/cm/script/cm-dbl-install install PostInstall 12.01.10000 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt" failed (1)

The system will now halt.

Continuing will allow you to view diagnostic information before halting.

irt-df cucm12.img
Filesystem                           1K-blocks       Used  Available  Use%
cucm12.img:/dev/sda1                  21688188   10620380   10829752   49%
cucm12.img:/dev/sda2                  21688188      44992   20518436    1%
cucm12.img:/dev/sda3                    245679       2322     226154    1%
cucm12.img:/dev/sda6                  75790432    4113716   67803692    6%
root@proxmoxdal01:/mnt/space# guestmount -a /dev/^C
root@proxmoxdal01:/mnt/space# mkdir mount
root@proxmoxdal01:/mnt/space# guestmount -a /dev/sda1 mount/
guestmount: error: you must specify either -i at least one -m option.
Try `guestmount --help' for more information.
root@proxmoxdal01:/mnt/space# guestmount -m -a /dev/sda1 mount/
guestmount: error: you must specify at least one -a or -d option.
Try `guestmount --help' for more information.
root@proxmoxdal01:/mnt/space# guestmount -m -d /dev/sda1 mount/
guestmount: error: you must specify at least one -a or -d option.
Try `guestmount --help' for more information.
root@proxmoxdal01:/mnt/space# guestmount -d /dev/sda1 mount/
guestmount: error: you must specify either -i at least one -m option.
Try `guestmount --help' for more information.
root@proxmoxdal01:/mnt/space# guestmount -a cucm12.img -m /dev/sda1 --ro mount/


#actually /dev/sda6 has what we need inside /log/install/install.log


04/11/2019 22:32:16 InstallWizard|'/usr/local/platform/bin/clm/clm_ctl set install_configuration_complete yes'  executed successfully|
04/11/2019 22:32:16 InstallWizard|written 6522 bytes to /usr/local/platform/conf/platformConfig.xml|
04/11/2019 22:32:16 InstallWizard|re encrypted file stored in platformConfig file|
04/11/2019 22:32:16 appmanager.sh|/usr/local/bin/base_scripts/InstallWizard returned 0|
04/11/2019 22:32:16 component_install|Initializing xproduct.sh API|
04/11/2019 22:32:16 component_install|Initializing xcomponent.sh API|
04/11/2019 22:32:16 component_install|Initializing xplatformconfig.sh API|
04/11/2019 22:32:16 component_install|PATH=/usr/local/cm/db/informix:/usr/local/cm/db/informix/bin:/usr/local/cm/bin:/usr/local//thirdparty/java/j2sdk/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/sbin:/home/sftpuser:/root/.security:/root/bin:/usr/local/sbin:/sbin:/usr/sbin:/bin:/usr/bin:/sbin:/home/sftpuser:/root/.security:/sbin:/home/sftpuser:/root/.security|
04/11/2019 22:32:16 component_install|LD_LIBRARY_PATH=/usr/local/lib:/usr/local/thirdparty/java/j2sdk/jre/lib/i386:/usr/local/thirdparty/java/j2sdk/jre/lib/i386/server:/usr/lib/pgsql:/usr/lib:/usr/local/cm/lib:/usr/local/platform/lib:/usr/local/lib:/usr/local/thirdparty/java/j2sdk/jre/lib/i386:/usr/local/thirdparty/java/j2sdk/jre/lib/i386/server:/usr/lib/pgsql:/usr/lib:/usr/local/cm/lib:/usr/local/lib:/usr/local/thirdparty/java/j2sdk/jre/lib/i386:/usr/local/thirdparty/java/j2sdk/jre/lib/i386/server:/usr/lib/pgsql:/usr/lib:/usr/local/cm/lib::/usr/local/platform/lib:/usr/local/platform/lib|
04/11/2019 22:32:16 component_install|Parse argument type=infrastructure_post|
04/11/2019 22:32:16 component_install|Parse argument mode=install|
04/11/2019 22:32:17 component_install|Install infrastructure_post component, mode install|
04/11/2019 22:32:17 component_install|Initialize product data, mode install|
04/11/2019 22:32:17 component_install|Initialize "to" side product version|
04/11/2019 22:32:17 component_install|Access "to" side API|
04/11/2019 22:32:17 component_install|Got version 12.0.1.10000-10|
04/11/2019 22:32:17 component_install|Initialize "to" side product version complete|
04/11/2019 22:32:17 component_install|Initialize product data complete|
04/11/2019 22:32:17 component_install|Initialize component data, mode install|
04/11/2019 22:32:17 component_install|Initialize ucplatform_post "to" side version|
04/11/2019 22:32:17 component_install|Access "to" side API|
04/11/2019 22:32:17 component_install|Got version 12.0.1.10000-10|
04/11/2019 22:32:17 component_install|Initialize ucplatform_post "to" side version complete|
04/11/2019 22:32:17 component_install|Initialize global data complete|
04/11/2019 22:32:17 component_install|Build the command list for ucplatform_post|
04/11/2019 22:32:17 component_install|Initialize command list|
04/11/2019 22:32:17 component_install|Build ucplatform_post install phase commands|
04/11/2019 22:32:17 component_install|Processing ucplatform_post install element|
04/11/2019 22:32:18 component_install|Processing ucplatform_post phase element|
04/11/2019 22:32:18 component_install|Processing ucplatform_post import element|
04/11/2019 22:32:18 component_install|Building the command list for ucplatform_post is complete|
04/11/2019 22:32:18 component_install|Command execution for ucplatform_post component RTMTStart|
04/11/2019 22:32:18 component_install|Execute commands in the command list for ucplatform_post component|
04/11/2019 22:32:18 component_install|No commands to execute for ucplatform_post component|
04/11/2019 22:32:18 component_install|Command execution for ucplatform_post component is complete|
04/11/2019 22:32:18 component_install|Command execution for ucplatform_post component RTMTFinish|
04/11/2019 22:32:18 component_install|Initialize component data, mode install|
04/11/2019 22:32:18 component_install|Initialize thirdparty "to" side version|
04/11/2019 22:32:18 component_install|Access "to" side API|
04/11/2019 22:32:18 component_install|Got version 12.0.1.10000-10|
04/11/2019 22:32:18 component_install|Initialize thirdparty "to" side version complete|
04/11/2019 22:32:18 component_install|Initialize global data complete|
04/11/2019 22:32:18 component_install|Build the command list for thirdparty|
04/11/2019 22:32:18 component_install|Initialize command list|
04/11/2019 22:32:18 component_install|Build thirdparty install phase commands|
04/11/2019 22:32:18 component_install|Processing thirdparty install element|
04/11/2019 22:32:18 component_install|Processing thirdparty package element|
04/11/2019 22:32:18 component_install|Checking if RPM /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-lib-1.0.0.0-1.i386.rpm exists|
04/11/2019 22:32:18 component_install|Add "rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-lib-1.0.0.0-1.i386.rpm" to command list|
04/11/2019 22:32:18 component_install|Processing thirdparty package element|
04/11/2019 22:32:18 component_install|Checking if RPM /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-jar-lib-1.0.0.0-1.i386.rpm exists|
04/11/2019 22:32:19 component_install|Add "rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-jar-lib-1.0.0.0-1.i386.rpm" to command list|
04/11/2019 22:32:19 component_install|Building the command list for thirdparty is complete|
04/11/2019 22:32:19 component_install|Command execution for thirdparty component RTMTStart|
04/11/2019 22:32:19 component_install|Execute commands in the command list for thirdparty component|
04/11/2019 22:32:19 IPM|Normalizer search path is /opt/cisco/install/bin|
04/11/2019 22:32:19 IPM|Checking normalizer /opt/cisco/install/bin/pmNormalizeGeneric|
04/11/2019 22:32:19 IPM|Returning normalizer /opt/cisco/install/bin/pmNormalizeGeneric|
04/11/2019 22:32:20 IPM|Open progress meter "Component Install"|
04/11/2019 22:32:20 IPM|  begin-of-session "Installing thirdparty component", 2 items|
04/11/2019 22:32:20 IPM|    begin-analysis: [2 commands]|
04/11/2019 22:32:20 IPM|      command #1: 3973452 bytes, 0 seconds: rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-lib-1.0.0.0-1.i386.rpm|
04/11/2019 22:32:20 IPM|      command #2: 6237296 bytes, 0 seconds: rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-jar-lib-1.0.0.0-1.i386.rpm|
04/11/2019 22:32:20 IPM|    end-analysis: 2 total objects, 10210748 total bytes, 0 total seconds, 0.067 secs.|
04/11/2019 22:32:20 IPM|    begin-work: [2 items]|
04/11/2019 22:32:20 IPM|Execute rpm command "rpm --percent -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-lib-1.0.0.0-1.i386.rpm "|
04/11/2019 22:32:25 IPM|      item  1: rpm-install    3973452 bytes (5.224 secs.)|
04/11/2019 22:32:25 IPM|Execute rpm command "rpm --percent -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-jar-lib-1.0.0.0-1.i386.rpm "|
04/11/2019 22:32:31 IPM|      item  2: rpm-install    6237296 bytes (6.037 secs.)|
04/11/2019 22:32:31 IPM|    end-work:          2 items  11.272 secs. total|
04/11/2019 22:32:33 IPM|  end-of-session "Installing thirdparty component": 13.278 secs.|
04/11/2019 22:32:33 IPM|Close progress meter "Component Install"|
04/11/2019 22:32:33 component_install|Command execution for thirdparty component is complete|
04/11/2019 22:32:33 component_install|Command execution for thirdparty component RTMTFinish|
04/11/2019 22:32:33 component_install|Initialize component data, mode install|
04/11/2019 22:32:33 component_install|Initialize serviceability_core "to" side version|
04/11/2019 22:32:33 component_install|Access "to" side API|
04/11/2019 22:32:34 component_install|Got version 12.0.1.10000-10|
04/11/2019 22:32:34 component_install|Initialize serviceability_core "to" side version complete|
04/11/2019 22:32:34 component_install|Initialize global data complete|
04/11/2019 22:32:34 component_install|Build the command list for serviceability_core|
04/11/2019 22:32:34 component_install|Initialize command list|
04/11/2019 22:32:34 component_install|Build serviceability_core install phase commands|
04/11/2019 22:32:34 component_install|Processing serviceability_core install element|
04/11/2019 22:32:34 component_install|Processing serviceability_core package element|
04/11/2019 22:32:34 component_install|Checking if RPM /common/rpm-archive/12.0.1.10000-10/RPMS/serviceability_core/cm-pi-0.0.0.1-0.i386.rpm exists|
04/11/2019 22:32:34 component_install|Add "rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/serviceability_core/cm-pi-0.0.0.1-0.i386.rpm" to command list|
04/11/2019 22:32:34 component_install|Building the command list for serviceability_core is complete|
04/11/2019 22:32:34 component_install|Command execution for serviceability_core component RTMTStart|
04/11/2019 22:32:34 component_install|Execute commands in the command list for serviceability_core component|
04/11/2019 22:32:35 IPM|Normalizer search path is /opt/cisco/install/bin|
04/11/2019 22:32:35 IPM|Checking normalizer /opt/cisco/install/bin/pmNormalizeGeneric|
04/11/2019 22:32:35 IPM|Returning normalizer /opt/cisco/install/bin/pmNormalizeGeneric|
04/11/2019 22:32:36 IPM|Open progress meter "Component Install"|
04/11/2019 22:32:36 IPM|  begin-of-session "Installing core serviceability component", 1 items|
04/11/2019 22:32:36 IPM|    begin-analysis: [1 commands]|
04/11/2019 22:32:36 IPM|      command #1: 4318680 bytes, 0 seconds: rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/serviceability_core/cm-pi-0.0.0.1-0.i386.rpm|
04/11/2019 22:32:36 IPM|    end-analysis: 1 total objects, 4318680 total bytes, 0 total seconds, 0.076 secs.|
04/11/2019 22:32:36 IPM|    begin-work: [1 items]|
04/11/2019 22:32:36 IPM|Execute rpm command "rpm --percent -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/serviceability_core/cm-pi-0.0.0.1-0.i386.rpm "|
04/11/2019 22:32:41 IPM|      item  1: rpm-install    4318680 bytes (5.131 secs.)|
04/11/2019 22:32:41 IPM|    end-work:          1 items  5.141 secs. total|
04/11/2019 22:32:43 IPM|  end-of-session "Installing core serviceability component": 7.154 secs.|
04/11/2019 22:32:43 IPM|Close progress meter "Component Install"|
04/11/2019 22:32:43 component_install|Command execution for serviceability_core component is complete|
04/11/2019 22:32:43 component_install|Command execution for serviceability_core component RTMTFinish|
04/11/2019 22:32:43 component_install|Initialize component data, mode install|
04/11/2019 22:32:43 component_install|Initialize database "to" side version|
04/11/2019 22:32:43 component_install|Access "to" side API|
04/11/2019 22:32:43 component_install|Got version 12.0.1.10000-10|
04/11/2019 22:32:43 component_install|Initialize database "to" side version complete|
04/11/2019 22:32:43 component_install|Initialize global data complete|
04/11/2019 22:32:43 component_install|Build the command list for database|
04/11/2019 22:32:43 component_install|Initialize command list|
04/11/2019 22:32:43 component_install|Build database install phase commands|
04/11/2019 22:32:43 component_install|Processing database install element|
04/11/2019 22:32:43 component_install|Processing database package element|
04/11/2019 22:32:43 component_install|Checking if RPM /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbms-1.0.0.0-1.i386.rpm exists|
04/11/2019 22:32:43 component_install|Add "rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbms-1.0.0.0-1.i386.rpm" to command list|
04/11/2019 22:32:44 component_install|Processing database package element|
04/11/2019 22:32:44 component_install|Checking if RPM /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbl-1.0.0.0-1.i386.rpm exists|
04/11/2019 22:32:44 component_install|Add "rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbl-1.0.0.0-1.i386.rpm" to command list|
04/11/2019 22:32:44 component_install|Processing database phase element|
04/11/2019 22:32:44 component_install|Processing database import element|
04/11/2019 22:32:44 component_install|Processing database phase element|
04/11/2019 22:32:44 component_install|Processing database migration element|
04/11/2019 22:32:44 component_install|Processing database phase element|
04/11/2019 22:32:44 component_install|Processing database postinstall element|
04/11/2019 22:32:44 component_install|Processing database script element|
04/11/2019 22:32:44 component_install|Add "cm-dbms-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt" to command list|
04/11/2019 22:32:45 component_install|Processing database script element|
04/11/2019 22:32:45 component_install|Add "cm-dbl-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt" to command list|
04/11/2019 22:32:45 component_install|Building the command list for database is complete|
04/11/2019 22:32:45 component_install|Command execution for database component RTMTStart|
04/11/2019 22:32:45 component_install|Execute commands in the command list for database component|
04/11/2019 22:32:45 IPM|Normalizer search path is /opt/cisco/install/bin|
04/11/2019 22:32:45 IPM|Checking normalizer /opt/cisco/install/bin/pmNormalizeGeneric|
04/11/2019 22:32:45 IPM|Returning normalizer /opt/cisco/install/bin/pmNormalizeGeneric|
04/11/2019 22:32:46 IPM|Open progress meter "Component Install"|
04/11/2019 22:32:46 IPM|  begin-of-session "Installing database component", 4 items|
04/11/2019 22:32:46 IPM|    begin-analysis: [4 commands]|
04/11/2019 22:32:46 IPM|      command #1: 423348056 bytes, 0 seconds: rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbms-1.0.0.0-1.i386.rpm|
04/11/2019 22:32:46 IPM|      command #2: 12611328 bytes, 0 seconds: rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbl-1.0.0.0-1.i386.rpm|
04/11/2019 22:32:46 IPM|      command #3: 0 bytes, 4800 seconds: sh  -path /opt/cisco/install/database/scripts:/usr/local/cm/script -t 4800 -c cm-dbms-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt|
04/11/2019 22:32:46 IPM|      command #4: 0 bytes, 21600 seconds: sh  -path /opt/cisco/install/database/scripts:/usr/local/cm/script -t 21600 -c cm-dbl-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt|
04/11/2019 22:32:46 IPM|    end-analysis: 4 total objects, 435959384 total bytes, 26400 total seconds, 0.133 secs.|
04/11/2019 22:32:46 IPM|    begin-work: [4 items]|
04/11/2019 22:32:46 IPM|Execute rpm command "rpm --percent -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbms-1.0.0.0-1.i386.rpm "|
04/11/2019 22:33:23 IPM|      item  1: rpm-install  423348056 bytes (36.504 secs.)|
04/11/2019 22:33:23 IPM|Execute rpm command "rpm --percent -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbl-1.0.0.0-1.i386.rpm "|
04/11/2019 22:33:41 IPM|      item  2: rpm-install   12611328 bytes (18.213 secs.)|
04/11/2019 22:33:41 IPM|Execute shell command "/usr/local/cm/script/cm-dbms-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt "|
04/11/2019 23:00:17 IPM|      item  3: shell-script          0 bytes (1596.499 secs.)|
04/11/2019 23:00:17 IPM|Execute shell command "/usr/local/cm/script/cm-dbl-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt "|
04/11/2019 23:58:20 IPM|Internal Error, File:ipm.c:2011, Function: ipmReadNormalizedInputLine(), "/usr/local/cm/script/cm-dbl-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt " failed (1)|
04/11/2019 23:58:22 IPM|  end-of-session "Installing database component": 5136.088 secs.|
04/11/2019 23:58:22 IPM|Close progress meter "Component Install"|
04/11/2019 23:58:22 component_install|Writing database into /common/log/install/component_failed.xml file.|
04/11/2019 23:58:22 component_install|/common/log/install/component_failed.xml created : 0|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:15 2019 cm-dbms-install  DEBUG:  <--|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:17 2019 cm-dbl-install  DEBUG:  -->|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:17 2019 cm-dbl-install.ParamObject.validate  DEBUG:  -->|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:17 2019 cm-dbl-install.ParamObject.validate  DEBUG:  <--|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:17 2019 cm-dbl-install.doActionInstall  DEBUG:  -->|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:17 2019 cm-dbl-install.doActionInstall  DEBUG:  Inside doActionInstall...|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:17 2019 cm-dbl-install.doInstallPost_installDB  DEBUG:  -->|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:17 2019 cm-dbl-install.doInstallPost_installDB  DEBUG:  Inside doInstallPost...|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:17 2019 cm-dbl-install.doCreateLogDirectory  DEBUG:  -->|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:17 2019 cm-dbl-install.doCreateLogDirectory  DEBUG:  Verifying SDI directory [/var/log/active/cm/trace/dbl/sdi]|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:17 2019 cm-dbl-install.doCreateLogDirectory  DEBUG:  chown database.ccmbase /var/log/active/cm/trace/dbl/sdi|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.doCreateLogDirectory  DEBUG:  chmod 775 /var/log/active/cm/trace/dbl/sdi|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.doCreateLogDirectory  DEBUG:  <--|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.setupPreferences  DEBUG:  -->|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.setupPreferences  DEBUG:  Inside setupPreferences...|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.setupPreferences  DEBUG:  current_db [ccm12_0_1_10000_10]|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.setupPreferences  DEBUG:  chown database.ccmbase /usr/local/cm/conf/dbl/prefs.xml ; chmod 644 /usr/local/cm/conf/dbl/prefs.xml|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.setupPreferences  DEBUG:  Updating prefs [/usr/local/cm/conf/dbl/prefs.xml]|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.shortHostName  DEBUG:  -->|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.shortHostName  DEBUG:  <--|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.shortHostName  DEBUG:  -->|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.shortHostName  DEBUG:  <--|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.shortHostName  DEBUG:  -->|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.shortHostName  DEBUG:  <--|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.shortHostName  DEBUG:  -->|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.shortHostName  DEBUG:  <--|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.setupPreferences  DEBUG:  chown database.ccmbase /usr/local/cm/conf/dbl/sdi/prefs.xml ; chmod 664 /usr/local/cm/conf/dbl/sdi/prefs.xml|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.setupPreferences  DEBUG:  Updating prefs [/usr/local/cm/conf/dbl/sdi/prefs.xml]|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.setupPreferences  DEBUG:  chown database.ccmbase /usr/local/cm/conf/dbnotify/sdi/prefs.xml ; chmod 664 /usr/local/cm/conf/dbnotify/sdi/prefs.xml|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.setupPreferences  DEBUG:  Updating prefs [/usr/local/cm/conf/dbnotify/sdi/prefs.xml]|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.setupPreferences  DEBUG:  python "/usr/local/cm/bin/dbl" setprefs /common/log/install/capture.txt|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 dblsetprefs-plugin.run  DEBUG:  -->|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 dblsetprefs-plugin.run  DEBUG:  Create Preferences entries for various database components|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 dblsetprefs-plugin.run  DEBUG:  <--|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.setupPreferences  DEBUG:  <--|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.getPublisherFromInstallPrefs  DEBUG:  -->|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.getPublisherFromInstallPrefs  DEBUG:  Inside getPublisherFromInstallPrefs...|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.getPublisherFromInstallPrefs  DEBUG:  <--|
04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.doInstallPost_installDB  DEBUG:  (odbc setup moved to dbl init)| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.fixSQLLibPaths  DEBUG:  -->| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.fixSQLLibPaths  DEBUG:  Inside fixSQLLibPaths....| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.fixSQLLibPaths  DEBUG:  <--| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.fixSQLLibPaths  DEBUG:  -->| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:18 2019 cm-dbl-install.fixSQLLibPaths  DEBUG:  Inside fixSQLLibPaths....| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:19 2019 cm-dbl-install.fixSQLLibPaths  DEBUG:  <--| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:19 2019 cm-dbl-install.doInstallPost_installDB  DEBUG:  -->| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:19 2019 cm-dbl-install.doInstallPost_installDB  DEBUG:  Inside doInstallPost_installDB ...| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:19 2019 cm-dbl-install.installdb  DEBUG:  -->| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:19 2019 cm-dbl-install.installdb  DEBUG:  Inside installdb ...| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:19 2019 cm-dbl-install.installdb  DEBUG:  python "/usr/local/cm/bin/dbl" start --safe --nopreflight --log=/common/log/install/capture.txt| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:19 2019 dblstart-plugin.run  DEBUG:  -->| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:19 2019 dblstart-plugin.run  DEBUG:  Start DBMS| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:34 2019 dblstart-plugin.run  DEBUG:  do preflight| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:34 2019 dblstart-plugin.run  DEBUG:  <--| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:34 2019 cm-dbl-install.installdb  DEBUG:  rm -f /tmp/*.txt /tmp/*.log /tmp/*.err /var/log/active/cm/trace/dbl/sdi/psqlx /tmp/*.bin /tmp/af* /tmp/shmem*| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:34 2019 cm-dbl-install.installdb  DEBUG:  Disk size present in dbl/prefs is 128| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:34 2019 cm-dbl-install.getPublisherFromPrefs  DEBUG:  -->| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:34 2019 cm-dbl-install.getPublisherFromPrefs  DEBUG:  Inside getPublisherFromPrefs...| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:34 2019 cm-dbl-install.getPublisherFromPrefs  DEBUG:  <--| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:00:34 2019 cm-dbl-install.installdb  DEBUG:  su -l informix -s /bin/sh -c 'source /usr/local/cm/db/dblenv.bash /usr/local/cm ; source /usr/local/cm/db/informix/local/ids.env ; "/usr/local/cm/bin/installdb" -f IN "/usr/local/cm" "/usr/local/cm" 12.0.1.10000-10 12.0.1.10000-10 installdb_in.log'| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:58:18 2019 cm-dbl-install.installdb  DEBUG:  <--| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:58:18 2019 cm-dbl-install.doInstallPost_installDB  DEBUG:  <--| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:58:18 2019 cm-dbl-install.doInstallPost_installDB  DEBUG:  <--| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:58:18 2019 cm-dbl-install.doActionInstall  DEBUG:  <--| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:58:18 2019 cm-dbl-install  DEBUG:  cm-dbl-install [1]| 04/11/2019 23:58:22 component_install|(CAPTURE) Thu Apr 11 23:58:18 2019 cm-dbl-install  DEBUG:  <--| 04/11/2019 23:58:22 component_install|File:/opt/cisco/install/bin/component_install:821, Function: exec_progmeter(), /opt/cisco/install/bin/progmeter failed (1)| 04/11/2019 23:58:22 appmanager.sh|Internal Error, File:/usr/local/bin/base_scripts/appmanager.sh:153, Function: install(), failed to install infrastructure_post components| 04/11/2019 23:58:22 post_install|File:/opt/cisco/install/bin/post_install:1030, Function: install_applications(), /usr/local/bin/base_scripts/appmanager.sh -install failed (1)| 04/11/2019 23:58:22 post_install|Exiting with result 1| 04/11/2019 23:58:22 post_install|INSTALL_TYPE="Basic Install"| 04/11/2019 23:58:22 post_install|File:/opt/cisco/install/bin/post_install:721, Function: check_for_critical_error(), check_for_critical_error, found /common/log/install/critical.log, exiting| 04/11/2019 23:58:23 post_install|(CAPTURE) Mail notification cancelled - smtp server address for email not found! [/usr/local/platform/conf/platformConfig.xml]| 04/11/2019 23:58:23 display_screen|Arguments: "Critical Error" "The installation has encountered a unrecoverable internal error. For further assistance report the following information to your support provider. "/usr/local/cm/script/cm-dbl-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt " failed (1) The system will now halt. Continuing will allow you to dump diagnostic information before halting." "Continue"| 04/11/2019 23:58:23 display_screen|Button label size information 66, 1, 66| 04/11/2019 23:58:23 platform-events.sh|Received request for platform-event (platform-install-paused-for-input TYPE=INSTALL_PAUSED)| 04/11/2019 23:58:23 platform-events.sh|emitting platform-event (platform-install-paused-for-input TYPE=INSTALL_PAUSED)| 04/11/2019 23:58:23 platform-events.sh|emitted platform-event (platform-install-paused-for-input TYPE=INSTALL_PAUSED)| 04/11/2019 23:58:23 display_screen|installWizard service activated| 04/12/2019 00:28:58 display_screen|newtFormRun exited. reason=1| 04/12/2019 00:28:58 display_screen|installWizard service deactivated| 04/12/2019 00:28:58 post_install|Dumping diagnostic information to USB| 04/12/2019 00:28:58 display_screen|Arguments: "INSTALLATION FAILED" "Would you like to dump diagnostic information?" "Yes" "No"| 04/12/2019 00:28:58 display_screen|Button label size information 66, 2, 33| 04/12/2019 00:28:58 platform-events.sh|Received request for platform-event (platform-install-paused-for-input TYPE=INSTALL_PAUSED)| 04/12/2019 00:28:58 platform-events.sh|emitting platform-event (platform-install-paused-for-input TYPE=INSTALL_PAUSED)| 04/12/2019 00:28:58 platform-events.sh|emitted platform-event (platform-install-paused-for-input TYPE=INSTALL_PAUSED)| 04/12/2019 00:28:58 display_screen|installWizard service activated| 04/12/2019 00:29:00 display_screen|newtFormRun exited. reason=1| 04/12/2019 00:29:00 display_screen|installWizard service deactivated| 04/12/2019 00:29:00 post_install|Installer selected not to dump diagnostics| 04/12/2019 00:29:00 post_install|========================= Installation failed. =========================| 04/12/2019 00:29:00 post_install|Copy /usr/local/bin/base_scripts/INSTALLATION_FAILED to /etc/rc.d/init.d/| 04/12/2019 00:29:00 post_install|Calling "cp /usr/local/bin/base_scripts/INSTALLATION_FAILED /etc/rc.d/init.d"| 04/12/2019 07:35:52 display_screen|Arguments: "INSTALLATION FAILED" "The installation has failed and must be restarted to recover from the failure. You may dump diagnostic information at this time to the USB Key.  Would you like to dump diagnostic information?" "Yes" "No"| 04/12/2019 07:35:52 display_screen|Button label size information 66, 2, 33| 04/12/2019 07:35:52 display_screen|installWizard service activated| -rw-rw-r--. 1 512 505 1.0M Apr 12 14:33 dbl_installdb00000031.log -rw-rw-r--. 1 512 505 1.0M Apr 12 14:33 dbl_installdb00000032.log -rw-rw-r--. 1 512 505 1.0M Apr 12 14:33 dbl_installdb00000033.log -rw-rw-r--. 1 512 505 1.0M Apr 12 14:33 dbl_installdb00000034.log -rw-rw-r--. 1 512 505 1.0M Apr 12 14:33 dbl_installdb00000035.log -rw-rw-r--. 1 512 505 1.0M Apr 12 14:33 dbl_installdb00000036.log -rw-rw-r--. 1 512 505 1.0M Apr 12 14:33 dbl_installdb00000037.log -rw-rw-r--. 1 512 505 1.0M Apr 12 14:33 dbl_installdb00000038.log -rw-rw-r--. 1 512 505   50 Apr 12 14:33 dbl_installdb~num.bin -rw-rw-r--. 1 512 505 1.0M Apr 12 14:33 dbl_installdb00000039.log -rw-rw-r--. 1 512 505 771K Apr 12 14:58 dbl_installdb00000040.log /log/taos-log-a/cm/trace/dbl/sdi/installdb# -rw-rw-r--. 1 512 505 771K Apr 12 14:58 dbl_installdb00000040.log 23:56:20.773 |-->DriverManager::FreeConnection() 23:56:20.773 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:56:20.773 |<--DriverManager::FreeConnection() 23:56:20.773 |-->DriverManager::FreeConnectionFailOver() 23:56:20.773 |-->DriverManager::getFailOverConnWrapper() 23:56:20.773 |<--DriverManager::getFailOverConnWrapper() 23:56:20.773 |<--DriverManager::FreeConnectionFailOver() 23:56:24.777 |   ConnMonitorTask::svc() Timeout occured on select() 23:56:24.777 |-->DriverManager::FreeConnection() 23:56:24.777 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:56:24.777 |<--DriverManager::FreeConnection() 23:56:24.777 |-->DriverManager::FreeConnectionFailOver() 23:56:24.777 |-->DriverManager::getFailOverConnWrapper() 23:56:24.777 |<--DriverManager::getFailOverConnWrapper() 23:56:24.777 |<--DriverManager::FreeConnectionFailOver() 23:56:28.781 |   ConnMonitorTask::svc() Timeout occured on select() 23:56:28.781 |-->DriverManager::FreeConnection() 23:56:28.781 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:56:28.781 |<--DriverManager::FreeConnection() 23:56:28.781 |-->DriverManager::FreeConnectionFailOver() 23:56:28.781 |-->DriverManager::getFailOverConnWrapper() 23:56:28.781 |<--DriverManager::getFailOverConnWrapper() 23:56:28.781 |<--DriverManager::FreeConnectionFailOver() 23:56:32.785 |   ConnMonitorTask::svc() Timeout occured on select() 23:56:32.785 |-->DriverManager::FreeConnection() 23:56:32.785 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:56:32.785 |<--DriverManager::FreeConnection() 23:56:32.785 |-->DriverManager::FreeConnectionFailOver() 23:56:32.785 |-->DriverManager::getFailOverConnWrapper() 23:56:32.785 |<--DriverManager::getFailOverConnWrapper() 23:56:32.785 |<--DriverManager::FreeConnectionFailOver() 23:56:36.789 |   ConnMonitorTask::svc() Timeout occured on select() 23:56:36.790 |-->DriverManager::FreeConnection() 23:56:36.790 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:56:36.790 |<--DriverManager::FreeConnection() 23:56:36.790 |-->DriverManager::FreeConnectionFailOver() 23:56:36.790 |-->DriverManager::getFailOverConnWrapper() 23:56:36.790 |<--DriverManager::getFailOverConnWrapper() 23:56:36.790 |<--DriverManager::FreeConnectionFailOver() 23:56:40.794 |   ConnMonitorTask::svc() Timeout occured on select() 23:56:40.794 |-->DriverManager::FreeConnection() 23:56:40.794 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:56:40.794 |<--DriverManager::FreeConnection() 23:56:40.794 |-->DriverManager::FreeConnectionFailOver() 23:56:40.794 |-->DriverManager::getFailOverConnWrapper() 23:56:40.794 |<--DriverManager::getFailOverConnWrapper() 23:56:40.794 |<--DriverManager::FreeConnectionFailOver() 23:56:44.797 |   ConnMonitorTask::svc() Timeout occured on select() 23:56:44.797 |-->DriverManager::FreeConnection() 23:56:44.797 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:56:44.797 |<--DriverManager::FreeConnection() 23:56:44.797 |-->DriverManager::FreeConnectionFailOver() 23:56:44.797 |-->DriverManager::getFailOverConnWrapper() 23:56:44.797 |<--DriverManager::getFailOverConnWrapper() 23:56:44.797 |<--DriverManager::FreeConnectionFailOver() 23:56:48.801 |   ConnMonitorTask::svc() Timeout occured on select() 23:56:48.801 |-->DriverManager::FreeConnection() 23:56:48.802 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:56:48.802 |<--DriverManager::FreeConnection() 23:56:48.802 |-->DriverManager::FreeConnectionFailOver() 23:56:48.802 |-->DriverManager::getFailOverConnWrapper() 23:56:48.802 |<--DriverManager::getFailOverConnWrapper() 23:56:48.802 |<--DriverManager::FreeConnectionFailOver() 23:56:52.806 |   ConnMonitorTask::svc() Timeout occured on select() 23:56:52.806 |-->DriverManager::FreeConnection() 23:56:52.806 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:56:52.806 |<--DriverManager::FreeConnection() 23:56:52.806 |-->DriverManager::FreeConnectionFailOver() 23:56:52.806 |-->DriverManager::getFailOverConnWrapper() 23:56:52.806 |<--DriverManager::getFailOverConnWrapper() 23:56:52.806 |<--DriverManager::FreeConnectionFailOver() 23:56:56.809 |   ConnMonitorTask::svc() Timeout occured on select() 23:56:56.810 |-->DriverManager::FreeConnection() 23:56:56.810 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:56:56.810 |<--DriverManager::FreeConnection() 23:56:56.810 |-->DriverManager::FreeConnectionFailOver() 23:56:56.810 |-->DriverManager::getFailOverConnWrapper() 23:56:56.810 |<--DriverManager::getFailOverConnWrapper() 23:56:56.810 |<--DriverManager::FreeConnectionFailOver() 23:57:00.813 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:00.813 |-->DriverManager::FreeConnection() 23:57:00.813 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:00.813 |<--DriverManager::FreeConnection() 23:57:00.813 |-->DriverManager::FreeConnectionFailOver() 23:57:00.813 |-->DriverManager::getFailOverConnWrapper() 23:57:00.813 |<--DriverManager::getFailOverConnWrapper() 23:57:00.813 |<--DriverManager::FreeConnectionFailOver() 23:57:04.817 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:04.817 |-->DriverManager::FreeConnection() 23:57:04.817 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:04.817 |<--DriverManager::FreeConnection() 23:57:04.817 |-->DriverManager::FreeConnectionFailOver() 23:57:04.817 |-->DriverManager::getFailOverConnWrapper() 23:57:04.817 |<--DriverManager::getFailOverConnWrapper() 23:57:04.817 |<--DriverManager::FreeConnectionFailOver() 23:57:08.821 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:08.821 |-->DriverManager::FreeConnection() 23:57:08.821 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:08.821 |<--DriverManager::FreeConnection() 23:57:08.821 |-->DriverManager::FreeConnectionFailOver() 23:57:08.821 |-->DriverManager::getFailOverConnWrapper() 23:57:08.821 |<--DriverManager::getFailOverConnWrapper() 23:57:08.821 |<--DriverManager::FreeConnectionFailOver() 23:57:12.825 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:12.825 |-->DriverManager::FreeConnection() 23:57:12.825 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:12.825 |<--DriverManager::FreeConnection() 23:57:12.825 |-->DriverManager::FreeConnectionFailOver() 23:57:12.825 |-->DriverManager::getFailOverConnWrapper() 23:57:12.825 |<--DriverManager::getFailOverConnWrapper() 23:57:12.825 |<--DriverManager::FreeConnectionFailOver() 23:57:16.829 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:16.829 |-->DriverManager::FreeConnection() 23:57:16.829 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:16.829 |<--DriverManager::FreeConnection() 23:57:16.829 |-->DriverManager::FreeConnectionFailOver() 23:57:16.829 |-->DriverManager::getFailOverConnWrapper() 23:57:16.829 |<--DriverManager::getFailOverConnWrapper() 23:57:16.829 |<--DriverManager::FreeConnectionFailOver() 23:57:20.833 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:20.833 |-->DriverManager::FreeConnection() 23:57:20.833 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:20.833 |<--DriverManager::FreeConnection() 23:57:20.833 |-->DriverManager::FreeConnectionFailOver() 23:57:20.833 |-->DriverManager::getFailOverConnWrapper() 23:57:20.834 |<--DriverManager::getFailOverConnWrapper() 23:57:20.834 |<--DriverManager::FreeConnectionFailOver() 23:57:24.838 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:24.838 |-->DriverManager::FreeConnection() 23:57:24.838 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:24.838 |<--DriverManager::FreeConnection() 23:57:24.838 |-->DriverManager::FreeConnectionFailOver() 23:57:24.838 |-->DriverManager::getFailOverConnWrapper() 23:57:24.838 |<--DriverManager::getFailOverConnWrapper() 23:57:24.838 |<--DriverManager::FreeConnectionFailOver() 23:57:28.842 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:28.842 |-->DriverManager::FreeConnection() 23:57:28.842 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:28.842 |<--DriverManager::FreeConnection() 23:57:28.842 |-->DriverManager::FreeConnectionFailOver() 23:57:28.842 |-->DriverManager::getFailOverConnWrapper() 23:57:28.842 |<--DriverManager::getFailOverConnWrapper() 23:57:28.842 |<--DriverManager::FreeConnectionFailOver() 23:57:32.846 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:32.846 |-->DriverManager::FreeConnection() 23:57:32.846 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:32.846 |<--DriverManager::FreeConnection() 23:57:32.846 |-->DriverManager::FreeConnectionFailOver() 23:57:32.846 |-->DriverManager::getFailOverConnWrapper() 23:57:32.846 |<--DriverManager::getFailOverConnWrapper() 23:57:32.846 |<--DriverManager::FreeConnectionFailOver() 23:57:36.851 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:36.851 |-->DriverManager::FreeConnection() 23:57:36.851 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:36.851 |<--DriverManager::FreeConnection() 23:57:36.851 |-->DriverManager::FreeConnectionFailOver() 23:57:36.851 |-->DriverManager::getFailOverConnWrapper() 23:57:36.851 |<--DriverManager::getFailOverConnWrapper() 23:57:36.851 |<--DriverManager::FreeConnectionFailOver() 23:57:40.855 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:40.855 |-->DriverManager::FreeConnection() 23:57:40.855 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:40.855 |<--DriverManager::FreeConnection() 23:57:40.855 |-->DriverManager::FreeConnectionFailOver() 23:57:40.855 |-->DriverManager::getFailOverConnWrapper() 23:57:40.855 |<--DriverManager::getFailOverConnWrapper() 23:57:40.855 |<--DriverManager::FreeConnectionFailOver() 23:57:44.859 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:44.859 |-->DriverManager::FreeConnection() 23:57:44.859 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:44.859 |<--DriverManager::FreeConnection() 23:57:44.859 |-->DriverManager::FreeConnectionFailOver() 23:57:44.859 |-->DriverManager::getFailOverConnWrapper() 23:57:44.859 |<--DriverManager::getFailOverConnWrapper() 23:57:44.859 |<--DriverManager::FreeConnectionFailOver() 23:57:48.863 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:48.863 |-->DriverManager::FreeConnection() 23:57:48.863 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:48.863 |<--DriverManager::FreeConnection() 23:57:48.863 |-->DriverManager::FreeConnectionFailOver() 23:57:48.863 |-->DriverManager::getFailOverConnWrapper() 23:57:48.863 |<--DriverManager::getFailOverConnWrapper() 23:57:48.863 |<--DriverManager::FreeConnectionFailOver() 23:57:52.867 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:52.867 |-->DriverManager::FreeConnection() 23:57:52.867 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:52.867 |<--DriverManager::FreeConnection() 23:57:52.867 |-->DriverManager::FreeConnectionFailOver() 23:57:52.867 |-->DriverManager::getFailOverConnWrapper() 23:57:52.867 |<--DriverManager::getFailOverConnWrapper() 23:57:52.867 |<--DriverManager::FreeConnectionFailOver() 23:57:56.872 |   ConnMonitorTask::svc() Timeout occured on select() 23:57:56.872 |-->DriverManager::FreeConnection() 23:57:56.872 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:57:56.872 |<--DriverManager::FreeConnection() 23:57:56.872 |-->DriverManager::FreeConnectionFailOver() 23:57:56.872 |-->DriverManager::getFailOverConnWrapper() 23:57:56.872 |<--DriverManager::getFailOverConnWrapper() 23:57:56.872 |<--DriverManager::FreeConnectionFailOver() 23:58:00.875 |   ConnMonitorTask::svc() Timeout occured on select() 23:58:00.875 |-->DriverManager::FreeConnection() 23:58:00.875 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:58:00.875 |<--DriverManager::FreeConnection() 23:58:00.875 |-->DriverManager::FreeConnectionFailOver() 23:58:00.875 |-->DriverManager::getFailOverConnWrapper() 23:58:00.875 |<--DriverManager::getFailOverConnWrapper() 23:58:00.875 |<--DriverManager::FreeConnectionFailOver() 23:58:04.879 |   ConnMonitorTask::svc() Timeout occured on select() 23:58:04.879 |-->DriverManager::FreeConnection() 23:58:04.879 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:58:04.879 |<--DriverManager::FreeConnection() 23:58:04.879 |-->DriverManager::FreeConnectionFailOver() 23:58:04.880 |-->DriverManager::getFailOverConnWrapper() 23:58:04.880 |<--DriverManager::getFailOverConnWrapper() 23:58:04.880 |<--DriverManager::FreeConnectionFailOver() 23:58:08.884 |   ConnMonitorTask::svc() Timeout occured on select() 23:58:08.884 |-->DriverManager::FreeConnection() 23:58:08.884 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:58:08.884 |<--DriverManager::FreeConnection() 23:58:08.884 |-->DriverManager::FreeConnectionFailOver() 23:58:08.884 |-->DriverManager::getFailOverConnWrapper() 23:58:08.884 |<--DriverManager::getFailOverConnWrapper() 23:58:08.884 |<--DriverManager::FreeConnectionFailOver() 23:58:12.888 |   ConnMonitorTask::svc() Timeout occured on select() 23:58:12.888 |-->DriverManager::FreeConnection() 23:58:12.888 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:58:12.888 |<--DriverManager::FreeConnection() 23:58:12.888 |-->DriverManager::FreeConnectionFailOver() 23:58:12.888 |-->DriverManager::getFailOverConnWrapper() 23:58:12.888 |<--DriverManager::getFailOverConnWrapper() 23:58:12.888 |<--DriverManager::FreeConnectionFailOver() 23:58:16.892 |   ConnMonitorTask::svc() Timeout occured on select() 23:58:16.892 |-->DriverManager::FreeConnection() 23:58:16.892 |   DriverManager::FreeConnection() All [1] connections in pool are being used. 23:58:16.892 |<--DriverManager::FreeConnection() 23:58:16.892 |-->DriverManager::FreeConnectionFailOver() 23:58:16.892 |-->DriverManager::getFailOverConnWrapper() 23:58:16.892 |<--DriverManager::getFailOverConnWrapper() 23:58:16.892 |<--DriverManager::FreeConnectionFailOver() 23:58:17.859 |   updatestatsAUS Refresh result 1021 23:58:17.859 |-->XResultSetPtr::~XResultSetPtr, ptr = [0x8eafa28] 23:58:17.859 |-->XResultSetPtr::release1() 23:58:17.859 |   XResultSetPtr::release1() REL ResultSetPtr: count = [1], ptr = [0x8eafa28], manageStmt = [YES] 23:58:17.859 |   XResultSetPtr::release1() ABOUT TO DEL RS, ptr = [0x8eafa28] 23:58:17.860 |   XResultSetPtr::release1() ABOUT TO DEL STMT = [0x8ee51d8] 23:58:17.860 |<--XResultSetPtr::release1() 23:58:17.860 |<--XResultSetPtr::~XResultSetPtr, ptr = [0x8eafa28] 23:58:17.860 |-->Connector::Connector()-chardsn 23:58:17.860 |   Connector::Connector()-chardsn useDSN [DSN=sysmaster;DATABASE=sysadmin] 23:58:17.860 |   Connector::Connector()-chardsn Commit [1] 23:58:17.860 |-->DriverManager::stickpasswd() 23:58:17.860 |   DriverManager::stickpasswd() DSN is [DSN=sysmaster;DATABASE=sysadmin;RECVTIMEOUT=300] 23:58:17.860 |   DriverManager::stickpasswd() Found match with [DSN=ccm] semicolon index[31] 47 23:58:17.860 |<--DriverManager::stickpasswd() 23:58:17.860 |   Connector::Connector()-chardsn m_dsn[DSN=sysmaster;DATABASE=sysadmin;RECVTIMEOUT=300] 23:58:17.860 |<--Connector::Connector()-chardsn 23:58:17.860 |-->Connector::execute() (nil) 23:58:17.860 |set isolation to committed read last committed 23:58:17.860 |-->Connector::getTempStatement() 23:58:17.860 |-->Connector::ensureConnection() 23:58:17.860 |-->Connector::connect() 23:58:17.860 |   Connector::connect() ==> DSN [DSN=sysmaster;DATABASE=sysadmin;RECVTIMEOUT=300] 23:58:17.860 |-->Connector::tryConnection() 23:58:17.860 |-->DriverManager::getConnection() 23:58:17.860 |   DriverManager::getConnection() [4281] dsn=[DSN=sysmaster;DATABASE=sysadmin;RECVTIMEOUT=300] 23:58:17.860 |-->DriverManager::getConnectionFromPool() 23:58:17.860 |-->DriverManager::findUnused() 23:58:17.860 |   DriverManager::findUnused() [4281] Pool=[1] DSN=[DSN=sysmaster;DATABASE=sysadmin;RECVTIMEOUT=300] 23:58:17.861 |   DriverManager::findUnused() [4281] Could not find an unused connection to [DSN=sysmaster;DATABASE=sysadmin;RECVTIMEOUT=300]. 23:58:17.861 |<--DriverManager::findUnused() 23:58:17.861 |   DriverManager::getConnectionFromPool() [4281] Did not find free connection for DSN [DSN=sysmaster;DATABASE=sysadmin;RECVTIMEOUT=300]. Going to DriverManager. 23:58:17.896 |   DriverManager::getConnectionFromPool() [4281] odbc::Connection* [0x8ee5028] [46] 23:58:17.896 |-->DriverManager::addConn() 23:58:17.896 |<--DriverManager::addConn() 23:58:17.896 |<--DriverManager::getConnectionFromPool() 23:58:17.896 |   DriverManager::getConnection() [4281] Connections In Use [2] In Pool [2] Total Given [76214] Constructed [46] Destructed [44] 23:58:17.896 |<--DriverManager::getConnection() 23:58:17.896 |   Connector::tryConnection() Trying m_connection [0x8ee5028] 23:58:17.896 |   Connector::tryConnection() Have connection: testing tryConnection 23:58:17.896 |   Connector::tryConnection() set auto commit 23:58:17.896 |-->Connector::getTempStatement() 23:58:17.896 |-->Connector::ensureConnection() 23:58:17.896 |   Connector::ensureConnection() m_connection [0x8ee5028] 23:58:17.896 |<--Connector::ensureConnection() 23:58:17.897 |   Connector::getTempStatement() StatementPtr [0x8ea5310] 23:58:17.897 |<--Connector::getTempStatement() 23:58:17.897 |   Connector::tryConnection() ###execute [set lock mode to wait 30] 23:58:17.897 |   Connector::tryConnection() Try SUCCEEDED m_connection [0x8ee5028] 23:58:17.897 |<--Connector::tryConnection() 23:58:17.897 |<--Connector::connect() 23:58:17.897 |   Connector::ensureConnection() m_connection [0x8ee5028] 23:58:17.897 |<--Connector::ensureConnection() 23:58:17.897 |   Connector::getTempStatement() StatementPtr [0x8ee51d8] 23:58:17.897 |<--Connector::getTempStatement() 23:58:17.898 |   Connector::execute() (nil) Result [FALSE] 23:58:17.898 |<--Connector::execute() (nil) 23:58:17.898 |   updatestatsAUS execute function sysadmin:exectask("Alert Cleanup") 23:58:17.898 |-->Connector::executeQuery() 0x8ee5028 23:58:17.898 |execute function sysadmin:exectask("Alert Cleanup") 23:58:17.898 |-->XResultSetPtr::XResultSetPtr 23:58:17.898 |   XResultSetPtr::XResultSetPtr count = [0], ptr = [(nil)], manageStmt =[NULL] 23:58:17.898 |<--XResultSetPtr::XResultSetPtr 23:58:17.898 |-->Connector::ensureStatement() 23:58:17.898 |-->Connector::ensureConnection() 23:58:17.898 |   Connector::ensureConnection() m_connection [0x8ee5028] 23:58:17.898 |<--Connector::ensureConnection() 23:58:17.898 |   Connector::ensureStatement() Statement [0x8ee51d8] 23:58:17.898 |<--Connector::ensureStatement() 23:58:17.898 |   Connector::executeQuery() 0x8ee5028 Creating ResultSetPtr for stmt [0x8ee51d8], managed 23:58:17.899 |-->XResultSetPtr::XResultSetPtr 23:58:17.899 |   XResultSetPtr::XResultSetPtr count = [1], ptr = [0x8e39368], manageStmt =[YES] 23:58:17.899 |<--XResultSetPtr::XResultSetPtr 23:58:17.899 |-->XResultSetPtr::release1() 23:58:17.899 |<--XResultSetPtr::release1() 23:58:17.899 |-->XResultSetPtr::~XResultSetPtr, ptr = [0x8e39368] 23:58:17.899 |-->XResultSetPtr::release1() 23:58:17.899 |   XResultSetPtr::release1() REL ResultSetPtr: count = [2], ptr = [0x8e39368], manageStmt = [YES] 23:58:17.899 |<--XResultSetPtr::release1() 23:58:17.899 |<--XResultSetPtr::~XResultSetPtr, ptr = [0x8e39368] 23:58:17.899 |   Connector::executeQuery() 0x8ee5028 ptr = [0x8e39368] 23:58:17.899 |<--Connector::executeQuery() 0x8ee5028 23:58:17.899 |-->Connector::executeQuery() 0x8ee5028 23:58:17.899 |execute function sysadmin:exectask("Alert Cleanup") 23:58:17.899 |-->XResultSetPtr::XResultSetPtr 23:58:17.899 |   XResultSetPtr::XResultSetPtr count = [0], ptr = [(nil)], manageStmt =[NULL] 23:58:17.899 |<--XResultSetPtr::XResultSetPtr 23:58:17.899 |-->Connector::ensureStatement() 23:58:17.899 |-->Connector::ensureConnection() 23:58:17.899 |   Connector::ensureConnection() m_connection [0x8ee5028] 23:58:17.899 |<--Connector::ensureConnection() 23:58:17.899 |   Connector::ensureStatement() Statement [0x8ea54e8] 23:58:17.899 |<--Connector::ensureStatement() 23:58:17.899 |   Connector::executeQuery() 0x8ee5028 Creating ResultSetPtr for stmt [0x8ea54e8], managed 23:58:17.900 |-->XResultSetPtr::XResultSetPtr 23:58:17.900 |   XResultSetPtr::XResultSetPtr count = [1], ptr = [0x8ea5420], manageStmt =[YES] 23:58:17.900 |<--XResultSetPtr::XResultSetPtr 23:58:17.900 |-->XResultSetPtr::release1() 23:58:17.900 |<--XResultSetPtr::release1() 23:58:17.900 |-->XResultSetPtr::~XResultSetPtr, ptr = [0x8ea5420] 23:58:17.900 |-->XResultSetPtr::release1() 23:58:17.900 |   XResultSetPtr::release1() REL ResultSetPtr: count = [2], ptr = [0x8ea5420], manageStmt = [YES] 23:58:17.900 |<--XResultSetPtr::release1() 23:58:17.900 |<--XResultSetPtr::~XResultSetPtr, ptr = [0x8ea5420] 23:58:17.900 |   Connector::executeQuery() 0x8ee5028 ptr = [0x8ea5420] 23:58:17.900 |<--Connector::executeQuery() 0x8ee5028 23:58:17.900 |-->XResultSetPtr::release1() 23:58:17.900 |   XResultSetPtr::release1() REL ResultSetPtr: count = [1], ptr = [0x8e39368], manageStmt = [YES] 23:58:17.900 |   XResultSetPtr::release1() ABOUT TO DEL RS, ptr = [0x8e39368] 23:58:17.900 |   XResultSetPtr::release1() ABOUT TO DEL STMT = [0x8ee51d8] 23:58:17.900 |<--XResultSetPtr::release1() 23:58:17.900 |-->XResultSetPtr::~XResultSetPtr, ptr = [0x8ea5420] 23:58:17.900 |-->XResultSetPtr::release1() 23:58:17.900 |   XResultSetPtr::release1() REL ResultSetPtr: count = [2], ptr = [0x8ea5420], manageStmt = [YES] 23:58:17.900 |<--XResultSetPtr::release1() 23:58:17.900 |<--XResultSetPtr::~XResultSetPtr, ptr = [0x8ea5420] 23:58:17.964 |   updatestatsAUS Alert clean Count 0 23:58:17.964 |-->XResultSetPtr::~XResultSetPtr, ptr = [0x8ea5420] 23:58:17.964 |-->XResultSetPtr::release1() 23:58:17.964 |   XResultSetPtr::release1() REL ResultSetPtr: count = [1], ptr = [0x8ea5420], manageStmt = [YES] 23:58:17.964 |   XResultSetPtr::release1() ABOUT TO DEL RS, ptr = [0x8ea5420] 23:58:17.964 |   XResultSetPtr::release1() ABOUT TO DEL STMT = [0x8ea54e8] 23:58:17.964 |<--XResultSetPtr::release1() 23:58:17.964 |<--XResultSetPtr::~XResultSetPtr, ptr = [0x8ea5420] 23:58:17.964 |-->Connector::~Connector() 23:58:17.964 |   Connector::~Connector() Connector being destroyed DSN=[DSN=sysmaster;DATABASE=sysadmin;RECVTIMEOUT=300] 23:58:17.964 |-->DriverManager::retConnectionToPoolWithError() 23:58:17.964 |   DriverManager::retConnectionToPoolWithError() [4281] Clear bad ODBC connection. 23:58:17.964 |-->DriverManager::clearConn() 23:58:17.964 |   DriverManager::clearConn() moving connection [45] to FAILOVER list 23:58:17.964 |<--DriverManager::clearConn() 23:58:17.964 |   DriverManager::retConnectionToPoolWithError() [4281] Connections In Use [1] In Pool [1] Total Returned [76213] 23:58:17.964 |<--DriverManager::retConnectionToPoolWithError() 23:58:17.964 |<--Connector::~Connector() 23:58:17.964 |-->Connector::~Connector() 23:58:17.964 |   Connector::~Connector() Connector being destroyed DSN=[DSN=sysmaster;DATABASE=sysadmin;RECVTIMEOUT=300] 23:58:17.964 |-->DriverManager::retConnectionToPoolWithError() 23:58:17.964 |   DriverManager::retConnectionToPoolWithError() [4281] Clear bad ODBC connection. 23:58:17.964 |-->DriverManager::clearConn() 23:58:17.964 |   DriverManager::clearConn() moving connection [46] to FAILOVER list 23:58:17.964 |<--DriverManager::clearConn() 23:58:17.964 |   DriverManager::retConnectionToPoolWithError() [4281] Connections In Use [0] In Pool [0] Total Returned [76214] 23:58:17.964 |<--DriverManager::retConnectionToPoolWithError() 23:58:17.964 |<--Connector::~Connector() 23:58:17.964 |<--updatestatsAUS 23:58:17.964 |-->Connector::Connector()-stringdsn 23:58:17.964 |   Connector::Connector()-stringdsn useDSN [DSN=ccm_super] 23:58:17.964 |   Connector::Connector()-stringdsn Commit [1] 23:58:17.964 |-->DriverManager::stickpasswd() 23:58:17.964 |   DriverManager::stickpasswd() DSN is [DSN=ccm_super;RECVTIMEOUT=300] 23:58:17.964 |   DriverManager::stickpasswd() Found match with [DSN=ccm] semicolon index[13] 29 23:58:17.964 |<--DriverManager::stickpasswd() 23:58:17.964 |   Connector::Connector()-stringdsn m_dsn[DSN=ccm_super;RECVTIMEOUT=300] 23:58:17.964 |<--Connector::Connector()-stringdsn 23:58:17.964 |-->Connector::execute() (nil) 23:58:17.964 |execute procedure enablenotify() 23:58:17.964 |-->Connector::getTempStatement() 23:58:17.964 |-->Connector::ensureConnection() 23:58:17.965 |-->Connector::connect() 23:58:17.965 |   Connector::connect() ==> DSN [DSN=ccm_super;RECVTIMEOUT=300] 23:58:17.965 |-->Connector::tryConnection() 23:58:17.965 |-->DriverManager::getConnection() 23:58:17.965 |   DriverManager::getConnection() [4281] dsn=[DSN=ccm_super;RECVTIMEOUT=300] 23:58:17.965 |-->DriverManager::getConnectionFromPool() 23:58:17.965 |-->DriverManager::findUnused() 23:58:17.965 |   DriverManager::findUnused() [4281] Pool=[0] DSN=[DSN=ccm_super;RECVTIMEOUT=300] 23:58:17.965 |   DriverManager::findUnused() [4281] Could not find an unused connection to [DSN=ccm_super;RECVTIMEOUT=300]. 23:58:17.965 |<--DriverManager::findUnused() 23:58:17.965 |   DriverManager::getConnectionFromPool() [4281] Did not find free connection for DSN [DSN=ccm_super;RECVTIMEOUT=300]. Going to DriverManager. 23:58:17.995 |   DriverManager::getConnectionFromPool() [4281] odbc::Connection* [0x8e2c620] [47] 23:58:17.995 |-->DriverManager::addConn() 23:58:17.995 |<--DriverManager::addConn() 23:58:17.995 |<--DriverManager::getConnectionFromPool() 23:58:17.995 |   DriverManager::getConnection() [4281] Connections In Use [1] In Pool [1] Total Given [76215] Constructed [47] Destructed [46] 23:58:17.995 |<--DriverManager::getConnection() 23:58:17.995 |   Connector::tryConnection() Trying m_connection [0x8e2c620] 23:58:17.995 |   Connector::tryConnection() Have connection: testing tryConnection 23:58:17.995 |   Connector::tryConnection() set auto commit 23:58:17.995 |-->Connector::getTempStatement() 23:58:17.995 |-->Connector::ensureConnection() 23:58:17.995 |   Connector::ensureConnection() m_connection [0x8e2c620] 23:58:17.995 |<--Connector::ensureConnection() 23:58:17.995 |   Connector::getTempStatement() StatementPtr [0x8ea92b0] 23:58:17.995 |<--Connector::getTempStatement() 23:58:17.995 |   Connector::tryConnection() ###execute [set lock mode to wait 30] 23:58:17.995 |   Connector::tryConnection() Try SUCCEEDED m_connection [0x8e2c620] 23:58:17.995 |<--Connector::tryConnection() 23:58:17.995 |<--Connector::connect() 23:58:17.995 |   Connector::ensureConnection() m_connection [0x8e2c620] 23:58:17.995 |<--Connector::ensureConnection() 23:58:17.996 |   Connector::getTempStatement() StatementPtr [0x8ea92b0] 23:58:17.996 |<--Connector::getTempStatement() 23:58:17.997 |   Connector::execute() (nil) Result [FALSE] 23:58:17.997 |<--Connector::execute() (nil) 23:58:17.997 |-->Connector::~Connector() 23:58:17.997 |   Connector::~Connector() Connector being destroyed DSN=[DSN=ccm_super;RECVTIMEOUT=300] 23:58:17.997 |-->DriverManager::retConnectionToPool() 23:58:17.997 |   DriverManager::retConnectionToPool() [4281] ODBC connection [0x8e2c620] returned to pool. 23:58:17.997 |   DriverManager::retConnectionToPool() [4281] Connections In Use [0] In Pool [1] Total Returned [76215] 23:58:17.997 |<--DriverManager::retConnectionToPool() 23:58:17.997 |<--Connector::~Connector()

If you get error messages like this it is usually because /var/run/sshd does not exist.

root@userbox:/# service sshd status
● ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enab
   Active: failed (Result: start-limit-hit) since Wed 2019-04-10 02:24:44 EDT; 1
  Process: 511 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255)

Warning: Journal has been rotated since unit was started. Log output is incomple
root@userbox:/# service sshd start
Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details.



May 16 11:45:16userbox systemd[1]: ssh.service: Control process exited, code=exited status=255
May 16 11:45:16userbox systemd[1]: Failed to start OpenBSD Secure Shell server.
May 16 11:45:16userbox systemd[1]: ssh.service: Unit entered failed state.
May 16 11:45:16userbox systemd[1]: ssh.service: Failed with result 'exit-code'.
May 16 11:45:16userbox systemd[1]: ssh.service: Service hold-off time over, scheduling restart.
May 16 11:45:16userbox systemd[1]: Stopped OpenBSD Secure Shell server.
May 16 11:45:16userbox systemd[1]: ssh.service: Start request repeated too quickly.
May 16 11:45:16userbox systemd[1]: Failed to start OpenBSD Secure Shell server.
May 16 11:45:16userbox systemd[1]: ssh.service: Unit entered failed state.
May 16 11:45:16userbox systemd[1]: ssh.service: Failed with result 'start-limit-hit'.
 

This is a hack but is the simplest fix to this bug:

echo "mkdir -p /var/run/sshd" >> /etc/rc.local

*Double check rc.local to make sure the "exit 0" is at the end, otherwise the above won't work since it would not be executed.
 

*Also make sure that you have enabled the "rc-local service":

If the rc-local service is not enabled then the command above will not be executed since rc.local would not be used on startup without it being enabled with the command below.

systemctl enable rc-local

Basically we just need to create /var/run/sshd and restart SSHD and it will be good and SSH will start once again.

nmap by default only scans the most common, 1000 ports.

How about if you want all ports because some services may be listening on non-standard ports?

Just use the -p- switch for all ports or -p1-65535

nmap -p- somehost.com

I have seen this in a few rare cases after a reboot, where all folders and files will have the Read Only Attribute.  If you uncheck it, it will just come back.  It is more of a filesystem issue in Windows than a configuration issue and it looks like when Windows detects a badly corrupted filesystem that it will make things read-only, sort of like Linux would.

If you are Administrator or the owner of the folder and this is happening it is probably due to the reasoning mentioned below:

You can try this command:

attrib -r +s c:somepath

If it's just Windows being annoying/buggy the above should work.

But if it won't work and you may start noticing all folders have this read only attribute.

This issue is normally caused by filesystem errors and running chkdisk can normally fix it.

It is almost as intuitive as we would like it is just a *.

So literally:

* IN A 127.0.0.1

Complete working bind zonefile below:

$TTL    86400

@    IN    SOA    ns.rtt.ca. ns2.rtt.ca. (
            1247605715; Serial
            10800    ; Refresh
            3600    ; Retry
            604800    ; Expire
            10800 )    ; Minimum

*        IN CNAME rtt.ca.
rtt.ca.         IN A 191.15.11.61
forum            IN CNAME rtt.ca.
forums            IN CNAME rtt.ca.
rtt.ca.        IN NS ns1.rtt.com.
rtt.ca.        IN NS ns2.rtt.com.
webmail.rtt.ca.         IN A     191.15.11.55
mail.rtt.ca.         IN A     191.15.11.55
ftp.rtt.ca.         IN CNAME     rtt.ca.
www.rtt.ca.         IN CNAME     rtt.ca.
rtt.ca.         IN MX    10 mail.rtt.ca.
 

The strange thing is that usually the first install or two will work on any new machine but then it suddenly won't.  I had this experience on  QEMU 2.13 on a different machine. There is something finicky or buggy about the CUCM installer even when choosing the same virtual hardware specs.

qemu-kvm command:

/usr/libexec/qemu-kvm -version
QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2-2.506.el6_10.1), Copyright (c) 2003-2008 Fabrice Bellard
 

/usr/libexec/qemu-kvm -smp 6 -cdrom /mnt/vms/iso/Bootable_UCSInstall_UCOS_12.iso -boot once=d -vnc :9 -m 4096 -drive file=cucm-second-again.img,if=virtio -net nic,macaddr=ea:d9:1b:6d:e8:a3,model=virtio -net tap,ifname=tap49,script=no,downscript=no

This is the critical part and it is found by mounting /dev/sda6 using libguestfs:

guestmount -a cucm-second-again.img -m /dev/sda6 mount/

cat /log/install/install.log
 

05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 01:33:49 2019 cm-dbl-install  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|File:/opt/cisco/install/bin/component_install:821, Function: exec_progmeter(), /opt/cisco/install/bin/progmeter failed (1)|<LVL::Error>
05/01/2019 01:34:07 appmanager.sh|Internal Error, File:/usr/local/bin/base_scripts/appmanager.sh:153, Function: install(), failed to install infrastructure_post components|<LVL::Critical>
05/01/2019 01:34:07 post_install|File:/opt/cisco/install/bin/post_install:1030, Function: install_applications(), /usr/local/bin/base_scripts/appmanager.sh -install failed (1)|<LVL::Error>
05/01/2019 01:34:07 post_install|Exiting with result 1|<LVL::Info>
05/01/2019 01:34:07 post_install|INSTALL_TYPE="Basic Install"|<LVL::Debug>
05/01/2019 01:34:07 post_install|File:/opt/cisco/install/bin/post_install:721, Function: check_for_critical_error(), check_for_critical_error, found /common/log/install/critical.log, exiting|<LVL::Error>
05/01/2019 01:34:07 post_install|(CAPTURE) Mail notification cancelled - smtp server address for email not found! [/usr/local/platform/conf/platformConfig.xml]|<LVL::Debug>
05/01/2019 01:34:07 display_screen|Arguments: "Critical Error" "The installation has encountered a unrecoverable internal error. For further assistance report the following information to your support provider.


hssi_api_state_file

cat hssi_api_state_file

hardware_implementation_paths=../../server_implementation/KVM/RHEV/shared/bin/api_implementation.sh
HWModel=KVM
Vendor= Red Hat
CPUSpeed=(cpu64-rhel6)
CPUCount=6
MEMSize=4096
getDiskSize 1=128
getDiskSize 2=0
isPlatformVMware=1
getNumberOfDisks=


cat HSSI_LOG.txt
(05/01/2019 04:11:06 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:06 AM) DEBUG:[hssiInitialize] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(Wed May  1 04:11:06 UTC 2019) - No State file - sam_init sam_mode=HSSI_Mode sam_hssi_path=/mnt/source/Cisco/hssi/shared/bin sam_path=/mnt/source/Cisco/base_scripts
(05/01/2019 04:11:06 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:06 AM) DEBUG:[hardware isHardwareValid] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:06 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:06 AM) DEBUG:[getHardwareAttribute HWModel] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:06 AM) [KVM] retrieved from cache for key -[HWModel]-
(05/01/2019 04:11:06 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:06 AM) DEBUG:[getHardwareAttribute Vendor] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:06 AM) In runtime of KVM args [HssiDefines]
(05/01/2019 04:11:06 AM) In runtime of server_implementation args [HssiDefines]
(05/01/2019 04:11:07 AM) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:07 AM) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:07 AM) In runtime of RHEV args [Vendor]
(05/01/2019 04:11:07 AM) RHEV api_implementation.sh Vendor returns (0)
(05/01/2019 04:11:07 AM) HSSI set_inDataFile_forKey_value /tmp/hssi_api_state_file -> Vendor =  Red Hat
(05/01/2019 04:11:07 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:07 AM) DEBUG:[preBootHardwareSetup /tmp/hw_setup_log.txt /tmp/hw_setup_err.txt] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:07 AM) In runtime of KVM args [HssiDefines]
(05/01/2019 04:11:07 AM) In runtime of server_implementation args [HssiDefines]
(05/01/2019 04:11:07 AM) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:07 AM) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:07 AM) In runtime of RHEV args [preBootHardwareSetup /tmp/hw_setup_log.txt /tmp/hw_setup_err.txt]
(05/01/2019 04:11:07 AM) In runtime of KVM args [preBootHardwareSetup /tmp/hw_setup_log.txt /tmp/hw_setup_err.txt]
(05/01/2019 04:11:07 AM) In runtime of server_implementation args [preBootHardwareSetup /tmp/hw_setup_log.txt /tmp/hw_setup_err.txt]
(05/01/2019 04:11:07 AM) DEBUG: nothing to be setup for generic implementation
(05/01/2019 04:11:07 AM) server_implementation shared_implementation.sh preBootHardwareSetup /tmp/hw_setup_log.txt /tmp/hw_setup_err.txt returns (0)
(05/01/2019 04:11:07 AM) KVM shared_implementation.sh preBootHardwareSetup /tmp/hw_setup_log.txt /tmp/hw_setup_err.txt returns (0)
(05/01/2019 04:11:07 AM) RHEV api_implementation.sh preBootHardwareSetup /tmp/hw_setup_log.txt /tmp/hw_setup_err.txt returns (0)
(05/01/2019 04:11:07 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:07 AM) DEBUG:[getMountedDiskPartitions] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:07 AM) In runtime of KVM args [HssiDefines]
(05/01/2019 04:11:07 AM) In runtime of server_implementation args [HssiDefines]
(05/01/2019 04:11:08 AM) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:08 AM) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:08 AM) In runtime of RHEV args [getMountedDiskPartitions]
(05/01/2019 04:11:08 AM) In runtime of KVM args [getMountedDiskPartitions]
(05/01/2019 04:11:08 AM) In runtime of server_implementation args [getMountedDiskPartitions]
(05/01/2019 04:11:08 AM) server_implementation shared_implementation.sh getMountedDiskPartitions returns (0)
(05/01/2019 04:11:08 AM) KVM shared_implementation.sh getMountedDiskPartitions returns (0)
(05/01/2019 04:11:08 AM) RHEV api_implementation.sh getMountedDiskPartitions returns (0)
(05/01/2019 04:11:08 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:08 AM) DEBUG:[isMotorizedDVD] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:08 AM) In runtime of KVM args [HssiDefines]
(05/01/2019 04:11:08 AM) In runtime of server_implementation args [HssiDefines]
(05/01/2019 04:11:08 AM) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:08 AM) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:08 AM) In runtime of RHEV args [isMotorizedDVD]
(05/01/2019 04:11:08 AM) In runtime of KVM args [isMotorizedDVD]
(05/01/2019 04:11:08 AM) In runtime of server_implementation args [isMotorizedDVD]
(05/01/2019 04:11:08 AM) server_implementation shared_implementation.sh isMotorizedDVD returns (1)
(05/01/2019 04:11:08 AM) KVM shared_implementation.sh isMotorizedDVD returns (1)
(05/01/2019 04:11:08 AM) RHEV api_implementation.sh isMotorizedDVD returns (1)
(05/01/2019 04:11:09 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:09 AM) DEBUG:[getHardwareAttribute CPUSpeed] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:09 AM) In runtime of KVM args [HssiDefines]
(05/01/2019 04:11:09 AM) In runtime of server_implementation args [HssiDefines]
(05/01/2019 04:11:09 AM) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:09 AM) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:09 AM) In runtime of RHEV args [getHardwareAttribute CPUSpeedInMHz]
(05/01/2019 04:11:09 AM) In runtime of RHEV args [CPUSpeedInMHz]
(05/01/2019 04:11:09 AM) In runtime of KVM args [CPUSpeedInMHz]
(05/01/2019 04:11:09 AM) In runtime of server_implementation args [CPUSpeedInMHz]
(05/01/2019 04:11:09 AM) server_implementation shared_implementation.sh CPUSpeedInMHz returns (0)
(05/01/2019 04:11:10 AM) KVM shared_implementation.sh CPUSpeedInMHz returns (0)
(05/01/2019 04:11:10 AM) RHEV api_implementation.sh CPUSpeedInMHz returns (0)
(05/01/2019 04:11:10 AM) RHEV api_implementation.sh getHardwareAttribute CPUSpeedInMHz returns (0)
(05/01/2019 04:11:10 AM) HSSI set_inDataFile_forKey_value /tmp/hssi_api_state_file -> CPUSpeed = (cpu64-rhel6)
(05/01/2019 04:11:10 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:10 AM) DEBUG:[getHardwareAttribute CPUCount] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:10 AM) In runtime of KVM args [HssiDefines]
(05/01/2019 04:11:10 AM) In runtime of server_implementation args [HssiDefines]
(05/01/2019 04:11:10 AM) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:10 AM) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:10 AM) In runtime of RHEV args [CPUCount]
(05/01/2019 04:11:10 AM) In runtime of KVM args [CPUCount]
(05/01/2019 04:11:10 AM) In runtime of server_implementation args [CPUCount]
(05/01/2019 04:11:10 AM) server_implementation shared_implementation.sh CPUCount returns (0)
(05/01/2019 04:11:10 AM) KVM shared_implementation.sh CPUCount returns (0)
(05/01/2019 04:11:10 AM) RHEV api_implementation.sh CPUCount returns (0)
(05/01/2019 04:11:10 AM) HSSI set_inDataFile_forKey_value /tmp/hssi_api_state_file -> CPUCount = 6
(05/01/2019 04:11:10 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:10 AM) DEBUG:[getHardwareAttribute MEMSize] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:10 AM) In runtime of KVM args [HssiDefines]
(05/01/2019 04:11:10 AM) In runtime of server_implementation args [HssiDefines]
(05/01/2019 04:11:11 AM) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:11 AM) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:11 AM) In runtime of RHEV args [MemUnits]
(05/01/2019 04:11:11 AM) In runtime of KVM args [MemUnits]
(05/01/2019 04:11:11 AM) In runtime of server_implementation args [MemUnits]
(05/01/2019 04:11:11 AM) server_implementation shared_implementation.sh MemUnits returns (0)
(05/01/2019 04:11:11 AM) KVM shared_implementation.sh MemUnits returns (0)
(05/01/2019 04:11:11 AM) RHEV api_implementation.sh MemUnits returns (0)
(05/01/2019 04:11:11 AM) In runtime of KVM args [HssiDefines]
(05/01/2019 04:11:11 AM) In runtime of server_implementation args [HssiDefines]
(05/01/2019 04:11:11 AM) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:11 AM) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:11 AM) In runtime of RHEV args [getHardwareAttribute MEMSize]
(05/01/2019 04:11:11 AM) In runtime of RHEV args [MEMSize]
(05/01/2019 04:11:11 AM) In runtime of KVM args [MEMSize]
(05/01/2019 04:11:11 AM) In runtime of server_implementation args [MEMSize]
(05/01/2019 04:11:11 AM) server_implementation shared_implementation.sh MEMSize returns (0)
(05/01/2019 04:11:11 AM) KVM shared_implementation.sh MEMSize returns (0)
(05/01/2019 04:11:11 AM) RHEV api_implementation.sh MEMSize returns (0)
(05/01/2019 04:11:11 AM) RHEV api_implementation.sh getHardwareAttribute MEMSize returns (0)
(05/01/2019 04:11:11 AM) HSSI set_inDataFile_forKey_value /tmp/hssi_api_state_file -> MEMSize = 4096
(05/01/2019 04:11:11 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:11 AM) DEBUG:[hardware getDiskSize 1] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:11 AM) In runtime of KVM args [HssiDefines]
(05/01/2019 04:11:11 AM) In runtime of server_implementation args [HssiDefines]
(05/01/2019 04:11:12 AM) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:12 AM) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:12 AM) In runtime of RHEV args [getDiskSize 1]
(05/01/2019 04:11:12 AM) In runtime of RHEV args [disk_access]
(05/01/2019 04:11:12 AM) RHEV api_implementation.sh disk_access returns (0)
(05/01/2019 04:11:12 AM) In runtime of KVM args [getProcDiskSize vda]
(05/01/2019 04:11:12 AM) In runtime of server_implementation args [getProcDiskSize vda]
(05/01/2019 04:11:12 AM) server_implementation shared_implementation.sh getProcDiskSize vda returns (0)
(05/01/2019 04:11:12 AM) KVM shared_implementation.sh getProcDiskSize vda returns (0)
(05/01/2019 04:11:12 AM) RHEV api_implementation.sh getDiskSize 1 returns (0)
(05/01/2019 04:11:12 AM) HSSI set_inDataFile_forKey_value /tmp/hssi_api_state_file -> getDiskSize 1 = 128
(05/01/2019 04:11:12 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:12 AM) DEBUG:[hardware getDiskSize 2] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:12 AM) In runtime of KVM args [HssiDefines]
(05/01/2019 04:11:12 AM) In runtime of server_implementation args [HssiDefines]
(05/01/2019 04:11:12 AM) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:12 AM) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:12 AM) In runtime of RHEV args [getDiskSize 2]
(05/01/2019 04:11:12 AM) In runtime of RHEV args [disk_access]
(05/01/2019 04:11:12 AM) RHEV api_implementation.sh disk_access returns (0)
(05/01/2019 04:11:12 AM) In runtime of KVM args [getProcDiskSize vdb]
(05/01/2019 04:11:12 AM) In runtime of server_implementation args [getProcDiskSize vdb]
(05/01/2019 04:11:12 AM) server_implementation shared_implementation.sh getProcDiskSize vdb returns (0)
(05/01/2019 04:11:12 AM) KVM shared_implementation.sh getProcDiskSize vdb returns (0)
(05/01/2019 04:11:12 AM) RHEV api_implementation.sh getDiskSize 2 returns (0)
(05/01/2019 04:11:12 AM) HSSI set_inDataFile_forKey_value /tmp/hssi_api_state_file -> getDiskSize 2 = 0
(05/01/2019 04:11:13 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:13 AM) DEBUG:[isPlatformVMware] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:13 AM) In runtime of KVM args [HssiDefines]
(05/01/2019 04:11:13 AM) In runtime of server_implementation args [HssiDefines]
(05/01/2019 04:11:13 AM) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:13 AM) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:13 AM) In runtime of RHEV args [isPlatformVMware]
(05/01/2019 04:11:13 AM) In runtime of KVM args [isPlatformVMware]
(05/01/2019 04:11:13 AM) In runtime of server_implementation args [isPlatformVMware]
(05/01/2019 04:11:13 AM) server_implementation shared_implementation.sh isPlatformVMware returns (1)
(05/01/2019 04:11:13 AM) KVM shared_implementation.sh isPlatformVMware returns (1)
(05/01/2019 04:11:13 AM) RHEV api_implementation.sh isPlatformVMware returns (1)
(05/01/2019 04:11:13 AM) HSSI set_inDataFile_forKey_value /tmp/hssi_api_state_file -> isPlatformVMware = 1
(05/01/2019 04:11:21 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:21 AM) DEBUG:[hardware getNumberOfDisks] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:21 AM) In runtime of KVM args [HssiDefines]
(05/01/2019 04:11:21 AM) In runtime of server_implementation args [HssiDefines]
(05/01/2019 04:11:21 AM) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:21 AM) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/2019 04:11:21 AM) In runtime of RHEV args [getNumberOfDisks]
(05/01/2019 04:11:21 AM) In runtime of RHEV args [disk_access]
(05/01/2019 04:11:22 AM) RHEV api_implementation.sh disk_access returns (0)
(05/01/2019 04:11:22 AM) RHEV api_implementation.sh getNumberOfDisks returns (1)
(05/01/2019 04:11:22 AM) HSSI set_inDataFile_forKey_value /tmp/hssi_api_state_file -> getNumberOfDisks =
(05/01/2019 04:11:22 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:22 AM) DEBUG:[hardware isHardwareValid] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:22 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:22 AM) DEBUG:[hardware isPlatformVMware] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:22 AM) [1] retrieved from cache for key -[isPlatformVMware]-
(05/01/2019 04:11:24 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:24 AM) DEBUG:[getHardwareAttribute CPUSpeed] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:24 AM) [(cpu64-rhel6)] retrieved from cache for key -[CPUSpeed]-
(05/01/2019 04:11:24 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:24 AM) DEBUG:[getHardwareAttribute CPUCount] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:24 AM) [6] retrieved from cache for key -[CPUCount]-
(05/01/2019 04:11:24 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:24 AM) DEBUG:[getHardwareAttribute MEMSize] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:24 AM) [4096] retrieved from cache for key -[MEMSize]-
(05/01/2019 04:11:24 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:24 AM) DEBUG:[hardware getDiskSize 1] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:24 AM) [128] retrieved from cache for key -[getDiskSize 1]-
(05/01/2019 04:11:24 AM) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/2019 04:11:24 AM) DEBUG:[hardware getDiskSize 2] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/2019 04:11:24 AM) [0] retrieved from cache for key -[getDiskSize 2]-
(05/01/19 04:12:46) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/19 04:12:46) DEBUG:[hardware getNumberOfDisks] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/19 04:12:46) In runtime of KVM args [HssiDefines]
(05/01/19 04:12:47) In runtime of server_implementation args [HssiDefines]
(05/01/19 04:12:47) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/19 04:12:47) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/19 04:12:47) In runtime of RHEV args [getNumberOfDisks]
(05/01/19 04:12:47) In runtime of RHEV args [disk_access]
(05/01/19 04:12:47) RHEV api_implementation.sh disk_access returns (0)
(05/01/19 04:12:47) RHEV api_implementation.sh getNumberOfDisks returns (1)
(05/01/19 04:12:47) HSSI set_inDataFile_forKey_value /tmp/hssi_api_state_file -> getNumberOfDisks =
(05/01/19 04:12:47) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/19 04:12:47) DEBUG:[hardware getDiskSize 1] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/19 04:12:47) [128] retrieved from cache for key -[getDiskSize 1]-
(05/01/19 04:12:47) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/19 04:12:47) DEBUG:[hardware getDiskBlockSize 1] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/19 04:12:47) In runtime of KVM args [HssiDefines]
(05/01/19 04:12:47) In runtime of server_implementation args [HssiDefines]
(05/01/19 04:12:47) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/19 04:12:47) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/19 04:12:47) In runtime of RHEV args [getHardwareAttribute getDiskBlockSize 1]
(05/01/19 04:12:47) In runtime of RHEV args [getDiskBlockSize 1]
(05/01/19 04:12:47) In runtime of RHEV args [disk_access]
(05/01/19 04:12:47) RHEV api_implementation.sh disk_access returns (0)
(05/01/19 04:12:47) In runtime of KVM args [getProcDiskBlockSize vda]
(05/01/19 04:12:47) In runtime of server_implementation args [getProcDiskBlockSize vda]
(05/01/19 04:12:47) server_implementation shared_implementation.sh getProcDiskBlockSize vda returns (0)
(05/01/19 04:12:47) KVM shared_implementation.sh getProcDiskBlockSize vda returns (0)
(05/01/19 04:12:47) RHEV api_implementation.sh getDiskBlockSize 1 returns (0)
(05/01/19 04:12:47) RHEV api_implementation.sh getHardwareAttribute getDiskBlockSize 1 returns (0)
(05/01/19 04:12:50) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/19 04:12:50) DEBUG:[hardware getDiskName 1] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/19 04:12:50) In runtime of KVM args [HssiDefines]
(05/01/19 04:12:50) In runtime of server_implementation args [HssiDefines]
(05/01/19 04:12:50) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/19 04:12:50) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/19 04:12:50) In runtime of RHEV args [getHardwareAttribute getDiskName 1]
(05/01/19 04:12:50) In runtime of RHEV args [getDiskName 1]
(05/01/19 04:12:51) In runtime of RHEV args [disk_access]
(05/01/19 04:12:51) RHEV api_implementation.sh disk_access returns (0)
(05/01/19 04:12:51) In runtime of KVM args [getProcDiskName vda]
(05/01/19 04:12:51) In runtime of server_implementation args [getProcDiskName vda]
(05/01/19 04:12:51) server_implementation shared_implementation.sh getProcDiskName vda returns (0)
(05/01/19 04:12:51) KVM shared_implementation.sh getProcDiskName vda returns (0)
(05/01/19 04:12:51) RHEV api_implementation.sh getDiskName 1 returns (0)
(05/01/19 04:12:51) RHEV api_implementation.sh getHardwareAttribute getDiskName 1 returns (0)
(05/01/19 04:35:32) IN INITIALIZE model = KVM statefile=  /tmp/hssi_api_state_file
(05/01/19 04:35:32) DEBUG:[getHwRpmList] Current Directory=/mnt/source/Cisco/hssi/shared/bin
(05/01/19 04:35:33) In runtime of KVM args [HssiDefines]
(05/01/19 04:35:33) In runtime of server_implementation args [HssiDefines]
(05/01/19 04:35:33) server_implementation shared_implementation.sh HssiDefines returns (0)
(05/01/19 04:35:33) KVM shared_implementation.sh HssiDefines returns (0)
(05/01/19 04:35:33) In runtime of RHEV args [getHwRpmList]
(05/01/19 04:35:33) In runtime of KVM args [getHwRpmList]
(05/01/19 04:35:33) In runtime of server_implementation args [getHwRpmList]
(05/01/19 04:35:33) server_implementation shared_implementation.sh getHwRpmList returns (1)
(05/01/19 04:35:33) KVM shared_implementation.sh getHwRpmList returns (1)
(05/01/19 04:35:33) RHEV api_implementation.sh getHwRpmList returns (1)


cat initial_hardware_info
Vendor= Red Hat
HWModel=KVM
CPUCount=6
CPUType= QEMU Virtual CPU version (cpu64-rhel6)
CPUSpeed=(cpu64-rhel6)
MEMSize=4096
BIOSVer=Seabios 0.5.1 01/01/2007
ObjectId=KVM
OSVersion=UCOS 6.0.0.0-2.i386
SerialNumber= Not Specified
VendorOID=
areDisksAligned=0
isHardwareUnsupported=1
 

cat partAlloc
clearpart --drives=vda --all --initlabel
part swap --size 4000 --ondisk vda
part / --fstype ext4 --size 21648 --asprimary --ondisk vda
part /partB --fstype ext4 --size 21648 --asprimary --ondisk vda
part /grub --fstype ext4 --size 256 --asprimary --ondisk vda
part /common --fstype ext4 --size 1 --grow --ondisk vda


install.log (most of it)

04/30/2019 22:47:34 InstallWizard|newtFormRun exited. reason=1|<LVL::Info>
04/30/2019 22:47:34 InstallWizard|installWizard service deactivated|<LVL::Info>
04/30/2019 22:47:34 InstallWizard|validateNetworking Failed, user requested CONTINUE of the Install|<LVL::Warn>
04/30/2019 22:47:34 InstallWizard|validateNetworking Failed, validateNetworkingBypassEnabled set to TRUE|<LVL::Warn>
04/30/2019 22:47:34 InstallWizard|adminAcctConfigEnabled: admin='optional'.|<LVL::Debug>
04/30/2019 22:47:34 InstallWizard|validateAdminCredentials: valid administrator id admin|<LVL::Info>
04/30/2019 22:47:34 InstallWizard|multideployConfigEnabled: multideploy='optional'.|<LVL::Debug>
04/30/2019 22:47:34 InstallWizard|Updating /usr/local/platform/conf/platformConfig.xml|<LVL::Info>
04/30/2019 22:47:34 InstallWizard|6f e2 98 18|<LVL::Debug>
04/30/2019 22:47:34 InstallWizard|written 6267 bytes to /usr/local/platform/conf/platformConfig.xml|<LVL::Info>
04/30/2019 22:47:34 InstallWizard|finally salt = $5$wD3LN74K$|<LVL::Info>
04/30/2019 22:47:34 InstallWizard|runScript: Closing inewt|<LVL::Debug>
04/30/2019 22:47:34 InstallWizard|runScript: Calling system("/root/.security/unimmunize.sh >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:34 InstallWizard|runScript: 0 = system("/root/.security/unimmunize.sh >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:34 InstallWizard|runScript: Opening inewt|<LVL::Debug>
04/30/2019 22:47:34 InstallWizard|runScript: Closing inewt|<LVL::Debug>
04/30/2019 22:47:34 InstallWizard|runScript: Calling system("/usr/sbin/groupadd administrator >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:35 InstallWizard|(CAPTURE) groupadd: group 'administrator' already exists|<LVL::Debug>
04/30/2019 22:47:35 InstallWizard|runScript: 2304 = system("/usr/sbin/groupadd administrator >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:35 InstallWizard|runScript: Opening inewt|<LVL::Debug>
04/30/2019 22:47:35 InstallWizard|Created selinux security directory|<LVL::Info>
04/30/2019 22:47:35 InstallWizard|Opened selinux admin role shell script|<LVL::Info>
04/30/2019 22:47:35 InstallWizard|Added selinux admin role to shell script|<LVL::Info>
04/30/2019 22:47:35 InstallWizard|Added selinux admin login to shell script|<LVL::Info>
04/30/2019 22:47:35 InstallWizard|runScript: Closing inewt|<LVL::Debug>
04/30/2019 22:47:35 InstallWizard|runScript: Calling system("/usr/sbin/adduser -s /usr/local/platform/bin/startcliscript.sh -g administrator -p '$5$wD3LN74K$RZ8V/o3t5o0r0h0aexUL03/k3XsmCvQEsOFOC/2oT41' admin >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:36 InstallWizard|runScript: 0 = system("/usr/sbin/adduser -s /usr/local/platform/bin/startcliscript.sh -g administrator -p '$5$wD3LN74K$RZ8V/o3t5o0r0h0aexUL03/k3XsmCvQEsOFOC/2oT41' admin >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:36 InstallWizard|runScript: Opening inewt|<LVL::Debug>
04/30/2019 22:47:36 InstallWizard|runScript: Closing inewt|<LVL::Debug>
04/30/2019 22:47:36 InstallWizard|runScript: Calling system("/usr/sbin/usermod -p '$5$wD3LN74K$RZ8V/o3t5o0r0h0aexUL03/k3XsmCvQEsOFOC/2oT41' adminsftp >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|runScript: 0 = system("/usr/sbin/usermod -p '$5$wD3LN74K$RZ8V/o3t5o0r0h0aexUL03/k3XsmCvQEsOFOC/2oT41' adminsftp >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|runScript: Opening inewt|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|runScript: Closing inewt|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|runScript: Calling system("/root/.security/immunize.sh >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|runScript: 0 = system("/root/.security/immunize.sh >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|runScript: Opening inewt|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|csrConfigEnabled: cert='optional'.|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|Organziation = "aasdfas             "|<LVL::Info>
04/30/2019 22:47:37 InstallWizard|Unit = "sdafasd             "|<LVL::Info>
04/30/2019 22:47:37 InstallWizard|Location = "fsdf                "|<LVL::Info>
04/30/2019 22:47:37 InstallWizard|State = "sfas                "|<LVL::Info>
04/30/2019 22:47:37 InstallWizard|Country = "US        "|<LVL::Info>
04/30/2019 22:47:37 InstallWizard|runScript: Closing inewt|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|runScript: Calling system("/usr/local/bin/base_scripts/sd_zoneinfo America/Los_Angeles >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|runScript: 0 = system("/usr/local/bin/base_scripts/sd_zoneinfo America/Los_Angeles >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|runScript: Opening inewt|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|set TZ='America/Los_Angeles' succeeded|<LVL::Info>
04/30/2019 22:47:37 InstallWizard|The time zone has been set.  Updating the system clock|<LVL::Info>
04/30/2019 22:47:37 InstallWizard|runScript: Closing inewt|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|runScript: Calling system("/usr/sbin/hwclock --systz >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|runScript: 0 = system("/usr/sbin/hwclock --systz >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|runScript: Opening inewt|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|ntpConfigEnabled: ntp='optional'.|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|clusterConfigEnabled: cluster='optional'.|<LVL::Debug>
04/30/2019 22:47:37 InstallWizard|Calling /usr/local/bin/base_scripts/ipprefs --portTag ntp --enable |<LVL::Info>
04/30/2019 22:47:37 InstallWizard|runScriptPassive: Calling system("/usr/local/bin/base_scripts/ipprefs --portTag ntp --enable >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:47 InstallWizard|runScriptPassive: 0 = system("/usr/local/bin/base_scripts/ipprefs --portTag ntp --enable >/common/log/install/capture.txt 2>&1")|<LVL::Debug>
04/30/2019 22:47:47 InstallWizard|runScriptPassive: correcting rc per system/script call; returning rc=0|<LVL::Debug>
04/30/2019 22:47:47 InstallWizard|Relying on system/HW clock.|<LVL::Info>
04/30/2019 22:47:47 InstallWizard|ipmScriptListInit|<LVL::Debug>
04/30/2019 22:47:47 InstallWizard|ipmScriptListAdd: /usr/local/bin/base_scripts/sd_ntp -defaultConf|<LVL::Debug>
04/30/2019 22:47:47 InstallWizard|ipmScriptListRun: desc="Setting up NTP server to use hardware clock as time source ...", title="NTP Configuration", items=1|<LVL::Debug>
04/30/2019 22:47:47 IPM|Open progress meter "NTP Configuration"|<LVL::Info>
04/30/2019 22:47:47 IPM|  begin-of-session "Setting up NTP server to use hardware clock as time source ...", 1 items|<LVL::Info>
04/30/2019 22:47:47 IPM|    ipmDoTimedCommand: cmd="/usr/local/bin/base_scripts/sd_ntp -defaultConf", est(sec)=60, max(sec)=300|<LVL::Debug>
04/30/2019 22:47:47 IPM|    begin-of-work: [cmd="/usr/local/bin/base_scripts/sd_ntp -defaultConf"]|<LVL::Info>
04/30/2019 22:47:47 IPM-Child|execlp(/tmp/.ipmbzd4Pg) for cmd "/usr/local/bin/base_scripts/sd_ntp -defaultConf"|<LVL::Debug>
04/30/2019 22:47:47 IPM|(CAPTURE) rc=0|<LVL::Debug>
04/30/2019 22:47:47 IPM|    end-of-work: [cmd="/usr/local/bin/base_scripts/sd_ntp -defaultConf"]|<LVL::Info>
04/30/2019 22:47:47 IPM|Child's return-status = 0x00000000|<LVL::Debug>
04/30/2019 22:47:50 IPM|  end-of-session "Setting up NTP server to use hardware clock as time source ...": 3.253 secs.|<LVL::Info>
04/30/2019 22:47:50 IPM|Close progress meter "NTP Configuration"|<LVL::Info>
04/30/2019 22:47:50 InstallWizard|Security password = Passed|<LVL::Info>
04/30/2019 22:47:50 InstallWizard|6f e2 98 18|<LVL::Debug>
04/30/2019 22:47:50 InstallWizard|Updating /usr/local/platform/conf/platformConfig.xml|<LVL::Info>
04/30/2019 22:47:50 InstallWizard|openPlatformXml: Parse existing xml document /usr/local/platform/conf/platformConfig.xml.|<LVL::Info>
04/30/2019 22:47:50 InstallWizard|6f e2 98 18|<LVL::Debug>
04/30/2019 22:47:50 InstallWizard|written 6267 bytes to /usr/local/platform/conf/platformConfig.xml|<LVL::Info>
04/30/2019 22:47:50 InstallWizard|ipmScriptListInit|<LVL::Debug>
04/30/2019 22:47:50 InstallWizard|ipmScriptListAdd: /root/.security/sftp/update_sftpuser_pwd.sh|<LVL::Debug>
04/30/2019 22:47:50 InstallWizard|ipmScriptListRun: desc="Running Security Configuration", title="Security Configuration", items=1|<LVL::Debug>
04/30/2019 22:47:50 IPM|Open progress meter "Security Configuration"|<LVL::Info>
04/30/2019 22:47:50 IPM|  begin-of-session "Running Security Configuration", 1 items|<LVL::Info>
04/30/2019 22:47:50 IPM|    ipmDoTimedCommand: cmd="/root/.security/sftp/update_sftpuser_pwd.sh", est(sec)=60, max(sec)=300|<LVL::Debug>
04/30/2019 22:47:50 IPM|    begin-of-work: [cmd="/root/.security/sftp/update_sftpuser_pwd.sh"]|<LVL::Info>
04/30/2019 22:47:50 IPM-Child|execlp(/tmp/.ipmenpo1t) for cmd "/root/.security/sftp/update_sftpuser_pwd.sh"|<LVL::Debug>
04/30/2019 22:47:51 IPM|(CAPTURE) Changing password for user sftpuser.|<LVL::Debug>
04/30/2019 22:47:51 IPM|(CAPTURE) passwd: all authentication tokens updated successfully.|<LVL::Debug>
04/30/2019 22:47:51 IPM|(CAPTURE) Changing password for user drfuser.|<LVL::Debug>
04/30/2019 22:47:51 IPM|(CAPTURE) passwd: all authentication tokens updated successfully.|<LVL::Debug>
04/30/2019 22:47:51 IPM|(CAPTURE) Changing password for user drfkeys.|<LVL::Debug>
04/30/2019 22:47:51 IPM|(CAPTURE) passwd: all authentication tokens updated successfully.|<LVL::Debug>
04/30/2019 22:47:51 IPM|(CAPTURE) Set user-specified password for sftpuser, drfuser and drfkeys|<LVL::Debug>
04/30/2019 22:47:51 IPM|(CAPTURE) rc=0|<LVL::Debug>
04/30/2019 22:47:51 IPM|    end-of-work: [cmd="/root/.security/sftp/update_sftpuser_pwd.sh"]|<LVL::Info>
04/30/2019 22:47:51 IPM|Child's return-status = 0x00000000|<LVL::Debug>
04/30/2019 22:47:55 IPM|  end-of-session "Running Security Configuration": 4.352 secs.|<LVL::Info>
04/30/2019 22:47:55 IPM|Close progress meter "Security Configuration"|<LVL::Info>
04/30/2019 22:47:55 InstallWizard|Security configuration OK|<LVL::Info>
04/30/2019 22:47:55 InstallWizard|smtpConfigMandatory: smtp='optional'.|<LVL::Debug>
04/30/2019 22:47:55 InstallWizard|smtpConfigOptional: smtp='optional'.|<LVL::Debug>
04/30/2019 22:47:55 InstallWizard|applAcctConfigEnabled: appusr='optional'.|<LVL::Debug>
04/30/2019 22:47:55 InstallWizard|Validating Application User Credentials|<LVL::Info>
04/30/2019 22:47:55 InstallWizard|validateApplUserCredentials: valid application username id app|<LVL::Info>
04/30/2019 22:47:55 InstallWizard|validateData() status 1|<LVL::Info>
04/30/2019 22:47:55 InstallWizard|Data validation complete.|<LVL::Info>
04/30/2019 22:47:55 InstallWizard|Getting CallManager wizard|<LVL::Info>
04/30/2019 22:47:55 InstallWizard|Wizard not found for CallManager|<LVL::Info>
04/30/2019 22:47:55 InstallWizard|Getting Selfcare wizard|<LVL::Info>
04/30/2019 22:47:55 InstallWizard|Wizard not found for Selfcare|<LVL::Info>
04/30/2019 22:47:55 InstallWizard|multideployConfigEnabled: multideploy='optional'.|<LVL::Debug>
04/30/2019 22:47:55 InstallWizard|Updating /usr/local/platform/conf/platformConfig.xml|<LVL::Info>
04/30/2019 22:47:55 InstallWizard|openPlatformXml: Parse existing xml document /usr/local/platform/conf/platformConfig.xml.|<LVL::Info>
04/30/2019 22:47:56 InstallWizard|clusterConfigEnabled: cluster='optional'.|<LVL::Debug>
04/30/2019 22:47:56 InstallWizard|'/usr/local/platform/bin/clm/clm_ctl set install_configuration_complete yes'  executed successfully|<LVL::Info>
04/30/2019 22:47:56 InstallWizard|6f e2 98 18|<LVL::Debug>
04/30/2019 22:47:56 InstallWizard|written 6268 bytes to /usr/local/platform/conf/platformConfig.xml|<LVL::Info>
04/30/2019 22:47:56 InstallWizard|Exiting InstallWizard with return code 0|<LVL::Info>
04/30/2019 22:47:56 platform-events.sh|Received request for platform-event (platform-configuration-complete)|<LVL::Info>
04/30/2019 22:47:56 platform-events.sh|emitting platform-event (platform-configuration-complete)|<LVL::Info>
04/30/2019 22:47:56 platform-events.sh|emitted platform-event (platform-configuration-complete)|<LVL::Info>
04/30/2019 22:47:56 post_install|Changing reserved block percentage on root from 5% to 1%|<LVL::Debug>
04/30/2019 22:47:56 post_install|Reserved block percentage on root changed to 1%|<LVL::Debug>
04/30/2019 22:47:56 post_install|Installing platform prefs files|<LVL::Info>
04/30/2019 22:47:56 post_install|Calling "/usr/local/bin/base_scripts/sd_prefs -set ALL"|<LVL::Debug>
04/30/2019 22:47:57 post_install|Calling "/usr/local/bin/base_scripts/sd_installprefs -set ALL"|<LVL::Debug>
04/30/2019 22:47:58 post_install|Platform prefs files install complete|<LVL::Info>
04/30/2019 22:47:58 post_install|Checking if CLI disabling is supported ..|<LVL::Info>
04/30/2019 22:48:02 removeCliAccess.sh|The product Cisco Unified Communications Manager supports CLI (Command Line) access|<LVL::Info>
04/30/2019 22:48:02 post_install|Install applications|<LVL::Info>
04/30/2019 22:48:02 post_install|Calling /usr/local/bin/base_scripts/appmanager.sh -install|<LVL::Debug>
04/30/2019 22:48:04 appmanager.sh|Appliation install RTMTStart|<LVL::Notice>
04/30/2019 22:48:04 appmanager.sh|Parse argument -install|<LVL::Debug>
04/30/2019 22:48:04 appmanager.sh|action type is install|<LVL::Debug>
04/30/2019 22:48:04 appmanager.sh|Application install starting|<LVL::Info>
04/30/2019 22:48:04 InstallWizard|Platform Install: installWizMain.c@@/main/161|<LVL::Info>
04/30/2019 22:48:04 InstallWizard|Reencrypt password|<LVL::Info>
04/30/2019 22:48:04 InstallWizard|Running from local disk|<LVL::Info>
04/30/2019 22:48:07 InstallWizard|fipsAESAlgoConfig: fipsAES='optional'.|<LVL::Debug>
04/30/2019 22:48:07 InstallWizard|applAcctConfigEnabled: appusr='optional'.|<LVL::Debug>
04/30/2019 22:48:07 InstallWizard|ccmEncryptionConfigOptional: dynamicKeyCCMEncryption='enable'.|<LVL::Debug>
04/30/2019 22:48:07 InstallWizard|Populating config from file /usr/local/platform/conf/platformConfig.xml|<LVL::Info>
04/30/2019 22:48:07 InstallWizard|openPlatformXml: Parse existing xml document /usr/local/platform/conf/platformConfig.xml.|<LVL::Info>
04/30/2019 22:48:07 InstallWizard|ProductDeployment 'callmanager'|<LVL::Info>
04/30/2019 22:48:07 InstallWizard|Install or upgrade type 'Basic Install'|<LVL::Info>
04/30/2019 22:48:07 InstallWizard|timezoneConfigEnabled: timezone='optional'.|<LVL::Debug>
04/30/2019 22:48:07 InstallWizard|ApplUserUsername 'app'|<LVL::Info>
04/30/2019 22:48:07 InstallWizard|Tag ApplUserDbPwCrypt not found.|<LVL::Warn>
04/30/2019 22:48:08 InstallWizard|ReencryptFlag set to FALSE|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|NIC Auto Negotiate set to TRUE|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Host Name for this machine 'PubSecond'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Change MTU set to FALSE|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Is DHCP enabled for this machine 'no'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Host IP0 addr for this node '192.168.1.106'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Host IP0 mask for this node '255.255.255.0'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Gateway for this node '192.168.1.1'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Primary DNS server IP address '192.168.1.1'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Tag LocalHostDnsSecondary not found.|<LVL::Warn>
04/30/2019 22:48:08 InstallWizard|Domain name for this machine 'techrich.hk'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|First node in the cluster 'yes'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|node does NOT have external NTP server(s)|<LVL::Debug>
04/30/2019 22:48:08 InstallWizard|populateFromPlatformXml: IS first node.|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Timezone for this node 'America/Los_Angeles'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Administrator name for this node 'admin'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Administrator UID Value for this node 'admin'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Old decrypt method|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Certification Signing Request Organization 'aasdfas'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Certification Signing Request Unit 'sdafasd'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Certification Signing Request Location 'fsdf'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Certification Signing Request State 'sfas'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Certification Signing Request Country 'US'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Tag SMTPHostName not found.|<LVL::Warn>
04/30/2019 22:48:08 InstallWizard|A Special Install Mode for Testers which will ignore networking errors in the install process 'yes'|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Network Validation Bypassed|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|ccmEncryptionConfigOptional: dynamicKeyCCMEncryption='enable'.|<LVL::Debug>
04/30/2019 22:48:08 InstallWizard|Generating Dynamic Encryption Key with config of CCM Encryption enable|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Dynamic key file is not present|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|File read successful|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|encryptData : enter|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|encryptData (Success)|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|Dynamic Encryption Key generation Successful for fresh install|<LVL::Info>
04/30/2019 22:48:08 InstallWizard|fipsAESAlgoConfig: fipsAES='optional'.|<LVL::Debug>
04/30/2019 22:48:09 InstallWizard|Updating /usr/local/platform/conf/platformConfig.xml|<LVL::Info>
04/30/2019 22:48:09 InstallWizard|clusterConfigEnabled: cluster='optional'.|<LVL::Debug>
04/30/2019 22:48:09 InstallWizard|'/usr/local/platform/bin/clm/clm_ctl set install_configuration_complete yes'  executed successfully|<LVL::Info>
04/30/2019 22:48:09 InstallWizard|6f e2 98 18|<LVL::Debug>
04/30/2019 22:48:09 InstallWizard|written 6502 bytes to /usr/local/platform/conf/platformConfig.xml|<LVL::Info>
04/30/2019 22:48:09 InstallWizard|ccmEncryptionConfigOptional: dynamicKeyCCMEncryption='enable'.|<LVL::Debug>
04/30/2019 22:48:09 InstallWizard|encryptData : enter|<LVL::Info>
04/30/2019 22:48:09 InstallWizard|encryptData (Success)|<LVL::Info>
04/30/2019 22:48:09 InstallWizard|Updating /usr/local/platform/conf/platformConfig.xml|<LVL::Info>
04/30/2019 22:48:09 InstallWizard|openPlatformXml: Parse existing xml document /usr/local/platform/conf/platformConfig.xml.|<LVL::Info>
04/30/2019 22:48:09 InstallWizard|clusterConfigEnabled: cluster='optional'.|<LVL::Debug>
04/30/2019 22:48:09 InstallWizard|'/usr/local/platform/bin/clm/clm_ctl set install_configuration_complete yes'  executed successfully|<LVL::Info>
04/30/2019 22:48:09 InstallWizard|written 6522 bytes to /usr/local/platform/conf/platformConfig.xml|<LVL::Info>
04/30/2019 22:48:09 InstallWizard|re encrypted file stored in platformConfig file|<LVL::Info>
04/30/2019 22:48:09 appmanager.sh|/usr/local/bin/base_scripts/InstallWizard returned 0|<LVL::Info>
04/30/2019 22:48:09 component_install|Initializing xproduct.sh API|<LVL::Debug>
04/30/2019 22:48:09 component_install|Initializing xcomponent.sh API|<LVL::Debug>
04/30/2019 22:48:09 component_install|Initializing xplatformconfig.sh API|<LVL::Debug>
04/30/2019 22:48:09 component_install|PATH=/usr/local/cm/db/informix:/usr/local/cm/db/informix/bin:/usr/local/cm/bin:/usr/local//thirdparty/java/j2sdk/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/sbin:/home/sftpuser:/root/.security:/root/bin:/usr/local/sbin:/sbin:/usr/sbin:/bin:/usr/bin:/sbin:/home/sftpuser:/root/.security:/sbin:/home/sftpuser:/root/.security|<LVL::Info>
04/30/2019 22:48:09 component_install|LD_LIBRARY_PATH=/usr/local/lib:/usr/local/thirdparty/java/j2sdk/jre/lib/i386:/usr/local/thirdparty/java/j2sdk/jre/lib/i386/server:/usr/lib/pgsql:/usr/lib:/usr/local/cm/lib:/usr/local/platform/lib:/usr/local/lib:/usr/local/thirdparty/java/j2sdk/jre/lib/i386:/usr/local/thirdparty/java/j2sdk/jre/lib/i386/server:/usr/lib/pgsql:/usr/lib:/usr/local/cm/lib:/usr/local/lib:/usr/local/thirdparty/java/j2sdk/jre/lib/i386:/usr/local/thirdparty/java/j2sdk/jre/lib/i386/server:/usr/lib/pgsql:/usr/lib:/usr/local/cm/lib::/usr/local/platform/lib:/usr/local/platform/lib|<LVL::Info>
04/30/2019 22:48:09 component_install|Parse argument type=infrastructure_post|<LVL::Debug>
04/30/2019 22:48:09 component_install|Parse argument mode=install|<LVL::Debug>
04/30/2019 22:48:09 component_install|Install infrastructure_post component, mode install|<LVL::Info>
04/30/2019 22:48:09 component_install|Initialize product data, mode install|<LVL::Info>
04/30/2019 22:48:09 component_install|Initialize "to" side product version|<LVL::Info>
04/30/2019 22:48:09 component_install|Access "to" side API|<LVL::Debug>
04/30/2019 22:48:10 component_install|Got version 12.0.1.10000-10|<LVL::Debug>
04/30/2019 22:48:10 component_install|Initialize "to" side product version complete|<LVL::Info>
04/30/2019 22:48:10 component_install|Initialize product data complete|<LVL::Info>
04/30/2019 22:48:10 component_install|Initialize component data, mode install|<LVL::Info>
04/30/2019 22:48:10 component_install|Initialize ucplatform_post "to" side version|<LVL::Info>
04/30/2019 22:48:10 component_install|Access "to" side API|<LVL::Debug>
04/30/2019 22:48:10 component_install|Got version 12.0.1.10000-10|<LVL::Debug>
04/30/2019 22:48:10 component_install|Initialize ucplatform_post "to" side version complete|<LVL::Info>
04/30/2019 22:48:10 component_install|Initialize global data complete|<LVL::Info>
04/30/2019 22:48:10 component_install|Build the command list for ucplatform_post|<LVL::Info>
04/30/2019 22:48:10 component_install|Initialize command list|<LVL::Debug>
04/30/2019 22:48:10 component_install|Build ucplatform_post install phase commands|<LVL::Debug>
04/30/2019 22:48:10 component_install|Processing ucplatform_post install element|<LVL::Debug>
04/30/2019 22:48:10 component_install|Processing ucplatform_post phase element|<LVL::Debug>
04/30/2019 22:48:10 component_install|Processing ucplatform_post import element|<LVL::Debug>
04/30/2019 22:48:10 component_install|Building the command list for ucplatform_post is complete|<LVL::Info>
04/30/2019 22:48:10 component_install|Command execution for ucplatform_post component RTMTStart|<LVL::Notice>
04/30/2019 22:48:10 component_install|Execute commands in the command list for ucplatform_post component|<LVL::Info>
04/30/2019 22:48:11 component_install|No commands to execute for ucplatform_post component|<LVL::Info>
04/30/2019 22:48:11 component_install|Command execution for ucplatform_post component is complete|<LVL::Info>
04/30/2019 22:48:11 component_install|Command execution for ucplatform_post component RTMTFinish|<LVL::Notice>
04/30/2019 22:48:11 component_install|Initialize component data, mode install|<LVL::Info>
04/30/2019 22:48:11 component_install|Initialize thirdparty "to" side version|<LVL::Info>
04/30/2019 22:48:11 component_install|Access "to" side API|<LVL::Debug>
04/30/2019 22:48:11 component_install|Got version 12.0.1.10000-10|<LVL::Debug>
04/30/2019 22:48:11 component_install|Initialize thirdparty "to" side version complete|<LVL::Info>
04/30/2019 22:48:11 component_install|Initialize global data complete|<LVL::Info>
04/30/2019 22:48:11 component_install|Build the command list for thirdparty|<LVL::Info>
04/30/2019 22:48:11 component_install|Initialize command list|<LVL::Debug>
04/30/2019 22:48:11 component_install|Build thirdparty install phase commands|<LVL::Debug>
04/30/2019 22:48:11 component_install|Processing thirdparty install element|<LVL::Debug>
04/30/2019 22:48:11 component_install|Processing thirdparty package element|<LVL::Debug>
04/30/2019 22:48:11 component_install|Checking if RPM /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-lib-1.0.0.0-1.i386.rpm exists|<LVL::Debug>
04/30/2019 22:48:11 component_install|Add "rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-lib-1.0.0.0-1.i386.rpm" to command list|<LVL::Debug>
04/30/2019 22:48:11 component_install|Processing thirdparty package element|<LVL::Debug>
04/30/2019 22:48:11 component_install|Checking if RPM /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-jar-lib-1.0.0.0-1.i386.rpm exists|<LVL::Debug>
04/30/2019 22:48:11 component_install|Add "rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-jar-lib-1.0.0.0-1.i386.rpm" to command list|<LVL::Debug>
04/30/2019 22:48:11 component_install|Building the command list for thirdparty is complete|<LVL::Info>
04/30/2019 22:48:11 component_install|Command execution for thirdparty component RTMTStart|<LVL::Notice>
04/30/2019 22:48:11 component_install|Execute commands in the command list for thirdparty component|<LVL::Info>
04/30/2019 22:48:12 IPM|Normalizer search path is /opt/cisco/install/bin|<LVL::Debug>
04/30/2019 22:48:12 IPM|Checking normalizer /opt/cisco/install/bin/pmNormalizeGeneric|<LVL::Debug>
04/30/2019 22:48:12 IPM|Returning normalizer /opt/cisco/install/bin/pmNormalizeGeneric|<LVL::Debug>
04/30/2019 22:48:13 IPM|Open progress meter "Component Install"|<LVL::Info>
04/30/2019 22:48:13 IPM|  begin-of-session "Installing thirdparty component", 2 items|<LVL::Info>
04/30/2019 22:48:13 IPM|    begin-analysis: [2 commands]|<LVL::Info>
04/30/2019 22:48:13 IPM|      command #1: 3973452 bytes, 0 seconds: rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-lib-1.0.0.0-1.i386.rpm|<LVL::Info>
04/30/2019 22:48:13 IPM|      command #2: 6237296 bytes, 0 seconds: rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-jar-lib-1.0.0.0-1.i386.rpm|<LVL::Info>
04/30/2019 22:48:13 IPM|    end-analysis: 2 total objects, 10210748 total bytes, 0 total seconds, 0.051 secs.|<LVL::Info>
04/30/2019 22:48:13 IPM|    begin-work: [2 items]|<LVL::Info>
04/30/2019 22:48:13 IPM|Execute rpm command "rpm --percent -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-lib-1.0.0.0-1.i386.rpm "|<LVL::Debug>
04/30/2019 22:48:26 IPM|      item  1: rpm-install    3973452 bytes (13.020 secs.)|<LVL::Info>
04/30/2019 22:48:26 IPM|Execute rpm command "rpm --percent -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/thirdparty/cm-jar-lib-1.0.0.0-1.i386.rpm "|<LVL::Debug>
04/30/2019 22:48:35 IPM|      item  2: rpm-install    6237296 bytes (9.336 secs.)|<LVL::Info>
04/30/2019 22:48:35 IPM|    end-work:          2 items  22.367 secs. total|<LVL::Info>
04/30/2019 22:48:37 IPM|  end-of-session "Installing thirdparty component": 24.377 secs.|<LVL::Info>
04/30/2019 22:48:37 IPM|Close progress meter "Component Install"|<LVL::Info>
04/30/2019 22:48:37 component_install|Command execution for thirdparty component is complete|<LVL::Info>
04/30/2019 22:48:37 component_install|Command execution for thirdparty component RTMTFinish|<LVL::Notice>
04/30/2019 22:48:37 component_install|Initialize component data, mode install|<LVL::Info>
04/30/2019 22:48:37 component_install|Initialize serviceability_core "to" side version|<LVL::Info>
04/30/2019 22:48:37 component_install|Access "to" side API|<LVL::Debug>
04/30/2019 22:48:37 component_install|Got version 12.0.1.10000-10|<LVL::Debug>
04/30/2019 22:48:37 component_install|Initialize serviceability_core "to" side version complete|<LVL::Info>
04/30/2019 22:48:37 component_install|Initialize global data complete|<LVL::Info>
04/30/2019 22:48:37 component_install|Build the command list for serviceability_core|<LVL::Info>
04/30/2019 22:48:37 component_install|Initialize command list|<LVL::Debug>
04/30/2019 22:48:37 component_install|Build serviceability_core install phase commands|<LVL::Debug>
04/30/2019 22:48:37 component_install|Processing serviceability_core install element|<LVL::Debug>
04/30/2019 22:48:38 component_install|Processing serviceability_core package element|<LVL::Debug>
04/30/2019 22:48:38 component_install|Checking if RPM /common/rpm-archive/12.0.1.10000-10/RPMS/serviceability_core/cm-pi-0.0.0.1-0.i386.rpm exists|<LVL::Debug>
04/30/2019 22:48:38 component_install|Add "rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/serviceability_core/cm-pi-0.0.0.1-0.i386.rpm" to command list|<LVL::Debug>
04/30/2019 22:48:38 component_install|Building the command list for serviceability_core is complete|<LVL::Info>
04/30/2019 22:48:38 component_install|Command execution for serviceability_core component RTMTStart|<LVL::Notice>
04/30/2019 22:48:38 component_install|Execute commands in the command list for serviceability_core component|<LVL::Info>
04/30/2019 22:48:38 IPM|Normalizer search path is /opt/cisco/install/bin|<LVL::Debug>
04/30/2019 22:48:38 IPM|Checking normalizer /opt/cisco/install/bin/pmNormalizeGeneric|<LVL::Debug>
04/30/2019 22:48:38 IPM|Returning normalizer /opt/cisco/install/bin/pmNormalizeGeneric|<LVL::Debug>
04/30/2019 22:48:39 IPM|Open progress meter "Component Install"|<LVL::Info>
04/30/2019 22:48:39 IPM|  begin-of-session "Installing core serviceability component", 1 items|<LVL::Info>
04/30/2019 22:48:39 IPM|    begin-analysis: [1 commands]|<LVL::Info>
04/30/2019 22:48:39 IPM|      command #1: 4318680 bytes, 0 seconds: rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/serviceability_core/cm-pi-0.0.0.1-0.i386.rpm|<LVL::Info>
04/30/2019 22:48:39 IPM|    end-analysis: 1 total objects, 4318680 total bytes, 0 total seconds, 0.045 secs.|<LVL::Info>
04/30/2019 22:48:39 IPM|    begin-work: [1 items]|<LVL::Info>
04/30/2019 22:48:39 IPM|Execute rpm command "rpm --percent -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/serviceability_core/cm-pi-0.0.0.1-0.i386.rpm "|<LVL::Debug>
04/30/2019 22:48:48 IPM|      item  1: rpm-install    4318680 bytes (9.029 secs.)|<LVL::Info>
04/30/2019 22:48:48 IPM|    end-work:          1 items  9.156 secs. total|<LVL::Info>
04/30/2019 22:48:50 IPM|  end-of-session "Installing core serviceability component": 11.167 secs.|<LVL::Info>
04/30/2019 22:48:50 IPM|Close progress meter "Component Install"|<LVL::Info>
04/30/2019 22:48:50 component_install|Command execution for serviceability_core component is complete|<LVL::Info>
04/30/2019 22:48:50 component_install|Command execution for serviceability_core component RTMTFinish|<LVL::Notice>
04/30/2019 22:48:50 component_install|Initialize component data, mode install|<LVL::Info>
04/30/2019 22:48:50 component_install|Initialize database "to" side version|<LVL::Info>
04/30/2019 22:48:50 component_install|Access "to" side API|<LVL::Debug>
04/30/2019 22:48:51 component_install|Got version 12.0.1.10000-10|<LVL::Debug>
04/30/2019 22:48:51 component_install|Initialize database "to" side version complete|<LVL::Info>
04/30/2019 22:48:51 component_install|Initialize global data complete|<LVL::Info>
04/30/2019 22:48:51 component_install|Build the command list for database|<LVL::Info>
04/30/2019 22:48:51 component_install|Initialize command list|<LVL::Debug>
04/30/2019 22:48:51 component_install|Build database install phase commands|<LVL::Debug>
04/30/2019 22:48:51 component_install|Processing database install element|<LVL::Debug>
04/30/2019 22:48:51 component_install|Processing database package element|<LVL::Debug>
04/30/2019 22:48:51 component_install|Checking if RPM /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbms-1.0.0.0-1.i386.rpm exists|<LVL::Debug>
04/30/2019 22:48:51 component_install|Add "rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbms-1.0.0.0-1.i386.rpm" to command list|<LVL::Debug>
04/30/2019 22:48:51 component_install|Processing database package element|<LVL::Debug>
04/30/2019 22:48:51 component_install|Checking if RPM /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbl-1.0.0.0-1.i386.rpm exists|<LVL::Debug>
04/30/2019 22:48:51 component_install|Add "rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbl-1.0.0.0-1.i386.rpm" to command list|<LVL::Debug>
04/30/2019 22:48:51 component_install|Processing database phase element|<LVL::Debug>
04/30/2019 22:48:51 component_install|Processing database import element|<LVL::Debug>
04/30/2019 22:48:51 component_install|Processing database phase element|<LVL::Debug>
04/30/2019 22:48:51 component_install|Processing database migration element|<LVL::Debug>
04/30/2019 22:48:51 component_install|Processing database phase element|<LVL::Debug>
04/30/2019 22:48:51 component_install|Processing database postinstall element|<LVL::Debug>
04/30/2019 22:48:51 component_install|Processing database script element|<LVL::Debug>
04/30/2019 22:48:51 component_install|Add "cm-dbms-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt" to command list|<LVL::Debug>
04/30/2019 22:48:52 component_install|Processing database script element|<LVL::Debug>
04/30/2019 22:48:52 component_install|Add "cm-dbl-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt" to command list|<LVL::Debug>
04/30/2019 22:48:52 component_install|Building the command list for database is complete|<LVL::Info>
04/30/2019 22:48:52 component_install|Command execution for database component RTMTStart|<LVL::Notice>
04/30/2019 22:48:52 component_install|Execute commands in the command list for database component|<LVL::Info>
04/30/2019 22:48:52 IPM|Normalizer search path is /opt/cisco/install/bin|<LVL::Debug>
04/30/2019 22:48:52 IPM|Checking normalizer /opt/cisco/install/bin/pmNormalizeGeneric|<LVL::Debug>
04/30/2019 22:48:52 IPM|Returning normalizer /opt/cisco/install/bin/pmNormalizeGeneric|<LVL::Debug>
04/30/2019 22:48:53 IPM|Open progress meter "Component Install"|<LVL::Info>
04/30/2019 22:48:53 IPM|  begin-of-session "Installing database component", 4 items|<LVL::Info>
04/30/2019 22:48:53 IPM|    begin-analysis: [4 commands]|<LVL::Info>
04/30/2019 22:48:53 IPM|      command #1: 423348056 bytes, 0 seconds: rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbms-1.0.0.0-1.i386.rpm|<LVL::Info>
04/30/2019 22:48:53 IPM|      command #2: 12611328 bytes, 0 seconds: rpm  -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbl-1.0.0.0-1.i386.rpm|<LVL::Info>
04/30/2019 22:48:53 IPM|      command #3: 0 bytes, 4800 seconds: sh  -path /opt/cisco/install/database/scripts:/usr/local/cm/script -t 4800 -c cm-dbms-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt|<LVL::Info>
04/30/2019 22:48:53 IPM|      command #4: 0 bytes, 21600 seconds: sh  -path /opt/cisco/install/database/scripts:/usr/local/cm/script -t 21600 -c cm-dbl-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt|<LVL::Info>
04/30/2019 22:48:53 IPM|    end-analysis: 4 total objects, 435959384 total bytes, 26400 total seconds, 0.045 secs.|<LVL::Info>
04/30/2019 22:48:53 IPM|    begin-work: [4 items]|<LVL::Info>
04/30/2019 22:48:53 IPM|Execute rpm command "rpm --percent -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbms-1.0.0.0-1.i386.rpm "|<LVL::Debug>
04/30/2019 22:50:34 IPM|      item  1: rpm-install  423348056 bytes (101.099 secs.)|<LVL::Info>
04/30/2019 22:50:34 IPM|Execute rpm command "rpm --percent -iv --replacefiles /common/rpm-archive/12.0.1.10000-10/RPMS/database/cm-dbl-1.0.0.0-1.i386.rpm "|<LVL::Debug>
04/30/2019 22:51:16 IPM|      item  2: rpm-install   12611328 bytes (42.076 secs.)|<LVL::Info>
04/30/2019 22:51:16 IPM|Execute shell command "/usr/local/cm/script/cm-dbms-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt "|<LVL::Debug>
05/01/2019 00:11:17 IPM|Command exceeded maximum time (4800). Extending time by 24000 seconds.|<LVL::Warn>
05/01/2019 00:20:03 IPM|      item  3: shell-script          0 bytes (5327.358 secs.)|<LVL::Info>
05/01/2019 00:20:03 IPM|Execute shell command "/usr/local/cm/script/cm-dbl-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt "|<LVL::Debug>
05/01/2019 01:33:50 IPM|Internal Error, File:ipm.c:2011, Function: ipmReadNormalizedInputLine(), "/usr/local/cm/script/cm-dbl-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt " failed (1)|<LVL::Critical>
05/01/2019 01:33:53 IPM|  end-of-session "Installing database component": 9899.732 secs.|<LVL::Info>
05/01/2019 01:34:06 IPM|Close progress meter "Component Install"|<LVL::Info>
05/01/2019 01:34:06 component_install|Writing database into /common/log/install/component_failed.xml file.|<LVL::Info>
05/01/2019 01:34:07 component_install|/common/log/install/component_failed.xml created : 0|<LVL::Info>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:19:46 2019 cm-dbms-install  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.ParamObject.validate  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.ParamObject.validate  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.doActionInstall  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.doActionInstall  DEBUG:  Inside doActionInstall...|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.doInstallPost_installDB  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.doInstallPost_installDB  DEBUG:  Inside doInstallPost...|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.doCreateLogDirectory  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.doCreateLogDirectory  DEBUG:  Verifying SDI directory [/var/log/active/cm/trace/dbl/sdi]|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.doCreateLogDirectory  DEBUG:  chown database.ccmbase /var/log/active/cm/trace/dbl/sdi|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.doCreateLogDirectory  DEBUG:  chmod 775 /var/log/active/cm/trace/dbl/sdi|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.doCreateLogDirectory  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.setupPreferences  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.setupPreferences  DEBUG:  Inside setupPreferences...|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.setupPreferences  DEBUG:  current_db [ccm12_0_1_10000_10]|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.setupPreferences  DEBUG:  chown database.ccmbase /usr/local/cm/conf/dbl/prefs.xml ; chmod 644 /usr/local/cm/conf/dbl/prefs.xml|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.setupPreferences  DEBUG:  Updating prefs [/usr/local/cm/conf/dbl/prefs.xml]|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.shortHostName  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.shortHostName  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.shortHostName  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.shortHostName  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.shortHostName  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.shortHostName  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.shortHostName  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.shortHostName  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.setupPreferences  DEBUG:  chown database.ccmbase /usr/local/cm/conf/dbl/sdi/prefs.xml ; chmod 664 /usr/local/cm/conf/dbl/sdi/prefs.xml|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.setupPreferences  DEBUG:  Updating prefs [/usr/local/cm/conf/dbl/sdi/prefs.xml]|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.setupPreferences  DEBUG:  chown database.ccmbase /usr/local/cm/conf/dbnotify/sdi/prefs.xml ; chmod 664 /usr/local/cm/conf/dbnotify/sdi/prefs.xml|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.setupPreferences  DEBUG:  Updating prefs [/usr/local/cm/conf/dbnotify/sdi/prefs.xml]|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.setupPreferences  DEBUG:  python "/usr/local/cm/bin/dbl" setprefs /common/log/install/capture.txt|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 dblsetprefs-plugin.run  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 dblsetprefs-plugin.run  DEBUG:  Create Preferences entries for various database components|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 dblsetprefs-plugin.run  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.setupPreferences  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.getPublisherFromInstallPrefs  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.getPublisherFromInstallPrefs  DEBUG:  Inside getPublisherFromInstallPrefs...|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.getPublisherFromInstallPrefs  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.doInstallPost_installDB  DEBUG:  (odbc setup moved to dbl init)|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.fixSQLLibPaths  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.fixSQLLibPaths  DEBUG:  Inside fixSQLLibPaths....|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.fixSQLLibPaths  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.fixSQLLibPaths  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:03 2019 cm-dbl-install.fixSQLLibPaths  DEBUG:  Inside fixSQLLibPaths....|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:04 2019 cm-dbl-install.fixSQLLibPaths  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:04 2019 cm-dbl-install.doInstallPost_installDB  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:04 2019 cm-dbl-install.doInstallPost_installDB  DEBUG:  Inside doInstallPost_installDB ...|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:04 2019 cm-dbl-install.installdb  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:04 2019 cm-dbl-install.installdb  DEBUG:  Inside installdb ...|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:04 2019 cm-dbl-install.installdb  DEBUG:  python "/usr/local/cm/bin/dbl" start --safe --nopreflight --log=/common/log/install/capture.txt|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:04 2019 dblstart-plugin.run  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:04 2019 dblstart-plugin.run  DEBUG:  Start DBMS|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:20 2019 dblstart-plugin.run  DEBUG:  do preflight|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:20 2019 dblstart-plugin.run  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:20 2019 cm-dbl-install.installdb  DEBUG:  rm -f /tmp/*.txt /tmp/*.log /tmp/*.err /var/log/active/cm/trace/dbl/sdi/psqlx /tmp/*.bin /tmp/af* /tmp/shmem*|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:20 2019 cm-dbl-install.installdb  DEBUG:  Disk size present in dbl/prefs is 128|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:20 2019 cm-dbl-install.getPublisherFromPrefs  DEBUG:  -->|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:20 2019 cm-dbl-install.getPublisherFromPrefs  DEBUG:  Inside getPublisherFromPrefs...|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:20 2019 cm-dbl-install.getPublisherFromPrefs  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 00:20:20 2019 cm-dbl-install.installdb  DEBUG:  su -l informix -s /bin/sh -c 'source /usr/local/cm/db/dblenv.bash /usr/local/cm ; source /usr/local/cm/db/informix/local/ids.env ; "/usr/local/cm/bin/installdb" -f IN "/usr/local/cm" "/usr/local/cm" 12.0.1.10000-10 12.0.1.10000-10 installdb_in.log'|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 01:33:49 2019 cm-dbl-install.installdb  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 01:33:49 2019 cm-dbl-install.doInstallPost_installDB  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 01:33:49 2019 cm-dbl-install.doInstallPost_installDB  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 01:33:49 2019 cm-dbl-install.doActionInstall  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 01:33:49 2019 cm-dbl-install  DEBUG:  cm-dbl-install [1]|<LVL::Debug>
05/01/2019 01:34:07 component_install|(CAPTURE) Wed May  1 01:33:49 2019 cm-dbl-install  DEBUG:  <--|<LVL::Debug>
05/01/2019 01:34:07 component_install|File:/opt/cisco/install/bin/component_install:821, Function: exec_progmeter(), /opt/cisco/install/bin/progmeter failed (1)|<LVL::Error>
05/01/2019 01:34:07 appmanager.sh|Internal Error, File:/usr/local/bin/base_scripts/appmanager.sh:153, Function: install(), failed to install infrastructure_post components|<LVL::Critical>
05/01/2019 01:34:07 post_install|File:/opt/cisco/install/bin/post_install:1030, Function: install_applications(), /usr/local/bin/base_scripts/appmanager.sh -install failed (1)|<LVL::Error>
05/01/2019 01:34:07 post_install|Exiting with result 1|<LVL::Info>
05/01/2019 01:34:07 post_install|INSTALL_TYPE="Basic Install"|<LVL::Debug>
05/01/2019 01:34:07 post_install|File:/opt/cisco/install/bin/post_install:721, Function: check_for_critical_error(), check_for_critical_error, found /common/log/install/critical.log, exiting|<LVL::Error>
05/01/2019 01:34:07 post_install|(CAPTURE) Mail notification cancelled - smtp server address for email not found! [/usr/local/platform/conf/platformConfig.xml]|<LVL::Debug>
05/01/2019 01:34:07 display_screen|Arguments: "Critical Error" "The installation has encountered a unrecoverable internal error. For further assistance report the following information to your support provider.

"/usr/local/cm/script/cm-dbl-install install PostInstall 12.0.1.10000-10 12.0.1.10000-10 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt " failed (1)

The system will now halt.


Continuing will allow you to dump diagnostic information before halting." "Continue"|<LVL::Debug>
05/01/2019 01:34:07 display_screen|Button label size information 66, 1, 66|<LVL::Debug>
05/01/2019 01:34:07 platform-events.sh|Received request for platform-event (platform-install-paused-for-input TYPE=INSTALL_PAUSED)|<LVL::Info>
05/01/2019 01:34:07 platform-events.sh|emitting platform-event (platform-install-paused-for-input TYPE=INSTALL_PAUSED)|<LVL::Info>
05/01/2019 01:34:07 platform-events.sh|emitted platform-event (platform-install-paused-for-input TYPE=INSTALL_PAUSED)|<LVL::Info>
05/01/2019 01:34:07 display_screen|installWizard service activated|<LVL::Info>
05/01/2019 08:32:50 display_screen|newtFormRun exited. reason=1|<LVL::Info>
05/01/2019 08:32:50 display_screen|installWizard service deactivated|<LVL::Info>
05/01/2019 08:32:50 post_install|Dumping diagnostic information to USB|<LVL::Info>
05/01/2019 08:32:50 display_screen|Arguments: "INSTALLATION FAILED" "Would you like to dump diagnostic information?" "Yes" "No"|<LVL::Debug>
05/01/2019 08:32:50 display_screen|Button label size information 66, 2, 33|<LVL::Debug>
05/01/2019 08:32:50 platform-events.sh|Received request for platform-event (platform-install-paused-for-input TYPE=INSTALL_PAUSED)|<LVL::Info>
05/01/2019 08:32:50 platform-events.sh|emitting platform-event (platform-install-paused-for-input TYPE=INSTALL_PAUSED)|<LVL::Info>
05/01/2019 08:32:50 platform-events.sh|emitted platform-event (platform-install-paused-for-input TYPE=INSTALL_PAUSED)|<LVL::Info>
05/01/2019 08:32:50 display_screen|installWizard service activated|<LVL::Info>
05/01/2019 08:33:01 display_screen|newtFormRun exited. reason=1|<LVL::Info>
05/01/2019 08:33:01 display_screen|installWizard service deactivated|<LVL::Info>
05/01/2019 08:33:01 post_install|Installer selected not to dump diagnostics|<LVL::Debug>
05/01/2019 08:33:01 post_install|========================= Installation failed. =========================|<LVL::Info>
05/01/2019 08:33:01 post_install|Copy /usr/local/bin/base_scripts/INSTALLATION_FAILED to /etc/rc.d/init.d/|<LVL::Info>
05/01/2019 08:33:01 post_install|Calling "cp /usr/local/bin/base_scripts/INSTALLATION_FAILED /etc/rc.d/init.d"|<LVL::Debug>


2,6,A or E is what the second digit of your MAC address must be otherwise a lot of OS's will not work.  They will say the NIC is down/not connected even though it is.

This is because if the second digit is not set properly it will not view as a valid MAC or device uplink.  This is especially an issue with VMs whether in QEMU etc.. if you are making your own MAC.

MAC address is invalid

c4:d1:aa:e5:10:05

To fix it just change the c4 to c2, c6, ca or ce

MAC address is valid / correct

42:b9:4d:81:59:3c

46:b9:4d:81:59:3c

4a:b9:4d:81:59:3c

4e:b9:4d:81:59:3c

There are multiple layers but most are enabled by default such as the setting in the Phone Device Settings.

However the one not enabled by default is the one in "Enterprise Phone Configuration".

Enable "Cisco Camera" and then reboot your phones to enable it.

Oops did you get this error trying to install an oldschool driver and think it is hopeless in a new version of Windows?

First of all it is almost never a program compatibility issue:

Solve it by going to the control panel and booting into the F8 mode startup options:

Click "Troubleshooting Common Computer Problems"

Click on "Recovery" on the Left side menu and then click on "Restart now"

After your PC restarts click on Troubleshoot

Then click on "Startup Settings"

 Click on "Startup Settings" below and then the "Restart Button"

Choose the "Disable Driver Signature Enforcement" option, this will allow us to install our oldschool drivers properly.

Now install your driver whether from the setup.exe or if you manually install from the Control Panel (in this case we are installing AC97 sound drivers)

Now instead of faililng like last time you will be prompted to install the driver or not to install it. Obviously you will click "Install this driver software anyway" so the install completes!

After that you're all good.

DN = Directory Number:

It is basically the extension of the phone

In the example below, 55 is a DN assigned to the phone. 

It is much more useful to have meaningful and detailed logging from tftp to see what is or isn't happening especially for VOIP and other embedded device appications:

Edit the file:

vi /etc/xinetd.d/tftp

Change the server line like this:

        server_args             = -s /var/lib/tftpboot --verbose
 

Restart xinetd:

service xinetd restart

This will find all tap devices and try deleting all of them.  Of course don't run this if there is a chance an unused tap device is necessary and would not be created by the script ro application using it.

for tap in `ifconfig -a|grep tap[0-255]|awk '{print $1}'`; do


tunctl -d $tap


done

Pass QEMU this flag:

-soundhw ac97

Or you could use (for a Ensoniq soundcard):

-soundhw es1370

However on some machines I get this error:

pulseaudio: pa_simple_new for capture failed
pulseaudio: Reason: Connection terminated
pulseaudio: pa_simple_new for capture failed
pulseaudio: Reason: Connection terminated
audio: Failed to create voice `ac97.pi'
pulseaudio: pa_simple_new for playback failed
pulseaudio: Reason: Connection terminated
pulseaudio: pa_simple_new for playback failed
pulseaudio: Reason: Connection terminated
audio: Failed to create voice `ac97.po'
pulseaudio: pa_simple_new for capture failed
pulseaudio: Reason: Connection terminated
pulseaudio: pa_simple_new for capture failed
pulseaudio: Reason: Connection terminated
audio: Failed to create voice `ac97.mc'


You may have noticed if you are running QEMU/KVM manually that in Windows the the position of the physical mouse does not match where the mouse is positioned within Windows.

There is an easy command to pass to qemu-kvm or qemu-system (whatever you call your binary):

-usbdevice tablet

The above flag will fix your mouse pointing problems whether you are running Windows 95, 98, NT, XP 2000, 2003, Vista, 7, 8 10 or Server 2000, 2003, 2008, 2012, 2016 or 2019 etc... 

Are you tired of coming back to your computer only to find your SSH connections have been broken?  Even worse are the ones that hang where it appears to be connected but it is really not.

The one option you have is an SSH client side modification to send KeepAlive packets, sometimes this can also keep up your WiFi connection and stop it from disconnecting you as well.

To make the keep alive changes for your just yourself (not system wide)

vi ~/.ssh/config

Host *
    ServerAliveInterval 60
    ServerAliveCountMax 2
 

ServerAliveInternal 60 = keep alive time of 60 seconds (change according to your needs)

ServerAliveCountMax 2 = how many packets in that time that can fail before we disconnect or declare ourselves a dead connection.

To make the changes system wide (by default for all users) then edit the /etc/ssh/ssh_config file

vi /etc/ssh/ssh_config

Host *
    ServerAliveInterval 60
    ServerAliveCountMax 2

This is the closest way to disabling it without using the "libata.force=noncq" kernel boot option is to set the queue to a depth of 1 which doesn't actually disable it.

Change the sdc below to match the device you want to disable NCQ for.

[root@officebox ~]# echo "1" > /sys/block/sdc/device/queue_depth

Errors that indicate you are having a performance issue are these in messages or dmesg relating to NCQ and SATA bus timeout and reset are killing your IO performance!

Apr 12 12:12:50 officebox kernel: ata8: EH in SWNCQ mode,QC:qc_active 0x400FFFFF sactive 0x400FFFFF
Apr 12 12:12:50 officebox kernel: ata8: SWNCQ:qc_active 0x40000007 defer_bits 0xFFFF8 last_issue_tag 0x2
Apr 12 12:12:50 officebox kernel:  dhfis 0x40000003 dmafis 0x40000008 sdbfis 0x0
Apr 12 12:12:50 officebox kernel: ata8: ATA_REG 0x51 ERR_REG 0x84
Apr 12 12:12:50 officebox kernel: ata8: tag : dhfis dmafis sdbfis sacitve
Apr 12 12:12:50 officebox kernel: ata8: tag 0x0: 1 0 0 1 
Apr 12 12:12:50 officebox kernel: ata8: tag 0x1: 1 0 0 1 
Apr 12 12:12:50 officebox kernel: ata8: tag 0x2: 0 0 0 1 
Apr 12 12:12:50 officebox kernel: ata8: tag 0x1e: 1 1 0 1 
Apr 12 12:12:50 officebox kernel: ata8.00: exception Emask 0x1 SAct 0x400fffff SErr 0x0 action 0x6 frozen
Apr 12 12:12:50 officebox kernel: ata8.00: Ata error. fis:0x21
Apr 12 12:12:50 officebox kernel: ata8.00: failed command: WRITE FPDMA QUEUED
Apr 12 12:12:50 officebox kernel: ata8.00: cmd 61/08:00:bf:83:8b/00:00:02:00:00/40 tag 0 ncq 4096 out
Apr 12 12:12:50 officebox kernel:         res 51/84:10:d7:83:8b/84:00:02:00:00/40 Emask 0x10 (ATA bus error)
Apr 12 12:12:50 officebox kernel: ata8.00: status: { DRDY ERR }
Apr 12 12:12:50 officebox kernel: ata8.00: error: { ICRC ABRT }
Apr 12 12:12:50 officebox kernel: ata8.00: failed command: WRITE FPDMA QUEUED
Apr 12 12:12:50 officebox kernel: ata8.00: cmd 61/10:08:c7:83:8b/00:00:02:00:00/40 tag 1 ncq 8192 out
Apr 12 12:12:50 officebox kernel:         res 51/84:10:d7:83:8b/84:00:02:00:00/40 Emask 0x10 (ATA bus error)
Apr 12 12:12:50 officebox kernel: ata8.00: status: { DRDY ERR }
Apr 12 12:12:50 officebox kernel: ata8.00: error: { ICRC ABRT }
Apr 12 12:12:50 officebox kernel: ata8.00: failed command: WRITE FPDMA QUEUED
Apr 12 12:12:50 officebox kernel: ata8.00: cmd 61/18:10:d7:83:8b/00:00:02:00:00/40 tag 2 ncq 12288 out
Apr 12 12:12:50 officebox kernel:         res 51/84:10:d7:83:8b/84:00:02:00:00/40 Emask 0x10 (ATA bus error)
Apr 12 12:12:50 officebox kernel: ata8.00: status: { DRDY ERR }
Apr 12 12:12:50 officebox kernel: ata8.00: error: { ICRC ABRT }
Apr 12 12:12:50 officebox kernel: ata8.00: failed command: WRITE FPDMA QUEUED
Apr 12 12:12:50 officebox kernel: ata8.00: cmd 61/10:18:ef:83:8b/00:00:02:00:00/40 tag 3 ncq 8192 out
Apr 12 12:12:50 officebox kernel:         res 51/84:10:d7:83:8b/84:00:02:00:00/40 Emask 0x10 (ATA bus error)
:
 

This is usually because the Group Policy forbids that user or group from logging in.

1. run "gpmc" (not "gpedit.msc" as that is for local computer settings when you are not using Active Directory) or go to Administrative Tools and Group Policy Management.
2. Edit the default domain policy like below

You should also check under "User Rights Assignment" that your user or group is listed under the "Allow logon locally setting"

After that check policies like "Deny logon locally".  Any user or group there won't be able to login, so make sure you remove them if they are supposed to have access.

gsmartcontrol is a free tool that let's you see the status of the SMART parameters so you can check things like temperature, reallocated sectors, bad sectors etc.. to give you a better idea of your drive health.

Download it here.

gsmartcontrol is a very useful tool in Windows to check your HDD / Hard Drive health status.

In my experience you should NEVER trust that everything is OK just because SMART says  it has passed the health check.

http://realtechtalk.com/Why_SMART_is_not_smart_at_all_and_doesnt_properly_predict_disk_errors_that_cause_a_kernel_panic_or_crash-2122-articles

If you visit a site that exploits the WebRTC vulnerability including whatismyipaddress.com it may show "Local IP Address" which would be the real IP of your machine.

The vulnerability works on Windows and Linux machines (contrary to false information on the web which claims it only affects Windows).

The above works and happens even if you are using a proxy or VPN account like ProVPNAccounts.com

It is easy to fix the WebRTC IP Address Leak Vulnerability in Firefox and similar browsers in About:Config

Go into about:config and then search for "peerconnection.enabled"

Set it so the value is "false" like the screenshot from Firefox below.

chroot which stands for change root allows you to virtually operate in another operating system even though you haven't booted it.  It is commonly used to deploy new distros, applications and to fix a broken Linux/Unix install or prep a new system image without having to physically boot the drive or disk.

So in this example let's say we have a drive that has a Linux OS installed on /dev/sdb1 and we have mounted this partition on /mnt/sdb1

The key point is to edit the "chrootdevpath" to match where your intended chroot target is actually mounted to.

After that the bash script below mounts dev, proc and sys into the chroot path so you can interact with all hardware and devices (you can even use this to install grub to sdb).

chrootdevpath=/mnt/sdb1

for mount in dev proc sys; do

mount -o bind /$mount $chrootdevpath/$mount

done
#now let's chroot into our dev path /dev/sdb1
chroot $chrootdevpath

The above is what I find to be the easiest way of chrooting  since you don't have to type any commands aside and you just have to modify one variable and the rest is done for you.

WARNING: Image format was not specified for '/mnt/space/cucm12.img' and probing guessed raw.
         Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
         Specify the 'raw' format explicitly to remove the restrictions.

#you should manually specify the format


qemu-system-x86_64 -boot once=d -smp 4 -machine pc-1.3 -vnc :1 -m 8096 -drive file=/var/lib/vz/template/iso/cucum86.img,format=raw,if=virtio -net nic,model=virtio -net tap,ifname=tap2019,script=no,downscript=no

This is a common issue that I haven't seen many answers for on the internet.  When you are using Linux as your host machine and you are connecting to another Linux machine over VNC you CANNOT use Ctrl+Alt+F1 to change virtual consoles as it sends the keys to your actual local machine.

In many versions of Linux you can cycle through virtual terminals including over VNC using this:

Alt + Left Arrow or Alt + Right Arrow

This does not seem to work if you are running Xorg already though (at least in Linux Mint). 

https://docs.microsoft.com/en-us/powershell/module/skype/?view=skype-ps

Troubleshooting Client Connectivity Issues

The first step is to enable full logging in the Skype Client itself and then check the log on the client side.  In Windows this normally means going to the Skype client "settings" and then "Enable Full Logging".

After that you can open Event Viewer, click on the Application Log and see what entries for "Lync" come up (yes it is known as Lync despite the fact the product itself is now called Skype 2015 or 2019 for business).

Further Troubleshooting on the Front End Server Pool or Edge Server Pool

The first step here is to really just check th "Lync Server" log under "Event Viewer" and the "Applications and Services Logs"

This is usually because of STP causing a delay in the negotiation.

Edit your ifcfg script eg:

/etc/sysconfig/network-scripts/ifcfg-eth0

Add a LINKDELAY of 30 seconds or whatever works for you:

LINKDELAY=30
 

After that you should have an IP during bootup.

The net-tools command brings back all of the oldschool tools that we're used to:

• /bin/netstat

• /sbin/ifconfig

• /sbin/ipmaddr

• /sbin/iptunnel

• /sbin/mii-tool

• /sbin/nameif

• /sbin/plipconfig

• /sbin/rarp

• /sbin/route

• /sbin/slattach

• /usr/sbin/arp
   

To install it just do an:

apt-get install net-tools

Of coures this applies to all of the main Debian distros whether we are talking Ubuntu, Mint etc etc..

Uh oh, so you're working on some super l33t code or other stuff that is super important and Linux Mint's MATE or Cinnamon window manager freezes.  This means maybe you can move your mouse but you can't click anything, you can't Alt + Tab to another program but everything appears to be working other than that.

The first thing you would do is Ctrl + Alt + F1 (or whatever virtual terminal you want) and get into the Linux bash prompt (the black screen where things really happen :))

Sometimes people will try killing the mint-panel or filemanager as this can sometimes be the cause of it.

So you've tried the basics, tried to restart the mint-panel or caja filemanager but it doesn't work?

You're probably close to rebooting, or booting your PC out of the window at this point.  But wait there is Ctrl + Alt + Backspace (but don't do this).  You would lose all of your current open windows

Linux MINT Mate How To Restart the GUI without losing open windows

DISPLAY=:0 marco --replace&

Linux MINT Cinnamon How To Restart the GUI without losing open windows

DISPLAY=:0 cinnamon --replace&

Ubuntu Linux How To Restart the GUI without losing open windows

DISPLAY=:0 unity --replace&

The key thing is to use the --replace because that means to replace the existing session so the windows and open programs you have are preserved.

Perhaps you've just seen this in the bash prompt:

-bash-4.1#
 

Instead of the expected user@hostname#

It is probably because you are missing .bash_profile or .bashrc in your home directory

Check for yourself:

ls -al ~/|grep -E ".bash_profile|.bashrc"
-rw-r--r--.  1 root root       176 May 20  2009 .bash_profile
-rw-r--r--.  1 root root       176 Sep 22  2004 .bashrc


If you are missing either just take these default files that pull from /etc/bashrc and will give you what you want:

.bash_profile


# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
    . ~/.bashrc
fi

# User specific environment and startup programs

PATH=$PATH:$HOME/bin

export PATH
 

.bashrc

# .bashrc

# User specific aliases and functions

alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'

# Source global definitions
if [ -f /etc/bashrc ]; then
    . /etc/bashrc
fi
 

Once you've sorted this out just login again or open a new bash shell and things should be all good again

This may sound silly but often on the same machine multiple versions of SQL may be installed due to other applications.

How do we know which one we are running and connected to?

Use the query:

select @@version

If you don't aleady have it, you'll need EPEL

Install LXC

yum -y install lxc lxc-templates
Loaded plugins: fastestmirror
Setting up Install Process
Loading mirror speeds from cached hostfile
 * base: mirror.it.ubc.ca
 * epel: mirrors.kernel.org
 * extras: mirror.it.ubc.ca
 * updates: mirror.it.ubc.ca
Resolving Dependencies
--> Running transaction check
---> Package lxc.x86_64 0:1.0.11-1.el6 will be installed
--> Processing Dependency: lua-lxc(x86-64) = 1.0.11-1.el6 for package: lxc-1.0.11-1.el6.x86_64
--> Processing Dependency: lua-alt-getopt for package: lxc-1.0.11-1.el6.x86_64
--> Processing Dependency: liblxc.so.1()(64bit) for package: lxc-1.0.11-1.el6.x86_64
--> Running transaction check
---> Package lua-alt-getopt.noarch 0:0.7.0-1.el6 will be installed
---> Package lua-lxc.x86_64 0:1.0.11-1.el6 will be installed
--> Processing Dependency: lua-filesystem for package: lua-lxc-1.0.11-1.el6.x86_64
---> Package lxc-libs.x86_64 0:1.0.11-1.el6 will be installed
--> Running transaction check
---> Package lua-filesystem.x86_64 0:1.4.2-1.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

========================================================================================================================================================================
 Package                                      Arch                                 Version                                     Repository                          Size
========================================================================================================================================================================
Installing:
 lxc                                          x86_64                               1.0.11-1.el6                                epel                               124 k
Installing for dependencies:
 lua-alt-getopt                               noarch                               0.7.0-1.el6                                 epel                               6.9 k
 lua-filesystem                               x86_64                               1.4.2-1.el6                                 epel                                24 k
 lua-lxc                                      x86_64                               1.0.11-1.el6                                epel                                16 k
 lxc-libs                                     x86_64                               1.0.11-1.el6                                epel                               257 k

Transaction Summary
========================================================================================================================================================================
Install       5 Package(s)

Total download size: 429 k
Installed size: 953 k
Downloading Packages:
(1/5): lua-alt-getopt-0.7.0-1.el6.noarch.rpm                                                                                                     | 6.9 kB     00:00    
(2/5): lua-filesystem-1.4.2-1.el6.x86_64.rpm                                                                                                     |  24 kB     00:00    
(3/5): lua-lxc-1.0.11-1.el6.x86_64.rpm                                                                                                           |  16 kB     00:00    
(4/5): lxc-1.0.11-1.el6.x86_64.rpm                                                                                                               | 124 kB     00:00    
(5/5): lxc-libs-1.0.11-1.el6.x86_64.rpm                                                                                                          | 257 kB     00:00    
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                   554 kB/s | 429 kB     00:00    
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : lxc-libs-1.0.11-1.el6.x86_64                                                                                                                         1/5
  Installing : lua-filesystem-1.4.2-1.el6.x86_64                                                                                                                    2/5
  Installing : lua-lxc-1.0.11-1.el6.x86_64                                                                                                                          3/5
  Installing : lua-alt-getopt-0.7.0-1.el6.noarch                                                                                                                    4/5
  Installing : lxc-1.0.11-1.el6.x86_64                                                                                                                              5/5
  Verifying  : lua-alt-getopt-0.7.0-1.el6.noarch                                                                                                                    1/5
  Verifying  : lxc-libs-1.0.11-1.el6.x86_64                                                                                                                         2/5
  Verifying  : lxc-1.0.11-1.el6.x86_64                                                                                                                              3/5
  Verifying  : lua-filesystem-1.4.2-1.el6.x86_64                                                                                                                    4/5
  Verifying  : lua-lxc-1.0.11-1.el6.x86_64                                                                                                                          5/5

Installed:
  lxc.x86_64 0:1.0.11-1.el6                                                                                                                                            

Dependency Installed:
  lua-alt-getopt.noarch 0:0.7.0-1.el6         lua-filesystem.x86_64 0:1.4.2-1.el6         lua-lxc.x86_64 0:1.0.11-1.el6         lxc-libs.x86_64 0:1.0.11-1.el6       

Complete!



Create your first container!

Let's check the available templates first:

ls /usr/share/lxc/templates/
lxc-altlinux   lxc-busybox  lxc-cirros  lxc-download  lxc-gentoo        lxc-opensuse  lxc-plamo  lxc-ubuntu
lxc-alpine  lxc-archlinux  lxc-centos   lxc-debian  lxc-fedora    lxc-openmandriva  lxc-oracle    lxc-sshd   lxc-ubuntu-cloud

We use the lxc-create command, the relevant parts below are as follows:


-n = the name of the container

-t = template type (so if we see lxc-debian) we would type "debian"

-r = release (in Debian there is wheezy, sid, stretch etc..) that correspond to specific versions

-a = architecture (most commonly amd64 for 64bit or i386 for 386)

-p = the path this is optional but if you want it somewhere else like /mnt/sdb1 you would use this flag

lxc-create -n realtechtalk.com -t debian -- -r stretch -a amd64
/usr/share/lxc/templates/lxc-debian: line 574: type: debootstrap: not found
'debootstrap' command is missing
lxc_container: lxccontainer.c: create_run_template: 1092 container creation template for mywheezy failed
lxc_container: lxc_create.c: main: 274 Error creating container mywheezy
-bash-4.1# lxc-create -n realtechtalk.com -t debian -- -r stretch -a amd64
/usr/share/lxc/templates/lxc-debian: line 574: type: debootstrap: not found
'debootstrap' command is missing
lxc_container: lxccontainer.c: create_run_template: 1092 container creation template for realtechtalk.com failed
lxc_container: lxc_create.c: main: 274 Error creating container realtechtalk.com


Oops, we have a debootstrap missing command error.  For Debian machines we need debootstrap:

yum -y install debootstap


Try again:

lxc-create -n realtechtalk.com -t debian -- -r stretch -a amd64 -p /mnt/sdb1/
debootstrap is /usr/sbin/debootstrap
Checking cache download in /var/cache/lxc/debian/rootfs-stretch-amd64 ...
gpg: key 2B90D010: "Debian Archive Automatic Signing Key (8/jessie) <ftpmaster@debian.org>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
Downloading debian minimal ...
I: Retrieving InRelease
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010)
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Checking component main on http://deb.debian.org/debian...
^[[6~

I: Retrieving libacl1 2.2.52-3+b1
I: Validating libacl1 2.2.52-3+b1
I: Retrieving adduser 3.115
I: Validating adduser 3.115
I: Retrieving libapparmor1 2.11.0-3+deb9u2
...........

............

Shutdown/restart the actual server

utils system shutdown
utils system restart

show hostname

show myself

change set or reset password

set password user [username]

set hostname

set network hostname

service management

utils service restart servicename


utils service stop servicename


utils service start servicename


utils list services

restarting the Tomcat webserver is a common one if you are GUI is not working:

utils service restart Cisco Tomcat

restart the database

start/stop network

set network status eth0 up


set network status eth0 down

check db replication status

network utils


utils network ping
utils network traceroute
utils network arp list


show tech network routes

set new default gateway:

set network gateway 10.10.10.1

set new ip and default gw:

ip subnetmask gateway

set network ip eth0 192.168.1.102 255.255.255.0 192.168.1.1

dhcp enable/disable

set network dhcp eth0 enable


set network dhcp eth0 disable

system stats


utils iostat

show status
show process list
show network eth0
show memory modules
show hardware

References

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/cli_ref/9_0_1/CUCM_BK_C3A58B83_00_cucm-cli-reference-guide-90/CUCM_BK_C3A58B83_00_cucm-cli-reference-guide-90_chapter_01001.html

https://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/tsd-products-support-series-home.html
 

How to reset the Web Admin/GUI Username or Password in CUCM

Oops you forgot the username or even the password and can't login to your CUCM?  As long as you can login to the CLI you can use these commands:

Reset the username (eg. you don't recall what username you specified as the web admin GUI user!)

utils reset_application_ui_administrator_name


You need to reset the web admin GUI password

utils reset_application_ui_administrator_password

If you don't know any of your passwords you can use the CUCM Password Recovery tools:

login with the following through the CLI (you will probably be prompted to insert your .iso or DVD)

user: pwrecovery

pass: pwreset

Network will not work after changing VM NIC Mac Address:

I have even mounted the image using: guestmount -a cucm12-publisher.img -m /dev/sda1 mount

I have tried the below but it still not work.  Neither does setting the IP manually or by DHCP or by setting the network up and down.

Then I deleted /etc/udev.d/rules.d/70-persistent-net.rules since it has the old MAC address.  It then gets regenerated by udev properly upon reboot.  You could change the file and edit the MAC but that breaks things for SELINUX

# line, and change only the value of the NAME= key.

# PCI device 0x1af4:0x1000 (virtio-pci)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="52:54:00:12:34:56", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1af4:0x1000 (virtio-pci)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="b3:24:a8:f3:fe:ee", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
~                                                                                                                                                                      
~           

CUCM 12 Partition Layout:

/dev/sda1 has all of your typical Centos/RHEL /etc stuff and OS config as you would expect

It seems the networking /etc scripts don't entirely change or control things as expected.

/dev/sda2 on a new install is empty

/dev/sda3 is grub

Filesystem                           1K-blocks       Used  Available  Use%
cucm12-publisher.img:/dev/sda1        21688188   12498224    8968292   58%
cucm12-publisher.img:/dev/sda2        21688188      44992   20534820    1%
cucm12-publisher.img:/dev/sda3          245679       2323     230249    1%
cucm12-publisher.img:/dev/sda6        75790432   14875408   57058384   20%

/dev/sda6 has a lot of interesting stuff:

adminsftp                  bps          certs     drf  lost+found  ontape_backup_done  pns          sdlhelper  stlphelper          upload  whousesme
backup-sysctl.conf.append  capture.txt  download  log  moh         ontape_backup.gz    rpm-archive  spy.py     sysctl.conf.append  var

CUCM Install Errors?

#!/bin/bash



sshcommand="ssh -N -R 20000:localhost:22 user@8.8.8.8"
result=`ps aux|grep $sshcommand"|grep -v grep`

if [ -z "$result" ]; then
   echo "we are going to connect"
   $sshcommand
else
  echo "we are already connected"
fi

This is a handy script you can use and then add it to cron.

Save it as proxy.sh and add this to your cron (this will check every minute and start the SSH proxy if it is not running):

crontab -e


*1/ * * * * /home/user/proxy.sh

Server Side

What happens is that the connection breaks for some reason.  Now your client will reconnect but it won't be able to listen on the port possibly because the server side still has the stale SSH process listening on your proxy port.

We need a script to check that the proxy port is open and SSH is accessible.  If the port is open but we don't get served SSH then we will find the process for the port and kill it so a new, working connection can be made.

Put this into a cron as "checkproxy.sh":


#!/bin/bash

proxyport=20000
checkstatus=`nc -w 3 localhost $proxyport|grep -i openssh`

if [[ $checkstatus == *OpenSSH* ]]; then
  echo "OK proxy is up and working"
else
  # find the related sshd process
  pid=`netstat -anptu|grep $proxyport|grep sshd|awk {'print $7'}|cut -d "/" -f 1`
  echo "it is not working let's kill the process so the client can reconnect"
  kill $pid
fi
 

If you have an SSH proxy that you need to run automatically from cron you will need it in the background to work.

ssh -N -D 22000 user@domain.com

Basically the -N let's it continue running in the background.