Possible Solutions¶

No Connection to Message Broker¶

Check if the BROKER_SERVERS key in Consul is specified correctly.

Analyzing NATS Streams¶

SEAL NATS comes with a CLI which can be used for analyzing NATS problems.

Literature - NATS CLI documentation

For a detailed description, see the NATS CLI documentation on GitHub.

Activate NATS Monitoring¶

To check the NATS status, you can enable the monitoring port in nats.conf.

Open the NATS configuration file in an editor.
- Windows: C:\ProgramData\SEAL Systems\config\nats.conf
- Linux: /opt/seal/etc/nats.conf

Activate the NATS monitoring port:

# HTTP monitoring port
monitor_port: 8222

Restart NATS.

plossys service stop seal-nats
plossys service start seal-nats

If extern access to NATS monitoring is needed, open firewall port 8222.
Open NATS monitoring in a browser.
```
http://localhost:8222
```
Cluster connections can be seen under General.

Clear Buckets¶

In PLOSSYS Output Engine 7.0.0, a misconfiguration of the OMS Submit configuration caused no SAP notifications to be sent. After fixing the configuration, the NATS buckets must be cleared.

Stop seal-co-notifier service.
Switch to the NATS directory.
- Windows: cd "C:\Program Files\SEAL Systems\seal-nats"
- Linux: cd /opt/seal/seal-nats

Clear the buckets in the NATS key-value store used by seal-co-notifier service.

Windows:

./nats.exe kv del co-notifier-job-counters
./nats.exe kv del co-notifier-job-data
./nats.exe kv del co-notifier-device-counters
./nats.exe kv del co-notifier-printer-sap
./nats.exe kv del co-notifier-printer-mappings
./nats.exe kv del co-notifier-reply-groups

Linux:

./nats kv del co-notifier-job-counters
./nats kv del co-notifier-job-data
./nats kv del co-notifier-device-counters
./nats kv del co-notifier-printer-sap
./nats kv del co-notifier-printer-mappings
./nats kv del co-notifier-reply-groups

Literature - buckets in the NATS key-value store

For more information about the buckets in the NATS key-value store used by seal-co-notifier service, refer to SAP notifications.