Skip to main content
4-Participant
February 28, 2024
Question

About the log error Thing[xxxx] is not running

  • February 28, 2024
  • 1 reply
  • 3043 views

The platform log shows that Thing[xxxx] is not running. In this case, all services in this thing cannot be executed successfully. If any service log in this thin thin is executed, this error will be reported. Maybe it will recover on its own after a while, or maybe it will have to be done by restarting Thingworx. Can't find the reason? Is it possible that the service takes too long to execute or is called too frequently as an interface, leading to the exhaustion of memory resources, has anyone else encountered similar problems, and further in-depth analysis to reach a conclusion and solution ?

1 reply

Rocko
19-Tanzanite
February 28, 2024

If it's not running, it's because it can't be initialized or started. Check out the Error.log on disk (not ScriptErrorLog)

Could be a misconfiguration in the Config table, missing drivers, or any other exception thrown in the things init phase.

pliu14-ParticipantAuthor
4-Participant
February 28, 2024

The thing works normally, only suddenly not after a while
running, not from the beginning, you or err.log specifically refers to the error log in what location and path

16-Pearl
February 28, 2024

Hi, @pliu1   can you share your application, and error logs here?