"SPAT terminating from unhandled exception: segmentation fault" repeatedly

[dbrandesky]

Types of Issue

• Anomaly report (something appears to not work correctly)
• Enhancement request (describe the enhancement being requested)
• Other (please ensure the description clarifies why the issue doesn’t fall into either of the above categories)

Descriptive summary

In a docker deployed system, when the SPAT plugin is configured to receive SPAT data from, and communicate via NTCIP with, an Econolite EOS controller the aforementioned error occurs repeatedly and SPAT data is never actually received in the application.

Plugins enabled: SPAT, SPaTLoggerPlugin. The error is specifically logged by the SPAT plugin. This is an otherwise out of the box Docker deployment of V2X-Hub on an Ubuntu 22.04 system. The same issue was observed on an OpenSUSE Tumbleweed system.

V2XHUB version where this issue was discovered

7.3.0

Expected behavior

SPAT doesn't crash :)

Actual behavior

SPAT terminating from unhandled exception: Segmentation fault backtrace: (Hint: Use addr2line -C -e 0x#######) to find line number) SpatPlugin(+0x3e57b) [0x55761926d57b] SpatPlugin(+0x2da68) [0x55761925ca68] /lib/x86_64-linux-gnu/libpthread.so.0(+0x14420) [0x7fb7d328d420] SpatPlugin(+0x2da68) [0x55761925ca68] SpatPlugin(+0x2b687) [0x55761925a687] SpatPlugin(+0x29038) [0x557619258038] SpatPlugin(+0x275c2) [0x5576192565c2] SpatPlugin(+0x22126) [0x557619251126] SpatPlugin(+0x82806) [0x5576192b1806] SpatPlugin(+0x8b4c1) [0x5576192ba4c1] SpatPlugin(+0x8b417) [0x5576192ba417] SpatPlugin(+0x8b244) [0x5576192ba244] SpatPlugin(+0x8b050) [0x5576192ba050] /lib/x86_64-linux-gnu/libboost_thread.so.1.71.0(+0x1143b) [0x7fb7d32ad43b] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8609) [0x7fb7d3281609] /lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7fb7d2e55133] diagnostic info: /home/V2X-Hub/src/tmx/TmxUtils/src/PluginExec.cpp(220): Throw in function HandleSignal Dynamic exception type: tmx::utils::SignalException std::exception::what: Segmentation fault

Steps to reproduce the actual behavior

1. cd configuration/amd64
2. ./initialization.bash
3. ./mysql/add_v2x_user.bash
4. Open 127.0.0.1:19760 in web browser, accept security risk, then navigate to 127.0.0.1 and log in using credentials from step 3
5. Configure SPAT with IP of system running V2X-Hub and target port of SPAT messages from controller, and IP of controller with SNMP port of controller.
6. Note that SPAT status indicator cycles between green and red; looking at the Event Logs shows the exception occurring over and over.

Related work

[rob-baily]

@dbrandesky Sorry that no one ever responded on this. I believe this is the behavior if you don't have the secrets files for the MySQL passwords configured correctly. Would you be able to try the latest 7.3.1 release and follow the steps on https://usdot-carma.atlassian.net/wiki/spaces/V2XH/pages/1886158849/V2X-Hub+Docker+Deployment to attempt to deploy it?