NetBackup services that write logs using VxUL are unable to write any log messages; some NetBackup services may even fail to start
NetBackup services that write logs using VxUL are unable to write any log messages; some NetBackup services may even fail to start and the following message may be seen in syslog or Windows event log
OID:226:V-1-1 Unspecified error
This symptom is found to occur in the following circumstances.
1. Network configuration issues on host.
2. Missing registry key on Windows host
3. Unable to retrieve host id
These symptoms will occur if the hosts file on a system has the host name as an alias to the loopback address, e.g.,
Correct the problem by making the host name an alias of a non-loopback IP address. For example:
10.209.6.196 host10.xxx.yyy.com host10
Missing registry key:
On Windows hosts, the Unified Logging package (VxUL) stores the location of its configuration file in a registry sub-key. There have been rare cases where the registry key for VxUL in NetBackup is present, but the sub-key that locates the configuration file is missing. Once a host is in that state, the problem will remain until the registry is corrected.
The registry key in question is:
The key includes a sub-key, Configuration, that has the absolute path to the nblog.conf file as its value. The problem occurs when HKLM\SOFTWARE\VERITAS\vrtslog\51216 exists, but HKLM\SOFTWARE\VERITAS\vrtslog\51216\Configuration does not.
Correct the problem by doing one of the following.
1. Remove the HKLM\SOFTWARE\VERITAS\vrtslog\51216 key (either using regedit, or through an OS reinstall) first. Then recreate the correct entry by running the following command.
vxlogcfg -p 51216 -a -c "C:\Program Files\Veritas\NetBackup\nblog.conf" -n NB,nb
2. Manually restore/create the HKLM\SOFTWARE\VERITAS\vrtslog\51216\Configuration sub-key (using regedit)
Unable to retrieve host id:
Unified Logging uses the host id (on UNIX systems) that should generate a unique number to include in log file names. On systems configured with IPv6 addresses only, the APIs to retrieve the host id may return zero, which is taken as a failure return.
This problem is corrected in Unified Logging 188.8.131.52. NetBackup 7.1 will include Unified Logging 184.108.40.206 or later.
Alternatively, some platforms include a command, genhostid command, which may be used for generating a host id.
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):