Summary
The vStor 4.6 update may hang on a vStor that is also a DPX master server. The first messages indicating a problem are "short option is not supported with getopt_long_only call, ignored" and "logger: --t: unknown option". This followed by the start of the DPX logger module.
Symptoms
During the update of vStor 4.6 on a DPX master server, the update may hang reporting:
short option is not supported with getopt_long_only call, ignored
logger: --t: unknown option
Sat Dec 14 17:15:11 2019 SNBGEN1110I LogFile(/opt/DPX/logs/sslogger.log) opened by Module(logger)
Sat Dec 14 17:15:11 2019 SNBGEN1111I Module Build ID:[arch(Linux-amd64) ver(4.5) build_time(12:41:29) build_date(Jun 22 2019)]
Sat Dec 14 17:15:11 2019 SNBGEN1113I Process Info:[pid(19440) user(root) cmdline(logger -t os-prober)]
Sat Dec 14 17:15:11 2019 SNBGEN1112I Env:SSPRODIR(/opt/DPX)
Sat Dec 14 17:15:11 2019 SNBGEN1112I Env:SSICMAPI(-a 6123 -tnd -sbs 65535 -lcl no -ska on -c x)
SNBMSG: Invalid error message 1 issued
Sat Dec 14 17:15:11 2019 SNBLGC0002I Environment - NODE: brinkley.csse.catalogic.us MACHINE: x86_64
Sat Dec 14 17:15:11 2019 SNBLGC0003I Environment - SYSTEM: Linux RELEASE: 3.10.0-862.el7.x86_64 VERSION: #1 SMP Fri Apr 20 16:44:24 UTC 2018
Sat Dec 14 17:15:11 2019 SNBGEN3066D Appending (-lcl no) to SSICMAPI (pattern=(mod(<NULL>)))
Sat Dec 14 17:15:11 2019 SNBGEN3066D Calling cm_init2 with ssenv=( -lcl no)
Sat Dec 14 17:15:11 2019 SNBGEN3066D ms_register_module_str: listening on TCP port 7
Sat Dec 14 17:15:11 2019 SNBLGC1011I Listening on socket 0
Resolution
This occurs when these conditions are true:
1. The vStor is also a DPX master server.
2. The DPX environment has been set with bexenv
At this point, the update must be interrupted (<CTRL-C>), the path reset and the update restarted. After interrupting the update, get the value of the PATH, which may look like:
# echo $PATH
/opt/DPX/bin:/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/5bin:/usr/share:/usr/ucb:/usr/local/bin:/usr/etc:/etc:/usr/ccs/bin:/bin/posix:/usr/contrib/bin
In this example, the DPX bin directory is at the beginning of the path. It is sufficient to reset the path to:
# export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin
The update can then be run again as it was before. If the option to update the kernel was selected before, it should be selected again, though much of the work that was done in the first attempt will likely not be repeated.