|
Повідомлення створено: 24. 09. 2025 [16:44]
|
|
walhi
Sergey Karpesh
Автор теми
![]()
Зареєстрован(а) с: 26.01.2016
Повідомлення: 36
|
Hello. I've encountered a very large syslog on a machine running Ubuntu 24.04. Syslog output was disabled. Message level 0 (debug). I have syslog level 1 (Information) selected and enabled output to archive, stdout, and stderr. This behavior was present in build 3018 and the latest 3045, but only on Ubuntu. I'm not sure if this is a bug, so I apologize in advance if I haven't figured out how the logging works.
|
|
Повідомлення створено: 24. 09. 2025 [17:22]
|
|
roman
Roman Savochenko
Moderator Contributor Developer
Зареєстрован(а) с: 12.12.2007
Повідомлення: 3784
|
"walhi" wrote:
Hello. I've encountered a very large syslog on a machine running Ubuntu 24.04. Syslog output was disabled. Message level 0 (debug). I have syslog level 1 (Information) selected and enabled output to archive, stdout, and stderr. This behavior was present in build 3018 and the latest 3045, but only on Ubuntu. I'm not sure if this is a bug, so I apologize in advance if I haven't figured out how the logging works.
OpenSCADA doesn't write in the syslog at no setting such option — http://oscada.org/wiki/Special:MyLanguage/Documents/Program_manual#Config
And the log size in whole is dependent only from your project, who generates extra messages!!!
Learn, learn and learn better than work, work and work.
|
|
Повідомлення створено: 29. 09. 2025 [13:28]
|
|
walhi
Sergey Karpesh
Автор теми
![]()
Зареєстрован(а) с: 26.01.2016
Повідомлення: 36
|
And the log size in whole is dependent only from your project, who generates extra messages!!!
The problem is that the syslog add-on is disabled and the message level is set to 1, but in fact, messages with a level of 0 are logged. And this only occurs on Ubuntu.
<prm id="MessLev">1</prm> |
|
Повідомлення створено: 29. 09. 2025 [15:52]
|
|
roman
Roman Savochenko
Moderator Contributor Developer
Зареєстрован(а) с: 12.12.2007
Повідомлення: 3784
|
"walhi" wrote:
And the log size in whole is dependent only from your project, who generates extra messages!!!
The problem is that the syslog add-on is disabled and the message level is set to 1, but in fact, messages with a level of 0 are logged. And this only occurs on Ubuntu.
Then that is not syslog in whole but a replacement from systemd which writes stdout or stderr of the service programs.
In any way, OpenSCADA writes messages corresponding to the pointed level, what you can see from the sources — http://oscada.org/svn/trunk/OpenSCADA/src/tmess.cpp
You may have installed and running in the background the service configurations from openscada-server or openscada-plc with different message levels!
Learn, learn and learn better than work, work and work.
|
|
Повідомлення створено: 29. 09. 2025 [16:35]
|
|
walhi
Sergey Karpesh
Автор теми
![]()
Зареєстрован(а) с: 26.01.2016
Повідомлення: 36
|
"roman" wrote:
You may have installed and running in the background the service configurations from openscada-server or openscada-plc with different message levels!
No. One station is running. I'm checking it with tail -f /var/log/syslog, and the messages disappear if I uncheck all the boxes in the configurator "to stderr", "to stdout", and "to syslog". There's no response at the change message level". I found the problem. Level 0 was set in the PLC diagnostics. I was sure that the level set in the workstation settings took precedence over the one specified for the PLC. The only remaining issue was redirecting stdout/stder to syslog, which only occurred on one project and one operating system.
|
