** Changed in: lighttpd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/643518
Title:
Bus error
To manage notifications about this bug go to:
https://b
FYI: fixed in lighttpd 1.4.40, released July 2016.
Latest lighttpd release (at time this is being written) is lighttpd
1.4.44
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/643518
Title:
Bus error
I posted my question in the lighttpd development forum here:
http://redmine.lighttpd.net/boards/3/topics/3623
--
Bus error
https://bugs.launchpad.net/bugs/643518
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
Yes I will ask lighttpd development team if its normal or not.
>From my gut feeling a server software should never crash with Bus error.
What is interessting, I didn't notice to have this problem with OpenSolaris and
ZFS. Maybe nmap has a different behaviour on Linux than Solaris.
--
Bus error
h
Thank you for your bug report and investigating the root cause / issue.
I do not really agree that it is not a bug; a web server should not crash in
this case, but handle it more gracefully.
Therefore I am marking it Triaged for now.
Do you like to report it to the Lighttpd developers upstream?
Since I no more changed the file "stats", lighttpd no more crashes with bus
error.
So: Do not change files while lighttpd is reading them with nmap under Linux.
Solution: Change document root files only with UNIX "rename" syscall.
This bug will not happen if files will be changed properly.
You ca
locking would probably uses too much resources for a high-speed webserver.
The error comes from my side: I change a file while lighttpd is using it. The
solution would be to change it atomically without that lighttpd loss its file
descriptor. I will use "rename" for this.
So if I change the conte
Its possible that the content of "/var/www/trashmail/htdocs/stats" changed
between the "mmap" and "write" from outside on the filesystem.
Then the data addresses provided by mmap could be invalid.
Should lighttpd not lock the file after open and before executing mmap?
Then unlock after reading it?
lighttpd version:
lighttpd/1.4.26 (ssl)
I could use strace to trace when it bus error occured:
ioctl(14, FIONREAD, [0])= 0
read(14, 0x298dd70, 4159) = -1 EAGAIN (Resource temporarily
unavailable)
epoll_ctl(12, EPOLL_CTL_MOD, 14, {EPOLLIN|EPOLLERR|EPOLLHUP, {u32=14, u
Here are my system information:
# cat /etc/issue
Ubuntu 10.04.1 LTS \n \l
# uname -ar
Linux trashmail 2.6.32-23-server #37-Ubuntu SMP Fri Jun 11 09:11:11 UTC 2010
x86_64 GNU/Linux
--
Bus error
https://bugs.launchpad.net/bugs/643518
You received this bug notification because you are a member of
10 matches
Mail list logo
