LoadModule weblogic_module */lib/mod_wl_24.so - apache

I have a problem with Apache/2.4.17 (Unix) and the weblogic module (plugin) mod_wl_24.so
For this project I have used the httpd_vhosts.conf configuration under the extra directory (that I have enabled before in httpd.conf whith "Include conf/extra/httpd-vhosts.conf") and i have keep the default configurations in httpd.conf
I'm on arch-linux, but i think this is not relevant...
I download the right version of WL plugin and i had put the WLSPlugin12.2.1-Apache2.2-Apache2.4-Linux_x86_64-12.2.1.0.0 directory under the ServerRoot of apache:
/etc/httpd
drwxr-xr-x 4 root root 4096 4 dic 18.24 .
drwxr-xr-x 100 root root 12288 9 dic 09.57 ..
drwxr-xr-x 5 root root 4096 9 dic 11.02 conf
lrwxrwxrwx 1 root root 22 11 nov 17.33 modules -> /usr/lib/httpd/modules
drwxr-xr-x 5 root root 4096 4 dic 12.48 WLSPlugin12.2.1-Apache2.2-Apache2.4-Linux_x86_64-12.2.1.0.0
when I configure the httpd_vhosts.conf in extra directory of apache for load the plugin:
LoadModule weblogic_module WLSPlugin12.2.1-Apache2.2-Apache2.4-Linux_x86_64-12.2.1.0.0/lib/mod_wl_24.so
and after restart apache, I receive this error:
systemctl status httpd -l
● httpd.service - Apache Web Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since mer 2015-12-09 11:14:06 CET; 2h 23min ago
Process: 4231 ExecStop=/usr/bin/apachectl graceful-stop (code=exited, status=1/FAILURE)
Process: 4211 ExecStart=/usr/bin/apachectl start -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 4211 (code=exited, status=1/FAILURE)
dic 09 11:14:06 lollo-sorint systemd[1]: Stopped Apache Web Server.
dic 09 11:14:06 lollo-sorint systemd[1]: Started Apache Web Server.
dic 09 11:14:06 lollo-sorint apachectl[4211]: httpd: Syntax error on line 499 of /etc/httpd/conf/httpd.conf: Syntax error on line 26 of /etc/httpd/conf/extra/httpd-vhosts.conf: Cannot load WLSPlugin12.2.1-Apache2.2-Apache2.4-Linux_x86_64-12.2.1.0.0/lib/mod_wl_24.so into server: libopmnsecure.so: cannot open shared object file: No such file or directory
dic 09 11:14:06 lollo-sorint systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
dic 09 11:14:06 lollo-sorint apachectl[4231]: httpd: Syntax error on line 499 of /etc/httpd/conf/httpd.conf: Syntax error on line 26 of /etc/httpd/conf/extra/httpd-vhosts.conf: Cannot load WLSPlugin12.2.1-Apache2.2-Apache2.4-Linux_x86_64-12.2.1.0.0/lib/mod_wl_24.so into server: libopmnsecure.so: cannot open shared object file: No such file or directory
dic 09 11:14:06 lollo-sorint systemd[1]: httpd.service: Control process exited, code=exited status=1
dic 09 11:14:06 lollo-sorint systemd[1]: httpd.service: Unit entered failed state.
dic 09 11:14:06 lollo-sorint systemd[1]: httpd.service: Failed with result 'exit-code'.
I have correctly set the LD_LIBRARY_PATH on system for the lib directory of mod_wl_24.so:
ls -lrta WLSPlugin12.2.1-Apache2.2-Apache2.4-Linux_x86_64-12.2.1.0.0/lib/
-rwxr-x--- 1 root root 552424 6 ott 07.59 mod_wl.so
-rwxr-x--- 1 root root 553554 6 ott 07.59 mod_wl_24.so
-rwxr-x--- 1 root root 10535697 6 ott 07.59 libnnz11.so
-rwxr-x--- 1 root root 85909 6 ott 07.59 libopmnsecure.so
-rwxr-x--- 1 root root 67967 6 ott 07.59 libonssys.so
-rwxr-x--- 1 root root 326469 6 ott 07.59 libdms2.so
-rwxr-x--- 1 root root 52761218 6 ott 07.59 libclntsh.so
drwxr-xr-x 5 root root 4096 4 dic 12.48 ..
drwxr-xr-x 2 root root 4096 4 dic 17.15 .
env
LD_LIBRARY_PATH=/etc/httpd/WLSPlugin12.2.1-Apache2.2-Apache2.4-Linux_x86_64-12.2.1.0.0/lib
ldd WLSPlugin12.2.1-Apache2.2-Apache2.4-Linux_x86_64-12.2.1.0.0/lib/mod_wl_24.so
linux-vdso.so.1 (0x00007ffd173fb000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007fe6f4178000)
libopmnsecure.so => /etc/httpd/WLSPlugin12.2.1-Apache2.2-Apache2.4-Linux_x86_64-12.2.1.0.0/lib/libopmnsecure.so (0x00007fe6f3f68000)
libonssys.so => /etc/httpd/WLSPlugin12.2.1-Apache2.2-Apache2.4-Linux_x86_64-12.2.1.0.0/lib/libonssys.so (0x00007fe6f3d5a000)
libdms2.so => /etc/httpd/WLSPlugin12.2.1-Apache2.2-Apache2.4-Linux_x86_64-12.2.1.0.0/lib/libdms2.so (0x00007fe6f3b19000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007fe6f381b000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007fe6f3604000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007fe6f3260000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007fe6f305c000)
/usr/lib64/ld-linux-x86-64.so.2 (0x0000563b8fd02000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007fe6f2e3e000)
librt.so.1 => /usr/lib/librt.so.1 (0x00007fe6f2c36000)
So, libopmnsecure.so lib is defined and elaborate from system...
I'm little desperate because i can not find a logical explanation for that...
anyone had that such problem before? Any little help would be grateful :)

I have similar issue with Red Hat RHEL7 and apache 2.4.
For this kind of error
Cannot load .../lib/mod_wl_24.so into server: libonssys.so: cannot open shared object file: No such file or directory
Library libonssys.so is given with weblogic httpd module.
under
/etc/ld.so.conf.d/
create a file pluginWeblogic.conf valued with pathToWeblogicPlugin/lib
for this example valued file pluginWeblogic.conf with
/etc/httpd/WLSPlugin12.2.1-Apache2.2-Apache2.4-Linux_x86_64-12.2.1.0.0/lib
and on shell run :
ldconfig
then restart apache :
systemctl restart httpd

Review the following file:
cat /usr/lib/systemd/system/httpd.service
Under [Service] it specifies the EnvironmentFile=/etc/sysconfig/httpd
Update the file /etc/sysconfig/httpd with the LD_LIBRARY_PATH to the Weblogic Plugin
vi /etc/sysconfig/httpd
# Update to include Weblogic Plugin
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/PATH/weblogic-plugins/lib
#
Restart Apache
systemctl stop httpd.service ;
systemctl start httpd.service ;
systemctl status httpd.service

I have found the problem,
The new system control "systemd" don't load the ENV LD_LIBRARY_PATH when i use the "systemctl restart httpd" command... i don't know why, but is clearly, because if i restart the apache with "apachectl restart" the mod_weblogic is load correctly
i hope this help anybody have this problem

There's no need to set the LD_LIBRARY_PATH. You can simply update the LD_LIBRARY_PATH by copying the 'lib' contents to /usr/lib or /usr/lib64

I might be late but I think someone might be helped by the struggle and how it got fixed.
My environment:
Apache/2.4.41
Ubuntu 20.04.3 LTS
Oracle plugin: mod_wl_24.so
The plugins were placed in the path
/usr/lib/apache2/modules
I added the file "weblogic.load" in apache's mods_available path
echo LoadModule weblogic_module /usr/lib/apache2/modules/mod_wl_24.so > /etc/apache2/mods-available/weblogic.load
Starting apache was failing with the below error
/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/weblogic.load: Cannot load /usr/lib/apache2/modules/mod_wl_24.so into
Resolution
export LD_LIBRARY_PATH=/usr/lib/apache2/modules
cd /etc/ld.so.conf.d
echo /usr/lib/apache2/modules > wlsplugin.conf
ldconfig
apachectl start

Related

Failed to start The Apache HTTP Server after uninstalling and reinstalling apache2 on Raspbian

I uninstalled apache, php, mysql, proftpd, wordpress, cerbot and letsencrypt to get a new, fresh install of apache.
After uninstalling all packages and reinstalling apache, i got this error:
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
invoke-rc.d: initscript apache2, action "restart" failed.
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2021-08-28 15:46:46 CEST; 23ms ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 10693 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
Aug 28 15:46:46 raspberrypi systemd[1]: Starting The Apache HTTP Server...
Aug 28 15:46:46 raspberrypi apachectl[10693]: apache2: Syntax error on line 225 of /etc/apache2/apache2.conf: Syntax error on line 33 of /etc/apache2/sites-enabled/000-default-le-ssl.conf: Could not open configuration file /etc/letsencrypt/options-ssl-apache.conf: No such file or directory
Aug 28 15:46:46 raspberrypi apachectl[10693]: Action 'start' failed.
Aug 28 15:46:46 raspberrypi apachectl[10693]: The Apache error log may have more information.
Aug 28 15:46:46 raspberrypi systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
Aug 28 15:46:46 raspberrypi systemd[1]: apache2.service: Failed with result 'exit-code'.
Aug 28 15:46:46 raspberrypi systemd[1]: Failed to start The Apache HTTP Server.
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for systemd (241-7~deb10u8+rpi1) ...
I tried to remove all apache-related packages by
sudo apt-get remove apache2
sudo apt autoremove
but this didn't work either.
You have an typing error on line 225 of file /etc/apache2/apache2.conf
I flashed a new image onto the Pi because I couldn't make it run.

Can't Apache2 start erorr: Can't locate SOAP/Transport/HTTP.pm

I have a problem with apache2 start.
When I try apache start i have the message:
root#ocsi:/var/log/apache2# **systemctl start apache2.service**
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
in systemctl status apache2.service
root#ocsi:/var/log/apache2# systemctl status apache2.service
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-06-01 07:53:07 CEST; 19s ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 3142 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
Jun 01 07:53:07 ocsi systemd[1]: Starting The Apache HTTP Server...
Jun 01 07:53:07 ocsi apachectl[3142]: Action 'start' failed.
Jun 01 07:53:07 ocsi apachectl[3142]: The Apache error log may have more information.
Jun 01 07:53:07 ocsi systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
Jun 01 07:53:07 ocsi systemd[1]: apache2.service: Failed with result 'exit-code'.
Jun 01 07:53:07 ocsi systemd[1]: Failed to start The Apache HTTP Server.
in journalctl -xe
root#ocsi:/var/log/apache2# journalctl -xe
Jun 01 07:54:31 ocsi multipathd[700]: sda: add missing path
Jun 01 07:54:31 ocsi multipathd[700]: sda: failed to get udev uid: Invalid argument
Jun 01 07:54:31 ocsi multipathd[700]: sda: failed to get sysfs uid: Invalid argument
Jun 01 07:54:31 ocsi multipathd[700]: sda: failed to get sgio uid: No such file or directory
and in apache2 log is:
root#ocsi:/var/log/apache2# vi error.log
[Mon Jun 01 07:53:07.305344 2020] [perl:error] [pid 3149] Can't locate SOAP/Transport/HTTP.pm in #INC (you may need to install the SOAP::Transport::HTTP module) (#INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /etc/apache2) at /usr/local/share/perl/5.30.0/Apache/Ocsinventory/Plugins/Apache.pm line 25.\nBEGIN failed--compilation aborted at /usr/local/share/perl/5.30.0/Apache/Ocsinventory/Plugins/Apache.pm line 25.\nCompilation failed in require at (eval 16) line 1.\n
[Mon Jun 01 07:53:07.305621 2020] [perl:error] [pid 3149] Can't load Perl module Apache::Ocsinventory::Plugins::Apache for server localhost:0, exiting...
My system:
PHP Version : 7.4.3
Server version: Apache/2.4.41 (Ubuntu)
Description: Ubuntu 20.04 LTS
Ubuntu Linux 5.4.0-33-generic x86_64
How can I fix this error?
Looks like you need to install the SOAP::Lite module. That can be done by running:
$ sudo apt-get install libsoap-lite-perl
For more details, read on.
The error message is telling you that the Perl compiler can't find the module SOAP::Transport::HTTP (which is presumably used in some code used in your Apache start-up).
This module has never been part of a standard Perl distribution (you can test that by running corelist SOAP::Transport::HTTP). It, therefore, needs to be installed separately.
Perl modules are usually installed from CPAN. If you search for the module there, you'll see it's part of the SOAP-Lite distribution. Now you could install it directly from there using cpan but, given in this case, the easier approach is probably to install the pre-built package for your operating system. And that's done by running the command above.

apache2.service: Control process exited, code=exited status=139

I install apache2 on ubuntu 18.04. This is fresh install with all default configuration.
I tried to start apache2 but failed. And this is what I see.
# systemctl status apache2.service
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: failed (Result: exit-code) since Wed 2020-03-11 23:17:35 WIB; 13s ago
Process: 9151 ExecStart=/usr/sbin/apachectl start (code=exited, status=139)
Mar 11 23:17:35 xdn.id systemd[1]: Starting The Apache HTTP Server...
Mar 11 23:17:35 xdn.id apachectl[9151]: Segmentation fault
Mar 11 23:17:35 xdn.id apachectl[9151]: Action 'start' failed.
Mar 11 23:17:35 xdn.id apachectl[9151]: The Apache error log may have more information.
Mar 11 23:17:35 xdn.id systemd[1]: apache2.service: Control process exited, code=exited status=139
Mar 11 23:17:35 xdn.id systemd[1]: apache2.service: Failed with result 'exit-code'.
Mar 11 23:17:35 xdn.id systemd[1]: Failed to start The Apache HTTP Server.
When I check /var/log/apache2/error.log, there is empty.
What's wrong with this error?
The "status=139" error must have something to do with having multiple, conflicting versions of PHP enabled.
I am running 18.04 and an old PHP site I run only locally ceased to work. I am guessing aptitude installed and enabled php7.2, possibly when I installed kubuntu-desktop a few weeks back.
Regardless, I had two versions of PHP enabled:
$ cd /etc/apache2/
$ l mods-*/php*
-rw-r--r-- 1 root root 867 Jun 9 2017 mods-available/php5.6.conf
-rw-r--r-- 1 root root 102 Jun 9 2017 mods-available/php5.6.load
-rw-r--r-- 1 root root 867 Mar 2 2017 mods-available/php7.0.conf
-rw-r--r-- 1 root root 102 Oct 1 2018 mods-available/php7.0.load
-rw-r--r-- 1 root root 855 Jul 7 2017 mods-available/php7.1.conf
-rw-r--r-- 1 root root 102 Jul 7 2017 mods-available/php7.1.load
-rw-r--r-- 1 root root 855 Feb 8 2019 mods-available/php7.2.conf
-rw-r--r-- 1 root root 102 Feb 8 2019 mods-available/php7.2.load
lrwxrwxrwx 1 root root 29 Jul 1 2017 mods-enabled/php5.6.conf -> ../mods-available/php5.6.conf
lrwxrwxrwx 1 root root 29 Jul 1 2017 mods-enabled/php5.6.load -> ../mods-available/php5.6.load
lrwxrwxrwx 1 root root 29 May 28 06:05 mods-enabled/php7.2.conf -> ../mods-available/php7.2.conf
lrwxrwxrwx 1 root root 29 May 28 06:05 mods-enabled/php7.2.load -> ../mods-available/php7.2.load
In my case, I am fine with using php5.6, because the site is not online and is purely for my local use only. So disabling 7.2 did the trick:
sudo a2dismod php7.2
Now my php mods-enabled are less confusing to apache3:
$ l mods-*/php*
-rw-r--r-- 1 root root 867 Jun 9 2017 mods-available/php5.6.conf
-rw-r--r-- 1 root root 102 Jun 9 2017 mods-available/php5.6.load
-rw-r--r-- 1 root root 867 Mar 2 2017 mods-available/php7.0.conf
-rw-r--r-- 1 root root 102 Oct 1 2018 mods-available/php7.0.load
-rw-r--r-- 1 root root 855 Jul 7 2017 mods-available/php7.1.conf
-rw-r--r-- 1 root root 102 Jul 7 2017 mods-available/php7.1.load
-rw-r--r-- 1 root root 855 Feb 8 2019 mods-available/php7.2.conf
-rw-r--r-- 1 root root 102 Feb 8 2019 mods-available/php7.2.load
lrwxrwxrwx 1 root root 29 Jul 1 2017 mods-enabled/php5.6.conf -> ../mods-available/php5.6.conf
lrwxrwxrwx 1 root root 29 Jul 1 2017 mods-enabled/php5.6.load -> ../mods-available/php5.6.load
Naturally for a live site one would want to disable php-5.6 and leave the php7.2 enabled, because you should run the newer version in real life.
sudo a2dismod php5.6
sudo a2enmod php7.2
Then the php mods should look like this:
$ l mods-*/php*
-rw-r--r-- 1 root root 867 Jun 9 2017 mods-available/php5.6.conf
-rw-r--r-- 1 root root 102 Jun 9 2017 mods-available/php5.6.load
-rw-r--r-- 1 root root 867 Mar 2 2017 mods-available/php7.0.conf
-rw-r--r-- 1 root root 102 Oct 1 2018 mods-available/php7.0.load
-rw-r--r-- 1 root root 855 Jul 7 2017 mods-available/php7.1.conf
-rw-r--r-- 1 root root 102 Jul 7 2017 mods-available/php7.1.load
-rw-r--r-- 1 root root 855 Feb 8 2019 mods-available/php7.2.conf
-rw-r--r-- 1 root root 102 Feb 8 2019 mods-available/php7.2.load
lrwxrwxrwx 1 root root 29 May 29 17:43 mods-enabled/php7.2.conf -> ../mods-available/php7.2.conf
lrwxrwxrwx 1 root root 29 May 29 17:43 mods-enabled/php7.2.load -> ../mods-available/php7.2.load
Don't forget to resatart the server!
systemctl restart apache2
Thanks to Pavel's comment for inspiring this line of research!
I got this error and I fixed it by enabling PHP version 8.0 (current stable) and disabling PHP version 7.4 (old) in my ubuntu 20.04 by these commands:
sudo a2dismod php7.4
sudo a2enmod php8.0
sudo service apache2 restart
After doing these check your apache status by:
sudo systemctl status apache2.service
It has to be green and must show you active (running).
NOTE: You can do this to any PHP version that you have and want to
change.

RabbitMQ not starting with message "init terminating in do_boot, noproc" on Ubuntu 18.04

I cannot seem to start or install my RabbitMQ server anymore for my Ubuntu 18.04 anymore. I tried to remove and install it again, but it cannot finish the install because configuration fails. When I try to run sudo apt-get install --fix-broken. This is the result of it failing:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 61 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up rabbitmq-server (3.6.10-1) ...
Job for rabbitmq-server.service failed because the control process exited with error code.
See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details.
invoke-rc.d: initscript rabbitmq-server, action "start" failed.
● rabbitmq-server.service - RabbitMQ Messaging Server
Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2018-08-22 09:16:51 EEST; 5ms ago
Process: 20997 ExecStartPost=/usr/lib/rabbitmq/bin/rabbitmq-server-wait (code=exited, status=70)
Process: 20996 ExecStart=/usr/sbin/rabbitmq-server (code=exited, status=0/SUCCESS)
Main PID: 20996 (code=exited, status=0/SUCCESS)
elo 22 09:16:48 ubuntu-dev systemd[1]: Starting RabbitMQ Messaging Server...
elo 22 09:16:49 ubuntu-dev rabbitmq[20997]: Waiting for 'rabbit#ubuntu-dev'
elo 22 09:16:49 ubuntu-dev rabbitmq[20997]: pid is 21001
elo 22 09:16:51 ubuntu-dev rabbitmq[20997]: Error: process_not_running
elo 22 09:16:51 ubuntu-dev systemd[1]: rabbitmq-server.service: Control process exited, code=exited status=70
elo 22 09:16:51 ubuntu-dev systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'.
elo 22 09:16:51 ubuntu-dev systemd[1]: Failed to start RabbitMQ Messaging Server.
dpkg: error processing package rabbitmq-server (--configure):
installed rabbitmq-server package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
rabbitmq-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
Then when checking the log files they doesn't provide much more information either. Here is startup_err log file content:
init terminating in do_boot (noproc)
Crash dump is being written to: erl_crash.dump...done'
And here is startup_log file content:
BOOT FAILED
===========
Error description:
noproc
Log files (may contain more information):
/var/log/rabbitmq/rabbit.log
/var/log/rabbitmq/rabbit-sasl.log
Stack trace:
[{gen,do_for_proc,2,[{file,"gen.erl"},{line,228}]},
{gen_event,rpc,2,[{file,"gen_event.erl"},{line,239}]},
{rabbit,ensure_working_log_handlers,0,
[{file,"src/rabbit.erl"},{line,842}]},
{rabbit,'-boot/0-fun-0-',0,[{file,"src/rabbit.erl"},{line,281}]},
{rabbit,start_it,1,[{file,"src/rabbit.erl"},{line,417}]},
{init,start_em,1,[]},
{init,do_boot,3,[]}]
=INFO REPORT==== 22-Aug-2018::09:16:49.691453 ===
Error description:
noproc
Log files (may contain more information):
/var/log/rabbitmq/rabbit.log
/var/log/rabbitmq/rabbit-sasl.log
Stack trace:
[{gen,do_for_proc,2,[{file,"gen.erl"},{line,228}]},
{gen_event,rpc,2,[{file,"gen_event.erl"},{line,239}]},
{rabbit,ensure_working_log_handlers,0,
[{file,"src/rabbit.erl"},{line,842}]},
{rabbit,'-boot/0-fun-0-',0,[{file,"src/rabbit.erl"},{line,281}]},
{rabbit,start_it,1,[{file,"src/rabbit.erl"},{line,417}]},
{init,start_em,1,[]},
{init,do_boot,3,[]}]
{"init terminating in do_boot",noproc}
The other log files it claim to use for logging are empty. For example log file rabbit#ubuntu-dev.log and rabbit#ubuntu-dev-sasl.log.
I also found this post, which explains to check your hostname in /etc/hostname file but I checked and it's correct.
kazhu#ubuntu-dev:/var/log/rabbitmq$ cat /etc/hostname
ubuntu-dev
I also checked RabbitMQ troubleshoot guide and they said to check log folder permissions and they are right to my eye:
kazhu#ubuntu-dev:/var/log/rabbitmq$ ll
total 48
drwxr-xr-x 2 rabbitmq rabbitmq 4096 kesä 14 06:16 ./
drwxrwxr-x 16 root syslog 4096 elo 22 00:09 ../
-rw-r--r-- 1 rabbitmq rabbitmq 0 kesä 14 06:16 'rabbit#ubuntu-dev.log'
-rw-r--r-- 1 rabbitmq rabbitmq 5247 kesä 14 06:16 'rabbit#ubuntu-dev.log.1'
-rw-r--r-- 1 rabbitmq rabbitmq 954 touko 28 08:36 'rabbit#ubuntu-dev.log.2.gz'
-rw-r--r-- 1 rabbitmq rabbitmq 768 touko 21 07:11 'rabbit#ubuntu-dev.log.3.gz'
-rw-r--r-- 1 rabbitmq rabbitmq 708 touko 16 00:12 'rabbit#ubuntu-dev.log.4.gz'
-rw-r--r-- 1 rabbitmq rabbitmq 955 touko 7 07:26 'rabbit#ubuntu-dev.log.5.gz'
-rw-r--r-- 1 rabbitmq rabbitmq 4264 huhti 22 00:07 'rabbit#ubuntu-dev.log.6.gz'
-rw-r--r-- 1 rabbitmq rabbitmq 0 huhti 17 15:58 'rabbit#ubuntu-dev-sasl.log'
-rw-r--r-- 1 rabbitmq rabbitmq 95 elo 22 09:16 startup_err
-rw-r--r-- 1 rabbitmq rabbitmq 1212 elo 22 09:16 startup_log
Guide also stated that perl chrash dump file contains detailed information of the problem and requires Erlang expertises, which I don't have. So decided to upload the file to my Dropbox for you to see.
Can somebody help me solve this? I've tried some time myself but gave up because cannot figure out what the problem seems to be :/
I solved the problem with help of my colleague. I had installed newest erlang and rabbitmq from outside apt source separately. Now when I removed and purged everything related to rabbitmq and erlang, and removed the added apt sources too. Then I just ran sudo apt install rabbitmq-server and it wanted to install erlang packages too because of the dependency. And it installed and everything is working fine after that.
Wanted to share this solution if somebody else has the same problem as me.
UPDATE 9.12.2020:
Someone asked how I removed RabbitMQ and Erlang. I don't fully remember but I think I was following this guide: https://www.rabbitmq.com/install-debian.html.
The point is to remove the installed RabbitMQ and Erlang packages from added repositories and their configuration with
sudo apt purge rabbitmq-server erlang
You might need to search for rest of the erlang packages with
apt list | grep erlang
Then you need to remove added apt repositories. Usually added repositories in Ubuntu goes under /etc/apt/sources.list.d/ folder. Look for files names like rabbitmq and erlang. Make sure you are not deleting any other files!
After this run sudo apt update and apt should remove removed apt repositories. Then just running sudo apt install rabbitmq-server should do the trick and install Erlang package as a dependence. Of course installing this way you get much older version than using added repositories.

Apache 2.4.10 rotatelogs not able to open log file : no such file or directory error

I have apache 2.4.10 running . I tried to setup rotatelogs but haven'nt been able to . I was supposed to be a straightforward implementation .
Error which i am getitng is :
(2)No such file or directory: AH00104: unable to start piped log program 'bin/rotatelogs -v /opt/apache/http-ocfd1//logs/access_log 5'
[Mon Mar 16 09:44:53.965524 2015] [:emerg] [pid 7669:tid
140328321083136] AH00019: Unable to open logs, exiting
Rotation time interval: 60
Rotation size interval: 0
Rotation time UTC offset: 0
Rotation based on localtime: no
Rotation file date pattern: no
Rotation file forced open: no
Rotation verbose: yes
Rotation create empty logs: no
Rotation file name: /opt/apache/http-ocfd1/logs/access_log
Post-rotation prog: (null)
(2)No such file or directory: AH00104: unable to start piped log program 'bin/rotatelogs -v /opt/apache/http-ocfd1/logs/access_log 5'
[Mon Mar 16 09:44:55.515173 2015] [:emerg] [pid 7675:tid 140566727632640] AH00019: Unable to open logs, exiting
(
i have set rotattion time for 60 seconds just for testing purpose .
Additional information :
*Access log does create at /opt/apache/http-ocfd1/logs/access_log and this file exist .
I am running my server with root user
I tried doing ls -ltr to this file .
I also tried to give full paths to log file .
I am not sure why rotatelogs command is not able to locate access_log file ??
Any help would be great ! :)