The JavaScript sub-system is currently unavailable. Please open TMSH or ssh shell and try restarting restnoded. Also look for errors in /var/log/restnoded/restnoded.log.

[kjimenezlpz]

The JavaScript sub-system is currently unavailable. Please open TMSH or ssh shell and try restarting restnoded. Also look for errors in /var/log/restnoded/restnoded.log.

[dstokesf5]

Can you please provide additional information? The JavaScript sub-system (restnoded) can be a bit fragile, and this is a common symptom of many things that can go wrong with it.

• What version of BIG-IP are you using?
• What version of Telemetry Streaming are you using?
• Steps to reproduce the problem.
• Does this problem happen consistently?
• Any details you are willing to share about your Telemetry Streaming configuration.
• Any errors in the restnoded log (as described in the error message)

Without further information, there is nothing we can do to help.

[kjimenezlpz]

I'am using version 13.1.1.4
The version of Telemetry it's 1.7.0-1
I enable Package Management LX but show the message -->
**The iApp LX sub-system is currently unresponsive.
Less info
The JavaScript sub-system is currently unavailable. Please open TMSH or ssh shell and try restarting restnoded. Also look for errors in /var/log/restnoded/restnoded.log.

The REST sub-system is currently unavailable. Please open TMSH or ssh shell and try restarting restjavad. Also look for errors in /var/log/restjavad.log**

And I can't import my file .rpm of telemetry

On my log /var/log/restjavad.log

[WARNING][4707971][19 Nov 2019 16:06:33 UTC][8100/tm/apm/policy/agent/resource-assign PublicWorker] URI:http://localhost:8100/tm/sys/alert/lcd, Referrer:http://127.4.2.1/lcdui/alert_worker.js, Method:GET, Exception:java.util.concurrent.TimeoutException: remoteSender:127.4.2.2, method:GET
at com.f5.rest.common.RestWorker.logAndFailExpiredOperation(RestWorker.java:3099)
at com.f5.rest.common.RestWorker.checkForExpiredOperations(RestWorker.java:3088)
at com.f5.rest.common.RestServer.checkAndExpirePendingWorkerOperations(RestServer.java:1457)
at com.f5.rest.common.RestServer.access$400(RestServer.java:48)
at com.f5.rest.common.RestServer$4.run(RestServer.java:1430)
at com.f5.rest.common.ScheduleTaskManager$2$1.run(ScheduleTaskManager.java:123)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
at java.lang.Thread.run(Thread.java:748)

[dstokesf5]

If you are unable to install Telemetry Streaming at all, then this is a problem that is outside of the scope of Telemetry Streaming.

Are there any errors in /var/log/restnoded/restnoded.log?

[dstokesf5]

Closing this issue for inactivity. If you are still experiencing an issue with Telemetry Streaming (and not the systems that Telemetry Streaming runs on top of), please reopen this issue or create a new one.