RE: socket write failed

see this document: http://seer.entsupport.symantec.com/docs/323218.htm

Solution:
1. Disable SELinux security setting:
#sudo /usr/sbin/setenforce 0

2. Perform NBU 6.5.3 update procedure

3. Once the 6.5.3 update is complete:
#cd /usr/openv/lib
#sudo chcon -t textrel_shlib_t *.so*
This changes the security context of the shared object file which allows it to be executed.

4. Enable SE Linux security setting again:
#sudo /usr/sbin/setenforce 1
 

Hi Wrobbins,

As I am already using 6.5.4 version, is this solution applicable to this version too?

Thanks

Bharath

Have not run into this myself but figure it's worth a try !

Operating systems (master/client) - if it is linux, kudos to Bill!!!

Any clues in the problems report & logs?

Please always supply all relevant info when starting a new discussion:

https://www-secure.symantec.com/connect/forums/important-things-address-when-starting-new-threads

We need O/S versions of server and client as well as NBU version. Having as much info as possible will eliminate responses that might not be relevant to your situation.

This TN applies to Linux Clients for all NBU versions:

http://seer.entsupport.symantec.com/docs/347002.htm

Let us know what errors can be seen Job Details and bpbkar log.

Seems like my recommendation worked