- syslog-ng - lists.balabit.hu

Finding feature owner for Kafka source project
by Vithulan MV 21 May '16

21 May '16

Hi all, As you may have all known already, We are going to develop a new feature, Kafka source for syslog-ng product during this GSoC 2016 under the guidance of Viktor Juhasz. A simple abstract idea of this project is, The syslog-ng application can read messages from the sources. It processes them with filters, rewrite rules, parsers and finally sends messages to their destinations. The syslog-ng application already has a Kafka destination that is implemented in Java. The Kafka source will allow syslog-ng to read messages from Kafka, for an example this can be used for example as a queue between several syslog-ng instances. Kafka source project will allow you to, -Use Kafka consumer which uses the high level Kafka group consuming API. -Continue reading from the last message from which syslog-ng reloaded/restarted. -Avoid message loosing or message duplication as much as possible whenever there is multiple syslog-ng reading the same kafka input. If you are interested to become a feature owner for Kafka source project and give us guidance on user's perspective, it will be very easy for us to build a effective component. Appreciate if you can contact us by sending mail to us or to this thread. Thanks, Best regards, Vithulan. -- Vithulan MV. Undergraduate, Department of Computer Science & Engineering, University of Moratuwa, Sri lanka.

3 2

Re: [syslog-ng] message loss using multi-line-mode
by Laszlo Budai 19 May '16

19 May '16

Hi, opening a new issue is not necessary. I hope that a GSoC student will solve this issue. BTW GSoC: we are still looking for feature owners to our GSoC[1] projects[2]. As an experienced syslog-ng user you could join to us. What do you think? [1] https://syslog-ng.org/gsoc-2016/ [2] https://lists.balabit.hu/pipermail/syslog-ng/2016-April/022862.html regards, Laszlo Budai Sent from my HTC ----- Reply message ----- From: "Patrick Hemmer" <syslogng(a)stormcloud9.net> To: "Syslog-ng users' and developers' mailing list" <syslog-ng(a)lists.balabit.hu> Subject: [syslog-ng] message loss using multi-line-mode Date: Tue, May 17, 2016 00:17 Anybody? Should I open a new issue? -Patrick On 2016/3/28 12:01, Patrick Hemmer wrote: > I raised issue on an existing bug on the github tracker, but it seems > to have gone unnoticed, so I'm repeating it here to try and get some > attention on the issue. > > Using multi-line-mode without the multi-line-suffix option WILL result > in message loss. > When syslog-ng is running in multi-line-mode, it buffers multi-line > messages until it sees the start of a new message. When it sees the > start of a new message, it flushes the buffered message, and puts the > first line of the new message in the buffer. However if syslog-ng > shuts down, or receives a SIGHUP (reload), any lines currently > buffered are discarded. Given that syslog-ng can't stay running > forever, and it will get shut down or SIGHUPd eventually, using this > feature will result in messages getting lost. > > The message on the github issue where I brought this up is: > https://github.com/balabit/syslog-ng/issues/140#issuecomment-197673887 > > -Patrick > > > ______________________________________________________________________________ > 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

2 1

Re: [syslog-ng] message loss using multi-line-mode
by Laszlo Budai 19 May '16

19 May '16

Hi, it is an ideal topic for GSoC students during community bonding period (or those who want to participate in GSoC in the future). Any volunteer? L. Sent from my HTC ----- Reply message ----- From: syslogng(a)stormcloud9.net To: "Syslog-ng users' and developers' mailing list" <syslog-ng(a)lists.balabit.hu> Subject: [syslog-ng] message loss using multi-line-mode Date: Wed, May 18, 2016 15:58 That was my original intent (to write a patch), but after looking at the code, I didn't think it would be a good idea (I used to code against syslog-ng back in the around the 3.1 days, but it appears the code has gotten significantly more complex). Given that there is message loss involved here, I just thought it might raise the priority of the issue. -Patrick On 2016/5/17 08:47, Scheidler, Balázs wrote: > hi, > > I don't think that would help, sorry. Everyone is working on other > stuff as it seems. Would you try to cook up a patch? I know it might > intimidating at first, but you know it's all just code and computers > :) not more complicated than a shell script. * > > [*] ok, a bit more complicated, but everyone has to start somewhere :) > > > -- > Bazsi > > On Tue, May 17, 2016 at 12:16 AM, Patrick Hemmer > <syslogng(a)stormcloud9.net <mailto:syslogng@stormcloud9.net>> wrote: > > Anybody? Should I open a new issue? > > -Patrick > > > On 2016/3/28 12:01, Patrick Hemmer wrote: >> I raised issue on an existing bug on the github tracker, but it >> seems to have gone unnoticed, so I'm repeating it here to try and >> get some attention on the issue. >> >> Using multi-line-mode without the multi-line-suffix option WILL >> result in message loss. >> When syslog-ng is running in multi-line-mode, it buffers >> multi-line messages until it sees the start of a new message. >> When it sees the start of a new message, it flushes the buffered >> message, and puts the first line of the new message in the >> buffer. However if syslog-ng shuts down, or receives a SIGHUP >> (reload), any lines currently buffered are discarded. Given that >> syslog-ng can't stay running forever, and it will get shut down >> or SIGHUPd eventually, using this feature will result in messages >> getting lost. >> >> The message on the github issue where I brought this up is: >> https://github.com/balabit/syslog-ng/issues/140#issuecomment-197673887 >> >> -Patrick >> >> >> ______________________________________________________________________________ >> 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

message loss using multi-line-mode
by Patrick Hemmer 18 May '16

18 May '16

I raised issue on an existing bug on the github tracker, but it seems to have gone unnoticed, so I'm repeating it here to try and get some attention on the issue. Using multi-line-mode without the multi-line-suffix option WILL result in message loss. When syslog-ng is running in multi-line-mode, it buffers multi-line messages until it sees the start of a new message. When it sees the start of a new message, it flushes the buffered message, and puts the first line of the new message in the buffer. However if syslog-ng shuts down, or receives a SIGHUP (reload), any lines currently buffered are discarded. Given that syslog-ng can't stay running forever, and it will get shut down or SIGHUPd eventually, using this feature will result in messages getting lost. The message on the github issue where I brought this up is: https://github.com/balabit/syslog-ng/issues/140#issuecomment-197673887 -Patrick

4 4

Re: [syslog-ng] Syslog-NG RFC
by Ivan Adji - Krstev 17 May '16

17 May '16

On 05/17/2016 01:22 PM, Ivan Adji - Krstev wrote: > Hi Robert, > Everything is placed as it is. I have put the server and the client in > the networ() part the *flags* and still nothing. No template in use. > > Here is the configuration of the server: > > options { > flush_lines (0); > time_reopen (10); > log_fifo_size (1000); > chain_hostnames (off); > use_dns (no); > use_fqdn (no); > create_dirs (no); > keep_hostname (yes); > }; > > source s_sys { > system(); > internal(); > network(ip(0.0.0.0) port(6514) > flags(syslog-protocol) > transport("tls") > tls(key_file("/etc/syslog-ng/cert.d/serverkey.pem") > cert_file("/etc/syslog-ng/cert.d/servercert.pem") > ca_dir("/etc/syslog-ng/ca.d") > ) ); > > }; > > destination d_mongodb { > mongodb( > servers("localhost:27017") > database("syslog") > username("test") > password("test123") > collection("messages") > value-pairs( > scope("selected-macros" "nv-pairs" "sdata") > ) > ); > }; > > > And here it is on the client site: > > options { > flush_lines (0); > time_reopen (10); > log_fifo_size (1000); > chain_hostnames (off); > use_dns (no); > use_fqdn (no); > create_dirs (no); > keep_hostname (yes); > }; > > source s_sys { > system(); > internal(); > # udp(ip(0.0.0.0) port(514)); > }; > > > destination tls_destination { > network("x.x.x.x" port(6514) > flags(syslog-protocol) > transport("tls") > tls( ca_dir("/etc/syslog-ng/ca.d") > key_file("/etc/syslog-ng/cert.d/clientkey.pem") > cert_file("/etc/syslog-ng/cert.d/clientcert.pem") ) > ); > }; > > > And i have use the same configuration with MySQL and works perfect now > i have problems with MongoDB. > > Kind regards > Ivan > > > On 05/17/2016 01:10 PM, Fekete, Róbert wrote: >> Hi, >> >> The protocols used in the syslog-ng clients and the syslog-ng server >> should match. >> You posted a source that uses the network() driver - I take this is >> from your server. >> The destination on your client should also use the network() driver, >> and that's where you need the flags(syslog-protocol). >> >> Also check your client config to see if it uses a custom template >> that messes with the message format. >> >> Robert >> >> >> >> On Tue, May 17, 2016 at 10:49 AM, Ivan Adji - Krstev >> <akivanradix(a)gmail.com <mailto:akivanradix@gmail.com>> wrote: >> >> Any way i put it where i can and on a client but still nothing. >> >> Any other hints ? >> >> Ivan >> >> On 05/17/2016 10:31 AM, Fabien Wernli wrote: >>> Hi, >>> >>> On Tue, May 17, 2016 at 10:11:27AM +0200, Ivan Adji - Krstev wrote: >>>> some RFC model 5424. Is there an option to configure the syslog-ng to >>>> send this messages in that RFC format ? >>> Add `flags(syslog-protocol)` to the network destination >>> >>> ______________________________________________________________________________ >>> 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

Syslog-NG RFC
by Ivan Adji - Krstev 17 May '16

17 May '16

Hi all, I have configure the Syslog-NG with MongoDB and LogAnalyzer, and as output i have the messages but i have no Date, Facility Severity Syslogtag and other information from it. If i go on a message itself i have some additional information. I have found out that i should use some RFC model 5424. Is there an option to configure the syslog-ng to send this messages in that RFC format ? Kind regards Ivan

3 4

Building syslog-ng 3.7.3 in Ubuntu Xenial
by Vithulan MV 15 May '16

15 May '16

Hi all, I got the tarball from, https://github.com/balabit/syslog-ng/releases (version 3.7.3). When I tried to build it, - configure passed. - make passed - make check failed with the following message, /usr/bin/ld: modules/systemd-journal/tests/modules_systemd_journal_tests_test_systemd_journal-test_systemd_journal.o: undefined reference to symbol 'iv_task_registered@@IVYKIS_0.29' //usr/local/lib/libivykis.so.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status Makefile:6297: recipe for target 'modules/systemd-journal/tests/test_systemd_journal' failed make[3]: *** [modules/systemd-journal/tests/test_systemd_journal] Error 1 Makefile:11738: recipe for target 'check-am' failed make[2]: *** [check-am] Error 2 Makefile:11313: recipe for target 'check-recursive' failed make[1]: *** [check-recursive] Error 1 Makefile:11741: recipe for target 'check' failed make: *** [check] Error 2 Also, getting this warning when compiling, Makefile:12423: warning: overriding recipe for target 'eclipse' Makefile:12398: warning: ignoring old recipe for target 'eclipse' What could be the cause for this problem? Thanks. Best regards, Vithulan. -- Vithulan MV. Undergraduate, Department of Computer Science & Engineering, University of Moratuwa, Sri lanka.

2 3

Syslog-ng meetup in London
by Balazs Scheidler 14 May '16

14 May '16

Hi, We are experimenting with a new syslog-ng related event format in London, 26th of May. I am travelling there and will be speaking about syslog-ng, past, present and future. Peter Czanik will also be there. The general approach is more about questions and discussions instead of presentations. Anyone in the area is welcome, beer is on @Balabit. :) RSVP at http://www.meetup.com/syslog-ng-london/events/231038819 Cheers, Bazsi

1 0

Syslog-ng with MongoDB authentication
by Ivan Adji - Krstev 13 May '16

13 May '16

Hi all, I have configure MongoDB with Username and Password, but can't find how to configure destination on Syslog-ng using MongoDB with Username and Password. For now i have just this: destination d_mongodb { mongodb( servers("localhost:27017") database("syslog") collection("messages") value-pairs( scope("selected-macros" "nv-pairs" "sdata") ) ); }; But i should add some username and passwords somewhere and don't know how. Any hints on this ? Kind regards Ivan

2 1

Re: [syslog-ng] Installing Syslog-NG 3.7 on CentOS 7
by jrhendri 12 May '16

12 May '16

This has to be something very basic.Have you tried checking if another syslog server is running? ps -aef |grep syslog Assuming this shows nothing, try a very simple syslog-ng config file and a manual start on the command line. Make sure you check all the things in your configuration that your copy should open beforehand. This should narrow down the problem I hope :-) Jim Sent from my Verizon, Samsung Galaxy smartphone -------- Original message --------From: Ivan Adji - Krstev <akivanradix(a)gmail.com> Date: 5/12/16 5:26 AM (GMT-05:00) To: syslog-ng(a)lists.balabit.hu Subject: Re: [syslog-ng] Installing Syslog-NG 3.7 on CentOS 7 So i have install EPEL and i have install syslog-ng and mongodb and when i start the syslog-ng service with syslog-ng -Fevd command i have the following error AGAIN :). Im not sure what is it and how to prevent it and what to do. But i really need this to work :(. [2016-05-12T05:21:10.739940] Error binding socket; addr='AF_INET(0.0.0.0:6514)', error='Address already in use (98)' [2016-05-12T05:21:10.739973] Error initializing message pipeline; [root@syslogserver loganalyzer]# netstat -tupl Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 localhost:27017 0.0.0.0:* LISTEN 1352/mongod tcp 0 0 0.0.0.0:syslog-tls 0.0.0.0:* LISTEN 11377/syslog-ng tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN 8562/sshd tcp 0 0 localhost:smtp 0.0.0.0:* LISTEN 1778/master tcp6 0 0 [::]:http [::]:* LISTEN 11264/httpd tcp6 0 0 [::]:ssh [::]:* LISTEN 8562/sshd tcp6 0 0 localhost:smtp [::]:* LISTEN 1778/master udp 0 0 0.0.0.0:bootpc 0.0.0.0:* 638/dhclient udp 0 0 0.0.0.0:60094 0.0.0.0:* 638/dhclient udp6 0 0 [::]:3126 [::]:* 638/dhclient [root@syslogserver loganalyzer]# lsof | grep LISTEN mongod 1352 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 1393 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 2028 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 2033 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 2034 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 2138 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 2139 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 2141 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 2148 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 2404 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 2446 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 2447 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 2448 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 2449 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 2450 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 2451 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) mongod 1352 11380 mongod 6u IPv4 17057 0t0 TCP localhost:27017 (LISTEN) master 1778 root 13u IPv4 15893 0t0 TCP localhost:smtp (LISTEN) master 1778 root 14u IPv6 15894 0t0 TCP localhost:smtp (LISTEN) sshd 8562 root 3u IPv4 23963 0t0 TCP *:ssh (LISTEN) sshd 8562 root 4u IPv6 23965 0t0 TCP *:ssh (LISTEN) httpd 11264 root 4u IPv6 32697 0t0 TCP *:http (LISTEN) httpd 11265 apache 4u IPv6 32697 0t0 TCP *:http (LISTEN) httpd 11267 apache 4u IPv6 32697 0t0 TCP *:http (LISTEN) httpd 11268 apache 4u IPv6 32697 0t0 TCP *:http (LISTEN) httpd 11269 apache 4u IPv6 32697 0t0 TCP *:http (LISTEN) httpd 11270 apache 4u IPv6 32697 0t0 TCP *:http (LISTEN) httpd 11275 apache 4u IPv6 32697 0t0 TCP *:http (LISTEN) httpd 11276 apache 4u IPv6 32697 0t0 TCP *:http (LISTEN) httpd 11277 apache 4u IPv6 32697 0t0 TCP *:http (LISTEN) httpd 11278 apache 4u IPv6 32697 0t0 TCP *:http (LISTEN) syslog-ng 11377 root 14u IPv4 34906 0t0 TCP *:syslog-tls (LISTEN) syslog-ng 11377 11378 root 14u IPv4 34906 0t0 TCP *:syslog-tls (LISTEN) syslog-ng 11377 11541 root 14u IPv4 34906 0t0 TCP *:syslog-tls (LISTEN) httpd 11384 apache 4u IPv6 32697 0t0 TCP *:http (LISTEN) and the source config is as follow: source s_sys { system(); unix-stream("/dev/log"); internal(); network( port(6514) # tcp(port(5140)); # file("/proc/kmsg" log_prefix("kernel: ")); transport("tls") tls( key_file("/etc/syslog-ng/cert.d/serverkey.pem") cert_file("/etc/syslog-ng/cert.d/servercert.pem") ca_dir("/etc/syslog-ng/ca.d")) ); }; destination d_mongodb { mongodb( # servers("localhost:27017") # database("syslog") # uri('mongodb://localhost/syslog-ng') collection("messages") value-pairs( scope("selected-macros" "nv-pairs" "sdata") ) ); }; Kind regards Ivan On 05/10/2016 01:35 PM, Czanik, Péter wrote: Do you also have EPEL? The RHEL7/CentOS7 repo is built against EPEL, as some of the dependencies are missing from the base distribution: https://fedoraproject.org/wiki/EPEL Bye, Peter Czanik (CzP) <peter.czanik(a)balabit.com> Balabit / syslog-ng upstream http://czanik.blogs.balabit.com/ https://twitter.com/PCzanik On Tue, May 10, 2016 at 1:29 PM, Ivan Adji - Krstev <akivanradix(a)gmail.com> wrote: Hi i note this error of mine but i try the other one: https://copr.fedorainfracloud.org/coprs/czanik/syslog-ng37/repo/epel-7/czan… And i have the similar errors when ever i try to install on new CentOS The procedure im doing is: Fresh installation of CentOS yum update yum install httpd php vim wget then install mongodb ( add repo ) then install syslog-ng ( add repo ) I'm using: CentOS Linux release 7.2.1511 (Core) And im having the following repos: [root@syslogserver ~]# yum repolist Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.switch.ch * extras: mirror.switch.ch * updates: mirror.switch.ch repo id repo name status base/7/x86_64 CentOS-7 - Base 9,007 czanik-syslog-ng37/x86_64 Copr repo for syslog-ng37 owned by czanik 59 extras/7/x86_64 CentOS-7 - Extras 266 mongodb-org-3.2/7 MongoDB Repository 35 updates/7/x86_64 CentOS-7 - Updates 1,437 repolist: 10,804 [root@syslogserver ~]# yum install syslog-ng Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.switch.ch * extras: mirror.switch.ch * updates: mirror.switch.ch Resolving Dependencies --> Running transaction check ---> Package syslog-ng.x86_64 0:3.7.3-3.el7.centos will be installed --> Processing Dependency: ivykis >= 0.36.1 for package: syslog-ng-3.7.3-3.el7.centos.x86_64 --> Processing Dependency: libivykis.so.0(IVYKIS_0.29)(64bit) for package: syslog-ng-3.7.3-3.el7.centos.x86_64 --> Processing Dependency: libivykis.so.0(IVYKIS_0.30)(64bit) for package: syslog-ng-3.7.3-3.el7.centos.x86_64 --> Processing Dependency: libevtlog.so.0()(64bit) for package: syslog-ng-3.7.3-3.el7.centos.x86_64 --> Processing Dependency: libivykis.so.0()(64bit) for package: syslog-ng-3.7.3-3.el7.centos.x86_64 --> Processing Dependency: libnet.so.1()(64bit) for package: syslog-ng-3.7.3-3.el7.centos.x86_64 --> Running transaction check ---> Package libnet.x86_64 0:1.1.6-7.el7 will be installed ---> Package syslog-ng.x86_64 0:3.7.3-3.el7.centos will be installed --> Processing Dependency: ivykis >= 0.36.1 for package: syslog-ng-3.7.3-3.el7.centos.x86_64 --> Processing Dependency: libivykis.so.0(IVYKIS_0.29)(64bit) for package: syslog-ng-3.7.3-3.el7.centos.x86_64 --> Processing Dependency: libivykis.so.0(IVYKIS_0.30)(64bit) for package: syslog-ng-3.7.3-3.el7.centos.x86_64 --> Processing Dependency: libevtlog.so.0()(64bit) for package: syslog-ng-3.7.3-3.el7.centos.x86_64 --> Processing Dependency: libivykis.so.0()(64bit) for package: syslog-ng-3.7.3-3.el7.centos.x86_64 --> Finished Dependency Resolution Error: Package: syslog-ng-3.7.3-3.el7.centos.x86_64 (czanik-syslog-ng37) Requires: libivykis.so.0(IVYKIS_0.30)(64bit) Error: Package: syslog-ng-3.7.3-3.el7.centos.x86_64 (czanik-syslog-ng37) Requires: libivykis.so.0()(64bit) Error: Package: syslog-ng-3.7.3-3.el7.centos.x86_64 (czanik-syslog-ng37) Requires: ivykis >= 0.36.1 Error: Package: syslog-ng-3.7.3-3.el7.centos.x86_64 (czanik-syslog-ng37) Requires: libevtlog.so.0()(64bit) Error: Package: syslog-ng-3.7.3-3.el7.centos.x86_64 (czanik-syslog-ng37) Requires: libivykis.so.0(IVYKIS_0.29)(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Any idea ? On 05/09/2016 04:09 PM, Czanik, Péter wrote: Hi, You should add the repository using the file: https://copr.fedorainfracloud.org/coprs/czanik/syslog-ng37/repo/epel-7/czan… to yum and not just download individual packages. You can use then "yum install syslog-ng" which will also download all necessary dependencies. Bye, Peter Czanik (CzP) <peter.czanik(a)balabit.com> Balabit / syslog-ng upstream http://czanik.blogs.balabit.com/ https://twitter.com/PCzanik On Mon, May 9, 2016 at 3:07 PM, Ivan Adji - Krstev <akivanradix(a)gmail.com> wrote: I have the following errors when i try to install Syslog-NG 3.7 on CentOS 7 I have problem when i try to install Syslog-NG 3.7 on CentOS 7. The following errors i get: --> Finished Dependency Resolution Error: Package: syslog-ng-3.7.3-1.el6.x86_64 (czanik-syslog-ng37epel6) Requires: libevtlog.so.0()(64bit) Error: Package: syslog-ng-3.7.3-1.el6.x86_64 (czanik-syslog-ng37epel6) Requires: libpcre.so.0()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Any hints on this ? Kind regards Ivan ______________________________________________________________________________ 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

4 11