Cloudnode log written to /var/log/messages
Paul Timms
8-8-18
Is it possible to prevent the cloudnode log from being written to /var/log/messages on Linux? It makes it very difficult to find useful messages about the server.
Giuseppe L.
8-9-18
Hello Paul,
thank you for reaching out to us with this question.
By default, we don't save the log in the path you indicated.
Apparently, there is a Linux setting on your server which overrides the default settings.

I suggest you check /etc/rsyslog.conf

Best Regards,
Giuseppe
HansaWorld Italy
Paul Timms
8-13-18
Thanks Giuseppe, your information gave me enough of a clue to work out what was happening.


On Linux, I always use systemd to enable the cloudnode to run as a service, following Elar's original instructions:

"
[Unit]
Description=Standard ERP Cloud Node
After=syslog.target
After=network.target

[Service]
Type=simple
User=root

WorkingDirectory=
ExecStart=/hansa-cloudnode
KillMode=process
Restart=always
[Install]
WantedBy=multi-user.target

systemctl daemon-reload
systemctl stop hansa-cloudnode.service
systemctl start hansa-cloudnode.service
"

I discovered that all systemd services write their log messages to /var/log/messages by default, so the cloudnode was writing both to hansa.log and to /var/log/messages. To prevent this, I added:

StandardOutput=null


to the [Service] section, then reloaded the daemon and restarted the service. This should probably be added to the original notes on how to set up the service.
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Back to the list
Latest Posts
David Delač
Hi Piotr, The log entry:
2024-12-14 08:40:43 0.000 CallHal(IsHansaWorldCustomer) appears because the server is running with the verbosity=debug-detailed setting in its parameters.txt file. Thi...
09:43 16 Dec 2024
Brittany McGrath
Hi Vaughn, I can confirm this has been fixed now and is live in Standard ERP 2024-11-20 Version: 85556786. Thank you. ...
10:04 10 Dec 2024