Project

General

Profile

Bug #2855

Error segfault at 0 ip 000055c75bf12856 sp 00007ffc02c03fb0 error 4 in lighttpd[55c75beea000+3c000]

Added by rusborder 9 days ago. Updated 7 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
core
Target version:
Start date:
2018-01-10
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

Description

I have established lighttpd 1.4.48 on the Debian 9 server recently. Several times a day I receive mistakes. Can you help?

uname -a
Linux freedomrussia-SSD 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64 GNU/Linux

php -v
PHP 5.6.33-1+0~20180105151408.9+stretch~1.gbp0deeda (cli)
Copyright (c) 1997-2016 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies
with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies

dmesg -T | grep lighttpd
[Пн янв 8 08:59:48 2018] lighttpd[552]: segfault at 0 ip 000055d1f0d77856 sp 00007ffe05b39960 error 4 in lighttpd[55d1f0d4f000+3c000]
[Пн янв 8 08:59:57 2018] lighttpd[22772]: segfault at 0 ip 000055f9113da856 sp 00007fff4ebba480 error 4 in lighttpd[55f9113b2000+3c000]
[Вт янв 9 12:05:25 2018] lighttpd[4537]: segfault at 0 ip 0000560b0a426856 sp 00007ffd11ba1070 error 4 in lighttpd[560b0a3fe000+3c000]
[Вт янв 9 12:43:33 2018] lighttpd[5108]: segfault at 0 ip 0000558b7c6af856 sp 00007fff5742d3d0 error 4 in lighttpd[558b7c687000+3c000]
[Вт янв 9 12:43:41 2018] lighttpd[5420]: segfault at 0 ip 0000557b5093e856 sp 00007ffd46f2b100 error 4 in lighttpd[557b50916000+3c000]
[Вт янв 9 12:43:42 2018] lighttpd[5439]: segfault at 0 ip 000055905d0a6856 sp 00007ffc00aa7020 error 4 in lighttpd[55905d07e000+3c000]

/var/log/syslog
Jan 10 19:02:01 freedomrussia-SSD CRON24490: (logcheck) CMD ( if [ -x /usr/sbin/logcheck ]; then nice -n10 /usr/sbin/logcheck; fi)
Jan 10 19:04:25 freedomrussia-SSD systemd1: lighttpd.service: Main process exited, code=killed, status=11/SEGV
Jan 10 19:04:25 freedomrussia-SSD systemd1: lighttpd.service: Unit entered failed state.
Jan 10 19:04:25 freedomrussia-SSD systemd1: lighttpd.service: Failed with result 'signal'.
Jan 10 19:04:25 freedomrussia-SSD kernel: [252246.343560] lighttpd13761: segfault at 0 ip 0000557cbfe53856 sp 00007ffd7d90f9f0 error 4 in lighttpd[557cbfe2b000+3c000]
Jan 10 19:04:25 freedomrussia-SSD systemd1: lighttpd.service: Service hold-off time over, scheduling restart.
Jan 10 19:04:25 freedomrussia-SSD systemd1: Stopped Lighttpd Daemon.
Jan 10 19:04:25 freedomrussia-SSD systemd1: Starting Lighttpd Daemon...
Jan 10 19:04:25 freedomrussia-SSD systemd1: Started Lighttpd Daemon.
Jan 10 19:04:29 freedomrussia-SSD kernel: [252250.218559] lighttpd25487: segfault at 0 ip 0000561dace81856 sp 00007ffdf5114dc0 error 4 in lighttpd[561dace59000+3c000]
Jan 10 19:04:29 freedomrussia-SSD systemd1: lighttpd.service: Main process exited, code=killed, status=11/SEGV
Jan 10 19:04:29 freedomrussia-SSD systemd1: lighttpd.service: Unit entered failed state.
Jan 10 19:04:29 freedomrussia-SSD systemd1: lighttpd.service: Failed with result 'signal'.
Jan 10 19:04:29 freedomrussia-SSD systemd1: lighttpd.service: Service hold-off time over, scheduling restart.
Jan 10 19:04:29 freedomrussia-SSD systemd1: Stopped Lighttpd Daemon.
Jan 10 19:04:29 freedomrussia-SSD systemd1: Starting Lighttpd Daemon...
Jan 10 19:04:29 freedomrussia-SSD systemd1: Started Lighttpd Daemon.
Jan 10 19:04:33 freedomrussia-SSD kernel: [252254.122828] lighttpd25505: segfault at 0 ip 0000555aa52ff856 sp 00007ffced91af90 error 4 in lighttpd[555aa52d7000+3c000]
Jan 10 19:04:33 freedomrussia-SSD systemd1: lighttpd.service: Main process exited, code=killed, status=11/SEGV
Jan 10 19:04:33 freedomrussia-SSD systemd1: lighttpd.service: Unit entered failed state.
Jan 10 19:04:33 freedomrussia-SSD systemd1: lighttpd.service: Failed with result 'signal'.
Jan 10 19:04:33 freedomrussia-SSD systemd1: lighttpd.service: Service hold-off time over, scheduling restart.
Jan 10 19:04:33 freedomrussia-SSD systemd1: Stopped Lighttpd Daemon.
Jan 10 19:04:33 freedomrussia-SSD systemd1: Starting Lighttpd Daemon...
Jan 10 19:04:33 freedomrussia-SSD systemd1: Started Lighttpd Daemon.
Jan 10 19:04:48 freedomrussia-SSD systemd1: lighttpd.service: Main process exited, code=killed, status=11/SEGV
Jan 10 19:04:48 freedomrussia-SSD systemd1: lighttpd.service: Unit entered failed state.
Jan 10 19:04:48 freedomrussia-SSD systemd1: lighttpd.service: Failed with result 'signal'.
Jan 10 19:04:48 freedomrussia-SSD kernel: [252269.160056] lighttpd25522: segfault at 0 ip 000055c3ae47d856 sp 00007ffdb731d590 error 4 in lighttpd[55c3ae455000+3c000]
Jan 10 19:04:48 freedomrussia-SSD systemd1: lighttpd.service: Service hold-off time over, scheduling restart.
Jan 10 19:04:48 freedomrussia-SSD systemd1: Stopped Lighttpd Daemon.
Jan 10 19:04:48 freedomrussia-SSD systemd1: Starting Lighttpd Daemon...
Jan 10 19:04:48 freedomrussia-SSD systemd1: Started Lighttpd Daemon.
Jan 10 19:05:01 freedomrussia-SSD systemd1: lighttpd.service: Main process exited, code=killed, status=11/SEGV
Jan 10 19:05:01 freedomrussia-SSD systemd1: lighttpd.service: Unit entered failed state.
Jan 10 19:05:01 freedomrussia-SSD systemd1: lighttpd.service: Failed with result 'signal'.
Jan 10 19:05:01 freedomrussia-SSD kernel: [252281.920161] lighttpd25540: segfault at 0 ip 000055c75bf12856 sp 00007ffc02c03fb0 error 4 in lighttpd[55c75beea000+3c000]
Jan 10 19:05:01 freedomrussia-SSD systemd1: lighttpd.service: Service hold-off time over, scheduling restart.
Jan 10 19:05:01 freedomrussia-SSD systemd1: Stopped Lighttpd Daemon.
Jan 10 19:05:01 freedomrussia-SSD systemd1: Starting Lighttpd Daemon...
Jan 10 19:05:01 freedomrussia-SSD systemd1: Started Lighttpd Daemon.

lighttpd.conf
server.max-connections = 1024
server.max-fds = 2048
server.max-keep-alive-requests = 5
server.max-keep-alive-idle = 5
server.max-read-idle = 20
server.max-write-idle = 50
connection.kbytes-per-second = 0
server.kbytes-per-second = 0
server.max-request-size = 1024
server.range-requests = "disable"

server.modules = (
"mod_access",
"mod_alias",
"mod_accesslog",
"mod_compress",
"mod_redirect",
"mod_rewrite",
)

History

#1

Updated by gstrauss 8 days ago

  • Category changed from documentation to core

Are you able to provide any more details?
http://coredump.io/blog/2012/02/23/debugging-segfaults-from-logs-to-gdb/

Are you by any chance filling up your disk? See #2843

#2

Updated by rusborder 7 days ago

gstrauss wrote:

Are you able to provide any more details?
http://coredump.io/blog/2012/02/23/debugging-segfaults-from-logs-to-gdb/

Are you by any chance filling up your disk? See #2843

I have increased memory size on my VPS. At the moment I don't receive these mistakes again. Have you given the link to the publication - but I don't see the instruction what I have to make? I haven't understood a question about a disk?

Also available in: Atom