Vantage Pro2 Agent crash

[BrianJKoopman]

This I/O error was seen recently at site:

2026-02-26T14-17-41.562332 startup-op: launching init
2026-02-26T14-17-41.567118 start called for init
2026-02-26T14-17-41.581556 init:0 Status is now "starting".
2026-02-26T14-17-41.616813 Initialized Vantage Pro2 module: <socs.agents.vantagepro2.drivers.VantagePro2 object at 0xb4266a60>
2026-02-26T14-17-41.622534 start called for acq
2026-02-26T14-17-41.648539 acq:1 Status is now "starting".
2026-02-26T14-17-43.675864 init:0 Vantage Pro2 module initialized.
2026-02-26T14-17-43.690887 init:0 Status is now "done".
2026-02-26T18-05-46.842676 acq:1 CRASH: [Failure instance: Traceback: <class 'serial.serialutil.SerialException'>: write failed: [Errno 5] Input/output error
/usr/lib/python3.9/threading.py:954:_bootstrap_inner
/usr/lib/python3.9/threading.py:892:run
/home/user/.local/lib/python3.9/site-packages/twisted/_threads/_threadworker.py:47:work
/home/user/.local/lib/python3.9/site-packages/twisted/_threads/_team.py:182:doWork
--- <exception caught here> ---
/home/user/.local/lib/python3.9/site-packages/twisted/python/threadpool.py:244:inContext
/home/user/.local/lib/python3.9/site-packages/twisted/python/threadpool.py:260:<lambda>
/home/user/.local/lib/python3.9/site-packages/twisted/python/context.py:117:callWithContext
/home/user/.local/lib/python3.9/site-packages/twisted/python/context.py:82:callWithContext
/home/user/.local/lib/python3.9/site-packages/socs/agents/vantagepro2/agent.py:138:acq
/home/user/.local/lib/python3.9/site-packages/socs/agents/vantagepro2/drivers.py:362:weather_daq
/home/user/.local/lib/python3.9/site-packages/socs/agents/vantagepro2/drivers.py:94:startup
/usr/lib/python3/dist-packages/serial/serialposix.py:637:write
]
2026-02-26T18-05-46.868032 acq:1 Status is now "done".

socs version: 0.5.2

[BrianJKoopman]

After further investigation, it looks like the USB connection is flaky and the device ends up moving between various /dev/ttyUSBX paths. We do symlink to a consistent path, but aren't using the --port argument in practice. That will help with the path changing, but still the write exception should be caught and handled, and we should reconnect.