OTserver Documentation

Troubleshooting

Diagnose common OTserver deployment, scanner authorization, interface, import, and site-scope problems.

Start with the scanner’s doctor, interfaces, and validate commands, then inspect import warnings and the audit log. Keep the original JSON and command line when escalating an issue.

Linux raw EthernetIf the scanner cannot open the interface, check root or CAP_NET_RAW and confirm the selected interface.
Windows PROFINETIf discovery is passive, install Npcap separately and check doctor for backend availability. Select the physical adapter and its actual source MAC. pktmon requires Administrator rights and cannot transmit Identify.
Multiple configurationsEvery array entry needs a unique non-empty name and unique resolved output path. The scanner continues with later entries after an individual failure.
SNMP fallbackExplicit SNMPv1, v2c, and v3 selections do not fall back. Select auto only when the approved policy allows v3, then v2c, then v1 attempts.
Direct uploadIf upload is rejected, verify the server URL, Payload site document ID, API-key scope, and OTSERVER_API_KEY.
Unresolved assetsConfirm that the export contains a normalized MAC address and that the intended site is selected.