freebsd stable - May 2010 - www/lighttpd: lighttpd won't start anymore after SSL Update in 8.1-PRERELEASE (2010-05-27 09:34:56: (network.c.529) SSL: error:00000000:lib(0):func(0):reason(0))

Since I performed a make buildworld and installed everything and after 
an update of the ports tree (with which lighttpd was updated from 
lighttpd-1.4.26 to lighttpd-1.4.26_1 I receive this error when trying to 
start lighttpd:

2010-05-27 09:34:56: (network.c.529) SSL: 
error:00000000:lib(0):func(0):reason(0)

Are there any suggestions/known issues/workaround or is this a serious 
error and should be ready for a PR?

Thanks ina advance,
Oliver

On Thu, May 27, 2010 at 09:39:10AM +0200, O. Hartmann
wrote:
> Since I performed a make buildworld and installed everything and
> after an update of the ports tree (with which lighttpd was updated
> from lighttpd-1.4.26 to lighttpd-1.4.26_1 I receive this error when
> trying to start lighttpd:
> 
> 2010-05-27 09:34:56: (network.c.529) SSL:
> error:00000000:lib(0):func(0):reason(0)
> 
> Are there any suggestions/known issues/workaround or is this a
> serious error and should be ready for a PR?
I think you're correlating two things in correctly.  The OpenSSL update
was completely separate and unrelated to the update to
ports/www/lighttpd.  The version bump in ports/www/lighttpd was done for
an unrelated reason (to add support for TCP_NODELAY):

http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/lighttpd/Makefile
http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/lighttpd/Makefile.diff?r1=1.77;r2=1.78;f=h

Simply put: due to the OpenSSL upgrade, people should rebuild all ports
that are dependent upon OpenSSL.  If your problem persists after that,
then I would recommend contacting the lighttpd folks to find out why
their software doesn't work with OpenSSL 0.9.8n.

I can tell you factually that Apache 2.2 (ports/www/apache22) works fine
after the OpenSSL bump.  I *did* rebuild Apache after seeing the OpenSSL
change, however.

<rant>
This is what happens when there are library or include file semantic
changes.  I have to regularly remind folks that there is no guarantee
a semantic change results in a bump of the shared library version
number (e.g. libxxx.so.6 --> libxxx.so.7).
</rant>

-- 
| Jeremy Chadwick                                   jdc@parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |

On 27/05/2010 08:39, O. Hartmann wrote:
> Since I performed a make buildworld and installed everything and after
> an update of the ports tree (with which lighttpd was updated from
> lighttpd-1.4.26 to lighttpd-1.4.26_1 I receive this error when trying
> to start lighttpd:
>
> 2010-05-27 09:34:56: (network.c.529) SSL:
> error:00000000:lib(0):func(0):reason(0)
>
> Are there any suggestions/known issues/workaround or is this a serious
> error and should be ready for a PR?
>
It sounds like this error
http://dev.modmancer.com/index.php/2010/05/23/lighttpd-and-network-c-529-ssl-error/
There is a fix in that URL but a PR if there isnt one would probably
make sense.


Vince
> Thanks ina advance,
> Oliver
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to
"freebsd-stable-unsubscribe@freebsd.org"