Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

NetWorker Virtual Edition: Upgrade or Install Failure Log Locations and Collection

Summary: This KB provides a general log location for NetWorker Virtual Edition (NVE) upgrade or install failures.

This article applies to   This article does not apply to 

Instructions

This KB provides a general log location for NetWorker Virtual Edition (NVE) upgrade or install failures. For instructions on how to perform installations on the NVE see NVE: How To Upgrade NetWorker Software

Avinstaller Web UI Logs:

The following logs pertain to the avinstaller web user interface used to deploy and manage the NVE software packages. The following logs should be reviewed if issues are observed when attempting to access the avinstaller web UI during NVE deployment/upgrades. These logs may also be reviewed when the web UI is accessible but a deployment/initial configuration of the NVE fails:
 
  • /space/avamar/var/avi/server_log/avinstaller.log.
  • /space/avamar/var/avi/server_log/aviserver.log.
  • /space/avamar/var/avi/server_log/avitask.log.0

The avinstaller service has the following command options:

nve:~ # avinstaller.pl
Usage: avinstaller.pl [options]
avinstaller.pl performs AvInstaller tasks. For internal use only.
options:
--help                    Display this help message
--start                   Start AvInstaller
--stop                    Stop AvInstaller
--restart                 Restart AvInstaller
--test                    Test the AvInstaller status
--debug                   Launch AvInstaller in debug mode
--testconfigured          Test if AvInstller is configured
--update_passcode         Update the support passcode
--reset_passcode          Reset the support passcode to default value
--version                 Display version information


NetWorker Upgrade and NVE Installation Logs:

During NVE upgrades, a temporary folder is created using the name of the upgrade package being installed. You can see the temp upgrade directory by running: ls -l /data01/avamar/repo/temp/

This folder is removed post upgrade and may be deleted if the upgrade fails and the workflow is closed. To collect these logs, initiate the upgrade and before closing out the failure collect the logs.

  • /data01/avamar/repo/temp/*/tmp/workflow.log
  • /data01/avamar/repo/temp/*/tmp/err.log
NOTE: The workflow.log and err.log will be in the ../temp/tmp folder under the NVE upgrade package name. There will only be one package folder for an active installation or upgrade. The above path uses * to bypass the need for knowing the exact folder name.

Once an upgrade has completed, you can find the workflow.log and err.log in the upgrade package directory under:

/usr/local/avamar/var/avi/server_data/package_data/

A folder exists for each of the upgrades applied to the NVE since it was deployed, this tells you when a package was installed and each folder will contain files specific to completed upgrade jobs.

For example:

nve:~ # ls -ltr /usr/local/avamar/var/avi/server_data/package_data/
total 4
drwxr-xr-x 2 avi avi  335 May 31 21:55 NveInstall-19.11.0-12.avp_1717206867725
drwxr-xr-x 3 avi avi 4096 Jun 28 17:16 NveConfig-19.11.0-12.avp_1719608972274
drwxr-xr-x 2 avi avi  328 Aug 14 09:58 NvePlatformOsRollup_2024-R2-v3.avp_1723643818123

nve:~ # ls -ltr /usr/local/avamar/var/avi/server_data/package_data/NvePlatformOsRollup_2024-R2-v3.avp_1723643818123
total 368
-rw-r--r-- 1 avi avi   1243 Jul 15 07:24 pkgdef.xml
-rw-r--r-- 1 avi avi    282 Jul 15 07:24 callabledef.xml
-rw-r--r-- 1 avi avi  27043 Jul 15 07:24 process.jpdl.xml
-rw-r--r-- 1 avi avi   1034 Jul 15 07:24 process.flowchart.txt
-rw-r--r-- 1 avi avi    541 Jul 15 07:28 userinput.xml
-rw-r--r-- 1 avi avi    541 Jul 15 07:28 ui_library.xml
-rw-r--r-- 1 avi avi   1305 Aug 14 09:57 inventory.log
-rw-r--r-- 1 avi avi      0 Aug 14 09:57 err.log
-rw-r--r-- 1 avi avi      5 Aug 14 09:57 port-cache.txt
-rw-r--r-- 1 avi avi    784 Aug 14 09:58 workflow_xml_val.xml
-rw-r--r-- 1 avi avi    312 Aug 14 09:58 main-cache.yaml
-rw-r--r-- 1 avi avi    588 Aug 14 10:00 workflow-reports.yaml
-rw-r--r-- 1 avi avi    311 Aug 14 10:00 internal_config.xml
-rw-r--r-- 1 avi avi 300053 Aug 14 10:00 workflow.log

OsRollup Logs:

When installing an NVE OsRollup package the sec_install_os_errata_sles.pl process creates a temporary log /tmp/sec_install_os_errata_sles.pl.log. This file will be deleted after a system reboot. 


Upgrade history and repository:

  • Get output showing install and upgrade history:
    avi-cli --verbose localhost --password ROOT-PASSWORD --listhistory
  • List packages currently in the repository:
    avi-cli --verbose localhost --password ROOT-PASSWORD --listrepository


General Logs:

  • /var/log/messages                      - operating system level messages.
  • /nsr/logs/daemon.raw                 - NetWorker service messages.
  • /opt/lgtonmc/logs/gstd.raw    - NetWorker Management Console service messages.
  • /opt/nwui/logs/install.log   - NetWorker Web User Interface (NWUI) installation log.

Collection:

The logs can be collected and zipped using the Linux tar command: 
sudo tar cvzfP /space/`hostname`_`date -I`.tgz /space/avamar/var/avi/server_log/ /data01/avamar/repo/temp/*/tmp /usr/local/avamar/var/avi/server_data/package_data /tmp/sec_install_os_errata_sles.pl.log /var/log/zypp/history /var/log/messages* ; chmod 777 /space/`hostname`_`date -I`.tgz
NOTE: This command can be run as-is. It creates a .tgz bundle with the NVE's hostname and date on which the bundle was generated under the /space directory. You can specify another location; however, /space typically has the most disk space available. Do not copy and paste the above command as the ` ` may not be passed correctly. If the command is copied and pasted, it may produce unexpected errors. Depending on the issue faced some of the directories listed may not exist and will report an error when zipping.
 
The above command only collects logs specific to the NVE upgrade and installation process, it does not collect any NetWorker service logs or configuration files. NetWorker service logs and configuration files can be collected using the NSRGET utility:
NetWorker: How to Use the NSRGet NetWorker Data Collection Tool

An SCP agent (FileZilla, WinSCP, so forth) can be used to copy the bundle off of the NVE. You must use the admin user to collect the bundle; unless SSH root access was enabled:
NVE: How to Allow root SSH Access On a NetWorker Virtual Edition

For additional info on retrieving files from a Linux server see: 
NetWorker (Linux): How to copy files to/from a Linux NetWorker server.

Additional Information

Affected Products

NetWorker
Article Properties
Article Number: 000156134
Article Type: How To
Last Modified: 24 Sept 2024
Version:  17
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.