cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

The doubt of the vxlogview -o <oid> with history VxUL logs

How to globally display the following history VxUL logs via vxlogview -o <oid> ?
At the current, I can only partly view the history VxUL logs with specifying its sub-directory.


#
#
#
# ls -ltr /install/nbu*
total 4
drwxr-xr-x 2 root root 6 Feb 23 17:58 db-logs
drwxr-xr-x 93 root root 4096 Feb 23 17:58 nb-logs
drwxr-xr-x 23 root root 307 Feb 23 17:58 vxul-logs
drwxr-xr-x 2 root root 56 Feb 23 17:58 extra-logs
drwxr-xr-x 24 root root 324 May 30 12:11 logs
#
#
#
# ls -ltr /install/nbu*/vxul-logs
total 0
drwxr-xr-x 2 root root 54 Feb 23 17:58 nbpem
drwxr-xr-x 2 root root 54 Feb 23 17:58 nbemm
drwxr-xr-x 2 root root 54 Feb 23 17:58 nbrb
drwxr-xr-x 2 root root 54 Feb 23 17:58 nbjm
drwxr-xr-x 2 root root 6 Feb 23 17:58 bmrsetup
drwxr-xr-x 2 root root 54 Feb 23 17:58 bmrd
drwxr-xr-x 2 root root 198 Feb 23 17:58 nbsl
drwxr-xr-x 2 root root 198 Feb 23 17:58 nbsvcmon
drwxr-xr-x 2 root root 54 Feb 23 17:58 nbvault
drwxr-xr-x 2 root root 54 Feb 23 17:58 nbftclnt
drwxr-xr-x 2 root root 198 Feb 23 17:58 nbrmms
drwxr-xr-x 2 root root 54 Feb 23 17:58 nbstserv
drwxr-xr-x 2 root root 54 Feb 23 17:58 nbkms
drwxr-xr-x 2 root root 54 Feb 23 17:58 nbevtmgr
drwxr-xr-x 2 root root 54 Feb 23 17:58 nbim
drwxr-xr-x 2 root root 54 Feb 23 17:58 nbaudit
drwxr-xr-x 2 root root 54 Feb 23 17:58 nbars
drwxr-xr-x 2 root root 6 Feb 23 17:58 nbutils
drwxr-xr-x 2 root root 198 Feb 23 17:58 nbdisco
drwxr-xr-x 2 root root 198 Feb 23 17:58 nbpxyhelper
drwxr-xr-x 2 root root 54 Feb 23 17:58 nbpxytnl
#
#
#
#
# vxlogview -G /install/nbulogs_lcrt/vxul-logs -o 118
V-1-45 No log files found.
#
#
#
# vxlogview -G /install/nbulogs_lcrt/vxul-logs -o 118 -b '2/04/20 11:05:00 PM' -e '2/04/20 11:07:00 PM'
V-1-45 No log files found.
#
#
#
# vxlogview -b '2/04/20 11:05:00 PM' -e '2/04/20 11:07:00 PM' -G /install/nbulogs_lcrt/vxul-logs/nbrb|more
02/04/2020 23:05:34.975 [log_set_callback] switched to a new logging callback
02/04/2020 23:05:34.979 [Info] V-137-74 =====================================================
02/04/2020 23:05:34.979 [Info] V-137-13 Starting service: nbrb
02/04/2020 23:05:34.979 [Info] V-137-74 =====================================================
02/04/2020 23:05:34.979 [main] INITIATING nbrb
02/04/2020 23:05:34.981 [nbapp_info_init_ex] path=/etc/nbapp-release
02/04/2020 23:05:34.981 [read_keyvalue_file] failed to open file: "/etc/nbapp-release", status: 12
02/04/2020 23:05:34.981 [nbapp_info_init_ex] read_keyvalue_file failed, path:/etc/nbapp-release, status: 12
02/04/2020 23:05:34.981 [Warning] V-118-47 EMM Server jcbak is not this host jc41-x8bksv1-41fd02. Netbackup Resource Broker will not start.
02/04/2020 23:05:34.981 [Critical] V-137-9 OrbService will not start since subclass check failed
02/04/2020 23:05:34.981 [Critical] V-137-15 Unable to pass service start criteria
02/04/2020 23:05:34.981 [Info] V-137-74 =====================================================
02/04/2020 23:05:34.981 [Info] V-137-12 Stopping service: nbrb
02/04/2020 23:05:34.981 [Info] V-137-74 =====================================================
02/04/2020 23:05:34.981 [Info] V-118-50 nbrb exiting
#
#
#

Tags (2)
2 Replies
Highlighted

Re: The doubt of the vxlogview -o <oid> with history VxUL logs

I think you are over-complicating this. 
If you want to see logs on the master, there is no need to specify a directory. NBU know where the logs are kept (on Unix/Linux, unified logs are under /usr/openv/logs). 
Even if you have moved logs to a different mount point, you will still have a sym-link in /usr/openv/logs, right? 

Why would you want to see logs in other folders than in the default path?
Not even on a Sev1 call with Veritas Support have they ever asked for anything other that logs in default paths.

The only times I had to specify a directory name is when a customer sent me their raw logs and I had to run it through vxlogview.

The folders under /usr/openv/logs have the process names, not oid numbers. 

So, to see nbrb logs, you can either use the process name or the oid.

e.g. to see nbrb logs for last 20 minutes: 
vxlogview -o 118 -t 00:20:00 
or vxlogview -o nbrb -t 00:20:00
(There are obviously more parameters that can be added, but these are normally sufficient for initial troubleshooting. )

The reason why there are no recent nbrb logs on this particular server, is because this is not the master:

EMM Server jcbak is not this host jc41-x8bksv1-41fd02

Highlighted

Re: The doubt of the vxlogview -o <oid> with history VxUL logs

The problem key is that the standard/default current vxul logs cannot be "overwritten",   but the -o <oid> seems to only "recognize"  the standard/default current vxul logs.