02-08-2012 12:04 AM
We used to back up the file systems / and /opt on our solaris 10 netbackup clients until recently. The back up fails every time I take the backup
with status 13 file read failed. From the bpbkar log I was able to see the error below
read_and_sort_dir_entries: WRN - Cannot lstat some file name Error = 2 there is no such file
after this error the last one read the network link is brocken always displayed but I dont think there is a network problem because on the same machine the other policies( oracle policies) worked with out any problem. Any of your help will be appreciated
Solved! Go to Solution.
02-09-2012 01:01 AM
02-08-2012 12:35 AM
This messages means lstat() call to the file returns ENOENT. Please check file by "ls -l file_name" first.
And also check file name(s) reported are always same or not, and any clue recorded in syslog(/var/adm/messages).
This message is warning level, so this does not cause status 13 error. You should set higher logging level(VERBOSE = 5 in bp.conf), and reproduce this error.
02-08-2012 03:29 AM
thanks for the quick reply yasuhisa. I tried to reproduce the error by manually backing up the system but the back up finished successfully in the 2nd retry, and I cant generate the log. There is nothing reported in /var/adm/messages. I will wait till tomorrow the policy to run with the schedule and post u the log.
02-08-2012 06:26 AM
If you can not repuroduce this error, it might be timing issue. I suppose this error occured in senario like below.
02-08-2012 09:42 AM
Good responses above, by Yasuhisa. As he mentions, more details are needed...
W.R.T. "until recently" in the orginal question, did NBU get upgraded or reconfigured recently on this system...?
The verbose "read_and_sort_dir_entries: WRN - Cannot lstat some file name Error = 2 there is no such file" by itself is NOT an issue, as the backup logs that as a WRN message, and reports it as a TRV message to NBU server, and moves on to the next file, WITHOUT incrementing the error count. What that "some file name" is would probably help somewhat, and also if there is more than one file that reports that verbose.
W.R.T. "after this error the last one read the network link is broken always displayed", good to have that "some file name" to see what happened, even though you mention that the backup is of "file systems / and /opt" - both of which are presumably local filesystems.
02-08-2012 11:25 PM
actually when the policy run at night the error appeared and after I set the VERBOSE=5, here is the out put of bpbkar at the time of failure
PrintFile: /opt/s2100/om/
18:56:34.908 [24212] <8> bpbkar read_and_sort_dir_entries: WRN - Cannot lstat PMData_5min.xml.1302826861109. Errno = 2: No such file or directory
19:00:32.769 [24212] <16> bpbkar sighandler: ERR - bpbkar killed by SIGPIPE
19:00:32.769 [24212] <2> bpbkar sighandler: INF - ignoring additional SIGPIPE signals
19:00:32.780 [24212] <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 40: network connection broken
19:00:32.780 [24212] <4> bpbkar Exit: INF - EXIT STATUS 40: network connection broken
19:00:32.780 [24212] <2> bpbkar Exit: INF - Close of stdout complete
19:00:32.780 [24212] <4> bpbkar Exit: INF - setenv FINISHED=0
there are toomany PrintFile: xxxxxxxxxxxxxxxxx above this out put. I donot agree with the ntwk because the oracle policy is running without any error.\
Thank you!
02-09-2012 01:01 AM
02-13-2012 10:41 PM
thank you both yasuhisa and mn_ pankaj for your kind response. I added the file that lstat() can't get a return in my exclude_list file and the backup is running flawlessly. I will monitor it for some time and close the thread.