DX NetOps

 View Only
  • 1.  Failed NFA Upgrade to 20.2.5

    Posted Dec 02, 2020 08:55 AM
    Looking for a little help if anyone has run into this...

    Currently running ver 9.3.8 of NFA with no problems.  Attempted upgrade to 20.2.5 (10.0.5) last night with failures.

    Two server implementation - one DSA\Harvester and one console

    DB checks, prerequisite checks all were fine and the Harvester upgrade itself actually ran with no errors at all.  When the upgrade finished, all services were running, but according to documentation a reboot of the server is needed to continue.  This is where the failures occurred.  When the server restarts, the services go into an infinite loop of trying to start but fail constantly.  Because of an anomaly seen with a running McAfee service we thought virus scanning had been left on so we restored the server back to 9.3.8, made sure McAfee was disabled (it was the first time as it turns out), verified NFA was in a green status, and attempted the upgrade again.  Same result: services fine after upgrade...failing after reboot.

    Looking through the wrapper logs, there appear to be a lot of errors related to Java. 
    From dataretention-wrapper:
       ERROR | wrapper | 2020/12/01 21:38:50 | Failed to parse the version of Java. Resolving to the lowest supported version (1.4).
       STATUS | wrapper | 2020/12/01 21:38:50 | Launching a JVM...
       INFO | jvm 1 | 2020/12/01 21:38:50 | Error occurred during initialization of VM
       INFO | jvm 1 | 2020/12/01 21:38:50 | java/lang/NoClassDefFoundError: java/lang/Object
       ERROR | wrapper | 2020/12/01 21:38:50 | JVM exited while loading the application.

    fileserver-wrapper:
       INFO | jvm 2 | 2020/12/01 21:38:55 | Error occurred during initialization of VM
       INFO | jvm 2 | 2020/12/01 21:38:55 | java/lang/NoClassDefFoundError: java/lang/Object
       ERROR | wrapper | 2020/12/01 21:38:55 | JVM exited while loading the application.
       ERROR | wrapper | 2020/12/01 21:39:00 | Failed to parse the version of Java. Resolving to the lowest supported version (1.4).

    harvester-wrapper:
       ERROR | wrapper | 2020/12/01 21:38:48 | Failed to parse the version of Java. Resolving to the lowest supported version (1.4).
       STATUS | wrapper | 2020/12/01 21:38:49 | Launching a JVM...
       INFO | jvm 5 | 2020/12/01 21:38:49 | Error occurred during initialization of VM
       INFO | jvm 5 | 2020/12/01 21:38:49 | java/lang/NoClassDefFoundError: java/lang/Object
       ERROR | wrapper | 2020/12/01 21:38:49 | JVM exited while loading the application.
       FATAL | wrapper | 2020/12/01 21:38:49 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
       FATAL | wrapper | 2020/12/01 21:38:49 | There may be a configuration problem: please check the logs.
       STATUS | wrapper | 2020/12/01 21:38:49 | <-- Wrapper Stopped

    poller-wrapper
       ERROR | wrapper | 2020/12/01 21:38:50 | Failed to parse the version of Java. Resolving to the lowest supported version (1.4).
       STATUS | wrapper | 2020/12/01 21:38:50 | Launching a JVM...
       INFO | jvm 1 | 2020/12/01 21:38:50 | Error occurred during initialization of VM
       INFO | jvm 1 | 2020/12/01 21:38:50 | java/lang/NoClassDefFoundError: java/lang/Object
       ERROR | wrapper | 2020/12/01 21:38:50 | JVM exited while loading the application.

    and so on....

    I did verify the correct Java path was in the server variables.  I did verify that port 8089 was configured as the SNMP port. Couldn't find anything else in any docs related to this issue.

    Anyone have any ideas?  I do have a support ticket open but figured I'd reach out here as well.

    TIA  -  Mike



  • 2.  RE: Failed NFA Upgrade to 20.2.5

    Broadcom Employee
    Posted Dec 02, 2020 11:03 AM
    Mike,

    Could you please open a support ticket under Network Flow Analysis.

    This occurs when Java (OpenJDK) does not get upgraded properly.

    Thanks,

    Justin Signa


  • 3.  RE: Failed NFA Upgrade to 20.2.5
    Best Answer

    Posted Dec 02, 2020 11:45 AM
    As noted, I already had a ticket open and just got off the line with Support.

    It is running now...and ended up being a very easy "Fix".

    Although documentation does not state it, even if you are logged into the server with an admin account, you have to right click the upgrade exe and 'Run as administrator' in order for it to install properly.  Both Harvester and Console updated successfully after making this change when running the executable.

    Minor issue I know but it would be nice to have this specifically stated in the documentation for a Windows server.


  • 4.  RE: Failed NFA Upgrade to 20.2.5

    Broadcom Employee
    Posted Dec 02, 2020 02:41 PM
    Mike,

    Good point. I will have the documentation team add that.

    Thanks,

    Justin Signa