Ticket #1652 (new defect)

Opened 3 weeks ago

Last modified 4 days ago

Lighttpd Occasionally Crashes on Cygwin Windows Server 2003 R2

Reported by: alevchuk Assigned to: jan
Priority: normal Milestone: 1.5.0
Component: core Version: 1.4.19
Severity: normal Keywords:
Cc: Blocking:
Need Feedback: 1

Description

I got CYGWIN_NT-5.2 on Windows Server 2003 R2. Hardware: 4 x Intel(R) Xeon(TM) CPU 3.00GHz (probably 2 dual cores) with 4GB of RAM.

$ lighttpd -V lighttpd-1.4.19 - a light and fast webserver Build-Date: Mar 30 2008 18:42:34

Event Handlers:

+ select (generic) + poll (Unix)

  • rt-signals (Linux 2.4+)
  • epoll (Linux 2.6)
  • /dev/poll (Solaris)
  • kqueue (FreeBSD)

Network handler:

+ writev + mmap support

Features:

  • IPv6 support + zlib support + bzip2 support + crypt support
  • SSL Support + PCRE support
  • mySQL support
  • LDAP support
  • memcached support
  • FAM support
  • LUA support
  • xml support
  • SQLite support
  • GDBM support

Occasionally it crashes minutes after staring, with:

2008-04-25 11:49:38: (connections.c.1210) connection closed: poll() -> ERR 6

Alex

Attachments

backup.conf (7.9 kB) - added by alevchuk on 04/27/2008 12:07:43 AM.

Change History

04/25/2008 09:06:36 PM changed by stbuehler

  • severity changed from major to normal.
  • pending set to 1.

That message just means that a connection got closed, as the system reported an error for it.

I don't think lighty crashes just as a connection got closed, so can you perhaps provide more info, e.g. a backtrace?

04/27/2008 12:07:43 AM changed by alevchuk

  • attachment backup.conf added.

04/27/2008 12:07:58 AM changed by alevchuk

  • pending deleted.

Thanks!

I haven't been getting the crashes lately, but I did not change anything to fix that, so the problem is probably still there. I do not think that running lighty as a child of strace for many days would be a good idea. But if I find out what causes the crash then I will give you the system call trace.

The problem may be related to the lack of memory, because I had one other service. It was more verbose and left a "cannot malloc" in my logs.

With the method explained by Cygwin I found that no more then 1G can be malloc'ed on my system. More info is here:

http://www.cygwin.com/cygwin-ug-net/setup-maxmem.html

My initial default was 1G, and not 384 MB as said in the article. I was not able to increase my heap limit using the instructions that they provided.

Attached is my config.

04/27/2008 12:25:23 AM changed by alevchuk

Here are the references of people with similar problems:

04/28/2008 10:02:08 AM changed by stbuehler

  • pending set to 1.

You don't need to run it in strace, gdb / valgrind is enough for a backtrace.

04/29/2008 02:36:32 AM changed by alevchuk

  • pending deleted.

I installed gdb 6.8.0 from the package and valgrind has will not "./confugure" in cygwin (asks me to consider building a port).

The server crashed again today (once).

Can you tell me which lines of lighttpd-1.4.19 to break point so I can run under in gdb for several days?

04/29/2008 06:10:51 AM changed by stbuehler

  • pending set to 1.

gdb should break if lighttpd "fails" (segfaults), so you shouldn't need break points and just running it in gdb should be enough.

Ah, and to get as much information as possible, please try the full backtrace: 

bt full

05/12/2008 02:15:54 PM changed by Olaf van der Spek

That message just means that a connection got closed, as the system reported an error for it.

Are you sure? Lighttpd doesn't log all connections being closed, so I'm sure it's more than 'just' a connection being closed.

Add/Change #1652 (Lighttpd Occasionally Crashes on Cygwin Windows Server 2003 R2)




Change Properties