Error message in file /var/log/mdsplus/mdsipd/access

[alkhwarizmi]

Affiliation
Eurac Research

Version(s) Affected
Server Version: Stable 7.153.3

Platform(s)
Ubuntu 22.04 LTS

Installation Method(s)
apt-get

Describe the bug
By chance, after an OS upgrade to 22.04, I had a look to a very clean /var/log/mdsplus/mdsipd/access file.

Currently the file content is:

Wed Jan 14 14:37:19 2026 (0) (pid 30731) Connection received from XXXXX@172.22.132.80 [172.22.132.80]
Wed Jan 14 15:23:37 2026 (0) (pid 40531) Connection received from XXXXX@172.22.132.80 [172.22.132.80]
Wed Jan 14 15:26:38 2026 (0) (pid 41324) Connection received from JAVA_USER@172.22.132.80 [172.22.132.80]
Error: /usr/local/mdsplus/lib/libMdsMisc.so: undefined symbol: GetXYSignal

Error: /usr/local/mdsplus/lib/libMdsMisc.so: undefined symbol: GetXYSignal

Error: /usr/local/mdsplus/lib/libMdsMisc.so: undefined symbol: GetXYSignal

The error lines are suspicious and you may be willing to investigate. From the user point of view the jScope operation went well.

To Reproduce
Steps to reproduce the behavior:

1. Remove existing access file
2. Generate an access using the jScope app
3. Open the access file again

Expected behavior
No error lines. Maybe more appropriate in the errors file

Screenshots
Not needed, reported exactly what was on screen.

[mwinkel-dev]

Hi @alkhwarizmi -- Thanks for alerting us to this issue! I will be installing a new version of MDSplus on my development system today, so will run jScope and investigate that error.

[mwinkel-dev]

Hi @alkhwarizmi -- I am unable to reproduce the problem with the current alpha. When I launch jScope, no errors are written to the two log files.

So here are some questions:

• Are the error messages still being generated and written to the "access" log?
• What version of MDSplus is on your client computer (where you run jScope)?
• Is the version of MDSplus on the archive server stable-7-153-3 as per the initial bug report?