Removing a network channel bonding interface in Suse Linux 11

I have a Suse Linux 11 where someone made a backup copy before editing and it ended up starting a new bonding interface

root@linux:~ # cat /etc/*release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 3
Build no: 1565
Build date: Fri Aug 14 07:53:12 CEST 2015
Kiwi version: 7.02.58
LSB_VERSION=”core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64″

The interface is called bond4 and the backup file is /etc/sysconfig/network/ifcfg-bond4_original

root@linux:~ # cat /proc/net/bonding/bond4_original
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: None
MII Status: down
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: em50
MII Status: down
Speed: Unknown
Duplex: Unknown
Link Failure Count: 0
Permanent HW addr: 28:80:23:a5:c8:71
Slave queue ID: 0

Slave Interface: p6p2
MII Status: down
Speed: Unknown
Duplex: Unknown
Link Failure Count: 0
Permanent HW addr: 28:80:23:b3:07:dd
Slave queue ID: 0

I checked the configuration and ifcfg-bond4 and ifcfg-bond4_original are almost exactly the same file except for the parameter STARTMODE

root@linux:/etc/sysconfig/network # ls -l
total 108
-rw-r–r– 1 root root 14225 May 11 17:13 config
-rw-r–r– 1 root root 10590 May 11 17:16 dhcp
drwxr-xr-x 1 root root 108 May 11 17:13 if-down.d
drwxr-xr-x 1 root root 134 May 11 17:13 if-up.d
-rw——- 1 root root 303 May 11 17:13 ifcfg-bond2
-rw——- 1 root root 254 Jun 7 14:15 ifcfg-bond4
-rw——- 1 root root 254 Aug 16 10:26 ifcfg-bond4_original
-rw——- 1 root root 60 May 11 17:13 ifcfg-em49
-rw——- 1 root root 150 May 11 17:13 ifcfg-em50
-rw——- 1 root root 172 Jul 17 2015 ifcfg-lo
-rw——- 1 root root 189 May 11 17:13 ifcfg-p6p2
-rw——- 1 root root 164 May 11 17:13 ifcfg-p7p1
-rw——- 1 root root 164 May 11 17:13 ifcfg-p8p1
-rw——- 1 root root 252 May 11 17:13 ifcfg-vlan1700
-rw-r–r– 1 root root 29333 Jul 17 2015 ifcfg.template
-rw-r–r– 1 root root 239 Jul 17 2015 ifroute-lo
drwx—— 1 root root 0 May 5 2010 providers
-rw-r–r– 1 root root 26 Feb 8 2016 routes
drwxr-xr-x 1 root root 1722 May 11 17:17 scripts

Editing the file /etc/sysconfig/network/ifcfg-bond4_original

root@linux:/etc/sysconfig/network # vi ifcfg-bond4_original
BONDING_MASTER=’yes’
BONDING_MODULE_OPTS=’mode=active-backup miimon=100′
BONDING_SLAVE0=’em50′
BONDING_SLAVE1=’p6p2′
BOOTPROTO=’static’
BROADCAST=”
ETHTOOL_OPTIONS=”
IPADDR=”
MTU=”
NAME=”
NETWORK=”
REMOTE_IPADDR=”
STARTMODE=’off’
USERCONTROL=’no’

Removing the interfaces from the bonding

root@linux:~ # ifenslave -d bond4_original em50 p6p2

root@linux:~ # cat /proc/net/bonding/bond4_original
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: None
MII Status: down
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Removing the bonding

root@linux:~ # ifdown bond4_original
bond4_original

root@linux:~ # cat /proc/net/bonding/bond4_original
cat: /proc/net/bonding/bond4_original: No such file or directory

root@linux:~ # ls -l /proc/net/bonding
total 0
-r–r–r– 1 root root 0 Aug 16 10:41 bond2

How to disable purple alert box in Ghostery Firefox browser extension

To disable the purple alert box in Ghostery Firefox browser extension that appears in the right lower corner
ghostery1
Go to My Ghostery
ghostery2
Uncheck the option Show the purple box tracker list in the corner of my browser
ghostery3

NTP offset is over Critical threshold!

ATTENTION, RMC LEVEL 1 AGENT: This ticket will be automatically worked by the Automation Bus. Pls. ensure your Ticket List/View includes the

“Assignee” column, monitor this ticket until the user “ABOPERATOR” is no longer assigned, BEFORE you start work on this ticket.
Node : linux.setaoffice.com
Node Type : Intel/AMD x64(HTTPS)
Severity : critical
OM Server Time: 2016-07-25 18:54:18
Message : NTP offset is over Critical threshold!
Msg Group : OS
Application : ntpmon
Object : ntp
Event Type :
not_found

Instance Name :
not_found

Instruction : The ntpq -p command shows with one or more peers the
offset in time is greater than the threshold set in the
ntp_mon.cfg.

Please, review the ntp status of your system or increase
the threshold in the ntp_mon if you consider this offset
in time between the clocks of your system and the peer’s clock
is aceptable

Please check /var/opt/OV/log/OpC/ntp_mon.log for more details

Stopping ntp service

root@linux:~ # service ntp stop
Shutting down network time protocol daemon (NTPD) done

When I tried to run ntpdate in this Suse Linux Enterprise Server 11, I got an error message saying to use sntp

root@linux:~ # ntpdate ntpserver1
!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!!

The ntpdate program is deprecated and should not be used any more. To
quote the upstream ntp developers:

“The functionality ntpdate offered is now provided by the ntpd daemon
itself. If you call ntpd with the command line option -q it will
retrieve the current time and set it accordingly.”

Please check the Network Time Protocol (NTP) daemon man page and
http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate
for further information.

You can replace the ntpdate call with “rcntp ntptimeset” to achieve an
inital poll of the servers specified in /etc/ntp.conf.

The program /usr/sbin/sntp offers comparable functionality to ntpdate.
Specifically
sntp -P no -r pool.ntp.org
is equivalent to
ntpdate pool.ntp.org

For further details please refer to the man page of sntp.

root@linux:~ # cat /etc/*release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 3

I used my internal NTP server

root@linux:~ # sntp -P no -r ntpserver1

Started NTP server

root@linux:~ # service ntp start
Starting network time protocol daemon (NTPD) done

root@linux:~ # ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
ntpserver1 142.40.234.152 3 u 3 64 1 0.665 -27.640 0.001
ntpserver2 142.40.234.152 3 u 2 64 1 1.176 -17.426 0.001
142.40.5.45 .GPS. 1 u 1 64 1 11.257 -13.302 0.001

Check if the server lines in /etc/ntp.conf contain iburst

root@linux:~# grep server /etc/ntp.conf
server 142.40.234.152
server 142.40.234.153
server 10.32.5.29

root@linux:~ # vi /etc/ntp.conf

root@linux:~ # grep server /etc/ntp.conf
server 142.40.234.152 iburst
server 142.40.234.153 iburst
server 10.32.5.29 iburst

I was also having an reoccurence of this problem so I had to set the offset in ntp_mon.cfg

root@linux:~ # ls -l /var/opt/OV/conf/OpC/ntp_mon.cfg
ls: cannot access /var/opt/OV/conf/OpC/ntp_mon.cfg: No such file or directory

root@linux:~ # cp /var/opt/OV/bin/instrumentation/ntp_mon.cfg /var/opt/OV/conf/OpC

root@linux:~ # vi /var/opt/OV/conf/OpC/ntp_mon.cfg
###############################################################################
#@(#) $Id: ntp_mon.cfg 2149 2015-03-03 08:45:34Z zhaofeif $
#@(#) $Rev: 2149 $
#@(#) $Author: zhaofeif $
#@(#) $Date: 2015-03-03 16:45:34 +0800 (Tue, 03 Mar 2015) $
#@(#) $LastChangedBy: zhaofeif $
###############################################################################

############################################
# NTP_MON.CFG
# DESCRIPTION
#——————-
# Monitoring the NTP Daemon
# You can configure the monitoring to watch over
# the offset reported by the ntpq -p command
#
# PARAMS DESCRIPTION
#——————————
# [REARM = TRUE|FALSE]
# If set TRUE (or true), rearm function is enabled, default is disabled
#
# “DISABLE =[yes|no]” : This is the switch for ntpmon running
# NTP_OFFSET_CRITICAL,NTP_OFFSET_WARNING set offset critical and warning threshold for active peer, devaut values are 500 and 250 in ms
# NTP_STRATUM_CRITICAL, NTP_STRATUM_WARNING set offset of stratum of peers which status are one of “*”, “o”, “+” or “#”, the default value are 16 and 10
# NTP_ONLINE_TIME , ntpmon will not check anything if process ntpd is not running more than NTP_ONLINE_TIME(minutes), default value is 10(min)
# ALARM_DELAY, ntpmon allow to delay triggering alarm by setting minutes.
#——————————
# PARAMS REQUIRED
#———————————–
#
# CONFIG FILE
#————————–
############################################
#
# EXAMPLE:
#
#
#################################################################
#
# Set your configuration from here
#REARM = TRUE

DISABLE = NO
NTP_OFFSET_CRITICAL 1500
NTP_OFFSET_WARNING 500
NTP_STRATUM_CRITICAL 15
NTP_STRATUM_WARNING 12
NTP_ONLINE_TIME 3
#ALARM_DELAY 60

# Set your configuration from here

Problems with a NFS share coming from a Linux server and mounted on Linux client

Running df or ls in a NFS share it simply hangs.

See if df or ls hangs. Run strace df -h or strace ls -l and see if it finishes

root@linux:~ # strace df -h

root@linux:~ # strace ls -l

statfs(“/mnt/NFS”,

Umount with -f or -l

-f, –force
Force an unmount (in case of an unreachable NFS system). (Requires kernel 2.1.116 or later.)

Note that this option does not guarantee that umount command does not hang. It’s strongly recommended to use absolute paths without symlinks to avoid unwanted readlink and stat syscalls on unreachable NFS in umount.
-l, –lazy
Lazy unmount. Detach the filesystem from the file hierarchy now, and clean up all references to this filesystem as soon as it is not busy anymore. (Requires kernel 2.4.11 or later.)

HP-UX vgdisplay: Cannot display volume group “/dev/vgWP0log1_stage”

Listing volume groups available in the server, it showed me a message where it can’t display some volume groups

root@hpux:~ # vgdisplay | grep Name
VG Name /dev/vg00
VG Name /dev/vg01
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group “/dev/vgWP0log1_stage”.
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group “/dev/vgWP0log2_stage”.
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group “/dev/vgECPlog1_stage”.
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group “/dev/vgECPlog2_stage”.
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group “/dev/vgXPTO_stage”.
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group “/dev/vgSCP_stage”.
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group “/dev/vgSCPdat1_stage”.
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group “/dev/vgSCPjc_stage”.
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group “/dev/vgSCPlog1_stage”.
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group “/dev/vgSCPlog2_stage”.

This server had all the LUNs removed. So in this case I can remove the volume group from the system

root@hpux:~ # vgexport vgWP0log1_stage
vgexport: Volume group “vgWP0log1_stage” has been successfully removed.

su: (to novlwww) root on /dev/console

Jul 21 12:14:48 linux init: Switching to runlevel: 6
Jul 21 12:14:49 linux kernel: [19793592.659965] bootsplash: status on console 0 changed to on
Jul 21 12:15:01 linux syslog-ng[20531]: Log statistics; dropped=’pipe(/dev/xconsole)=0′, dropped=’pipe(/dev/tty10)=0′, processed=’center(queued)=1287386′, processed=’center(received)=1287371′, processed=’destination(messages)=2824′, processed=’destination(mailinfo)=15′, processed=’destination(mailwarn)=0′, processed=’destination(localmessages)=0′, processed=’destination(mailerr)=0′, processed=’destination(newserr)=0′, processed=’destination(netmgm)=0′, processed=’destination(warn)=0′, processed=’destination(console)=0′, processed=’destination(null)=0′, processed=’destination(mail)=15′, processed=’destination(xconsole)=0′, processed=’destination(httpheaders)=63703′, processed=’destination(firewall)=0′, processed=’destination(agsmessages)=1220828′, processed=’destination(acpid)=1′, processed=’destination(soapmessages)=0′, processed=’destination(newscrit)=0′, processed=’destination(newsnotice)=0′, processed=’source(src)=1287371′
Jul 21 12:15:03 linux su: (to novlwww) root on /dev/console
Jul 21 12:15:09 linux sshd[3877]: Received signal 15; terminating.
Jul 21 12:15:09 linux xinetd[5386]: Exiting…
Jul 21 12:15:10 linux auditd[2994]: The audit daemon is exiting.
Jul 21 12:15:10 linux haveged: haveged stopping due to signal 15
Jul 21 12:15:11 linux rpcbind: rpcbind terminating on signal. Restart with “rpcbind -w”
Jul 21 12:15:11 linux kernel: Kernel logging (proc) stopped.
Jul 21 12:15:11 linux kernel: Kernel log daemon terminating.
Jul 21 12:15:11 linux syslog-ng[20531]: Termination requested via signal, terminating;
Jul 21 12:15:11 linux syslog-ng[20531]: syslog-ng shutting down; version=’2.0.9′
Jul 21 12:18:03 linux syslog-ng[2937]: syslog-ng starting up; version=’2.0.9′

This server was rebooted by the user through NAM (Novell Access Manager) Console

Multipathed disk showing error message: Checksum error

Running pvs shows the error message Checksum error and the disk is not part of a volume group

root@linux:~ # pvs | grep NP0_trans_disk_002
/dev/mapper/NP0_trans_disk_002: Checksum error
Couldn’t read volume group metadata.
/dev/mapper/NP0_trans_disk_002: Checksum error
Couldn’t read volume group metadata.
/dev/mapper/NP0_trans_disk_002: Checksum error
Couldn’t read volume group metadata.
/dev/mapper/NP0_trans_disk_002 lvm2 — 50.00g 50.00g

Check all the files inside directory /etc/lvm/backup if there is a file containing the disk that is showing Checksum error

root@linux:~ # cd /etc/lvm/backup
root@linux:~ # grep NP0_trans_disk_002 *
vgNP0trans: device = “/dev/mapper/NP0_trans_disk_002” # Hint only

Restore the volume group configuration

root@linux:~ # vgcfgrestore -f /etc/lvm/backup/vgNP0trans vgNP0trans
/dev/mapper/NP0_trans_disk_002: Checksum error
Couldn’t read volume group metadata.
Restored volume group vgNP0trans

The physical volume starts starts showing volume group information

root@linux:~ # pvs | grep NP0_trans_disk_002
/dev/mapper/NP0_trans_disk_002 vgNP0trans lvm2 a– 46.02g 8.00m

NetIQ Remote Loader

SAP System ID: SMD
Logon Group:
SAP System id: 04
SAP User client number: 100
Logical System Name: SMDCLNT100
Authentication ID: IDM_CPIC
Authentication context: ascssmd.sap.valeglobal.net
Remote Loader connection parameters: hostname=ascssmd.sap.valeglobal.net port=13073 kmo=’sap_dev’

File where some configuration is found

root@linux:/usr/sap/SMD/NOVELL_RemoteLoader # cat config.txt
################################################################################
# Sample configuration file for rdxml or dirxml_jremote. See usage.html for
# descriptions and explanations of these and other available parameters.
#
# This sample demonstrates a configuration for loading the Delimited Text
# driver.
################################################################################
-description “Integration IDM SAP”
-commandport 14033
-connection “address=10.106.136.33 port=13033 handshaketimeout=1000000 keystore=sap_dev.keystore storepass=dirxml”
-trace 10
-tracefile ./trace.log
-tracefilemax 10M
-class com.novell.nds.dirxml.driver.sapumshim.SAPDriverShim

Problems with a NFS share coming from a Linux server and mounted on Linux client

Running df or ls in a NFS share it simply hangs.

See if df or ls hangs. Run strace df -h or strace ls -l and see if it finishes

root@linux:~ # strace df -h

root@linux:~ # strace ls -l

statfs(“/mnt/NFS”,

Try to umount with -f or -l

-f, –force
Force an unmount (in case of an unreachable NFS system). (Requires kernel 2.1.116 or later.)

Note that this option does not guarantee that umount command does not hang. It’s strongly recommended to use absolute paths without symlinks to avoid unwanted readlink and stat syscalls on unreachable NFS in umount.

-l, –lazy
Lazy unmount. Detach the filesystem from the file hierarchy now, and clean up all references to this filesystem as soon as it is not busy anymore. (Requires kernel 2.4.11 or later.)

NetIQ Remote Loader: JCO_ERROR_LOGON_FAILURE: Initialization of repository destination SAP-GRC_PRIMCONN failed: Password logon no longer possible – too many failed attempts

DirXML: [07/11/16 08:15:03.685]: TRACE: Remote Loader: Sending…
DirXML: [07/11/16 08:15:03.686]: TRACE:

Identity Manager Driver for User Management of SAP Software Novell, Inc.

 

com.novell.nds.dirxml.driver.sapumshim.BapiException: Error authenticating to SAP host: com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Initialization of repository destination SAP-GRC_PRIMCONN failed: Password logon no longer possible – too many failed attempts on ascsND0.setaoffice.com sysnr 01

Asked SAP team to reset the user IDM_CPIC

%d bloggers like this: