- The REFInd Boot Managerby Roderick W. Smith.
- Cached
- The Refind Binary File Is Missing Aborting Installation Management Services
- The Refind Binary File Is Missing Aborting Installation Guide ..
[ Previous Page | Next Page | Table of Contents ]
Version 3.6.3, May, 2000
Endpoints and Gateways
- If an endpoint is allowed to broadcast for initial login, and the login request can reach multiple gateways in different TMRs, several of the gateways might receive the request and process it. This results in one endpoint logging into multiple TMRs. One login request is honored and the rest will return 'HMAC' errors on downcalls and upcalls. (CMVC-26857)
- APAR-IX80312, IX83059, IX82918: For Windows NT, a Tivoli Remote Access Account (TRAA) or 'password invalid' error is displayed the first time you install an endpoint with InstallShield if a user name is specified in the Remote Access dialog. This error is displayed even if the Administrator account is specified. (CMVC-43621) Workaround: Cancel the installation and log off from the target computer. Log on again and restart the installation. The TRAA account will then be recognized.
- For Windows NT, binary policies do not execute properly on Windows NT endpoint managers and gateways. (CMVC-42284) Workaround: You can invoke the binary in a policy script.
- Aborting a winstlcf installation with the n response at the Continue? prompt generates the following error: (CMVC-44256) Workaround: The message is harmless and can be avoided by responding with a for 'abort' instead of n for 'no.'
- APAR-IX82542, IX82870: When the endpoint is running in console mode (lcfd -s) and an attempt is made to distribute a file package to an endpoint, the endpoint might fail with the following message: (CMVC-42993) Workaround: Run the endpoint as a service, rather than in console mode.
- Installations of NetWare 4.x endpoints with the InstallShield report that the endpoint does not log in, even when it does. (CMVC-44272) Workaround: Disregard the InstallShield message and verify if the endpoint installation directory contains the /dat/1/lcf.dat file. If the file exists, the endpoint logged in successfully. If it does not, refer to the lcfd.log file in the same location for information.
- Sixteen-bit programs (batch files) executed by an endpoint or an application that is a client of an endpoint can fail when the Pathenvironment variable is too long. Most endpoint programs are 32-bit programs and run correctly with any setting of Path. However, problems can arise when a 16-bit program is run and the Pathvalue is greater than the limit supported by Microsoft Windows 3.1. The Microsoft Windows 3.1 command interpreter limits the size of any environment variable string (VAR=VALUE) to 127 characters. With this limitation, a Pathenvironment value cannot exceed 118 characters in length. (CMVC-43537) The endpoint automatically sets the Pathfor processes (lcfd.exe). By default, the endpoint adds the following directories to Pathwhen it starts:
- The path to the endpoint library directory
- The path to the endpoint cache library directory
- The path to the endpoint tools directory
Examples of Tivoli applications and services that invoke 16-bit programs are the following:- Tivoli Software Distribution (configuration program scripts)
- Tivoli Inventory
- Tivoli Task Library (batch files)
When the endpoint executes a sixteen-bit program or batch file, the MS-DOS command interpreter (COMMAND.COM) is invoked to run the program or batch file. If the Pathvalue that is passed to COMMAND.COM is too long, the command interpreter will fail to execute correctly. The endpoint will detect this situation and log a warning to the endpoint log file (lcfd.log) if the endpoint log threshold level is set to level 1 (the default) or higher. The message logged is as follows:Workaround: To avoid this problem, install the endpoint in the Tivoli recommended default location (C:TIVOLILCF). Using this path means that the three values that are added to the endpoint path at startup will not cause the Pathvariable to exceed the 118 character limit.Using a short installation path occasionally is not enough. The endpoint also passes the Windows 3.1 system environment (from AUTOEXEC.BAT) to child processes. This can create problems if the system Pathon the user's computer has been modified to contain additional entries. This can happen when the user has installed other software packages on the system that have updated the Pathin AUTOEXEC.BAT.If a path is too long, perform one of the following actions:- Reinstall the endpoint to a location on the system with a shorter path.
- Edit the AUTOEXEC.BATfile.
- Add the following line:
- Create virtual drives for long directory names in Path as follows:
- Reboot the computer to apply the changes.
- Upgrade Windows 3.1 systems to Microsoft Windows 95 or Microsoft Windows NT. These versions of Windows do not have Pathlimitation problems when running 16-bit programs.
- If you uninstall an endpoint from a NetWare system and fail to remove the LCF.SYS file, a new installation will use the old file and rely on the previous DAT directory location. (CMVC-44108) Workaround: Follow the 'Removing Endpoints' procedure in the TME 10 Framework Planning and Installation Guide.
- When you install some OS/2 endpoints from a mounted drive on a remote computer (OS/2 Software Installer), the installation times out and causes the installation to fail. (CMVC-41705) Workaround: Copy the directory to the target computer and perform the installation locally.
- The silent InstallShield template provided for NetWare 4.x endpoints is missing information and does not work. (CMVC-42769) Workaround: You can create a new Setup.iss file with the following command:
- The encryption of task data passed between servers and endpoints is disabled. (Task data between servers and managed node clients is still encrypted.) (CMVC-26589)
- The Edit button on the Gateway List dialog is disabled. (CMVC-27074)
- For OS/2, silent install of an OS/2 endpoint locks out the use of the keyboard. (CMVC-24920)
- Upgrades of Version 3.2 UNIX endpoints fail if you do not set the lib_dir variable. Workaround: Install the 3.2 EP. Edit the last.cfg file and add the line:Restart the endpoint and the upgrade is succesfull. (CMVC-88723)
- Gateways on HP-UX managed nodes sometimes fail. This problem occurs when large numbers of endpoints log in and the login_policy script is set to automatically upgrade endpoint software. (CMVC-84043)
- Endpoint tasks, jobs, and methods running on Windows 2000 systems may experience restricted system access due to changes in the default security settings between Windows NT 4.0 and Windows 2000. (CMVC-81288) Workaround: You can overcome this new restriction by adding the tmersrvd account (the Tivoli Unprivileged Operations Account) to the Power Users group for Windows 2000 Professional or to the Server Operators group for Windows 2000 Server. If you are concerned about the possible misuse of the tmersrvd account for interactive logins, you can disable the account.Windows NT and Windows 2000 provide both GUI and CLI utilities for account management. The NET.EXE CLI utility can be invoked from a TMA task to manage the tmersrvd account on multiple endpoints. You must execute this task with administrator privileges to successfully alter groups or accounts.The following examples illustrate group management on Windows NT 4.0 Workstation or Windows 2000 Professional. Substitute NET GROUP for NET LOCALGROUP when dealing with a domain controller. Use NET GROUP HELP (or NET LOCALGROUP HELP) for detailed usage information.To view current group membership, run the following command:To add the tmersrvd account to the Power Users group, run the following command:To remove the tmersrvd account from Power Users group, run the following command:The next examples illustrate user account management on Windows 2000. Use NET HELP USER for detailed usage information.To view current account information for the tmersrvd account, run the following command:To disable interactive logins for the tmersrvd account, run the following command:To enable interactive logins for the tmersrvd account, run the following command:
- After you upgrade a NetWare endpoint using the wadminepep_nameupgrade command, the last line of the LCF.NCF file on the NetWare endpoint may become corrupted. The NCF file works correctly, but a command not found message is displayed. (CMVC-82090)
- The wepep_label command does not work on Version 3.6.1 OS/2 managed nodes in a Version 3.6.3 TMR. Patch 3.6.1-TMF-0064 corrects this problem. (CMVC-83963)
- If an administrator with a user role tries to perform the wepset_label command, the command fails without displaying an error message and returns a zero return code. (CMVC-84172)
- If an administrator with the global senior role runs the wepmgrstop command, that administrator will not be able to run the wepmgrstart command. An error message is displayed stating that the administrator is not authorized to run the command. (CMVC-84402)
Home | Switchboard | Unix Administration | Red Hat | TCP/IP Networks | Neoliberalism | Toxic Managers |
May the source be with you, but remember the KISS principle ;-) Skepticism and critical thinking is not panacea, but can help to understand the world better |
News | Agents | Recommended Links | HP HPOM Reference | itochecker | HPOM Health Check | Tracing |
opcagt | opcragt | ovc | ovcert | bbcutil | Unix System Monitoring | Shadow IT |
Changing OVcoreid of the node due to mismatch | Certificate server is not set | Changing coreid of the node due to mismatch | Undefined certificate state | opcmsgm message manager aborted | Message from opcmsg not reaching HPOM console | Error opc_dflt_lang |
Starting and stopping HPOM agent | Troubleshooting of communication problems with the agent | Deinstallation of agent | Agent patching | Change of IP for the Agent | Multihomed Agenets | Policies troubleshooting |
Unix System Monitoring | Unix Configuration Management Tools | Enterprise Job schedulers | Sysadmin Horror Stories | Support Forum | Humor |
Make a backup copy of your refind.conf file, if you did any custom configuration. Delete the /boot/efi/EFI/refind/ directory and all other rEFInd files. Run efibootmgr -v to see the boot order, identify the rEFInd entry, then delete it via efibootmgr -b X -B where X is the boot number of the rEFInd entry. Re-install rEFInd via the section above. This manual explains how to boot the Red Hat Enterprise Linux 6.9 installation program (anaconda) and to install Red Hat Enterprise Linux 6.9 on 32-bit and 64-bit x86 systems, 64-bit Power Systems servers, and IBM System z. It also covers advanced installation methods such as kickstart installations, PXE installations, and installations over VNC. Finally, it describes common post-installation.
Note:HP renamed the product called now HP operations manager way too many times. Also it is very inconsistent with using abbreviations. Here we will assume that the term 'HP Operations manager' and abbreviations HPOM, OMU, and OVO mean the same thing :-)
- Troubleshooting of communication problems with the agent
- Key commands used in troubleshooting
Introduction
HPOM agents are complex (multicomponent) and thus extremely unreliable with some components that tend to fail spontaneously. For each 20 servers with HPOM typically there is at least one failure in 24 hours. That means for 200 servers you might well around a dozen of such problem in 24 hours (some days more, some days less). This is a major problem with HPOM.
If agent health is monitored in a primitive way -- by creating a ticket for each failure, such helpdesk tickets about them became major nuisance for system administrators and source of well-deserved hate of HPOM, and, especially, people in the organization who are responsible for it. BTW minor problems usually can be fixed by just restarting the agent. If this is not done automatically via a cron script, your HPOM people are extremely stupid or lazy or both. And the same is true for you :-).
This monitoring script should have a 'map of running components' stored as a file and compare it with the current 'map' on each invocation (say, once an hour). If there is a difference it needs to restart the agent and compare again. If difference persists, than it should write a 'do not do it again' file that will prevent this operation from repeating indefinitely on the next invocation and many be send email that the agent needs manual intervention to the primary administrator of the server. This 'do not do this again' file can expire in 24 hours (you can delete it via find is it is older then one day). Such a script can be implemented in less then a hundred lines of Perl, or bash code or can be implmented as a part private 'parralel' monitoring system that admistor uses for his servers ('Shadow IT' solution ;-) .
Agents are extremely unreliable with some components that tend to fail spontaneously. Minor problems usually can be fixed by just restarting the agent. If this is not done automatically via a cron script |
In order properly troubleshoot the agent one needs to understand the agent architecture. SeeHPOM Agent Architecture. You chances to find problem are higher is you have a snapshot of the 'working' configuration and list of processes as in large organization there might be difference version of agents installed on different servers.
If your agent was recently switched from one management server to another it is important to establish to which manager it is now reporting. You can do it with the command:
For example:If this is correct OV manager server then the next thing to check is whether the agent can communicate with the management server
Creating a snapshot of the current configuration
Having a snapshot of a working configuration greatly simplifies troubleshooting. For each agent you can get a snapshot on installed components using the commands
After that you need to create a tar of relevant directories such as /opt/OV, /var/opt/OV, /etc/OV. Difference of the current directory content with that tar of 'working' configuration often suggest areas where to search the problems. Pkease note that GNU diff can compare two different directories directly if you put them as arguments to the command.
The following three commands provide a snapshot of the configuration of the management server
Troubleshooting of communication problems with the agent
The most typical source of troubles with the HPOM agent are communication problems. They happen probably less often the 'spontanious' crashes of some agent-related processes, but they need to be checked first. Among them most common reasons:
- Linux firewall is enabled on agent host, but port 383 is not opened.
In this case attempt to get status of the agent from the HPOM server with the commandproduces the following error:Connection refused above suggests that we are dealing with the firewall problem.NOTE:itocheckerversion 09.00.160 diagnoses this error incorrectly as certificate error: - Check if NTP is working correctly on server and agent. HPOM will not function properly if clocks are not in sync and, for example, messages are coming 'from the future'.
- Check if IP is correct or the node was moved. Also check /etc/hosts file if it contains and entry for the node. In case the node was moved and IP changed, but /etc/hostswas not corrected this is a difficult to find bug. It is also very typical.
- Check whether the node exists on the server and is assigned to any node group. Check if IP is correct (it is editable) Check if core ID on the node record on the server is the same as core ID reported by agent. See Changing OVcoreid of the node due to mismatch
- Run the following commands from management server and save output:
- bbcutil -ping <managed nodename>
- opcragt -status<managed nodename>
- telnet <Managed node IP> 383 (i.e., default https port used by OVO 8.x)
Compare with the output from other similar working node or, better, with your snapshot. - From Managed node execute the following:
- bbcutil -ping <management server>
- telnet<management server IP Address>383
- opcagt -status
Sometimes version of the agent is just too old. To get a version of the agent from HPOM server use the command:
There are some cases when the node and the server can't communicate with each other. HPOM uses name resolution services (DNS and/or a host file) and that can get wrong too. Here are some potentially useful questions to start with:
- Can you connect to the node using ssh and/or telnet? If you can't this is the problem that you need to troubleshoot first.
- Whatcommand tells? Is only one node is involved or are there multiple nodes with the same problem? See Health Checks using itochecker
- What itochecker -5-s <node> tells
- Are all of the agent processes running on the node ? Check using the command: (we assume you added the path to /opt/OV/bin/). If not:
- on all OSes other then AIX you can use
- Sometimes just one process is crushed and all you need to do is to restart agent. That's a common problem with SLES 11For example:In this case all you need is to restart the agent.Now check the list of processes again using /opt/OV/bin/opcagt -statusAs you can see simple restart fixed the problem..Note:You can also do this do this operation from the OV server usingopcragtcommand
- What log files are telling? See HPOM Log Files
- Is this a networking problem; can the node ping the server? In simple restart of the agent can't fix the problem, the next question to answer is: 'Can the server ping the node?' What traceroute displays for both ends of the communication?
- Do the server and the node resolve the same names and addresses for each other? This is a typical problem if you changed the DNS name or host name of the node. Also if the node is relocated with the change of IP address.
- Does the node have more than one network interface card? If so,
- Does the DNS name reflects right interface for the communication with the server?
- Whatopcragtcommand on OV server tells ?
- Is the communication processes opcmsgaand ovbbccbrunning:
- Message Agent (opcmsga )— Sends messages to message receiver on HPOM server, sends action responses to the server, interface for programs that access the internal message stream interface (MSI), forwards data to other HPOM servers, and sends agent alive packet to server.
- HTTPS Communication Broker (ovbbccb)— Listens on port 383 for HTTP connection requests; returns port number of registered programs.
- See How to check for HTTP communication problems
Communication Broker problems checklist
- On all systems, the Operations Manager Server, Certificate Authority server and HTTPS managed node, check if the Communication Broker ovbbccb is running. Use the following commands: The ovbbccb process must be listed as running. The output takes the following form:
- Then the command ovbbccb must be listed.
- Now use command Status of ovbbccb must be ok. For exampleIf non standard ports are used make a note of the ports listed using the command:• on HTTPS managed node as <AGENT-PORT>• on Operations Manager Server as <MGMT-SRV-PORT>• on Certificate Authority server as <CA-SRV-PORT>Alternatively, you can use the command:Installed OpenView components have associated configuration settings files that contain one or more namespaces. A namespace is a group of configuration settings that belong to a component. All configurations specified in the settings files are duplicated in the settings.dat configuration database. For each specified namespace, ovconfget returns the specified attribute or attributes and writes them to stdout. Used without arguments, ovconfget writes all attributes in all namespaces to stdout. For details of how to use this tool, use ovconfget -h.
- If communication broker is not running you can start it with the command: No error messages should be displayed.
Restarting failed agent process
Following are descriptions of the HTTPS agent processes:
- Control Agent (ovcd)— Parent process, starts/stops/statuses subagents, communicates with the local communication broker.
- Message Agent (opcmsga )— Sends messages to message receiver on HPOM server, sends action responses to the server, interface for programs that access the internal message stream interface (MSI), forwards data to other HPOM servers, and sends agent alive packet to server.
- HTTPS Communication Broker (ovbbccb)— Listens on port 383 for HTTP connection requests; returns port number of registered programs.
- Configure/Distribute (ovconfd)— Distributes policies to the final location on the local file system.
- Action Agent (opcacta)— Starts/stops automatic and operator actions; handles command broadcast and other desktop application requests.
- Logfile Encapsulator (opcle)— Reads logfile(s), checks the logfile nodes and creates time, and triggers a file to be executed. The file to be executed is used in a case when the actual logfile may be a binary file. The content of the binary file must be converted into ASCII format and stored in a readable file in order for the logfile encapsulator to process the data. The file that is executed is the program that converts the binary file into ASCII format. For example, in order to convert the binary file wtmp, you need to execute the command last. The output from the execution of the command can be redirected to a file (such as /usr/bin/last agent process>/tmp/last.out ). This process is referred to as the binary conversion process. Then the file to be read becomes /tmp/last.out.
- Monitor Agent (opcmona)— Executes monitor scripts, checks monitor script returned values against threshold, creates message and sends to message agent, handles scheduled actions, and connects to the embedded performance component for performance monitor requests.
- Message Interceptor (opcmsgi)— Intercepts messages created with the opcmsg command or the application program interface (API), evaluates message for match condition, and sends matched message to the message agent.
- Trap Interceptor (opctrapi)— Converts SNMP traps to HPOM messages, sends messages to the message agent, can register with NNM to obtain incoming traps or listen for traps on port 162.
- Event Correlation Agent (opceca)— Correlates events on the node; requires an ECS policy.
- ECS Annotate Server (opcecaas)— Starts external programs; requires ECS engine.
- Security Certificate Client (ovcs)— Used during installation to allow or deny certificate requests.
- Performance Agent (coda)— Embedded performance component; collects performance metrics data.
The most common process the 'accidentally dies' is coda. Depending on the status on communications broker you can start it with the following commands:
- If communication broker is not running you need to execute command on the node (or using ssh from from the other server):
- If communication broker is running you can do it on the HPOM server with the command:
Certificate related problems
Those are typical after the installation of the agent. Rarely happen with working agent. SeeCertificates management
Key commands used in troubleshooting
- opcagt -- The command opcagt administers the agent processes running on a Managed Node of HPOM. This command can only be issued by the superuser. On the server similar command opcragt should be used to administer processing of remote nodes (opcagt command on the server applies to the agent running on the server).
- opcragt -- The command opcragt remotely administers the agent processes running on the managed nodes from the management server. If called without any option, opcragt returns the current status of all agent processes on the specified system(s). This command is only available on the HPOM management server and can be used only by root. This command will exit with value 0 after successful operation; otherwise the exit value will be set to 1 and an appropriate message will be displayed on stderr.
- ovcoreid (OpenView Unique System Identifier) The ovcoreid command is used to display existing OvCoreId value and, in addition, create and set new OvCoreId values on the local system. For details of how to use this tool, use ovcoreid -h.
- ovc(OpenView Process Control) ovc controls starting and stopping, event notification, and status reporting of all components registered with the OpenView Control service, ovcd. For details of how to use this tool, use ovc -h.
- bbcutilThe bbcutil command is used to control the OV Communication Broker.
- ovconfchg Installed OpenView components have associated configuration settings files that contain one or more namespaces. A namespace is a group of configuration settings that belong to a component. ovconfchg manipulates the settings in the configuration file, updates the configuration database, and triggers notification scripts. For details of how to use this tool, use ovconfchg -h.
- ovpolicy Command ovpolicy manages local policies and templates. A policy or template is a set of one or more specifications, rules and other information that help automate network, system, service, and process management. Policies and templates can be deployed to managed systems, providing consistent, automated administration across the network. Policies and templates can be grouped into categories. Each category can have one or more policies. Each category can also have one or more attributes, an attribute being a name value pair. You use ovpolicy to install, remove, enable, and disable local policies and templates.
- ovcertThe ovcert command is used to manage certificates on an HTTPS node through the Certificate Client. You can execute tasks such as adding managed node certificates and importing the private keys, adding certificates to the trusted root certificates, and checking the certificate status. For details of how to use this tool, use ovcert -h.
BBCUTIL - used to test HTTPS communications between managed node and management server.
If there are any problems in the area of HTTPS communication, the bbcutil command can be used to test
basic communication and verify whether RPC servers have registered correctly.
basic communication and verify whether RPC servers have registered correctly.
A common test is by using bbcutil -ping, as shown from the following example output:
C:Program FilesHP OpenViewdatabininstrumentation>bbcutil -ping
localhost: status=eServiceOK coreID=079f1de2-a609-7512-13c2-d6c7194b9864
bbcV=05.20.010 appN=ovbbccb appV=05.20.010 conn=1 time=156 ms
bbcV=05.20.010 appN=ovbbccb appV=05.20.010 conn=1 time=156 ms
Output of BBCUTIL help
C:Documents and Settingsroot>bbcutil -help
Usage: bbcutil [-count|-size|-list] -path [-t|-target ]
bbcutil -deregister {|*} [-force]
bbcutil -migrate {[namespace] [appname] [filename]}
bbcutil -getcbport []
bbcutil -gettarget []
bbcutil -ping {[|[:]] | []} [count]
bbcutil {-reg|-registrations} [|]
bbcutil -status {[|[:]] | [] [status|version|
connections|services|ovrg|messenger|msgHandler]}
bbcutil [-v|-verbose]
bbcutil [-h|-help]
bbcutil [-ovrg]
bbcutil [-version]
bbcutil -deregister {|*} [-force]
bbcutil -migrate {[namespace] [appname] [filename]}
bbcutil -getcbport [
bbcutil -gettarget []
bbcutil -ping {[|
bbcutil {-reg|-registrations} [|]
bbcutil -status {[|[:]] | [] [status|version|
connections|services|ovrg|messenger|msgHandler]}
bbcutil [-v|-verbose]
bbcutil [-h|-help]
bbcutil [-ovrg
bbcutil [-version]
HP OpenView BBC Utility Program.
The following options are recognized by bbcutil.
The following options are recognized by bbcutil.
- -count Display the number of requests in the BBC Store & Forward buffer for
the specified target, or the euxre buffer if no target is
specified. - -deregister {|*} [-force]
Deregisters the specified path from the OV Communication Broker on
the localhost. '*' may be used to denote all paths. The path will
not be deregistered if the application servicing the specified path
is currently running. Use the -force option to override this
behaviour. - -getcbport []
Display the configured OV Communication Broker port number for the
specified hostname. - -gettarget []
Display the target node IP address and OV Communication Broker port
number, or the HTTP Proxy and port number, if a proxy is configured,
for the specified hostname. - -list Display all requests in the BBC Store & Forward buffer for the
specified target. - -migrate {[namespace] [appname] [filename]}
Migrates the specified BBC configuration parameters. If no command
parameters are specified the BBC 2 LLB and the BBC 4 CB parameters
will be migrated to the namespace bbc.cb in the configuration
database. The BBC 2/3 DEFAULT parameters will be migrated to the
namespaces bbc.http, bbc.fx, and bbc.snf. BBC 4 CB parameters will
override BBC 2 LLB parameters. The namespace specifies the BBC 2/3/4
namespace to migrate the parameters from. The appname specifies the
application name to use in determining the BBC 5 target namespace.
Parameters are migrated to the bbc.http.ext.,
bbc.fx.ext., and bbc.snf.ext. namespaces. The
filename parameter specifies the file to read the parameters from.
Default filename is the BBC 2 standard default.txt file and the
standard BBC 4 OV Communication Broker settings.ini file. The BBC 4
settings.ini parameters overrride the BBC 2 default.txt parameters. - -p|-path Specifies the path to the BBC Store & Forward buffer. This parameter
will be used to set the BUFFER_PATH parameter. - -ping {[|][:]] | []} [count]
Pings the specified HP OpenView server process. A hostname or IP
address with an optional port number or a URI may be given to locate
the server process to ping. If a URI is given with the path of a
valid process registered with the OV Communication Broker, the OV
Communication Broker will automatically forward the ping to the
registered process. Count specifies the number of times to execute
the ping. The node may be specified with a hostname or IP address.
Default for the node is localhost. Default for the port is the OV
Communication Broker port on the specified node. Default count is 1. - -reg|-registrations [|]
Queries the OV Communication Broker on the specified node for a list
of all registered applications. The node may be specified with a
hostname or IP address. Default for the node is localhost. - -size Display the size of the BBC Store & Forward buffer. If -verbose is
specified the size of each individual request is displayed. - -status {[|][:]] | []}
Displays the status of the specified HP OpenView server process. A
hostname or IP address with an optional port number or a URI may be
given to locate the server process. The node may be specified with a
hostname or IP address. Default for the node is localhost. Default
for the port is the OV Communication Broker on the specified node. - -t|-target
Specifies the target URI to display BBC Store & Forward information
about. Information for all targets in the buffer is displayed if no
target is specified. - -v|-verbose
Show a more detailed output. - -h|-help Show this help message.
- -ovrg
Specify the OV Resource Group configuration to load. - -version Show the bbcutil version.
Upon completion, bbcutil returns one of the following values:
- 0 bbcutil exited normally with no error.
- 1 Command syntax error encountered. See command syntax for more
details on possible values. - 2 Command partially succeeded.
- 3 Command failed. See command output for more detailed information.
- 6 The command could not be completed because the OV Communication
Broker is not running. - 8 The command could not be completed due to an authorization error.
- 9 The OV HTTP server process cannot be queried because the server
process is not running. - 100 An exception was encountered causing the utility to exit.
OPCAGT - command used to check current status of OVO Agents on managed node (for backwards compatability with previous OVO versions)
See also opcragt
Output of OPCAGT help
C:Documents and Settingsroot>opcagt -help
Usage: opcagt [ -help| -h | -stop | -kill | -start | -restart | -status | -type
[verbose] ]
-help Prints this message.
-stop Stop Event/Action Agent and Coda.
-kill Stop OV Core functionality.
-start Start Event/Action Agent and Coda.
-restart Restart OV Core functionality.
-status Show status of Event/Action Agent and Coda.
-type Show type of Event/Action Agent.
-verbose Show detailed info of Event/Action Agent.
-version Show version information.
Usage: opcagt [ -help| -h | -stop | -kill | -start | -restart | -status | -type
[verbose] ]
-help Prints this message.
-stop Stop Event/Action Agent and Coda.
-kill Stop OV Core functionality.
-start Start Event/Action Agent and Coda.
-restart Restart OV Core functionality.
-status Show status of Event/Action Agent and Coda.
-type Show type of Event/Action Agent.
-verbose Show detailed info of Event/Action Agent.
-version Show version information.
Example usage (checking status of the agents):
C:Documents and Settingsroot>opcagt -status
opcacta OVO Action Agent AGENT,EA (3772) Running
coda OV Performance Core AGENT,CODA (3788) Running
opcmsgi OVO Message Interceptor AGENT,EA (3820) Running
opcle OVO Logfile Encapsulator AGENT,EA (3896) Running
opcmona OVO Monitor Agent AGENT,EA (4016) Running
opcmsga OVO Message Agent AGENT,EA (3836) Running
opcacta OVO Action Agent AGENT,EA (3772) Running
coda OV Performance Core AGENT,CODA (3788) Running
opcmsgi OVO Message Interceptor AGENT,EA (3820) Running
opcle OVO Logfile Encapsulator AGENT,EA (3896) Running
opcmona OVO Monitor Agent AGENT,EA (4016) Running
opcmsga OVO Message Agent AGENT,EA (3836) Running
OVC - command used to check current status of OVO8 Agents on managed node (similar to opcagt command)
Output of OVC help
C:Documents and Settingsroot>ovc -help
(ctrl-76) Usage: ovc -help|-h
-start [ .. ] [-boot]
-stop [ .. ] [-nostart]
-restart [ .. ]
-kill
-status [ .. ] [-level]
-trace [ .. ]
-notify[ .. ] [-value ]
-version
(ctrl-76) Usage: ovc -help|-h
-start [ .. ] [-boot]
-stop [ .. ] [-nostart]
-restart [ .. ]
-kill
-status [ .. ] [-level
-trace [ .. ]
-notify
-version
Example usage (checking status of the agents):
C:Documents and Settingsroot>ovc -status
ovcd OV Control CORE (1204) Running
opcacta OVO Action Agent AGENT,EA (3772) Running
coda OV Performance Core AGENT,CODA (3788) Running
opcmsgi OVO Message Interceptor AGENT,EA (3820) Running
opcle OVO Logfile Encapsulator AGENT,EA (3896) Running
opcmona OVO Monitor Agent AGENT,EA (4016) Running
opcmsga OVO Message Agent AGENT,EA (3836) Running
ovconfd OV Config and Deploy COREXT (3848) Running
ovbbccb OV Communication Broker CORE (3296) Running
ovcd OV Control CORE (1204) Running
opcacta OVO Action Agent AGENT,EA (3772) Running
coda OV Performance Core AGENT,CODA (3788) Running
opcmsgi OVO Message Interceptor AGENT,EA (3820) Running
opcle OVO Logfile Encapsulator AGENT,EA (3896) Running
opcmona OVO Monitor Agent AGENT,EA (4016) Running
opcmsga OVO Message Agent AGENT,EA (3836) Running
ovconfd OV Config and Deploy COREXT (3848) Running
ovbbccb OV Communication Broker CORE (3296) Running
OVCERT - Command to check, request, or modify the certificate on the managed node
Output of OVCERT help
C:Program FilesHP OpenViewdatabininstrumentation>ovcert -h
Usage: ovcert -importcert -file[-pass ]
[-ovrg]
ovcert -exportcert -file [-alias ] [-pass ]
[-ovrg ]
ovcert -importtrusted -file [-ovrg ]
ovcert -exporttrusted -file [-alias ]
[-ovrg ]
ovcert -certreq [-instkey [-pass ]]
ovcert -list [-ovrg ]
ovcert -remove [-f] [-ovrg ]
ovcert -certinfo [-ovrg ]
ovcert -check [-ovrg ]
ovcert -status
ovcert -updatetrusted
ovcert -version
ovcert [-h|-help]
Usage: ovcert -importcert -file
[-ovrg
ovcert -exportcert -file [-alias ] [-pass ]
[-ovrg ]
ovcert -importtrusted -file [-ovrg ]
ovcert -exporttrusted -file [-alias ]
[-ovrg ]
ovcert -certreq [-instkey [-pass ]]
ovcert -list [-ovrg ]
ovcert -remove [-f] [-ovrg ]
ovcert -certinfo [-ovrg ]
ovcert -check [-ovrg ]
ovcert -status
ovcert -updatetrusted
ovcert -version
ovcert [-h|-help]
Example usage (checking the status of the certificate):
C:Program FilesHP OpenViewdatabininstrumentation>ovcert -status
Status: Certificate is installed.
Status: Certificate is installed.
NEWS CONTENTS
- 20101201 : OVO Agent Error in UNIX Servers ( Feb 13, 2006 , IT Resource Center forums )
- 20101201 : IT Resource Center forums - HP Operations HTTPS agent processes aborted ( IT Resource Center forums - HP Operations HTTPS agent processes aborted, )
Old News
Switchboard | |||||
Latest | |||||
Past week | |||||
Past month |
[Dec 01, 2010] OVO Agent Error in UNIX Servers
Feb 13, 2006 | IT Resource Center forums
Ujjwal Gupta:
hi,
I am using OVOU8.x environment. When i have already installed agent in UNIX/LINUX/Solaris server. Now Management server not communicating with some servers. When i check these servers with help of using commands i.e :-
opcagt -status
Then it gives error just like as:-
' Network Communication problem occurred during distribution to node <Node Name>. '
Please suggest me, How do remove this error.
Reymond Keiluhu:
did you execute that command on managed node? why is the error about distribution? https agent or dce agent? have you verified all the required ports between mgmt server and managed nodes are ok?
Ujjwal Gupta:
Hi,
Thanks for immediate response. I am using https agent. I executed this command on Management Node. it runs sucessfully. Yah, I have checked all the ports which are required for mgmt server & mgmt node.
Any another way to resolve this issue.
Reymond Keiluhu:
what is the output of this command:
- -(on mgmt server) `bbcutil -ping <managed_node>`
- - (on the managed node) `ovconfget`, and write down MANAGER_ID
- - (on mgmt server) `ovcert -list`
Ravindra:
Hi Ujjwal,
Please try the following from management server
- bbcutil -ping <managed nodename>
- opcragt -status <managed nodename>
- telnet <Managed node IP> 383 (i.e., default https port used by OVO 8.x)
- opcsv -status
From Managed node execute the following
- bbcutil -ping <management server> 6. telnet <management server IP Address> 383 7. opcagt -status
Even after checking these conditions, check whether the node is assigned to any node group.
Still if you are facing the same problem, remove and re-install the agent on managed node.
Regards, Ravindra
Ujjwal Gupta:
Hi Ravindra,
Thanks for reply. I check all the command which you have send me in rply.
One of them in Magement Server when i run the command i.e opcragt <Node Name>
It gives the error ' Network Communication problem occurred during distribution to node <Node Name>. '
Please suggest me how do resolve it
Regards
Shivam Tiwari:
Hi Ujjwal,
To start with
Just check the output of this from Management Server
#bbcutil -ping http://FQDNOFNODE
and check that the COREID is same as what known to the management server by
#opcnode -list_id node_list=FQDNOFNODE
If they are not same then change the id of the node on the management server
On the Node do
#bbcutil -ping https://FQDNOFSERVER
If this is OK then the communication is OK otherwise there is some network routing issues.
HTH,
Shivam Tiwari
Ravindra:
Try with reinstalling the agent. First remove the node from node bank. it asks for automatic deinstalling of agent say 'yes'. once agent is uninstalled and node is not visible in node bank, restart the GUI. then discover node once again and install the agent automatically. You need the root password of managed node to install the agent. because before it is ftp'ing the packages, it asks for the password.
Regards, Ravindra
Shivam Tiwari :
I believe reinstalling is the last step to perform as this doesnt give us the oppurtunity to troublehshoot the root cause of the Incident.
Anyways
if the bbcutil -ping http:// is working both the ways then try for bbcutil -ping https://FQDN both the ways to check the Secure Communication is OK.
Id it is then delete all the certificate on the node and issue a new certificate request from the node by #ovcert -certreq
grant the certificate from management server and hope this will reolve your issue.
![Configuring Configuring](https://trick77.com/wp-content/uploads/2015/01/odroid-c1-kodi-summary.png)
HTH,
Shivam Tiwari Omnisphere 2 torrent windows.
IT Resource Center forums - HP Operations HTTPS agent processes aborted
Hello
I believe that from agent (installation and processes related to agent) perspective the Linux nodes will be just that - no difference whethere it is in Oracle RAC.
The log file you need to look for is the System.txt file - /var/opt/OV/log/System.txt file.
Hope this helps.
Regards
Ram
Regards
Ram
Nov 4, 2010 21:35:45 GMT N/A: Question Author
The REFInd Boot Managerby Roderick W. Smith.
Hello,
thanks for your reply,
regarding the processes aborted problem, i have been searching in other threads and almost all recommed this procedure:
regarding the processes aborted problem, i have been searching in other threads and almost all recommed this procedure:
1. ovc -kill
2. make sure all corresponding services (OvCtrl, HPOvTrcSvc) and processes (ov* opc* ,coda, agtrep) are shut;
3. remove all agt queues & buffers in
%ovagentdir%tmpOpC
%ovagentdir%tmppublicOpC
4. ovc -start
2. make sure all corresponding services (OvCtrl, HPOvTrcSvc) and processes (ov* opc* ,coda, agtrep) are shut;
3. remove all agt queues & buffers in
%ovagentdir%tmpOpC
%ovagentdir%tmppublicOpC
4. ovc -start
I already did it with no success, the problem persists:
ovc -start
(ctrl-7) Error in the target component.
ovc -status
ovcd OV Control CORE (5153) Running
ovbbccb OV Communication Broker CORE (5178) Running
agtrep OV Discovery Agent AGENT,AgtRep (5917) Running
opcle OVO Logfile Encapsulator AGENT,EA Aborted
opcacta OVO Action Agent AGENT,EA Aborted
opcmsga OVO Message Agent AGENT,EA (5648) Running
coda OV Performance Core COREXT (18011) Running
opcmona OVO Monitor Agent AGENT,EA Aborted
ovconfd OV Config and Deploy COREXT (5215) Running
opcmsgi OVO Message Interceptor AGENT,EA Aborted
(ctrl-7) Error in the target component.
ovc -status
ovcd OV Control CORE (5153) Running
ovbbccb OV Communication Broker CORE (5178) Running
agtrep OV Discovery Agent AGENT,AgtRep (5917) Running
opcle OVO Logfile Encapsulator AGENT,EA Aborted
opcacta OVO Action Agent AGENT,EA Aborted
opcmsga OVO Message Agent AGENT,EA (5648) Running
coda OV Performance Core COREXT (18011) Running
opcmona OVO Monitor Agent AGENT,EA Aborted
ovconfd OV Config and Deploy COREXT (5215) Running
opcmsgi OVO Message Interceptor AGENT,EA Aborted
Q: is there any other way to fix this before reinstall the agent?
best regards.
Etc
Windowfx alternative windows. Society
Groupthink :Two Party System as Polyarchy : Corruption of Regulators :Bureaucracies :Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia :Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience :Who Rules America :Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
Quotes
War and Peace: Skeptical Finance : John Kenneth Galbraith :Talleyrand :Oscar Wilde :Otto Von Bismarck :Keynes :George Carlin :Skeptics :Propaganda : SE quotes : Language Design and Programming Quotes :Random IT-related quotes : Somerset Maugham :Marcus Aurelius :Kurt Vonnegut :Eric Hoffer :Winston Churchill :Napoleon Bonaparte :Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Bulletin:
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis :Political Skeptic Bulletin, 2013 :Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments :Slightly Skeptical Euromaydan Chronicles, June 2014 :Greenspan legacy bulletin, 2008 :Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) :Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 :Inequality Bulletin, 2009 :Financial Humor Bulletin, 2008 :Copyleft Problems Bulletin, 2004 :Financial Humor Bulletin, 2011 :Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult :Political Skeptic Bulletin, 2011 :Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
History:
Fifty glorious years (1950-2000): the triumph of the US computer engineering :Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds :Larry Wall :John K. Ousterhout : CTSS : Multix OSUnix History : Unix shell history :VI editor :History of pipes concept :Solaris : MS DOS : Programming Languages History :PL/1 : Simula 67 :C :History of GCC development : Scripting Languages :Perl history :OS History : Mail :DNS : SSH : CPU Instruction Sets :SPARC systems 1987-2006 :Norton Commander :Norton Utilities :Norton Ghost :Frontpage history :Malware Defense History :GNU Screen : OSS early history
Classic books:
The Peter Principle : Parkinson Law : 1984 :The Mythical Man-Month : How to Solve It by George Polya :The Art of Computer Programming :The Elements of Programming Style :The Unix Hater’s Handbook :The Jargon file :The True Believer :Programming Pearls :The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society :Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story :The Cuckoo's Egg :IT Slang : C++ Humor : ARE YOU A BBS ADDICT? :The Perl Purity Test :Object oriented programmers of all nations : Financial Humor :Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor :Goldman Sachs related humor :Greenspan humor : C Humor :Scripting Humor :Real Programmers Humor :Web Humor : GPL-related Humor : OFM Humor :Politically Incorrect Humor :IDS Humor : 'Linux Sucks' Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor :Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor :Networking Humor :Shell Humor :Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 :Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor :Education Humor : IBM Humor : Assembler-related Humor :VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
![The refind binary file is missing aborting installation management services The refind binary file is missing aborting installation management services](https://i.stack.imgur.com/yeV4x.jpg)
The Last but not LeastTechnology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D
Copyright © 1996-2020 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) in the author free time and without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICEThis site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
Cached
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree..
You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info |
The Refind Binary File Is Missing Aborting Installation Management Services
Disclaimer:
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with.We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.
The Refind Binary File Is Missing Aborting Installation Guide ..
Last modified: July 28, 2019