Highlighted

Policy creation failed with status 254

New NBU 8.2 installation on SLES 12 SP4.

bppolicynew data -M n2810-bsl -verbose
<2>bppolicynew: INITIATING: version NetBackup 8.2 created: 2019062501
<2>bppolicynew: server name not found in the NetBackup configuration
<2>bppolicynew: EXIT status = 254
server name not found in the NetBackup configuration

The same happens when attemted via the GUI

Any idea?

admin log file:

bppolicynew: INITIATING: version NetBackup 8.2 created: 2019062501
17:10:37.298 [29864] <2> logparams: data -M n2810-bsl -verbose
17:10:37.298 [29864] <2> bppolicynew: VERBOSE = 5
17:10:37.321 [29864] <2> vnet_pcache_init_table: [vnet_private.c:207] starting cache size 200 0xc8
17:10:37.323 [29864] <2> LOCAL CLASS_ATT_DEFS: Product ID = 6
17:10:37.324 [29864] <2> nbapp_info_init_ex: path=/etc/nbapp-release
17:10:37.325 [29864] <2> read_keyvalue_file: failed to open file: "/etc/nbapp-release", status: 12
17:10:37.325 [29864] <2> nbapp_info_init_ex: read_keyvalue_file failed, path:/etc/nbapp-release, status: 12
17:10:37.325 [29864] <8> vnet_get_user_credential_path: [vnet_vxss.c:1620] status 35 0x23
17:10:37.325 [29864] <8> vnet_check_user_certificate: [vnet_vxss_helper.c:4122] vnet_get_user_credential_path failed 35 0x23
17:10:37.325 [29864] <2> ConnectionCache::connectAndCache: Acquiring new connection for host n2810-bsl, query type 186
17:10:37.325 [29864] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3215] Comparing name1:[n2810-bsl] name2:[localhost]
17:10:37.326 [29864] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3340] matched as locals NAME1=n2810-bsl NAME2=localhost
17:10:37.327 [29864] <2> vnet_sortaddrs: [vnet_addrinfo.c:4408] sorted addrs: 1 0x1
17:10:37.327 [29864] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:5395] Local [strong] check, using interface ANY
17:10:37.327 [29864] <2> init_resilient_cache: [vnet_nbrntd.c:1878] Initialize resilient cache. 0 0x0
17:10:37.328 [29864] <2> async_connect: [vnet_connect.c:2782] connect in progress 1 0x1
17:10:37.328 [29864] <2> is_connection_INBOUND: non-proxy, localhost connection
17:10:37.328 [29864] <2> is_connection_INBOUND: Connection-Is-INBOUND:[FALSE]
17:10:37.329 [29864] <2> async_connect: [vnet_connect.c:2974] connect async CONNECT FROM 10.10.44.6.43757 TO 10.10.44.6.13721 fd = 4
17:10:37.329 [29864] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO n2810-bsl 10.10.44.6 bpdbm
17:10:37.329 [29864] <2> is_connection_INBOUND: non-proxy, localhost connection
17:10:37.329 [29864] <2> is_connection_INBOUND: Connection-Is-INBOUND:[FALSE]
17:10:37.330 [29864] <2> is_connection_INBOUND: non-proxy, localhost connection
17:10:37.330 [29864] <2> is_connection_INBOUND: Connection-Is-INBOUND:[FALSE]
17:10:37.331 [29864] <2> logconnections: BPDBM CONNECT FROM 10.10.44.6.43757 TO 10.10.44.6.13721 fd = 4
17:10:37.331 [29864] <2> vnet_check_vxss_client_magic_with_info_ex: [vnet_vxss_helper.c:1137] Ignoring VxSS authentication 2 0x2
17:10:37.403 [29864] <4> TZ: Send Timezone offset=-3600
17:10:37.404 [29864] <2> db_end: Need to collect reply
17:10:37.459 [29864] <2> isDONE: reply DONE 254 <?xml version="1.0" encoding="utf-8"?><StatusMsgDoc><StatusMsg NBUStatus="254" Severity="2" VXULoid="271" VXULtid="254"><MsgString>server&#32;name&#32;not&#32;found&#32;in&#32;the&#32;NetBackup&#32;configuration</MsgString></StatusMsg></StatusMsgDoc>
17:10:37.470 [29864] <2> isDONE: reply DONE 254
17:10:37.470 [29864] <2> db_end: no DONE from db_getreply(): server name not found in the NetBackup configuration
17:10:37.470 [29864] <2> closeConnection: Caching connection for query type 186 for reuse
17:10:37.471 [29864] <2> db_CLASS: db_end_sts() failed: server name not found in the NetBackup configuration (254)

Tags (2)
1 Solution

Accepted Solutions
Accepted Solution!

Re: Policy creation failed with status 254

Thanks guys for you suggestions.

I eventually found the reason for that strange error message.

During installation I added a second backup interface to the Master server name *-bkp without changing the name of the Master server to that name.

Once I made the neccessary changes everythin is now working as expected/

View solution in original post

Tags (1)
5 Replies

Re: Policy creation failed with status 254

1) Is this new NBU 8.2 install on SLES 12 SP4 a new standalone master server, or is it a new media server of the master named "n2810-bsl" ?

2) If this is a brand new install, maybe you can check the install log file, something like:   /tmp/install_trace.<number>     and check for errors / failures during the product install

3) This tech note might help re status 254:

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

Re: Policy creation failed with status 254

This installation does not look healthy

Does the file exist :
read_keyvalue_file: failed to open file: "/etc/nbapp-release", status: 12

How does bp.conf looks ?

Is /etc/hosts world readable ?

 

 

Re: Policy creation failed with status 254

Please help us understand where these 2 IP addresses fit in the picture?

10.10.44.6
17:10:37.329

Re: Policy creation failed with status 254

@Marianne  I believe 17:10:37.329 is a time stamp as it is not a valid IP. Copy and past error ?

Accepted Solution!

Re: Policy creation failed with status 254

Thanks guys for you suggestions.

I eventually found the reason for that strange error message.

During installation I added a second backup interface to the Master server name *-bkp without changing the name of the Master server to that name.

Once I made the neccessary changes everythin is now working as expected/

View solution in original post

Tags (1)