syslogd | nodejs syslog server , including syslog message parser

This might be an example of what you're looking for. It uses a Timer event with a FileWatcher event.

I found the problem myself. In my Docker compose file, I specified an order of containers via "depends_on". This order prevented my memory from filling up at once. However, after a reboot/crash the "restart:always" function kicked in and started all 11 containers at once.

Note: As docker-compose I also used a docker container (aarch64 - problems) which could possibly lead to this problem.

This issue was recently fixed with openthread/ot-br-posix#614 and new Docker images have been pushed. Please try again.

The log files states that it cannot bind to the standard slurmd port 6818, because there is something else using this address already.

Do you have another slurmd running on this node? Or something else listening there? Try netstat -tulpen | grep 6818 to see what is using the address.

This is due to faulty RAM. Frequent ECC error correction such as in your case defines a faulty hardware. Fix is to find out the memory that causes this issue and replace it. If it's not a critical system, you might not need to fix it immediately.

In some instances, the RAM which is not working in it's expected frequency can also cause this issue.

See the references for more information. Ref 1, Ref 2, Ref 3

This is happening because the caret ^, in a regex, matches the start of a string without consuming any characters.

And because you do have spaces before missingok and sharedscripts, your insertafter and insertbefore regex are matching nothing.

To fix this, you can allow spaces and spaces only at the beginning of the line with the help of \s that matches any space, tab or newline character and of the star * that matches zero or more consecutive characters.

So the correct regex would be

Assuming that your service is running on port 3000 inside container gogs-repo(because I am not sure after looking at the container logs), you should make the following changes in the existing setup.

First thing first. The two containers - gogs-repo and another container (from where you are trying to access the service) are not connected to each other. Hence the host gogs-repo is not resolved.

To fix this, you need to run both the containers in single network.

You can perform the following steps to achieve the desired result.

• Create a private bridge network.

Have your container log to stdout, but collect the logs elsewhere.

One option is to configure Docker itself to send container logs to syslog:

Just what I saw immediately, there is a typo in the parser attribute "CustonSyslogParser" vs. "CustomSyslogParser". Just to make sure you don't have another problem here :)

Otherwise, there are two components which come into play:

• An event definition which is the result the Syslog message is mapped into an OpenNMS Event
• The Syslog parsing rule which identifies the Syslog message and maps it to the given OpenNMS event definition

You should have a look at the Postfix Syslog implementation which comes with OpenNMS.

For example, in the file $OPENNMS_HOME/etc/syslog/Postfix.syslog.xml you will find a rule which looks at the incoming Syslog messages and will pick every Syslog message which contains "disabling TLS support" and will create a event with the OpenNMS Unique Event Identifier (UEI) uei.opennms.org/vendor/postfix/syslog/postfix/TLSDisabled.

The event with the UEI uei.opennms.org/vendor/postfix/syslog/postfix/TLSDisabled is defined with its severity in $OPENNMS_