Table of Contents

Thread problem in x: y

In an error message of this type:

  • "x" is the DataMiner process in which the error occurred.
  • "y" is the thread that encountered a problem.

Alternatively, if there is a problem affecting more than one thread, the following variation on this error message can appear, in which "z" is the number of threads that encountered a problem:

Thread problem in x: y [+ z pending]

The following error messages are possible:

Thread problem in SLDataMiner: ActionPoolThread

An ActionPoolThread is created to take care of the start/stop/pause actions of an element.

Symptom

An element takes a long time or even fails to start, stop, or pause.

Possible cause

  • A long startup action, such as retrieving the database data of the element.
  • Element startup is stuck.

Resolution

  • At the RTE root time, check SLDataMiner.txt and the element log. It should show which step exactly is stuck.

Thread problem in SLDataMiner: AlarmStackThread

The AlarmStackThread processes alarm or information requests originating from different modules, and it forwards them to SLElement, which then creates the actual alarms. These are not alarms generated based on the settings in one of the alarm templates.

Symptom

No more alarms are being generated.

Possible cause

  • SLElement has encountered a problem.
  • An element lock is stuck.

Resolution

Restart DataMiner.

Thread problem in SLDataMiner: DBCleaning

The DBCleaning thread removes data that is no longer needed from the local database, e.g., old trending and alarm data.

Symptom

  • The database size is increasing.
  • Disk I/O performance and free space are decreasing.
  • Performance is decreasing with regard to trending, alarms, and backups.

Possible cause

  • There is a problem with the local database.
  • There is an element-specific lock in DataMiner.
  • One database table is taking more than the allowed amount of time.

Resolution

  • Check the database.
  • Manually intervene to help with the cleanup.
  • Check if the amount of trending is within reasonable bounds.
Note

Restarting DataMiner will not help.

Thread problem in SLDataMiner: DBForwarding

The DBForwarding thread pushes data saved in the system cache offload to the central database.

Possible cause

There is a problem with the central database.

Resolution

Check the database.

Thread problem in SLDataMiner: DBThread

The DBThread thread processes plain SQL queries for the local database (insert, delete, and update only).

Possible cause

  • There is a problem with the local database.
  • Queries take too long to finish.
  • There might be an issue with a protocol.

Resolution

  • Check whether the database has any large tables.
  • If there is an issue with a protocol, upload a new version of that protocol.

Thread problem in SLDataMiner: ElementStackThread

The ElementStackThread is dynamically created for every element when needed, and it is removed when no more sets are pending. It forwards sets directly to the correct SLProtocol.

These sets can originate from DataMiner clients, SLSNMPManager, other elements, scripts (except for scripts with waits), element connections, etc. They can contain trap information, alarm level linking, SLA alarm forwarding, advanced naming changes (DCF), etc.

Possible cause

  • SLProtocol has encountered a problem.
  • SLElement has encountered a problem.
  • An element lock is stuck.

Resolution

  • Restart the element in question.
  • Stop the SLScripting process.

Thread problem in SLDataMiner: ExportThread

When you export and import elements using .dmimport packages, or when you migrate elements between DataMiner Agents, these operations are handled by the ExportThread in SLDataMiner.

Possible cause

Exporting or importing involves many steps, and one of these steps may take longer than expected, or, in the worst case, may be stuck. Typical steps in this process include (but are not limited to) gathering element files, protocol and template files, documents, and Visio drawings, isolating view information, and retrieving database data.

Resolution

To resolve this issue, you will need to pinpoint what is going wrong first. To do so, check the following log files:

  • SLDELT.txt
  • SLDataminer.txt
  • SLNet.txt
  • SLErrors.txt

First determine whether the thread is truly stuck or just taking longer than anticipated. If you find an error or exception related to the process in any of these log files, the thread is likely stuck. If no errors are present, the operation is probably still in progress.

Depending on the situation, it may also be useful to look at C:/Skyline Dataminer/System Cache/DELT, either on the source or destination Agent. This location holds the data used to export or import the package.

If the thread is indeed stuck, and you are unable to resolve the issue, contact support.

Note

Export and import speed depends on several factors such as hardware performance, system load, load on elements and services, network throughput, database performance, and the overall package content. In some cases, the process can take several hours to complete.

Thread problem in SLDataMiner: MobileNotificationThread

The MobileNotificationThread sends text message notifications to the SLGSMGateway process.

Thread problem in SLDataMiner: MobileThread

When a Mobile Gateway address is defined, the MobileThread will create the SLGSMGateway process and keep it up to date.

Thread problem in SLDataMiner: OffloadDBThread

The OffloadDBThread pushes data saved in the system cache offload "local" folder to the local database.

Symptom

  • History data is not up to date.
  • Element data is not saved.
  • Free disk space is decreasing, which could lead to a crash.
  • Disk I/O performance is decreasing.
  • The database is using too many CPU resources.
  • The next startup could be very slow.

Possible cause

  • There is a problem with the local database.

  • SLDatabase.dll is loaded but not registered.

  • There is a configuration issue in db.xml.

  • There are too many files in the offload folder.

  • Actions take too long:

    • A database table is becoming too large.
    • Too many keys are being updated.

Resolution

  • Check the database.

  • Clear the system cache.

    Caution

    Note that information may get lost. Information regarding to alarms, properties, services, or correlation can be copied and pasted, but this is not advisable for trending or element data.

  • Check any new trend templates.

  • Check any new alarm templates.

  • Check any recently installed protocols.

Thread problem in SLDataMiner: ReplicationDBThread

The ReplicationDBThread pushes the local database data to the Failover DMA (both a query queue and a file-based offload).

Resolution

  • Check the database.

  • Restart DataMiner, but only if it is not a connectivity issue.

    • First restart the offline Agent, and check whether that solves the problem.
    • If a query is slow, check on which DMA the issue occurs, and restart that DMA.
Caution

Switching might cause more issues.

Thread problem in SLDataMiner: ServiceThread

The ServiceThread handles all service logic, from service states to triggers.

Possible cause

  • SLElement has encountered a problem.
  • SLDMS has encountered a problem.

Thread problem in SLDataMiner: ServiceReplicationThread

The ServiceReplicationThread connects and subscribes on remote service states via SLManagedScripting.dll/SLNet. This thread is not responsible for processing the service states.

Symptom

Replicated services are not up to date.

Possible cause

  • A thread resets Watchdog at the end.
  • Connecting takes longer than 1 minute.
  • A remote server may be down or there may be an issue with a firewall.

Resolution

  • Check whether a connection can be set up with the remote DMA.
Note

Restarting the DMA will probably not solve the issue.

Improve this page