RealTechTalk (RTT) - Linux/Server Administration/Related

We have years of knowledge with technology, especially in the IT (Information Technology) industry.

realtechtalk.com will always have fresh and useful information on a variety of subjects from Graphic Design, Server Administration, Web Hosting Industry and much more.

This site will specialize in unique topics and problems faced by web hosts, Unix/Linux administrators, web developers, computer technicians, hardware, networking, scripting, web design and much more. The aim of this site is to explain common problems and solutions in a simple way. Forums are ineffective because they have a lot of talk, but it's hard to find the answer you're looking for, and as we know, the answer is usually not there. No one has time to scour the net for forums and read pages of irrelevant information on different forums/threads. RTT just gives you what you're looking for.

Latest Articles

Cisco Unified Communications Manager / CUCM IP 8.6,10,12 Install Error Solution

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()

Ubuntu Debian Mint Linux SSHD OpenSSH Server Not Starting After Reboot Solution

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;service sshd restart" > /etc/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 how to scan for all ports and not just the 1000 most common ports

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

Windows 7,8,10 and Server 2008, 2012, 2016, 2019 Read Only Attribute Won't Go Away

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.

bind / named how to make a wildcard record and retain defined A records

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.

Cisco Unified Communications Manager 12 Install Errors on Proxmox/KVM

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>

Local Vs Universally Administered MAC Address NIC Refuses to come up

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

Cisco Unified Communications Manager 12 CUCM 12 - How To Enable Video Calling

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.

Windows 7, 8, 10, Windows Server 2008, 2012, 2016, 2019 How To AC97 Audio Drivers and Other Unsigned Drivers

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.

Cisco Unified Communications Manager / CUCM IP Telephony Definitions

DN = Directory Number:

It is basically the extension of the phone

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

tftp Linux xinetd verbose logging

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

Linux delete unused tap devices automatically

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

Linux qemu-kvm How To Enable Soundcard in Guestl

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'

QEMU-KVM Windows and Server Guest Installs Mouse Tracking Pointer Location Solution

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...

SSH Keep Alive To stop Disconnections

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

Linux How To Disable SATA NCQ For Better Performance

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)
:

the sign-in method you're trying to use isn't allowed. For more info, contact your network administrator - solution for active directory

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

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.
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 for Windows to Check the SMART S.M.A.R.T status

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

WebRTC Vulnerability Shows Local IP Address Even When Using a Proxy or VPN Firefox Fix And Disable Solution

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 in Linux Howto Simple and Easy Guide

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.

qemu-kvm qemu-system 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 'ra

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

Linux Over VNC VMWare How To Switch Virtual Terminals Console Without Using Ctrl+Alt+F1

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).

Skype For Business 2015 and 2019 Guide, Reference, Howto and Troubleshooting Solutions

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"

Centos 6 or 7 no DHCP IP during startup on first boot or reboot solution

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.

Debian / Mint / Ubuntu net-tools packages provides netstat, ifconfig, route, arp and other classic network admin tools

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..

Linux Mint XWindows Ubuntu MATE or Cinnamon How To Restart The GUI / Graphics / Session if it freezes without losing current windows or programs

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.

Linux bash prompt why does it not show username@host and the current directory?

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

Microsoft SQL Server Check What Version is Running

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

How to install and setup LXC Containers (OpenVZ alternative) on Centos 6 / 7

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...........

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

Cisco CUCM Unified Communication Manager Howto Guide and Tutorials

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

start/stop network

set network status eth0 up

set network status eth0 down

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

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?

SSH persistent and automatic login script for proxy

#!/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

SSH proxy/command in the background or from cron script

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.

ssh reverse proxy to enable remote access behind a LAN and firewall

So say you are behind a typical NAT/LAN setup whether at home, work or while travelling. What if you have a computer or server that you need to connect to from the outside?

Yes you could use a VPN but a quick and dirty, temporary and secure way is to use SSH's Reverse Tunneling Proxy feature.

Requirements

On the remote ssh server host you need the GatewayPorts option enabled in sshd_config (be sure to restart sshd after making the change)

Your sshd_config needs this:

GatewayPorts yes

On the client / machine that is behind the firewall run the SSH command

ssh -R 33000:localhost:3389 username@remoteip

33000 means when we connect to remoteip:33000 we will be connected to port 3389 o the localhost.

Now we can change the localhost to another IP on our LAN if we wanted to.

Now if we connected to remote ip's 3389 we could connect to RDP even though the machine is firewall'd (this works even if all ports are closed and nothing is forwarded to your machine since the ssh -R reverse proxy command is what handles our inbound connections through the remoteip).

How To Use Letsencrypt SSL/TLS Encryption to Create Certificates without installing on the target machine

For some reason, perhaps you don't want to run a daemon or let Letsencrypt have access to your production server.

There is a way to use it like a normal CSR/CA setup in manual mode.

./letsencrypt-auto certonly --manual -d realtechtalk.com - www.realtechtalk.com

Eventually you will get prompted to create a certain path and file with certain data:

Create a file containing just this data: CasdfasfadsfsadfsdafsdafdsafdsafdsuKVQ And make it available on your web server at this URL: http://realtechtalk.com.well-known/acme-challenge/C-asdfasfdsafdsQciE_IQ8 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Press Enter to Continue

#edit this script to suite your vhost path and then run it:

#!/bin/bash fullurl=$1 data=$2 if [ -z $fullurl ] || [ -z $data ]; then echo "Usage $0 http://url/.well-known/file data" exit 1 fi #replace http://www if [[ $fullurl == http://www.* ]]; then path=`echo $fullurl|sed s#"http://www."##g|cut -f 1 -d "/"` #echo "path with www" else path=`echo $fullurl|sed s#"http://"##g|cut -f 1 -d "/"` fi fullpath=/www/vhosts/$path/httpdocs/ createpath=`echo $fullurl|sed s#"http://"##g|cut -d "/" -f 4` # put your main vhost path here cd /www/vhosts/$path/httpdocs mkdir -p .well-known/acme-challenge echo "$data" > .well-known/acme-challenge/$createpath

Then run the script:

the first argument is the URL they wanted you to create the second is the data they want in the file.

./letsencrypt-realtechtalk.com http://realtechtalk.com.well-known/acme-challenge/C-asdfasfdsafdsQciE_IQ8 CasdfasfadsfsadfsdafsdafdsafdsafdsuKVQ

Then hit enter on the letsencrypt screen

Waiting for verification... Cleaning up challenges IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/realtechtalk.com/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/realtechtalk.com/privkey.pem Your cert will expire on 2019-06-26. To obtain a new or tweaked version of this certificate in the future, simply run letsencrypt-auto again. To non-interactively renew *all* of your certificates, run "letsencrypt-auto renew" - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le

After this you can just copy over the .pem files to your server as needed.

bash if statement with wildcard string matching

In this case if fullurl started with http://www. then it is a match

Note that you CANNOT put quotes around it or it becomes a literal match which will not work as intended in the bash script example below.

if [[ $fullurl == http://www.* ]]; then echo "do something" fi

Another example say we want to delete every file or dir in a path except sometihng that starts with "hellothere":

for file in `ls -1`; do if [[ $file == hellothere* ]]; then echo "oops electrum $file - do nothing" else rm -rf $file fi done

We could also change the if above to match "hellothere" at the end or in the middle eg. $file== *hellothere*

Cisco Router Setup Guide and Tutorial Howto With Commands and Examples

In most of the Cisco router IOS I find the ports like ge0/0 ge0/1 and ge0/2 or whatever your ports are down. They will not even give you a link light. So one of the first tasks should be getting the port you are working with up.

In my case the first goal is often connectivity with the LAN and WAN.

LAN = your local area network (eg. in the office/home )

WAN = your ISP/public internet (eg. fiber/cable/dsl/ethernet).

In these examples I assume we have 3 x gigabit ethernet interfaces.

GE0/0, GE0/1, GE0/2

GE0/0 plugged into the WAN / public internet

GE0/1 lugged into the LAN / local net

Login and bring up GE0/1 (your LAN port) which should be plugged into another switch

#you can also use int gi0/1 for short

Router>enable Router#conf t Router(config)#interface gigabitethernet0/1 Router(config-if)#no shutdown

*Mar 25 20:39:21.151: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
*Mar 25 20:39:23.695: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*Mar 25 20:39:24.695: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up

Assign an IP address to an interface:

Router(config-if)#int gi0/1 Router(config-if)#ip address 192.168.1.1 255.255.255.0

You should be able to ping this IP from devices connected to the switch provided that they are on the same VLAN as the port that you have plugged into on the switch. You should also be able to ping other devices on your LAN from the router interface successfully.

Create a DHCP Pool for this network:

#let's run our own DNS R1(config)#ip dns server R1(config)#ip dhcp pool nat R1(dhcp-config)#default-router 192.168.1.1 R1(dhcp-config)#network 192.168.1.0 255.255.255.0 #specify ourselves/own DNS as the DNS server for clients to use R1(dhcp-config)#dns-server 192.168.1.1 #go back to our main config and make sure we exclude the router address R1(config)#ip dhcp excluded-address 192.168.1.1

show interface status/brief details:

show interface gi0/0 GigabitEthernet0/0 is up, line protocol is up Hardware is PQ3_TSEC, address is 881d.fc4f.4500 (bia ----------------) Internet address is 199.24.89.101/25 MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full Duplex, 1Gbps, media type is RJ45 output flow-control is unsupported, input flow-control is unsupported ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:00, output 00:00:03, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 1000 bits/sec, 1 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 791 packets input, 91550 bytes, 0 no buffer Received 784 broadcasts (0 IP multicasts) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 27 multicast, 0 pause input 80 packets output, 10098 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets 13 unknown protocol drops 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier, 0 pause output 0 output buffer failures, 0 output buffers swapped out

show the ip of an interface:

show ip interface gi0/0 GigabitEthernet0/0 is up, line protocol is up Internet address is 199.24.89.101/25 Broadcast address is 255.255.255.255 Address determined by DHCP MTU is 1500 bytes Helper address is not set Directed broadcast forwarding is disabled Outgoing access list is not set Inbound access list is not set Proxy ARP is enabled Local Proxy ARP is disabled Security level is default Split horizon is enabled ICMP redirects are always sent ICMP unreachables are always sent ICMP mask replies are never sent IP fast switching is enabled IP fast switching on the same interface is disabled IP Flow switching is disabled IP CEF switching is enabled IP CEF switching turbo vector IP multicast fast switching is enabled IP multicast distributed fast switching is disabled IP route-cache flags are Fast, CEF Router Discovery is disabled IP output packet accounting is disabled IP access violation accounting is disabled TCP/IP header compression is disabled RTP/IP header compression is disabled Policy routing is disabled Network address translation is enabled, interface in domain outside BGP Policy Mapping is disabled Input features: Common Flow Table, Stateful Inspection, Virtual Fragment Reassembly, Virtual Fragment Reassembly After IPSec Decryption, NAT Outside, MCI Check Output features: Post-routing NAT Outside, Common Flow Table, Stateful Inspection, NAT ALG proxy IPv4 WCCP Redirect outbound is disabled IPv4 WCCP Redirect inbound is disabled IPv4 WCCP Redirect exclude is disabled

Show routing table:

show ip route Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP a - application route + - replicated route, % - next hop override Gateway of last resort is 0.0.0.0 to network 0.0.0.0 S* 0.0.0.0/0 is directly connected, GigabitEthernet0/0 199.81.0.0/16 is variably subnetted, 3 subnets, 2 masks C 199.81.89.0/25 is directly connected, GigabitEthernet0/0 L 199.81.89.101/32 is directly connected, GigabitEthernet0/0 S 199.81.204.103/32 [254/0] via 199.81.89.126, GigabitEthernet0/0 10.20.1.0/24 is variably subnetted, 2 subnets, 2 masks C 10.20.1.0/24 is directly connected, GigabitEthernet0/1 L 10.20.1.1/32 is directly connected, GigabitEthernet0/1

Show arp table:

Switch#show arp Protocol Address Age (min) Hardware Addr Type Interface Internet 10.25.20.20 - 0000.0000.0000 ARPA Vlan7 Internet 192.168.1.1 0 0000.0000.0000 ARPA Vlan9 Internet 192.168.1.3 7 0000.0000.0000 ARPA Vlan9 Internet 192.168.1.2 - 0000.0000.0000 ARPA Vlan9

In the above example .1 is our own router gi0/1 IP, .2 is the switch and .3 is a client device. The 10.25.20.20 is assigned to another VLAN (7) on the switch.

Set hostname

Router(config)#hostname realtechtalk.com realtechtalk.com(config)#

Enable http/https Web Server

Router(config)#ip http server Router(config)#ip http secure-server % Generating 1024 bit RSA keys, keys will be non-exportable...

Enable SSH Server

#Set a domain name, username and password

Router(config)#ip domain-name realtechtalk.com Router(config)#username testuser privilege 15 Password realechtalk.compass

#create your SSH RSA keys

crypto key generate rsa

#I choose at least a key size of 4096

The name for the keys will be: realtechtalk.com.realtechtalk.com Choose the size of the key modulus in the range of 360 to 4096 for your General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes. How many bits in the modulus [512]: 4096 % Generating 4096 bit RSA keys, keys will be non-exportable... [OK] (elapsed time was 43 seconds)

Router(config-line)#line vty 0 Router(config-line)#transport input ssh Router(config-line)#password realtechtalk.com Router(config-line)#login Router(config-line)#logging synchronous Router(config-line)#banner motd "realtechtalk.com" Router(config-line)#exit

Change SSH Port

Here we change the port to 3599 for rotary value 1 (or whatever number we specify for rotary).

realtechtalk.com(config)#ip ssh port 3599 rotary 1

Then take the rotary value and assign it to line vty 0 (or whatever vty you used for your SSH):

realtechtalk.com(config)#line vty 0 realtechtalk.com(config-line)#rotary 1

If you want only the new SSH port to be accessed then follow this to add a proper ACL

#do not forget the permit ip any any after the deny or you will have blocked your new SSH port too!

realtechtalk.com(config)#ip access-list extended sshblock realtechtalk.com(config-ext-nacl)#deny tcp any any eq 22 realtechtalk.com(config-ext-nacl)#permit ip any any realtechtalk.com(config-ext-nacl)#line vty 0 realtechtalk.com(config-line)#access-class sshblock in

Is SSH enabled?

realtechtalk.com#show ip ssh SSH Enabled - version 2.0 Authentication methods:publickey,keyboard-interactive,password Authentication timeout: 50 secs; Authentication retries: 2 Minimum expected Diffie Hellman key size : 1024 bits IOS Keys in SECSH format(ssh-rsa, base64 encoded):

#sometimes there are issues logging in:

ssh testuser@192.168.1.1
Connection closed by 192.168.1.1

The error above where you do not get a password prompt from SSH is caused by your client and also Cisco. You see if you check the logs, it will often try to send your RSA key to authenticate, when that fails it also says your password failed (even though it never prompted you!). I am thinking it is a bug. If you have client-side SSH keys you need to make sure you DO NOT send them by using this option on the client side:

ssh -o PubkeyAuthentication=no user@10.10.10.1

debug ip ssh

*Mar 26 21:20:23.079: SSH2 0: MAC compared for #6 :ok *Mar 26 21:20:23.079: SSH2 0: input: padlength 10 bytes *Mar 26 21:20:23.079: SSH2 0: Using method = publickey *Mar 26 21:20:23.079: SSH2 0: Verifying pubkey blob is acceptable for 'testuser' in SSH2_MSG_USERAUTH_REQUEST *Mar 26 21:20:23.079: SSH2 0: Publickey for 'testuser' not found *Mar 26 21:20:23.079: SSH2 0: Pubkey Authentication failed for user 'testuser' *Mar 26 21:20:23.079: SSH0: password authentication failed for testuser

The client side ssh -v shows abou the same and basically it never prompts for a password.

Who is connected to SSH?

show ssh %No SSHv2 server connections running. %No SSHv1 server connections running.

Enable password (also works for http/https/ssh/telnet)

Router#conf t Enter configuration commands, one per line. End with CNTL/Z. Router(config)#enable password realtechtalk.com Router(config)#end Router#wr Building configuration...

Enable telnet password:

R1(config)#line vty 0 1 R1(config-line)#password realtechtalk.com

You need a vty password set otherwise you won't be able to telnet in:

Trying 10.10.10.1...
Connected to 10.10.10.1.
Escape character is '^]'.

Password required, but none set
Connection closed by foreign host.

Setting Up NAT in 4 commands

The following assumes gi0/0 is the WAN and gi0/1 points to the LAN

#first let's create our access list which really in our case is the subnet to be used for the internal NAT 192.168.1.0/24 realtechtalk.com(config)#access-list 23 permit 192.168.1.0 realtechtalk.com(config)#access-list 23 permit 0.0.0.0 255.255.255.0 realtechtalk.com(config)access-list 199 permit ip any any

#create NAT overload on our outside interface (gi0/0) pointing to the inside

realtechtalk.com(config)ip nat inside source list 199 interface gi0/0 overload #now define the internal NAT interface (in our case gi0/1 which is connected to our LAN). realtechtalk.com(config)#int gi0/1 realtechtalk.com(config-if)#ip nat inside #now we define the external/public/WAN NAT interface realtechtalk.com(config)#int gi0/0 realtechtalk.com(config-if)#ip nat outside

#not working still don't forget your default route/last resort especially if you are using DHCP on gi0/0 (your WAN interface)

ip route 0.0.0.0 0.0.0.0 dhcp

Linux Bash Script To List All Connected IPs and their network name

for ip in `netstat -nt|awk '{ print $5 }'|cut -d ":" -f 1|tail -n +3|sort|uniq`; do echo $ip;whois $ip|grep -i netname;echo "---------------------------" done

77.88.47.40
netname:        YANDEX-77-88-47
---------------------------
40.77.167.5
---------------------------
180.76.15.143
netname:        Baidu
---------------------------
77.88.47.40
netname:        YANDEX-77-88-47
---------------------------
5.255.250.113
netname:        YANDEX-5-255-250
---------------------------
77.88.47.40
netname:        YANDEX-77-88-47
---------------------------
180.76.15.156
netname:        Baidu
---------------------------
77.88.47.40
netname:        YANDEX-77-88-47
---------------------------
207.46.13.111
---------------------------
77.88.47.40
netname:        YANDEX-77-88-47
---------------------------

Revised More Efficient/Better Version:

I like this version better becaues it uses the same data from netstat because even a few seconds later the table may have changed and the connection will no longer be visible. This way is also quicker and more efficient since there are no more multiple calls to the netstat binary.

rawoutput=`netstat -nt` ipoutput=`echo "$rawoutput"|awk '{ print $5 }'|cut -d ":" -f 1|tail -n +3|sort|uniq` for ip in $ipoutput; do echo $ip; sourceconn=`echo "$rawoutput"|grep -i $ip|awk '{print $4}'|sort|uniq` whois=`whois $ip|grep -Ei "netname|range:|route:|cidr:"` if [ -z "$whois" ]; then whois=`whois $ip|grep -vE "^$|^#|^$|^["` fi echo -e "$whoisn$sourceconnn---------------------------" done

More Advanced/Slower Version

The above version doesn't always capture the name of the network, here is a more advanced script that is more inclusive and also shows the IP ranges associated with the IP and also the IPs and ports it is actually connected to.

for ip in `netstat -nt|awk '{ print $5 }'|cut -d ":" -f 1|tail -n +3|sort|uniq`; do echo $ip; sourceconn=`netstat -nt|grep -i $ip|awk '{print $4}'|sort|uniq` whois=`whois $ip|grep -Ei "netname|range:|route:|cidr:"` if [ -z "$whois" ]; then whois=`whois $ip|grep -vE "^$|^#|^$|^["` fi echo -e "$whoisn$sourceconnn---------------------------" done

58.242.83.36
netname:        HUAIBEIBASIP
route:          58.242.0.0/15
route:          58.242.0.0/15
192.168.1.236:22
---------------------------
198.255.100.58
FDCservers.net FDCSERVERS (NET-198-255-0-0-1) 198.255.0.0 - 198.255.127.255
FDCservers.net FDCSERVERS-DENVERENT (NET-198-255-100-0-1) 198.255.100.0 - 198.255.101.255
192.168.1.102:80
192.168.1.189:80
192.168.1.236:80
192.168.1.61:80
---------------------------
185.71.66.10
netname:        StormWall-net
route:          185.71.66.0/24
192.168.1.102:80
192.168.1.189:80
192.168.1.236:80
192.168.1.61:80
---------------------------

Cisco Switches How To Get Of Port Line Status Console Messages

00:55:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to down 00:55:09: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to up

Switch(config)#no logging console

Cisco DHCP Snooping Relay Setup Information

Switch#show ip dhcp snooping

Switch DHCP snooping is disabled DHCP snooping is configured on following VLANs: 1 Insertion of option 82 is enabled circuit-id format: vlan-mod-port remote-id format: MAC Option 82 on untrusted port is not allowed Verification of hwaddr field is enabled Interface Trusted Rate limit (pps) ------------------------ ------- ---------------- FastEthernet0/1 yes unlimited GigabitEthernet0/1 yes unlimited

To enable global "Switch DHCP Snooping":

Switch(config)#ip dhcp snooping

To enable DHCP snoop debugging

Note this only works IF the global dhcp snooping is enabled

debug ip dhcp snooping packet

To disable the DHCP debugging:

no debug ip dhcp snooping packet

Enable Port As Trusted:

You cannot broadcast DHCP unless the port is trusted so here's how you enable trust on a port (it does not work on a vlan I suppose for security reasons):

Switch(config-if)#int fa0/1 Switch(config-if)#ip dhcp snooping trust

Enable Snooping on VLAN:

Switch(config)# Switch(config)#ip dhcp snooping vlan 1

Allow Untrusted Port:

int fa0/3

ip dhcp snooping information option allow-untrusted

Disable Option 82

If the relay or destination DHCP server doesn't support Option 82 Information it will break your DHCP and you will NOT get an IP/lease.

So disable Option 82 unless you are sure your network supports it:

Switch(config)#no ip dhcp snooping information option

Resources:

https://community.cisco.com/t5/switching/dhcp-snooping-not-working-dropping-packets/td-p/2076543

https://www.askitmen.com/network/ccna/configure-dhcp-snooping/

Cisco Switch Setup Guide Command List

Enter configuration console:

enable

configure terminal

This is important because if your console doesn't look like below none of the commands will work!

Switch(config)#

Save and Apply Settings

wr

Show Switch Configuration:

show run

Show Port List/Status:

Switch#show interface status Port Name Status Vlan Duplex Speed Type Fa0/1 connected 1 a-full a-100 10/100BaseTX Fa0/2 notconnect 1 auto auto 10/100BaseTX Fa0/3 notconnect 1 auto auto 10/100BaseTX Fa0/4 notconnect 1 auto auto 10/100BaseTX Fa0/5 notconnect 1 auto auto 10/100BaseTX Fa0/6 notconnect 1 auto auto 10/100BaseTX Fa0/7 notconnect 1 auto auto 10/100BaseTX Fa0/8 notconnect 1 auto auto 10/100BaseTX Fa0/9 notconnect 1 auto auto 10/100BaseTX Fa0/10 notconnect 1 auto auto 10/100BaseTX Fa0/11 notconnect 1 auto auto 10/100BaseTX Fa0/12 notconnect 1 auto auto 10/100BaseTX Fa0/13 notconnect 1 auto auto 10/100BaseTX Fa0/14 notconnect 1 auto auto 10/100BaseTX Fa0/15 notconnect 1 auto auto 10/100BaseTX Fa0/16 notconnect 1 auto auto 10/100BaseTX Fa0/17 notconnect 1 auto auto 10/100BaseTX Fa0/18 notconnect 1 auto auto 10/100BaseTX Fa0/19 notconnect 1 auto auto 10/100BaseTX Fa0/20 notconnect 1 auto auto 10/100BaseTX Fa0/21 notconnect 1 auto auto 10/100BaseTX Fa0/22 notconnect 1 auto auto 10/100BaseTX Fa0/23 notconnect 1 auto auto 10/100BaseTX Fa0/24 notconnect 1 auto auto 10/100BaseTX Gi0/1 connected 1 a-full a-1000 10/100/1000BaseTX Gi0/2 notconnect 1 auto auto Not Present

Show config of individual port or vlan

You could also have used "interface vlan 1" and you would get the config of the vlan.

Switch#show running-config interface gi0/1 Building configuration... Current configuration : 36 bytes ! interface GigabitEthernet0/1 end

Show all VLANs:

show vlan

VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------- 1 default active Fa0/1, Fa0/2, Fa0/3, Fa0/4 Fa0/5, Fa0/6, Fa0/7, Fa0/8 Fa0/9, Fa0/10, Fa0/11, Fa0/12 Fa0/13, Fa0/14, Fa0/15, Fa0/16 Fa0/17, Fa0/18, Fa0/19, Fa0/20 Fa0/21, Fa0/22, Fa0/23, Fa0/24 Gi0/1, Gi0/2 1002 fddi-default act/unsup 1003 token-ring-default act/unsup 1004 fddinet-default act/unsup 1005 trnet-default act/unsup VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2 ---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------ 1 enet 100001 1500 - - - - - 0 0 1002 fddi 101002 1500 - - - - - 0 0 1003 tr 101003 1500 - - - - - 0 0 1004 fdnet 101004 1500 - - - ieee - 0 0 1005 trnet 101005 1500 - - - ibm - 0 0

Show Specific VLAN

show vlan id 1

Configure interfaces

100M Ethernet is normally known as fa0

So for port 1 you would use fa0/1

int fa0/1

int fastethernet0/1

1Gig Ethernet known as gigabitethernet or gi0

int gigabitethernet0/1

int gi0/1

You can configure vlans in the same way:

int vlan 1

Working with a range of ports (example of ports 1-12)

int range fa0/1-12

Enable Port(s)

int fa0/1

no shutdown

The no in front of shutdown means turn on the port (the opposite or !)

How to Assign ports to vlan

#how to assign ports to vlan in this case it is ports 1-24 and they are being assigned to vlan 1

Switch(config)#int range fa0/1-24 Switch(config-if-range)#switchport access vlan 1

Port Security

Maximum MAC addresses/devices

Where 8 below is the maximum number of MAC's

rtt(config)#int fa0/3 rtt(config-if)#switchport port-security maximum 8

To Disable MAC Limit

rtt(config-if)#no switchport port-security maximum

How To Disable Port Security On A Port

no switchport port-security no switchport port-security violation protect no switchport port-security mac-address sticky no switchport mode access

BPDU Guard

This can be the source of a lot of pain for end users and network admins. To understand this, first let's talk about STP (Spanning Tree Protocol) which is designed to prevent routing loops that would otherwise kill a network. A routing loop could be something as simple as an ethernet cable that has both ends plugged into the same switch.

STP works by exchanging BPDU (Bridge Protocol Data Units) which are multicast messages sent out and contain info like the source MAC, switch ID, originating switch port, switch port priority. It then uses an algorithm based on the BPDU information to create an STA (Spanning Tree Algorithm) at the layer 2 level and will shut down a port if it is creating a loop.

Now BPDU Guard in the world of Cisco just means that if it receives a BPDU it will shutdown the port in errdisable.

I say this is good in terms of keeping a network secure and running well, but a pain for end users who need to run a managed switch and for network admins who were unaware that BPDU was enabled.

Check a port's settings and you may see this:

rtt#show run int gi0/1 Building configuration... Current configuration : 335 bytes ! interface GigabitEthernet0/1 switchport access vlan 999 switchport mode access switchport port-security switchport port-security aging time 2 switchport port-security violation restrict switchport port-security aging type inactivity macro description cisco-desktop spanning-tree portfast spanning-tree bpduguard enable end

To disable bpduguard
rtt(config-if)#spanning-tree bpduguard disable

To enable bpduguard

rtt(config-if)#spanning-tree bpduguard enable

*Note you can also enable or disable BPDUguard globally by just being in conf t

#enable by default

rtt(config)#spanning-tree portfast bpduguard default

#disable by defaultrtt(config)#no spanning-tree portfast bpduguard default

How to assign IP to VLAN

Choose your interface eg vlan 777

Where below 10.25.20.2 is the IP and the netmask is 255.255.255.0

Switch(config-if)#ip address 10.25.20.2 255.255.255.0

Assign the default gateway:

Switch(config-if)#ip default-gateway 10.25.20.1

How To Set Administrative "enable" mode Password

Switch(config)#enable password realtechtalk.com

DHCP Server Creation for VLAN

Create VLAN and assign IP 10.25.2.2 and DFGW 10.25.2.1

switch(config-if)#int vlan 1800 switch(config-if)#ip address 10.25.2.2 255.255.255.0 switch(config-if)#ip default-gateway 10.25.2.1

#you could add Option 150 if this VLAN is for phones and you have a CUCM Server (specify the CUCM server IP)

switch(dhcp-config)#option 150 ip 10.25.2.8

Create DHCP Pool for VLAN 1800 range 10.25.2.0

switch(config)#ip dhcp pool Update switch(dhcp-config)#network 10.25.2.0 255.255.255.0 switch(dhcp-config)#dns-server 8.8.8.8 4.2.2.1 switch(dhcp-config)#default-router 10.25.2.1

Exclude Relevant Addresses

switch(config)#ip dhcp excluded-address 10.25.2.1 10.25.2.2

Troubleshooting

Why can't I ping or connect to my VLAN IP?

Make sure the VLAN that has the IP is assigned to a port
Make sure the IP address is correct and it has the appropriate default gateway if necessary
Make sure your client side machine has an IP on that subnet AND that you have a route to it through the right adapter (eg. in Linux ip route add 10.10.25.0/24 dev eth0)*Remember to specify the /24 or whatever mask you desire and the right device.
Is the port and VLAN in a noshut state?

Cisco 2960 Switch Reset To Factory Defaults

*The easy way is to just hold the mode button for 10+ seconds.

The full/proper way is below:

1.) Either power on the unit and hold the "mode" button or hold the "mode" button until you see the below:

00:04:08: %SYS-7-NV_BLOCK_INIT: Initalized the geometry of nvram
00:04:08: %EXPRESS_SETUP-6-CONFIG_IS_RESET: The configuration is reset and the system will now reboot
00:04:09: %SYS-5-RELOAD: Reload requested Reload Reason: power-on.
Base ethernet MAC Address: 00:1a:a2:4e:6a:00
Xmodem file system is available.
The password-recovery mechanism is enabled.
Initializing Flash...
flashfs[0]: filesystem check interrupted!
...done Initializing Flash.
Boot Sector Filesystem (bs) installed, fsid: 3

The system has been interrupted, or encountered an error
during initializion of the flash filesystem. The following
commands will initialize the flash filesystem, and finish
loading the operating system software:

    flash_init
    load_helper
    boot

2.) Initialize the flash by typing "flash_init"

switch: flash_init
Initializing Flash...
flashfs[0]: 600 files, 19 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 32514048
flashfs[0]: Bytes used: 7713280
flashfs[0]: Bytes available: 24800768
flashfs[0]: flashfs fsck took 10 seconds.
...done Initializing Flash.
Setting console baud rate to 9600...

3.) Delete config files

del flash:config.text
Are you sure you want to delete "flash:config.text" (y/n)?y
File "flash:config.text" deleted

del flash:vlan.dat
Are you sure you want to delete "flash:vlan.dat" (y/n)?y
File "flash:vlan.dat" deleted

4.) boot!

boot

Cisco IOS Software, C2960 Software (C2960-LANBASE-M), Version 12.2(25)SEE2, RELEASE SOFTWARE (fc1) Copyright (c) 1986-2006 by Cisco Systems, Inc. Compiled Fri 28-Jul-06 04:33 by yenanh Image text-base: 0x00003000, data-base: 0x00AA2F34 Initializing flashfs... flashfs[1]: 600 files, 19 directories flashfs[1]: 0 orphaned files, 0 orphaned directories flashfs[1]: Total bytes: 32514048 flashfs[1]: Bytes used: 7713280 flashfs[1]: Bytes available: 24800768 flashfs[1]: flashfs fsck took 1 seconds. flashfs[1]: Initialization complete....done Initializing flashfs. POST: CPU MIC register Tests : Begin POST: CPU MIC register Tests : End, Status Passed POST: PortASIC Memory Tests : Begin POST: PortASIC Memory Tests : End, Status Passed POST: CPU MIC PortASIC interface Loopback Tests : Begin POST: CPU MIC PortASIC interface Loopback Tests : End, Status Passed POST: PortASIC RingLoopback Tests : Begin POST: PortASIC RingLoopback Tests : End, Status Passed

How To Boot Cisco CUCM UCSInstall 8.6, 10, 11 and 12 on KVM/Proxmox

The key thing is that you must use a "machine" id of "pc-1.3" or it will say your hardware is not supported.

Additionally you MUST use a virtio disk or you will get a ks_pre.sh error as soon as the install starts (a look at logs will show it can't find a disk). This is funny because even though the OS finds the disk and an fdisk -l shows it, it looks like the script looks for a /dev/vda device (virtio) and nothing else, so if you didn't use Virtio as your disk and you have a /dev/sda it won't work.

In Promxox you will have to edit your config file like this:

bootdisk: sata0 cores: 12 ide2: local:iso/Bootable_UCSInstall_UCOS_12.iso,media=cdrom,size=3523684K machine: pc-1.3 memory: 8096 name: ciscouc net0: virtio=DE:C3:A0:F8:50:11,bridge=vmbr0 numa: 0 ostype: l26 scsihw: virtio-scsi-pci smbios1: uuid=99bf1ee3-b527-4ea2-bf68-179bee9699b1 sockets: 1 unused0: thin:vm-124-disk-1 virtio0: thin:vm-124-disk-2,size=90G

Raw QEMU-KVM execution:

qemu-system-x86_64 -boot dc -smp 4 -machine pc-1.3 -vnc :1 -m 8096 -drive file=cucum86.img,if=virtio -cdrom Bootable_UCSInstall_UCOS_12.iso

How To Modify the ISO to enable KVM

Tested on UCS 8.6 and 12

mkdir mountcucm mount -o loop Bootable_UCSInstall_UCOS_UNRST_8.6.2.10000-14.sgn.iso mountcucum/

mv cucm8.6kvm/Cisco/hssi/server_implementation/KVM/QEMU/shared/bin/api_implementation.sh.proposed cucm8.6kvm/Cisco/hssi/server_implementation/KVM/QEMU/shared/bin/api_implementation.sh vi cucm8.6kvm/Cisco/base_scripts/ihardware.sh

#change this function hasHwSnmpMonitoring() { local method="hasHwSnmpMonitoring" _forwardToSAM $method $@ } #to function hasHwSnmpMonitoring() { return 1 } cd cucm8.6kvm

#use mkisofs or genisoimage

genisoimage -o /var/lib/vz/template/iso/Bootable_UCSInstall_UCOS_UNRST_8.6.2.10000-14.sgn-KVMenabled-by-realtechtalk.com.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -J -R -iso-level 4

cd cucm8.6kvm/Cisco/hssi/server_implementation

#delete everything other than KVM

total 40K drwxrwxr-x 8 900711 floppy 4.0K Aug 22 2011 . drwxrwxr-x 5 900711 floppy 4.0K Aug 22 2011 .. drwxrwxr-x 5 900711 floppy 4.0K Aug 22 2011 HP drwxrwxr-x 6 900711 floppy 4.0K Aug 22 2011 IBM drwxrwxr-x 5 900711 floppy 4.0K Aug 22 2011 KVM -r--r--r-- 1 900711 floppy 92 Dec 13 2008 README.TXT drwxrwxr-x 4 900711 floppy 4.0K Aug 22 2011 shared -r--r--r-- 1 900711 floppy 1.5K Aug 22 2011 TRANS.TBL drwxrwxr-x 4 900711 floppy 4.0K Aug 22 2011 VMWARE drwxrwxr-x 4 900711 floppy 4.0K Aug 22 2011 VOLARIS

#:/var/lib/vz/template/iso/cucm8.6kvm/Cisco/hssi/server_implementation# rm -rf HP/ IBM/ VMWARE/ VOLARIS/

#you may need to do this:

#fix this file vi Cisco/hssi/server_implementation/KVM/shared/bin/KVM.data #change expected_manufacturer=QEMU|Bochs #to expected_manufacturer=QEMU|Bochs|Seabios

VBOX VirtualBox How To Import Raw .img Disk File

What you need to do if you have taken a dd or real raw image dump of a hard disk:

VBoxManage convertdd windows2019-eval-template.img windows2019.vdi --format VDI

The .img is the raw dd dump and the .vdi is the output file.

--format VDI specifies to output to .vdi format

If you are in a pinch you can always use qemu-kvm binary and manually specify the .img as your disk and it will just work.

*Even the above didn't work for some reason with VBOX

VBoxManage convertdd windows2019-eval-template.img windows2019.vdi --format VDIConverting from raw image file="windows2019-eval-template.img" to file="windows2019.vdi"... Creating dynamic image with size 21474836480 bytes (20480MB)...
*Note if you are mounting the .vdi over SMB or SSHFS you may still get the below error (sometimes it only works well locally)

VD: error VERR_NET_OPERATION_NOT_SUPPORTED

What doesn't work if you have taken a raw image / dd of an LVM or Physical Hard Disk:

I tried the raw image and you get:

Could not get the storage format of the medium (VERR_NOT_SUPPORTED).

Then I converted it to qcow2:

qemu-img convert -f raw -O qcow2 windows2019-eval-template.img windows2019-eval-template.qcow2

But I still got the same error.

So then I tried to convert it to .vdi:

qemu-img convert -f raw -O vdi windows2019-eval-template.img windows2019-eval-template.vdi

VD: error VERR_NET_OPERATION_NOT_SUPPORTED

The original partition of the .img looks like this:

fdisk -l windows2019-eval-template.img Disk windows2019-eval-template.img: 21.5 GB, 21474836480 bytes 255 heads, 63 sectors/track, 2610 cylinders, total 41943040 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 Disk identifier: 0xb5ad7258 Device Boot Start End Blocks Id System windows2019-eval-template.img1 * 2048 1126399 562176 7 HPFS/NTFS/exFAT windows2019-eval-template.img2 1126400 41940991 20407296 7 HPFS/NTFS/exFAT

Windows Server 2012, 2016, 2019 How To Install and Missing Disabled Telnet Client

By default telnet is not enabled or installed on the latest Windows servers so you'll get an error saying:

telnet is not recognized as an internal or external command

dism /online /Enable-Feature /FeatureName:TelnetClient

proxmox vm networking breaks when you restart your network on the hostnode

I did a systemctl restart networking and it broke Proxmox VM connectivity!

#proxmox is the problem after restarting the network the tap devices go to disabled state [2230884.919905] vmbr0: port 7(tap118i0) entered disabled state [2230884.948864] vmbr0: port 8(tap122i0) entered disabled state [2230884.972748] vmbr0: port 6(tap119i0) entered disabled state [2230885.004745] vmbr0: port 5(tap117i0) entered disabled state [2230885.036736] vmbr0: port 4(tap112i0) entered disabled state [2230885.060693] vmbr0: port 3(tap111i0) entered disabled state [2230885.100729] vmbr0: port 2(tap110i0) entered disabled state [2230885.227515] vmbr0: port 1(enp0s8) entered blocking state [2230885.227518] vmbr0: port 1(enp0s8) entered disabled state [2230885.228071] device enp0s8 entered promiscuous mode

As we can see the tap devices went disabled which makes sense BUT they didn't come back so all VMs now have no network connection (the equivalent of basically unplugging the cable from the server):

#use brctl to fix

brctl addif vmbr0 tap118i0

Feb 25 06:30:42 proxmoxdal01 kernel: [2231303.128510] vmbr0: port 2(tap118i0) entered blocking state Feb 25 06:30:42 proxmoxdal01 kernel: [2231303.128513] vmbr0: port 2(tap118i0) entered disabled state Feb 25 06:30:42 proxmoxdal01 kernel: [2231303.128754] vmbr0: port 2(tap118i0) entered blocking state Feb 25 06:30:42 proxmoxdal01 kernel: [2231303.128756] vmbr0: port 2(tap118i0) entered forwarding state

Here is a handy bash script that will automatically readd all of your tap devices to vmbr0

for tapdev in `ip a|grep tap| awk '{print $2}'|sed s/://`; do brctl addif vmbr0 $tapdev done

And they all came back:

Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.163869] vmbr0: port 3(tap110i0) entered blocking state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.163873] vmbr0: port 3(tap110i0) entered disabled state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.164059] vmbr0: port 3(tap110i0) entered blocking state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.164062] vmbr0: port 3(tap110i0) entered forwarding state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.165739] vmbr0: port 4(tap111i0) entered blocking state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.165742] vmbr0: port 4(tap111i0) entered disabled state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.165926] vmbr0: port 4(tap111i0) entered blocking state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.165928] vmbr0: port 4(tap111i0) entered forwarding state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.167515] vmbr0: port 5(tap112i0) entered blocking state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.167520] vmbr0: port 5(tap112i0) entered disabled state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.167717] vmbr0: port 5(tap112i0) entered blocking state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.167721] vmbr0: port 5(tap112i0) entered forwarding state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.169253] vmbr0: port 6(tap117i0) entered blocking state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.169260] vmbr0: port 6(tap117i0) entered disabled state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.169396] vmbr0: port 6(tap117i0) entered blocking state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.169398] vmbr0: port 6(tap117i0) entered forwarding state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.170867] vmbr0: port 7(tap119i0) entered blocking state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.170869] vmbr0: port 7(tap119i0) entered disabled state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.171023] vmbr0: port 7(tap119i0) entered blocking state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.171026] vmbr0: port 7(tap119i0) entered forwarding state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.172605] vmbr0: port 8(tap122i0) entered blocking state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.172608] vmbr0: port 8(tap122i0) entered disabled state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.172768] vmbr0: port 8(tap122i0) entered blocking state Feb 25 06:31:52 proxmoxdal01 kernel: [2231373.172770] vmbr0: port 8(tap122i0) entered forwarding state

Linux ln symlink how to update existing symbolic link

ln -s --force newfile.jpg existingsymlink.jpg

All you do is use the --force flag to force/update the existing one.

The above modifies a symlink called "existingsymlink.jpg" and points it to "newfile.jpg" as the source.

Ubuntu 18.04 / Linux Mint 19.1 Cannot Type or Login - solution

It was broken because of this package for xorg I installed:

xserver-xorg-core-hwe-18.04

Just remove it even if you have to chroot from a live USB/CD:

sudo apt-get remove xserver-xorg-core-hwe-18.04

LUKS Hard Drive Encryption on Linux Mint Ubuntu Debian etc how to mount encrypted hard drive

The key thing here is to know the actual partition that is encrypted.

Often in Linux Mint's installer that ends up being partition 5 or /dev/sda5

sudo cryptsetup luksOpen /dev/sda5 anynamehere

You will then be prompted for your irrecoverable passphrase:

Enter passphrase for /dev/sda5:

If all goes well it won't say anything further. If it says ""No key available with this passphrase." it means you have entered the wrong password.

How to mount

The above command will create a device based on the third argument that you passed to cryptsetup (anynamehere) in the above example.

So you would see i/dev/mapper/anynamehere

From there just go ahead and mount it (assuming it is not using LVM-read on if you are).

mount /dev/mapper/anynamehere /mnt/crypteddisk

Chroot

To make it more practical perhaps you are trying to modify or fix your OS.

From here if we were using many OS's we would then do an "lvscan". It will then show us the LVM volumes and you can then mount the vg-root to /mnt

You can then do something like this:

mount /dev/vgname/vg-root /mnt

#use the bash script to mount /dev /proc and /sys to your /mnt (chroot) root dir so stuff works when you chroot

for mount in dev proc sys; do

mount -o bind /$mount /mnt/$mount

done

#now let's chroot in!

chroot /mnt

How to use nmap locate other machines/computers/servers on your network using nmap

A lot of people think arp wil do it but the arp table will only show devices you have communicated with.

Using nmap is a quick and simple way to scan a range to find a machine you may not know the IP for:

eg:

nmap -sP 10.1.5.0/24

Just change the above to your subnet

Linux Mint 18.2 Create Config File To Start Application Upon Login

This is not about systemd/systemctl and not about "onboot" so there's no rc.local trick here but it's the GUI/Gnome etc when a user logs in that a command is launched.

Put this in your home dir

The .config/autostart directory is where Linux Mint/Ubuntu checks for autostart application config files

mkdir -p ~/.config/autostart

Create a new entry/file that starts an application:

vi realtechtalk.com.desktop

The name can be anything but must have ".desktop" as the extension.

[Desktop Entry] Type=Application Exec=/usr/bin/firefox http://realtechtalk.com Hidden=false X-MATE-Autostart-enabled=true Name[en_US]=firefox Name=firefox Comment[en_US]=Visit realtechtalk.com! Comment=

The key point from above is the "Exec" variable and Name variable. Change exec to what you want to execute and change the name to something meaningful

Dell Wyse Thin Client BIOS Access Key

For most of these machines you just have to power the unit on while holding the "Del" key and you'll enter the BIOS.

sudoers file in /etc warning about comments/includes!

If you see this in /etc/sudoers it is NOT a comment but an include.

#includedir /etc/sudoers.d

For example in Linux mint sudoers.d contains the following files:

casper mintupdate README

casper for example contains the following sudoers line:

mint ALL=(ALL) NOPASSWD: ALL

So if you are messing around with sudoers or creating a new file understand that #includedir is absolutely not a comment and may be critical to properly functioning sudo functionality for your machine or user.

Of course this is contrary to most Unix based config files where often a pound # is a comment.

Centos 7 Reallocate logical volume space to another

Do you hate how Centos 7 defaults to allocating most of your valuable space to /home even though it is a production server?

Here is a quick guide on how to take back that space live, while online (of course make sure you have backups just in case something goes wrong!):

First we will reduce our home dir by 100G:

lvreduce -L -100G /dev/mapper/centos-home WARNING: Reducing active and open logical volume to <5.12 GiB. THIS MAY DESTROY YOUR DATA (filesystem etc.) Do you really want to reduce centos/home? [y/n]: y Size of logical volume centos/home changed from <105.12 GiB (26910 extents) to <5.12 GiB (1310 extents). Logical volume centos/home successfully resized.

Now let's give it back to /root:

lvextend -l 100%FREE /dev/centos/root Size of logical volume centos/root changed from 50.00 GiB (12800 extents) to 100.00 GiB (25601 extents). Logical volume centos/root successfully resized.

OK but now what does our filesystem magically know what we did with the LV/logical volume? No

[root@disc livefilesystem]# df -h
Filesystem               Size Used Avail Use% Mounted on
/dev/mapper/centos-root   50G   35G   16G 70% /
devtmpfs                 1.9G     0 1.9G   0% /dev
tmpfs                    1.9G     0 1.9G   0% /dev/shm
tmpfs                    1.9G 8.7M 1.9G   1% /run
tmpfs                    1.9G     0 1.9G   0% /sys/fs/cgroup
/dev/mapper/centos-home 106G   33M 106G   1% /home
/dev/sda1               1014M 176M 839M 18% /boot
tmpfs                    379M     0 379M   0% /run/user/0

Maybe we could just remount it? No

[root@disc livefilesystem]# mount -o remount / [root@disc livefilesystem]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/centos-root 50G 35G 16G 70% /

How do we resize the filesystem? xfs_growfs of course!

xfs_growfs /dev/mapper/centos-root
meta-data=/dev/mapper/centos-root isize=512    agcount=4, agsize=3276800 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=0 spinodes=0
data     =                       bsize=4096   blocks=13107200, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
log      =internal               bsize=4096   blocks=6400, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
data blocks changed from 13107200 to 26215424

Now it's all good!

[root@disc livefilesystem]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/centos-root 100G 35G 66G 35% / devtmpfs 1.9G 0 1.9G 0% /dev tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 1.9G 8.7M 1.9G 1% /run tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mapper/centos-home 106G 33M 106G 1% /home /dev/sda1 1014M 176M 839M 18% /boot tmpfs 379M 0 379M 0% /run/user/0

lvm how to reduce volume size

lvreduce -L -100G /dev/mapper/centos-home

Do you really want to reduce centos/home? [y/n]: y
Size of logical volume centos/home changed from <105.12 GiB (26910 extents) to <5.12 GiB (1310 extents). Logical volume centos/home successfully resized.

Just modify the command above with the -100G to suite how much you want to reduce your volume by.

letsencrypt certbot error "Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80."

./certbot-auto --apache certonly Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator apache, Installer apache No names were found in your configuration files. Please enter in your domain name(s) (comma and/or space separated) (Enter 'c' to cancel): yourdomain.com Obtaining a new certificate Performing the following challenges: http-01 challenge for yourdomain.com Cleaning up challenges Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80.

SSH error cannot Forward or Listen "bind: Cannot assign requested address"

debug1: Local connections to LOCALHOST:18006 forwarded to remote address 192.168.1.93:8006 debug1: Local forwarding listening on 127.0.0.1 port 18006. debug1: channel 0: new [port listener] debug1: Local forwarding listening on ::1 port 18006. bind: Cannot assign requested address

What we are seeing is that we can't listen on an IPV6 address of ::1. We need to tell SSH to stop using IPV6 so we'll edit ssh_config to take care of this issue.
Solution:

sudo vi /etc/ssh/ssh_config

Set this:

Host * AddressFamily inet

Formerly the "inet" would say any which means it would be IPV6 too but we can't have that since it breaks out forwarding!

The "inet" in address family disables IPV6 because we can see in the SSH verbose output earlier that it was trying to listen on ::1 (which is an IPV6 address). This breaks if you don't have IPV6 enabled in your OS which is why we get the message from bind.

X11 SSH Linux Forwarding Error

Jan 30 17:16:10 localhost sshd[25385]: error: Failed to allocate internet-domain X11 display socket.

The solution for me on the server side was the following in sshd_config:

AddressFamily inet

*Remember to restart sshd and also reconnect from the client side.

I had all the normal X11 settings on the server but it just stopped working for me randomly:

X11Forwarding yes X11DisplayOffset 10

I am thinking this is a client side error in the sense that perhaps newer SSH clients cause this bug because things were working fine for months and nothing changed on the server side.

This happened on Linux Mint/Ubuntu/Debian based machines.

Using Microsoft's Group Policy Management Editor (GPME) To Change Default Permissions and Internet Explorer Security Settings

The defaults in Windows 2016 server leave clients crippled so they can't even download basic files or software. But Group Policy Management Editor comes to our rescue!

Use cmd or Powershell and run:

gpme.msc

Choose your domain/computer and then navigate like below and create a new menu entry for IE11 or whatever your version is. Don't be worried if the highest version is IE10 it means that it applies to IE10 AND above.

Make your changes

After that close the GPME and the settings will apply to users once they login again.

Of course you can use GPME for other apps, settings etc.. so customize as you need.

Don't forget to run "gpupdate" on existing clients or they may not get the GP changes you've made (eg. meaning what you did will have no effect on the user).

Thunderbird How To Disable An Email Account

Navigate to Tools -> Account Settings -> Server Settings

Uncheck the following:

"Check for new messages on startup"
"Check for new messages every NN minutes"
"Automatically download new messages".

Source: http://forums.mozillazine.org/viewtopic.php?t=635510

iptables linux firewall recommended rules for public computing

Whether you are at work, at the coffee shop or on the public internet here are some basic but effective rules for iptables that lock things down (eg. no one can SMB or SSH to you or really anything):

# Generated by iptables-save v1.4.21 on Fri Dec 14 14:00:08 2018 *nat :PREROUTING ACCEPT [160:19844] :INPUT ACCEPT [4:357] :OUTPUT ACCEPT [2955:182236] :POSTROUTING ACCEPT [2955:182236] COMMIT # Completed on Fri Dec 14 14:00:08 2018 # Generated by iptables-save v1.4.21 on Fri Dec 14 14:00:08 2018 *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [1284:148262] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -m limit --limit 5/min -j LOG --log-prefix "iptables denied: " -A INPUT -j DROP COMMIT # Completed on Fri Dec 14 14:00:08 2018

LVM How To Create Pool (dynamically allocated and not fully allocated)

The main use I have for this is virtual servers being able to use an LVM volume but not occupying all of the space. It saves time in deploying machines and copying them so you are only copying the space they are using (eg. 5GB / 60GB vs the full 60GB). There are some disadvantages which is mainly the fact that thin pools by their nature allow you to "overallocate" disk space which is that you could use more space than is available on the disk itself and corrupt your data.

So in my opinion it is best to avoid thin pools EXCEPT if you have a testing environment you need to get up quickly or if you REALLY know what you are doing (eg. you are sure the disk space won't be overallocated or you have some other safeguards).

How To Create An LVM Thin Pool

-L = the size of the pool

--thinpool = specifies we are creating a thin pool

vmthinpool = the name of our thinpool

vms = the name of the vg / volume group we are creating it on.

lvcreate -L 500GB --thinpool vmthinpool vms
Using default stripesize 64.00 KiB.
Logical volume "vmthinpool" created.

VMWare Pro Workstation Nic Disconnected and No IP Using NAT

By default VMWare Workstation often doesn't work as we would like.

If you create a VM with a default NAT IP it won't work you will find the NIC is disconnected (even though on the VMWare side it says connected including at Power On).

How To Solve It

1.) Create New VMNet for NAT

Click "Edit" -> "Virtual Network Editor"

Click "Add Network"

Select Network To Add "VMNet1" (or the next available name).

Click on "NAT" under "Network Information"

It should by default enable DHCP and a default range of 192.168.*.*

and hit OK.

2.) Edit your VM and assign it the VMNet you created above.

Linux How To Create A RamDisk

size = the amount of RAM (m for megabytes)

/mnt/ram = the mount location of the ram disk (change to the path you want it mounted to)

mount -t tmpfs -o size=4096m tmpfs /mnt/ram/

Example test in an old server:

You can see that when reading if you don't specify bs1=M the read speeds are several times slower (eg. 450MB/s vs 2.1GB/s)

mount -t tmpfs -o size=4096m tmpfs /mnt/ram/^C root@testserver:~# dd if=/dev/zero of=/mnt/ram/testhere bs=1M count=3000 3000+0 records in 3000+0 records out 3145728000 bytes (3.1 GB, 2.9 GiB) copied, 2.51162 s, 1.3 GB/s root@testserver:~# dd if=/dev/mnt/ram^C root@testserver:~# dd if=/mnt/ram/testhere of=/dev/null 6144000+0 records in 6144000+0 records out 3145728000 bytes (3.1 GB, 2.9 GiB) copied, 6.99788 s, 450 MB/s root@testserver:~# dd if=/mnt/ram/testfile of=/dev/null dd: failed to open '/mnt/ram/testfile': No such file or directory root@testserver:~# dd if=/mnt/ram/testhere testhere root@testserver:~# dd if=/mnt/ram/testhere of=/dev/null 6144000+0 records in 6144000+0 records out 3145728000 bytes (3.1 GB, 2.9 GiB) copied, 6.94865 s, 453 MB/s root@testserver:~# dd if=/mnt/ram/testhere of=/dev/null bs=1M 3000+0 records in 3000+0 records out 3145728000 bytes (3.1 GB, 2.9 GiB) copied, 1.49836 s, 2.1 GB/s

mdadm force resync when resync=PENDING solution

cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md127 : active (auto-read-only) raid10 sdc1[0] sdb1[2] 1953382400 blocks super 1.2 512K chunks 2 far-copies [2/1] [U_] resync=PENDING bitmap: 15/15 pages [60KB], 65536KB chunk

Solution force repair/resync:

echo "repair" > /sys/block/md127/md/sync_action

Proxmox Breaks Storage/LVM Backing If Killing QEMU-IMG

I tried to stop a qemu-img copy or clone and it broke everything. It was fine to "stop" it from the GUI but a process still persisted so I killed the relevant qemu-img and the kernel went crazy. It also may not have helped that I tried to lvremove a different volume (an unused disk). But either way it breaks LVM (you cannot even run lvdisplay) so a reboot is necessary.

Jan 17 06:45:21 testserver kernel: [ 5680.439337] systemd-udevd D 0 9948 469 0x00000104 Jan 17 06:45:21 testserver kernel: [ 5680.439341] Call Trace: Jan 17 06:45:21 testserver kernel: [ 5680.439356] __schedule+0x3e3/0x880 Jan 17 06:45:21 testserver kernel: [ 5680.439363] schedule+0x36/0x80 Jan 17 06:45:21 testserver kernel: [ 5680.439366] schedule_preempt_disabled+0xe/0x10 Jan 17 06:45:21 testserver kernel: [ 5680.439370] __mutex_lock.isra.2+0x2b1/0x4e0 Jan 17 06:45:21 testserver kernel: [ 5680.439374] ? kobj_lookup+0x115/0x160 Jan 17 06:45:21 testserver kernel: [ 5680.439377] __mutex_lock_slowpath+0x13/0x20 Jan 17 06:45:21 testserver kernel: [ 5680.439379] ? _cond_resched+0x1a/0x50 Jan 17 06:45:21 testserver kernel: [ 5680.439382] ? __mutex_lock_slowpath+0x13/0x20 Jan 17 06:45:21 testserver kernel: [ 5680.439384] mutex_lock+0x2f/0x40 Jan 17 06:45:21 testserver kernel: [ 5680.439389] __blkdev_get+0x71/0x4d0 Jan 17 06:45:21 testserver kernel: [ 5680.439391] blkdev_get+0x125/0x310 Jan 17 06:45:21 testserver kernel: [ 5680.439394] blkdev_open+0x92/0x100 Jan 17 06:45:21 testserver kernel: [ 5680.439397] do_dentry_open+0x202/0x310 Jan 17 06:45:21 testserver kernel: [ 5680.439399] ? bd_acquire+0xd0/0xd0 Jan 17 06:45:21 testserver kernel: [ 5680.439401] vfs_open+0x4f/0x80 Jan 17 06:45:21 testserver kernel: [ 5680.439403] path_openat+0x617/0x14a0 Jan 17 06:45:21 testserver kernel: [ 5680.439407] ? page_add_file_rmap+0xf7/0x150 Jan 17 06:45:21 testserver kernel: [ 5680.439411] do_filp_open+0x99/0x110 Jan 17 06:45:21 testserver kernel: [ 5680.439414] ? __check_object_size+0xb3/0x190 Jan 17 06:45:21 testserver kernel: [ 5680.439417] ? __alloc_fd+0x46/0x170 Jan 17 06:45:21 testserver kernel: [ 5680.439420] do_sys_open+0x135/0x280 Jan 17 06:45:21 testserver kernel: [ 5680.439421] ? do_sys_open+0x135/0x280 Jan 17 06:45:21 testserver kernel: [ 5680.439424] SyS_open+0x1e/0x20 Jan 17 06:45:21 testserver kernel: [ 5680.439428] do_syscall_64+0x73/0x130 Jan 17 06:45:21 testserver kernel: [ 5680.439432] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jan 17 06:45:21 testserver kernel: [ 5680.439437] RIP: 0033:0x7f5864f81820 Jan 17 06:45:21 testserver kernel: [ 5680.439439] RSP: 002b:00007ffc4632b0f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002 Jan 17 06:45:21 testserver kernel: [ 5680.439441] RAX: ffffffffffffffda RBX: 000056554f2b5cd0 RCX: 00007f5864f81820 Jan 17 06:45:21 testserver kernel: [ 5680.439443] RDX: 000056554f14bda3 RSI: 0000000000080000 RDI: 000056554f29f370 Jan 17 06:45:21 testserver kernel: [ 5680.439444] RBP: 0000000000000001 R08: 000056554f14bda3 R09: 0000000000000110 Jan 17 06:45:21 testserver kernel: [ 5680.439445] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 Jan 17 06:45:21 testserver kernel: [ 5680.439446] R13: 0000000000000000 R14: 000056554f29eec0 R15: 00000000ffffffff Jan 17 06:45:21 testserver kernel: [ 5680.455730] vgs D 0 9952 1777 0x00000000 Jan 17 06:45:21 testserver kernel: [ 5680.455732] Call Trace: Jan 17 06:45:21 testserver kernel: [ 5680.455736] __schedule+0x3e3/0x880 Jan 17 06:45:21 testserver kernel: [ 5680.455739] ? __switch_to_asm+0x40/0x70 Jan 17 06:45:21 testserver kernel: [ 5680.455741] ? __switch_to_asm+0x34/0x70 Jan 17 06:45:21 testserver kernel: [ 5680.455743] schedule+0x36/0x80 Jan 17 06:45:21 testserver kernel: [ 5680.455746] schedule_preempt_disabled+0xe/0x10 Jan 17 06:45:21 testserver kernel: [ 5680.455751] __mutex_lock.isra.2+0x2b1/0x4e0 Jan 17 06:45:21 testserver kernel: [ 5680.455754] ? kobj_lookup+0x115/0x160 Jan 17 06:45:21 testserver kernel: [ 5680.455757] __mutex_lock_slowpath+0x13/0x20 Jan 17 06:45:21 testserver kernel: [ 5680.455759] ? _cond_resched+0x1a/0x50 Jan 17 06:45:21 testserver kernel: [ 5680.455762] ? __mutex_lock_slowpath+0x13/0x20 Jan 17 06:45:21 testserver kernel: [ 5680.455764] mutex_lock+0x2f/0x40 Jan 17 06:45:21 testserver kernel: [ 5680.455766] __blkdev_get+0x71/0x4d0 Jan 17 06:45:21 testserver kernel: [ 5680.455768] blkdev_get+0x125/0x310 Jan 17 06:45:21 testserver kernel: [ 5680.455771] blkdev_open+0x92/0x100 Jan 17 06:45:21 testserver kernel: [ 5680.455773] do_dentry_open+0x202/0x310 Jan 17 06:45:21 testserver kernel: [ 5680.455774] ? bd_acquire+0xd0/0xd0 Jan 17 06:45:21 testserver kernel: [ 5680.455777] vfs_open+0x4f/0x80 Jan 17 06:45:21 testserver kernel: [ 5680.455778] path_openat+0x617/0x14a0 Jan 17 06:45:21 testserver kernel: [ 5680.455780] ? putname+0x54/0x60 Jan 17 06:45:21 testserver kernel: [ 5680.455782] ? filename_lookup+0xf8/0x1a0 Jan 17 06:45:21 testserver kernel: [ 5680.455785] do_filp_open+0x99/0x110 Jan 17 06:45:21 testserver kernel: [ 5680.455787] ? __check_object_size+0xb3/0x190 Jan 17 06:45:21 testserver kernel: [ 5680.455790] do_sys_open+0x135/0x280 Jan 17 06:45:21 testserver kernel: [ 5680.455792] ? do_sys_open+0x135/0x280 Jan 17 06:45:21 testserver kernel: [ 5680.455794] SyS_open+0x1e/0x20 Jan 17 06:45:21 testserver kernel: [ 5680.455796] do_syscall_64+0x73/0x130 Jan 17 06:45:21 testserver kernel: [ 5680.455799] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jan 17 06:45:21 testserver kernel: [ 5680.455800] RIP: 0033:0x7f09f35c44b0 Jan 17 06:45:21 testserver kernel: [ 5680.455801] RSP: 002b:00007ffcaf62bd98 EFLAGS: 00000246 ORIG_RAX: 0000000000000002 Jan 17 06:45:21 testserver kernel: [ 5680.455803] RAX: ffffffffffffffda RBX: 0000000000044000 RCX: 00007f09f35c44b0 Jan 17 06:45:21 testserver kernel: [ 5680.455805] RDX: 00000000000001ff RSI: 0000000000044000 RDI: 000056513f681440 Jan 17 06:45:21 testserver kernel: [ 5680.455806] RBP: 0000000000000000 R08: 000056513f6d48a0 R09: 00007ffcaf62bd00 Jan 17 06:45:21 testserver kernel: [ 5680.455807] R10: 00007f09f356a6a0 R11: 0000000000000246 R12: 0000000000000001 Jan 17 06:45:21 testserver kernel: [ 5680.455808] R13: 000056513f681440 R14: 0000000000000000 R15: 000056513f681218 Jan 17 06:45:21 testserver kernel: [ 5680.472311] lvremove D 0 9963 3981 0x00000000 Jan 17 06:45:21 testserver kernel: [ 5680.472313] Call Trace: Jan 17 06:45:21 testserver kernel: [ 5680.472317] __schedule+0x3e3/0x880 Jan 17 06:45:21 testserver kernel: [ 5680.472328] ? __switch_to_asm+0x40/0x70 Jan 17 06:45:21 testserver kernel: [ 5680.472332] ? __switch_to_asm+0x34/0x70 Jan 17 06:45:21 testserver kernel: [ 5680.472338] schedule+0x36/0x80 Jan 17 06:45:21 testserver kernel: [ 5680.472340] schedule_preempt_disabled+0xe/0x10 Jan 17 06:45:21 testserver kernel: [ 5680.472343] __mutex_lock.isra.2+0x2b1/0x4e0 Jan 17 06:45:21 testserver kernel: [ 5680.472346] ? kobj_lookup+0x115/0x160 Jan 17 06:45:21 testserver kernel: [ 5680.472349] __mutex_lock_slowpath+0x13/0x20 Jan 17 06:45:21 testserver kernel: [ 5680.472351] ? _cond_resched+0x1a/0x50 Jan 17 06:45:21 testserver kernel: [ 5680.472353] ? __mutex_lock_slowpath+0x13/0x20 Jan 17 06:45:21 testserver kernel: [ 5680.472355] mutex_lock+0x2f/0x40 Jan 17 06:45:21 testserver kernel: [ 5680.472358] __blkdev_get+0x71/0x4d0 Jan 17 06:45:21 testserver kernel: [ 5680.472360] blkdev_get+0x125/0x310 Jan 17 06:45:21 testserver kernel: [ 5680.472363] blkdev_open+0x92/0x100 Jan 17 06:45:21 testserver kernel: [ 5680.472364] do_dentry_open+0x202/0x310 Jan 17 06:45:21 testserver kernel: [ 5680.472366] ? bd_acquire+0xd0/0xd0 Jan 17 06:45:21 testserver kernel: [ 5680.472372] vfs_open+0x4f/0x80 Jan 17 06:45:21 testserver kernel: [ 5680.472379] path_openat+0x617/0x14a0 Jan 17 06:45:21 testserver kernel: [ 5680.472385] ? putname+0x54/0x60 Jan 17 06:45:21 testserver kernel: [ 5680.472392] ? filename_lookup+0xf8/0x1a0 Jan 17 06:45:21 testserver kernel: [ 5680.472399] do_filp_open+0x99/0x110 Jan 17 06:45:21 testserver kernel: [ 5680.472406] ? __check_object_size+0xb3/0x190 Jan 17 06:45:21 testserver kernel: [ 5680.472415] do_sys_open+0x135/0x280 Jan 17 06:45:21 testserver kernel: [ 5680.472417] ? do_sys_open+0x135/0x280 Jan 17 06:45:21 testserver kernel: [ 5680.472419] SyS_open+0x1e/0x20 Jan 17 06:45:21 testserver kernel: [ 5680.472421] do_syscall_64+0x73/0x130 Jan 17 06:45:21 testserver kernel: [ 5680.472423] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jan 17 06:45:21 testserver kernel: [ 5680.472425] RIP: 0033:0x7f6d01eeb4b0 Jan 17 06:45:21 testserver kernel: [ 5680.472426] RSP: 002b:00007fff72ab50a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002 Jan 17 06:45:21 testserver kernel: [ 5680.472428] RAX: ffffffffffffffda RBX: 0000000000044000 RCX: 00007f6d01eeb4b0 Jan 17 06:45:21 testserver kernel: [ 5680.472429] RDX: 00000000000001ff RSI: 0000000000044000 RDI: 000055736d459640 Jan 17 06:45:21 testserver kernel: [ 5680.472430] RBP: 0000000000000000 R08: 000055736d4863e0 R09: 00007fff72ab5000 Jan 17 06:45:21 testserver kernel: [ 5680.472431] R10: 00007f6d01e916a0 R11: 0000000000000246 R12: 0000000000000001 Jan 17 06:45:21 testserver kernel: [ 5680.472432] R13: 000055736d459640 R14: 0000000000000000 R15: 000055736d459418 Jan 17 06:45:21 testserver kernel: [ 5680.488832] vgs D 0 9977 9974 0x00000000 Jan 17 06:45:21 testserver kernel: [ 5680.488834] Call Trace: Jan 17 06:45:21 testserver kernel: [ 5680.488837] __schedule+0x3e3/0x880 Jan 17 06:45:21 testserver kernel: [ 5680.488840] ? __switch_to_asm+0x40/0x70 Jan 17 06:45:21 testserver kernel: [ 5680.488842] ? __switch_to_asm+0x34/0x70 Jan 17 06:45:21 testserver kernel: [ 5680.488844] schedule+0x36/0x80 Jan 17 06:45:21 testserver kernel: [ 5680.488847] schedule_preempt_disabled+0xe/0x10 Jan 17 06:45:21 testserver kernel: [ 5680.488849] __mutex_lock.isra.2+0x2b1/0x4e0 Jan 17 06:45:21 testserver kernel: [ 5680.488856] ? kobj_lookup+0x115/0x160 Jan 17 06:45:21 testserver kernel: [ 5680.488858] __mutex_lock_slowpath+0x13/0x20 Jan 17 06:45:21 testserver kernel: [ 5680.488861] ? _cond_resched+0x1a/0x50 Jan 17 06:45:21 testserver kernel: [ 5680.488863] ? __mutex_lock_slowpath+0x13/0x20 Jan 17 06:45:21 testserver kernel: [ 5680.488865] mutex_lock+0x2f/0x40 Jan 17 06:45:21 testserver kernel: [ 5680.488867] __blkdev_get+0x71/0x4d0 Jan 17 06:45:21 testserver kernel: [ 5680.488870] blkdev_get+0x125/0x310 Jan 17 06:45:21 testserver kernel: [ 5680.488872] blkdev_open+0x92/0x100 Jan 17 06:45:21 testserver kernel: [ 5680.488874] do_dentry_open+0x202/0x310 Jan 17 06:45:21 testserver kernel: [ 5680.488876] ? bd_acquire+0xd0/0xd0 Jan 17 06:45:21 testserver kernel: [ 5680.488878] vfs_open+0x4f/0x80 Jan 17 06:45:21 testserver kernel: [ 5680.488879] path_openat+0x617/0x14a0 Jan 17 06:45:21 testserver kernel: [ 5680.488881] ? putname+0x54/0x60 Jan 17 06:45:21 testserver kernel: [ 5680.488883] ? filename_lookup+0xf8/0x1a0 Jan 17 06:45:21 testserver kernel: [ 5680.488885] do_filp_open+0x99/0x110 Jan 17 06:45:21 testserver kernel: [ 5680.488888] ? __check_object_size+0xb3/0x190 Jan 17 06:45:21 testserver kernel: [ 5680.488891] do_sys_open+0x135/0x280 Jan 17 06:45:21 testserver kernel: [ 5680.488893] ? do_sys_open+0x135/0x280 Jan 17 06:45:21 testserver kernel: [ 5680.488895] SyS_open+0x1e/0x20 Jan 17 06:45:21 testserver kernel: [ 5680.488897] do_syscall_64+0x73/0x130 Jan 17 06:45:21 testserver kernel: [ 5680.488899] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jan 17 06:45:21 testserver kernel: [ 5680.488901] RIP: 0033:0x7f98ef2644b0 Jan 17 06:45:21 testserver kernel: [ 5680.488902] RSP: 002b:00007ffc7ee8f7e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002 Jan 17 06:45:21 testserver kernel: [ 5680.488904] RAX: ffffffffffffffda RBX: 0000000000044000 RCX: 00007f98ef2644b0 Jan 17 06:45:21 testserver kernel: [ 5680.488905] RDX: 00000000000001ff RSI: 0000000000044000 RDI: 000055e16b9ee440 Jan 17 06:45:21 testserver kernel: [ 5680.488906] RBP: 0000000000000000 R08: 000055e16ba34d20 R09: 00007ffc7ee8f800 Jan 17 06:45:21 testserver kernel: [ 5680.488907] R10: 00007f98ef20a6a0 R11: 0000000000000246 R12: 0000000000000001 Jan 17 06:45:21 testserver kernel: [ 5680.488908] R13: 000055e16b9ee440 R14: 0000000000000000 R15: 000055e16b9ee218 Jan 17 06:47:22 testserver kernel: [ 5801.279621] systemd-udevd D 0 9948 469 0x00000104 Jan 17 06:47:22 testserver kernel: [ 5801.279625] Call Trace: Jan 17 06:47:22 testserver kernel: [ 5801.279640] __schedule+0x3e3/0x880 Jan 17 06:47:22 testserver kernel: [ 5801.279647] schedule+0x36/0x80 Jan 17 06:47:22 testserver kernel: [ 5801.279650] schedule_preempt_disabled+0xe/0x10 Jan 17 06:47:22 testserver kernel: [ 5801.279654] __mutex_lock.isra.2+0x2b1/0x4e0 Jan 17 06:47:22 testserver kernel: [ 5801.279658] ? kobj_lookup+0x115/0x160 Jan 17 06:47:22 testserver kernel: [ 5801.279661] __mutex_lock_slowpath+0x13/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.279664] ? _cond_resched+0x1a/0x50 Jan 17 06:47:22 testserver kernel: [ 5801.279666] ? __mutex_lock_slowpath+0x13/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.279668] mutex_lock+0x2f/0x40 Jan 17 06:47:22 testserver kernel: [ 5801.279673] __blkdev_get+0x71/0x4d0 Jan 17 06:47:22 testserver kernel: [ 5801.279675] blkdev_get+0x125/0x310 Jan 17 06:47:22 testserver kernel: [ 5801.279678] blkdev_open+0x92/0x100 Jan 17 06:47:22 testserver kernel: [ 5801.279681] do_dentry_open+0x202/0x310 Jan 17 06:47:22 testserver kernel: [ 5801.279682] ? bd_acquire+0xd0/0xd0 Jan 17 06:47:22 testserver kernel: [ 5801.279685] vfs_open+0x4f/0x80 Jan 17 06:47:22 testserver kernel: [ 5801.279687] path_openat+0x617/0x14a0 Jan 17 06:47:22 testserver kernel: [ 5801.279691] ? page_add_file_rmap+0xf7/0x150 Jan 17 06:47:22 testserver kernel: [ 5801.279695] do_filp_open+0x99/0x110 Jan 17 06:47:22 testserver kernel: [ 5801.279698] ? __check_object_size+0xb3/0x190 Jan 17 06:47:22 testserver kernel: [ 5801.279701] ? __alloc_fd+0x46/0x170 Jan 17 06:47:22 testserver kernel: [ 5801.279703] do_sys_open+0x135/0x280 Jan 17 06:47:22 testserver kernel: [ 5801.279705] ? do_sys_open+0x135/0x280 Jan 17 06:47:22 testserver kernel: [ 5801.279708] SyS_open+0x1e/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.279711] do_syscall_64+0x73/0x130 Jan 17 06:47:22 testserver kernel: [ 5801.279716] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jan 17 06:47:22 testserver kernel: [ 5801.279721] RIP: 0033:0x7f5864f81820 Jan 17 06:47:22 testserver kernel: [ 5801.279723] RSP: 002b:00007ffc4632b0f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002 Jan 17 06:47:22 testserver kernel: [ 5801.279725] RAX: ffffffffffffffda RBX: 000056554f2b5cd0 RCX: 00007f5864f81820 Jan 17 06:47:22 testserver kernel: [ 5801.279727] RDX: 000056554f14bda3 RSI: 0000000000080000 RDI: 000056554f29f370 Jan 17 06:47:22 testserver kernel: [ 5801.279728] RBP: 0000000000000001 R08: 000056554f14bda3 R09: 0000000000000110 Jan 17 06:47:22 testserver kernel: [ 5801.279729] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 Jan 17 06:47:22 testserver kernel: [ 5801.279730] R13: 0000000000000000 R14: 000056554f29eec0 R15: 00000000ffffffff Jan 17 06:47:22 testserver kernel: [ 5801.297280] vgs D 0 9952 1777 0x00000000 Jan 17 06:47:22 testserver kernel: [ 5801.297283] Call Trace: Jan 17 06:47:22 testserver kernel: [ 5801.297286] __schedule+0x3e3/0x880 Jan 17 06:47:22 testserver kernel: [ 5801.297297] ? __switch_to_asm+0x40/0x70 Jan 17 06:47:22 testserver kernel: [ 5801.297303] ? __switch_to_asm+0x34/0x70 Jan 17 06:47:22 testserver kernel: [ 5801.297309] schedule+0x36/0x80 Jan 17 06:47:22 testserver kernel: [ 5801.297312] schedule_preempt_disabled+0xe/0x10 Jan 17 06:47:22 testserver kernel: [ 5801.297314] __mutex_lock.isra.2+0x2b1/0x4e0 Jan 17 06:47:22 testserver kernel: [ 5801.297317] ? kobj_lookup+0x115/0x160 Jan 17 06:47:22 testserver kernel: [ 5801.297320] __mutex_lock_slowpath+0x13/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.297322] ? _cond_resched+0x1a/0x50 Jan 17 06:47:22 testserver kernel: [ 5801.297324] ? __mutex_lock_slowpath+0x13/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.297327] mutex_lock+0x2f/0x40 Jan 17 06:47:22 testserver kernel: [ 5801.297329] __blkdev_get+0x71/0x4d0 Jan 17 06:47:22 testserver kernel: [ 5801.297336] blkdev_get+0x125/0x310 Jan 17 06:47:22 testserver kernel: [ 5801.297338] blkdev_open+0x92/0x100 Jan 17 06:47:22 testserver kernel: [ 5801.297340] do_dentry_open+0x202/0x310 Jan 17 06:47:22 testserver kernel: [ 5801.297342] ? bd_acquire+0xd0/0xd0 Jan 17 06:47:22 testserver kernel: [ 5801.297344] vfs_open+0x4f/0x80 Jan 17 06:47:22 testserver kernel: [ 5801.297348] path_openat+0x617/0x14a0 Jan 17 06:47:22 testserver kernel: [ 5801.297354] ? putname+0x54/0x60 Jan 17 06:47:22 testserver kernel: [ 5801.297361] ? filename_lookup+0xf8/0x1a0 Jan 17 06:47:22 testserver kernel: [ 5801.297368] do_filp_open+0x99/0x110 Jan 17 06:47:22 testserver kernel: [ 5801.297375] ? __check_object_size+0xb3/0x190 Jan 17 06:47:22 testserver kernel: [ 5801.297385] do_sys_open+0x135/0x280 Jan 17 06:47:22 testserver kernel: [ 5801.297392] ? do_sys_open+0x135/0x280 Jan 17 06:47:22 testserver kernel: [ 5801.297399] SyS_open+0x1e/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.297404] do_syscall_64+0x73/0x130 Jan 17 06:47:22 testserver kernel: [ 5801.297406] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jan 17 06:47:22 testserver kernel: [ 5801.297407] RIP: 0033:0x7f09f35c44b0 Jan 17 06:47:22 testserver kernel: [ 5801.297409] RSP: 002b:00007ffcaf62bd98 EFLAGS: 00000246 ORIG_RAX: 0000000000000002 Jan 17 06:47:22 testserver kernel: [ 5801.297411] RAX: ffffffffffffffda RBX: 0000000000044000 RCX: 00007f09f35c44b0 Jan 17 06:47:22 testserver kernel: [ 5801.297412] RDX: 00000000000001ff RSI: 0000000000044000 RDI: 000056513f681440 Jan 17 06:47:22 testserver kernel: [ 5801.297413] RBP: 0000000000000000 R08: 000056513f6d48a0 R09: 00007ffcaf62bd00 Jan 17 06:47:22 testserver kernel: [ 5801.297414] R10: 00007f09f356a6a0 R11: 0000000000000246 R12: 0000000000000001 Jan 17 06:47:22 testserver kernel: [ 5801.297416] R13: 000056513f681440 R14: 0000000000000000 R15: 000056513f681218 Jan 17 06:47:22 testserver kernel: [ 5801.315415] lvremove D 0 9963 3981 0x00000000 Jan 17 06:47:22 testserver kernel: [ 5801.315417] Call Trace: Jan 17 06:47:22 testserver kernel: [ 5801.315426] __schedule+0x3e3/0x880 Jan 17 06:47:22 testserver kernel: [ 5801.315431] ? __switch_to_asm+0x40/0x70 Jan 17 06:47:22 testserver kernel: [ 5801.315433] ? __switch_to_asm+0x34/0x70 Jan 17 06:47:22 testserver kernel: [ 5801.315438] schedule+0x36/0x80 Jan 17 06:47:22 testserver kernel: [ 5801.315441] schedule_preempt_disabled+0xe/0x10 Jan 17 06:47:22 testserver kernel: [ 5801.315443] __mutex_lock.isra.2+0x2b1/0x4e0 Jan 17 06:47:22 testserver kernel: [ 5801.315446] ? kobj_lookup+0x115/0x160 Jan 17 06:47:22 testserver kernel: [ 5801.315448] __mutex_lock_slowpath+0x13/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.315451] ? _cond_resched+0x1a/0x50 Jan 17 06:47:22 testserver kernel: [ 5801.315453] ? __mutex_lock_slowpath+0x13/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.315455] mutex_lock+0x2f/0x40 Jan 17 06:47:22 testserver kernel: [ 5801.315458] __blkdev_get+0x71/0x4d0 Jan 17 06:47:22 testserver kernel: [ 5801.315460] blkdev_get+0x125/0x310 Jan 17 06:47:22 testserver kernel: [ 5801.315462] blkdev_open+0x92/0x100 Jan 17 06:47:22 testserver kernel: [ 5801.315464] do_dentry_open+0x202/0x310 Jan 17 06:47:22 testserver kernel: [ 5801.315466] ? bd_acquire+0xd0/0xd0 Jan 17 06:47:22 testserver kernel: [ 5801.315468] vfs_open+0x4f/0x80 Jan 17 06:47:22 testserver kernel: [ 5801.315475] path_openat+0x617/0x14a0 Jan 17 06:47:22 testserver kernel: [ 5801.315481] ? putname+0x54/0x60 Jan 17 06:47:22 testserver kernel: [ 5801.315486] ? filename_lookup+0xf8/0x1a0 Jan 17 06:47:22 testserver kernel: [ 5801.315493] do_filp_open+0x99/0x110 Jan 17 06:47:22 testserver kernel: [ 5801.315499] ? __check_object_size+0xb3/0x190 Jan 17 06:47:22 testserver kernel: [ 5801.315510] do_sys_open+0x135/0x280 Jan 17 06:47:22 testserver kernel: [ 5801.315518] ? do_sys_open+0x135/0x280 Jan 17 06:47:22 testserver kernel: [ 5801.315525] SyS_open+0x1e/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.315527] do_syscall_64+0x73/0x130 Jan 17 06:47:22 testserver kernel: [ 5801.315529] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jan 17 06:47:22 testserver kernel: [ 5801.315530] RIP: 0033:0x7f6d01eeb4b0 Jan 17 06:47:22 testserver kernel: [ 5801.315531] RSP: 002b:00007fff72ab50a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002 Jan 17 06:47:22 testserver kernel: [ 5801.315533] RAX: ffffffffffffffda RBX: 0000000000044000 RCX: 00007f6d01eeb4b0 Jan 17 06:47:22 testserver kernel: [ 5801.315534] RDX: 00000000000001ff RSI: 0000000000044000 RDI: 000055736d459640 Jan 17 06:47:22 testserver kernel: [ 5801.315535] RBP: 0000000000000000 R08: 000055736d4863e0 R09: 00007fff72ab5000 Jan 17 06:47:22 testserver kernel: [ 5801.315536] R10: 00007f6d01e916a0 R11: 0000000000000246 R12: 0000000000000001 Jan 17 06:47:22 testserver kernel: [ 5801.315538] R13: 000055736d459640 R14: 0000000000000000 R15: 000055736d459418 Jan 17 06:47:22 testserver kernel: [ 5801.333864] vgs D 0 9977 9974 0x00000000 Jan 17 06:47:22 testserver kernel: [ 5801.333866] Call Trace: Jan 17 06:47:22 testserver kernel: [ 5801.333870] __schedule+0x3e3/0x880 Jan 17 06:47:22 testserver kernel: [ 5801.333880] ? __switch_to_asm+0x40/0x70 Jan 17 06:47:22 testserver kernel: [ 5801.333885] ? __switch_to_asm+0x34/0x70 Jan 17 06:47:22 testserver kernel: [ 5801.333887] schedule+0x36/0x80 Jan 17 06:47:22 testserver kernel: [ 5801.333893] schedule_preempt_disabled+0xe/0x10 Jan 17 06:47:22 testserver kernel: [ 5801.333895] __mutex_lock.isra.2+0x2b1/0x4e0 Jan 17 06:47:22 testserver kernel: [ 5801.333898] ? kobj_lookup+0x115/0x160 Jan 17 06:47:22 testserver kernel: [ 5801.333901] __mutex_lock_slowpath+0x13/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.333903] ? _cond_resched+0x1a/0x50 Jan 17 06:47:22 testserver kernel: [ 5801.333905] ? __mutex_lock_slowpath+0x13/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.333908] mutex_lock+0x2f/0x40 Jan 17 06:47:22 testserver kernel: [ 5801.333910] __blkdev_get+0x71/0x4d0 Jan 17 06:47:22 testserver kernel: [ 5801.333912] blkdev_get+0x125/0x310 Jan 17 06:47:22 testserver kernel: [ 5801.333914] blkdev_open+0x92/0x100 Jan 17 06:47:22 testserver kernel: [ 5801.333916] do_dentry_open+0x202/0x310 Jan 17 06:47:22 testserver kernel: [ 5801.333918] ? bd_acquire+0xd0/0xd0 Jan 17 06:47:22 testserver kernel: [ 5801.333920] vfs_open+0x4f/0x80 Jan 17 06:47:22 testserver kernel: [ 5801.333922] path_openat+0x617/0x14a0 Jan 17 06:47:22 testserver kernel: [ 5801.333929] ? putname+0x54/0x60 Jan 17 06:47:22 testserver kernel: [ 5801.333936] ? filename_lookup+0xf8/0x1a0 Jan 17 06:47:22 testserver kernel: [ 5801.333943] do_filp_open+0x99/0x110 Jan 17 06:47:22 testserver kernel: [ 5801.333950] ? __check_object_size+0xb3/0x190 Jan 17 06:47:22 testserver kernel: [ 5801.333959] do_sys_open+0x135/0x280 Jan 17 06:47:22 testserver kernel: [ 5801.333968] ? do_sys_open+0x135/0x280 Jan 17 06:47:22 testserver kernel: [ 5801.333975] SyS_open+0x1e/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.333977] do_syscall_64+0x73/0x130 Jan 17 06:47:22 testserver kernel: [ 5801.333979] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jan 17 06:47:22 testserver kernel: [ 5801.333980] RIP: 0033:0x7f98ef2644b0 Jan 17 06:47:22 testserver kernel: [ 5801.333981] RSP: 002b:00007ffc7ee8f7e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002 Jan 17 06:47:22 testserver kernel: [ 5801.333983] RAX: ffffffffffffffda RBX: 0000000000044000 RCX: 00007f98ef2644b0 Jan 17 06:47:22 testserver kernel: [ 5801.333984] RDX: 00000000000001ff RSI: 0000000000044000 RDI: 000055e16b9ee440 Jan 17 06:47:22 testserver kernel: [ 5801.333985] RBP: 0000000000000000 R08: 000055e16ba34d20 R09: 00007ffc7ee8f800 Jan 17 06:47:22 testserver kernel: [ 5801.333986] R10: 00007f98ef20a6a0 R11: 0000000000000246 R12: 0000000000000001 Jan 17 06:47:22 testserver kernel: [ 5801.333988] R13: 000055e16b9ee440 R14: 0000000000000000 R15: 000055e16b9ee218 Jan 17 06:47:22 testserver kernel: [ 5801.352691] vgs D 0 10058 1 0x00000004 Jan 17 06:47:22 testserver kernel: [ 5801.352693] Call Trace: Jan 17 06:47:22 testserver kernel: [ 5801.352704] __schedule+0x3e3/0x880 Jan 17 06:47:22 testserver kernel: [ 5801.352706] ? __switch_to_asm+0x40/0x70 Jan 17 06:47:22 testserver kernel: [ 5801.352707] ? __switch_to_asm+0x34/0x70 Jan 17 06:47:22 testserver kernel: [ 5801.352710] schedule+0x36/0x80 Jan 17 06:47:22 testserver kernel: [ 5801.352715] schedule_preempt_disabled+0xe/0x10 Jan 17 06:47:22 testserver kernel: [ 5801.352718] __mutex_lock.isra.2+0x2b1/0x4e0 Jan 17 06:47:22 testserver kernel: [ 5801.352720] ? kobj_lookup+0x115/0x160 Jan 17 06:47:22 testserver kernel: [ 5801.352723] __mutex_lock_slowpath+0x13/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.352725] ? _cond_resched+0x1a/0x50 Jan 17 06:47:22 testserver kernel: [ 5801.352727] ? __mutex_lock_slowpath+0x13/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.352730] mutex_lock+0x2f/0x40 Jan 17 06:47:22 testserver kernel: [ 5801.352738] __blkdev_get+0x71/0x4d0 Jan 17 06:47:22 testserver kernel: [ 5801.352744] blkdev_get+0x125/0x310 Jan 17 06:47:22 testserver kernel: [ 5801.352751] blkdev_open+0x92/0x100 Jan 17 06:47:22 testserver kernel: [ 5801.352756] do_dentry_open+0x202/0x310 Jan 17 06:47:22 testserver kernel: [ 5801.352762] ? bd_acquire+0xd0/0xd0 Jan 17 06:47:22 testserver kernel: [ 5801.352769] vfs_open+0x4f/0x80 Jan 17 06:47:22 testserver kernel: [ 5801.352774] path_openat+0x617/0x14a0 Jan 17 06:47:22 testserver kernel: [ 5801.352775] ? putname+0x54/0x60 Jan 17 06:47:22 testserver kernel: [ 5801.352777] ? filename_lookup+0xf8/0x1a0 Jan 17 06:47:22 testserver kernel: [ 5801.352780] do_filp_open+0x99/0x110 Jan 17 06:47:22 testserver kernel: [ 5801.352783] ? __check_object_size+0xb3/0x190 Jan 17 06:47:22 testserver kernel: [ 5801.352785] do_sys_open+0x135/0x280 Jan 17 06:47:22 testserver kernel: [ 5801.352788] ? do_sys_open+0x135/0x280 Jan 17 06:47:22 testserver kernel: [ 5801.352792] SyS_open+0x1e/0x20 Jan 17 06:47:22 testserver kernel: [ 5801.352794] do_syscall_64+0x73/0x130 Jan 17 06:47:22 testserver kernel: [ 5801.352796] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jan 17 06:47:22 testserver kernel: [ 5801.352798] RIP: 0033:0x7f73752144b0 Jan 17 06:47:22 testserver kernel: [ 5801.352799] RSP: 002b:00007ffe643df188 EFLAGS: 00000246 ORIG_RAX: 0000000000000002 Jan 17 06:47:22 testserver kernel: [ 5801.352801] RAX: ffffffffffffffda RBX: 0000000000044000 RCX: 00007f73752144b0 Jan 17 06:47:22 testserver kernel: [ 5801.352802] RDX: 00000000000001ff RSI: 0000000000044000 RDI: 00005592cd22f440 Jan 17 06:47:22 testserver kernel: [ 5801.352803] RBP: 0000000000000000 R08: 00005592cd27af20 R09: 00007ffe643df100 Jan 17 06:47:22 testserver kernel: [ 5801.352804] R10: 00007f73751ba6a0 R11: 0000000000000246 R12: 0000000000000001 Jan 17 06:47:22 testserver kernel: [ 5801.352805] R13: 00005592cd22f440 R14: 0000000000000000 R15: 00005592cd22f218 Jan 17 06:48:27 testserver pvedaemon[7787]: <root@pam> starting task UPID:testserver:0000285C:0008F35F:5C3FB4BB:qmstart:102:root@pam: Jan 17 06:48:56 testserver pvedaemon[7128]: <root@pam> successful auth for user 'root@pam' Jan 17 06:49:23 testserver kernel: [ 5922.120683] systemd-udevd D 0 9948 469 0x00000104 Jan 17 06:49:23 testserver kernel: [ 5922.120690] Call Trace: Jan 17 06:49:23 testserver kernel: [ 5922.120709] __schedule+0x3e3/0x880 Jan 17 06:49:23 testserver kernel: [ 5922.120716] schedule+0x36/0x80 Jan 17 06:49:23 testserver kernel: [ 5922.120725] schedule_preempt_disabled+0xe/0x10 Jan 17 06:49:23 testserver kernel: [ 5922.120728] __mutex_lock.isra.2+0x2b1/0x4e0 Jan 17 06:49:23 testserver kernel: [ 5922.120733] ? kobj_lookup+0x115/0x160 Jan 17 06:49:23 testserver kernel: [ 5922.120741] __mutex_lock_slowpath+0x13/0x20 Jan 17 06:49:23 testserver kernel: [ 5922.120748] ? _cond_resched+0x1a/0x50 Jan 17 06:49:23 testserver kernel: [ 5922.120753] ? __mutex_lock_slowpath+0x13/0x20 Jan 17 06:49:23 testserver kernel: [ 5922.120755] mutex_lock+0x2f/0x40 Jan 17 06:49:23 testserver kernel: [ 5922.120761] __blkdev_get+0x71/0x4d0 Jan 17 06:49:23 testserver kernel: [ 5922.120763] blkdev_get+0x125/0x310 Jan 17 06:49:23 testserver kernel: [ 5922.120765] blkdev_open+0x92/0x100 Jan 17 06:49:23 testserver kernel: [ 5922.120769] do_dentry_open+0x202/0x310 Jan 17 06:49:23 testserver kernel: [ 5922.120770] ? bd_acquire+0xd0/0xd0 Jan 17 06:49:23 testserver kernel: [ 5922.120772] vfs_open+0x4f/0x80 Jan 17 06:49:23 testserver kernel: [ 5922.120775] path_openat+0x617/0x14a0 Jan 17 06:49:23 testserver kernel: [ 5922.120779] ? page_add_file_rmap+0xf7/0x150 Jan 17 06:49:23 testserver kernel: [ 5922.120788] do_filp_open+0x99/0x110 Jan 17 06:49:23 testserver kernel: [ 5922.120795] ? __check_object_size+0xb3/0x190 Jan 17 06:49:23 testserver kernel: [ 5922.120802] ? __alloc_fd+0x46/0x170 Jan 17 06:49:23 testserver kernel: [ 5922.120810] do_sys_open+0x135/0x280 Jan 17 06:49:23 testserver kernel: [ 5922.120818] ? do_sys_open+0x135/0x280 Jan 17 06:49:23 testserver kernel: [ 5922.120821] SyS_open+0x1e/0x20 Jan 17 06:49:23 testserver kernel: [ 5922.120825] do_syscall_64+0x73/0x130 Jan 17 06:49:23 testserver kernel: [ 5922.120829] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jan 17 06:49:23 testserver kernel: [ 5922.120832] RIP: 0033:0x7f5864f81820 Jan 17 06:49:23 testserver kernel: [ 5922.120834] RSP: 002b:00007ffc4632b0f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002 Jan 17 06:49:23 testserver kernel: [ 5922.120837] RAX: ffffffffffffffda RBX: 000056554f2b5cd0 RCX: 00007f5864f81820 Jan 17 06:49:23 testserver kernel: [ 5922.120838] RDX: 000056554f14bda3 RSI: 0000000000080000 RDI: 000056554f29f370 Jan 17 06:49:23 testserver kernel: [ 5922.120839] RBP: 0000000000000001 R08: 000056554f14bda3 R09: 0000000000000110 Jan 17 06:49:23 testserver kernel: [ 5922.120840] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 Jan 17 06:49:23 testserver kernel: [ 5922.120841] R13: 0000000000000000 R14: 000056554f29eec0 R15: 00000000ffffffff

Proxmox trying to acquire lock... TASK ERROR: can't lock file '/var/lock/qemu-server/lock-102.conf' - got timeout

If Proxmox won't start aVM with an error like this:

trying to acquire lock... TASK ERROR: can't lock file '/var/lock/qemu-server/lock-102.conf' - got timeout

rm /var/lock/qemu-server/lock-102.conf

Then try to restart the VM and it should be good.

Debian 9 SSH root password authentication failure password not working problem / solution

In Debian a lot of times SSH disables the root user to login by password by default. This means you will get an authentication failure as if you typed in the wrong password.

The logs also indicate the password is wrong but what is often the case is in the config file

Check /etc/ssh/sshd_config

cat /etc/ssh/sshd_config|grep -i permitrootlogin

Make sure it says:

PermitRootLogin yes

If not change it and restart SSH and it will work again.

QEMU / KVM How To Manually Create Basic Virtual Machine VM

1.) Create Image using qemu-img

qemu-img create -f qcow2 skype.img 40G

2.) Start VM using flags

-m = memory in MB

-drive file=yourimagefile.img

-cdrom /path/to/the.iso

qemu-system-x86_64 -m 4096 -drive file=skype.img -cdrom ~/Downloads/SfB-E-9319.0-enUS.ISO

Enable Bridged Networking

First of all you need a bridged NIC, see this post on how to do that.

If you get this message it basically / usually means you have no networking eg. no NIC or it is not connected to anything.

qemu-system-x86_64: warning: vlan 0 is not connected to host network

Take the same qemu-system command from earlier one and add this:

The below assumes you have a bridged tap adapter called "tap2019". You will also need to bring the tap adapter up:

ip link set dev tap2019 up

qemu-system-x86_64 -m 4096 -drive file=skype.img -cdrom ~/Downloads/SfB-E-9319.0-enUS.ISO -net nic,model=virtio -net tap,ifname=tap2019,script=no,downscript=no

You can change the model=virtio to something else like Intel's e1000. The ifname=tap2019 is obviously going to be set to the tap device you have.

Nice Script To Tie Basic QEMU-KVM Usage Together:

tapdev=`tunctl -b`macaddr=`openssl rand -hex 6 | sed 's/(..)(..)(..)(..)(..)(..)/1:2:3:4:5:6/'` iso=/mnt/vms/iso/linuxmint-19.1-mate-64bit.iso drive="-drive somefile.img,if=virtio" ram=4096 cores=8 qemubin="/usr/libexec/qemu-kvm" vncport=5 cdrom="-cdrom $iso" $qemubin -smp $cores $cdrom -boot once=d -vnc :$vncport -m $ram $drive -net nic,macaddr=$macaddr,model=virtio -net tap,ifname=$tapdev,script=no,downscript=no& ifconfig $tapdev up #or #brctl addif br0 $tapdev

# proxy arp only needed if you are not using a bridge

# if not using a bridge you need proxy_arp AND you need to do add the route of the VMs IP to the tapdev eg. ip route add 10.10.25.20 dev tap20194 echo 1 > /proc/sys/net/ipv4/conf/$tapdev/proxy_arp

tapdev= name of your tap device

tunctl -t $tapdev creates this device

iso= path of your iso

ram= ram in megabytes

cores=8 how many SMP/processors the VM gets

qemubin= the path to your qemu binary

vncport= your port number a number of 5 means port 5905

cdrom= the $iso is the path to the iso you specified above

the actual execution of the script is somewhat dynamic. For example if you don't specifiy "$drive" in the command line there won't be any hard disk (useful for livecds). Or commenting it out as shown above achieves the same result.

The "ifconfig" part actually puts up the tap device or is kind of the equivalent of plugging in a cable to the virtual NIC on the VM.

The echo 1 to proxy_arp makes it so your tap device can broadcast and receive arp requests. This way you can assign any IP to it and have it work.

Now the caveat not listed here which is very important is the routing.

You need to statically assign an IP to your VM and then add the routing (assuming you don't have a bridge which in this case brctl add if br0 $tapdev will automatically make the route work

If you don't have a bridge then you will need to do a "ip route add yourip dev yournic"

This will need to be done each time you start the VM or restart the host machine.

Linux wlan0 check all wireless clients

iw dev wlan0 station dump 

This is very useful because it is helpful if you are running something like hostapd and need to see the signal strength and negotiated connection speed.


Station ff:ff:ff:ff:ff:ff (on wlan0)
    inactive time:    16309 ms
    rx bytes:    25451
    rx packets:    325
    tx bytes:    44381
    tx packets:    159
    tx retries:    0
    tx failed:    0
    signal:      -72 [-72] dBm
    signal avg:    -72 [-72] dBm
    tx bitrate:    150.0 MBit/s MCS 7 40MHz short GI
    rx bitrate:    1.0 MBit/s
    authorized:    yes
    authenticated:    yes
    preamble:    long
    WMM/WME:    yes
    MFP:        no
    TDLS peer:    no
Station ff:ff:ff:ff:ff:ff (on wlan0)
    inactive time:    12223 ms
    rx bytes:    1206073
    rx packets:    8835
    tx bytes:    18597457
    tx packets:    14004
    tx retries:    0
    tx failed:    0
    signal:      -69 [-69] dBm
    signal avg:    -62 [-62] dBm
    tx bitrate:    150.0 MBit/s MCS 7 40MHz short GI
    rx bitrate:    6.0 MBit/s
    authorized:    yes
    authenticated:    yes
    preamble:    long
    WMM/WME:    yes
    MFP:        no
    TDLS peer:    no
Station ff:ff:ff:ff:ff:ff (on wlan0)
    inactive time:    406 ms
    rx bytes:    297303650
    rx packets:    213207
    tx bytes:    72276773
    tx packets:    150172
    tx retries:    0
    tx failed:    0
    signal:      -79 [-79] dBm
    signal avg:    -78 [-78] dBm
    tx bitrate:    15.0 MBit/s MCS 0 40MHz short GI
    rx bitrate:    45.0 MBit/s MCS 2 40MHz short GI
    authorized:    yes
    authenticated:    yes
    preamble:    short
    WMM/WME:    yes
    MFP:        no
    TDLS peer:    no

PHP Issues With Decoding Strange Smart Quotes And Non-Standard ASCII Characters

When using strip_tags and html_entity_decode with PHP it often breaks and produces annoying diamonds with question marks.

It is probably because of characters like these:

… (looks like 3 dots but it is a single weird character).

’ (looks like a normal apostraphe but it is not)

” (looks like a normal double quote but it is not).

An easy way to sort this out is to copy the above and search in an ASCII table to extend the functionality below.

Basically the first array has a list of "all the bad stuff" and the second array is what to replace it with.

<? function CleanupSmartQuotes($text) { $badwordchars=array( chr(145), // weird apostraphe chr(146), // weird apostraphe chr(147), // weird quote chr(148), // weird quote chr(151), // weird dash chr(133), // three dots ' ', ); $fixedwordchars=array( "'", "'", '"', '"', '—', '...', '', ); return str_replace($badwordchars,$fixedwordchars,$text); } ?>

/etc/iproute2/rt_tables default settings file in Linux Centos 6,7 and most other NIX's

This should apply to most Linux distributions just incase you get into trouble or wipe out the defaults by accident.

/etc/iproute2/rt_tables
# # reserved values # 255 local 254 main 253 default 0 unspec # # local # #1 inr.ruhep

bind named error solutions named[2169]: error (no valid DS) resolving / error (broken trust chain) resolving / : error (no valid RRSIG) resolving 'com/DS/IN':

Below are the common errors you'll get with named AKA bind if your time is incorrect.

The simplest solution is to install and run ntpd to correct your system's time (install ntpd if it is not installed)

systemctl start ntpd

systemctl enable ntpd

Dec 20 13:36:16 hostingbox named[2169]: error (no valid DS) resolving 'develop.waxrain.com/A/IN': 14.215.150.17#53 Dec 20 13:36:16 hostingbox named[2169]: error (no valid DS) resolving 'loc.map.baidu.com/A/IN': 202.108.22.220#53 Dec 20 13:36:16 hostingbox named[2169]: validating @0x7fc6f802ad00: org DS: verify failed due to bad signature (keyid=2134): RRSIG validity period has not begun Dec 20 13:36:16 hostingbox named[2169]: validating @0x7fc6f802ad00: org DS: no valid signature found Dec 20 13:36:16 hostingbox named[2169]: error (no valid RRSIG) resolving 'org/DS/IN': 192.33.4.12#53 Dec 20 13:36:16 hostingbox named[2169]: validating @0x7fc6fc4ba1e0: com DS: verify failed due to bad signature (keyid=2134): RRSIG validity period has not begun Dec 20 13:36:16 hostingbox named[2169]: validating @0x7fc6fc4ba1e0: com DS: no valid signature found Dec 20 13:36:16 hostingbox named[2169]: error (no valid RRSIG) resolving 'com/DS/IN': 199.7.91.13#53 Dec 20 13:36:16 hostingbox named[2169]: validating @0x7fc6f4013c50: org DS: verify failed due to bad signature (keyid=2134): RRSIG validity period has not begun Dec 20 13:36:16 hostingbox named[2169]: validating @0x7fc6f4013c50: org DS: no valid signature found Dec 20 13:36:16 hostingbox named[2169]: error (no valid RRSIG) resolving 'org/DS/IN': 192.228.79.201#53 Dec 20 13:36:16 hostingbox named[2169]: validating @0x7fc6fc4bb1f0: com DS: verify failed due to bad signature (keyid=2134): RRSIG validity period has not begun Dec 20 13:36:16 hostingbox named[2169]: validating @0x7fc6fc4bb1f0: com DS: no valid signature found Dec 20 13:36:16 hostingbox named[2169]: error (no valid RRSIG) resolving 'com/DS/IN': 192.5.5.241#53 Dec 20 13:37:30 hostingbox named[2229]: validating @0x7fb260010c30: detectportal.firefox.com A: bad cache hit (com/DS) Dec 20 13:37:30 hostingbox named[2229]: error (broken trust chain) resolving 'detectportal.firefox.com/A/IN': 96.7.49.66#53 Dec 20 13:37:30 hostingbox named[2229]: validating @0x7fb26848b0a0: detectportal.firefox.com A: bad cache hit (com/DS) Dec 20 13:37:30 hostingbox named[2229]: error (broken trust chain) resolving 'detectportal.firefox.com/A/IN': 96.7.49.66#53 Dec 20 13:37:30 hostingbox named[2229]: validating @0x7fb2580068f0: detectportal.firefox.com A: bad cache hit (com/DS) Dec 20 13:37:30 hostingbox named[2229]: error (broken trust chain) resolving 'detectportal.firefox.com/A/IN': 96.7.49.66#53 Dec 20 13:37:30 hostingbox named[2229]: validating @0x7fb2640028d0: detectportal.firefox.com A: bad cache hit (com/DS) Dec 20 13:37:30 hostingbox named[2229]: error (broken trust chain) resolving 'detectportal.firefox.com/A/IN': 96.7.49.66#53 Dec 20 13:37:30 hostingbox named[2229]: validating @0x7fb260010c30: detectportal.firefox.com A: bad cache hit (com/DS) Dec 20 13:37:30 hostingbox named[2229]: error (broken trust chain) resolving 'detectportal.firefox.com/A/IN': 96.7.49.66#53

iptables how to log ALL dropped incoming packets

A lot of people just have a -j DROP to drop all unwanted traffic or traffic not explicitly allowed but there is a better solution if you want real and proper logging:

Take an example iptables rules file

-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i eth1 -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i eth1 -j ACCEPT -N LOGGING -A INPUT -j LOGGING -A LOGGING -j LOG --log-prefix "ipt denied: " --log-level 4 -A LOGGING -j DROP

Add the above in bold below your last allowed incoming traffic rule and all dropped packets can be seen in dmesg or /var/log/messages

We create a new chain called "LOGGING" -N LOGGING
We are then passing all of our packets to that chain. -A INPUT -j LOGGING
Log all packets that are about to dropped with prefix "ipt denied:" (of course change it how you like) -A LOGGING -j LOG --log-prefix "ipt denied: " --log-level 4
Drop all packets in the LOGGING Chain -A LOGGING -j DROP

So in essence we change the -j DROP to the 4 lines in bold so that we have logging.

Checking dmesg or /var/log/messages should show similar to the following:

ipt denied: IN=eth0 OUT= MAC= SRC=194.113.106.121 DST=192.198.5.8 LEN=40 TOS=0x08 PREC=0x20 TTL=246 ID=45694 PROTO=TCP SPT=43848 DPT=54270 WINDOW=1024 RES=0x00 SYN URGP=0 ipt denied: IN=eth0 OUT= MAC= SRC=10.10.10.10 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2 ipt denied: IN=eth0 OUT= MAC= SRC=45.227.254.18 DST=192.198.5.8 LEN=40 TOS=0x08 PREC=0x20 TTL=245 ID=4350 PROTO=TCP SPT=56638 DPT=30450 WINDOW=1024 RES=0x00 SYN URGP=0 ipt denied: IN=eth0 OUT= MAC= SRC=176.119.7.50 DST=192.198.5.8 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=52004 PROTO=TCP SPT=54661 DPT=9153 WINDOW=1024 RES=0x00 SYN URGP=0 ipt denied: IN=eth0 OUT= MAC= SRC=109.248.9.116 DST=192.198.5.8 LEN=40 TOS=0x08 PREC=0x20 TTL=243 ID=49390 PROTO=TCP SPT=42898 DPT=37318 WINDOW=1024 RES=0x00 SYN URGP=0 ipt denied: IN=eth0 OUT= MAC= SRC=77.72.85.26 DST=192.198.5.8 LEN=40 TOS=0x08 PREC=0x20 TTL=243 ID=40508 PROTO=TCP SPT=49454 DPT=3978 WINDOW=1024 RES=0x00 SYN URGP=0 ipt denied: IN=eth0 OUT= MAC= SRC=115.74.194.77 DST=192.198.5.8 LEN=44 TOS=0x00 PREC=0x00 TTL=53 ID=10246 PROTO=TCP SPT=13207 DPT=23 WINDOW=24567 RES=0x00 SYN URGP=0 ipt denied: IN=eth0 OUT= MAC= SRC=10.10.10.10 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2 ipt denied: IN=eth0 OUT= MAC= SRC=176.119.7.10 DST=192.198.5.8 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=36884 PROTO=TCP SPT=51349 DPT=3992 WINDOW=1024 RES=0x00 SYN URGP=0 ipt denied: IN=eth0 OUT= MAC= SRC=87.27.61.197 DST=192.198.5.8 LEN=44 TOS=0x00 PREC=0x00 TTL=243 ID=44567 DF PROTO=TCP SPT=48364 DPT=23 WINDOW=14600 RES=0x00 SYN URGP=0 ipt denied: IN=eth0 OUT= MAC= SRC=185.255.31.38 DST=192.198.5.8 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=11928 PROTO=TCP SPT=8080 DPT=1013 WINDOW=1024 RES=0x00 SYN URGP=0 ipt denied: IN=eth0 OUT= MAC= SRC=185.255.31.38 DST=192.198.5.8 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=61268 PROTO=TCP SPT=8080 DPT=3303 WINDOW=1024 RES=0x00 SYN URGP=0 ipt denied: IN=eth0 OUT= MAC= SRC=185.255.31.18 DST=192.198.5.8 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=17889 PROTO=TCP SPT=42264 DPT=7129 WINDOW=1024 RES=0x00 SYN URGP=0 ipt denied: IN=eth0 OUT= MAC= SRC=194.113.106.121 DST=192.198.5.8 LEN=40 TOS=0x08 PREC=0x20 TTL=247 ID=64437 PROTO=TCP SPT=43848 DPT=58247 WINDOW=1024 RES=0x00 SYN URGP=0 ipt denied: IN=eth0 OUT= MAC= SRC=10.10.10.10 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2 ipt denied: IN=eth0 OUT= MAC= SRC=220.133.67.9 DST=192.198.5.8 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=64397 DF PROTO=TCP SPT=27852 DPT=23 WINDOW=14600 RES=0x00 SYN URGP=0 ipt denied: IN=eth0 OUT= MAC= SRC=101.255.58.22 DST=192.198.5.8 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=4583 DF PROTO=TCP SPT=53537 DPT=23 WINDOW=14600 RES=0x00 SYN URGP=0

How can I log the messages to a separate file eg. /var/log/iptables.log or /var/log/iptables-dropped.log?

The file name below can be arbitrary but it should have meaning to you.

Note that I am searching for the string "ipt denied: " this depends on what you have set as your log prefix in the example above.

vi /etc/rsyslog.d/10-iptables.conf

:msg, contains, "ipt denied: " -/var/log/iptables.log & ~

#note we need the "& ~" below the first line otherwise it will still send the log to where ever it would have been (eg. often /var/log/messages).
#the & ~ means to delete

service rsyslog restart

You should now notice that /var/log/messages has nothing for iptables and that you have /var/log/iptables.log

How To Edit Linux Based NM Network Manager Connection Settings Without GUI

Just find the relevant file in /etc/NetworkManager/system-connections

sudo vi /etc/NetworkManager/system-connections/Wired connection 1

[802-3-ethernet] duplex=full mac-address=00:00:00:FE:FE:FE [connection] id=Wired connection 1 type=802-3-ethernet timestamp=1532403341 [ipv6] method=ignore [ipv4] method=manual dns=192.168.1.1; address1=192.168.1.89/24,192.168.1.1

Linux Disable IPV6 Centos / Debian / Mint Howto

Set this in /etc/sysctl.conf

net.ipv6.conf.all.disable_ipv6 = 1

#apply the settings

sudo sysctl -p

Linux use growisofs to burn a larger file on a BD-R / Bluray Disc

growisofs -Z /dev/sr0 critical.tar.gz.gpg Executing 'genisoimage critical.tar.gz.gpg | builtin_dd of=/dev/sr0 obs=32k seek=0' I: -input-charset not specified, using utf-8 (detected in locale settings) File critical.tar.gz.gpg is larger than 4GiB-1.-allow-limited-size was not specified. There is no way do represent this file size. Aborting. :-( write failed: Input/output error

#remember to use -allow-limited-size

growisofs -allow-limited-size -Z /dev/sr0 critical.tar.gz.gpg

finish Sat Dec 15 16:23:34 2018 99.79% done, estimate finish Sat Dec 15 16:23:34 2018 99.85% done, estimate finish Sat Dec 15 16:23:34 2018 99.91% done, estimate finish Sat Dec 15 16:23:34 2018 99.97% done, estimate finish Sat Dec 15 16:23:34 2018 Total translation table size: 0 Total rockridge attributes bytes: 0 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 8087219 extents written (15795 MB) builtin_dd: 8087232*2KB out @ average 2.6x4390KBps /dev/sr0: flushing cache /dev/sr0: closing track /dev/sr0: closing session :-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: Input/output error /dev/sr0: reloading tray

Linux partprobe/partx cannot access last and 4th partition

On a test machine I was never able to access to a newly created 4th partiton. As we can see there are dev devices for everything but the 4th partition.

The normal "partprobe" or "kpartx" or kernel being told to rescan the block device didn't help (only a reboot did).

fdisk -l /dev/sda Disk /dev/sda: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 1 123 987966 83 Linux /dev/sda2 124 3771 29302560 83 Linux /dev/sda3 3772 11067 58605120 83 Linux /dev/sda4 11068 91201 643676355 83 Linux

#but where is sda4 why can't I see it but the other partitions are available in /dev
ls /dev/sda* /dev/sda /dev/sda1 /dev/sda2 /dev/sda3
partprobe didn't help partprobe Warning: WARNING: the kernel failed to re-read the partition table on /dev/sda (Device or resource busy). As a result, it may not reflect all of your changes until after reboot. Warning: WARNING: the kernel failed to re-read the partition table on /dev/sdb (Device or resource busy). As a result, it may not reflect all of your changes until after reboot. Warning: WARNING: the kernel failed to re-read the partition table on /dev/sdc (Device or resource busy). As a result, it may not reflect all of your changes until after reboot. Warning: /dev/sdd contains GPT signatures, indicating that it has a GPT table. However, it does not have a valid fake msdos partition table, as it should. Perhaps it was corrupted -- possibly by a program that doesn't understand GPT partition tables. Or perhaps you deleted the GPT table, and are now using an msdos partition table. Is this a GPT partition table? Warning: WARNING: the kernel failed to re-read the partition table on /dev/sdd (Device or resource busy). As a result, it may not reflect all of your changes until after reboot.

partx didn't helppartx -a /dev/sda BLKPG: Device or resource busy error adding partition 1 BLKPG: Device or resource busy error adding partition 2 BLKPG: Device or resource busy error adding partition 3 BLKPG: Device or resource busy error adding partition 4
OK let's manually tell the kernel to rescan the relevant block device.

echo 1 > /sys/block/sda/device/rescan

DRBD Errors Caused By Physical Corruption

In a RAID array I had a have periodically lost a drive here and there over the past several months. I was always able to readd and resync without losing data. However at some point it looks like some minor corruption happened and this makes DRBD unhappy.

Using fsck did not help either.

Dec 19 06:01:45 storageboxtest4 kernel: [19005.945890] EXT3-fs error (device drbd0): ext3_get_inode_loc: unable to read inode block - inode=22184379, block=88735771 Dec 19 06:01:45 storageboxtest4 kernel: [19005.946084] EXT3-fs error (device drbd0): ext3_get_inode_loc: unable to read inode block - inode=22184380, block=88735771 Dec 19 06:01:45 storageboxtest4 kernel: [19005.946289] EXT3-fs error (device drbd0): ext3_get_inode_loc: unable to read inode block - inode=22184381, block=88735771 Dec 19 06:01:46 storageboxtest4 kernel: [19006.903899] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 exit code 0 (0x0) Dec 19 06:01:46 storageboxtest4 kernel: [19006.903918] block drbd0: helper command: /sbin/drbdadm local-io-error minor-0 Dec 19 06:01:46 storageboxtest4 kernel: [19006.908202] Power Off Dec 19 06:01:46 storageboxtest4 kernel: [19006.910016] md: md125: recovery interrupted. Dec 19 06:01:47 storageboxtest4 kernel: [19007.715470] EXT3-fs error (device drbd0): ext3_get_inode_loc: unable to read inode block - inode=22840092, block=91357233 Dec 19 06:01:47 storageboxtest4 kernel: [19007.715789] EXT3-fs error (device drbd0): ext3_get_inode_loc: unable to read inode block - inode=22840092, block=91357233 Dec 19 06:01:47 storageboxtest4 kernel: [19007.785375] EXT3-fs error (device drbd0): ext3_get_inode_loc: unable to read inode block - inode=22840094, block=91357233 Dec 19 06:01:47 storageboxtest4 kernel: [19007.785705] EXT3-fs error (device drbd0): ext3_get_inode_loc: unable to read inode block - inode=22840094, block=91357233 Dec 19 13:35:55 storageboxtest4 kernel: imklog 5.8.10, log source = /proc/kmsg started.

Just a simple dd test gives back an io error near the end of the array:

dd: reading `/dev/drbd0': Input/output error

mdadm: add new device failed for /dev/sdb4 as 3: Invalid argument solution

mdadm --manage /dev/md125 -a /dev/sdb4 mdadm: add new device failed for /dev/sdb4 as 3: Invalid argument

Dec 19 01:23:48 storageboxtest kernel: [ 2328.854491] md: sdb4 does not have a valid v1.2 superblock, not importing! Dec 19 01:23:48 storageboxtest kernel: [ 2328.854499] md: md_import_device returned -22

#zero the superblock and try again!
mdadm --zero-superblock /dev/sdb4 mdadm --manage /dev/md125 -a /dev/sdb4

mdadm: add new device failed for /dev/sdb4 as 3: Invalid argument

Solution / this is the only thing that fixed it (basically do more than just zero-superblock)

dd if=/dev/zero of=/dev/sdb4 ^C77149+0 records in 77149+0 records out 39500288 bytes (40 MB) copied, 5.35553 s, 7.4 MB/s

#success!

mdadm --manage /dev/md125 -a /dev/sdb4mdadm: added /dev/sdb4

The weird thing is that you can see zero-superblock was NOT enough to fix it and sometimes you have to wipe a little further than zero-superblock does and it will fix it. I didn't find this solution anywhere so I thought I'd share it.

Linux named / bind how to dump, view and clear the cache!

Do you hate it when your ISP has old cached records because of a high TTL on the DNS record of the relevant domain? In plain English this means you often can't connect to a site or service because your ISP's DNS servers haven't gotten word of the new IP address (probably because they haven't checked). There are also some that are notorious for ignoring TTL and not updating records for days!

But if you are lucky and smart enough to have your own Linux based DNS server you can do the following:

rndc dumpdb -cache

This let's you see the cached entries by writing the bind cache to /var/named/data/cache_dump.db

If you just want to clear your DNS cache:

rndc flush

The above flushes all of your DNS cache which is never a bad idea since it saves memory and increases the performance potentially.

Centos 6 / 7 / 8 How To Change Default nameservers in /etc/resolv.conf when using DHCP / dhclient

First we need to create dhclient.conf if it doesn't exist or edit it:

vi /etc/dhclient/dhclient.conf

#add this line at the top add the IPs as commas they will be the highest priority nameservers and whatever your ISP gives you will be used after these one (good for DNS backup)

prepend domain-name-servers 127.0.0.1,10.10.25.8;

After you restart your network or run dhclient again you should see the contents of /etc/resolv.conf are as you expect.

This is mainly when you are running a local router and local DNS (and usually your own local DNS is quicker and more reliable than your ISP in my experience).

Adobe Acrobat Reader for Linux to use and view XFA Fillable Forms

The reason for not being able to read one of these dreaded/ fillable "XFA" forms is because no Linux PDF reader that I'm aware of supports them. Part of this reasoning is for security. It is really silly, they should ban these XFA forms or at least replace the Please Wait with the non-fillable version.

Download Adobe Reader 9.5 for Linux from here:

This is the solution but only so much, at least for me I was able to view the PDF and fill it but printing it produces a blank page (even print preview shows it as blank). I tried converting it to a normal pdf with print to file including postscript but none of that worked either.

With that said you too can get this broken version of the Linux Adobe Acrobat version :)

Perhaps a previous 9.5 (older version) even though the latest is from 2013 may work better?

ftp://ftp.adobe.com/pub/adobe/reader/unix/9.x/9.5.5/enu/

Sick of this error?

Please wait...
If this message is not eventually replaced by the proper contents of the document, your PDF
viewer may not be able to display this type of document.
You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by
visiting http://www.adobe.com/go/reader_download.
For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark
of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries

Debian Linux Mint Ubuntu iptables save and restore settings automatically onboot and reboot

First you need the "iptables-persistent" package. This gives you an init script that loads your settings from /etc/iptables/rules.v4 and rules.v6

When you install it, it wll save your default setings in /etc/iptables.

sudo apt-get install iptables-persistent

Why SMART is not smart at all and doesn't properly predict disk errors that cause a kernel panic or crash

Before getting into the output here is my typical experience with SMART, there is what I call a "bad disk" with pending and uncorrectable sectors that cannot be reallocated.
It has caused a kernel panic and system crash repeatedly as we can see from the logs.
But SMART says it has "PASSED" its self assessment.  SMART is still useful to me but it is more about looking at Current_Pending_Sector.
Any time I have had anything but 0 for that attribute it means the disk is bad and is unusable (eg. will cause kernel panics).
In this case even RAID doesn't help when the bad disk taints the kernel.

First let's check this disk and see what SMART thinks

smartctl -a /dev/sda

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda ES
Device Model:     ST3750640NS
Serial Number:    ABCAEAAA
LU WWN Device Id: 5 000c50 0083422e5
Firmware Version: 3BKH
User Capacity:    750,156,374,016 bytes [750 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Thu Dec 13 12:43:37 2018 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED


ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   093   086   006    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0003   091   091   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       27
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   090   060   030    Pre-fail  Always       -       951683243
  9 Power_On_Hours          0x0032   052   052   000    Old_age   Always       -       42128
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       27
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   066   054   045    Old_age   Always       -       34 (Min/Max 28/36)
194 Temperature_Celsius     0x0022   034   046   000    Old_age   Always       -       34 (0 17 0 0 0)
195 Hardware_ECC_Recovered  0x001a   081   055   000    Old_age   Always       -       220199
197 Current_Pending_Sector  0x0012   096   096   000    Old_age   Always       -       93
198 Offline_Uncorrectable   0x0010   096   096   000    Old_age   Offline      -       93
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       971
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
202 Data_Address_Mark_Errs  0x0032   100   253   000    Old_age   Always       -       0

Now let's see /var/log/messages

Dec 12 05:29:46 somepoorbox kernel: [30883839.026190] sd 0:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Dec 12 05:29:46 somepoorbox kernel: [30883839.026196] sd 0:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor] Dec 12 05:29:46 somepoorbox kernel: [30883839.026203] Descriptor sense data with sense descriptors (in hex): Dec 12 05:29:46 somepoorbox kernel: [30883839.026206]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Dec 12 05:29:46 somepoorbox kernel: [30883839.026215]         57 4f 86 7b Dec 12 05:29:46 somepoorbox kernel: [30883839.026219] sd 0:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed Dec 12 05:29:46 somepoorbox kernel: [30883839.026225] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 57 4f 8a 43 00 03 38 00 Dec 12 05:29:46 somepoorbox kernel: [30883839.026236] end_request: I/O error, dev sda, sector 1464830531 Dec 12 05:29:46 somepoorbox kernel: [30883839.026331] block drbd0: disk( UpToDate -> Failed ) Dec 12 05:29:46 somepoorbox kernel: [30883839.026345] block drbd0: Local IO failed in __req_mod. Detaching... Dec 12 05:29:46 somepoorbox kernel: [30883839.026365] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 Dec 12 05:29:46 somepoorbox kernel: [30883839.026476] sd 0:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Dec 12 05:29:46 somepoorbox kernel: [30883839.026480] sd 0:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor] Dec 12 05:29:46 somepoorbox kernel: [30883839.026485] Descriptor sense data with sense descriptors (in hex): Dec 12 05:29:46 somepoorbox kernel: [30883839.026488]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Dec 12 05:29:46 somepoorbox kernel: [30883839.026497]         57 4f 86 7b Dec 12 05:29:46 somepoorbox kernel: [30883839.026501] sd 0:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed Dec 12 05:29:46 somepoorbox kernel: [30883839.026506] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 57 4f 86 7b 00 03 c8 00 Dec 12 05:29:46 somepoorbox kernel: [30883839.026514] end_request: I/O error, dev sda, sector 1464829563 Dec 12 05:29:46 somepoorbox kernel: [30883839.026632] block drbd0: IO ERROR: neither local nor remote disk Dec 12 05:29:46 somepoorbox kernel: [30883839.026636] ata1: EH complete Dec 12 05:29:46 somepoorbox kernel: [30883839.026728] block drbd0: IO ERROR: neither local nor remote disk Dec 12 05:29:46 somepoorbox kernel: [30883839.026811] block drbd0: IO ERROR: neither local nor remote disk Dec 12 05:29:46 somepoorbox kernel: [30883839.162977] Buffer I/O error on device drbd0, logical block 53203520 Dec 12 05:29:46 somepoorbox kernel: [30883839.163110] lost page write due to I/O error on drbd0 Dec 12 05:29:46 somepoorbox kernel: [30883839.163117] Buffer I/O error on device drbd0, logical block 59744311 Dec 12 05:29:46 somepoorbox kernel: [30883839.163200] lost page write due to I/O error on drbd0 Dec 12 05:29:46 somepoorbox kernel: [30883839.163208] Buffer I/O error on device drbd0, logical block 59744312 Dec 12 05:29:46 somepoorbox kernel: [30883839.163289] lost page write due to I/O error on drbd0 Dec 12 05:29:46 somepoorbox kernel: [30883839.163299] Buffer I/O error on device drbd0, logical block 59746338 Dec 12 05:29:46 somepoorbox kernel: [30883839.163316] Buffer I/O error on device drbd0, logical block 59744312 Dec 12 05:29:46 somepoorbox kernel: [30883839.163320] lost page write due to I/O error on drbd0 Dec 12 05:29:46 somepoorbox kernel: [30883839.163328] EXT3-fs: ext3_journal_dirty_data: aborting transaction: IO failure in ext3_journal_dirty_data Dec 12 05:29:46 somepoorbox kernel: [30883839.163336] EXT3-fs (drbd0): error in ext3_orphan_add: Readonly filesystem Dec 12 05:29:46 somepoorbox kernel: [30883839.165257]  [] ? warn_slowpath_common+0x91/0xe0 Dec 12 05:29:46 somepoorbox kernel: [30883839.165260] EXT3-fs (drbd0): I/O error while writing superblock Dec 12 05:29:46 somepoorbox kernel: [30883839.165280]  [] ? ext3_get_group_desc+0x51/0xa0 [ext3] Dec 12 05:29:46 somepoorbox kernel: [30883839.165285] JBD: Spotted dirty metadata buffer (dev = drbd0, blocknr = 0). There's a risk of filesystem corruption in case of system crash. Dec 12 05:29:46 somepoorbox kernel: [30883839.165292]  [] ? warn_slowpath_null+0x1a/0x20 Dec 12 05:29:46 somepoorbox kernel: [30883839.165297]  [] ? mark_buffer_dirty+0x82/0xa0 Dec 12 05:29:46 somepoorbox kernel: [30883839.165316]  [] ? ext3_commit_super.clone.0+0x69/0x100 [ext3] Dec 12 05:29:46 somepoorbox kernel: [30883839.165329]  [] ? ext3_handle_error+0x7f/0xe0 [ext3] Dec 12 05:29:46 somepoorbox kernel: [30883839.165343]  [] ? __ext3_std_error+0x5e/0xb0 [ext3] Dec 12 05:29:46 somepoorbox kernel: [30883839.165356]  [] ? ext3_orphan_add+0xbf/0x1a0 [ext3] Dec 12 05:29:46 somepoorbox kernel: [30883839.165360] EXT3-fs: ext3_journal_dirty_data: aborting transaction: IO failure in ext3_journal_dirty_data Dec 12 05:29:46 somepoorbox kernel: [30883839.165374]  [] ? journal_dirty_data_fn+0x0/0x30 [ext3] Dec 12 05:29:46 somepoorbox kernel: [30883839.165378] EXT3-fs (drbd0): error in ext3_orphan_add: Readonly filesystem [] ? ext3_ordered_write_end+0x158/0x1c0 [ext3] Dec 12 05:29:46 somepoorbox kernel: [30883839.165395] Dec 12 05:29:46 somepoorbox kernel: [30883839.165400]  [] ? generic_file_buffered_write_iter+0x184/0x2b0 Dec 12 05:29:46 somepoorbox kernel: [30883839.165407]  [] ? __generic_file_write_iter+0x225/0x420 Dec 12 05:29:46 somepoorbox kernel: [30883839.165412]  [] ? __generic_file_aio_write+0x85/0xa0 Dec 12 05:29:46 somepoorbox kernel: [30883839.165417]  [] ? generic_file_aio_write+0x88/0x100 Dec 12 05:29:46 somepoorbox kernel: [30883839.165423]  [] ? do_sync_write+0xf2/0x140 Dec 12 05:29:46 somepoorbox kernel: [30883839.165432]  [] ? sys_getpeername+0xd4/0xf0 Dec 12 05:29:46 somepoorbox kernel: [30883839.165436]  [] ? vfs_write+0xb8/0x1a0 Dec 12 05:29:46 somepoorbox kernel: [30883839.165441]  [] ? fget_light_pos+0x16/0x50 Dec 12 05:29:46 somepoorbox kernel: [30883839.165445]  [] ? sys_write+0x51/0xb0 Dec 12 05:29:46 somepoorbox kernel: [30883839.165450]  [] ? __audit_syscall_exit+0x25e/0x290 Dec 12 05:29:46 somepoorbox kernel: [30883839.165455]  [] ? system_call_fastpath+0x16/0x1b Dec 12 05:29:46 somepoorbox kernel: [30883839.165459] ---[ end trace 32aa3e2dc89d4c30 ]--- Dec 12 05:29:46 somepoorbox kernel: [30883839.165462] Tainting kernel with flag 0x9

scp: ambiguous target error and solution

scp -rp Week09 one@10.10.5.80:"/some/remote/path/with a space/"

Gives me an error:

scp: ambiguous target

The issue is caused by the space in the remote path which needs to be escaped like this:

scp -rp Week09 one@10.10.5.80:"/some/remote/path/with a space/"

Basically you add a backslash in front of each space.

VirtualBox How To Add iSCSI Storage using VBoxManage

#to show all
VBoxManage list vms

#show ONLY running vms
VBoxManage list runningvms

VBoxManage storageattach test --storagectl "SATA" --port 0 --device 0 --type hdd --medium iscsi --server 192.168.1.91 --target "iqn.2018-12.local.abcrandom.target:sdb" --initiator "iqn.1982-01.ca.bla.tld:abc123" --tport 3260 --lun 1 iSCSI disk created. UUID: 3bbdd942-f3b0-4bc9-8f22-b0118f6f11ec

--server = the IP address of the iSCSI target server

--target = the target on the iSCSI srever

--initiator = your initiator name (eg. the equivalent of /etc/iscsi/initiator.iscsi)

--lun 1 (or whatever LUN number

Troubleshooting

If the disk creates successfully but VBox says it is inacessible it means you have probably specified something wrong in the flags above. Eg. a typo in your target, initiator, forgetting your LUN

UUID Already Exists

VBoxManage storageattach test --storagectl "SATA" --port 0 --device 0 --type hdd --medium iscsi --server 192.168.1.91 --target "iqn.1982-01.ca.bla.tld:abc123" VBoxManage: error: Cannot register the hard disk '192.168.1.91|iqn.1982-01.ca.bla.tld:abc123' {16b201f8-da53-499c-86ec-753a8b940e58} because a hard disk '192.168.1.91|iqn.1982-01.ca.bla.tld:abc123' with UUID {8cd2dd6e-9b69-488c-81f6-22fa96da0a2f} already exists VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports VBoxManage: error: Context: "CreateMedium(Bstr("iSCSI").raw(), bstrISCSIMedium.raw(), AccessMode_ReadWrite, DeviceType_HardDisk, pMedium2Mount.asOutParam())" at line 608 of file VBoxManageStorageController.cpp

#list all hdds

vboxmanage list hddsUUID: 8cd2dd6e-9b69-488c-81f6-22fa96da0a2f Parent UUID: base State: inaccessible Type: normal (base) Location: 192.168.1.91|iqn.1982-01.ca.bla.tld:abc123 Storage format: iSCSI Capacity: 0 MBytes Encryption: disabled

#let's delete it

vboxmanage closemedium disk 8cd2dd6e-9b69-488c-81f6-22fa96da0a2f --delete #uh oh iSCSI disks can't be deleted this way vboxmanage closemedium disk 8cd2dd6e-9b69-488c-81f6-22fa96da0a2f --delete VBoxManage: error: Medium format 'iSCSI' does not support storage deletion VBoxManage: error: Details: code VBOX_E_NOT_SUPPORTED (0x80bb0009), component MediumWrap, interface IMedium, callee nsISupports VBoxManage: error: Context: "DeleteStorage(pProgress.asOutParam())" at line 1603 of file VBoxManageDisk.cpp VBoxManage: error: Failed to delete medium. Error code Unknown Status -2135228407 (0x80bb0009)

Sometimes just using closemedium before works:

vboxmanage closemedium disk 8cd2dd6e-9b69-488c-81f6-22fa96da0a2f

Either way after the above you should be able to retry to connect your iSCSI disk

iSCSI on Centos 7 Configuration and Setup Guide for Initiator and Target

initiator = client

target = server

These are the first concepts you should understand which is that in iscsi essentially the "initiator" is the client and the "target" is the server.

iSCSI is derived from the old fashioned SCSI that us oldtimers grew to love. The "i" stands for Internet and the SCSI stands for "Small Computers Systems Interface" (SCSI).

iSCSI Target (Server) Setup

targetcli is the package that creates the iSCSI server and allows you to export your devices.

yum -y install targetcli

Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: centos.ca-west.mirror.fullhost.io * epel: mirrors.cat.pdx.edu * extras: centos.ca-west.mirror.fullhost.io * updates: centos.ca-west.mirror.fullhost.io Resolving Dependencies --> Running transaction check ---> Package targetcli.noarch 0:2.1.fb46-6.el7_5 will be updated ---> Package targetcli.noarch 0:2.1.fb46-7.el7 will be an update --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Updating: targetcli noarch 2.1.fb46-7.el7 base 67 k Transaction Summary ================================================================================ Upgrade 1 Package Total download size: 67 k Downloading packages: No Presto metadata available for base targetcli-2.1.fb46-7.el7.noarch.rpm | 67 kB 00:00 Running transaction check Running transaction test Transaction test succeeded Running transaction Updating : targetcli-2.1.fb46-7.el7.noarch 1/2 Cleanup : targetcli-2.1.fb46-6.el7_5.noarch 2/2 Verifying : targetcli-2.1.fb46-7.el7.noarch 1/2 Verifying : targetcli-2.1.fb46-6.el7_5.noarch 2/2 Updated: targetcli.noarch 0:2.1.fb46-7.el7 Complete!

systemctl enable target

systemctl start target

systemctl disable firewalld

systemctl stop firewalld

firewall-cmd --permanent --add-port=3260/tcp firewall-cmd --reload

Launch targetcli to configure our iSCSI target

Let's see what block storage/backing devices we have?

/> cd backstores/block /backstores/block> ls o- block .................................................. [Storage Objects: 0] /backstores/block>

Create our iSCSI disk

/backstores/block> create areebsfault /dev/sdb Created block storage object areebsfault using /dev/sdb.

Create our target

The "iqn" must go first and then year-time and then local and finally the "host name" and after the colon the target name "sdb". IQN= iSCSI Qualified Name

iqn
Date (1982-01)
Reversed domain name of the authority (eg. target.abcrandom.local) becomes local.abcrandom.target
Optional “:” that prefixes a storage target name specified by the naming authority

cd /iscsi

/iscsi> create iqn.2018-12.local.abcrandom.target:sdb Created target iqn.2018-12.local.abcrandom.target:sdb. Created TPG 1. Global pref auto_add_default_portal=true Created default portal listening on all IPs (0.0.0.0), port 3260.

Do we have any LUN?

/iscsi/iqn.20...sdb/tpg1/acls> cd /iscsi/iqn.2018-12.local.abcrandom.target:sdb/ /iscsi/iqn.20...om.target:sdb> ls o- iqn.2018-12.local.abcrandom.target:sdb ............................ [TPGs: 1] o- tpg1 ............................................... [no-gen-acls, no-auth] o- acls .......................................................... [ACLs: 0] o- luns .......................................................... [LUNs: 0] o- portals .................................................... [Portals: 1] o- 0.0.0.0:3260 ..................................................... [OK]

Create our LUN

cd /iscsi/iqn.2018-12.local.abcrandom.target:sdb/tpg1/luns

/iscsi/iqn.20...sdb/tpg1/luns> create /backstores/block/areebsfault lun1 Created LUN 1. /iscsi/iqn.20...sdb/tpg1/luns> ls o- luns .............................................................. [LUNs: 1] o- lun1 .................... [block/areebsfault (/dev/sdb) (default_tg_pt_gp)]Create ACL so our initiator can connect

cd /iscsi/iqn.2018-12.local.abcrandom.target:sdb/tpg1/acls

/iscsi/iqn.20...sdb/tpg1/acls> create iqn.1982-01.ca.bla.tld:abc123 Created Node ACL for iqn.1982-01.ca.bla.tld:abc123 Created mapped LUN 1.

*Note the iqn for this ACL as you will need to use it in the clientside (initiator setup).

Client Side Setup

systemctl disable firewalld

systemctl stop firewalld

firewall-cmd --permanent --add-port=3260/tcp firewall-cmd --reload

yum -y install iscsi-initiator-utils

Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.its.sfu.ca * extras: mirror.its.sfu.ca * updates: mirror.its.sfu.ca Resolving Dependencies --> Running transaction check ---> Package iscsi-initiator-utils.x86_64 0:6.2.0.874-10.el7 will be installed --> Processing Dependency: iscsi-initiator-utils-iscsiuio >= 6.2.0.874-10.el7 for package: iscsi-initiator-utils-6.2.0.874-10.el7.x86_64 --> Running transaction check ---> Package iscsi-initiator-utils-iscsiuio.x86_64 0:6.2.0.874-10.el7 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: iscsi-initiator-utils x86_64 6.2.0.874-10.el7 base 421 k Installing for dependencies: iscsi-initiator-utils-iscsiuio x86_64 6.2.0.874-10.el7 base 92 k Transaction Summary ================================================================================ Install 1 Package (+1 Dependent package) Total download size: 513 k Installed size: 2.6 M Downloading packages: (1/2): iscsi-initiator-utils-6.2.0.874-10.el7.x86_64.rpm | 421 kB 00:00 (2/2): iscsi-initiator-utils-iscsiuio-6.2.0.874-10.el7.x86 | 92 kB 00:00 -------------------------------------------------------------------------------- Total 977 kB/s | 513 kB 00:00 Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : iscsi-initiator-utils-6.2.0.874-10.el7.x86_64 1/2 Installing : iscsi-initiator-utils-iscsiuio-6.2.0.874-10.el7.x86_64 2/2 Verifying : iscsi-initiator-utils-iscsiuio-6.2.0.874-10.el7.x86_64 1/2 Verifying : iscsi-initiator-utils-6.2.0.874-10.el7.x86_64 2/2 Installed: iscsi-initiator-utils.x86_64 0:6.2.0.874-10.el7 Dependency Installed: iscsi-initiator-utils-iscsiuio.x86_64 0:6.2.0.874-10.el7 Complete!

Edit initiatorname.iscsi

vi /etc/iscsi/initiatorname.iscsi

You can also use the echo command (make sure you use the correct iqn):

echo "InitiatorName=iqn.1982-01.ca.bla.tld:abc123" > /etc/iscsi/initiatorname.iscsi

Start and Enable iscsid

[root@localhost ~]# systemctl start iscsid [root@localhost ~]# systemctl enable iscsid Created symlink from /etc/systemd/system/multi-user.target.wants/iscsid.service to /usr/lib/systemd/system/iscsid.service.

Find Targets!

iscsiadm -m discovery --type sendtargets -p 192.168.1.91 192.168.1.91:3260,1 iqn.2018-12.local.abcrandom.target:sdb

If all is well you should see this with ls

ls /var/lib/iscsi/nodes iqn.2018-12.local.abcrandom.target:sdb [root@localhost ~]# ls /var/lib/iscsi/ ifaces/ nodes/ slp/ isns/ send_targets/ static/ [root@localhost ~]# ls /var/lib/iscsi/send_targets/ 192.168.1.91,3260Mount all iscsi targets

iscsiadm -m node -l Logging in to [iface: default, target: iqn.2018-12.local.abcrandom.target:sdb, portal: 192.168.1.91,3260] (multiple) Login to [iface: default, target: iqn.2018-12.local.abcrandom.target:sdb, portal: 192.168.1.91,3260] successful.

You should now see a /dev/sdb available that you can format like a normal disk.

cat /proc/partitions major minor #blocks name 11 0 1048575 sr0 8 0 15728640 sda 8 1 1048576 sda1 8 2 14679040 sda2 253 0 13103104 dm-0 253 1 1572864 dm-1 8 16 4096 sdb

Set it for onboot loading

mkfs.ext4 /dev/sdb1 mke2fs 1.42.9 (28-Dec-2013) Filesystem label= OS type: Linux Block size=1024 (log=0) Fragment size=1024 (log=0) Stride=0 blocks, Stripe width=32764 blocks 1024 inodes, 4092 blocks 204 blocks (4.99%) reserved for the super user First data block=1 Maximum filesystem blocks=4194304 1 block group 8192 blocks per group, 8192 fragments per group 1024 inodes per group Allocating group tables: done Writing inode tables: done Creating journal (1024 blocks): done Writing superblocks and filesystem accounting information: done [root@localhost ~]# blkid /dev/sdb1 /dev/sdb1: UUID="7c1b6358-24b0-4296-b099-13eb1100f72e" TYPE="ext4"

add something like this to /etcfstab

UUID=7c1b6358-24b0-4296-b099-13eb1100f72e /mnt/iscsi ext4 _netdev 0 0

Troubleshooting Common Issues

Firewall Issues. Make sure firewalls are disabled or port 3260 is enabled.
Listening on the wrong IP or port in your portal.
Specifying the target instead of the initiator name/ACL name.
Not creating an LUN
Mixing up different target names with the wrong initiator name.
The client side is using the wrong initiator name (often a random generated one by the OS).

How To

Login To All Targets

iscsiadm -m node -l

Login To Specific Target

iscsiadm -m node -l -T iqn.target.name:bla

Delete your iscsi target

/iscsi> cd /iscsi/ /iscsi> delete iqn.2016-06.localb.a.bla:123 Deleted Target iqn.2016-06.localb.a.bla:123.

Disconnect your client from a target

iscsiadm -m node --logout -T iqn.2018-12.local.abcrandom.target:sdb Logging out of session [sid: 1, target: iqn.2018-12.local.abcrandom.target:sdb, portal: 192.168.1.91,3260] Logout of [sid: 1, target: iqn.2018-12.local.abcrandom.target:sdb, portal: 192.168.1.91,3260] successful.

Disconnect from ALL targets

iscsiadm -m node --logout all Logging out of session [sid: 2, target: iqn.2018-12.local.abcrandom.target:sdb, portal: 192.168.1.91,3260] Logout of [sid: 2, target: iqn.2018-12.local.abcrandom.target:sdb, portal: 192.168.1.91,3260] successful.

Python and BeautifulSoup4's BS4's Decompose Method To Remove Unwanted Inner Tags

<div class="c-shca-icon-item__body-name"> < a href="/Products/MX72244"> < span class="c-shca-icon-item__body-name-brand"> ADATA < / span> XPG SX8200 PCI - E 3.0 x4 M .2 NVMe SSD, 480 GB < / a>

The problem in the html above is that there is a "span" inside the "a" and this is unusual except for a few products with ADATA.
Otherwise it would print out ADATA with the other product information "XPG SX8200 PCI - E 3.0 x4 M .2 NVMe SSD, 480 GB". So we just want the product info and not the ADATA inside span.

The solution is to use beautifulsoup's "decompose method below".

hddname = prices.find("div", {"class": "c-shca-icon-item__body-name"}) hddname=hddname.find("a") hddname.span.decompose() hddname=hddname.get_text().strip()

Once we have the "a" tag contents which contain a "span inside". We just use the decompose() method.

The format is as follows

soupname.tagname.decompose()

httpd AH00534: httpd: Configuration error: No MPM loaded. solution

httpd AH00534: httpd: Configuration error: No MPM loaded.

Simple Solution (assuming you don't have this line in httpd.conf aleady:

echo "Include conf.modules.d/*.conf" >> /etc/httpd/conf/httpd.conf

bash script to remove modules from httpd.conf that are not actually installed

confmodules=`cat /etc/httpd/conf/httpd.conf |grep -v ^#|grep "modules/"|awk '{print $3}'|cut -d "/" -f 2` for module in $confmodules; do echo "module=$module" if [ ! -f /etc/httpd/modules/$module ]; then linenum=`awk /"$module/{ print NR; exit}" /etc/httpd/conf/httpd.conf` sed -i "$linenum"s/.*// /etc/httpd/conf/httpd.conf echo "hey we don't have this $module in /etc/httpd/modules" fi done

Basically the script checks all of the modules your httpd.conf tries to load. Then it checks if the file actually exists in /etc/httpd/modules/ and if it doesn't it edits httpd.conf by removing the relevant line for the module that doesn't exist.

bash scripting how to create a function

function centos7 { release=`cat /etc/redhat-release|awk '{print $4}'|grep ^[7]` if [ "$release" != "" ]; then centos7='yes' fi } centos7 echo "$centos7"

We create a function called "centos7" and then call it by just typing "centos7"

We then access a variable that may be set if we are running centos7 which is also called "$centos7".

If the value is present it should be = "yes" which means we are running Centos 7.

Centos 7 PHP MySQL Not Working Solution

PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib64/php/modules/pdo_mysql.so' - /usr/lib64/php/modules/pdo_mysql.so: symbol mysql_options, version libmysqlclient_18 not defined in file libmysqlclient.so.18 with link time reference in Unknown on line 0

#not sure what is wrong with php-mysql but I removed it and installed mysqlnd

yum -y remove php-mysql yum -y install php-mysqlnd

Bash How To Cut or Split Natively And Get The LAST Field

This takes "yourvariable" and splits it based on the last character in this case "-" and shows the last field of that split.

${yourvariable##*-}

Bash Script How To Manipulate Text/Strings By Searchig and Replacing Natively

# a single first slash means first occurrence
# format=${haystack/needle/replacement}
# if you use a double first slash it means ALL occurrences
# format=${haystack//needle/replacement}

email=${file/.txt-marked/}

In the example above we are searching in the variable $file for ".txt-marked" and replacing with nothing (the empty part after the last / means we are replacing with nothing or actually removing it).

How to replace all occurrences?

email=${file//.txt-marked/}

The only difference is where the first slash goes. If you use double slashes it means to replace ALL occurences.

How Does Cisco CUCM (Cisco Unified Communication Manager) Work?

Cisco's CUCM (Cisco Unified Communication Manager) is a system that combines voice, video, data and mobile products into a single unified management suite. At its core, the CUCM is like a "Super PBX" that controls the flow of all communications through an organization even single or multiple site deployments.

Cisco's CUCM makes communication more effective and simple through centralized management and unification of communications resources.

How Does CUCM Work?

First of all the CUCM is a Linux based OS that is installed onto a server. It is like the "Control Panel" or "PBX" for all of your communications in terms of voice and video.

CUCM consists of 4-layers or building blocks to function and create a cohesive communication solution for your enterprise.

4-Layers of CUCM

Layer 1.) Infrastructure

Since CUCM is IP (Internet Protocol) based it uses traditional network infrastructure including switches, routers with the addition of voice specific gateway and switching (voice gateway and voice switch). This layer is also where high availability, QoS (Quality of Service) and management.

Layer 2.) Call Control

The call control layer is actually where CUCM lives and is active. It is the layer that handles and processes the calls, manages devices and where the PBX administrator can set dial plans and other features.

Layer 3.) Application

The applicaton layer processes things other than calls and is indepedent of the Call Control layer.

Examples of applications under this layer are the following:

Cisco Unity - Voicemail, unified messaging and integrated messaging applications
Cisco Unified Contact Center - Call Center Management
Cisco Unified Meeting Place - Video Conferencing
Cisco ER (Emergency Responder) - Identifies the caller location and maps that location to an emergency line identification number.
Cisco Unified Presence Server - Collects and reports information on user devices and availability over what mediums (eg. voice, video etc..)
Third Party App Support - Supports common standards such as TAPI (Telephone Application Programming Interface), SIP (Session Initiation Protocol) (for VOIP), H.323 (an open standard that allows for unified video, audio and data collaboration), MGCP (Media Gateway Control Protocol)

Layer 4.) Endpoints

The end points layer should be described and thought of as the "user level" which is essentially the end-product for the end user. This is because the Endpoints layer presents itself as a Cisco based IP phone, or other VOIP device/application, video terminal etc.

How the Cisco Unified Communications Network Works

The Cisco CUCM is like the "director" or "operator" of calls and helps initially connect or signal the parties involved in a phone conversation. It refers to the complete process of originating, terminating and routing calls. It also allows for stats to be collected for metrics and billing.

The actual voice and data travels directly between the devices themselves over whatever network they are connected to and the failure or loss of connectivity to the CUCM does not impact current conversations (unless you try to use a feature that CUCM controls such as hold, transfer etc..)

The CUCM also creates dialplans which control how and where a user can call.

CUCM also creates basic phone functionality such as the ability to hold, conference or transfer calls.

CUCM also integrates with your existing Active Directory setup to help reduce the configuration and authentication of new users.

How Do Calls Get Setup?

Once the end-user picks up their phone, the phone signals the CUCM that it is "off hook" or "picked up" and will signal the device to play the dialtone. Their device either sends each digit back to CUCM to be dialed (if it uses the SCCP protocol) or sends all digits at once, once the user has dialed (if using the SIP protocol). If a match is found in their dialplan on their CUCM the call will be routed/go through, otherwise the user would receive the "reorder tone" or busy signal.

Recommended Implementation - Campus Model

In this call processing deployment model, the Unified Communications services and the endpoints are co-located in the campus, and the QoS-enabled network between the service nodes, the endpoints, and applications is considered highly available, offering virtually unlimited bandwidth with less than 15 ms of latency end-to-end. Likewise, the quality and availability of power are very high, and services are hosted in an appropriate data center environment. Communications between the endpoints traverses a LAN or a MAN, and communications outside the enterprise goes over an external network such as the PSTN. An enterprise would typically deploy the campus model over a single building or over a group of buildings connected by a LAN or MAN.

The campus model typically has the following design characteristics:

•Single Cisco Unified CM cluster. Some campus call processing deployments may require more than one Unified CM cluster, for instance, if scale calls for more endpoints than can be serviced by a single cluster or if a cluster needs to be dedicated to an application such as a call center.

•Alternatively for smaller deployments, Cisco Business Edition 3000, 5000, or 6000 may be deployed in the campus.

•Maximum of 40,000 configured and registered Skinny Client Control Protocol (SCCP) or Session Initiation Protocol (SIP) IP phones, Cisco Cius, video endpoints, mobile clients, and Cisco Virtualization Experience Clients (VXC) per Unified CM cluster.

•Maximum of 2,100 gateways and trunks (that is, the total number of H.323 gateways, H.323 trunks, digital MGCP devices, and SIP trunks) per Unified CM cluster.

•Trunks and/or gateways (IP or PSTN) for all calls to destinations outside the campus.

•Co-located digital signal processor (DSP) resources for conferencing, transcoding, and media termination point (MTP).

•Other Unified Communications services, such as messaging (voicemail), presence, and mobility are typically co-located.

•Interfaces to legacy voice services such as PBXs and voicemail systems are connected within the campus, with no operational costs associated with bandwidth or connectivity.

•Multipoint Control Unit (MCU) resources are required for multipoint video conferencing. Depending on conferencing requirements, these resources may be either SCCP or H.323, or both.

•H.323 and H.320 video gateways are needed to communicate with H.320 videoconferencing devices on the public ISDN network.

•High-bandwidth audio is available (for example, G.722 or Cisco Wideband Audio) between devices within the site.

•High-bandwidth video (for example, 384 kbps or greater) is available between devices within the site. The Cisco Unified Video Advantage Wideband Codec, operating at 7 Mbps, is also supported.
Best Practices for the Campus Model

Follow these guidelines and best practices when implementing the single-site model:

•Ensure that the infrastructure is highly available, enabled for QoS, and configured to offer resiliency, fast convergence, and inline power.

•Know the calling patterns for your enterprise. Use the campus model if most of the calls from your enterprise are within the same site or to PSTN users outside your enterprise.

•Use G.711 codecs for all endpoints. This practice eliminates the consumption of digital signal processor (DSP) resources for transcoding, and those resources can be allocated to other functions such as conferencing and media termination points (MTPs).

•Implement the recommended network infrastructure for high availability, connectivity options for phones (in-line power), Quality of Service (QoS) mechanisms, and security. (See Network Infrastructure.)

•Follow the provisioning recommendations listed in the chapter on Call Processing.

What DNS Options Does Active Directory Offer in Windows Server 2008,2012,2016 ?

What Is Active Directory?

Active Directory is essentially an enhanced, centralized database with a set of objects that make user management, authorization, and data management simpler. Active Directory is synonymous with "Domain Controllers" where a single "domain" often consists of multiple sites and members of the domain. Multiple domains can also be joined to belong to a tree ( a collection of domains). And the highest layer is the forest which is created from multiple trees.

Active Directory can help provide DNS service by enabling the "DNS Server Role" which will allow members of a Domain to process DNS requests and create a highly available, fault-tolerant, redundant DNS design.

The first step is to ensure all relevant servers have the "Active Directory" role added and including the DNS portion.

The preferred method and setup is that the first DNS server should be set to the IP of another domain controller or DNS server that serves DNS and the secondary one should point to the localhost. DNS forwarders should be configured on each server that is running DNS, as this allows DNS resolutons to the outside to continue working in the event that one server hosting DNS goes down.

Best Practices According To Microsoft:

Question

What is Microsoft’s best practice for where and how many DNS servers exist? What about for configuring DNS client settings on DC’s and members?

Answer

It depends on who you ask. 🙂 We in MS have been arguing this amongst ourselves for 11 years now. Here are the general guidelines that the Microsoft AD and Networking Support teams give to customers, based on our not inconsiderable experience with customers and their CritSits:

If a DC is hosting DNS, it should point to itself at least somewhere in the client list of DNS servers.
If at all possible on a DC, client DNS should point to another DNS server as primary and itself as secondary or tertiary. It should not point to self as primary due to various DNS islanding and performance issues that can occur. (This is where the arguments usually start)
When referencing a DNS server on itself, a DNS client should always use a loopback address and not a real IP address.
Unless there is a valid reason not to that you can concretely explain with more pros than cons, all DC’s in a domain should be running DNS and hosting at least their own DNS zone; all DC’s in the forest should be hosting the _MSDCS zones. This is default when DNS is configured on a new Win2003 or later forest’s DC’s. (Lots more arguments here).
DC’s should have at least two DNS client entries.
Clients should have these DNS servers specified via DHCP or by deploying via group policy/group policy preferences, to avoid admin errors; both of those scenarios allow you to align your clients with subnets, and therefore specific DNS servers. Having all the clients & members point to the same one or two DNS servers will eventually lead to an outage and a conversation with us and your manager. If every DC is a DNS server, clients can be fine-tuned to keep their traffic as local as possible and DNS will be highly available with special work or maintenance. It also means that branch offices can survive WAN outages and keep working, if they have local DC’s running DNS.
We don’t care if you use Windows or 3rd party DNS. It’s no skin off our nose: you already paid us for the DC’s and we certainly don’t need you to buy DNS-only Windows servers. But we won’t be able to assist you with your BIND server, and their free product’s support is not free.
(Other things I didn’t say that are people’s pet peeves, leading to even more arguments).

Other Options

It should be noted that Active Directory Domain Controllers are not required to serve their own DNS and it is optional at the time of domain controller creation.

Another option that exists are the integration of Linux's NAMED or BIND DNS Server which is known to scale well and be extremely reliable.

Many cybersecurity experts believe this provides an enhanced level of performance and security, while still giving you the full features that Active Directory offers.

In general having a non-Microsoft DNS can offer you better performance and security. Securing your DNS servers is especially important, not only for DOS attacks but DNS poisoning especially due to privilege escalation or a compromise of a domain controller. This would allow an attacker to trick users into believing they were visiting a site they are not (eg. accounting may login to their online banking but unknowingly pass their details off to the hackers who have poisoned the DNS and sent them to a spoof site).

Here is a list of some of the value-added features offered by third-party DNS solutions available today:

Proactive automated adaptive behavior protection from DNS attacks, malware and data exfiltration through customized DNS firewall security
Utilize DNS and DHCP features that are unavailable from Microsoft in-box solutions such as Identity Mapping (linking IP addresses to users)
Intelligently resolve queries and direct traffic according to geographic location
Increased logging to help determine where issues and attacks are originating
Utilizing a single solution for external and internal DNS (aka "single view")
Operating system-agnostic way to manage DNS
Increased security by reducing admin privilege usage
Increased granularity for control of dynamic DNS updates via IP-based access-control, as opposed to the Microsoft's three-level approach of "none," "secure only" (i.e., AD-integrated clients (GSS-TSIG)) or "secure and insecure" (i.e., anyone, no TSIG or IP-based authentication required)

A good example is if you have 10 servers:

Server 1
Primary DNS: 172.16.254.2
Second DNS: 127.0.0.1
---------------------------------
Server 2
Primary DNS: 172.16.254.3
Second DNS: 127.0.0.1
---------------------------------
Server 3
Primary DNS: 172.16.254.4
Second DNS: 127.0.0.1
---------------------------------
Server 4
Primary DNS: 172.16.254.5
Second DNS: 127.0.0.1
---------------------------------
Server 5
Primary DNS: 172.16.254.6
Second DNS: 127.0.0.1
---------------------------------
Server 6
Primary DNS: 172.16.254.7
Second DNS: 127.0.0.1
---------------------------------
Server 7
Primary DNS: 172.16.254.8
Second DNS: 127.0.0.1
---------------------------------
Server 8
Primary DNS: 172.16.254.9
Second DNS: 127.0.0.1
---------------------------------
Server 9
Primary DNS: 172.16.254.10
Second DNS: 127.0.0.1
---------------------------------
Server 10
Primary DNS: 172.16.254.11
Second DNS: 127.0.0.1
---------------------------------

By setting up your DNS this way you are ensuring that should a domain member that provides DNS goes down that you have redundancy and the remaining servers will still function rather than if they were all relying on a single server as their secondary DNS source.

syntax error, unexpected T_SL in PHP Solution

This happened in a PHP script with heredoc but it could really happen anywhere. The issue was whitespace in code like this:

$variable = <<< HTML some stuff here $othervar HTML;

Notice on the first line that there is extra white space after the HTML. Whitespace was a deadly killer since it isn't obvious in terms of syntax.

grep regular expression match number range between specific numbers

grep -E servers1[2-6] somefile.txt

The 1 before the [ bracket means that the number must start with one and can be between 1 and [2-6] or in plain English between 12-16.

bash how to print out lines of text within a range from the first occurrence

#get line number of occurrence in text file and then print out x lines from that point

#get the line number of the first occurrence of our search text linenumber=`grep -n "someuniqueitem" inventory.txt|head -n1|cut -d ":" -f 1` #linestop represents how many lines after the occurring line we want to print out in this case "20" linestop=$((linenumber+20))

# sed prints out the line range we want for inventory.txt # note that the p after $linestop tells sed to print sed -n "$linenumber,$linestop p" inventory.txt

Combing it into one line:

linenumber=`grep -n "evodal07" inventory.txt|head -n1|cut -d ":" -f 1`&&sed -n "$linenumber,$((linenumber+20)) p" inventory.txt

bash script how to to check LAN computers for open ports

In this case it just searches for port 80 it is fairly handy if you have some sort of appliance or something else you aren't sure of the IP of

Of course change the port 80 port to whatever port(s) you want.

for ip in `arp -n|arp -n|tail -n +2|head -n -1 |grep -v incomplete|awk '{print $1}'`; do echo "checking $ip:80" nc -w 1 -z $ip 80 if [ "$?" == 0 ]; then echo "**Port 80 Open on $ip**" fi done