Re: Need help! Apache core dumps when running startssl
--- Andreas Wider�e Andersen [EMAIL PROTECTED] wrote: Hi, I recently upgraded one of my production servers to FreeBSD 4.11 p19 and then upgraded all ports. I'm now running Apache 1.3.36 mod_ssl and Php 4.4.2 . I had Squirrelmail running on https and now I can't start Apache with ssl. Every time it coredumps. I've tried snakeoil and my own cert. Same thing happens. This is the error message I can see from my httpd-error.log: [Mon Aug 7 20:20:03 2006] [notice] caught SIGTERM, shutting down ssl-engine log: [07/Aug/2006 20:29:01 16880] [info] Server: Apache/1.3.36, Interface: mod_ssl/2.8.27, Library: OpenSSL/0.9.8b [07/Aug/2006 20:29:01 16880] [info] Init: 1st startup round (still not detached) [07/Aug/2006 20:29:01 16880] [info] Init: Initializing OpenSSL library [07/Aug/2006 20:29:01 16880] [info] Init: Loading certificate private key of SSL-aware server my.domain.com:443 [07/Aug/2006 20:29:01 16880] [info] Init: Seeding PRNG with 136 bytes of entropy [07/Aug/2006 20:29:01 16880] [info] Init: Generating temporary RSA private keys (512/1024 bits) from messages: Aug 7 20:34:52 server /kernel: pid 17041 (httpd), uid 0: exited on signal 11 (core dumped) That's it. I can't find any other logs and I can't tell what's wrong. What could it be and what can I do? I have checked the httpd.conf file and compared the previous version with the new dist. Same directives related to ssl virtualhost as far as I can see. Hope to get some input. Looks like ur random seeding is not happening properly. check whether /dev/random and /dev/urandom work properly. You can verify it with the command $openssl rand 512 HTH, Girish Thanks Best regards, Andreas W. Andersen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need help! Apache core dumps when running startssl
On 8/8/06, Girish Venkatachalam [EMAIL PROTECTED] wrote:
--- Andreas Wider�e Andersen [EMAIL PROTECTED]
wrote:
Hi,
I recently upgraded one of my production servers to
FreeBSD 4.11 p19 and
then upgraded all ports. I'm now running Apache
1.3.36 mod_ssl and Php 4.4.2
.
I had Squirrelmail running on https and now I can't
start Apache with ssl.
Every time it coredumps. I've tried snakeoil and my
own cert. Same thing
happens.
This is the error message I can see from my
httpd-error.log:
[Mon Aug 7 20:20:03 2006] [notice] caught SIGTERM,
shutting down
ssl-engine log:
[07/Aug/2006 20:29:01 16880] [info] Server:
Apache/1.3.36, Interface:
mod_ssl/2.8.27, Library: OpenSSL/0.9.8b
[07/Aug/2006 20:29:01 16880] [info] Init: 1st
startup round (still not
detached)
[07/Aug/2006 20:29:01 16880] [info] Init:
Initializing OpenSSL library
[07/Aug/2006 20:29:01 16880] [info] Init: Loading
certificate private key
of SSL-aware server my.domain.com:443
[07/Aug/2006 20:29:01 16880] [info] Init: Seeding
PRNG with 136 bytes of
entropy
[07/Aug/2006 20:29:01 16880] [info] Init:
Generating temporary RSA private
keys (512/1024 bits)
from messages:
Aug 7 20:34:52 server /kernel: pid 17041 (httpd),
uid 0: exited on signal
11 (core dumped)
That's it. I can't find any other logs and I can't
tell what's wrong.
What could it be and what can I do? I have checked
the httpd.conf file and
compared the previous version with the new dist.
Same directives related to
ssl virtualhost as far as I can see.
Hope to get some input.
Looks like ur random seeding is not happening
properly. check whether /dev/random and /dev/urandom
work properly. You can verify it with the command
$openssl rand 512
HTH,
Girish
Thanks for your reply. This just gave me a lot of garbage on the screen.
Ie, like this:
¿Ð3•Éšï¼–|¥¾WpŒÞÐàvC~
jþ‚vzü¼ùµÒ¼}$(c)swüg;€ñ¿gé¶ïa°(c)éå4|C—(c)\Î
}™v=Ãñ5Î×%âÔÙZ`,BÜÃT‰‹þBŒv´ýh£ÙlõKkòä2ZüìÊg{åVµ±ü3`BɦÁ(›¤2çyõû12ÿNº9Å—ùèkÒ™ºß…¼'—ú
...
Rgds,
Andreas
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need help! Apache core dumps when running startssl
--- Andreas Wider�e Andersen [EMAIL PROTECTED]
wrote:
On 8/8/06, Girish Venkatachalam
[EMAIL PROTECTED] wrote:
--- Andreas Wider�e Andersen [EMAIL PROTECTED]
wrote:
Hi,
I recently upgraded one of my production servers
to
FreeBSD 4.11 p19 and
then upgraded all ports. I'm now running Apache
1.3.36 mod_ssl and Php 4.4.2
.
I had Squirrelmail running on https and now I
can't
start Apache with ssl.
Every time it coredumps. I've tried snakeoil and
my
own cert. Same thing
happens.
This is the error message I can see from my
httpd-error.log:
[Mon Aug 7 20:20:03 2006] [notice] caught
SIGTERM,
shutting down
ssl-engine log:
[07/Aug/2006 20:29:01 16880] [info] Server:
Apache/1.3.36, Interface:
mod_ssl/2.8.27, Library: OpenSSL/0.9.8b
[07/Aug/2006 20:29:01 16880] [info] Init: 1st
startup round (still not
detached)
[07/Aug/2006 20:29:01 16880] [info] Init:
Initializing OpenSSL library
[07/Aug/2006 20:29:01 16880] [info] Init:
Loading
certificate private key
of SSL-aware server my.domain.com:443
[07/Aug/2006 20:29:01 16880] [info] Init:
Seeding
PRNG with 136 bytes of
entropy
[07/Aug/2006 20:29:01 16880] [info] Init:
Generating temporary RSA private
keys (512/1024 bits)
from messages:
Aug 7 20:34:52 server /kernel: pid 17041
(httpd),
uid 0: exited on signal
11 (core dumped)
That's it. I can't find any other logs and I
can't
tell what's wrong.
What could it be and what can I do? I have
checked
the httpd.conf file and
compared the previous version with the new dist.
Same directives related to
ssl virtualhost as far as I can see.
Hope to get some input.
Looks like ur random seeding is not happening
properly. check whether /dev/random and
/dev/urandom
work properly. You can verify it with the command
$openssl rand 512
HTH,
Girish
Thanks for your reply. This just gave me a lot of
garbage on the screen.
Ie, like this:
¿Ã3â¢Ãšï¼â|¥¾WpÅÃÃà vCÂ~
jþâvzü¼ùµÃ¼}$(c)swügþâ¬Ã±Â¿gé¶ïa°(c)éå4|Câ(c)\Ã
}â¢v=Ãñ5ÃÃ%âÃÃZ`Â,BÃÃTâ°â¹Ã¾BÅv´ýh£ÃlõKkòä2ZüìÃg{Ã¥Vµ±ü3`BæÃ(âºÂ¤2çyõû12ÿNº9Ã
âùèkÃâ¢ÂºÃâ¦Â¼'âúÂÂ
...
Then that is working properly. I think you can try
this then. Which might also work and I am out of
ideas. :-(
$ openssl genrsa 1024
Rgds,
Andreas
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need help! Apache core dumps when running startssl
Quoting Girish Venkatachalam [EMAIL PROTECTED]: Hope to get some input. Looks like ur random seeding is not happening properly. check whether /dev/random and /dev/urandom work properly. You can verify it with the command $openssl rand 512 Why not just run httpd under gdb, and see WHY it is crashing? gdb httpd httpd.core run -X once cored, just back trace, step, and it should tell you exactly why it is crashing... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need help! Apache core dumps when running startssl
[snip] Then that is working properly. I think you can try this then. Which might also work and I am out of ideas. :-( $ openssl genrsa 1024 # openssl genrsa 1024 Generating RSA private key, 1024 bit long modulus ...++ ...++ e is 65537 (0x10001) -BEGIN RSA PRIVATE KEY- [deleted] -END RSA PRIVATE KEY- Seems fine to me. It generates the key just like it should I think. Cheers, Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need help! Apache core dumps when running startssl
On 8/8/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Quoting Girish Venkatachalam [EMAIL PROTECTED]: Hope to get some input. Looks like ur random seeding is not happening properly. check whether /dev/random and /dev/urandom work properly. You can verify it with the command $openssl rand 512 Why not just run httpd under gdb, and see WHY it is crashing? gdb httpd httpd.core run -X once cored, just back trace, step, and it should tell you exactly why it is crashing... Thanks! How do I start httpd with ssl support from this command? (I do apachectl startssl when Apache crashes. apachectl start works fine though.) Apache runs fine when ssl is NOT started. Thanks, Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need help! Apache core dumps when running startssl
Quoting Andreas Widerøe Andersen [EMAIL PROTECTED]: On 8/8/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Quoting Girish Venkatachalam [EMAIL PROTECTED]: Hope to get some input. Looks like ur random seeding is not happening properly. check whether /dev/random and /dev/urandom work properly. You can verify it with the command $openssl rand 512 Why not just run httpd under gdb, and see WHY it is crashing? gdb httpd httpd.core run -X once cored, just back trace, step, and it should tell you exactly why it is crashing... Thanks! How do I start httpd with ssl support from this command? (I do apachectl startssl when Apache crashes. apachectl start works fine though.) Apache runs fine when ssl is NOT started. run -X -DSSL ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need help! Apache core dumps when running startssl
On 8/8/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Quoting Andreas Widerøe Andersen [EMAIL PROTECTED]: On 8/8/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Quoting Girish Venkatachalam [EMAIL PROTECTED]: Hope to get some input. Looks like ur random seeding is not happening properly. check whether /dev/random and /dev/urandom work properly. You can verify it with the command $openssl rand 512 Why not just run httpd under gdb, and see WHY it is crashing? gdb httpd httpd.core run -X once cored, just back trace, step, and it should tell you exactly why it is crashing... Thanks! How do I start httpd with ssl support from this command? (I do apachectl startssl when Apache crashes. apachectl start works fine though.) Apache runs fine when ssl is NOT started. run -X -DSSL Here's the output: # gdb httpd httpd.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd...(no debugging symbols found)... Core was generated by `httpd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libcrypt.so.2...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libmm.so.14...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libexpat.so.6...(no debugging symbols found)...done. Reading symbols from /usr/lib/libc.so.4...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_mmap_static.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_vhost_alias.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_env.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_define.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_log_config.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_mime_magic.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_mime.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_negotiation.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_status.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_info.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_include.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_autoindex.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_dir.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_cgi.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_asis.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_imap.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_actions.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_speling.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_userdir.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_alias.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_rewrite.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_access.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_auth.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_auth_anon.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_auth_db.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_digest.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/libproxy.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_cern_meta.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_expires.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_headers.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_usertrack.so...(no debugging symbols found)...done. Reading symbols from /usr/local/libexec/apache/mod_log_forensic.so...(no debugging symbols found)...done. Reading symbols from
Re: Need help! Apache core dumps when running startssl
Quoting Andreas Widerøe Andersen [EMAIL PROTECTED]: (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... Program received signal SIGPIPE, Broken pipe. 0x2810b1e8 in writev () from /usr/lib/libc.so.4 (gdb) And there's your problem. Some library did not link to libc properly. Do a backtrace and a step, it will tell you which module is failing. I've had numerous problems like this in the past (mostly with mod_php though), recompiling the modules that gave errors sorted them out. I doubt this is a mod_ssl issue. -- C ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need help! Apache core dumps when running startssl
On 8/8/06, Andreas Widerøe Andersen [EMAIL PROTECTED] wrote: On 8/8/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Quoting Andreas Widerøe Andersen [EMAIL PROTECTED] : (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... Program received signal SIGPIPE, Broken pipe. 0x2810b1e8 in writev () from /usr/lib/libc.so.4 (gdb) And there's your problem. Some library did not link to libc properly. Do a backtrace and a step, it will tell you which module is failing. I've had numerous problems like this in the past (mostly with mod_php though), recompiling the modules that gave errors sorted them out. I doubt this is a mod_ssl issue. Thanks. How do I find out which module is creating these problems? and can I just recompile? I mean, what if it's a system module... Sorry for all these questions, but this is a little above my head. :-) Best regards, Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need help! Apache core dumps when running startssl
On 8/8/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Quoting Andreas Widerøe Andersen [EMAIL PROTECTED]: On 8/8/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Quoting Andreas Widerøe Andersen [EMAIL PROTECTED]: (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... Program received signal SIGPIPE, Broken pipe. 0x2810b1e8 in writev () from /usr/lib/libc.so.4 (gdb) And there's your problem. Some library did not link to libc properly. Do a backtrace and a step, it will tell you which module is failing. I've had numerous problems like this in the past (mostly with mod_php though), recompiling the modules that gave errors sorted them out. I doubt this is a mod_ssl issue. Thanks. How do I find out which module is creating these problems? and can I just recompile? I mean, what if it's a system module... As I said, use a backtrace gdb httpd httpd.core run -X -DSSL bt step It should show you right up to the very line of code in the module that is causing the crash... This is what I get now: (gdb) bt #0 0x283d1d61 in bn_mul_add_words () from /usr/local/lib/libcrypto.so.4 #1 0x8 in ?? () Error accessing memory address 0x55b7d3a2: Bad address. (gdb) step Single stepping until exit from function bn_mul_add_words, which has no line number information. Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. (gdb) bt No stack. Best regards, Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [SOLVED] Need help! Apache core dumps when running startssl
On 8/8/06, Andreas Widerøe Andersen [EMAIL PROTECTED] wrote: On 8/8/06, Girish Venkatachalam [EMAIL PROTECTED] wrote: --- Andreas Wider�e Andersen [EMAIL PROTECTED] wrote: On 8/8/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Quoting Andreas Wider�e Andersen [EMAIL PROTECTED]: On 8/8/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Quoting Andreas Wider�e Andersen [EMAIL PROTECTED]: (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... Program received signal SIGPIPE, Broken pipe. 0x2810b1e8 in writev () from /usr/lib/libc.so.4 (gdb) And there's your problem. Some library did not link to libc properly. Do a backtrace and a step, it will tell you which module is failing. I've had numerous problems like this in the past (mostly with mod_php though), recompiling the modules that gave errors sorted them out. I doubt this is a mod_ssl issue. Thanks. How do I find out which module is creating these problems? and can I just recompile? I mean, what if it's a system module... As I said, use a backtrace gdb httpd httpd.core run -X -DSSL bt step It should show you right up to the very line of code in the module that is causing the crash... This is what I get now: (gdb) bt #0 0x283d1d61 in bn_mul_add_words () from /usr/local/lib/libcrypto.so.4 #1 0x8 in ?? () Error accessing memory address 0x55b7d3a2: Bad address. (gdb) step Single stepping until exit from function bn_mul_add_words, which has no line number information. Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. (gdb) bt No stack. OpenSSL shared libraries are the culprit. Try installing some other version of openssl and please remember to build shared objects, IIRC it is ./config --enable-shared or something. That shud take care of ur problem. Best, Girish I went into /usr/ports/security/openssl and did a make deinstall and then make reinstall and it worked! Now things are back normal again. Thanks a lot for all your help. Very much appreciated!!! Best regards from sunny Norway, Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Need help! Apache core dumps when running startssl
Hi, I recently upgraded one of my production servers to FreeBSD 4.11 p19 and then upgraded all ports. I'm now running Apache 1.3.36 mod_ssl and Php 4.4.2 . I had Squirrelmail running on https and now I can't start Apache with ssl. Every time it coredumps. I've tried snakeoil and my own cert. Same thing happens. This is the error message I can see from my httpd-error.log: [Mon Aug 7 20:20:03 2006] [notice] caught SIGTERM, shutting down ssl-engine log: [07/Aug/2006 20:29:01 16880] [info] Server: Apache/1.3.36, Interface: mod_ssl/2.8.27, Library: OpenSSL/0.9.8b [07/Aug/2006 20:29:01 16880] [info] Init: 1st startup round (still not detached) [07/Aug/2006 20:29:01 16880] [info] Init: Initializing OpenSSL library [07/Aug/2006 20:29:01 16880] [info] Init: Loading certificate private key of SSL-aware server my.domain.com:443 [07/Aug/2006 20:29:01 16880] [info] Init: Seeding PRNG with 136 bytes of entropy [07/Aug/2006 20:29:01 16880] [info] Init: Generating temporary RSA private keys (512/1024 bits) from messages: Aug 7 20:34:52 server /kernel: pid 17041 (httpd), uid 0: exited on signal 11 (core dumped) That's it. I can't find any other logs and I can't tell what's wrong. What could it be and what can I do? I have checked the httpd.conf file and compared the previous version with the new dist. Same directives related to ssl virtualhost as far as I can see. Hope to get some input. Thanks Best regards, Andreas W. Andersen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
