/usr/local/lib/rsyslog/omrelp.so: cannot open shared object

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

Moderator: rgerhards

Google Ads


/usr/local/lib/rsyslog/omrelp.so: cannot open shared object

Postby adimitrov » Wed Dec 14, 2016 4:33 pm

Hello team,

I am new to this forum and i am using rsyslog for 1-2 months now without any issues and i am really satisfied. Unfortunately the time has come. I am using:

root@enmc:~# rsyslogd -version
rsyslogd 8.23.0, compiled with:
PLATFORM: x86_64-pc-linux-gnu
PLATFORM (lsb_release -d): Description: Ubuntu 16.04.1 LTS
FEATURE_REGEXP: Yes
GSSAPI Kerberos 5 support: No
FEATURE_DEBUG (debug build, slow code): No
32bit Atomic operations supported: Yes
64bit Atomic operations supported: Yes
memory allocator: system default
Runtime Instrumentation (slow code): No
uuid support: Yes
Number of Bits in RainerScript integers: 64

See http://www.rsyslog.com for more information.

For several machines (all of them Ubuntu 16.04.1 LTS) i have installed and it is working fine and collecting without any issues. On one of the machines (fresh installation), i have this:

root@enmc:~# service rsyslog status
● rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2016-12-14 16:28:15 EET; 44min ago
Docs: man:rsyslogd(8)
http://www.rsyslog.com/doc/
Main PID: 3250 (rsyslogd)
Tasks: 5
Memory: 640.0K
CPU: 5ms
CGroup: /system.slice/rsyslog.service
└─3250 /usr/local/sbin/rsyslogd -n

Dec 14 16:28:15 enmc systemd[1]: Stopped System Logging Service.
Dec 14 16:28:15 enmc systemd[1]: Starting System Logging Service...
Dec 14 16:28:15 enmc liblogging-stdlog[3250]: [origin software="rsyslogd" swVersion="8.23.0" x-pid="3250" x-info="http://www.rsyslog.com"] start
Dec 14 16:28:15 enmc liblogging-stdlog[3250]: could not load module '/usr/local/lib/rsyslog/omrelp.so', dlopen: /usr/local/lib/rsyslog/omrelp.so: cannot open shared obj
Dec 14 16:28:15 enmc liblogging-stdlog[3250]: module name 'omrelp' is unknown [v8.23.0 try http://www.rsyslog.com/e/2209 ]
Dec 14 16:28:15 enmc liblogging-stdlog[3250]: error during parsing file /etc/rsyslog.conf, on or before line 22: errors occured in file '/etc/rsyslog.conf' around line
Dec 14 16:28:15 enmc liblogging-stdlog[3250]: could not load module '/usr/local/lib/rsyslog/pmciscoios.so', dlopen: /usr/local/lib/rsyslog/pmciscoios.so: cannot open sh
Dec 14 16:28:15 enmc liblogging-stdlog[3250]: $WorkDirectory: /var/spool/rsyslog can not be accessed, probably does not exist - directive ignored [v8.23.0 try http://ww
Dec 14 16:28:15 enmc systemd[1]: Started System Logging Service.

I check the rsyslog.conf file and it is the same as the others on the other machines. Interesting thing is that omrelp.so does not exist on the machine. I tried to install librelp manually, but the situation is the same. So my question is if i can download manually the needed modules from somewhere and why is this happening. I am using the same procedure every time on totally identical machines and only this one "spits on me". Is it possible that the configure script is not creating the modules and why? Is there a way to remove totally the rsyslog installation and configure it from the zero?

I am installing if from tarball downloaded from the official page. all the requirements are met.

Best Regards,
Adrian
adimitrov
New
 
Posts: 4
Joined: Thu Dec 08, 2016 4:57 pm

Urgent Question?

  • Pulling out your Hair?
  • Wasting Time and Money?
  • Deadline Approaching?

Re: /usr/local/lib/rsyslog/omrelp.so: cannot open shared obj

Postby dlang » Wed Dec 14, 2016 10:49 pm

you are probably missing the rsyslog-relp package on that system

dpkg -l |grep rsyslog

look at what packages are installed on the various systems.
dlang
Frequent Poster
 
Posts: 1001
Joined: Mon Sep 15, 2008 7:44 am

Re: /usr/local/lib/rsyslog/omrelp.so: cannot open shared obj

Postby adimitrov » Thu Dec 15, 2016 8:45 am

Hello ,

Yes they are missing for sure, not only the rsyslog-relp package. The output from dpkg -l | grep rsyslog is empty from the problematic machines. For all others the output is:

root@orwhosyslog1:~# dpkg -l |grep rsyslog
ii rsyslog 8.4.2-1+deb8u2 amd64 reliable system and kernel logging daemon
ii rsyslog-gnutls 8.4.2-1+deb8u2 amd64 TLS protocol support for rsyslog
ii rsyslog-relp 8.4.2-1+deb8u2 amd64 RELP protocol support for rsyslog

From where i can donwload the packages and install them manually, would this help and why "configure" script didn't install the packages. How can i avoid such issues in the future ?
adimitrov
New
 
Posts: 4
Joined: Thu Dec 08, 2016 4:57 pm

Re: /usr/local/lib/rsyslog/omrelp.so: cannot open shared obj

Postby rgerhards » Thu Dec 15, 2016 9:46 am

As you mention ./configure, which looks like you build from source: how is your complete install procedure?
rgerhards
Site Admin
 
Posts: 3807
Joined: Thu Feb 13, 2003 11:57 am

Re: /usr/local/lib/rsyslog/omrelp.so: cannot open shared obj

Postby adimitrov » Thu Dec 15, 2016 10:29 am

Here it is:

Update the system
apt-get update

Download all the prerequisites
apt-get install gcc -y
apt-get install make -y
apt-get install libtool -y

apt-get install python-docutils -y
which rst2man

apt-get install bison -y
apt-get install flex -y

apt-get install zlib1g-dev -y
apt-get install libjson0 libjson0-dev -y

apt-get install uuid-dev -y // (libuuid)
apt-get install libgcrypt-dev -y

apt-get install liblogging-stdlog-dev -y
apt-get install libestr-dev -y

apt-get install pkg-config -y

wget http://download.rsyslog.com/libfastjson ... 9.3.tar.gz
tar -zxvf libfastjson-0.99.3.tar.gz
cd libfastjson-0.99.3
./configure
make
make install

wget http://www.rsyslog.com/files/download/r ... 3.0.tar.gz
tar -zxvf rsyslog-8.23.0.tar.gz
cd rsyslog-8.23.0
./configure
make
make install

Everything went smooth, in this case i even downlaoded librelp and build it with confiure script -> make -> make install.

Best Regards,
Adrian
adimitrov
New
 
Posts: 4
Joined: Thu Dec 08, 2016 4:57 pm

Re: /usr/local/lib/rsyslog/omrelp.so: cannot open shared obj

Postby dlang » Fri Dec 16, 2016 10:46 am

Ok, the process you are using does not create any packages, you install the software, but it's invisible to the packaging system.

I'll try to dig up the instructions that I used to build packages that I could then use in ubuntu, but in the meantime..

if you look at the output of configure and make, you will see that it lists what features it supports down towards the bottom. You will find that relp is not amoung the features included in your build. Besides installing the librelp package (and probably librelp-dev) you will also need to enable using it in your config call.
dlang
Frequent Poster
 
Posts: 1001
Joined: Mon Sep 15, 2008 7:44 am

Re: /usr/local/lib/rsyslog/omrelp.so: cannot open shared obj

Postby rgerhards » Fri Dec 16, 2016 11:34 am

./configure --help lists all available options.

./configure --enable-relp

will probably build all relp related things. But you for sure need also to adjust the binary and library paths to make sure the custom-build software is installed into the right locations.
rgerhards
Site Admin
 
Posts: 3807
Joined: Thu Feb 13, 2003 11:57 am

Re: /usr/local/lib/rsyslog/omrelp.so: cannot open shared obj

Postby adimitrov » Mon Dec 19, 2016 9:06 am

Hello ,

After checking what are my options with --help i tried the following:

./configure --enable-gnutls --enable-relp --enable-pmcisconames --enable-omrelp-default-port

Nothing changed ... output of dpkg -l |grep rsyslog is still empty.

Best regards,
Adrian
adimitrov
New
 
Posts: 4
Joined: Thu Dec 08, 2016 4:57 pm

Google Ads



Return to Installation

Who is online

Users browsing this forum: No registered users and 0 guests

cron