- syslog-ng - lists.balabit.hu

Re: [syslog-ng] Unbale to mount syslog-ng.conf to /etc/syslog-ng using docker image
by László Várady 27 May '18

27 May '18

Hi, Thanks. It might be possible that you have SELinux enabled on your system. Give it another try using the :Z flag: docker run -it -v /demo/syslog-ng/syslog-ng.conf:/etc/syslog-ng/syslog-ng.conf*:Z* --name syslog-ng -p 514:514 -p 601:601 balabit/syslog-ng:latest Please note that you are using the latest edge version of Docker with the devicemapper storage engine. It has nothing to do with your issue, but I would consider switching to the stable version (with overlay2). https://docs.docker.com/install/linux/docker-ce/centos/ -- László Várady On Sun, May 27, 2018 at 12:56 PM Mujeeb Baig <baig.mujeeb(a)gmail.com> wrote: > Hi, > > Docker info output > > root@hdata3:/home/smb/code/conf# docker info > Containers: 0 > Running: 0 > Paused: 0 > Stopped: 0 > Images: 0 > Server Version: 18.05.0-ce > Storage Driver: devicemapper > Pool Name: docker-8:1-100670142-pool > Pool Blocksize: 65.54kB > Base Device Size: 10.74GB > Backing Filesystem: xfs > Udev Sync Supported: true > Data file: /dev/loop0 > Metadata file: /dev/loop1 > Data loop file: /var/lib/docker/devicemapper/devicemapper/data > Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata > Data Space Used: 11.73MB > Data Space Total: 107.4GB > Data Space Available: 51.36GB > Metadata Space Used: 581.6kB > Metadata Space Total: 2.147GB > Metadata Space Available: 2.147GB > Thin Pool Minimum Free Space: 10.74GB > Deferred Removal Enabled: true > Deferred Deletion Enabled: true > Deferred Deleted Device Count: 0 > Library Version: 1.02.146-RHEL7 (2018-01-22) > Logging Driver: json-file > Cgroup Driver: cgroupfs > Plugins: > Volume: local > Network: bridge host macvlan null overlay > Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk > syslog > Swarm: inactive > Runtimes: runc > Default Runtime: runc > Init Binary: docker-init > containerd version: 773c489c9c1b21a6d78b5c538cd395416ec50f88 > runc version: 4fc53a81fb7c994640722ac585fa9ca548971871 > init version: 949e6fa > Security Options: > seccomp > Profile: default > Kernel Version: 3.10.0-693.21.1.el7.x86_64 > Operating System: CentOS Linux 7 (Core) > OSType: linux > Architecture: x86_64 > CPUs: 2 > Total Memory: 7.147GiB > Name: api-es-syslog-ng-2 > ID: HOBZ:AVPN:MRVO:JAMW:YZFU:SF5M:LTFF:7H7Y:BKBA:MNV4:OMY3:4IJM > Docker Root Dir: /var/lib/docker > Debug Mode (client): false > Debug Mode (server): false > Registry: https://index.docker.io/v1/ > Labels: > provider=google > Experimental: false > Insecure Registries: > 127.0.0.0/8 > Live Restore Enabled: false > > WARNING: devicemapper: usage of loopback devices is strongly discouraged > for production use. > Use `--storage-opt dm.thinpooldev` to specify a custom block > storage device. > > > On 25 May 2018 at 18:21, László Várady <laszlo.varady(a)balabit.com> wrote: > >> Hi, >> >> Thanks. >> >> Could you share what version of Docker you are using? >> The output of "docker version" and "docker info" might be interesting. >> >> -- >> László Várady >> >> On Fri, May 25, 2018 at 6:41 PM Mujeeb Baig <baig.mujeeb(a)gmail.com> >> wrote: >> >>> Hi Laci >>> >>> Here is the output, this time I created another folder /demo/syslog-ng >>> and copied the syslog-ng.conf file there, but same issue. I had also >>> attached the output of >>> docker volume inspect syslog-ng (see attcahment) >>> By the way thanks for your help so far. >>> >>> root@hdata3:/home/smb/code/conf# docker rmi balabit/syslog-ng:latest >>> Untagged: balabit/syslog-ng:latest >>> Untagged: balabit/syslog-ng@sha256 >>> :55ed29d3f68e6ce5c0494580af0b49bdfbbd83232902d9db0596486dbc2f0d3f >>> Deleted: >>> sha256:aea40146388e85ca11d2b8b4ee7877d2939a71bed41b727431d48b21084967e1 >>> Deleted: >>> sha256:b97aefa7a738770d348b4c7b5ba8d6cfcaada9453e41603db7b57b01a6bf6773 >>> Deleted: >>> sha256:11aa7498ed3edbf74eea2ee5de418fb8789055e278e750d1db5e4fe9057cada4 >>> Deleted: >>> sha256:a15ea7dac472320a77dfffe1066680e7dfd46eea735376a5b8a2040f4d0ca57e >>> Deleted: >>> sha256:f2f7b467bea911acac35d8a24c3b14cf163bb00370209f5214e5950813d45686 >>> Deleted: >>> sha256:42a1952fea491565f3b8fb19d5869576c8d12a9192f867c4b72234349fa9059a >>> Deleted: >>> sha256:e30891f348eea2928d4027527455904b5933426cbbef4be4b9a908c97a09ba68 >>> Deleted: >>> sha256:ffc4c11463ee21b7532b63abd6079393c619a5d0f4b00397a4b9d1cf9efc4d9b >>> root@hdata3:/home/smb/code/conf# >>> root@hdata3:/home/smb/code/conf# docker pull balabit/syslog-ng >>> Using default tag: latest >>> latest: Pulling from balabit/syslog-ng >>> 4176fe04cefe: Pull complete >>> af68cba418f8: Pull complete >>> 9b2b4fba2935: Pull complete >>> 6297af76ec77: Pull complete >>> 7bf2bd8c0da2: Pull complete >>> 85f1f826e469: Pull complete >>> 24a506d1872d: Pull complete >>> Digest: >>> sha256:55ed29d3f68e6ce5c0494580af0b49bdfbbd83232902d9db0596486dbc2f0d3f >>> Status: Downloaded newer image for balabit/syslog-ng:latest >>> root@hdata3:/home/smb/code/conf# >>> root@hdata3:/home/smb/code/conf# >>> root@hdata3:/home/smb/code/conf# docker run -it -v >>> /demo/syslog-ng/syslog-ng.conf:/etc/syslog-ng/syslog-ng.conf --name >>> syslog-ng -p 514:514 -p 601:601 balabit/syslog-ng:latest >>> docker: Error response from daemon: OCI runtime create failed: >>> container_linux.go:348: starting container process caused >>> "process_linux.go:402: container init caused \"rootfs_linux.go:58: mounting >>> \\\"/demo/syslog-ng/syslog-ng.conf\\\" to rootfs >>> \\\"/var/lib/docker/devicemapper/mnt/4751fd8ef1ddb782156a57749429486610b6c3d532a77c6ebf0727ca72ea451a/rootfs\\\" >>> at >>> \\\"/var/lib/docker/devicemapper/mnt/4751fd8ef1ddb782156a57749429486610b6c3d532a77c6ebf0727ca72ea451a/rootfs/etc/syslog-ng/syslog-ng.conf\\\" >>> caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a >>> directory onto a file (or vice-versa)? Check if the specified host path >>> exists and is the expected type. >>> root@hdata3:/home/smb/code/conf# >>> root@hdata3:/home/smb/code/conf# docker volume ls >>> DRIVER VOLUME NAME >>> root@hdata3:/home/smb/code/conf# >>> >>> >>> On 25 May 2018 at 17:01, László Várady <laszlo.varady(a)balabit.com> >>> wrote: >>> >>>> Hi Mujeeb, >>>> >>>> Something weird happened when you executed >>>> >>>> docker run -it -v "$PWD"/syslog-ng.conf:/etc/syslog-ng/syslog-ng.conf >>>> --name syslog-ng -p 514:514 -p 601:601 balabit/syslog-ng:latest >>>> >>>> for the first time, so I would like to ask you to start from a clean >>>> environment. >>>> >>>> - You've made sure that /home/smb/code/conf/syslog-ng.conf exists on >>>> your host and it is a file. >>>> >>>> - In the original balabit/syslog-ng image, >>>> /etc/syslog-ng/syslog-ng.conf is also a file, so the mount should work. >>>> >>>> Please run the following commands: >>>> >>>> 1. docker rm syslog-ng >>>> >>>> 2. docker rmi balabit/syslog-ng >>>> >>>> 3. docker pull balabit/syslog-ng >>>> >>>> And finally, what you actually wanted to run: >>>> >>>> 4. docker run -it -v /home/smb/code/conf/syslog-ng.conf:/etc/syslog-ng/syslog-ng.conf >>>> --name syslog-ng -p 514:514 -p 601:601 balabit/syslog-ng:latest >>>> >>>> If you still experience problems after this, please send us the output >>>> of "docker volume ls". >>>> >>>> One more question: >>>> Is it possible that "/home/smb/code/conf/" is a mounted network >>>> filesystem (NFS, SMB)? >>>> >>>> -- >>>> László Várady >>>> >>>> On Fri, May 25, 2018 at 5:33 PM Mujeeb Baig <baig.mujeeb(a)gmail.com> >>>> wrote: >>>> >>>>> Hi Laci, >>>>> >>>>> It runs fine >>>>> root@hdata3:/home/smb/code/conf# file >>>>> /home/smb/code/conf/syslog-ng.conf >>>>> /home/smb/code/conf/syslog-ng.conf: ASCII text >>>>> >>>>> Regards >>>>> Mujeeb >>>>> >>>>> On 25 May 2018 at 16:20, Szemere, László <laszlo.szemere(a)balabit.com> >>>>> wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> Thank you for the output. Can you run the >>>>>> >>>>>> *file /home/smb/code/conf/syslog-ng.conf* >>>>>> >>>>>> command on your HOST machine? >>>>>> >>>>>> >>>>>> Br, >>>>>> Laci >>>>>> >>>>>> >>>>>> On Fri, May 25, 2018 at 5:04 PM, Mujeeb Baig <baig.mujeeb(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>>> It is locating the source correctly, this is what I see under >>>>>>> 'Mounts' section of inspect >>>>>>> >>>>>>> "Mounts": [ >>>>>>> { >>>>>>> "Type": "bind", >>>>>>> "Source": "/home/smb/code/conf/syslog-ng.conf", >>>>>>> "Destination": "/1234", >>>>>>> "Mode": "", >>>>>>> "RW": true, >>>>>>> "Propagation": "rprivate" >>>>>>> } >>>>>>> ], >>>>>>> >>>>>>> >>>>>>> On 25 May 2018 at 15:57, Szemere, László <laszlo.szemere(a)balabit.com >>>>>>> > wrote: >>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> From the Docker documentation: >>>>>>>> https://docs.docker.com/v17.09/engine/admin/volumes/bind-mounts/#difference… >>>>>>>> >>>>>>>> If you use -v or --volume to bind-mount a file or directory that >>>>>>>>> does not yet exist on the Docker host, -v will create the >>>>>>>>> endpoint for you. >>>>>>>>> *It is always created as a directory.*If you use --mount to >>>>>>>>> bind-mount a file or directory that does not yet exist on the Docker host, >>>>>>>>> Docker does *not* automatically create it for you, but generates >>>>>>>>> an error. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> It looks like docker daemon still can not find your file >>>>>>>> *"$PWD"/syslog-ng.conf* and creates a directory instead. >>>>>>>> Instead of heavy debugging, I suggest to run *docker inspect >>>>>>>> syslog-ng* to see what path was actually mounted by the docker >>>>>>>> daemon. You should see something like this in the output: >>>>>>>> >>>>>>>> "Mounts": [ >>>>>>>>> { >>>>>>>>> "Type": "bind", >>>>>>>>> "Source": "XXX/syslog-ng.conf", >>>>>>>>> "Destination": "/1234", >>>>>>>>> "Mode": "", >>>>>>>>> "RW": true, >>>>>>>>> "Propagation": "rprivate" >>>>>>>>> } >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Once we have the actual mounted path, it will be easier to figure >>>>>>>> out why the docker daemon can not find your original config file. >>>>>>>> >>>>>>>> Br, >>>>>>>> Laci >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, May 25, 2018 at 4:19 PM, Mujeeb Baig <baig.mujeeb(a)gmail.com >>>>>>>> > wrote: >>>>>>>> >>>>>>>>> Hi Andrew, >>>>>>>>> >>>>>>>>> Thanks for your response. Yes the path is correct >>>>>>>>> >>>>>>>>> When I execute with host location as /1234 it creates the >>>>>>>>> container, but nothing inside /1234 folder >>>>>>>>> >>>>>>>>> root@hdata3:/home/smb/code/conf# docker run -it -v >>>>>>>>> "$PWD"/syslog-ng.conf:/1234 --name syslog-ng -p 514:514 -p 601:601 >>>>>>>>> balabit/syslog-ng:latest >>>>>>>>> syslog-ng: Error setting capabilities, capability management >>>>>>>>> disabled; error='Operation not permitted' >>>>>>>>> [2018-05-25T14:12:15.695588] WARNING: Configuration file format is >>>>>>>>> too old, syslog-ng is running in compatibility mode. Please update it to >>>>>>>>> use the syslog-ng 3.14 format at your time of convenience. To upgrade the >>>>>>>>> configuration, please review the warnings about incompatible changes >>>>>>>>> printed by syslog-ng, and once completed change the @version header at the >>>>>>>>> top of the configuration file.; >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> I can see inside the container that /etc/syslog-ng/ this folder >>>>>>>>> is not updated >>>>>>>>> >>>>>>>>> root@hdata3:/home/smb# docker exec -ti syslog-ng /bin/bash >>>>>>>>> root@d634d32aee4c:/# >>>>>>>>> root@d634d32aee4c:/# ls -l /1234/ >>>>>>>>> total 0 >>>>>>>>> root@d634d32aee4c:/# >>>>>>>>> root@d634d32aee4c:/# ls -l /sy/etcslog-ng/ >>>>>>>>> conf.d/ patterndb.d/ scl.conf syslog-ng.conf >>>>>>>>> root@d634d32aee4c:/# ls -lrt /etc/syslog-ng/ >>>>>>>>> total 12 >>>>>>>>> -rw-r--r--. 1 root root 5910 Feb 23 13:17 syslog-ng.conf >>>>>>>>> drwxr-xr-x. 2 root root 6 Mar 2 12:58 conf.d >>>>>>>>> drwxr-xr-x. 2 root root 6 Mar 2 12:58 patterndb.d >>>>>>>>> -rw-r--r--. 1 root root 1336 Mar 2 12:58 scl.conf >>>>>>>>> root@d634d32aee4c:/# >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On 25 May 2018 at 13:31, Mitzki, András <andras.mitzki(a)balabit.com >>>>>>>>> > wrote: >>>>>>>>> >>>>>>>>>> Hi Mujeeb, >>>>>>>>>> >>>>>>>>>> Maybe the problem is with the config file path: >>>>>>>>>> "/home/smb/code/conf/syslog-ng.conf" >>>>>>>>>> Could you check that path is correct? >>>>>>>>>> >>>>>>>>>> Regards >>>>>>>>>> Andrew >>>>>>>>>> >>>>>>>>>> On Fri, May 25, 2018 at 1:13 PM, Mujeeb Baig < >>>>>>>>>> baig.mujeeb(a)gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi >>>>>>>>>>> >>>>>>>>>>> This is my first trial of syslog-ng. I've tried to start >>>>>>>>>>> syslog-ng just like described on the official bolg page >>>>>>>>>>> https://syslog-ng.com/blog/central-log-server-docker/ >>>>>>>>>>> https://syslog-ng.com/blog/collecting-docker-infrastructure-logs-using-sysl… >>>>>>>>>>> >>>>>>>>>>> I am starting docker container as: >>>>>>>>>>> >>>>>>>>>>> docker run -it -v >>>>>>>>>>> "$PWD"/syslog-ng.conf:/etc/syslog-ng/syslog-ng.conf --name syslog-ng -p >>>>>>>>>>> 514:514 -p 601:601 balabit/syslog-ng:latest >>>>>>>>>>> >>>>>>>>>>> But unfortunately it is failing to mount my custom (local) >>>>>>>>>>> configuration file from source to host, complaining about mounting a >>>>>>>>>>> directory onto file >>>>>>>>>>> >>>>>>>>>>> Error: >>>>>>>>>>> >>>>>>>>>>> docker: Error response from daemon: OCI runtime create failed: >>>>>>>>>>> container_linux.go:348: starting container process caused >>>>>>>>>>> "process_linux.go:402: container init caused \"rootfs_linux.go:58: mounting >>>>>>>>>>> \\"/home/smb/code/conf/syslog-ng.conf\\" to rootfs >>>>>>>>>>> \\"/var/lib/docker/devicemapper/mnt/52d32f854a030b396b03e7596ab5d71eb1a18f34a09d5e4997c437568749b259/rootfs\\" >>>>>>>>>>> at >>>>>>>>>>> \\"/var/lib/docker/devicemapper/mnt/52d32f854a030b396b03e7596ab5d71eb1a18f34a09d5e4997c437568749b259/rootfs/etc/syslog-ng/syslog-ng.conf\\" >>>>>>>>>>> caused \\"not a directory\\"\"": unknown: Are you trying to mount a >>>>>>>>>>> directory onto a file (or vice-versa)? Check if the specified host path >>>>>>>>>>> exists and is the expected type. >>>>>>>>>>> >>>>>>>>>>> Am I missing something? >>>>>>>>>>> >>>>>>>>>>> Please let me know >>>>>>>>>>> >>>>>>>>>>> Many Thanks >>>>>>>>>>> >>>>>>>>>>> Mujeeb >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> ______________________________________________________________________________ >>>>>>>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>>>>>>>>>> Documentation: >>>>>>>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng >>>>>>>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ______________________________________________________________________________ >>>>>>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>>>>>>>>> Documentation: >>>>>>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng >>>>>>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ______________________________________________________________________________ >>>>>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>>>>>>>> Documentation: >>>>>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng >>>>>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ______________________________________________________________________________ >>>>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>>>>>>> Documentation: >>>>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng >>>>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> ______________________________________________________________________________ >>>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>>>>>> Documentation: >>>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng >>>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> ______________________________________________________________________________ >>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>>>>> Documentation: >>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng >>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>>>>> >>>>>> >>>>>> >>>>> >>>>> ______________________________________________________________________________ >>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>>>> Documentation: >>>>> http://www.balabit.com/support/documentation/?product=syslog-ng >>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>>>> >>>>> >>> >

1 0

Re: [syslog-ng] Unbale to mount syslog-ng.conf to /etc/syslog-ng using docker image
by László Várady 25 May '18

25 May '18

Hi, Thanks. Could you share what version of Docker you are using? The output of "docker version" and "docker info" might be interesting. -- László Várady On Fri, May 25, 2018 at 6:41 PM Mujeeb Baig <baig.mujeeb(a)gmail.com> wrote: > Hi Laci > > Here is the output, this time I created another folder /demo/syslog-ng and > copied the syslog-ng.conf file there, but same issue. I had also attached > the output of > docker volume inspect syslog-ng (see attcahment) > By the way thanks for your help so far. > > root@hdata3:/home/smb/code/conf# docker rmi balabit/syslog-ng:latest > Untagged: balabit/syslog-ng:latest > Untagged: balabit/syslog-ng@sha256 > :55ed29d3f68e6ce5c0494580af0b49bdfbbd83232902d9db0596486dbc2f0d3f > Deleted: > sha256:aea40146388e85ca11d2b8b4ee7877d2939a71bed41b727431d48b21084967e1 > Deleted: > sha256:b97aefa7a738770d348b4c7b5ba8d6cfcaada9453e41603db7b57b01a6bf6773 > Deleted: > sha256:11aa7498ed3edbf74eea2ee5de418fb8789055e278e750d1db5e4fe9057cada4 > Deleted: > sha256:a15ea7dac472320a77dfffe1066680e7dfd46eea735376a5b8a2040f4d0ca57e > Deleted: > sha256:f2f7b467bea911acac35d8a24c3b14cf163bb00370209f5214e5950813d45686 > Deleted: > sha256:42a1952fea491565f3b8fb19d5869576c8d12a9192f867c4b72234349fa9059a > Deleted: > sha256:e30891f348eea2928d4027527455904b5933426cbbef4be4b9a908c97a09ba68 > Deleted: > sha256:ffc4c11463ee21b7532b63abd6079393c619a5d0f4b00397a4b9d1cf9efc4d9b > root@hdata3:/home/smb/code/conf# > root@hdata3:/home/smb/code/conf# docker pull balabit/syslog-ng > Using default tag: latest > latest: Pulling from balabit/syslog-ng > 4176fe04cefe: Pull complete > af68cba418f8: Pull complete > 9b2b4fba2935: Pull complete > 6297af76ec77: Pull complete > 7bf2bd8c0da2: Pull complete > 85f1f826e469: Pull complete > 24a506d1872d: Pull complete > Digest: > sha256:55ed29d3f68e6ce5c0494580af0b49bdfbbd83232902d9db0596486dbc2f0d3f > Status: Downloaded newer image for balabit/syslog-ng:latest > root@hdata3:/home/smb/code/conf# > root@hdata3:/home/smb/code/conf# > root@hdata3:/home/smb/code/conf# docker run -it -v > /demo/syslog-ng/syslog-ng.conf:/etc/syslog-ng/syslog-ng.conf --name > syslog-ng -p 514:514 -p 601:601 balabit/syslog-ng:latest > docker: Error response from daemon: OCI runtime create failed: > container_linux.go:348: starting container process caused > "process_linux.go:402: container init caused \"rootfs_linux.go:58: mounting > \\\"/demo/syslog-ng/syslog-ng.conf\\\" to rootfs > \\\"/var/lib/docker/devicemapper/mnt/4751fd8ef1ddb782156a57749429486610b6c3d532a77c6ebf0727ca72ea451a/rootfs\\\" > at > \\\"/var/lib/docker/devicemapper/mnt/4751fd8ef1ddb782156a57749429486610b6c3d532a77c6ebf0727ca72ea451a/rootfs/etc/syslog-ng/syslog-ng.conf\\\" > caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a > directory onto a file (or vice-versa)? Check if the specified host path > exists and is the expected type. > root@hdata3:/home/smb/code/conf# > root@hdata3:/home/smb/code/conf# docker volume ls > DRIVER VOLUME NAME > root@hdata3:/home/smb/code/conf# > > > On 25 May 2018 at 17:01, László Várady <laszlo.varady(a)balabit.com> wrote: > >> Hi Mujeeb, >> >> Something weird happened when you executed >> >> docker run -it -v "$PWD"/syslog-ng.conf:/etc/syslog-ng/syslog-ng.conf >> --name syslog-ng -p 514:514 -p 601:601 balabit/syslog-ng:latest >> >> for the first time, so I would like to ask you to start from a clean >> environment. >> >> - You've made sure that /home/smb/code/conf/syslog-ng.conf exists on your >> host and it is a file. >> >> - In the original balabit/syslog-ng image, /etc/syslog-ng/syslog-ng.conf >> is also a file, so the mount should work. >> >> Please run the following commands: >> >> 1. docker rm syslog-ng >> >> 2. docker rmi balabit/syslog-ng >> >> 3. docker pull balabit/syslog-ng >> >> And finally, what you actually wanted to run: >> >> 4. docker run -it -v /home/smb/code/conf/syslog-ng.conf:/etc/syslog-ng/syslog-ng.conf >> --name syslog-ng -p 514:514 -p 601:601 balabit/syslog-ng:latest >> >> If you still experience problems after this, please send us the output of >> "docker volume ls". >> >> One more question: >> Is it possible that "/home/smb/code/conf/" is a mounted network >> filesystem (NFS, SMB)? >> >> -- >> László Várady >> >> On Fri, May 25, 2018 at 5:33 PM Mujeeb Baig <baig.mujeeb(a)gmail.com> >> wrote: >> >>> Hi Laci, >>> >>> It runs fine >>> root@hdata3:/home/smb/code/conf# file /home/smb/code/conf/syslog-ng.conf >>> /home/smb/code/conf/syslog-ng.conf: ASCII text >>> >>> Regards >>> Mujeeb >>> >>> On 25 May 2018 at 16:20, Szemere, László <laszlo.szemere(a)balabit.com> >>> wrote: >>> >>>> Hello, >>>> >>>> Thank you for the output. Can you run the >>>> >>>> *file /home/smb/code/conf/syslog-ng.conf* >>>> >>>> command on your HOST machine? >>>> >>>> >>>> Br, >>>> Laci >>>> >>>> >>>> On Fri, May 25, 2018 at 5:04 PM, Mujeeb Baig <baig.mujeeb(a)gmail.com> >>>> wrote: >>>> >>>>> It is locating the source correctly, this is what I see under 'Mounts' >>>>> section of inspect >>>>> >>>>> "Mounts": [ >>>>> { >>>>> "Type": "bind", >>>>> "Source": "/home/smb/code/conf/syslog-ng.conf", >>>>> "Destination": "/1234", >>>>> "Mode": "", >>>>> "RW": true, >>>>> "Propagation": "rprivate" >>>>> } >>>>> ], >>>>> >>>>> >>>>> On 25 May 2018 at 15:57, Szemere, László <laszlo.szemere(a)balabit.com> >>>>> wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> From the Docker documentation: >>>>>> https://docs.docker.com/v17.09/engine/admin/volumes/bind-mounts/#difference… >>>>>> >>>>>> If you use -v or --volume to bind-mount a file or directory that >>>>>>> does not yet exist on the Docker host, -v will create the endpoint >>>>>>> for you. >>>>>>> *It is always created as a directory.*If you use --mount to >>>>>>> bind-mount a file or directory that does not yet exist on the Docker host, >>>>>>> Docker does *not* automatically create it for you, but generates an >>>>>>> error. >>>>>> >>>>>> >>>>>> >>>>>> It looks like docker daemon still can not find your file >>>>>> *"$PWD"/syslog-ng.conf* and creates a directory instead. >>>>>> Instead of heavy debugging, I suggest to run *docker inspect >>>>>> syslog-ng* to see what path was actually mounted by the docker >>>>>> daemon. You should see something like this in the output: >>>>>> >>>>>> "Mounts": [ >>>>>>> { >>>>>>> "Type": "bind", >>>>>>> "Source": "XXX/syslog-ng.conf", >>>>>>> "Destination": "/1234", >>>>>>> "Mode": "", >>>>>>> "RW": true, >>>>>>> "Propagation": "rprivate" >>>>>>> } >>>>>> >>>>>> >>>>>> >>>>>> Once we have the actual mounted path, it will be easier to figure >>>>>> out why the docker daemon can not find your original config file. >>>>>> >>>>>> Br, >>>>>> Laci >>>>>> >>>>>> >>>>>> >>>>>> On Fri, May 25, 2018 at 4:19 PM, Mujeeb Baig <baig.mujeeb(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Hi Andrew, >>>>>>> >>>>>>> Thanks for your response. Yes the path is correct >>>>>>> >>>>>>> When I execute with host location as /1234 it creates the container, >>>>>>> but nothing inside /1234 folder >>>>>>> >>>>>>> root@hdata3:/home/smb/code/conf# docker run -it -v >>>>>>> "$PWD"/syslog-ng.conf:/1234 --name syslog-ng -p 514:514 -p 601:601 >>>>>>> balabit/syslog-ng:latest >>>>>>> syslog-ng: Error setting capabilities, capability management >>>>>>> disabled; error='Operation not permitted' >>>>>>> [2018-05-25T14:12:15.695588] WARNING: Configuration file format is >>>>>>> too old, syslog-ng is running in compatibility mode. Please update it to >>>>>>> use the syslog-ng 3.14 format at your time of convenience. To upgrade the >>>>>>> configuration, please review the warnings about incompatible changes >>>>>>> printed by syslog-ng, and once completed change the @version header at the >>>>>>> top of the configuration file.; >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> I can see inside the container that /etc/syslog-ng/ this folder is >>>>>>> not updated >>>>>>> >>>>>>> root@hdata3:/home/smb# docker exec -ti syslog-ng /bin/bash >>>>>>> root@d634d32aee4c:/# >>>>>>> root@d634d32aee4c:/# ls -l /1234/ >>>>>>> total 0 >>>>>>> root@d634d32aee4c:/# >>>>>>> root@d634d32aee4c:/# ls -l /sy/etcslog-ng/ >>>>>>> conf.d/ patterndb.d/ scl.conf syslog-ng.conf >>>>>>> root@d634d32aee4c:/# ls -lrt /etc/syslog-ng/ >>>>>>> total 12 >>>>>>> -rw-r--r--. 1 root root 5910 Feb 23 13:17 syslog-ng.conf >>>>>>> drwxr-xr-x. 2 root root 6 Mar 2 12:58 conf.d >>>>>>> drwxr-xr-x. 2 root root 6 Mar 2 12:58 patterndb.d >>>>>>> -rw-r--r--. 1 root root 1336 Mar 2 12:58 scl.conf >>>>>>> root@d634d32aee4c:/# >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 25 May 2018 at 13:31, Mitzki, András <andras.mitzki(a)balabit.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Mujeeb, >>>>>>>> >>>>>>>> Maybe the problem is with the config file path: >>>>>>>> "/home/smb/code/conf/syslog-ng.conf" >>>>>>>> Could you check that path is correct? >>>>>>>> >>>>>>>> Regards >>>>>>>> Andrew >>>>>>>> >>>>>>>> On Fri, May 25, 2018 at 1:13 PM, Mujeeb Baig <baig.mujeeb(a)gmail.com >>>>>>>> > wrote: >>>>>>>> >>>>>>>>> Hi >>>>>>>>> >>>>>>>>> This is my first trial of syslog-ng. I've tried to start syslog-ng >>>>>>>>> just like described on the official bolg page >>>>>>>>> https://syslog-ng.com/blog/central-log-server-docker/ >>>>>>>>> https://syslog-ng.com/blog/collecting-docker-infrastructure-logs-using-sysl… >>>>>>>>> >>>>>>>>> I am starting docker container as: >>>>>>>>> >>>>>>>>> docker run -it -v >>>>>>>>> "$PWD"/syslog-ng.conf:/etc/syslog-ng/syslog-ng.conf --name syslog-ng -p >>>>>>>>> 514:514 -p 601:601 balabit/syslog-ng:latest >>>>>>>>> >>>>>>>>> But unfortunately it is failing to mount my custom (local) >>>>>>>>> configuration file from source to host, complaining about mounting a >>>>>>>>> directory onto file >>>>>>>>> >>>>>>>>> Error: >>>>>>>>> >>>>>>>>> docker: Error response from daemon: OCI runtime create failed: >>>>>>>>> container_linux.go:348: starting container process caused >>>>>>>>> "process_linux.go:402: container init caused \"rootfs_linux.go:58: mounting >>>>>>>>> \\"/home/smb/code/conf/syslog-ng.conf\\" to rootfs >>>>>>>>> \\"/var/lib/docker/devicemapper/mnt/52d32f854a030b396b03e7596ab5d71eb1a18f34a09d5e4997c437568749b259/rootfs\\" >>>>>>>>> at >>>>>>>>> \\"/var/lib/docker/devicemapper/mnt/52d32f854a030b396b03e7596ab5d71eb1a18f34a09d5e4997c437568749b259/rootfs/etc/syslog-ng/syslog-ng.conf\\" >>>>>>>>> caused \\"not a directory\\"\"": unknown: Are you trying to mount a >>>>>>>>> directory onto a file (or vice-versa)? Check if the specified host path >>>>>>>>> exists and is the expected type. >>>>>>>>> >>>>>>>>> Am I missing something? >>>>>>>>> >>>>>>>>> Please let me know >>>>>>>>> >>>>>>>>> Many Thanks >>>>>>>>> >>>>>>>>> Mujeeb >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ______________________________________________________________________________ >>>>>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>>>>>>>> Documentation: >>>>>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng >>>>>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ______________________________________________________________________________ >>>>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>>>>>>> Documentation: >>>>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng >>>>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> ______________________________________________________________________________ >>>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>>>>>> Documentation: >>>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng >>>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> ______________________________________________________________________________ >>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>>>>> Documentation: >>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng >>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> ______________________________________________________________________________ >>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>>>> Documentation: >>>>> http://www.balabit.com/support/documentation/?product=syslog-ng >>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>>>> >>>>> >>>>> >>>> >>>> >>>> ______________________________________________________________________________ >>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>>> Documentation: >>>> http://www.balabit.com/support/documentation/?product=syslog-ng >>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>>> >>>> >>>> >>> >>> ______________________________________________________________________________ >>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng >>> Documentation: >>> http://www.balabit.com/support/documentation/?product=syslog-ng >>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq >>> >>> >

1 0

Unbale to mount syslog-ng.conf to /etc/syslog-ng using docker image
by Mujeeb Baig 25 May '18

25 May '18

Hi This is my first trial of syslog-ng. I've tried to start syslog-ng just like described on the official bolg page https://syslog-ng.com/blog/ central-log-server-docker/ https://syslog-ng.com/blog/collecting-docker- infrastructure-logs-using-syslog-ng/ I am starting docker container as: docker run -it -v "$PWD"/syslog-ng.conf:/etc/syslog-ng/syslog-ng.conf --name syslog-ng -p 514:514 -p 601:601 balabit/syslog-ng:latest But unfortunately it is failing to mount my custom (local) configuration file from source to host, complaining about mounting a directory onto file Error: docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"rootfs_linux.go:58: mounting \\"/home/smb/code/conf/syslog-ng.conf\\" to rootfs \\"/var/lib/docker/ devicemapper/mnt/52d32f854a030b396b03e7596ab5d7 1eb1a18f34a09d5e4997c437568749b259/rootfs\\" at \\"/var/lib/docker/ devicemapper/mnt/52d32f854a030b396b03e7596ab5d7 1eb1a18f34a09d5e4997c437568749b259/rootfs/etc/syslog-ng/syslog-ng.conf\\" caused \\"not a directory\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type. Am I missing something? Please let me know Many Thanks Mujeeb

4 7

exclude empty pairs from json-parser()
by Nik Ambrosch 23 May '18

23 May '18

Hi - I'm trying to figure out how to instruct json-parser() to exclude empty (or nonexistent) json pairs from being passed to it's template. This is possible with the csv parser using null("") but not json. It seems that if i specify all my json-parser() pairs using --pair example=\"${MYMACRO}\" the desired behavior is achieved, however using --scope nv-pairs instead will log the empty values.

2 2

syslog-ng Open Source Edition official binary repository
by Gergely Bodnár 23 May '18

23 May '18

Dear syslog-ng users, Last autumn, we asked for your feedback ( https://syslog-ng.com/blog/new-website-and-official-repo-coming-up-tell-us-…) on our plan to introduce official binary repositories for syslog-ng Open Source Edition. The overwhelming majority of those who got back to us agreed that it is fair to provide this service tied to a simple registration. We are happy to announce that although a bit late compared to our originally planned schedule, we are launching this service, first as a test run with Debian Jessie packages. We will always host the latest release, and these packages will be built and tested by us, so you won't have to worry about dependencies - provided you are running a suitable Linux distribution. We are planning to add an RPM repository as well in the future, knowing well that many of our open source users require that. How to use repository? ------------------------------- To use the newly introduced syslog-ng Open Source Edition Debian Jessie repository, you only have to complete a few quick and easy steps. 1. Create a MyBalabit account (https://my.balabit.com/signup) Just click on MyBalabit in the top right corner of the page, and then choose Sign Up (under OS X, the sign up option will be hiding under the hamburger menu). At the top of the form, there will be a drop down menu where you have to specify why are you requesting access to this portal. Choose syslog-ng OSE Binary Repository Access, then fill out the rest of the form, read and agree to our privacy policy, then hit create you account.If you already happen to have a MyBalabit account, simply log in and look for Request Access in the top menu. Once in there, select syslog-ng OSE Binary Repository Access and click on request access. 2. Once you finished with the initial steps, look for the Access tokens option at the bottom of the left menu bar. In there, you will find your token to be used with the syslog-ng OSE DEB repository. If for some reason you need a new token, use the regenerate button. 3. Now you should be all set to configure your compatible Linux distribution to access the repository. # echo "deb http://JXJiI9Znyt:@apt.syslog-ng.com/syslog-ng-ose jessie main" >/etc/apt/sources.list.d/oserepo.list # apt-get update # apt-get install --no-install-recommends -y curl # curl http://JXJiI9Znyt@apt.syslog-ng.com/syslog-ng-ose/pubkey.gpg | apt-key add - # apt-get update # apt-cache policy syslog-ng # apt-get install syslog-ng And that's it, you should be all set! Please, don't forget that this is still very much a trial for us to gauge the interest in such a service. Bugs might surface, the repository might be inaccessible due to technical glitches, etc. We encourage you to share your feedback with us. It would be much appreciated! Regards, Gergely Bodnar -- *Gergely Bodnar* | syslog-ng Product Owner gergely.bodnar(a)balabit.com follow Balabit on: web <http://go.balabit.com/F9ZZ500bh0U013LX000VAE5> | blog <http://go.balabit.com/VZZi000AL90V300U55X1cE0> | linkedin <http://go.balabit.com/CZ100j0d50LU0EAZ3X09V05>| facebook <http://go.balabit.com/I090eUZ0551kEA3X0L0ZV00> | twitter <http://go.balabit.com/c0503X1U05EZ09AVl0ZfL00> *© BalaBit Corp.* Weiser Mazars 135 West 50th Street New York, NY 10020 USA

5 7

Forwarding flat files to a remote syslog-ng server
by Song, Young 22 May '18

22 May '18

Hi, I'm trying to send various flat files to a central syslog-ng server. So, I have the following setups but somehow using the "local1" and "local2" facilities don't work, although no errors when restarting syslog services on both client & server. Any advice would be appreciated much! ======================================================================= My syslog-ng CLIENT (running syslog-ng 3.6.2): source s_file1 { file("/var/log/syslog/file1.log" follow-freq(1) flags(no-parse) program_override("audit")); }; filter f_file1 { facility(local1); }; destination d_file1 { syslog("10.10.10.10" transport("udp") port(514)); }; log { source(s_file1); filter(f_file1); destination(d_file1); }; source s_file2 { file("/var/log/syslog/file2.log" follow-freq(1) flags(no-parse) program_override("audit")); }; filter f_file2 { facility(local2); }; destination d_file2 { syslog("10.10.10.10" transport("udp") port(514)); }; log { source(s_file2); filter(f_file2); destination(d_file2); }; ======================================================================== My syslog-ng SERVER (10.10.10.10 - running syslog-ng 2.0.9): destination d_file1 { file ("/var/log/syslogs/file1-$YEAR$MONTH$DAY.log" owner(root) group(root) perm(0644) dir_perm(0755) create_dirs(yes)); }; filter f_file1 { facility(local1); }; log { source(remote); filter(f_file1); destination(d_file1); }; destination d_file2 { file ("/var/log/syslogs/file2-$YEAR$MONTH$DAY.log" owner(root) group(root) perm(0644) dir_perm(0755) create_dirs(yes)); }; filter f_file2 { facility(local2); }; log { source(remote); filter(f_file2); destination(d_file2); }; Thanks. - Young

3 3

Error binding socket;
by vinod samant 14 May '18

14 May '18

Hi I am getting below error while restarting server . [root@localhost logs]# /etc/init.d/syslog-ng restart Stopping syslog-ng: [FAILED] syslog-ng is stopped Starting syslog-ng: [2018-05-11T16:41:55.756615] Error binding socket; addr='AF_INET(0.0.0.0:514)', error='Address already in use (98)' [2018-05-11T16:41:55.756684] Error initializing message pipeline; plugin name='network', location='/etc/syslog-ng/syslog-ng.conf:24:3' [FAILED] My requirement :- OS:- centos 6.5 1. I want to use wildcard to send all apache custom logs from client to server . Configuration of both client and server :- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>client conf<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< @version:3.13 @include "scl.conf" @define allow-config-dups 1 source s_local { system(); internal(); }; destination d_network {udp("192.168.122.67" port(514)); }; destination d_local { file("/var/log/messages"); }; log{ source(s_local); destination(d_network); destination(d_local); }; #################### source s_local{ wildcard-file( base-dir("/usr/local/apache/logs") filename-pattern("*.log") recursive(no) follow-freq(1)); }; destination d_network {tcp("192.168.122.67" port(514)); }; log{ source(s_local); destination(d_network); }; >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>server conf<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< @version:3.13 @include "scl.conf" source s_local{system(); internal();}; source s_network{ udp(); tcp(); }; destination d_local{file("/var/log/messages");}; destination d_from_net{file("/var/log/from_net");}; log{ source(s_local); destination(d_local); }; log { source(s_network); destination(d_from_net); }; source s_net { network(flags(no-parse)); }; parser p_apache { csv-parser( columns("apache.FILE_NAME", "apache.MESSAGE") flags(greedy) ); }; destination d_apache { file("/usr/local/apache/logs/${apache.FILE_NAME}" template("${apache.MESSAGE}\n")); }; log{ source (s_net); parser (p_apache); destination(d_apache); }; What should be changed on configuration file on both side ? *Thanks & Regards :-* *VINOD SINGH SAUD* *(M):- 09718663552* *(W):-09997645597* *(E) :- vinod.samant.123(a)gmail.com <vinod.samant.123(a)gmail.com>*

3 6

How to configure client and host server
by vinod samant 11 May '18

11 May '18

Hi , I am beginner in linux and first time i am going to installation and configure syslog-ng .So, I hope ,will get more help from your side because i am being confuse while reading documentation.first of all i want to mention my requirements. OS:- centos 6.9 My Requirements:- 1. we have 20 apache webserver ,we are writing apache custom logs or php applications logs in a particular directory ,But directory location is different different for both apache log and php application logs. For example we are writing log in "/usr/local/apache/logs " and apache log format or php application log format are mentioned below . *apche custom logs Fromta:- * abc_access_2018-05-09.log ,abc_error_2018-05-09.log and xyz_access_2018-05-09.log etc.. *Php application log format:- * hello_vidoes_20180509.txt , world_music_20180509.txt 2. I want to store these logs of 20 web servers on a centralised server at real time and we do not want to change logs file and format . Is this possible? 3. I want to make 20 web server as client server and centralised server (as host server). Here ,I can not understand from documentation ,So Can you provide the configuration for both side client and host side ? Client ip:- 192.168.122.184 server IP(centralised):- 192.168.122.61 *Thanks & Regards :-* *VINOD SINGH SAUD* *(M):- 09718663552* *(W):-09997645597* *(E) :- vinod.samant.123(a)gmail.com <vinod.samant.123(a)gmail.com>*

3 9

Best way to pipe "application" logs to central syslog-ng server.
by Delon Lee Di Lun 09 May '18

09 May '18

Hi, I am working on a mini project that requires the receipt of "application" logs using rsyslog client to pipe it to a syslog-ng central server. An example of the "application" logs im referring to would be for instance Apache HTTPD logs, I want to separate the "application" logs, in this example, the apache logs, and the "OS" logs into different directories. I am thinking of certain crude way, using regex to filter the messages at my server end ,to do it which might not be as clean. Would like to ask the floor if anybody had experience with working in this environment. Would change my rsyslog client and my syslog-ng server to use RFC5424, IETF's compare to the legacy BSD syslog protocol help? Comparing the headers there is a "app-name" variable in the IETF's syslog protocol I can use? Yours Sincerely, Delon Lee

5 12

Disk based queuing with rsyslog?
by Delon Lee Di Lun 09 May '18

09 May '18

Hi, I read that syslog-ng can be setup to use disk based with flow control with the client to prevent lost of logs. However I was just thinking, how does this mechanism works? Does the client have to be using syslog-ng? Will it work if the client is using rsyslog? Native appliance that purely support syslog? Yours Sincerely, Delon Lee

4 9