Protection Engine for Cloud Services

 View Only
  • 1.  ScanEngine Java LiveUpdate Error

    Posted Jan 30, 2012 10:22 AM

    Hello,

    We have just bought the Symantec ScanEngine and installed it on a Redhat enterprise Linux 5.5

    The engine works well, but the AV definitions can't be updated.

    We have the line "Java LiveUpdate Error" displayed in the console.

    When looking at the logs, we have the followings lines:

    30 janv. 2012 14:20:48 Loading guard file:  /tmp/1327929647532/csapi$20avenge$20definitions$20for$20x86$2dredhat7.2
    _1.0_symalllanguages_livetri.zip1327929648129/liveupdt.grd
    30 janv. 2012 14:20:48 Unable to calculate free space but JLU will continue.
    30 janv. 2012 14:20:48 Disk space check for 1327864614jtun_ennluapi.lin failed. Requested free space was 786,181 (i
    n MB).
    30 janv. 2012 14:20:48
    30 janv. 2012 14:20:48 The Java LiveUpdate session did not complete successfully.
    30 janv. 2012 14:20:48 Return code = 246

    You can notice this:

    Unable to calculate free space but JLU will continue

    then

    Disk space check for 1327864614jtun_ennluapi.lin failed. Requested free space was 786,181 (in MB).

    We should have enough free space because we have more than 2.5 GB free...

    When manually lauching java LiveUpdate in debug, we have no error:

    java -classpath jlu.jar com.symantec.liveupdate.LiveUpdate -d

    The Java LiveUpdate session has completed successfully.
    Return code = 0

    I have searched the internet, the forums, the support articles, etc but found nothing...

    Does anybody have an idea of why this issue ???

    Thanks for your help !!!



  • 2.  RE: ScanEngine Java LiveUpdate Error

    Posted Jan 30, 2012 10:47 AM

    Error 246 indicates you don't have enough free space on the drive/paration.

     

    _1.0_symalllanguages_livetri.zip1327929648129/liveupdt.grd
    30 janv. 2012 14:20:48 Unable to calculate free space but JLU will continue.
    30 janv. 2012 14:20:48 Disk space check for 1327864614jtun_ennluapi.lin failed. Requested free space was 786,181 (i
    n MB).

    30 janv. 2012 14:20:48
    30 janv. 2012 14:20:48 The Java LiveUpdate session did not complete successfully.
    30 janv. 2012 14:20:48 Return code = 246

     

    If possible free up as much space as possible or at least one gigabyte to the /tmp/ directory/partition and possibly /opt as well.



  • 3.  RE: ScanEngine Java LiveUpdate Error

    Posted Jan 30, 2012 11:03 AM

    Hello,

    Thanks for your reply, but as I said above we have more than 2.5 GB free. This free space is available on "/". I assume than the the "/tmp" folder is used ?

    We should have enough free space because we have more than 2.5 GB free...

    Therefore, I assume this message is the key:

    Unable to calculate free space but JLU will continue.

    Thanks anyway for your reply, I will be pleased if you have another suggestion...



  • 4.  RE: ScanEngine Java LiveUpdate Error

    Posted Jan 30, 2012 01:10 PM

    /tmp and /opt are used and should have at least a gig free. 



  • 5.  RE: ScanEngine Java LiveUpdate Error

    Posted Jan 31, 2012 06:02 AM
    Hello, Thanks for the reply. Finally, I have more that 5GB free. I have more than 1 GB on /dev/shm too. extract from a df: used available capacity mounted on 2530240 5055796 34% / 12145 83722 13% /boot 0 1037712 0% /dev/shm Any other idea or suggestion ? Please !?


  • 6.  RE: ScanEngine Java LiveUpdate Error

    Posted Jan 31, 2012 09:46 AM

    Can you upload a full liveupdt.log

    Is are /opt and /tmp part of the / partition?



  • 7.  RE: ScanEngine Java LiveUpdate Error

    Posted Feb 01, 2012 03:10 AM
      |   view attached

    Hello,

    I attached the file renamed to "liveupdt.txt".

    concerning /opt and /tmp, they are on the / partition.

     

    Thanks again for your help.

    Attachment(s)

    txt
    liveupdt_3.txt   7 KB 1 version


  • 8.  RE: ScanEngine Java LiveUpdate Error

    Posted Feb 01, 2012 04:44 AM
      |   view attached

    Hello again,

    I think I got the issue.

    I manually ran the liveUpdate in debug mode with the parameters indicated in the previous log file.

    It seems to launch a df and bugs when parsing the disk name. So, it seems that the wrong column of the df command is used...

    But why this issue on a RedHat Enterprise 5.5 ? I assume this is working on other systems !?

    I attach the new logs below.

    Best regards

    Attachment(s)

    txt
    liveupdt-debug.txt   14 KB 1 version


  • 9.  RE: ScanEngine Java LiveUpdate Error
    Best Answer

    Posted Feb 01, 2012 09:30 AM

    I recommend opening a support case at this point. This issue may require a code fix.



  • 10.  RE: ScanEngine Java LiveUpdate Error

    Posted Feb 02, 2012 05:46 AM

    Ok, thanks again for your help.