Endpoint Protection

 View Only
  • 1.  Failing LiveUpdate on Linux Server -RHEL5

    Posted Jan 12, 2015 03:29 PM

    We have SEP 12.1.5 for Linux installed on RHEL5 (Tikanga), with Java 1.8 that is unable to receive update definitions from internal LiveUpdate Administrator (LUA). We have confirmed the LUA server has proper content since definition updates are currently being distributed on another RHEL5 server (working well). We have also confirmed the server is pointing to proper LUA. server. The LiveUpdate log shows it trying to connect to LUA server, but at the end of log it says: <IdsJavaSessionFailure> and <IdsJavaSessionReturnCode><-1>.

    When we try to manually run LiveUpdate command, it returns -  Command Failed: Problem with LiveUpdate. Check that java directory is in PATH. Unable to perform update. Any ideas/suggestions? Thank you!

     

      



  • 2.  RE: Failing LiveUpdate on Linux Server -RHEL5

    Posted Jan 12, 2015 08:00 PM

    can you post the complete log file, does it say permission denied at any point?

    check if there are multiple versions of Java installed and set accordingly

    http://www.symantec.com/business/support/index?page=content&id=TECH123038



  • 3.  RE: Failing LiveUpdate on Linux Server -RHEL5

    Posted Jan 12, 2015 08:30 PM

    Any exact error message(s)?



  • 4.  RE: Failing LiveUpdate on Linux Server -RHEL5

    Posted Jan 13, 2015 04:10 PM

    We are not running RHEL 5 in a GUI mode and there are no permission denied messages in the liveupdt.log.

    When reviewing the liveupdt.log the client appears to be making successful connections to our internal live update server, however when the liveupdate finally fails the log has three final entries:  <IdsHttpWaitingMsg>, IdsJavaSessionFailure>, and <IdsJavaSessionReturnCode><-1>.  We have also executed the update_java_home.sh file and the symantec.conf file in /etc reveals the correct path to Java.

    Is there another log that we should be reviewing?  Is there a way to turn on verbose logging?

     

    Thank you!



  • 5.  RE: Failing LiveUpdate on Linux Server -RHEL5

    Posted Jan 13, 2015 04:15 PM

    return code -1 is generic in that it mean JLU didn't run successfully.

    Check /var/symantec/Logs/debug.log



  • 6.  RE: Failing LiveUpdate on Linux Server -RHEL5

    Posted Jan 13, 2015 04:33 PM

    -227554416 ERROR smc.SmcIPCManager Could not contact savtray.  err: -1

    -238044272 ERROR smc.SmcIPManager received shutdown signal in SocketAcceptThread

    -227554416 ERROR SchedulerEx ThreadFunction: catch errors.

     

    The SAVTRAY message is interesting, we are not running x windows/gui for the rhel box...Why would it look for that tray?

     

    Thanks!

     



  • 7.  RE: Failing LiveUpdate on Linux Server -RHEL5

    Posted Jan 20, 2015 10:16 AM

    Our RHEL 5.11 (Tikanga) servers are configured without X functionality per security requirements we are un runlevel 3 CLI only.  Considering the errror found in debug.log "-227554416 ERROR smc.SmcIPCManager Could not contact savtray.  err: -1", is thera a way to disable the call to SAVTRAY?

     

    Thanks!