# Nodered syslogging on raspberry pi

**URL:** <https://discourse.nodered.org/t/nodered-syslogging-on-raspberry-pi/64766>\
**Category:** General\
**Created:** [6 July 2022 13:24 UTC](https://discourse.nodered.org/t/nodered-syslogging-on-raspberry-pi/64766 "2022-07-06T13:24:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![zubenubi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zubenubi/32/44576_2.png) [@zubenubi](https://discourse.nodered.org/u/zubenubi)\
**Post date:** [6 July 2022 13:24 UTC](https://discourse.nodered.org/t/nodered-syslogging-on-raspberry-pi/64766/1 "2022-07-06T13:24:49Z")

</div>

Hi All,

I have a flow (see below) that is trying to send a msg to the local syslog running on the same rpi as nodered. I am able to send the same msg to a remote syslog server, but not the local server. I would prefer to have it written tot the local syslog because the rpi is periodically disconnected from internet. Please advise what I can do/change to get these messages into the localhost syslog (/var/log/messages). Thanks In Advance

```auto
[{"id":"02f90e2212754b3f","type":"tab","label":"Flow 1","disabled":false,"info":"","env":[]},{"id":"d29dca5db151ecb2","type":"syslog-node","z":"02f90e2212754b3f","name":"","level":"6","category":"1","process":"Node-RED","pid":"0","hostname_mode":"automatic","hostname":"192.168.111.1","x":330,"y":140,"wires":[["a8a10fdefe9518a8"]]},{"id":"5b3e57fcacb0761d","type":"change","z":"02f90e2212754b3f","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"msg.payload & \" mS to 8.8.8.8\" & \" \" & $flowContext(\"statOffboard\")","tot":"jsonata"}],"action":"","property":"","from":"","to":"","reg":false,"x":160,"y":140,"wires":[["d29dca5db151ecb2"]]},{"id":"a8a10fdefe9518a8","type":"udp out","z":"02f90e2212754b3f","name":"","addr":"127.0.0.1","iface":"","port":"514","ipv":"udp4","outport":"","base64":false,"multicast":"false","x":530,"y":140,"wires":[]}]

```

---

<div class="post-metadata">

**Author:** ![r0ller](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/r0ller/32/14327_2.png) [@r0ller](https://discourse.nodered.org/u/r0ller)\
**Post date:** [7 July 2022 18:45 UTC](https://discourse.nodered.org/t/nodered-syslogging-on-raspberry-pi/64766/2 "2022-07-07T18:45:47Z")

</div>

I'm not sure if I got you right but a simple node.warn() will end up in syslog if that fits the bill. Not sure about node.log() though.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [7 July 2022 20:16 UTC](https://discourse.nodered.org/t/nodered-syslogging-on-raspberry-pi/64766/3 "2022-07-07T20:16:36Z")

</div>

TBH, when logging things from node-RED, I always find it much easier to create it's own log using `node-red-contrib-flogger` - [node-red-contrib-flogger (node) - Node-RED](https://flows.nodered.org/node/node-red-contrib-flogger)  
It enables limiting log size, log rotation, compression and various formats, and log results don't then get hidden amongst other sys log data.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [8 July 2022 07:06 UTC](https://discourse.nodered.org/t/nodered-syslogging-on-raspberry-pi/64766/4 "2022-07-08T07:06:58Z")

</div>

How did you install node-red?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [22 July 2022 07:07 UTC](https://discourse.nodered.org/t/nodered-syslogging-on-raspberry-pi/64766/5 "2022-07-22T07:07:18Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.