Forum Discussion

fly99h's avatar
fly99h
Level 3
5 years ago

Re: Cannot log into GUI, status 526

Hello, not sure if I am posting this correctly ( just joined with a new user account). The topic "Cannot log into GUI, status 526" seems to fit my stuation, but the solution does not seem to apply to me. So when I try to log onto Netbackup admin console ( NB ver 8.1.2) from Win 10, I get status 526 Cannot Connect to the PBX service. I have master server on Centos 7; media server on Win server 2008R2; and have i500 for automatic tape library; and VNX5400 for NDMP backup/restore. I think the problem started in BAR GUI, as I was trying to do a NDMP restore on a folder; I think I incorrectly selected a Full backup and 2 incremental backups after the Full backup (3 backups all at once) and clicked on “Start Restore”; the GUI got hung, and Netbackup never recovered from that. I restarted Netbackup processes ( bp.killl_all, bp_start_all).  I also tried rebooting the master server and the media server. But the problem never cleared up; I cannot login to the admin console, and the nackups do not seem to be running. I also tried to restart PBX process, etc. without success. Any help would be appreciated.

8.1.2
cannot log to netbackup console
PBX connect
status 526
UNIX
  • davidmoline's avatar
    davidmoline
    5 years ago

    Hi fly99h 

    I didn't mean for you to uninstall the RPM, just reinstall. You appear to have also uninstalled some critical NetBackup packages so it is good that you have a snapshot you can recover to. 

    For PBX - just try something like "rpm -i --force VRTSpbx.rpm"

    Cheers
    David

  • Marianne's avatar
    Marianne
    Level 6
    5 years ago
    Please post output of bpps -x.
    This will confirm if all NBU processes are running.

    PS:
    Are you aware that CentOS is not supported as NBU master server?
  • EthanH's avatar
    EthanH
    Level 4
    5 years ago

    Were you able to get this sorted out?

    If the backups are running, the GUI status 526 is most likely a symptom of a bigger issue on the master server. Runnin bpps -x and make sure that nbwmc and nbsl are running, as that's usually the issue when the admin console is unresponsive. 

    I would also check and make sure that there aren't any defunct Java processes running on your PC. 

    Finally, make sure you use "Run as Administrator" when opening the Admin Console for non-AD master servers.

    • fly99h's avatar
      fly99h
      Level 3
      5 years ago

      Thank you for responses; in my case, backups are NOT running. 

       Between centos master server and Windows media server, there seems to be different syntax for bpps  ( ex:   -x  meaning  exclude in windows ).

      Not quite sure which output is more trustworthy.

       

      centos$ bpps -x

      NB Processes

      ------------

      root  9212 1  2 Oct05 ?    00:18:44 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/g lobal/databases.conf -hn 5

      nbwebsvc  9618 1  0 Oct05 ?    00:04:21 /usr/openv/java/jre/bin/java -Dnop -Djava.util.logging.manager=org.apache.juli.C lassLoaderLogManager -Dnbwmc -d64 -Xms1024m -Xmx1024m -XX:MetaspaceSize=192m -XX:NewRatio=1 -XX:SurvivorRatio=4 -XX:-UseAdaptive SizePolicy -Djava.library.path=/usr/openv/lib -DNB_HOSTNAME=CENTOS-SERVER -DNB_INSTALL_DIR=/usr/openv -DVAR_GLOBAL=/usr/op env/var/global -Djava.util.logging.config.file=/usr/openv/wmc/config/tomcat.logging.properties -Dvrts.NBJAVA_CONF=/usr/openv/wmc /config/nbj.conf -Dvrts.common.utilities.DEBUG_PROPERTIES=/usr/openv/wmc/config/Debug.properties -Dlog.conf.path=/usr/openv/netb ackup/nblog.conf -Dvrtsat.home=/usr/openv/netbackup/sec/at -Dvrtsat.datadir=/usr/openv/var/vxss -Djdk.tls.ephemeralDHKeySize=204 8 -Djdk.tls.rejectClientInitiatedRenegotiation=true -verbose:jni -XX:ErrorFile=/usr/openv/wmc/webserver/logs/hs_err_pid%p.log -X X:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/usr/openv/wmc/webserver/logs -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.h andler.pkgs=org.apache.catalina.webresources -Djava.endorsed.dirs=/usr/openv/wmc/webserver/endorsed -classpath /usr/openv/wmc/we bserver/bin/bootstrap.jar:/usr/openv/wmc/webserver/bin/tomcat-juli.jar -Dcatalina.base=/usr/openv/wmc/webserver -Dcatalina.home= /usr/openv/wmc/webserver -Djava.io.tmpdir=/usr/openv/wmc/webserver/temp org.apache.catalina.startup.Bootstrap start

      root 10623 1  0 Oct05 ?    00:00:01 /usr/openv/netbackup/bin/vnetd -proxy inbound_proxy -number 0

      root 10625 1  0 Oct05 ?    00:00:00 /usr/openv/netbackup/bin/vnetd -proxy outbound_proxy -number 0

      root 10691 1  0 Oct05 ?    00:00:04 /usr/openv/netbackup/bin/vnetd -standalone

      root 10698 1  0 Oct05 ?    00:00:00 /usr/openv/netbackup/bin/bpcd -standaloneE:\Program Files\Veritas\NetBackup\bin

      root 10960 1  0 Oct05 ?    00:00:19 /usr/openv/netbackup/bin/bprd

      root 10978 1  0 Oct05 ?    00:00:00 /usr/openv/netbackup/bin/bpcompatd

      root 11007 1  0 Oct05 ?    00:00:00 /usr/openv/netbackup/bin/bpdbm

      root 11011 11007  0 Oct05 ?    00:00:10 /usr/openv/netbackup/bin/bpjobd

      root 11388 1  0 Oct05 ?    00:00:06 /usr/openv/netbackup/bin/nbcssc -a NetBackup

       

      MM Processes

      ------------

      root 10931 1  0 Oct05 ?    00:00:35 /usr/openv/volmgr/bin/ltid

      root 10937 1  0 Oct05 ?    00:00:35 vmd

       

       

      Shared Veritas Processes

      -------------------------

       

      #####################################

      E:\Program Files\Veritas\NetBackup\bin\bpps

      PS E:\> E:\"Program Files"\Veritas\NetBackup\bin\bpps

       

      COMMAND       PID  LOAD         TIME   MEM              START

      nbdisco      2624 0.000%        3.931   28M  10/05/20 18:32:25.262

      vnetd        2804    0.000%        0.156   11M  10/05/20 18:32:29.162

      nbrmms       2836 0.000%        1.482   36M  10/05/20 18:32:30.301

      vnetd        2844 0.000%        0.234   21M  10/05/20 18:32:30.442

      vnetd        2876 0.000%        0.312   24M  10/05/20 18:32:30.473

      vnetd        2884 0.000%        1.778   19M  10/05/20 18:32:30.473

      nbsl         2580 0.000%        0.889   41M  10/05/20 18:32:38.366

      nbsvcmon     3524 0.000%        0.468   18M  10/05/20 18:32:52.126

      bpinetd      3556 0.000%       27.081   12M  10/05/20 18:32:54.232

      bpcd         3696 0.000%        0.374   16M  10/05/20 18:32:57.305

      ltid         3864 0.000%        0.249   19M  10/05/20 18:32:58.958

      vmd         3672 0.000%        0.187   20M  10/05/20 18:33:13.623

      bpps         8440 0.000%        0.249  8.1M  10/06/20 08:59:22.662

      ###############################################

        The following seems to indicate that pbx service is perhaps not handled by

      Centos master server

      (

      [root]# /etc/rc.d/init.d/vxpbx_exchanged start

      Veritas PBX Exchange daemon not found on this host.

      )

      Also, I found ( on windows media server) “Veritas Private Branch Exchange” service in compu mgmt “services”; however, When I restarted that service,  I saw no impact from that; nothing seemed to change.



      • EthanH's avatar
        EthanH
        Level 4
        5 years ago

        Yes, bpps has different switches for what OS you're using.

        PBX is definitely handled by CentOS, or else you would not have been able to use the server for backups. 

        Stop all processes on the master and media server

        Run bpclntcmd -clear_host_cache

        Start PBX using the default install location for NBU (linked to /etc/init.d): /opt/VRTSpbx/vxpbx_exchanged start

        If it starts successfully on the master server, start the remaining NBU processes with bp.start_all. 

        With NBU processes stopped on your Windows media server, go to Services and restart PBX again. Your order is: Stop NBU processes (confirm with bpps or Task Manager) > stop PBX > start PBX > start NBU processes. If PBX is not running when you start services, things will not come up cleanly and you will keep having issues. 

        These two articles seem to detail what you're experiencing, and they both point to issues with the file system for PBX not being mounted after reboot: 

        https://www.veritas.com/support/en_US/article.100033993

        https://www.veritas.com/support/en_US/article.100031908