Bug 32740
| Summary: | ftpd segfaults after get | ||
|---|---|---|---|
| Product: | Base System | Reporter: | never |
| Component: | bin | Assignee: | Yar Tikhiy <yar> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 4.4-STABLE | ||
| Hardware: | Any | ||
| OS: | Any | ||
On Wed, Dec 12, 2001 at 10:43:38AM +0200, Alexandr P. Kovalenko wrote: [snip] > daily security output: > > pid 43138 (ftpd), uid 3033: exited on signal 11 > > Dec 11 16:35:26 rabbit /kernel: pid 43138 (ftpd), uid 3033: exited on signal 11 > > uid 3033 is user atlon > > >How-To-Repeat: > I cannot reproduce this error for sure, it happens according to very > strange law... > >Fix: > > Haven't find anything that could cause this on 'get' in sources. Maybe you > will? Have a look at, http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#SIGNAL11 Anything there look familiar? Is ftpd(8) the only on dying like this? Do you have a better idea of how to reproduce this yet? -- "It's always funny until someone gets hurt. Then it's hilarious." Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org State Changed From-To: open->feedback We need more information to zero in on any problem (if one exists). Hello, Crist J . Clark! On Mon, Dec 17, 2001 at 03:36:09AM -0800, you wrote: > > > pid 43138 (ftpd), uid 3033: exited on signal 11 > > > Dec 11 16:35:26 rabbit /kernel: pid 43138 (ftpd), uid 3033: exited on signal 11 > > > > uid 3033 is user atlon > > > > >How-To-Repeat: > > I cannot reproduce this error for sure, it happens according to very > > strange law... > > >Fix: > > > > Haven't find anything that could cause this on 'get' in sources. Maybe you > > will? > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#SIGNAL11 > > Anything there look familiar? Is ftpd(8) the only on dying like this? I've checked URL, nothing looks familiar, I have not overclocked CPU, I have brand new Trascend memory, I have 400W power suppoly and ftpd(8) is the only one which is dying like this. No 11 signals except for ftpd. This server is pretty loaded with apache/mysql/postgresql, and nothing segfaults except for ftpd. > Do you have a better idea of how to reproduce this yet? No, unfortunately... I had this problem few times on different hardware known to be absolutely good. And the strange thing -- it does not leave core... -- NEVE-RIPE State Changed From-To: feedback->analyzed I've investigated such segfaults on my pretty busy FTP server. They result from bogus signal handling in the old BSD FTPD, when non-reentrant functions are called from signal handlers etc. I'm working on merging OpenBSD improvements to FTPD, which include proper signal handling. Responsible Changed From-To: freebsd-bugs->yar I'm working on the solution. State Changed From-To: analyzed->closed PR bin/33846 describes the same problem in much greater detail. |
# grep 43138 ftpd.log Dec 11 16:34:25 rabbit ftpd[43138]: connection from h13.227.dialup.iptcom.net (212.9.227.13) Dec 11 16:34:26 rabbit ftpd[43138]: FTP LOGIN FROM h13.227.dialup.iptcom.net as atlon Dec 11 16:35:26 rabbit ftpd[43138]: get /usr/local/www/www.atlon.com.ua/htdocs/content/price/header.htm = 18 bytes # ls -la /usr/local/www/www.atlon.com.ua/htdocs/contect/price/header.htm -rw-r--r-- 1 atlon nobody 18 Dec 10 18:19 /usr/local/www/www.atlon.com.ua/htdocs/content/price/header.htm daily security output: > pid 43138 (ftpd), uid 3033: exited on signal 11 > Dec 11 16:35:26 rabbit /kernel: pid 43138 (ftpd), uid 3033: exited on signal 11 uid 3033 is user atlon Fix: Haven't find anything that could cause this on 'get' in sources. Maybe you will? How-To-Repeat: I cannot reproduce this error for sure, it happens according to very strange law...