IBM QRadar

IBM QRadar

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

dlc.service not getting started after successfull installation

  • 1.  dlc.service not getting started after successfull installation

    Posted Fri August 13, 2021 04:10 PM

    After the successful installation of DLC in centos 7, dlc.service is not getting started.

    Status of the service:

    dlc.service - Disconnected log collector

    Loaded: loaded (/usr/lib/systemd/system/dlc.service; enabled; vendor preset: disabled)

    Active: failed (Result: signal) since Fri 2021-08-13 21:13:47 IST; 20min ago

    Process: 1278 ExecStart=/usr/bin/env ${JAVAHOME}/bin/java $JOPTS_MS $GC_OPTS $RMI_GC_OPTS $CLASSLOADER_UNLOADING $GC_THREADS $MEM_OPTS $DUMPOPTS $REMOTE_DEBUG_OPTS -Dcom.q1labs.frameworks.jmx.port=${JMXPORT} -cp ${SERVICEPATH}/current/bin/*:${SERVICEPATH}/current/lib/*:${PROTOCOLPATH}/* ${SERVICEMAINCLASS} ${SERVICEPATH}/current/ ${SERVICEPATH}/current/eventgnosis ecs-dlc.ecs 220 noconsole (code=killed, signal=ABRT)

    Process: 1163 ExecStartPre=/opt/ibm/si/services/dlc/current/systemd/bin/generate_environment.sh ${SERVICENAME} ${SERVICEPATH} (code=exited, status=0/SUCCESS)

    Main PID: 1278 (code=killed, signal=ABRT)

    Aug 13 21:13:46 localhost.localdomain systemd[1]: Starting Disconnected log collector...

    Aug 13 21:13:47 localhost.localdomain systemd[1]: Started Disconnected log collector.

    Aug 13 21:13:47 localhost.localdomain DLC[1278]: stdSplitFreeListSplitAmount= 1

    Aug 13 21:13:47 localhost.localdomain systemd[1]: dlc.service: main process exited, code=killed, status=6/ABRT

    Aug 13 21:13:47 localhost.localdomain systemd[1]: Unit dlc.service entered failed state.

    Aug 13 21:13:47 localhost.localdomain systemd[1]: dlc.service failed.

    Logs in the Messages:

    Aug 13 11:54:24 localhost systemd: Cannot add dependency job for unit dlc.service, ignoring: Unit not found.

    Aug 13 11:57:52 localhost systemd: Cannot add dependency job for unit dlc.service, ignoring: Unit not found.

    Aug 13 12:10:47 localhost systemd: Cannot add dependency job for unit dlc.service, ignoring: Unit not found.

    Aug 13 12:18:35 localhost yum[4076]: Installed: dlc-service-1.6.0-1.noarch

    Aug 13 12:18:48 localhost systemd: dlc.service: main process exited, code=killed, status=6/ABRT

    Aug 13 12:18:48 localhost systemd: Unit dlc.service entered failed state.

    Aug 13 12:18:48 localhost systemd: dlc.service failed.

    Aug 13 12:31:25 localhost systemd: dlc.service: main process exited, code=killed, status=6/ABRT

    Aug 13 12:31:25 localhost systemd: Unit dlc.service entered failed state.

    Aug 13 12:31:25 localhost systemd: dlc.service failed.

    Aug 13 12:37:50 localhost systemd: dlc.service: main process exited, code=killed, status=6/ABRT

    Aug 13 12:37:50 localhost systemd: Unit dlc.service entered failed state.

    Aug 13 12:37:50 localhost systemd: dlc.service failed.

    Aug 13 14:57:43 localhost systemd: dlc.service: main process exited, code=killed, status=6/ABRT

    Aug 13 14:57:43 localhost systemd: Unit dlc.service entered failed state.

    Aug 13 14:57:43 localhost systemd: dlc.service failed.

    Aug 13 15:26:38 localhost systemd: dlc.service: main process exited, code=killed, status=6/ABRT

    Aug 13 15:26:38 localhost systemd: Unit dlc.service entered failed state.

    Aug 13 15:26:38 localhost systemd: dlc.service failed.

    Aug 13 18:04:13 localhost systemd: dlc.service: main process exited, code=killed, status=6/ABRT

    Aug 13 18:04:13 localhost systemd: Unit dlc.service entered failed state.

    Aug 13 18:04:13 localhost systemd: dlc.service failed.

    Aug 13 18:38:57 localhost systemd: dlc.service: main process exited, code=killed, status=6/ABRT

    Aug 13 18:38:57 localhost systemd: Unit dlc.service entered failed state.

    Aug 13 18:38:57 localhost systemd: dlc.service failed.

    Aug 13 18:39:26 localhost systemd: dlc.service: main process exited, code=killed, status=6/ABRT

    Aug 13 18:39:26 localhost systemd: Unit dlc.service entered failed state.

    Aug 13 18:39:26 localhost systemd: dlc.service failed.

    Aug 13 19:51:13 localhost systemd: dlc.service: main process exited, code=killed, status=6/ABRT

    Aug 13 19:51:13 localhost systemd: Unit dlc.service entered failed state.

    Aug 13 19:51:13 localhost systemd: dlc.service failed.

    Aug 13 21:13:47 localhost systemd: dlc.service: main process exited, code=killed, status=6/ABRT

    Aug 13 21:13:47 localhost systemd: Unit dlc.service entered failed state.

    Aug 13 21:13:47 localhost systemd: dlc.service failed.

    Kindly help me in fixing this issue.

    Best Regards,

    Dinesh.



    #QRadar
    #Support
    #SupportMigration


  • 2.  RE: dlc.service not getting started after successfull installation

    Posted Wed August 25, 2021 03:58 PM

    I'm not sure if this has been solved, but you are hitting a known issue in Java version 8.0-6.35, which causes the stdSplitFreeListSplitAmount error. There is a confirmed issue where ibm-java-x86_64-sdk-8.0-6.35.x86_64 doesn't work due to a JVM configuration problem and the service cannot start.

     

    What to do:

    Option 1. Contact Support to report this issue, if you have not done so already.

    Option 2. You can try to downgrade the Java version on your host where DLC is installed to 8.0-6.30.x86_64. Then try to restart the DLC service: systemctl restart dlc

     

    I would probably talk with support first, to ensure that your case is added to this known issue for DLC. If you do open a case, I would include this forum post as a reference. The support rep can confirm you've got the proper Java version in case things have changed since I responded to this forum post.

     

    Title: DLC error stdSplitFreeListSplitAmount

    Reference: DLC-346



    #QRadar
    #Support
    #SupportMigration