cancel
Showing results for 
Search instead for 
Did you mean: 

failed accessing daemon lock file

rookie11
Moderator
Moderator
   VIP   

hii all

master and media server at 7.6.0.1, client solaris version 7.6, SunOS  5.10. backup selection all local driives, multistreaming ON.

when backup stream for '/' starts it fails with error code 158 after writing some data.

bpbkar logs from client server

<16> bpbkar Exit: ERR - bpbkar FATAL exit status = 158: failed accessing daemon lock file
<4> bpbkar Exit: INF - EXIT STATUS 158: failed accessing daemon lock file
<2> bpbkar Exit: INF - Close of stdout complete
<16> bpbkar Exit: ERR - read server exit status = 158: failed accessing daemon lock file
<2> bpbkar manage_fscp_info: Start
<2> bpbkar manage_fscp_info: status=158, checkpoint_restart=900
<2> ct_cat_close: close current track journal
<2> ct_cat_close: close previous track journal
<4> ct_logfiles_deleteall: no log files
<2> bpbkar manage_fscp_info: End
<4> bpbkar Exit: INF - setenv FINISHED=0

already checked few things. no orphan process of bpbkar on server

please suggest something

2 REPLIES 2

sdo
Moderator
Moderator
Partner    VIP    Certified

Did you see this:

https://www.veritas.com/community/forums/image-cleanup-keeps-failing-158-error-failed-accessing-daemon-lock-file-158

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Hopefully 'Cross mount points' is NOT enabled in the policy?

Have you enabled bpbkar log on this client?
Best to increase logging level to higher that 0 (my suggestion : 3)

To troubleshoot issue with this stream only, please create a test policy with only / in Backup Selection.
If bpbkar folder exists, rename the current log file, then run the test policy.

After the failure, please copy the bpbkar log file to bpbkar.txt and upload as File Attachment.

Some TNs that I have found suggest permission problems.
The bpbkar log should point out what/where the problem is.