Erlang OTP-observer not displaying my application - process

I'm currently struggling with erlang's OTP observer.
My application - gen_server, and supervisor - runs fine, but when I'm trying to use an observer to view processes I'm only able to view the "kernel" in the tab "applications" in the observer GUI.
These are the commands leading up to the nodes connecting but nothing more:
------------------------Observer------------------------
/home/erlang# erl -pa ebin/ -sname observer -setcookie tmp -run observer
(Erlang:9911): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(Erlang:9911): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(Erlang:9911): GLib-GIO-CRITICAL **: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Eshell V6.0 (abort with ^G)
(observer#ergo)1>
(Erlang:9911): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(Erlang:9911): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(Erlang:9911): GLib-GIO-CRITICAL **: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(Erlang:9911): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(Erlang:9911): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(Erlang:9911): GLib-GIO-CRITICAL **: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
------------------------Node to view------------------------
/home/erlang# erl -pa ebin/ -sname worker
Eshell V6.0 (abort with ^G)
(worker#ergo)1> nodes().
[]
(worker#ergo)2> net_adm:ping(observer#ergo).
pong
(worker#ergo)3> nodes().
[observer#ergo]
In the observer GUI, "Trace Overview", I've added the node (worker#ergo). However I can only view the kernel in the application-tab, and in Trace overview there are no processes listed.
How can I view the process-tree of my application in the observer GUI?

Does your application follow OTP application behavior? Do you start it with application:start/1?

You do not need to add the worker node in the Trace Overview tab. However, you need to make sure you are observing the worker node by choosing the node from the Nodes menu. The observed node typically appears in the title of the observer window.
The Applications tab lists all running applications with a supervision tree. If your application is not listed, it might not be running or it might not have a supervision tree. You can check it is running with undocumented API application:info(). You can check it has a supervision tree with undocumented API application_controller:get_master(AppName) that returns the pid of the master process of any application with a supervision tree.

Related

Can not extract resource from com.android.aaptcompiler.ParsedResource#6997c081

New in coding here, I was making an app from course and everything seems to be fine until I wanted to run the app :c
`
inner element must either be a resource reference or empty.
Execution failed for task ':app:mergeDebugResources'.
A failure occurred while executing com.android.build.gradle.internal.res.ResourceCompilerRunnable
Resource compilation failed (Failed to compile values resource file /Users/konradmichalski/AndroidStudioProjects/FirstApp/app/build/intermediates/incremental/debug/mergeDebugResources/merged.dir/values/values.xml. Cause: java.lang.IllegalStateException: Can not extract resource from com.android.aaptcompiler.ParsedResource#3041067.). Check logs for more details.
*urce compilation failed (Failed to compile values resource file /Users/konradmichalski/AndroidStudioProjects/FirstApp/app/build/intermediates/incremental/debug/mergeDebugResources/merged.dir/values/values.xml. Cause: java.lang.IllegalStateException: Can not extract resource from com.android.aaptcompiler.ParsedResource#3041067.). Check logs for more details.
at com.android.aaptcompiler.ResourceCompiler.compileResource(ResourceCompiler.kt:129)
at com.android.build.gradle.internal.res.ResourceCompilerRunnable$Companion.compileSingleResource(ResourceCompilerRunnable.kt:34)
at com.android.build.gradle.internal.res.ResourceCompilerRunnable.run(ResourceCompilerRunnable.kt:15)
at com.android.build.gradle.internal.profile.ProfileAwareWorkAction.execute(ProfileAwareWorkAction.kt:74)
at org.gradle.workers.internal.DefaultWorkerServer.execute(DefaultWorkerServer.java:63)
at org.gradle.workers.internal.NoIsolationWorkerFactory$1$1.create(NoIsolationWorkerFactory.java:66)
at org.gradle.workers.internal.NoIsolationWorkerFactory$1$1.create(NoIsolationWorkerFactory.java:62)
at org.gradle.internal.classloader.ClassLoaderUtils.executeInClassloader(ClassLoaderUtils.java:97)
at org.gradle.workers.internal.NoIsolationWorkerFactory$1.lambda$execute$0(NoIsolationWorkerFactory.java:62)
at org.gradle.workers.internal.AbstractWorker$1.call(AbstractWorker.java:44)
at org.gradle.workers.internal.AbstractWorker$1.call(AbstractWorker.java:41)
at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
at org.gradle.workers.internal.AbstractWorker.executeWrappedInBuildOperation(AbstractWorker.java:41)
at org.gradle.workers.internal.NoIsolationWorkerFactory$1.execute(NoIsolationWorkerFactory.java:59)
at org.gradle.workers.internal.DefaultWorkerExecutor.lambda$submitWork$2(DefaultWorkerExecutor.java:205)
at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.runExecution(DefaultConditionalExecutionQueue.java:187)
at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.access$700(DefaultConditionalExecutionQueue.java:120)
at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner$1.run(DefaultConditionalExecutionQueue.java:162)
at org.gradle.internal.Factories$1.create(Factories.java:31)
at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:270)
at org.gradle.internal.work.DefaultWorkerLeaseService.runAsWorkerThread(DefaultWorkerLeaseService.java:119)
at org.gradle.internal.work.DefaultWorkerLeaseService.runAsWorkerThread(DefaultWorkerLeaseService.java:124)
at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.runBatch(DefaultConditionalExecutionQueue.java:157)
at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.run(DefaultConditionalExecutionQueue.java:126)
2 more
Caused by: com.android.aaptcompiler.ResourceCompilationException: Failed to compile values resource file /Users/konradmichalski/AndroidStudioProjects/FirstApp/app/build/intermediates/incremental/debug/mergeDebugResources/merged.dir/values/values.xml
at com.android.aaptcompiler.ResourceCompiler.compileTable(ResourceCompiler.kt:192)
at com.android.aaptcompiler.ResourceCompiler.access$compileTable(ResourceCompiler.kt:1)
at com.android.aaptcompiler.ResourceCompiler$getCompileMethod$1.invoke(ResourceCompiler.kt:138)
at com.android.aaptcompiler.ResourceCompiler$getCompileMethod$1.invoke(ResourceCompiler.kt:138)
at com.android.aaptcompiler.ResourceCompiler.compileResource(ResourceCompiler.kt:123)
32 more
Caused by: java.lang.IllegalStateException: Can not extract resource from com.android.aaptcompiler.ParsedResource#3041067.
at com.android.aaptcompiler.TableExtractor.extractResourceValues(TableExtractor.kt:270)
at com.android.aaptcompiler.TableExtractor.extract(TableExtractor.kt:181)
at com.android.aaptcompiler.ResourceCompiler.compileTable(ResourceCompiler.kt:188)
36 more
`
Someone know how to fix it? :/

Ignite RestartProcessFailureHandler failed to restart the stuck node

Ignite version v2.8.1-1
I have configured RestartProcessFailureHandler for handling the system critical errors like SYSTEM_WORKER_BLOCKED, however, when the error occurs, the restart never happens even after hours, is this expected behavior?
However, do see in the logs that indicating a restart has been requested but it seems never got executed.
As an alternative, I am thinking of enabling the rest API for a liveness check of the service and restarting the service once the check fails if the failure handler is not suitable for handling this case, please advise.
Thanks.
[2022-03-08T02:14:32,561][ERROR][disco-event-worker-#44%ignite-instance%][] Critical system error detected. Will be handled accordingly to configured handler [hnd=RestartProcessFailureHandler [super=AbstractFailureHandler [ignoredFailureTypes=Unmod
ifiableSet []]], failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker [name=sys-stripe-6, igniteInstanceName=ignite-instance, finished=false, heartbeatTs=1646705660633]]]
org.apache.ignite.IgniteException: GridWorker [name=sys-stripe-6, igniteInstanceName=ignite-instance, finished=false, heartbeatTs=1646705660633]
at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$3.apply(IgnitionEx.java:1810) [ignite-core-2.8.1.jar:2.8.1]
at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$3.apply(IgnitionEx.java:1805) [ignite-core-2.8.1.jar:2.8.1]
at org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:234) [ignite-core-2.8.1.jar:2.8.1]
at org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:297) [ignite-core-2.8.1.jar:2.8.1]
at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2796) [ignite-core-2.8.1.jar:2.8.1]
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) [ignite-core-2.8.1.jar:2.8.1]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_312]
...
[2022-03-08T02:14:32,603][ERROR][node-restarter][] Restarting JVM on Ignite failure: [failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class o.a.i.IgniteException: GridWorker [name=sys-stripe-6, igniteInstanceName=ignite-instance, finished=false, heartbeatTs=1646705660633]]]
....
There is no standard way for a JVM to restart itself from Java application and therefore ignite rely on external tools to provide that capability. According to docs for org.apache.ignite.failure.RestartProcessFailureHandler
https://ignite.apache.org/docs/2.11.1/perf-and-troubleshooting/handling-exceptions#failures-handling
standard ignite.sh|bat scripts support restarting when JVM process exits with this code.
If you run ignite as part of your application, you can write your own script to start. And add IGNITE_SUCCESS_FILE=<path to marker file, which will be created by ignite during restart is called> as jvm option at start java process. After this failure handler works, jvm exits with org.apache.ignite.IgniteSystemProperties#IGNITE_RESTART_CODE, then you need to check that IGNITE_SUCCESS_FILE was created, remove it and start jvm again.

How to use qt-gstreamer with qtquick2videosink on Qt5 on Raspberry Pi3

I built qt-gstreamer from source code on GitHub (version 1.2.0). Then I tried to run qmlplayer2 application (built from qt-gstreamer and use qtquick2videosink) on qt5 on Raspberry Pi3 but I got the following error at runtime:
(gst-plugin-scanner:3749): GStreamer-WARNING **: Failed to load plugin
'/usr/lib/gstreamer-0.10/libgstqt5videosink.so':
/usr/lib/gstreamer-0.10/libgstqt5videosink.so: undefined symbol:
_Z33gst_qt_quick2_video_sink_get_typev Failed to create qtquick2videosink. Make sure it is installed correctly
(qmlplayer2:8517): GStreamer-CRITICAL **: gst_bin_add: assertion
'GST_IS_ELEMENT (element)' failed
(qmlplayer2:8517): GStreamer-CRITICAL **:
gst_element_link_pads_filtered: assertion 'GST_IS_ELEMENT (dest)'
failed
Look at source code of qt-gstreamer, i found that the function gst_qt_quick2_video_sink_get_type() is implemented in gstqtquick2videosink.cpp but this file was not compiled due to missing configuration in cmake related to OpenGL.
I config cmake as below :
then rebuild and deploy new file libgstqt5videosink.so to /usr/lib/gstreamer-0.10/libgstqt5videosink.so on target device. After that qmlplayer2 application work fine.

Install fails but enhanced logging does not contain errors

I have a ClickOnce Office Add-In that inconsistently fails to install in a PowerShell script. The script is being run from SCCM. When it fails, the only error in the install log is a -400 return value, which of course means almost nothing. There is other output both before and after that error, and nothing stands out.
I was able to replicate this once while ClickOnce logging was turned on, and the output is below (no timestamps because I had to transcribe this by hand).
Failed install:
PLATFORM VERSION INFO
Windows : 6.2.9200.0 (WinNT)
Common Language Runtime : 4.0.30319.42000
System.Deployment.dll : 4.7.2046.0 built by: NET47REL1
clr.dll : 4.7.3260.0 built by: NET472REL1LAST_C
dfdll.dll : 4.7.2046.0 built by: NET47REL1
dfshim.dll : 10.0.15063.0 (WinBuild.160101.0800)
SOURCES
Deployment url : file://path/to/my.vsto
ERROR SUMMARY
No errors were detected during this operation.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
No phase information is available.
ERROR DETAILS
No errors were detected during this operation.
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
DETAILED EXECUTION FLOW
Activation through IPHM APIs is started.
Method Call : InPlaceHostingManager(file://path/to/my.vsto,False) called.
Method Call : InPlaceHostingManager.GetManifestAsync() called.
Internal state=GettingManifest
Method Call : DeploymentManager.BindAsync() called.
Binding started in a worker thread.
Internal state=DownloadingDeploymentInformation
Method Call : InPlaceHostingManager.Dispose() called.
Internal state=Done
Successful install:
PLATFORM VERSION INFO
Windows : 6.2.9200.0 (WinNT)
Common Language Runtime : 4.0.30319.42000
System.Deployment.dll : 4.7.2046.0 built by: NET47REL1
clr.dll : 4.7.3260.0 built by: NET472REL1LAST_C
dfdll.dll : 4.7.2046.0 built by: NET47REL1
dfshim.dll : 10.0.15063.0 (WinBuild.160101.0800)
SOURCES
Deployment url : file://path/to/my.vsto
Application url : file://path/to/my/Application Files/my_1_0_0_123/my.dll.manifest
IDENTITIES
Deployment Identity : my.vsto, Version=1.0.0.123, Culture=neutral, PublicKeyToken=<an alphnumeric value>, processorArchitecture=msil
Application Identity : my.dll, Version=1.0.0.123, Culture=neutral, PublicKeyToken=<an alphnumeric value>, processorArchitecture=msil, type=win32
APPLICATION SUMMARY
* Online only application
ERROR SUMMARY
No errors were detected during this operation.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
No phase information is available.
ERROR DETAILS
No errors were detected during this operation.
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
DETAILED EXECUTION FLOW
Activation through IPHM APIs is started.
Method Call : InPlaceHostingManager(file://path/to/my.vsto,False) called.
Method Call : InPlaceHostingManager.GetManifestAsync() called.
Internal state=GettingManifest
Method Call : DeploymentManager.BindAsync() called.
Binding started in a worker thread.
Internal state=DownloadingDeploymentInformation
Method Call : InPlaceHostingManager.Dispose() called.
expectedAppId=file://path/to/my.vsto#my.vsto, Version=1.0.0.123, culture=neutral, PublicKeyToken=<an alphnumeric value>, processorArchitecture=msil/my.dll, Version=1.0.0.123, culture=neutral, PublicKeyToken=<an alphnumeric value>, processorArchitecture=msil, type=win32
Application is not found in store.
Internal state=DownloadingApplicationInformation
_cached=False
_isUpdate=False
Binding is successful.
Creating GetManifestCompletedEventArgs.
Application Identity=file://path/to/my.vsto, Version=1.0.0.123, culture=neutral, PublicKeyToken=<an alphnumeric value>, processorArchitecture=msil/my.dll, Version=1.0.0.123, culture=neutral, PublicKeyToken=<an alphnumeric value>, processorArchitecture=msil, type=win32
IsCached=False
Method Call : InPlaceHostingManager.DownloadApplicationAsync() called.
Internal state=DownloadingApplcication
Method Call : DeploymentManager.SynchronizeAsync() called.
Download and install of the application started ina worker thread.
Application is not cached.
Application is successfully committed to the store.
Refreshing ActivationContext from store.
Installation is successful.
Internal state=Done
Method Call : InPlaceHostingManager.Dispose() called.
Internal state=Done
Note that there are no actual errors in the failed install.
When I do see this, it does not re-occur a second time. How do I troubleshoot this further?

Evosuite test generation from command line on linux

I am using Evosuite from the command line in Linux and I get an error.
the path for the project is: /home/ina/workspace/ina
the target class files are located in: /home/ina/workspace/ina/bin/paketa1
I use the command:
java -jar evosuite-0.2.0.jar -projectCP /home/ina/workspace/ina -target /home/ina/workspace/ina/bin/paketa1
Here is what I get:
EvoSuite
Found 2 matching classes in target /home/ina/workspace/ina/bin/paketa1
Analyzing classpath (generating inheritance tree)
/home/ina/workspace/ina
/home/ina/workspace/ina/bin/paketa1
Current class: Shembull2
Going to generate test cases for class: Shembull2
Starting client
Connecting to master process on port 5601
Analyzing classpath:
Inheritance tree loaded from /tmp/ES_inheritancetree2503904095717002256.xml.gz
Error while initializing target class: Target class not found in inheritance tree
[MASTER] 14:01:22.015 [logback-2] ERROR TestSuiteGenerator - Problem for Shembull2. Full stack:
java.lang.ClassNotFoundException: Target class not found in inheritance tree
at org.evosuite.setup.DependencyAnalysis.analyze(DependencyAnalysis.java:84) ~[evosuite-0.2.0.jar:na]
at org.evosuite.TestSuiteGenerator.generateTestSuite(TestSuiteGenerator.java:221) ~[evosuite-0.2.0.jar:na]
at org.evosuite.rmi.service.ClientNodeImpl$1.run(ClientNodeImpl.java:125) [evosuite-0.2.0.jar:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_79]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [na:1.7.0_79]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_79]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_79]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_79]
Computation finished
[MASTER] 14:01:22.162 [main] ERROR SearchStatistics - No statistics has been saved because EvoSuite failed to generate any test case
[MASTER] 14:01:22.263 [main] ERROR TestGeneration - failed to write statistics data
Current class: Shembull1
Going to generate test cases for class: Shembull1
Starting client
Connecting to master process on port 14113
Analyzing classpath:
Inheritance tree loaded from /tmp/ES_inheritancetree2503904095717002256.xml.gz
Error while initializing target class: Target class not found in inheritance tree
[MASTER] 14:01:25.039 [logback-2] ERROR TestSuiteGenerator - Problem for Shembull1. Full stack:
java.lang.ClassNotFoundException: Target class not found in inheritance tree
at org.evosuite.setup.DependencyAnalysis.analyze(DependencyAnalysis.java:84) ~[evosuite-0.2.0.jar:na]
at org.evosuite.TestSuiteGenerator.generateTestSuite(TestSuiteGenerator.java:221) ~[evosuite-0.2.0.jar:na]
at org.evosuite.rmi.service.ClientNodeImpl$1.run(ClientNodeImpl.java:125) [evosuite-0.2.0.jar:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_79]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [na:1.7.0_79]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_79]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_79]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_79]
Computation finished
[MASTER] 14:01:25.155 [main] ERROR SearchStatistics - No statistics has been saved because EvoSuite failed to generate any test case
[MASTER] 14:01:25.256 [main] ERROR TestGeneration - failed to write statistics data
Any help would be very appreciated!
Thank You
At a first look, it seems the classpath is not properly set. If you have a project in /home/ina/workspace/ina, and the .class files are compiled in the folder bin, then the classpath would be /home/ina/workspace/ina/bin
If you a class Foo in package "paketa1", like for example paketa1.Foo, then the classpath is still /home/ina/workspace/ina/bin, and not /home/ina/workspace/ina/bin/paketa1