Siemens Enhanced Driver Refresh Browse fails

Ignition
,
1

Hi, I’m running a perspective project with Ignition v8.3.2 (b2025120210) and an S7-1500 PLC communicating via the Siemens Enhanced Driver. The connection works great and I previously had no issues with it at all, but in the last week the manual device tag browse refresh stopped working for me. I navigate to connections → devices → connections → PLC_Symbolic connection → Refresh Browse and am met with “Error” in the top right corner of the gateway but nothing appears in the logs and I’m not sure what to do about this. The refresh browse button used to work and I am not having any other issues with the existing tags. The new tags in the PLC do not show up in the tag browser as expected per my last post here but this leaves me with no way to access new PLC tags. Any ideas on how to resolve this?

I disabled and re-enabled the Siemens Enhanced driver device connection which refreshed the browse but I would strongly prefer to not do this every time I need to add a new tag to Ignition.

Thank you in advance!

image
image1787×352 26.3 KB

2

The new Siemens driver has been receiving regular updates/fixes, I'd upgrade to 8.3.4 first and see if that fixes it.

2 Likes
3

Good morning,
version 8.3.4, gateway installed in environment in Docker.

When I perform a Browse refresh in the Siemens Enhanced Driver, the gateway restarts.
Is this a known issue?

image
image616×427 12.7 KB

Log attached.

image
image1647×384 45.6 KB

4

Please upload actual log files, not screenshots of logs. In this case the wrapper.log files are probably needed. There may also be a crash dump file in the container...

5

wrapper.log (8.1 MB)

diagnostics_20260319-1722.zip (1.4 MB)

Hi Kevin,

i uploaded wrapper (generated from docker log) and diagnostic bundle file.

Thanks

6

It is a crash in the Siemens native library... might be one we're already tracking.

jvm 1    | 2026/03/19 10:03:46 | I [d.S.SymbolicAddressSpace      ] [10:03:46.305]: Symbols loaded: SymbolContext(rootHandle=139753635761312, plcNodeName=PLC) device-name=C1_QG_CPU
jvm 1    | 2026/03/19 10:03:46 | #
jvm 1    | 2026/03/19 10:03:46 | # A fatal error has been detected by the Java Runtime Environment:
jvm 1    | 2026/03/19 10:03:46 | #
jvm 1    | 2026/03/19 10:03:46 | #  SIGSEGV (0xb) at pc=0x0000000000000000, pid=96, tid=2475
jvm 1    | 2026/03/19 10:03:46 | #
jvm 1    | 2026/03/19 10:03:46 | # JRE version: OpenJDK Runtime Environment Zulu17.62+18-SA (17.0.17+10) (build 17.0.17+10-LTS)
jvm 1    | 2026/03/19 10:03:46 | # Java VM: OpenJDK 64-Bit Server VM Zulu17.62+18-SA (17.0.17+10-LTS, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
jvm 1    | 2026/03/19 10:03:46 | # Problematic frame:
jvm 1    | 2026/03/19 10:03:46 | # C  [libAGLink40_x64.so+0x302cf6]
jvm 1    | 2026/03/19 10:03:46 | #
jvm 1    | 2026/03/19 10:03:46 | # Core dump will be written. Default location: Core dumps may be processed with "/wsl-capture-crash %t %E %p %s" (or dumping to /usr/local/bin/ignition/core.96)
jvm 1    | 2026/03/19 10:03:46 | #
jvm 1    | 2026/03/19 10:03:46 | # An error report file with more information is saved as:
jvm 1    | 2026/03/19 10:03:46 | # /usr/local/bin/ignition/hs_err_pid96.log
jvm 1    | 2026/03/19 10:03:46 | [thread 160 also had an error]
jvm 1    | 2026/03/19 10:03:46 | #
jvm 1    | 2026/03/19 10:03:46 | # If you would like to submit a bug report, please visit:
jvm 1    | 2026/03/19 10:03:46 | #   http://www.azul.com/support/
jvm 1    | 2026/03/19 10:03:46 | # The crash happened outside the Java Virtual Machine in native code.
jvm 1    | 2026/03/19 10:03:46 | # See problematic frame for where to report the bug.
jvm 1    | 2026/03/19 10:03:46 | #
wrapperp | 2026/03/19 10:04:10 | Backend connection closed unexpectedly.  Waiting for the process to complete.
wrapper  | 2026/03/19 10:04:10 | JVM received a signal UNKNOWN (6).

/usr/local/bin/ignition/hs_err_pid96.log

can you get this file?

7

error_logs.zip (187.5 KB)

Here they are, Kevin, I’ve also copied also some earlier logs.

8

This looks like the same crash to me... I think a fix is going to land in 8.3.5.

2 Likes
9

Upgrading to 8.3.4 seems to have fixed this issue, thank you!

10

I have 8.3.4 in docker environment and I still have this issue.

I try also in Windows environment but it’s the same.