error 25 request daemon will not start on same server master/client debug inside

[Jbouey]

getting this error constantly the request daemon will not start at all. someone please assist thanks

[sdo]

Many of us will not open PDF or Word files.  Please remove the word docx file, and re-attach output as plain ascii text .txt file.  Thank you.

[Marianne]

@Jbouey 

Do you have bprd log folder on the master server?
If not, please create the folder and restart NBU. 

Copy the log file in bprd folder to bprd.txt and upload here. 

[Jbouey]

text file attached. after reading this im seeing that the service is marked for deletion.... which was another issue with the request daemon. it would not start initially because it was marked for deletion. how do i get it restored. there is no delete flag. also thanks guys

[Jbouey]

more up to date bprd reading....from what i understand maybe their is a case sensitive issue? why isnt n1-ph-we-a125 not the primary server N1-PH-WE-A125.oly.tds. 13:23:00.906 [4796.4792] <2> bprd: INITIATING bprd (VERBOSE = 0): NetBackup 8.1 2017091018 on n1-ph-we-a125 13:23:00.906 [4796.4792] <2> bprd: Now initializing logging for libcorbaobj 13:23:00.906 [4796.4792] <2> bprd: the request timeout value is 300 seconds 13:23:00.906 [4796.4792] <2> bprd: n1-ph-we-a125 is not the primary server N1-PH-WE-A125.oly.tds...exiting 13:49:08.903 [5068.4808] <2> bprd: INITIATING bprd (VERBOSE = 0): NetBackup 8.1 2017091018 on N1-PH-WE-A125 13:49:08.903 [5068.4808] <2> bprd: Now initializing logging for libcorbaobj 13:49:08.918 [5068.4808] <2> bprd: the request timeout value is 300 seconds 13:49:08.918 [5068.4808] <2> bprd: N1-PH-WE-A125 is not the primary server N1-PH-WE-A125.oly.tds...exiting My setup in regedit config is as follows: Browser: N1-PH-WE-A125.oly.tds Client_Name: N1-PH-WE-A125.oly.tds EMMSERVER: n1-ph-we-a125.oly.tds Server: N1-PH-WE-A125.oly.tds N1-PH-WE-A125 n1-ph-we-a125 n1-ph-we-a125.oly.tds

[Jbouey]

more up to date bprd reading....from what i understand maybe there is a case sensitive issue? why isnt n1-ph-we-a125 not the primary server

N1-PH-WE-A125.oly.tds. 13:23:00.906 [4796.4792] <2> bprd: INITIATING bprd (VERBOSE = 0): NetBackup 8.1 2017091018 on n1-ph-we-a125
13:23:00.906 [4796.4792] <2> bprd: Now initializing logging for libcorbaobj
13:23:00.906 [4796.4792] <2> bprd: the request timeout value is 300 seconds
13:23:00.906 [4796.4792] <2> bprd: n1-ph-we-a125 is not the primary server N1-PH-WE-A125.oly.tds...exiting
13:49:08.903 [5068.4808] <2> bprd: INITIATING bprd (VERBOSE = 0): NetBackup 8.1 2017091018 on N1-PH-WE-A125
13:49:08.903 [5068.4808] <2> bprd: Now initializing logging for libcorbaobj
13:49:08.918 [5068.4808] <2> bprd: the request timeout value is 300 seconds
13:49:08.918 [5068.4808] <2> bprd: N1-PH-WE-A125 is not the primary server N1-PH-WE-A125.oly.tds...exiting

My setup in regedit config is as follows:
Browser: N1-PH-WE-A125.oly.tds
Client_Name: N1-PH-WE-A125.oly.tds
EMMSERVER: n1-ph-we-a125.oly.tds
Server: N1-PH-WE-A125.oly.tds
N1-PH-WE-A125
n1-ph-we-a125
n1-ph-we-a125.oly.tds

[Jbouey]

a lil more context

[Marianne]

@Jbouey 

Has this installation ever worked?

If so, has someone added/changed names in Registry Server entries? Aliases added above the original entry?

When you install NBU as Master server, the Master and EMM entries are populated by default.

The 1st name in the registry must correspond with the master server's local hostname. And yes. NBU is case sensitive.
Additional Server names and aliases must be added after the 1st entry (Master).

1st thing to verify is how the master server is resolving it's own name - run commands like 'hostname' and 'bpclntcmd -self'.
(bpclntcmd is in ....netbackup\bin directory.)

If I look at bprd log, it seems that local hostname is n1-ph-we-a125
'INITIATING bprd (VERBOSE = 0): NetBackup 8.1 2017091018 on n1-ph-we-a125'

Please verify what the hostname is, then we can take it from there.

As a workaround, you can add all possible variations of the hostname as aliases in the server's own hosts file. 

Oh, this is really worrying: 

'Could not start the NetBackup Database Manager service: The dependency service does not exist or has been marked for deletion. (1075)'

Makes me wonder if this installation has ever worked? 

[sdo]

I have similar question... has this ever worked, or is this a new build?

To me it looks like a failed or incomplete install or repair or un-install.  Maybe someone accidentally started a repair or uninstall and aborted it.  Or maybe server was rebooted during an install, repair, or uninstall.  Look for, and inspect any NetBackup related logs here:

dir /s /b /a C:\ProgramData\*NetBackup*.log
dir /s /b /a C:\Users\*NetBackup*.log

[Jbouey]

new build it  worked for about 3 weeks then stopped working one day when i logged in it wouldnt connect.. the hostname for the master/client server is n1-ph-we-a125 full name n1-ph-we-a124.oly.tds. yes i edited the registry trying multiple combinations since it seemed that it could not read the DNS entry. BUT this was only after the errors occured. the first issue was the request daemon  which started the error 25 because it seemingly could not reach the database. so.... 

seems i went to repair the installation to perhaps repair the service and this happened

i adjusted the emm setting then it went

above says my hostname is N1-PH-WE-A125

but below says....

these are my latest settings....another thing i wondered was when i installed i enter the full domain n1-ph-we-a125.oly.tds instead of just N1-PH-WE-A125...i thought id seen a post here saying thats a no no. thanks for you guys help

[Jbouey]

still marked for deletion....i honestly think the FQDN and DNS are getting mixed up

[Marianne]

Pity you did not log a Support call before you started to make changes in the Registry.

The MOST valuable piece of advice that I was given by a Veritas catman (catalog manipulation) trainer was this:

When you're in a hole, stop digging!

Changing hostnames in NBU or at OS-level is a BIG non-no on a master server.
Hostnames are so deeply embedded in the NBU databases that it should only be attempted by a person with appropriate training and a deep understanding of NBU catalogs/databases.

The DBM service is worrying.

Your best bet now is to re-install NBU from scratch and restore your last good catalog backup. 

If the status 25 errors pop up again, please log a Support call with Veritas. 

[sdo]

Please can we see:

type "C:\Program Files\Veritas\NetBackupDB\CONF\server.conf"
findstr /v /i "^I. " "C:\Program Files\Veritas\NetBackupDB\log\server.log"
findstr /v "<2> <4>" "C:\Program Files\Veritas\NetBackup\logs\bpdbm\*.log"

...and it's probably best to attach the output as a text file.

And, adjust the drive letter as required, because maybe you installed to D: volume.

[Jbouey]

*sigh.....alright thanks guys 

[sdo]

Try the search of the bpdbm logs again.  I think you might have missed the /v switch and missed the <4> when you typed the command in.

[Jbouey]

second command wouldnt work entered as follows..... so i went to the bpdbm folder and checked

[sdo]

I was after this:

findstr /v "<2> <4>" "C:\Program Files\Veritas\NetBackup\logs\bpdbm\*.log"

...please.  In a text file.  :)   Thank you.

[Hamza_H]

Hello,

How about a bpcltncmd -clear_host_cache  ?