Re: Dying jail
On Wed, Oct 26, 2016 at 03:09:31PM +0700, Eugene Grosbein wrote: > Hi! > > Recently I've upgraded one of my server running 9.3-STABLE with jail > containing 4.11-STABLE system. > The host was source-upgraded upto 10.3-STABLE first and next to 11.0-STABLE > and jail configuration migrated to /etc/jail.conf. The jail kept intact. > > "service jail start" started the jail successfully > but "service jail restart" fails due to jail being stuck in "dying" state for > long time: > "jls" shows no running jails and "jls -d" shows the dying jail. > > How do I know why is it stuck and how to forcebly kill it without reboot of > the host? > I have the same problem on a FreeBSD 11.0 I have no specific jail.conf for exec.start is directly calls service cassandra onestart and stop calls the stop of the very same service. jail -f /myconf -r nameofthejail I can see the jail staying in dying mode for multiple minutes even after sockstat -j has been showing no TCP is left at all. No processes are left in the jail I'm mostly clueless on how to debug that and know that the dying jail is waiting on. It is painful as it prevents from exporting the zfs pool the jail was sitting on. Any one has ideas? Best regards, Bapt signature.asc Description: PGP signature
1MB swap partition on 11.0 memstick
Tried in -questions but no takers .. root@x200:~ # mdconfig -lv md0 vnode 700M /home/smithi/FreeBSD-11.0-RELEASE-amd64-memstick.img root@x200:~ # gpart show -p md0 => 3 1433741md0 GPT (700M) 3 1600 md0p1 efi (800k) 1603 125 md0p2 freebsd-boot (62k) 1728 1429968 md0p3 freebsd-ufs (698M) 1431696 2048 md0p4 freebsd-swap (1.0M) What is the 1.0M swap partition for? Is it needed by bsdinstall? I have an MBR-scheme sliced memstick using boot0 with that md0p3 dd'd to da0s2a which boots fine, but have only run it as 'Live CD' and have not run the installer, but am wondering if a) that swap partition is really needed and if so, b) what can usefully be done with 1MB of swap .. cheers, Ian ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
USB keyboard (wired) caps-lock takes for ever on 11-STABLE
After I did a wipe/reinstall going from 10.3 to 11 the same machine/keyboard has gone from instantly registering the pressing of caps-lock to causing a 2-3 second pause in keyboard i/o when pressing it (on or off). -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
NFS Client can't reconnect (RPC timeout) after reboot
I get a RPC time out when I attempt to reboot a 11-STABLE (1st uname) NFS client attempting to connect to a 11-STABLE NFS server (2nd uname): (Note: NIS continues to work w/ "server" being the NIS server also note rebooting the server clears it but restarting rpcbind/nfsd/mountd does not) FreeBSD lilith 11.0-STABLE FreeBSD 11.0-STABLE #7 r308121: Mon Oct 31 02:58:37 EDT 2016 root@lilith:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD server 11.0-STABLE FreeBSD 11.0-STABLE #0 r308000: Thu Oct 27 09:47:19 EDT 2016 aryeh@server2:/data/usr.obj/data/usr.src/sys/GENERIC amd64 Server /etc/rc.conf: hostname="server" ifconfig_vtnet0="inet 10.0.10.254 netmask 255.255.255.0" defaultrouter="10.0.10.1" sshd_enable="YES" # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev="AUTO" named_enable="YES" rpcbind_enable="YES" nfs_server_enable="YES" mountd_flags="-r" nisdomainname="office" nis_server_enable="YES" nis_yppasswdd_enable="YES" lockd_enable="YES" statd_enable="YES" Server /etc/exports: /usr/local/com -maproot=root -network 10.0.10/24 /data/home /data/usr.src /data/ports -maproot=root -network 10.0.10/24 Client /etc/rc.conf: hostname="lilith" ifconfig_re0="inet 10.0.10.20 netmask 255.255.255.0" defaultrouter="10.0.10.1" sshd_enable="YES" # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev="AUTO" nisdomainname="office" nis_client_enable="YES" tomcat7_enable="YES" cupsd_enable="YES" autofs_enable="YES" lockd_enable="YES" statd_enable="YES" -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Dying jail
Peter wrote on 2016/10/28 14:28: Eugene Grosbein wrote: Hi! Recently I've upgraded one of my server running 9.3-STABLE with jail containing 4.11-STABLE system. The host was source-upgraded upto 10.3-STABLE first and next to 11.0-STABLE and jail configuration migrated to /etc/jail.conf. The jail kept intact. "service jail start" started the jail successfully but "service jail restart" fails due to jail being stuck in "dying" state for long time: "jls" shows no running jails and "jls -d" shows the dying jail. Same issue here. During upgrade to 10 I wrote a proper jail.conf, and, as this is now a much more transparent handling, I also began to start+stop my jails individually w/o reboot. I found the same issue: often jails do not want to fully terminate, but stay in the "dying" state - sometimes for a minute or so, but sometimes very long (indefinite). It seems this is not related to remaining processes or open files (there are none) but to network connections/sockets which are still present. Probably these connections can be displayed with netstat, and probably netstat -x shows some decreasing counters associated with them - I have not yet found the opportunity to figure out what they exactly mean, but anyway it seems like there may be long times involved (hours? forever?), unless one finds the proper connection and terminates both ends. There seems to be no other way to deliberately "kill" such connections and thereby terminate the jail, so the proposal to let it have a new number might be the only feasible approach. (I dont like it, I got used to the numbers of my jails.) I am no sure where but I think it was discussed in jail@ mailing list that keeping the same JID is not recommended. Or recycling freed JID. It was few years ago when I talked about this with BZ. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
