Forum Discussion
- quebekModerator
Hey
Anything in logs under /usr/openv/netbackup/logs/admin/
??
Maybe you will have to change verbose = 5 in bp.conf and do bprdreq -rereadconfig and execute this bpexpdate again
- mdderechoLevel 3
Hi guys, thanks for reply, herein the logs I got in /usr/openv/netbackup/logs/admin/root.053121_00001.log
[root@PMLPMSDPINF01 admin]# tail root.053121_00001.log
17:02:27.191 [58181] <2> dump_proxy_info: ----process_hint_reason: a known master server is the connected peer
17:02:27.193 [58181] <2> logconnections: PROXY CONNECT FROM 10.7.231.146.35496 TO 10.7.231.147.1556 fd = 10
17:02:27.193 [58181] <2> logconnections: BPDBM CONNECT FROM 127.0.0.1.49417 TO 127.0.0.1.40118 fd = 10
17:02:27.212 [58181] <2> isDONE: reply DONE 43 <?xml version="1.0" encoding="utf-8"?><StatusMsgDoc><StatusMsg NBUStatus="43" Severity="2" VXULoid="271" VXULtid="43"><MsgString>unexpected message received</MsgString></StatusMsg></StatusMsgDoc>
17:02:27.212 [58181] <2> isDONE: reply DONE 43
17:02:27.212 [58181] <2> db_startrequest: protocol error 1
17:02:27.212 [58181] <16> db_begin: db_startrequest() failed: unexpected message received
17:02:27.213 [58181] <2> db_IMAGE: db_begin() failed: unexpected message received
17:02:27.213 [58181] <16> bpexpdate: db_IMAGE() failed: unexpected message received (43)
17:02:27.221 [58181] <2> main: EXIT STATUS 43: unexpected message received- quebekModerator
Hi
Hmmm this log is too short... but it does not look good. please provide more. Also I would look into bpdbm logs and bprd to check out there...
Also it would not harm to run nbcc in order to check catalog consistency.
https://www.veritas.com/support/en_US/doc/15263389-130536298-0/v48054848-130536298
https://www.veritas.com/support/en_US/downloads/update.UPD639818
- mdderechoLevel 3
hi guys, thanks for helping, Im now able to change the expiration date via master server. Thank you again.
Related Content
- 13 years ago
- 11 years ago
- 3 years ago