From mboxrd@z Thu Jan 1 00:00:00 1970 From: ummeegge To: development@lists.ipfire.org Subject: Re: Testing Core Update 118 Date: Fri, 02 Feb 2018 20:49:34 +0100 Message-ID: In-Reply-To: <1517498173.2319.5.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7306746328275274147==" List-Id: --===============7306746328275274147== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi all, did some tests now with Rsyslog which needed some entries in rsyslog.conf mor= e then before but the old sysklogd format can nevertheless be used and the lo= gging results are the same then sysklogd=C2=B4s . Have build Rsyslog also in openssl-11 environment which looks good for the bu= ilding process, a test on a machine without OpenSSL-1.1.0g looked like this: -> /etc/init.d/rsyslog start Starting system logger...=20 /usr/sbin/rsyslogd: error while loading shared libraries: libssl.so.1.1: cann= ot open shared object file: No such file or directory [ OK ] which looks good. Started with a configuration file and an initscript whereby= both are functional but this is a fast shot and there should be more possibl= e. Am 01.02.2018 um 16:16 schrieb Michael Tremer: > Hi, >=20 > On Thu, 2018-02-01 at 15:43 +0100, ummeegge wrote: >> Hello, >>=20 >> Am 01.02.2018 um 12:37 schrieb Michael Tremer: >>=20 >>> Hi, >>>=20 >>> nothing of that sounds too bad - except that it sounds a bit extortionate= for >>> just some syslogging. >>>=20 >>> Maybe it is worth trying it if can be built without json at least. >>=20 >> Have tried yesterday for fast checkout if it builds but the compilation qu= its causing a non existing libfastjson. Also the Rsyslog documentation points= json-c as a requirement --> http://www.rsyslog.com/doc/master/installation/i= nstall_from_source.html#build-requirements out, not sure if can get around it= . Some of the other listed libs at the bottom might not be a requirement but= possibly a nice one to have even the logs should be send to a remote log ser= ver. >> Rsyslog do provides really a lot of extensions which might be worth for a = look over... >=20 > I am not sure if we need any of the extensions since we are basically > using the bare minimum at the moment - sysklogd cannot do much more. > And so far nobody has really complained about this. I think we need in a minimum 'imuxsock.so' and 'imklog.so' to get the same lo= gging results then sysklod provides it. But there is more and it might be nic= e if someone jump into this here and complains more about possible extensions. It might also be possible to make a rsyslog-mysql or rsyslog-elasticsearch pa= cket available via Pakfire ? But this only as an idea from here... >=20 > json-c is fine. Some other packages need this too and I am sure that I > have built this before somewhere. Yes i do remember that too ??=20 >=20 > The rest: I think the rsyslogd people are doing this a bit wrong. It is > quite an excessive amount of libraries and I do not get why some basic > functionality like a syslog daemon needs that. But I guess we don't > have any other choice here than packaging all of them. Think so, lot=C2=B4s of new packages event they aren=C2=B4t that heavy weight= s but as mentioned some of them can possibly also be dropped but may they are= also nice ones to have ? Possibly Peter can also take a look into that. >=20 >>> However, since we are on the topic of logging reliably, it might be inter= esting >>> to have support for SSL in there. >>=20 >> This should be no problem i think. Rsyslog can be linked against libgcrypt= , GnuTLS and OpenSSL. A build is currently running on a openssl-11 basis wher= eby i think OpenSSL should be preferred ? >=20 > OpenSSL should be preferred. Yes. >=20 >>>=20 >>> Have you tried if the old configuration file works or does it come with a= new >>> configuration file format? >>=20 >> The new version 8.32 is in building process will check this if it is ready= . On my first tries with Rsyslog which is no also 1+ year ago, i needed to ma= ke two changes on syslog.conf --> https://forum.ipfire.org/viewtopic.php?t=3D= 16669#p98481 and after that i renamed it to rsyslog.conf and everything worke= d just fine. >=20 > That sounds good. They have their own configuration file format for > some modules stuff but since we don't intend to use any of that, we > should be fine here. Think so. >=20 > Would you update those packages and rebase the branch on next since you > have already been working on this? Please send this over to Peter for > review then and let him test the TCP logging capabilities since he was > the one who required this in the first place. No problem but i think it might be a little more then a review only since som= e more stuff needs to be checked especially for the config but also the inits= cript. Build it currently as packages (easier to install) 32bit are ready and a litt= le tested am currently on a 64 bit build. >=20 > But let's only start working on this when the current OpenVPN stuff is > done. For an OK is it too late now :D but i won=C2=B4t do much more on this since i= t works and i think this might be a good state to work further on it. Will pu= sh it to Git then ? Greetings, Erik --===============7306746328275274147==--