|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
HP-UX series 700 11.X patch digest
From: IT Resource Center (support_feedback
us-support2-mail.external.hp.com)
Date: Sun May 11 2003 - 18:50:44 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
HP Support Information Digests
===============================================================================
o IT Resource Center World Wide Web Service
---------------------------------------------------
If you subscribed through the IT Resource Center and would
like to be REMOVED from this mailing list, access the
IT Resource Center on the World Wide Web at:
http://support.itrc.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Support Information Digests (located under
Maintenance and Support). You may then unsubscribe from the
appropriate digest.
To download a patch referenced below, access the
IT Resource Center on the World Wide Web at:
http://support.itrc.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Individual Patches (under Maintenance and Support)
to access the patch. You may also download a patch via anonymous
ftp(1) from ftp.itrc.hp.com.
===============================================================================
Digest Name: weekly HP-UX series 700 11.X patch digest
Created: Sun May 11 7:05:36 EDT 2003
Table of Contents:
Document ID Title
--------------- -----------
PHSS_28943 s700_800 11.X OV ITO7.1X Windows Agent A.07.20
PHSS_28820 s700_800 11.X OV ITO7.1X HP 10.20 Embedded Perf Agt A.07.15
PHCO_29052 s700_800 11.04 (VVOS) vvosmta(1M) enhancement
PHSS_28958 s700_800 11.X OV ITO7.1X HP-UX 11.00/11.11 Agent A.07.20
PHSS_28922 s700_800 11.X OV ECS3.20 Intermediate Patch April 2003
PHNE_28183 s700_800 11.00 R6.11.00 SNAplus2 Link/Common, TN3270 patch
PHKL_28665 s700_800 11.11 PCI-X enablement for OLA/R subsystem
PHKL_28569 s700_800 11.11 INTRMIGR enabler, WSIO support patch
PHKL_28464 s700_800 11.11 IPMI driver port, LUN change
PHCO_28769 s700_800 11.11 nPar cmds cumulative patch,IOX,dual cpu
PHCO_28666 s700_800 11.11 PCI-X enablement for rad(1M) command
PHCO_27847 s700_800 11.00 cumulative patch for syslogd(1M)
PHSS_28968 s700_800 11.X OV ITO7.1X JavaGUI client A.07.14
PHSS_28962 s700_800 11.X OV ITO7.1X server patch A.07.15
PHSS_28825 s700_800 11.X OV ITO7.1X Solaris Embedded Perf Agt A.07.15
PHSS_28821 s700_800 11.X OV ITO7.1X 11.X Embedded Perf Agent A.07.15
PHNE_28588 s700_800 11.00 EISA FDDI B.11.00.0[0-7] cumulative patch
PHNE_28143 s700_800 11.00 LAN product cumulative patch
PHCO_28998 s700_800 11.11 fbackup(1M),frecover(1M) cumulative patch
PHCO_28719 s700_800 11.11 wall(1M) patch
PHCO_28718 s700_800 11.00 wall(1M) patch
PHCO_28247 s700_800 11.11 script(1) cumulative patch
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_28943
Date Loaded: 20030508
Title: s700_800 11.X OV ITO7.1X Windows Agent A.07.20
Patch Name: PHSS_28943
Patch Description: s700_800 11.X OV ITO7.1X Windows Agent A.07.20
Creation Date: 03/04/30
Post Date: 03/05/08
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
OpenView Operations 7.1
Filesets:
OVOPC-CLT.OVOPC-NT-CLT,fr=A.07.10,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-CLT.OVOPC-NT-CLT,fr=A.07.10,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28943
Symptoms:
PHSS_28943:
- SR: B555015785
opcecaas may report that it runs out of free process
slots and therefore can't start anymore process.
- SR: 8606294668
The trap interceptor does not use new/changed
templates/policies when doing SNMP trap interception on a
Windows system that has NNM installed.
- SR: B555015674
The Windows agent installation may abort with the error
that the node is already managed by a different
management server.
The inst.log and the command line output on the node you
are installing to may contain:
E-> NOTE: VPO software, version A.0X.X installed on
system <node name>, belongs to Management Server
<management server name>.
- SR: 8606282084
The change between multiple managements doesn't work,
because the configuration file primmgr - that has higher
priority for agent, is not updated by the
'SwitchMgmtServer.cmd' tool that uses 'mgmt_sv.vbs'
script.
- SR: B555016133
opcwbemi.exe may abort while stopping the agent on
Microsoft Windows XP.
- SR: B555015741
During the shutdown of a system, the agent processes
still try to start new processes, causing pop up windows.
- SR: B555015449
Monitor agent may abort while receiving
templates/policies.
- SR: 8606290346
After installing a new version the registry key
HKLM\SOFTWARE\Hewlett-Packard\OpenView\ITO\Agent Version
remains at A.07.10.
- SR: B555015199
If OPC_IP_ADDRESS (nodeinfo) and OPC_NAMESRV_LOCAL_NAME
(opcinfo) were used in combination the entry in
OPC_IP_ADDRESS was not used in the right way.
- SR: B555015557
The current implementation of the control agent does not
allow to restart aborted sub agent processes
automatically.
- SR: 8606303962
After time change (beginning of daylight saving time),
all logfiles are read from the beginning.
- SR: B555015700
Agent often fails to shut down from the services control
panel in time. It also fails to stop in time during the
uninstall/redeployment of the agent software.
- SR: 8606299704
You may get the error
"Cannot open file <$...>. System Error Number: ... -
(OPC20-63)"
when using environment variables in the "File to be Read"
field of a logfile policy/template.
- SR: B555015170
During distribution of templates, the agent might report
that 'The codeset "-1" is incompatible to the codeset
"acp1252"'.
- SR: B555015758
opcmsgi aborts if one of the set attributes has an
unmatched '<'.
- SR: 8606290908
The OVO Windows agent may loos it's AgentID when
doing a "Redeploy All" or installing an agent package
with a higher version. In case this happens, Service
Discovery may stop working correctly.
- SR: B555015770
Agent should report the current internal status of
policies. The Flag OPC_TEMPL_STATUS TRUE can be set now,
reporting the status for monitors and logfile policies in
the two files 'monitor.status' and 'le.status' in
'%OvAgentDir%\tmp\OpC'.
- SR: B555015771
opcmona.exe may sometimes fail to start and show up a
message box that a certain ordinal can not be found.
- SR: B555015325
opcmsga wrongly generates a message OpC30-3002 'opcctla
not running on node localhost.' when receiving a
reconfigure signal, or at exit time.
- SR: H555008529
If a process dies immediately after being started by the
Control Agent, it is possible that OpC30-1094 messages
start appearing in the error logfile.
- SR: 8606297998
The ECS engine (opcecm & opceca) might have problems
when a circuit is using global dictionaries.
(This is the case for the MessageStorm detection ECS
circuit).
- SR: B555008674
The opcagt and the opcragt commands have a new option
'-version'. In both man pages, this was not documented.
The new option was not part of the usage strings of
opcagt and opcragt.
- SR: B555015378
The agent might not be able to monitor instances of the
LogicalDisk object and returns no data for it at all.
- SR: B555014942
The opcle process loops if a logfile is removed while
it is read.
- SR: B555014851
opcmsga sends the same message operation (e.g. an
acknowledge request created by opcmack(1) )
again and again if the related message is not in the
cache and one of the target managers can not be reached.
- SR: B555016032
The process opcapm.exe may show a memory leak during
runtime.
- SR: B555015912
Agent installation fails when ntmsgm.dll is in use by
other process
- SR: B555015484
You might not be able to install the agent either through
server based deployment or manual agent installation. In
case Dr. Watson is configured you will see there, that
the opcsetup.exe aborted.
The problem can also show up during agent runtime. In
this case you may not be able to execute any commands
through the agent.
- SR: 8606293840
Monitor agent and Event interceptor grow in memory.
- SR: B555015496
Queue file handling was inefficient for larger queue
files.
- SR: B555015485
In this case the cause was a mapped network drive listed
in the system environment variable PATH.
Every time the agent tries to execute an external
command, the PATH might be scanned by the used Windows
APIs.
This is causing a login error on the PC providing the
network share and in case this PC also has the "HP ITO
account" it will lock this account.
- SR: B555015441
Action agent aborts when process table is full. This
happens when more than 52 tools/actions are called from
the console in parallel.
- SR: 8606290675
Agent should report 'agent start' into the opcerror file.
- SR: R555018185
If the agent is started in Simplified Chinese codeset,
monitor agent, logfile encapsulator and message
interceptor processes will fail.
- SR: B555015155
Errors in the opcerror file are not written to the trace
file. This makes it difficult to find the place in the
trace file where the error occured.
- SR: 8606280846
Monitor Agent often reports 'Evaluation of policy
stopped'.
- SR: B555015277
The NT monitor agent aborts in process-monitoring policy
when the 'ID Process' performance counter exists twice in
the performance registry.
- SR: B555015331
The monitor agent, opcmona, may report wrong results of
executed monitor scripts or programs when using many
'advanced monitors' such as OVPERF. In some of these
cases opcmona might even abort.
- SR: B555015712
The trap/event interceptor forwards traps with the source
address 127.0.0.1 unchanged, therefore they are discarded
by the management server due to the unknown source
address.
- SR: 8606232431
VPO tries to resolve node names that only contain blanks
because of typo in template definition or variable
assignment. This leads to a lot of unnecessary DNS
traffic.
- SR: 8606300119
The logfile encapsulator does not return the last line of
a logfile immediatelly, if there is no carriage return in
this line.
PHSS_28501:
- SR: 8606290723
You may get errors about commands or DLLs that can not be
found while executing a command or batch file using the
OVO Windows agent. This behavior has been seen with the
DBSPI very often.
- SR: B555015349
The monitor agent might abort while using
templates/policies
that have an external source specified.
- SR: B555015308
When configuring the agent with apminfo.xml
to be cluster aware, the agent may not install newly
deployed policies correctly.
PHSS_27388:
- SR: B555013936
agent installation may fail with a high number of the
following messages in the inst.log:
T-> Tracing information: Can't get status for service:
...
It can even happen that the install script reports
successfull but nothing gets installed.
This may happen when you have installed HP OpenView
Internet Services and not all MS Internet Information
Services.
- SR: B553003927
opcmsgi leaks memory when handling messages with custom
message attributes.
- SR: B555014999
The start of batch files (.bat|.cmd) with Tools/Automatic
or Operator initiated actions by using the OVO Agent on
Windows NT may fail with a an error saying, the command
is not found.
- SR: B555014328
opcevti.exe may abort when using <$x>.
- SR: B555015077
Installation server always receives version A.07.10
to be installed on the target node.
This causes problems in case the installation server just
knows A.07.12 but not A.07.10.
- SR: B555014961
The OVO agent should be able to execute tools and
scheduled commands for either the "HP ITO account" or the
SYSTEM account user. Or any other user currently running
the agent. In any case this should work without a switch
user.
- SR: B555014634
The OVO Windows agent may not pickup the SYSTEM event log
entries with ID 6008 or 6009 during the system is
rebooted.
Or in other cases the opcle may go to 100 % CPU time for
several minutes during startup.
- SR: B555013965
The pdh.dll delivered with the agent
has a memory leak as it is described
in Microsoft article: Q263221.
- SR: B555013978
In case the agent buffering and you execute the command
opcagt or "opcagt -status" you may get an output like:
"Message Agent opcmsga buffering for
testmgmtsrv.bbn.hp.com (2376) is running"
- SR: B555014558
itodiag.exe/OvNtDiag.exe may start looping/hanging
forever.
- SR: B555014093
opcmona may crash (UNIX) or doesn't process all SCHEDULE
templates (Windows) when using SCHEDULE templates.
- SR: B555014513
opcle.exe may generate a message storm with messages
saying that one of the Windows event logs is corrupt.
- SR: B555014714
You may receive a message storm with messages:
OPC INTERNAL ERROR, CANNOT GENERATE MESSAGE
1500 OF SET ZERO
Or the opcle may start taking a lot of CPU over a long
period of time.
- SR: B555014523
nt_inst.exe may abort with Dr. Watson while trying to
install the Windows agent to a node.
- SR: B555013510
Autoactions are not executed on systems in a NAT
environment.
- SR: R555017956
The monitor agent is terminated if you use a session
variable within the message text of a template followed
by any other variable (for example $INSTANCE).
- SR: R555018043
Japanese characters in Perl scripts within templates
don't get converted correctly into the server code set.
If the Japanese characters are used as message text for
example these characters are corrupted.
- SR: B555014715
The Control Agent slowly grows in memory usage.
- SR: B555014212
opcle may report:
ntle.c:3670: OpC internal error: Cannot generate message
1500 of set 0
System Error Number: 1966234 (1e009a) - (OpC0-1500)
- SR: B555012869
Instead of using the trap's UUID, the trap interceptor
created a new message id for all but the first trap
template. The original message id was not set correctly
in these cases.
- SR: B555014728
Currently OvNtKill.exe / itokill.exe requires the
libopc.dll as well as some other DLLs required by
libopc.dll.
- SR: 8606282247
Logfile Encapsulator does not perform variable
replacement
for all Message Defaults fields.
- SR: 8606267798
In SNMP trap policies when using the <$r> or <$R>
variables, on Windows systems the IP address is used in
reverse order and therefore there are incorrect results.
- SR: B555014667
The first lines of a logfile are not forwarded to the
message browser when using a command to discover
logfiles and the logfile was created after the first
polling interval.
- SR: B555014708
Memory leaks in agent process. Especially monitor and
action agent leak when executing processes.
- SR: B555014378
opcctla may crash when doing a distribution on a Windows
XP node in a NAT environment.
- SR: B555014799
NT agent reinstall might cause cmd.exe startup issues.
This can happen when scheduled actions or tools have been
executed as user opc_op without specifying a password.
- SR: B555013796
When using itomserv.exe/opcntmserv.exe to list services
or devices where the Service Name or Description contains
Japanese Multibyte characters it may happen
that the text is truncated wrongly. The leads to a wrong
last character and maybe even to problem when displaying
this text in the Java or Motif UI.
- SR: B555009284
The authorization verification for remote start and stop
requests of the agent was sometimes unreliable. Possibly
this allowed more OVO servers to start or stop the agent,
than specified in the MoM configuration.
- SR: 8606242614
Messages are incorrectly suppressed by the logfile
encapsulator if "suppress identical output messages" is
specified and the messages differ only in the values of
<$LOGFILE> and/or <$LOGPATH>.
- SR: B555014882
When monitoring Windows performance values by using the
NTPerfMon (OVO UX) / Real Time Performance (OVO Windows)
sources, there might be an error that not all instances
can be found.
- SR: B555014759
When enabling/disabling policies you might discover a
memory leak in the agent processes.
- SR: B555014319
When reading Windows Event logs the opcle.exe and
services.exe may start taking a lot of CPU time for a
longer period of time.
- SR: B555013872
Agent installation sets full access rights for "HP ITO
account" on files in %SYSTEMROOT%\system32
(opcauth.dll and psapi.dll).
- SR: 8606286316
When retrieving a list of logfiles by using <`...`>
the logfile encapsulator may not retrieve any filename.
This has been seen when using perl scripts, that
internally call other system commands through the perl
function 'system' or 'open' or just use the backticks to
execute the command.
e.g.: $output = `more c:\loglist.txt`;
- SR: B555014591
When the OPC_INT_MSG_FLT is set to TRUE then the filtered
message is received corrupted on the server in
a Japanese environment.
- SR: B555015004
After uninstalling an OV Agent in Local Security Policy
there were still some SIDs left over.
- SR: R555019153
When deplying policies from a Windows management server
and using the "StoreCollection" method within the Perl
or VBScript, the monitor agent might show the Policy name
instead of the given metricname or may abort.
- SR: 8606285428
SNMP V2 Traps cannot be received via Windows Agent, when
NNM is not installed on the Node.
- SR: B555013891
In MoM environments, opcmsga does not return action
responses to SECONDARY managers, if their name is not
resolvable.
- SR: B555015072
'opcagt -id 12 -stop' may not work when starting as
'Administrator' as long as the OVO agent runs with
'SYSTEM' (LocalSystem) account.
- SR: H555008631
Customer receives a lot of OpC20-61 and OpC20-63 messages
in the error logfile when using NCS agents.
- SR: B555014442
opcle may report system error 32 and OPC20-63 while
processing a logfile on MS Windows systems and after this
stopping the processing of this logfile at all.
- SR: B555014570
The logfile encaspulator might start consuming CPU when
doing Windows Event Log monitoring.
- SR: B555012827
Support Windows XP with the VPO Windows agent.
Please see the "Defect Description" section below for
further details.
- SR: 8606244582
The distribution/deployment of action/command/monitor
binaries might fail due to some of them being used.
- SR: B555014101
Monitor agent may report error OPC30-783 and the
initialisation of the first template/policy using Windows
Performance data fails.
- SR: B555015047
opcecaas (Annotation Server) might log error
"Illegal NULL parameter (function ) (OpC10-11)"
with many similar lines.
- SR: B555014281
When using the Windows agent SDK (opcapi.h and
opcapi.lib) you may get linker unresolved symbol errors
when using one of the following API calls:
opcdata_type, opcdata_ldel, opcdata_ladd,
opcdata_lget_len, opcdata_lget_str, opcdata_lset_str,
opcdata_generate_id, opcdata_get_error_msg,
opcdata_lget_long, opcdata_lset_long, opccdata_clear,
opc_version
- SR: B555014700
The monitor agent and action agent on NT leak handles.
- SR: B555013540
opcsetup may report:
E-> Error from opc_ipinterf_getaddrs.
E-> Error from InitSetup.
E-> Setup program aborted.
- SR: B555015050
The environment PATH set by the agent during executing
external commands may contain several duplicate entries
and get very large therefore. This may cause problems
when an executed program tries to add it's own
directories as well.
- SR: B555013719
Message agent doesn't stop message buffering when the
management server is available again after a network
outage, fixed DNS problem or similar.
This can happen when the agent restarts/the machine
reboots during the network problem occurred.
- SR: 8606187183
After deploy/undeploy of opcmsg policies/templates the
suppressing times are lost. Messages that should be
suppressed after a deploy/undeploy of policies/templates
are shown.
- SR: B555014873
The exit code of commands executed through an ECS
annotate node and the OVO annotation server is always 0.
- SR: B555013534
When the "HP ITO Installtion Server" service
gets started you may find the following event in your
Application event log:
EventID: 0xC0001B68 (7016) - The HP ITO Installation
Server service has
reported an invalid current state 0.
- SR: 8606282754
When calling the perl interpreter without fully qualified
pathname within a automatic/operator initiated action or
a tool, you may run in problems, since the wrong perl
interpreter is used.
- SR: B555012562
The control agent might crash while processing a
distribution. This only happens in very special
situations. So far it has been seen in environments
which are using firewalls.
- SR: B555014132
During a distribution the agent may report an error like:
ITO responsible manager configuration. (OpC30-1203)
Cannot open file \usr\OV\tmp\OpC\cfgchg.
System Error Number: 13 (d) - The data is invalid.
(OpC20-63)
- SR: B555013096
several itoprocs.exe might hang instead of finishing.
- SR: 8606228146
opcntmserv.exe/itomserv.exe uses fixed width to display
the service names.
The defined values are 18 characters for the service
name and 25 for the description.
Defect Description:
PHSS_28943:
- SR: B555015785
One possible cause for opcecaas to report that there are
no more free process slots is, that all slots are in use
by applications that are running very long or might even
hang. In order to have control on this, the opcecaas
retrieves the timeout set for the "Annotate Node" in the
ECS circuit and kills the process in case it is beyond
this timeout.
- SR: B555015674
The setup may report an error in case your management
server name did change from short hostname to a long
hostname. e.g.: test123 changed to test123.test.com
or even test123.test.com is different to
test123.TEST.COM.
This caused the old setup to fail, since the management
server names are different while doing a string compare.
The new version of setup does a case insensitive compare
of the names and in case they do not match. It checks
whether at least the short hostname of the new and old
server matches.
- SR: 8606282084
Add the specific code to update also the primmgr file,
not only the opcinfo file.
- SR: 8606290346
The version in the registry key
HKLM\SOFTWARE\Hewlett-Packard\OpenView\ITO\Agent Version
is not updated in the right way during an installation
of a new version.
- SR: B555015557
The control agent has been changed in order to make the
restart of an aborted sub agent process configurable.
The control agent can be configured to restart aborted
sub agent processes. Furthermore it can be defined how
often a process should be restarted in a certain time
interval.
To configure this, you can use the following variables
in the opcinfo file:
OPC_RESTART_SUBAGENT
If set to TRUE, the control agent tries
to restart aborted sub agent processes.
The restart is done a defined number of
times (OPC_RESTART_COUNT) in a specified
period of time (OPC_RESTART_MINIMUM_RUN_TIME).
In case the process aborts more often,
it wont be restarted again.
Type/Unit : TRUE|FALSE
Default : TRUE
OPC_RESTART_COUNT
Defines how often an aborted sub agent process
should be restarted within the specified
minimum runtime. In case a process stops more often
it wont be restarted.
(See OPC_RESTART_SUBAGENT)
Type/Unit : integer
Default : 5
OPC_RESTART_DELAY
Defines the time the control agent waits
before it restarts an aborted sub agent
process. The time is specified in seconds.
Type/Unit : integer
Default : 10
OPC_RESTART_MINIMUM_RUN_TIME
Defines the time frame a sub agent process
should run without being restarted more
than specified by OPC_RESTART_COUNT.
The time is specified in minutes.
Type/Unit : integer (minutes)
Default : 60
- SR: B555015700
To deploy the new agent version to a system holding an
older version of the agent (7.00, 7.10, 7.12, 7.14),
execute the following steps:
- Call a tool that executes 'opcagt -stop' as 'HP ITO
account'. this tool execution will not come back with
either 'Successful' or 'Failed' but stay in state
'Starting'.
This is to stop the subagents. This will speed up the
later redeployment, causing this not to fail. Due to the
stopped agents, this action will never be completed in
the console.
- Wait for 2 minutes to make sure the stopping of the
agents is finished.
- 'Stop' and 'Rerun' this tool execution. The status
should switch to 'Failed', reporting that the 'Action
could not be executed because action agent is not
running'.
This is just to verify that the agents are actually
stopped.
- Now either 'Redeploy All' or deploy the new version of
the 'OpenView Operations Agent' package to the node. This
will now work without failing and during this process all
agents are restarted.
- SR: 8606299704
The error OPC20-63 comes when using environment variables
in the "File to be read" field, because the logfile
encapsulator does not correctly resolve those environment
variables.
This has been changed to resolve those variables.
The logfile encapsulator also resolves the environment
variables in the "File to be executed" field now.
- SR: 8606290908
The OVO Windows agent may loos it's AgentID when
doing a "Redeploy All" or installing an agent package
with a higher version.
Root cause for this problem is the agent setup. It
overwrites the currently existing nodeinfo file without
merging the values in there.
- SR: B555015771
In order to ensure, that the opcmona.exe always uses the
most recent libopc.dll, the dll is copied to
%OvAgentDir%\bin. Since the opcmona.exe is located in the
same place, this is the first location it will search for
the dll.
- SR: B555015325
During startup a timing issue prevented a connection from
opcmsga to opcctla, which generated the message. This
message was not immediately reported, but only after
receiving a signal. Retries will now prevent the
connection failure. If it still fails because opcctla is
really not running, the error will be reported
immediately.
- SR: H555008529
This is a timing issue, where internal structures are not
updated by the signal handler in time for proper values
to be written in the PIDS file.
An additional check for process presence has been
implemented before writing the PIDS file.
- SR: B555008674
The man pages for opcagt and opcragt now document the new
option '-version'. The message catalog was updated to
show the '-version' option in the usage string of the
opcagt and opcragt commands.
- SR: B555015378
The agent might not be able to monitor instances of the
LogicalDisk object and returns no data for it at all.
The root cause for this problem is a problem in the used
Microsoft API's, it is documented that wildcard patterns
can be used to retrieve performance data anywhere. But
the implementation only allows either wildcards or names.
A workaround for this issue has been implemented. The
monitor agent retrieves all data now and filters on the
searched values afterwards.
- SR: B555014851
opcmsga maintains an internal cache to find out the
target managers per message ID. The cache expires
after 1 hour (can be changed with the opcsvinfo variable
OPC_STORE_TIME_FOR_MGR_INFO) and then it runs into a
problem in its algorithm so that a message operation on
a non-cached message is sent again and again until the
last target manager in an internal list can be reached.
- SR: B555016032
The memory leak that shows up in opcapm.exe has several
causes.
1. The application opens a connection to the Cluster
several times, but does not close it.
2. The application reconnects to the Control Agent
several times without disconnecting and
overwrites the internal connection structure.
3. The application leaks while reading the XML
configuration file due to a memory leak
in the used BBC XML parser.
- SR: B555015484
The agent might not be able to execute any external
commands. This can be caused by disabling the 8.3
filename creation in the registry as it is described in
the Microsoft article Q174456.
The agent internally tries to convert all path names of
executed commands to 8.3, because otherwise you get
problems while executing programs with quoted parameters.
With this new version the error while converting the path
is ignored and the long path name is used instead.
- SR: B555015496
So far a queue file garbage collection was done, if more
than 256 Kbyte were unused. Now the unused space has to
be more than 256 Kbyte and more than a quarter of the
queue file size. This drastically reduces file I/O when
handling large queue files.
- SR: B555015485
To avoid that the "HP ITO account" gets locked out
on a machine providing network shares a new opcinfo
variable has been introduced.
Keyword :
OPC_WIN_DONT_USE_PATH_NWDRIVE
Description :
Force the Windows agent to scan the currently used
environment PATH to remove all mapped network
paths referenced in the PATH to avoid login
errors on the machines providing the network share.
Please note, this also removes relative PATH entries
like "." or ".." .
Type/Unit :
BOOLEAN (TRUE|FALSE)
Default :
FALSE
Used In :
opcinfo
In case you want to use these new features, please edit
the %OvAgentDir%\bin\OpC\install\opcinfo file.
Add the following entry and restart the agent:
OPC_WIN_DONT_USE_PATH_NWDRIVE TRUE
- SR: R555018185
Simplified Chinese codeset is now mapped as a valid
codeset.
- SR: B555015155
Whenever an error is added to the internal error list,
a trace entry with the DEBUG area ERRLIST is written to
the trace file.
When the error list is written to opcerror, another
trace line with the DEBUG area ERROR is written.
ERROR and ERRLIST are distinguished, since some errors
are added to the error list, but then later ignored
and therefore never appear in the opcerror file.
- SR: B555015331
opcmona holds a central table for all subprocess related
information. Advanced monitors are executed in separate
threads and could access this table in parallel, thus
overwriting each other's data. The table accesses are now
serialized by a mutex.
- SR: B555015712
In order to be able to correctly handle traps that have a
source address 127.0.0.1 the trap/event interceptor is
now able to replace the localhost address (127.0.0.1)
with the IP address of the node processing the trap.
In order to enable this, you need to add the following
line to the opcinfo file on your managed node:
OPC_RESOLVE_TRAP_LOCALHOST TRUE
- SR: 8606232431
VPO now ignores node names that contain only white space
characters without contacting the name service.
PHSS_28501:
- SR: 8606290723
The agent may report errors about commands or DLLs that
can not be found while executing commands using the OVO
Windows agent.
The cause is a modification of the system environment
variable PATH during the agent runtime. The agent
modifies the PATH in order to add certain agent specific
directories and to remove duplicate entries in order to
limit the size of the PATH. The size has to be reduced
because the length of PATH is limited to 2 kByte within
command prompts.
- SR: B555015349
The monitor agent aborts when using templates/policies
with external sources as soon as it receives a value
from the external source during checking for the
threshold with a previously received value. In this case
the received value is stored temporary and as soon as the
monitor agent
tries to process this value it aborts. The root cause
is that the montior agent tries to free up already freed
memory.
- SR: B555015308
When configuring the agent with apminfo.xml
to be cluster aware, the agent may not install newly
deployed policies correctly. The root cause
for this problem is the wrong status the policy has
internally once the Application Package Monitor(APM)
wants to inform all other sub agents. All policies are
set to status UNCHANGED and therefore no information of
the sub agents is done at all. A new status has been
introduced to
allow the APM to remember that there were modified
policies.
PHSS_27388:
- SR: B555013936
agent installation may fail with many of such messages:
T-> Tracing information: Can't get status for service: ..
in the inst.log file.
The install script may even report that the installation
was successfull but it wasn't.
The cause for this problem is that the installation tries
to stop MS Internet Information Services and OpenView
Internet Services in case OVIS has been installed and
fails when not all MS Internet Information Services are
installed. It then tries to stop the missing services in
a loop and in the end just dies or even brings a Dr.
Watson error message.
This fix just ignores the missing service and goes to the
next one.
- SR: B555014999
The problem while starting batch files on Windows NT is a
result of a problem in a Windows API.
This seems to have problems handling commands that have a
space in there path in case there are also quoted
parameters used.
The behavior have been modified in the way that the path
is converted to the 8.3 filename format.
Please note, the command itself is not converted.
This is not done, because the command name might be
used by the program itself for identification or
something similar.
The consequence is that you will still see this problem
when using commands containing a space under Windows NT.
The following will work:
c:\temp\test test1\dummy.bat test "test test",
but:
c:\temp\test test1\dummy 1.bat test "test test"
doesn't work on Windows NT.
- SR: B555014328
opcevti.exe may abort when using <$x>.
This issue is caused by traps having a timestamp
not in the range between 0 and 2147483647.
In case such a trap is received, the timestamp will be
reset to 0 now.
- SR: B555015077
Installation server always receives version A.07.10
to be installed on the target node.
Therefore it never tries to install the latest agent
package, but just A.07.10.
Since the version is no longer used to distinguish
between the different agent packages on the Management
Server it has been completely removed in
\usr\OV\databases directory on the Installation Server.
on the Installation
- SR: B555014961
The OVO agent should be able to execute tools and
scheduled commands for either the "HP ITO account" or
the SYSTEM account user. Or any other user currently
running the agent.
In any case this should work without a switch user.
To allow this, a design change has been made.
As soon as the agent executes some action now, it allows
actions to be executed as "HP ITO account" even in case
the agent is running as SYSTEM and vica versa.
Both user accounts are also mapped the way, that
no 'Switch User' is performed in case an action
contains those user names.
For OVO Windows 7.x users there is an updated
version (3.0) of the
'Using the SYSTEM account for Windows agents' white paper
available. This white paper is also part of this patch
and can be found unter
<InstallDir>\NLS\1033\Manuals\SystemAccount.pdf
after installing the patch.
- SR: B555014634
The OVO Windows agent may not pickup the SYSTEM event log
entries with ID 6008 or 6009 during the system is
rebooted.
The logfile encapsulator that is used to monitor
the SYSTEM event log uses entries in the event log
itself to find the time the agent has been stopped.
In order to achieve this, the agent writes a
"agent stop" event to the event log as soon as the
opcle.exe process goes down. This fails
during system shutdown, since the event log is already
stopped.
Now the agent is using a registry value instead of the
event log to get the correct time and this can be written
even late in the shutdown process.
This fix also prevents reading the SYSTEM event log in
order to find the "Agent Stop" event and therefore makes
the agent startup less expensive.
- SR: B555013965
The memory leak which can occur as described in Microsoft
article Q263221. Has been fixed by Microsoft
by providing a new pdh.dll, which is included in the
patch.
- SR: B555013978
In case the agent buffering and you execute the command
opcagt or "opcagt -status" you may get an output like:
"Message Agent opcmsga buffering for
testmgmtsrv.bbn.hp.com (2376) is running"
The output has been correct to look like on the UNIX
agents, where the information about the management
servers the agent is buffering to comes on the bottom.
- SR: B555014558
itodiag.exe/OvNtDiag.exe may start looping/hanging
forever.
This problem occurs in case of an error returned by
PdhGetFormattedCounterArray. This brings the program in
an endless loop trying to get the correct data. Has been
fixed by breaking the loop in error case immediately.
- SR: B555014093
opcmona may crash (UNIX) or doesn't process all SCHEDULE
templates (Windows) when using SCHEDULE templates.
This can occur when there are only spaces in
one of the schedule fields (Minute, Hour, Day of the
Month, Month, Year, Day of the Week).
You can verify this by going to the conf/OpC directory on
the node and doing an opcdcode monitor. When
there are entries like WEEKDAY " " the problem can occur.
Now the monitor agent treats sequences of spaces like
an empty string that is a wildcard and uses all valid
values in the possible range.
For WEEKDAY this is 0-6.
- SR: B555014714
You may receive a message storm with messages:
OPC INTERNAL ERROR, CANNOT GENERATE MESSAGE
1500 OF SET ZERO
Or the opcle may start taking a lot of CPU over a long
period of time.
This problem is caused by a corrupt Windows event log the
Logfile Encapsulator tries to read. With the last version
the opcle tried to read on with the next event instead of
exiting, but this doesn't work since the Windows API used
to read events reports very strange error codes once the
event log is corrupt.
The behavior of the opcle has been changed.
Now it stops monitoring the particular event log that is
corrupt and sends a message (OPC30-154) that this event
log has to be cleared and the agent must be restarted.
- SR: B555014523
nt_inst.exe may abort with Dr. Watson while trying to
install the Windows agent to a node.
This can happen when the command 'nslookup <target node>'
doesn't produce valid output on your installation server.
The installation server tries to get the WINS name of the
target node and therefore tries to get the IP address
first via GetHostByName.
Internally this failure results in an invalid pointer and
accessing this causes the crash.
To fix this, the invalid pointer is catched and goes to
the next possible case that can be tried to get the WINS
name.
- SR: B555014212
opcle may report:
ntle.c:3670: OpC internal error: Cannot generate message
1500 of set 0
System Error Number: 1966234 (1e009a) - (OpC0-1500)
The cause is the a wrong error number in the logfile
encapsulator itself.
- SR: B555014728
Currently OvNtKill.exe / itokill.exe requires the
libopc.dll as well as some other DLLs required by
libopc.dll.
This new version is indepented from the other agent
libraries.
- SR: 8606282247
Variable replacement is now performed for all Message
Defaults fields.
- SR: B555014708
Documented Microsoft API memeory leak in putenv():
Q235601. Replaced putenv() by SetEnvironmentVariable()
- SR: B555013796
itomserv.exe / opcntmserv.exe do truncate display and
service names and with Japanese multibyte characters it
can happen that the text is truncated exactly in the
middle of such a character.
This wrong character or better first part of a multibyte
character confuses the Java and the Motif UI and leads to
problems when calling this application.
With this version the truncation is done by using a
function which is aware of multibyte characters and
truncates them correctly.
- SR: B555009284
There were two different authorization algorithms which
interfered with each other. This has been consolidated
and is now checked more strictly.
- SR: 8606242614
The variables <$LOGFILE> and <$LOGPATH> were replaced
after the suppression rules were evaluated. Therefore the
comparison did not use the actual logfile name or path,
but compared the string "<$LOGFILE>" or "<$LOGPATH>".
- SR: B555014882
When monitoring Windows performance values by using the
NTPerfMon (OVO UX) / Real Time Performance (OVO Windows)
sources, there might be an error that not all instances
can be found. This is caused by an incorrect parsing of
the given instance name. This splitted one instance name
into parent instance and instance name even in case there
is no parent. This has been corrected now.
- SR: B555014319
When reading Windows Event logs the opcle.exe and
services.exe may start taking a lot of CPU time for a
longer period of time.
The cause was a misleading return code from a Windows API
which says the event log is on it's end, but it wasn't so
the logfile encapsulator permanently looped on the same
event instead of proceeding with the next one.
This behavior has been fixed by doing some additional
checks whether the end of the event log has been really
reached. If not, the current event will be skipped.
- SR: B555013872
Agent installation sets unrequired file permissions
on files in %SYSTEMROOT%\system32 for "HP ITO account".
These unrequired file permissions have been removed
and should disappear when installing this patch.
- SR: 8606286316
When retrieving a list of logfiles by using <`...`>
the logfile encapsulator may not retrieve any filename.
This has been seen when using perl scripts.
The cause for this problem is the StdInput file handle
provided to the executed program. This handle is invalid,
this doesn't matter as long as the called program doesn't
use internal redirection or piping.
Now the agent provides a valid file handle and so the
internal handling of the executed program should work
correctly.
- SR: B555014591
The defect was caused by the double conversion from the
server code set to the internal code set, once on the
agents side when it sent the internal message to opcmsga
and once by opcmsgi when it forwarded the message again.
Now, the message is converted back from the internal code
set to the server code set in opcmsga before sending the
message to the opcmsgi queue. The management server will
get the message through opcmsga in the internal code set,
and it will convert it into the server code set.
The conversion is made only if the internal code set is
different from the server code set.
- SR: B555015004
Some privileges of the OV-accounts were not deleted
after uninstalling the OV Agent.
- SR: 8606285428
SNMP V2 Traps can be received by the windows agent with
the following settings now:
- disable the Windows
SNMP Service / SNMP Trap Service on the Node
- add the following line to opcinfo:
SNMP_SESSION_MODE NNM_LIBS
- restart the agent (opcagt -start)
- SR: B555013891
Even if the IP address of the management server was
specified in the mgrconf file, it was not used except for
the primary manager. This behavior was changed to give
the mgrconf file precedence over name resolution.
- SR: B555015072
'opcagt -id 12 -stop' may not work when starting as
'Administrator' as long as the OVO agent runs with
'SYSTEM' (LocalSystem) account.
The root cause for this is an 'Access Denied' error,
since the 'Administrator' by default is not allowed to
send events for processes running as 'SYSTEM'.
- SR: H555008631
NCS agent open() and stat() calls did not handle EINTR,
so a check/loop was implemented to handle it.
- SR: B555014442
opcle may report system error 32 (Sharing violation) and
OPC20-63 when trying to access a file and after such an
error the monitoring of this file is stopped.
With this fix the opcle tries to read the file
at each interval even, when there was an error 32.
- SR: B555012827
Together with the "Windows XP" support for the VPO
Windows agent, there are some changes that are results of
changes in the way "Windows XP" works, these
changes/issues are documented below.
As default templates for "Windows XP" you can
use the same than for "Windows 2000".
List of all known changes/issues:
- Users created by the agent setup (HP ITO account &
opc_op) appear on the XP Welcome Screen
- Dr. Watson shows internal program name instead of
binary name.
This may affect you when troubleshooting processes
should be necessary.
- "itouser /local" doesn't work correctly, but
returns errors.
The tool can't be used with this switch under
Windows XP.
- Mapped network drives no longer visible to all users
- Windows XP is capable to really separate several
user environments
and therefore also the network drives mapped by one
user can't be seen by the other one
- This is a new functionality of Windows XP and
may effect user who have shared tools
placed on network drives and using them in scripts
executed by the agent.
- To avoid this don't use mapped network drives
but the complete network path to access such tools.
- Bug in snmptrap.exe (Microsoft Article Q319680, see
http://support.microsoft.com)
Microsoft confirmed this to be bug in Windows XP and
will be fixed with the first service pack.
Microsoft may also provide a HotFix for users
needing this functionality.
The result is that you can't do trap interception
or MIB monitoring.
- SR: B555014101
Monitor agent may report error OPC30-783 and the
initialisation of the first template/policy using Windows
Performance data fails.
This can be caused by a none critical problem in the
Windows registry. The monitor agent queries for the
languages, for which there are counter and object names.
When accessing some languages the system returns "NOT
FOUND" and the monitor agent internally reports this
errors and this causes the first template using this
source type to fail. All subsequent call will pass, since
the query of the registry is done only once to get all
performance counter and object names.
The opcmona ignores this error completely now.
- SR: B555014281
When using the Windows agent SDK (opcapi.h and
opcapi.lib) you may get linker unresolved symbol errors.
Some of the APIs were not exported in the DLL and LIB and
therefore you get linker errors.
The missing exports have been added now.
- SR: B555013540
Cause is a problem in the registry
That a TcpIP Device is there but
doesn't contain any entry for it's IPAddress.
Devices with such behavior are skipped now.
- SR: B555015050
The environment PATH set by the agent during executing
external commands may contain several duplicate entries
and get very large therefore.
To avoid this duplicates and to make the used PATH
shorter, the PATH is parsed and all duplicates are
removed.
- SR: B555013719
Message agent remains in buffering mode even when
the management server is available again.
The reason is that the agent wasn't able to resolve
the management server name to an IP address at startup
and the agent doesn't try again during runtime.
This has been fixed by checking for a resolvable name
every time a message should be buffered till the name can
be resolved, after this the normal checkalive mechanism
which handles buffered message takes place.
- SR: 8606187183
The opcmsg interceptor restarts after a deploy/undeploy
of policies/templates. During this process all the
policy/template information is cleaned and read again
from a temporary file. Because suppressing times are not
stored in this temporary file, this times are lost.
Now the suppressing times are taken over to the new data.
- SR: B555014873
The exit code of commands executed through an ECS
annotate node and the OVO annotation server is always 0.
The reason is an hardcoded return value in the OVO
annotation server. With this patch the annotation server
passes the received exit code to ECS.
- SR: B555013534
The "HP ITO Installation Server" service doesn't
set the status correctly at startup and therefore
it reports an invalid status when the operating
system asks for it.
- SR: 8606282754
When calling the perl interpreter without fully qualified
pathname within a automatic/operator initiated action or
a tool, you may run in problems, since the wrong perl
interpreter is used.
This is caused by the OVO agent, that contains a perl
interpreter. This perl interpreter can be found through
the PATH and when executing any command with the OVO
agent, the OVO agent directories are always added to the
beginning of the PATH. Therefore it is more likely that
the perl.exe shipped with OVO will be used.
In order to avoid this, you can install the agent with a
new option. While setting this option, the perl.exe will
be renamed to ovperl.exe.
In case you want to use the perl interpreter coming with
the OVO Windows agent, please use the environment
variable OVPERLBIN to call the perl interpreter in
future. This will ensure, that you are independent
whether you selected to rename the perl interpreter or
not. This variable is always set according to the setting
you made.
The option is configured differently for agent
installations with OVO Unix server and an OVO Windows
server.
OVO Unix server:
- do a manual or ftp installation
- before calling opc_inst.bat or opc_pre.bat
- edit opcsetup.inf, add
[Rename Perl]
TRUE
- start the installation
OVO Windows server:
- the tool setmgmtserver.exe has been extended with
a new switch /renperl
- in order to use ovperl.exe instead of perl.exe, please
call "setmgmtserver.exe /renperl /on"
- redeploy the agents that the changes are made
on the agents
The setting you made will be stored to the registry. This
ensures that a patch installation will not overwrite your
settings.
- SR: B555012562
The control agent might abort with Dr. Watson message
while it processes a distribution request.
The problem might only occur from time to time because
it depends on the system, the data transfer rate
between agent and server and other factors.
In the end it's a timing issue between two threads which
should end in a specific order and especially in
environments with firewalls it seems that the threads
often end in the wrong order which leaded to the
crash because of pointers used in both threads.
The issue has been fixed by defining the pointer
differently so that they are not lost in case
a thread closes.
- SR: B555014132
During a distribution the agent may report error number
OPC30-1203/OPC20-63 when trying to access the cfgchg
file.
The cause for this problem is that there are several
processes trying to get exclusive access to this file
at the same time. The problem has been fixed by doing a
retry for 10 times in case the error should occur with a
delay of one second.
- SR: B555013096
itoprocs.exe might hang when several itoprocs.exe
are running at the same time.
The reason is a dead lock between all of them.
This is fixed by using a central mutex to protect
critical areas.
- SR: 8606228146
opcntmserv.exe/itomserv.exe is only able to display
service names with a specific length of less than
18 characters.
This patch introduces a new option for the program
which allows to set the length via command line switch.
The new switch is called /width and takes as parameters
the width of the service name and the width of the
description.
Following example list the service name with a width
of 30 characters and completely hides the description.
> itomserv.exe /list s /width 30 0
The width switch is useful together with the /list and
&nbs