"Error: CAN'T START NETWORK TICKET when restarting AlarmNotifier - DX Spectrum".
Article ID: 443351
Updated On:
Products
Issue/Introduction
When attempting to restart the **AlarmNotifier** process in DX Spectrum using the command `./processd --restart AlarmNotifier`, the process fails to restart. Symptoms include:
- Process IDs (PIDs) and start dates do not update.
- The `processd` log file contains the error: `CAN'T START NETWORK TICKET`.
Environment
Product DX NetOps Spectrum
Component AlarmNotifier
Cause
This error typically occurs when the Spectrum Process Daemon (`processd`) is unable to properly initialize or re-establish the network ticket required to manage the AlarmNotifier process. This can be caused by environmental hangs or issues with the underlying install tickets (.idb files).
Resolution
If the standard restart command fails, use the `launchinstdbapp` utility to manually register and start the process via its install ticket.
### Step 1: Stop the Process
Navigate to the `$SPECROOT/bin/` directory and manually stop the specific notifier process:
bash./cmdC.exe 2 [PARTNAME]
(Replace `[PARTNAME]` with the name defined in your .idb file, e.g., ALARMNOTIFIER).
### Step 2: Manually Launch to Initialize (Optional)
If the process has not been registered correctly, navigate to the Notifier directory and run it once with the `-n` flag to re-establish the SANM application connection:
bash./AlarmNotifier.exe -n [APPNAME]
*Press `Ctrl+C` to end the process once the logs show initialization is complete.*
### Step 3: Restart via launchinstdbapp
Use the `launchinstdbapp` utility to start the process as a managed daemon:
bash./launchinstdbapp.exe [PARTNAME] y [LOGNAME].OUT
To confirm the restart was successful, inspect the corresponding `.OUT` log file for the following messages:
- Successful Stop: `AlarmNotifier: [Date/Time] - Non-critical signal received. Exiting...`
- Successful Start: `Alarm Notification Manager Enabled`
- Note if the log says `connection has been re-established`
Feedback
