From owner-freebsd-stable Sun Mar 25 4: 3:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id CB52737B71D for ; Sun, 25 Mar 2001 04:03:17 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f2PC3B347041; Sun, 25 Mar 2001 14:03:11 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Henk Wevers" Cc: freebsd-stable@freebsd.org Subject: Re: Strange problems with multiple jail's In-Reply-To: Your message of "Sun, 25 Mar 2001 13:50:14 +0200." <00be01c0b521$c76bc190$01000001@kpnlep> Date: Sun, 25 Mar 2001 14:03:11 +0200 Message-ID: <47039.985521791@critter> From: Poul-Henning Kamp Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Henk, This sounds strange, and my initial reaction is that it sounds a bit like some kind of limit being reached, number of processes, filehandles or something. The fact that it hits a new "random" service each boot is what makes me think so. I'm aware of at least one machine with 100+ jails, so I don't think we have a magic number limit in the jail code as such. My best suggestion is that you examine the startup messages for each jail in turn, and try to spot any error messages which might offer a clue to why some services fails. In particular, try to locate the messages pertaining to the service which failed... My second best suggestion to you is to try to start the jails sequentially at boot, maybe even put a "sleep 30" between them, to make sure that one is finished before the next one starts. It could be that during bootup you get far too many processes running at the same time or something... That's the best I can offer you right now, Poul-Henning In message <00be01c0b521$c76bc190$01000001@kpnlep>, "Henk Wevers" writes: >I have an enviorement with more than 25 jail's >There is always atleast one jail who can not connect to service like >mail on the same ipadress. Telnet ipnumber(from the jail) 25 does not >work in that jail, the main server cannot connect to any service on that >jail. From the outside the jail is working fine, only if you have an php >based webmail server on it, it could not connect to localhostIP port >143. >This problem is that if i reboot the server and start the jail's again, >the next time another jail cannot connect to the local services. >This problem is here from FreeBSD 4.2-STABLE Okt 2000. >I did an update to FreeBSD 4.3-RC1 and the problem is still here. > >In short >* In a multiple jail enviorement(20>) one or more jails cannot connect >to localip services >* The main server can not connect to the jail >* Every service on the jail is working fine, and is connectable from the >outside. >* After a reboot the jail that can not connect to the localIP is >different than before the reboot. >* The problem with this is active sinds Okt 2000 in FreeBSD 4.x -STABLE >(LocalIP is a real ipnumber) > > >Hope it could be fixed. > >Henk Wevers > > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message