Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
@Thomas Hampel LND 2.9 is not supported to HCL notes V11. Which tool we should use for nsd analysis? or HCL will provide similar tool in future?
HCL support team (which formerly was IBM) always ask customer to collect manual NSD (NSD -monitor) whenever the NSD generated during server crash was uncompleted.
I thinking of, why not the Domino developer enhance the integrated NSD tool to include any additional code being used by NSD -monitor.
@Thomas Hampel I‘ve used LND. It acts as a nicer frontend/analysis tool. Hence, it would be nice to have it more accessible, or even as an installable option in the future.
However, it does not resolve the issues underneath. In my specific problems, and apparently those problems reported by the idea creator, LND does not help.
Would it help to use this tool ? https://www.ibm.com/support/docview.wss?uid=swg24019151
From my side, I can see a specific scenario to enhance:
In these Domino server crashes I've seen, there is a too high percentace of these crashes, where a Domino process just dumped code (e.g. http), the process disappears from the OS's process list, and then Domino's ProcessMonitorTask notices that one of it's child PID's is missing.
In these cases, Domino will issue a Panic, which is the correct behaviour.
However, there is no useful evidence in the NSD file regarding the missing child process (because it's already gone). In these cases, the root cause of the crash cannot be evaluated, or it is very hard.
A set of proper crash dump files should allow a skilled technician (or IBM support) to evaluate the crash root cause in almost any case.
A desirable solution could be to avoid most cases, where a core dump will happen, and instead issue a controlled Panic directly from the problematic Domino process.
Additionally, it would be good if NSD was able to auto-process core files belonging to the current crash incident, including the processed data in the NSD file.