Install rsyslog-3.22.0 with gnutls on RHEL5.2

Everything related with getting rsyslog up and running (but not beyond that point ;))

Moderator: rgerhards

Install rsyslog-3.22.0 with gnutls on RHEL5.2

Postby flaco » Thu May 14, 2009 7:29 am

Hi all,
I have a great problem upgrading from source rsyslog-3.20.4 to rsyslog-3.22.0 with gnutls.

Until 3.20.4 rsyslog accepts gnutls-1.4. Red Hat EL5 distributes only gnutls-1.x.

With 3.22.0 rsyslog requires gnutls > 2.0.0. This make me desperate. I tried, but there is no way to upgrade gnutls from 1.4 to 2.x. Even with gnutls tar source I see make errors.

Maybe could you tell me how can I install rsyslog-3.22.0 with gnutls over Red Hat enterprise 5?

Thank you very much for every hints.

Best Regards
Marco
flaco
Avarage
 
Posts: 18
Joined: Thu Sep 20, 2007 10:23 am

Professional Services Information

  • Custom written rsyslog.conf?
  • Maintenance Contract?
  • Installation support?

Re: Install rsyslog-3.22.0 with gnutls on RHEL5.2

Postby rgerhards » Thu May 14, 2009 9:28 am

I think this is easy to fix, I just need confirmation to do it on a permanent basis. Go to configure.ac. Search for gnutls. Theer is a check "gnutls > 2.0.0". Replace 2.0.0 with the version you have (1.4.0?). Then rebuild the system. If it works, the issue is solved.

The 2.0.0 check is a side-effect of the new pkgconfig check. I could only verify with down to 2.0.0, thus I used that version. However, if it compiles successfully, it also runs with the older version. I think I even developed it with 1.3 or so.

If you can confirm that this fix works for you, I can make the same change in the official release tarball. But I don't like to do that without at least one confirmation...

Looking forward to your results.

Rainer
User avatar
rgerhards
Site Admin
 
Posts: 2647
Joined: Thu Feb 13, 2003 11:57 am

Re: Install rsyslog-3.22.0 with gnutls on RHEL5.2

Postby flaco » Thu May 14, 2009 11:03 am

rgerhards wrote:If you can confirm that this fix works for you, I can make the same change in the official release tarball. But I don't like to do that without at least one confirmation...

Looking forward to your results.

Rainer


Rainer,
I thank you very much for this.

I have modified configure.ac and configure as you say. These are the diffs:

configure.ac:
Code: Select all
520c520
<       PKG_CHECK_MODULES(GNUTLS, gnutls >= 2.0.0)
---
>       PKG_CHECK_MODULES(GNUTLS, gnutls >= 1.4.0)


configure:
Code: Select all
27746,27747c27746,27747
<     { ($as_echo "$as_me:$LINENO: \$PKG_CONFIG --exists --print-errors \"gnutls >= 2.0.0\"") >&5
<   ($PKG_CONFIG --exists --print-errors "gnutls >= 2.0.0") 2>&5
---
>     { ($as_echo "$as_me:$LINENO: \$PKG_CONFIG --exists --print-errors \"gnutls >= 1.4.0\"") >&5
>   ($PKG_CONFIG --exists --print-errors "gnutls >= 1.4.0") 2>&5
27751c27751
<   pkg_cv_GNUTLS_CFLAGS=`$PKG_CONFIG --cflags "gnutls >= 2.0.0" 2>/dev/null`
---
>   pkg_cv_GNUTLS_CFLAGS=`$PKG_CONFIG --cflags "gnutls >= 1.4.0" 2>/dev/null`
27762,27763c27762,27763
<     { ($as_echo "$as_me:$LINENO: \$PKG_CONFIG --exists --print-errors \"gnutls >= 2.0.0\"") >&5
<   ($PKG_CONFIG --exists --print-errors "gnutls >= 2.0.0") 2>&5
---
>     { ($as_echo "$as_me:$LINENO: \$PKG_CONFIG --exists --print-errors \"gnutls >= 1.4.0\"") >&5
>   ($PKG_CONFIG --exists --print-errors "gnutls >= 1.4.0") 2>&5
27767c27767
<   pkg_cv_GNUTLS_LIBS=`$PKG_CONFIG --libs "gnutls >= 2.0.0" 2>/dev/null`
---
>   pkg_cv_GNUTLS_LIBS=`$PKG_CONFIG --libs "gnutls >= 1.4.0" 2>/dev/null`
27785c27785
<               GNUTLS_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors "gnutls >= 2.0.0" 2>&1`
---
>               GNUTLS_PKG_ERRORS=`$PKG_CONFIG --short-errors --print-errors "gnutls >= 1.4.0" 2>&1`
27787c27787
<               GNUTLS_PKG_ERRORS=`$PKG_CONFIG --print-errors "gnutls >= 2.0.0" 2>&1`
---
>               GNUTLS_PKG_ERRORS=`$PKG_CONFIG --print-errors "gnutls >= 1.4.0" 2>&1`
27792c27792
<       { { $as_echo "$as_me:$LINENO: error: Package requirements (gnutls >= 2.0.0) were not met:
---
>       { { $as_echo "$as_me:$LINENO: error: Package requirements (gnutls >= 1.4.0) were not met:
27803c27803
< $as_echo "$as_me: error: Package requirements (gnutls >= 2.0.0) were not met:
---
> $as_echo "$as_me: error: Package requirements (gnutls >= 1.4.0) were not met:



The modified configure script works properly:

rsyslog will be compiled with the following settings:

Code: Select all
Multithreading support enabled:           yes
Klog functionality enabled:               yes (linux)
Regular expressions support enabled:      yes
Zlib compression support enabled:         yes
MySql support enabled:                    yes
libdbi support enabled:                   no
PostgreSQL support enabled:               no
SNMP support enabled:                     yes
Mail support enabled:                     yes
RELP support enabled:                     yes
imdiag enabled:                           no
file input module enabled:                yes
input template module will be compiled:   yes
Large file support enabled:               yes
Networking support enabled:               yes
GnuTLS network stream driver enabled:     yes
Enable GSSAPI Kerberos 5 support:         no
Debug mode enabled:                       no
Runtime Instrumentation enabled:          no
Diagnostic tools enabled:                 no
valgrind support settings enabled:        no
rsyslog runtime will be built:            yes
rsyslogd will be built:                   yes


Also 'make' and 'make install' work fine.
I notice only what follow. 'make' explains that:

Code: Select all
WARNING: `aclocal-1.10' is missing on your system.  You should only need it if
         you modified `acinclude.m4' or `configure.ac'.  You might want
         to install the `Automake' and `Perl' packages.  Grab them from
         any GNU archive site.
cd . && /bin/sh /root/setup/3_rsyslog/rsyslog-3.22.0/missing --run autoconf
cd . && /bin/sh /root/setup/3_rsyslog/rsyslog-3.22.0/missing --run automake-1.10 --gnu
/root/setup/3_rsyslog/rsyslog-3.22.0/missing: line 54: automake-1.10: command not found
WARNING: `automake-1.10' is missing on your system.  You should only need it if
         you modified `Makefile.am', `acinclude.m4' or `configure.ac'.
         You might want to install the `Automake' and `Perl' packages.
         Grab them from any GNU archive site.
aclocal.m4:20: warning: this file was generated for autoconf 2.63.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.
configure.ac:4: error: Autoconf version 2.61 or higher is required
configure.ac:4: the top level
autom4te: /usr/bin/m4 failed with exit status: 63
WARNING: `autoconf' is probably too old.  You should only need it if
         you modified `configure.ac'.  You might want to install the
         `Autoconf' and `GNU m4' packages.  Grab them from any GNU
         archive site.
/bin/sh ./config.status --recheck
running CONFIG_SHELL=/bin/sh /bin/sh ./configure --prefix=/usr --libdir=/usr/lib64 --enable-gnutls --enable-snmp --enable-relp --enable-imfile --enable-imtemplate --enable-mysql --enable-mail --no-create --no-recursion


So a new configure has made, but it seems this doesn't change the result.

Rsyslog works:

Code: Select all
rsyslogd 3.22.0, compiled with:
        FEATURE_REGEXP:                         Yes
        FEATURE_LARGEFILE:                      Yes
        FEATURE_NETZIP (message compression):   Yes
        GSSAPI Kerberos 5 support:              No
        FEATURE_DEBUG (debug build, slow code): No
        Atomic operations supported:            Yes
        Runtime Instrumentation (slow code):    No


This is all... I don't see problems.

Regards
marco
flaco
Avarage
 
Posts: 18
Joined: Thu Sep 20, 2007 10:23 am

Google Ads



Return to Installation

Who is online

Users browsing this forum: No registered users and 0 guests

cron