cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Failing with Error 13 : NIS Does Not Seems to be Running

Hi Team,

 

I am facing issues with Backup of a Solaris Client.

Backup is failing with error 13...

Error with bpclntcmd -self is below..

root@OVM-brcytrgws1 # ./bpclntcmd -self
yp_get_default_domain failed: (6) internal yp server or client error
NIS does not seem to be running: (1) args to yp function are bad
gethostname() returned: ovm-brcytrgws1-bpg.uk.tcgdns.com
host ovm-brcytrgws1-bpg.uk.tcgdns.com: ovm-brcytrgws1-bpg.uk.tcgdns.com at 10.17.136.**
aliases:     ovm-brcytrgws1-bpg.uk.tcgdns.com     10.17.136.**

Kindly help.

 

Regards,

Pankaj Narang

1 Solution

Accepted Solutions
Accepted Solution!

Unless your host is

Unless your host is configured to lookup hostname thru NIS, this NIS(yp) error can be ignored. Your host name is successfuly resolved to 10.17.136.** by other method like DNS, hosts file or so.

Status code 13 means "file read failed", which is likely not related to name resolving. Look into job detail to identify in which point or process any error is first logged, and check related debug logs.

View solution in original post

3 Replies
Accepted Solution!

Unless your host is

Unless your host is configured to lookup hostname thru NIS, this NIS(yp) error can be ignored. Your host name is successfuly resolved to 10.17.136.** by other method like DNS, hosts file or so.

Status code 13 means "file read failed", which is likely not related to name resolving. Look into job detail to identify in which point or process any error is first logged, and check related debug logs.

View solution in original post

I agree with Yasuhisa - NIS

I agree with Yasuhisa - NIS message can be ignored.

I have never seen status 13 being caused by name resolution.

'File read failed' can be anything from a real file read error to network read error.
The 1st step to troubleshoot is to have a look at the info in Details tab of the failed job.
If you post it here, we can point you in the right direction.

In the meantime, ensure all of these log folders exist:
on media server: bpbrm and bptm
on client: bpcd and bpbkar

NIS does not seem to be

NIS does not seem to be running happens on every host where NIS is not running, when you run bpcltncmd commands,  just ignore that message as mentioned.

How long has the status 13 been happening for? Has that backup worked in the past?

Try rebooting the client (if possible), check the logs Marianne has posted above to see where the failure occurs first.