10-02-2020 05:57 PM
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.
Solved! Go to Solution.
10-07-2020 08:00 PM
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
10-02-2020 07:44 PM
10-05-2020 06:40 AM
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.
10-06-2020 10:40 AM
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.
10-06-2020 12:46 PM
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
10-07-2020 01:24 AM
The main problem is with PBX not running. This is preventing other processes (e.g. nbemm, nbpem, nbrb) from starting up.
Please have a look at the TN's that @EthanH posted to fix this.
Please stop all NBU processes with 'netbackup stop or bp.kill_all', then start PBX.
Only when you have confirmed that PBX is running, start NBU (netbackup start or bp.start_all).
Check with bpps -x
When all is good on the master, You can restart NBU on the Windows media server:
From cmd: bpdown -v -f.
Use Services to stop Private Branch Exchange
Start Private Branch Exchange
From cmd: bpup -v -f
Next:
Speak to your management about CentOS that is not supported as NBU master server.
10-07-2020 07:21 AM
Thank you for posts. I will try things as suggested and will let you know. As to centos master server, we have been using it for some time ( ~3 yrs); Asumption is, maybe not officially supported, but
should be just about identical to RedHat ( and obviously more economical); care to expand a little on dangers of centos?
10-07-2020 07:41 AM
The danger is that if you have a catastrophe or require Veritas support, they will say they are unable to help you because your environment is unsupported.
10-07-2020 07:48 AM
It's not that there is anything wrong with CentOS, it's that CentOS 7 is not a supported OS for NBU master server. If a major issue were to arise on your master, Veritas Support would not be able to assist you.
CentOS has not been a support master server OS for quite some time (I found another forum post from 2015 with warnings against using it as a master server). If it was set up ~3 years ago, it was set up with an unsupported OS and I'd recommend beginning the conversation with your management to rectify it.
CentOS 7 also reached one of its EoSL in August, which means there will be no more full updates provided for it (maintenace updates will still be released). This means you will be not only running an unsupported OS from an NBU perspective, but will most likely be out of compliance for other requirements as well.
10-07-2020 03:21 PM
Hi @fly99h
Just to clarify things around Centos support for a master server OS platform - what others have said is true in that for NetBackup 8.1.2 is is an unsupported OS platform. Cheap and "about identical" are not good reasons to use for something critical like data protection.
However Centos it is not completely unsupported. If you are running NetBackup 8.2 or newer, then Centos is a supported platform for a master server depending on which version of Centos is used (Centos 8.1+, or Centos 7.7+) - you should check the SCL for further details.
10-07-2020 03:54 PM
Thank you for posts and ideas. I tried a few things on the centos master server, but no luck so far it seems. /etc/rc.d/init.d/vxpbx_exchanged is not a link in our case. And we happen to have centos 7.6.1810 .
[root@CENTOS-SERVER ~]# bpclntcmd -clear_host_cache
Successfully cleared host cache
Successfully cleared peer validation cache
[root@CENTOS-SERVER ~]# /etc/rc.d/init.d/vxpbx_exchanged start
Veritas PBX Exchange daemon not found on this host.
[root@CENTOS-SERVER ~]# systemctl status vxpbx_exchanged.service
â vxpbx_exchanged.service - SYSV: Provides Veritas Private Branch Exchange
Loaded: loaded (/etc/rc.d/init.d/vxpbx_exchanged; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2020-10-05 18:45:38 PDT; 1 day 19h ago
Docs: man:systemd-sysv-generator(8)
Process: 8499 ExecStart=/etc/rc.d/init.d/vxpbx_exchanged start (code=exited, status=1/FAILURE)
Oct 05 18:45:38 CENTOS-SERVER systemd[1]: Starting SYSV: Provides Veritas Private Branch Exchange...
Oct 05 18:45:38 CENTOS-SERVER vxpbx_exchanged[8499]: Veritas PBX Exchange daemon not found on this host.
Oct 05 18:45:38 CENTOS-SERVER systemd[1]: vxpbx_exchanged.service: control process exited, code=exited status=1
Oct 05 18:45:38 CENTOS-SERVER systemd[1]: Failed to start SYSV: Provides Veritas Private Branch Exchange.
Oct 05 18:45:38 CENTOS-SERVER systemd[1]: Unit vxpbx_exchanged.service entered failed state.
Oct 05 18:45:38 CENTOS-SERVER systemd[1]: vxpbx_exchanged.service failed.
[root@CENTOS-SERVER ~]#
[root@CENTOS-SERVER log]# cat /var/log/messages | grep -i pbx
Oct 5 12:31:54 CENTOS-SERVER nbatd[23650]: V-18--1 Failed to open PBX acceptor
Oct 5 16:33:49 CENTOS-SERVER nbatd[11646]: V-18--1 Failed to open PBX acceptor
Oct 5 16:49:53 CENTOS-SERVER nbatd[16644]: V-18--1 Failed to open PBX acceptor
Oct 5 18:14:32 CENTOS-SERVER vxpbx_exchanged: Veritas PBX Exchange daemon not found on this host.
Oct 5 18:14:32 CENTOS-SERVER systemd: vxpbx_exchanged.service: control process exited, code=exited status=1
Oct 5 18:14:32 CENTOS-SERVER systemd: Unit vxpbx_exchanged.service entered failed state.
Oct 5 18:14:32 CENTOS-SERVER systemd: vxpbx_exchanged.service failed.
Oct 5 18:14:41 CENTOS-SERVER nbatd[9401]: V-18--1 Failed to open PBX acceptor
Oct 5 18:45:38 CENTOS-SERVER vxpbx_exchanged: Veritas PBX Exchange daemon not found on this host.
Oct 5 18:45:38 CENTOS-SERVER systemd: vxpbx_exchanged.service: control process exited, code=exited status=1
Oct 5 18:45:38 CENTOS-SERVER systemd: Unit vxpbx_exchanged.service entered failed state.
Oct 5 18:45:38 CENTOS-SERVER systemd: vxpbx_exchanged.service failed.
Oct 5 18:45:46 CENTOS-SERVER nbatd[9429]: V-18--1 Failed to open PBX acceptor
[root@CENTOS-SERVER log]#
[root@CENTOS-SERVER log]# ls -l /etc/init.d/vxpbx_exchanged
-r-xr-x---. 1 root root 11014 Oct 16 2018 /etc/init.d/vxpbx_exchanged
[root@CENTOS-SERVER log]# nbemmcmd –listhosts // this command hangs as shown
NBEMMCMD, Version: 8.1
# ls /var/run/systemd/generator.late
CISCOSMIS.service FMServer.service PIPELINE.service velocity-storage.service
elasticsearch.service netbackup.service runlevel2.target.wants vxpbx_exchanged.service
Elasticsearch.service netconsole.service runlevel3.target.wants
flexnet_admin-service.service network.service runlevel4.target.wants
flexnet_report-service.service pdde-storage.service runlevel5.target.wants
# cat vxpbx_exchanged.service
# Automatically generated by systemd-sysv-generator
[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/rc.d/init.d/vxpbx_exchanged
Description=SYSV: Provides Veritas Private Branch Exchange
Before=runlevel2.target
Before=runlevel3.target
Before=runlevel4.target
Before=runlevel5.target
Before=shutdown.target
Before=FMServer.service
Before=flexnet_admin-service.service
Before=flexnet_report-service.service
Before=elasticsearch.service
Before=netbackup.service
Before=CISCOSMIS.service
Before=PIPELINE.service
After=network-online.target
After=network.service
Conflicts=shutdown.target
[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
ExecStart=/etc/rc.d/init.d/vxpbx_exchanged start
ExecStop=/etc/rc.d/init.d/vxpbx_exchanged stop
10-07-2020 04:09 PM
Hi @fly99h
Has someone messed around with the contents of the /opt file system? That message you show when trying to start PBX is indicating that the init script cannot find the binary!
Investigate if the directory/folder "/opt/VRTSpbx/bin/" exists and that there is a binary pbx_exchange in that directory (if it exists, check the size as well). Also can you run the command "rpm -qa | grep VRTSpbx" and show the output to verify that the RPM binary is still installed.
Cheers
David
10-07-2020 05:05 PM
It looks like /opt/VRTSpbx may have been deleted indeed at some point ( maybe ~ 1mo ago ).
VRTSpbx-1.7.13.0-0.x86_64 appears installed.
10-07-2020 05:11 PM - edited 10-07-2020 05:13 PM
There is nothing special with the installation of this RPM.
If you are lucky, the folder has been moved - try to see if you can find the binary:
"find / -name pbx_exchange" to see if you can locate it (if you find it see if it and its folder) can be relocated back to where it needs to be. Failing thatFind the rpm in the installation bundle and reinstall it.
10-07-2020 05:19 PM
About a month ago when the root ( / ) directory disk space was filled up; somebody may have deleted the /opt/VRTSpbx dir inadvertently, thinking it was not important..
What should be done at this point? Thank you.
###########################
[root@CENTOS-SERVER opt]# rpm -qa |grep VRTSpbx
VRTSpbx-1.7.13.0-0.x86_64
# cd /opt
[root@CENTOS-SERVER opt]# du -h --max-depth=1
3.2G ./anaconda3
4.0K ./veritas
2.3M ./Symantec
8.1G ./openv
793M ./scc
8.2G ./FLEXnet
12K ./pdde
23M ./emc
21G .
[root@CENTOS-SERVER opt]# date
Wed Oct 7 16:58:13 PDT 2020
[root@CENTOS-SERVER opt]# du -h --max-depth=1 // notes from the past
0 ./rh
3.2G ./anaconda3
4.0K ./veritas
2.3M ./Symantec
21G ./openv
793M ./scc
2.4G ./FLEXnet
12G ./openv_20181016
26M ./VRTSpbx
12K ./pdde
39G .
10-07-2020 05:25 PM
Would installing the .rpm require signature/certificate, etc. ?
10-07-2020 05:32 PM
No - you may need to tweak the normal rpm commands to get the rpm to install (--force maybe), but as I indicated, there is nothing special about the installation of the package itself. You should be able to find the RPM in the client install binary folder (/usr/openv/netbackup/client/Linux/RedHat2.6.32/VRTSpbx.rpm)
10-07-2020 07:35 PM
The installation appears not going smoothly. I created a snapshot for the master server on vSphere first; then I tried to remove the package and re-install ;
#############
[root@CENTOS-SERVER ~]# ls -l /opt/openv/netbackup/client/Linux/RedHat2.6.32/VRTSpbx.rpm
-r-xr-xr-x. 1 root daemon 6635380 Aug 27 2018 /opt/openv/netbackup/client/Linux/RedHat2.6.32/VRTSpbx.rpm
[root@CENTOS-SERVER ~]# yum info VRTSpbx
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
* base: mirrors.usinternet.com
* extras: centos.mirror.ndchost.com
* updates: centos.s.uw.edu
Installed Packages
Name : VRTSpbx
Arch : x86_64
Version : 1.7.13.0
Release : 0
Size : 26 M
Repo : installed
Summary : Veritas Private Branch Exchange
License : Copyright (c) 2017 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered
: trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their
: respective owners. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212
: and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS
: 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor
: regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and
: Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.
Description : Veritas Private Branch Exchange
##############
# yum remove VRTSpbx
Loaded plugins: fastestmirror, langpacks
Resolving Dependencies
There are unfinished transactions remaining. You might consider running yum-complete-transaction, or "yum-complete-transaction --cleanup-only" and "yum history redo last", first to finish them. If those don't work you'll have to try removing/installing packages by hand (maybe package-cleanup can help).
--> Running transaction check
---> Package VRTSpbx.x86_64 0:1.7.13.0-0 will be erased
--> Processing Dependency: VRTSpbx >= 1.7 for package: VRTSnbclt-8.1.0.0-1505107526.x86_64
--> Running transaction check
---> Package VRTSnbclt.x86_64 0:8.1.0.0-1505107526 will be erased
--> Processing Dependency: VRTSnbclt >= 8.1.0.0 for package: VRTSnbcfg-8.1.0.0-1505107442.x86_64
--> Processing Dependency: VRTSnbclt >= 8.1.0.0 for package: VRTSnbjava-8.1.0.0-1505107483.x86_64
--> Running transaction check
---> Package VRTSnbcfg.x86_64 0:8.1.0.0-1505107442 will be erased
---> Package VRTSnbjava.x86_64 0:8.1.0.0-1505107483 will be erased
--> Finished Dependency Resolution
--> Finding unneeded leftover dependencies
Found and removing 0 unneeded dependencies
http://mirrors.tripadvisor.com/centos/7.8.2003/os/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to 129.198.69.26:8080; Connectio n refused"
Trying other mirror.
http://mirror.cs.vt.edu/pub/CentOS/7.8.2003/os/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to 129.198.69.26:8080; Connection r efused"
...
http://mirror.clarkson.edu/centos/7.8.2003/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to 129.198.69.26:8080; Connecti on refused"
Trying other mirror.
Dependencies Resolved
==================================================================================================================================================
Package Arch Version Repository Size
==================================================================================================================================================
Removing:
VRTSpbx x86_64 1.7.13.0-0 installed 26 M
Removing for dependencies:
VRTSnbcfg x86_64 8.1.0.0-1505107442 installed 31 k
VRTSnbclt x86_64 8.1.0.0-1505107526 installed 480 M
VRTSnbjava x86_64 8.1.0.0-1505107483 installed 335 M
Transaction Summary
==================================================================================================================================================
Remove 1 Package (+3 Dependent packages)
Installed size: 840 M
Is this ok [y/N]: y
…
warning: file /opt/VRTSpbx/bin/cluster/offline: remove failed: No such file or directory
warning: file /opt/VRTSpbx/bin/cluster/monitor_server: remove failed: No such file or directory
warning: file /opt/VRTSpbx/bin/cluster/monitor: remove failed: No such file or directory
warning: file /opt/VRTSpbx/bin/cluster/clean: remove failed: No such file or directory
warning: file /opt/VRTSpbx/bin/cluster/VxPBXclconf.pl: remove failed: No such file or directory
warning: file /opt/VRTSpbx/bin/cluster/VxPBXClusEnv.conf: remove failed: No such file or directory
warning: file /opt/VRTSpbx/bin/cluster/VCS-Clus-Readme.txt: remove failed: No such file or directory
Verifying : VRTSpbx-1.7.13.0-0.x86_64 1/4
Verifying : VRTSnbclt-8.1.0.0-1505107526.x86_64 2/4
Verifying : VRTSnbcfg-8.1.0.0-1505107442.x86_64 3/4
Verifying : VRTSnbjava-8.1.0.0-1505107483.x86_64 4/4
Removed:
VRTSpbx.x86_64 0:1.7.13.0-0
Dependency Removed:
VRTSnbcfg.x86_64 0:8.1.0.0-1505107442 VRTSnbclt.x86_64 0:8.1.0.0-1505107526 VRTSnbjava.x86_64 0:8.1.0.0-1505107483
Complete!
[root@CENTOS-SERVER ~]# yum install /opt/openv/netbackup/client/Linux/RedHat2.6.32/VRTSpbx.rpm
Loaded plugins: fastestmirror, langpacks
Examining /opt/openv/netbackup/client/Linux/RedHat2.6.32/VRTSpbx.rpm: VRTSpbx-1.10.14.0-0.x86_64
Marking /opt/openv/netbackup/client/Linux/RedHat2.6.32/VRTSpbx.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package VRTSpbx.x86_64 0:1.10.14.0-0 will be installed
--> Finished Dependency Resolution
--> Finding unneeded leftover dependencies
Found and removing 0 unneeded dependencies
http://mirrors.tripadvisor.com/centos/7.8.2003/os/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to 129.198.69.26:8080; Connection refused"
Trying other mirror.
http://mirror.cs.vt.edu/pub/CentOS/7.8.2003/os/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to 129.198.69.26:8080; Connection refused"
…….
Dependencies Resolved
============================================================================================================================================================
Package Arch Version Repository Size
============================================================================================================================================================
Installing:
VRTSpbx x86_64 1.10.14.0-0 /VRTSpbx 24 M
Transaction Summary
============================================================================================================================================================
Install 1 Package
Total size: 24 M
Installed size: 24 M
Is this ok [y/d/N]: y
Downloading packages:
Package VRTSpbx.rpm is not signed
10-07-2020 08:00 PM
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
10-08-2020 01:22 PM