Re: apache-1.3.19 segfaulting on FreeBSD-4.3 RC
On Fri, Mar 30, 2001 at 06:50:44PM +0200, Dan Larsson wrote: Does anyone have a clue why I get these segfaults? (The apache port installed is /usr/ports/www/apache13 with no optimizations or extra modules) #0 0x8064287 in ap_get_local_host () apache cannot look up your hostname/IP? -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org PGP signature
Re: apache-1.3.19 segfaulting on FreeBSD-4.3 RC
On Fri, 30 Mar 2001, Chris Faulhaber wrote: | On Fri, Mar 30, 2001 at 06:50:44PM +0200, Dan Larsson wrote: | Does anyone have a clue why I get these segfaults? | | (The apache port installed is /usr/ports/www/apache13 with no | optimizations or extra modules) | | #0 0x8064287 in ap_get_local_host () | | apache cannot look up your hostname/IP? I thought of that, but it seemed too much that apache would segfault because of not being able to resolv its hostname. I'll restart apache after I've updated the A record and see what happens from there. | Regards +-- Dan Larsson | Tel: +46 8 550 120 21 Tyfon Svenska AB | Fax: +46 8 550 120 02 GPG and PGP keys | finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: apache-1.3.19 segfaulting on FreeBSD-4.3 RC
"Dan Larsson" [EMAIL PROTECTED] wrote: On Fri, 30 Mar 2001, Chris Faulhaber wrote: | On Fri, Mar 30, 2001 at 06:50:44PM +0200, Dan Larsson wrote: | Does anyone have a clue why I get these segfaults? | | (The apache port installed is /usr/ports/www/apache13 with no | optimizations or extra modules) | | #0 0x8064287 in ap_get_local_host () | | apache cannot look up your hostname/IP? I thought of that, but it seemed too much that apache would segfault because of not being able to resolv its hostname. I'll restart apache after I've updated the A record and see what happens from there. There was some traffic on the list recently about this. Apparently it's a known bug in Apache 1.3.19. There's a patch, or you can use a config file directive (ServerName?) so Apache doesn't try to lookup it's hostname. Jim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: apache-1.3.19 segfaulting on FreeBSD-4.3 RC
On Fri, 30 Mar 2001, Jim King wrote: | "Dan Larsson" [EMAIL PROTECTED] wrote: | | On Fri, 30 Mar 2001, Chris Faulhaber wrote: | | | On Fri, Mar 30, 2001 at 06:50:44PM +0200, Dan Larsson wrote: | | Does anyone have a clue why I get these segfaults? | | | | (The apache port installed is /usr/ports/www/apache13 with no | | optimizations or extra modules) | | | | #0 0x8064287 in ap_get_local_host () | | | | apache cannot look up your hostname/IP? | | I thought of that, but it seemed too much that apache would segfault | because of not being able to resolv its hostname. That was the case. After updating the A record apache starts just fine. | There was some traffic on the list recently about this. Apparently it's a | known bug in Apache 1.3.19. There's a patch, or you can use a config file | directive (ServerName?) so Apache doesn't try to lookup it's hostname. Where would I look to find the patch? | Regards +-- Dan Larsson | Tel: +46 8 550 120 21 Tyfon Svenska AB | Fax: +46 8 550 120 02 GPG and PGP keys | finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
re: apache-1.3.19 segfaulting on FreeBSD-4.3 RC
Dan, I had the same problem yesterday on a 4.2-RELEASE machine. Even though name lookups were working, I could not make Apache start until I added a line to /etc/hosts describing the machine's name: 206.190.29.230 clutch.slgdevelopment.com clutch try mapping your hostname to address in /etc/hosts and restarting Apache. Regards, Tom Duffey To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: apache-1.3.19 segfaulting on FreeBSD-4.3 RC
From: "Dan Larsson" [EMAIL PROTECTED] Does anyone have a clue why I get these segfaults? (The apache port installed is /usr/ports/www/apache13 with no optimizations or extra modules) This problem ocurs when the ServerName directive is not defined in the httpd.conf file. Program received signal SIGSEGV, Segmentation fault. 0x8064287 in ap_get_local_host () (gdb) bt It occurs because "p" is null. The Apache folks have fixed the problem for the next release 1.3.2x. I have fixed this problem in the Apache13-fp port (patch-fj) a week ago. The fix should be applied to the other apache ports (apache13, apache13-modssl, apache13+ipv6). http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/apache13-fp/files/patch-fj?r ev=1.3content-type=text/x-cvsweb-markup We should get this patch into the other apache13 ports before 4.3-RELEASE. Otherwise we'll have a broken apache server on the Release CDs. Scot Note: the fix is in the last two patches of patch-fj. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: desktop selection on sysinstall and available packages inCD-ROM
Hi, We usually go to some trouble to make sure that all the packages referenced by sysinstall are there on the disc #1 image. Can you verify that these items are still missing in the 4.3-rc2 ISO? If you can tell us precisely what's missing, we can make sure that this doesn't happen for the next one or, certainly, for 4.3-RELEASE. Thanks, - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
4.3 Release candidate #2 now ready
Due to the recent security fixes which went into the tree, along with the fact that I'll be following a very large moving truck on Monday and will be somewhat busy, I'm releasing the second release candidate image today instead of monday. Please find the relevent x86 bits at: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.3rc2-install.iso ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.3-RC2/ I've also done an alpha build which I'll be uploading a little later today, though probably no ISO image yet since I'm still waiting on packages and XFree86 bits for the Alpha. Thanks, as always, for testing these bits! - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
primary ftpd[3921]: control bind: Address already in use - Help!
My ftpd stopped working today. It works occasionally, but when you connect to it there is a very long wait between when the socket is connected and the welcome message is displayed. The error message in the log is: Mar 30 13:51:31 primary ftpd[3921]: control bind: Address already in use Any ideas? I'm using 3.5 STABLE -mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: nfsd Benchmark
Rami, You will want to use v2.2.19 of the Linux kernel if you are testing the NFS server and client issues. The newer kernel fixed a few problems they had with NFS that may add to your problems testing with FreeBSD. Ken From: Rami AlZaid <[EMAIL PROTECTED]> To: David Malone <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] Subject: Re: nfsd Benchmark Date: Fri, 30 Mar 2001 02:16:33 -0500 I've compiled the debugger into the kernel and read the section about that in the handbook but now after the crash there isn't any dump restored! I tried using the ctl-alt-esc but that doesn't help... when the machined is killed I'm not about to do anything with it at all other than resetting the machine. At 04:29 AM 3/28/2001, you wrote: On Tue, Mar 27, 2001 at 08:29:35PM -0500, Rami AlZaid wrote: I'm currently running 4.3-BETA and I'm trying to benchmark nfsd with iozone. When using a Linux machine (2.2.18) as the nfs client and a FreeBSD machine as the nfs server, the whole FreeBSD machine hangs when trying to benchmark and the only thing I could do is turn it off and turn it back on again. The nfsd works fine in normal usage but it just hangs when benchmarking. Does anyone know why would nfsd hangs the FreeBSD machine when trying to benchmark it? is this a bug? Definitely a bug. Linux used to have lousy clustering, which would result in the NFS server being hit harder during writes, but I think this has been fixed. It shouldn't kill the server either way. Have you tried compiling the debugger into the kernel and using ctl-alt-esc when it is wedged? Rami AlZaid * ICQ # 1071118 WebPages: www.alzaid.com * www.wooyeah.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message Get your FREE download of MSN Explorer at http://explorer.msn.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: apache-1.3.19 segfaulting on FreeBSD-4.3 RC
Make sure your /etc/hosts file is up to date. ie. it lists the ip adress of the host you run apache on. Ron. - Original Message - From: "Dan Larsson" [EMAIL PROTECTED] To: "FreeBSD Stable List" [EMAIL PROTECTED] Sent: Friday, March 30, 2001 6:50 PM Subject: apache-1.3.19 segfaulting on FreeBSD-4.3 RC Does anyone have a clue why I get these segfaults? (The apache port installed is /usr/ports/www/apache13 with no optimizations or extra modules) I have attached the debug and dmesg. Regards +-- Dan Larsson | Tel: +46 8 550 120 21 Tyfon Svenska AB | Fax: +46 8 550 120 02 GPG and PGP keys | finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Stopped receiving freebsd-stable mail...
Not sure if this is really a mail for this list, but a few days ago I suddenly stopped receiving mail from this mailing list after being on it several months. I resubscribed yesterday, then received 8 messages ending with a mail from Valentin Nechayev of subject "Re: Threads vs. blocking sockets", now nothing again. A quick check on the archives at www.freebsd.org told me that there were certainly more messages, but I seem to have stopped recieving them for no particular reason, and I just stumped as to why! Any help greatly appreciated. Please CC me into any replys, well you can guess why :) Thanks Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: Threads vs. blocking sockets
I've gotten behind on this thread (no pun intended :-)) so here are replies to a bunch of stuff: | the implementation of the threading library | should, hopefully, be irrelevant. | It's certainly not irrelevant. No, in the real world it's not irrelevant, although it should be. And just because it's not irrelevant doesn't mean we shouldn't strive to make it so (I'm talking POSIX-compliant threading libraries here). | It is not correct even in case of single-threaded program. Consider, | for example, a case when waiting on blocking call is interrupted | with signal. Generally if a signal interrupts a call I don't want to restart it. In the few cases I do (usually SIGCHLD), I specify SA_RESTART when catching the signal. In the specific case that lead me to the original problem, it was an XML-RPC client. It bundles up some data and squirts it at a server. Any signal that comes in I want to kill the client, I most definitely *don't* want it retrying the call. | If you rely on sending all data in send() without checking, your code is buggy. It's not my code. :-) It's the standard Python libraries. I suspect you'd have trouble convincing Guido et al. that code that works as expected on most Unix variants, MacOS, and Windows needs to be changed just for FreeBSD. | Linux does not implement threads correctly. I have had so many problems | with the pseudo-threads that Linux uses, it isn't funny. Threading on | Linux is just another name for forking, and causes so many performance | issues as to be useless. I suspect we could argue forever over "correctly" (for one thing, it doesn't screw up blocking sockets. :-)) However, I agree that Linux' implementation of threads, whether "correct" or not, isn't optimal, and is in fact one of the reasons I'm investigating FreeBSD. | There was a bug in Python 1.52 that caused sends to fail on FreeBSD. I wasn't aware of this, however in my case it's not relevant as I'm using Python 2.0, and the equivalent C code exhibits the same problem. | Nice little tidbit for you: | int sendall(int sd, const char * buf, int * len) I'm aware I could write a little function to loop over sends. My argument is that the libc_r wrappers should do so for me. Also, I don't want to have to modify the Python (and probably perl and maybe some other stuff) standard libraries every time I update them. Brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Garbled keymaps in RC1
I just installed RC1. It was a new installation on an empty slice. In the configuration portion of the install, I chose the us.unix keymap. When I reached the point of needing to make a text entry, the character map was very garbled. It may have been Dvorak, but it as sure not qwerty. I've normally used this keymap in the past with no problems. I switched to us.iso and everything was back to normal. I then had to re-enter the root password as it was totally hosed when entered in sysinstall. Has anyone else seen this? R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
