Quantcast
Channel: All Data Protector Practitioners Forum posts
Viewing all articles
Browse latest Browse all 10494

Re: The execution of the script was interrupted (most probably the script died ungracefully).

$
0
0

Most of what I found on this error involves having OES2 installed on the Linux system, which, to my knowledge, makes it look like a Novell server.  Please check for this, if it does not have this application present, you can ignore the 1st three possibilities

 

===========

 

Cause
SMS services have failed or not been started.

Workaround / Fix

This issue is resolved after re-starting SMS service using the command:
/etc/init.d/novell-smdrd start

 

===============

 

Run ls /opt/omni/lib
Go to cd /etc
Run ls *rel*
cat novell-release
                 If it has OES in the patch level

 Then, rename the novell-release file
                      for example: novell-release.old

Remove the Client installation from the DP GUI
Install the Client again.

 

==================

 

Cause

It appeared that the required service tsafs wasn't running.
Check using:

/opt/novell/sms/bin/smsconfig -l tsafs
Could not communicate with SMDR

 

 

Workaround / Fix

From http://www.novell.com/support/viewContent.do?externalId=7001767  is how to start the tsafs service.

 

==============

 

Now, a non-OES2 possibility

 

Check the /etc/hosts file on the Linux client, and make sure this line is in there

127.0.0.1  localhost loopback

The entry is actually the work 'localhost', not a hostname

If it is not there then add it

 

===============

 

Finally, I saw some lab cases where this was fix with a new binary.  If you are still on DP 6.2, I recommend that you upgrade to 6.21 by installing a patch bundle, and install the subsequent patches.  The patch bundle and patches can be downloaded from

 

http://support.openview.hp.com/selfsolve/patches


Viewing all articles
Browse latest Browse all 10494

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>