log4cplus:ERROR ConnectorThread::run()- Cannot connect to server

PLCnext Technology & PLCnext Controls
1

In the system journal of an AXC F 3152 I get every 35 s four messages like

Nov 20 10:38:43 axcf3152 Arp.System.Application[1103]: log4cplus:ERROR ConnectorThread::run()- Cannot connect to server
Nov 20 10:38:43 axcf3152 Arp.System.Application[1161]: log4cplus:ERROR ConnectorThread::run()- Cannot connect to server
Nov 20 10:38:43 axcf3152 Arp.System.Application[1162]: log4cplus:ERROR ConnectorThread::run()- Cannot connect to server
Nov 20 10:38:43 axcf3152 Arp.System.Application[1160]: log4cplus:ERROR ConnectorThread::run()- Cannot connect to server

How can I stop that?

FontColor_eHMI.JPG
FontColor_eHMI.JPG538×531 26 KB

2

Hi armali, welcome to the forum.
Where exactly did you find the information?
Is there any more information?
Please give me the following info:
-Firmware version of the AXC F control unit
-The firmware version of the AXC F controller stored in the project

3

Hi, Tim - thanks for the welcome.
I can query the system journal e. g. with journalctl -f.
This shows not more information.
-Firmware version of the AXC F control unit now is 2025.6.0 (25.6.0.40).
-The firmware version of the AXC F controller stored in the project is (according to my PLC colleague) 04/2025.6.0.

4

Hi armali,
Thank you for the information.
Is the syslog server active on the AXC F 3152?

image.png
image.png1000×368 57.6 KB

5

Hi, Tim!
Well, the syslog server is active by systemctl status syslog-ng@default:

* syslog-ng@default.service - System Logger Daemon "default" instance
     Loaded: loaded (/usr/lib/systemd/system/syslog-ng@.service; enabled; preset: enabled)
     Active: active (running) since Fri 2025-11-21 12:10:29 UTC; 1 year 11 months ago
       Docs: man:syslog-ng(8)
    Process: 380304 ExecReload=/usr/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
   Main PID: 884 (syslog-ng)
      Tasks: 2 (limit: 2187)
     Memory: 52.3M (peak: 53.5M)
        CPU: 14min 52.013s
     CGroup: /system.slice/system-syslog\x2dng.slice/syslog-ng@default.service
             `-884 /usr/sbin/syslog-ng -F --enable-core --cfgfile /etc/syslog-ng/syslog-ng.conf --control /var/run/syslog-ng/syslog-ng.ctl --persist-file /var/lib/syslog-ng/syslog-ng.persist --pidfile /var/run/syslog-ng.pid
Notice: journal has been rotated since unit was started, output may be incomplete.

Syslog server destination activation is off, as in your image.

6

Hi armali,
You have found out very well that the server is running in the background.
I think that the message is related to the syslog service.
I will ask our experts for advice. Unfortunately this will take some time.

7

Hi, Tim, thanks, no worries - a good thing takes time.

8

Hi armali,
I have received new information.
The behavior has already appeared elsewhere.
It is currently planned to be solved with 2026.0.
But it is not yet clear whether this solution will make it into 2026.0.

9

Hi, Tim, thanks for the information!
It’s good to know that it’s not a misconfiguration done by me; I can live with it for a while.