[syslog-ng] Syslog messages not stored in separate lines

[Evan Rempel]

Is there a line break anywhere in the log file?

If yes

1. is the line break in the middle of a syslog line from this device?
2. is the line break at the maximum message size?
3. is the line break at the end of a log message from a different device 
that is logging to the same s_xxx_xxx source?


What I am wondering is that the source of the log messages is logging 
the exact same stream of data to the TCP port that it would have over 
the UDP port (which would be an error). UDP messages are not terminated 
with a new line, while the TCP messages are. If that were the case then 
syslog-ng would never see multiple messages, and would write a 
continuous stream on a single line until it reached the maximum message 
length, or it logged a correctly terminated message from a different device.

Evan.


On 2023-02-02 05:55, Dragan Zecevic wrote:
>
> Hi Balazs,
>
> this is how the whole config snippet looks like:
>
> source s_xxx_xxx {
>         network(
>                 ip(0.0.0.0)
>                 transport(tcp)
>                 port(xxxx)
> flags(store-raw-message)
>         );
> };
>
>
>
> filter filter_xxx_xxx {
>
>                 host("xxx") or host("xxx") ...;
> };
>
>
> destination folder_xxx_xxx {
>
>                 file(
> "/xxx/.../xxx/${R_YEAR}${R_MONTH}${R_DAY}/${SOURCEIP}_${HOST}_${R_HOUR}.log"
> template("${RAWMSG}\n")
> dir-group(xxx)
> dir-perm(xxx)
>                         group(xxx)
>
>                 );
> };
>
>
> log {
>                 source(s_xxx_xxx); filter(filter_xxx_xxx); 
> destination(folder_xxx_xxx);
> };
>
> Sorry for the xxx but I can't export real parameters in conversation 
> like this. Also, I can't provide some pcap or tcpdump.
>
> I restarted syslog-ng multiple times because I also added some other 
> sources and there were no error messages. And this is the only part of 
> the configuration where either this destination or folder are used.
>
> I hope this info is helpful.
>
> Thanks,
> Dragan
>
> ------------------------------------------------------------------------
> *From:* syslog-ng <syslog-ng-bounces at lists.balabit.hu> on behalf of 
> Balazs Scheidler <bazsi77 at gmail.com>
> *Sent:* Tuesday, January 31, 2023 9:18 PM
> *To:* Syslog-ng users' and developers' mailing list 
> <syslog-ng at lists.balabit.hu>
> *Subject:* Re: [syslog-ng] Syslog messages not stored in separate lines
> If there's an initialization error with a config at reloading, 
> syslog-ng can fall back to the old one. Can this happen? Or two 
> destinations writing the same file?
>
> If the problem persists, can you create minimal example with complete 
> with config and sample message that you send and which reproduces the 
> issue?
>
> Thanks
>
> On Tue, Jan 31, 2023, 20:44 Dragan Zecevic <dragan.zecevic at live.com> 
> wrote:
>
>
>     Hi Balazs,
>     thank you for your reply.
>     Yes, I used config like this for other sources as well and
>     restarted syslog-ng service.
>     I don't get it why it doesn't work in this case. I was thinking it
>     is up to the input.
>
>     ------------------------------------------------------------------------
>     *From:* syslog-ng <syslog-ng-bounces at lists.balabit.hu> on behalf
>     of Balazs Scheidler <bazsi77 at gmail.com>
>     *Sent:* Monday, January 30, 2023 6:48 AM
>     *To:* Syslog-ng users' and developers' mailing list
>     <syslog-ng at lists.balabit.hu>
>     *Subject:* Re: [syslog-ng] Syslog messages not stored in separate
>     lines
>     This would be very strange indeed as the template of your file
>     destination includes a newline character at the end of every
>     message, so it should not depend on the input.
>
>     You sure that this is the destination config that you quote here?
>     Did you reload syslog-ng to use that config?
>
>     On Sun, Jan 29, 2023, 13:55 Dragan Zecevic
>     <dragan.zecevic at live.com> wrote:
>
>
>         Hi,
>         I am collecting logs from a network device. They configured
>         syslog format on their source side to be RFC3164.
>
>         On syslog-ng side I am using source and destination like this:
>
>         source s_xxx {
>                 network(
>                         ip(0.0.0.0)
>                         transport(tcp)
>                         port(xxx)
>         flags(store-raw-message)
>                 );
>         };
>
>
>         destination folder_xxx {
>
>                         file(
>         "/xxx/${R_YEAR}${R_MONTH}${R_DAY}/${SOURCEIP}_${HOST}_${R_HOUR}.log"
>         template("${RAWMSG}\n")
>                         );
>         };
>
>         syslog-ng version 3.34
>         CentOS Linux release 7.9.2009
>
>         The problem is that syslog messages are stored in raw format
>         but not separated in different line. Parity bit of new message
>         starts imidiatelly after previous line -without space or enter.
>
>         I have the same config for some other hosts and there log
>         files are created with separate lines. Vendor says they can't
>         change anything on source side.
>
>         Do you have any idea what is the cause of this?
>
>         Thank you.
>
>         Br,
>         Dragan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20230202/29382adf/attachment-0001.htm>