[SOLVED] LFS + Chroot on Grsec kernel + Apache = fail

fmillion · 12-01-2010, 09:23 PM

I have compiled an LFS tree that I wish to run on a friend's box who is going to host for me. He is running kernel 2.6.19 with Grsecurity. I did not have a Grsec kernel on the source box (the one I compiled the LFS on) and I am not sure if this is the problem in and of itself.

In any case, I tried to run Apache on his box (after chrooting into the environment) and got the following message:

Code:

[root@host] /home/fmillion # chroot lfs_environment /bin/bash -l
[root@host) /root # cd /home/www/apache/bin
[root@host] /home/www/apache/bin # ./apachectl start
[Thu Dec 02 03:21:12 2010] [crit] (22)Invalid argument: alloc_listener: failed to get a socket for x.x.x.x
Syntax error on line 41 of /home/www/apache/conf/httpd.conf:
Listen setup failed
[root@host] /home/www/apache/bin #

(Note, the x.x.x.x is the actual IP on which Apache will be listening. IT is not "(null)" as I've seen on other posts related to this issue.)

Line 41 simply reads:

Code:

Listen x.x.x.x:80

(again, x.x.x.x is the real IP)

I've heard this has to do with APR not being able to make certain kernel calls. As I'm not highly familiar with Grsec, can I 1) assume that this is the root of the problem and 2) fix it somehow without having to ask my friend to change his setup, or redo an entire LFS with Grsec or something?

Simpler apps (nc for example) run fine and can open listening sockets and receive on them. This problem appears specific to Apache, and possibly may also include other daemons (but I haven't tried other ones yet.)

Advice greatly appreciated.

Thanks

FM

slimm609 · 12-02-2010, 09:59 PM

see here. Its the same issue as stated in my other post.

http://www.linuxquestions.org/questi...6/#post4179015

fmillion · 12-03-2010, 09:49 AM

I figured out that it has to do with the fact that the kernel on the destination system is different than the one on the build system. The destination system's kernel is older and lacks some kernel features needed. I was able to find a post with some Configure variables that will solve the problem.

That problem is solved, and I used my build system to recompile Apache, and transferred it up to the production system and it worked.We're still faced with the other issue on this same box though:

http://www.linuxquestions.org/questi...d.php?t=848016

Thanks

fm