Author: Emerson .

Outlook 2013 Message Preview Message Text Turned Blue After Update

After you update Outlook 2013, you will start to notice that the preview message text turned blue
Outlook
To fix it, go to View Tab -> View Settings -> Other Settings and then click the button Font under Message Preview section.

Change the color to Auto or Black

Outlook2

You need to change the color for each folder in Outlook

error while loading shared libraries: libnl.so.1

error while loading shared libraries: libnl.so.1

Check which package provides the library that you want.

On Red Hat Linux you can check running yum whatprovides. On my case, I need to install libnl to solve my problem

root@linux:~ # yum whatprovides */libnl.so.1
Loaded plugins: downloadonly, rhnplugin, security

libnl-1.0-0.10.pre5.4.i386 : Convenience library for kernel netlink sockets
Repo : internalrepository
Matched from:
Filename : /usr/lib/libnl.so.1

libnl-1.0-0.10.pre5.5.i386 : Convenience library for kernel netlink sockets
Repo : internalrepository
Matched from:
Filename : /usr/lib/libnl.so.1

libnl-1.0-0.10.pre5.5.x86_64 : Convenience library for kernel netlink sockets
Repo : internalrepository
Matched from:
Filename : /usr/lib64/libnl.so.1

libnl-1.0-0.10.pre5.4.x86_64 : Convenience library for kernel netlink sockets
Repo : internalrepository
Matched from:
Filename : /usr/lib64/libnl.so.1

lvlnboot: Boot volume should be the first logical volume on the physical volume

If you run lvlnboot and try to set the boot volume but it gives you the error saying that the boot volume should be the first logical volume

root@hpux:~ # /usr/sbin/lvlnboot -b /dev/vg00/lvol1
lvlnboot: Boot volume should be the first logical volume on the physical volume

Check with pvdisplay and check which volume shows on the Physical Extents section. It must match with the logical volume you’re declaring above.

In this case, it should show /dev/vg00/lvol1 instead of /dev/vg00/lvermhome

root@hpux:~ # pvdisplay -v /dev/disk/disk31_p2 | more
— Physical volumes —
PV Name /dev/disk/disk31_p2
VG Name /dev/vg00
PV Status available
Allocatable yes
VGDA 2
Cur LV 11
PE Size (Mbytes) 32
Total PE 3171
Free PE 1323
Allocated PE 1848
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On
Proactive Polling On

— Distribution of physical volume —
LV Name LE of LV PE for LV
/dev/vg00/lvol1 56 56
/dev/vg00/lvol2 256 256
/dev/vg00/lvol3 160 160
/dev/vg00/lvol4 64 64
/dev/vg00/lvol5 160 160
/dev/vg00/lvol6 64 64
/dev/vg00/lvol7 320 320
/dev/vg00/lvol8 160 160
/dev/vg00/lvol9 256 256
/dev/vg00/lvol10 320 320
/dev/vg00/lvermhome 32 32

— Physical extents —
PE Status LV LE
00000 current /dev/vg00/lvermhome 00000
00001 current /dev/vg00/lvermhome 00001
00002 current /dev/vg00/lvermhome 00002

I mirrored a new disk to replace the old boot disk. So that’s why it showed this message in this case.

Default vsftpd log file location

The default log location for vsftpd is not /var/log/vsftpd.log

It is on /var/log/xferlog

root@linux:~ # cat /etc/vsftpd/vsftpd.conf
# The target log file can be vsftpd_log_file or xferlog_file.
# This depends on setting xferlog_std_format parameter
xferlog_enable=YES

# The name of log file when xferlog_enable=YES and xferlog_std_format=YES
# WARNING – changing this filename affects /etc/logrotate.d/vsftpd.log
xferlog_file=/var/log/xferlog

If syslog_enable is set, vsftpd will log everything to /var/log/messages

UXMON: ServiceGuard: Package(s) are running on ADOPTIVE node(s): infraHP0 (linux02)

UXMON: ServiceGuard: Package(s) are running on ADOPTIVE node(s): infraHP0 (linux02)

Node : linux01.setaoffice.com
Node Type : Intel/AMD x64(HTTPS)
Severity : major
OM Server Time: 2016-02-22 14:54:56
Message : UXMON: ServiceGuard: Package(s) are running on ADOPTIVE node(s): infraHP0 (linux02)
Msg Group : OS
Application : sgmon
Object : cmviewcl
Event Type :
not_found

Instance Name :
not_found

Instruction : Check with cmviewcl -v;

If package was down the customer has to be informed about the downtime.

Do not close this case before it is resolved.
As long as this EWM-case is not resolved or closed, monitoring is disabled
In any case inform technical lead!

This ticket is about the cluster package that it is running on alternate node.

root@linux:~ # cp -p /var/opt/OV/bin/instrumentation/sg_mon.cfg /var/opt/OV/conf/OpC/sg_mon.cfg
root@linux:~ # vi /var/opt/OV/conf/OpC/sg_mon.cfg
# PKG[0]=XYZ Package name 1
# PKG_NODE[0]=ABC Primary node on which the package must run
# Define as * will disable running on adoptive node check
# PKG_SWTCH[0]=1 Set to 1 if Package_switching should be ENABLED
# Set to 0 if Package_switching must not be ENABLED

In our case, it was disabled the node check for the package

root@linux:~ # vi /var/opt/OV/conf/OpC/sg_mon.cfg
PKG[0]=infraHP0; PKG_NODE[0]=*; PKG_SWTCH[0]=0

UX:vxfs fsadm: ERROR: V-3-20279: /dev/volumegroup/logicalvolume is not the root inode of a vxfs file system

I ran fsadm on the device and it showed this error message

root@hpux:~ # fsadm -F vxfs -b 14336M /dev/vgSAPappls/lvusrsapWP0
UX:vxfs fsadm: ERROR: V-3-20279: /dev/vgSAPappls/lvusrsapWP0 is not the root inode of a vxfs file system

I needed to run in the mount point

root@hpux:~ # fsadm -F vxfs -b 14336M /usr/sap/WP0
UX:vxfs fsadm: INFO: V-3-25942: /dev/vgSAPappls/rlvusrsapWP0 size increased from 10485760 sectors to 14680064 sectors

The LUN callback routine has failed the LUN destroy request as there are 1 active opens on the LUN

Node : hpux.setaoffice.com
Node Type : Itanium 64/32(HTTPS)
Severity : major
OM Server Time: 2016-02-16 14:45:48
Message : DMESG-UNCLASSIFIED: The LUN callback routine has failed the LUN destroy request as there are 1 active opens on the LUN (64000/0xfa00/0x5c).
Msg Group : OS
Application : HPUX_dmesg
Object : dmesg_UNCLASSIFIED
Event Type :
not_found

Instance Name :
not_found

Instruction : No

We found a LUN that we are unable to remove

root@hpux:~ # ioscan -fNC disk | grep NO_HW
disk 825 64000/0xfa00/0x5c esdisk NO_HW DEVICE offline HP OPEN-V

root@hpux:~ # ioscan -fNC disk | grep 825
disk 825 64000/0xfa00/0x5c esdisk NO_HW DEVICE offline HP OPEN-V
/dev/disk/disk825 /dev/rdisk/disk825

Edited file /var/opt/OV/conf/OpC/dmsg_mon.cfg to include the string 64000/0xfa00/0x5c to not trigger this alarm

Feb 16 17:58:13 hpux vmunix: The LUN callback routine has failed the LUN destroy request as there are 2 active opens on the LUN (64000/0xfa00/0x5c).
Feb 16 18:16:59 hpux vmunix: The LUN callback routine has failed the LUN destroy request as there are 1 active opens on the LUN (64000/0xfa00/0x5c).

Received disconnect from host: 2: Too many authentication failures for username

root@linux:~ # ssh emerson@10.32.36.45
Received disconnect from 10.32.36.45: 2: Too many authentication failures for emerson

The problem was that my server 10.32.36.45 tried to authenticate using a method and then gave up.

To fix it, edit file /etc/ssh/sshd_config and increase MaxAuthTries. On my server was just trying 1 time.

root@linux:~ # vi /etc/ssh/sshd_config
#MaxAuthTries 1

You can try to not use ssh keys to login but I commented the parameter to restore the default value and restarted the sshd service

root@linux:~ # service sshd restart
Stopping sshd: [ OK ]
Starting sshd: [ OK ]

Does my Mad Catz Tournament Edition Arcade Stick for PS3 works on PC / PS4 / Street Fighter 5?

Your Mad Catz Tournament Edition Arcade Stick for PS3 will work as a DirectInput device on your PC.

DirectInput was the standard for PC controllers before XInput made available for both the Xbox 360 and Windows XP with Service Pack 1 (SP1) and later, and Windows Vista. XInput is the new API where your controller is recognized as a Xbox 360 controller.

Most new games will expect a Xbox 360 controller. You can use “Xbox 360 Controller Emulator” that will allow your controller (gamepad, joystick, wheel, etc.) to function as an Xbox 360 controller.

You can also install Motion in Joy drivers with the Better DS3

Your Mad Catz Tournament Edition Arcade Stick for PS3 will be recognized as a PS3 controller on the PS4, so it won’t work. PS3 sticks by default are not compatible with PS4. The game developers need to enable it.

LabZero developed a custom driver that allowed any stick that reads as a generic USB gamepad or joystick would work with the PS4 version of its fighting game Skullgirls Encore. Capcom used that driver to make PS3 arcade sticks compatible with Ultra Street Fighter IV.

How to get your PS3 stick to work for USF4 on PS4: Follow these steps released by Capcom, similar to Mortal Kombat X

Street Fighter V for PS4 is not released yet so nothing confirmed. Capcom Still Evaluating Legacy Controller Support for Street Fighter V

Update: Capcom confirms Street Fighter V will support PS3 arcade sticks Street Fighter V Day One Update Adds Legacy Controller Support, Alex Coming in March

systool – Query information about Fibre Channel HBA card on a Linux server

To query information about Fibre Channel HBA cards, use systool

root@linux:~ # which systool
/usr/bin/systool

Install the package sysfsutils using yum install systool if you have a Red Hat based distribution

root@linux:~ # rpm -qf /usr/bin/systool
sysfsutils-2.1.0-7.el6.x86_64

root@linux:~ # rpm -qi sysfsutils
Name : sysfsutils Relocations: (not relocatable)
Version : 2.1.0 Vendor: Red Hat, Inc.
Release : 7.el6 Build Date: Thu 20 Sep 2012 10:11:43 AM BRT
Install Date: Fri 23 May 2014 12:17:31 PM BRT Build Host: x86-012.build.bos.redhat.com
Group : Development/Tools Source RPM: sysfsutils-2.1.0-7.el6.src.rpm
Size : 117100 License: GPLv2
Signature : RSA/8, Fri 09 Nov 2012 09:27:58 AM BRST, Key ID 199e2f91fd431d51
Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla&gt;
URL : http://sourceforge.net/projects/linux-diag/
Summary : Utilities for interfacing with sysfs
Description :
This package’s purpose is to provide a set of utilities for interfacing
with sysfs.

root@linux:~ # cat /etc/*release
LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Red Hat Enterprise Linux Server release 6.5 (Santiago)
Red Hat Enterprise Linux Server release 6.5 (Santiago)