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))

Jeremy Chadwick freebsd at jdc.parodius.com
Thu May 27 08:29:21 UTC 2010

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):


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.

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).

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

More information about the freebsd-ports mailing list