From owner-freebsd-stable@freebsd.org Sun Oct 15 09:33:14 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8BC81E3EB92 for ; Sun, 15 Oct 2017 09:33:14 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2E27E7094A for ; Sun, 15 Oct 2017 09:33:14 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v9F9XAHY082179 for ; Sun, 15 Oct 2017 11:33:10 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 757BE9E6; Sun, 15 Oct 2017 11:33:10 +0200 (CEST) Message-ID: <59E32B56.6050203@omnilan.de> Date: Sun, 15 Oct 2017 11:33:10 +0200 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: FreeBSD Stable Subject: reboot-less zfs volmode property refresh? Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Sun, 15 Oct 2017 11:33:10 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Oct 2017 09:33:14 -0000 Hello, maybe I'm just missing something obvious, but modifying a dataset's volmode property seems to force me to reboot the host to have any effect. Test to reproduce (parent dataset hostPsys/bhyveVOL/sys has volmode set ot "dev"): 1.) Create new volume with volmode=geom, and write new GPT zfs create -o volmode=geom -V 10G hostPsys/bhyveVOL/sys/test gpart create -s gpt /dev/zvol/hostPsys/bhyveVOL/sys/test gpart show -l /dev/zvol/hostPsys/bhyveVOL/sys/test => 40 20971440 zvol/hostPsys/bhyveVOL/sys/test GPT (10G) 40 20971440 - free - (10G) (works as expected) 2.) Create new volume with volmode=dev, and write new GPT zfs destroy hostPsys/bhyveVOL/sys/test zfs create -V 10G hostPsys/bhyveVOL/sys/test gpart create -s gpt /dev/zvol/hostPsys/bhyveVOL/sys/test gpart: arg0 'zvol/hostPsys/bhyveVOL/sys/test': Invalid argument (fails as expected) 3.) Modify existing volmode=dev dataset and write new GPT zfs set volmode=geom hostPsys/bhyveVOL/sys/test zfs get volmode hostPsys/bhyveVOL/sys/test NAME PROPERTY VALUE SOURCE hostPsys/bhyveVOL/sys/test volmode geom local gpart create -s gpt /dev/zvol/hostPsys/bhyveVOL/sys/test gpart: arg0 'zvol/hostPsys/bhyveVOL/sys/test': Invalid argument (fails unexpected) What can I do to let geom(4) know that there's a new device? And vice versa, changing volmode property from "geom" to "dev" or "none" doesn't have any effecit either, until reboot. Thanks, -harry From owner-freebsd-stable@freebsd.org Sun Oct 15 09:57:31 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC90CE3F238 for ; Sun, 15 Oct 2017 09:57:31 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 476E8710BD for ; Sun, 15 Oct 2017 09:57:31 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v9F9vTeQ082359 for ; Sun, 15 Oct 2017 11:57:29 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 4F0669EC; Sun, 15 Oct 2017 11:57:29 +0200 (CEST) Message-ID: <59E33109.6010101@omnilan.de> Date: Sun, 15 Oct 2017 11:57:29 +0200 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: FreeBSD Stable Subject: Re: reboot-less zfs volmode property refresh? References: <59E32B56.6050203@omnilan.de> In-Reply-To: <59E32B56.6050203@omnilan.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Sun, 15 Oct 2017 11:57:29 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Oct 2017 09:57:31 -0000 Bezüglich Harry Schmalzbauer's Nachricht vom 15.10.2017 11:33 (localtime): > Hello, > > maybe I'm just missing something obvious, but modifying a dataset's > volmode property seems to force me to reboot the host to have any effect. > > Test to reproduce (parent dataset hostPsys/bhyveVOL/sys has volmode set > ot "dev"): > > 1.) Create new volume with volmode=geom, and write new GPT > > zfs create -o volmode=geom -V 10G hostPsys/bhyveVOL/sys/test > gpart create -s gpt /dev/zvol/hostPsys/bhyveVOL/sys/test > gpart show -l /dev/zvol/hostPsys/bhyveVOL/sys/test > => 40 20971440 zvol/hostPsys/bhyveVOL/sys/test GPT > (10G) > 40 20971440 - free - (10G) > > (works as expected) > > 2.) Create new volume with volmode=dev, and write new GPT > > zfs destroy hostPsys/bhyveVOL/sys/test > zfs create -V 10G hostPsys/bhyveVOL/sys/test > gpart create -s gpt > /dev/zvol/hostPsys/bhyveVOL/sys/test > > gpart: arg0 'zvol/hostPsys/bhyveVOL/sys/test': Invalid argument > > (fails as expected) > > 3.) Modify existing volmode=dev dataset and write new GPT > > zfs set volmode=geom > hostPsys/bhyveVOL/sys/test > > zfs get volmode > hostPsys/bhyveVOL/sys/test > > NAME PROPERTY VALUE > SOURCE > > hostPsys/bhyveVOL/sys/test volmode geom local > gpart create -s gpt > /dev/zvol/hostPsys/bhyveVOL/sys/test > > gpart: arg0 'zvol/hostPsys/bhyveVOL/sys/test': Invalid argument > > (fails unexpected) > > What can I do to let geom(4) know that there's a new device? Device should read provider. I found that last sentence in the zfs(8) man page, describing the volmode property: »This property can be changed any time, but so far it is processed only during volume creation and pool import.« So it seems to be a limitation by design. re-importing the pool is no option for me, so I'll keep in mind that changing volmode means outage. I'm aware that I can utilize ctl(8) to get access to a volmode=dev volume, also md(4) might help in that case, but for changing volmode=geom a reboot / re-import was required. I guess the benefit of extending the implementation design is much to small to justify the effort. But I think making "volmode" a creation-only property (like utf8only) should be considered. Thanks, -harry From owner-freebsd-stable@freebsd.org Sun Oct 15 11:38:34 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97288E40E51 for ; Sun, 15 Oct 2017 11:38:34 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 36ADA73EA2 for ; Sun, 15 Oct 2017 11:38:34 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v9FBcWMM083249 for ; Sun, 15 Oct 2017 13:38:32 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 02788A1C; Sun, 15 Oct 2017 13:38:31 +0200 (CEST) Message-ID: <59E348B7.3060102@omnilan.de> Date: Sun, 15 Oct 2017 13:38:31 +0200 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: FreeBSD Stable Subject: Re: reboot-less zfs volmode property refresh? References: <59E32B56.6050203@omnilan.de> <59E33109.6010101@omnilan.de> In-Reply-To: <59E33109.6010101@omnilan.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Greylist: ACL 129 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Sun, 15 Oct 2017 13:38:32 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Oct 2017 11:38:34 -0000 Bezüglich Harry Schmalzbauer's Nachricht vom 15.10.2017 11:57 (localtime): > Bezüglich Harry Schmalzbauer's Nachricht vom 15.10.2017 11:33 (localtime): … >> 3.) Modify existing volmode=dev dataset and write new GPT >> >> zfs set volmode=geom >> hostPsys/bhyveVOL/sys/test >> >> zfs get volmode >> hostPsys/bhyveVOL/sys/test >> >> NAME PROPERTY VALUE >> SOURCE >> >> hostPsys/bhyveVOL/sys/test volmode geom local >> gpart create -s gpt >> /dev/zvol/hostPsys/bhyveVOL/sys/test >> >> gpart: arg0 'zvol/hostPsys/bhyveVOL/sys/test': Invalid argument >> >> (fails unexpected) >> >> What can I do to let geom(4) know that there's a new device? > Device should read provider. > > I found that last sentence in the zfs(8) man page, describing the > volmode property: > »This property can be changed any time, but > so far it is processed only during volume creation and pool import.« > > So it seems to be a limitation by design. > > re-importing the pool is no option for me, so I'll keep in mind that > changing volmode means outage. > > I'm aware that I can utilize ctl(8) to get access to a volmode=dev > volume, also md(4) might help in that case, but for changing > volmode=geom a reboot / re-import was required. I'ts not correct that md(4) could help here since ms(4) can't use character devices as vnode backend. Just to correct myself. > I guess the benefit of extending the implementation design is much to > small to justify the effort. > But I think making "volmode" a creation-only property (like utf8only) > should be considered. On the other hand, a reboot/re-import might be preferably over zfs send|recv, which would be the only way in that case and which was a regression; better to not consider making it creation-only... I'd like to share two workarounds: The first makes it possible to easily create backups from (bhyve(8)) guests which have ZVOLs as ahci/virtio-block backend. Like described, changing "volmode" property for the corresponding volume dataset from "dev" to "geom" doesn't help without reboot/re-import. But you can clone: zfs snapshot hostPsys/bhyveVOL/sys/guest@offline zfs clone -o volmode=geom hostPsys/bhyveVOL/sys/guest@offline hostPsys/bhyveVOL/sys/guest.gc glabel status gpt/guestSWAP N/A zvol/hostPsys/bhyveVOL/sys/guest.gcp3 gpt/guestBOOT N/A zvol/hostPsys/bhyveVOL/sys/guest.gcp4 gpt/guestSAFE N/A zvol/hostPsys/bhyveVOL/sys/guest.gcp5 gpt/guestVAR N/A zvol/hostPsys/bhyveVOL/sys/guest.gcp6 gpt/guestLOCAL N/A zvol/hostPsys/bhyveVOL/sys/guest.gcp7 gpt/guestDATA N/A zvol/hostPsys/bhyveVOL/sys/guest.gcp8 gpt/guestJbase N/A zvol/hostPsys/bhyveVOL/sys/guest.gcp9 gpt/guestENTITIES N/A zvol/hostPsys/bhyveVOL/sys/guest.gcp10 After you did what ever you need, simply destroy the snapshot and it's clone: zfs destroy -R hostPsys/bhyveVOL/sys/guest@offline This is just a way to work around the volmode limitation for one special case (reading data from the guest's volume). If you need to access the guest volume for other things than non-destructive ones (writing data), you have to go the ctl(4) way. Of course, also for read-only tasks ctl(4) would be appropriate, but since I'm more used to `zfs` than to `ctladm`, the former is easier for me. The latter has more dynamics. Here's the ctl(4) example: ctladm create -b block -d guest-zvol -o file=/dev/zvol/hostPsys/bhyveVOL/sys/guest ctladm port -p `ctladm port -l | grep "camsim.*naa" | cut -w -f 1` -o on geom disk list Geom name: da11 Providers: 1. Name: da11 Mediasize: 8589934592 (8.0G) Sectorsize: 512 Stripesize: 8192 Stripeoffset: 0 Mode: r0w0e0 descr: FREEBSD CTLDISK lunname: FREEBSD guest-zvol lunid: FREEBSD guest-zvol ident: MYSERIAL 0 rotationrate: 0 fwsectors: 63 fwheads: 255 glabel status gpt/guestSWAP N/A da11p3 gpt/guestBOOT N/A da11p4 gpt/guestSAFE N/A da11p5 gpt/guestVAR N/A da11p6 gpt/guestLOCAL N/A da11p7 gpt/guestDATA N/A da11p8 gpt/guestJbase N/A da11p9 gpt/guestENTITIES N/A da11p10 ctladm devlist and ctladm portlist give more info. After you did what ever needed, switch camsim off and remove target: ctladm port -p `ctladm port -l | grep "camsim.*naa" | cut -w -f 1` -o off ctladm remove -b block -l `ctladm devl | grep "guest-zvol" | cut -w -f 2` -harry From owner-freebsd-stable@freebsd.org Sun Oct 15 20:45:15 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44170E4A989 for ; Sun, 15 Oct 2017 20:45:15 +0000 (UTC) (envelope-from fabian.freyer@physik.tu-berlin.de) Received: from mail.tu-berlin.de (mail.tu-berlin.de [130.149.7.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 045DA115C for ; Sun, 15 Oct 2017 20:45:14 +0000 (UTC) (envelope-from fabian.freyer@physik.tu-berlin.de) X-tubIT-Incoming-IP: 130.149.50.25 Received: from mail.physik-pool.tu-berlin.de ([130.149.50.25] helo=mail.physik.tu-berlin.de) by mail.tu-berlin.de (exim-4.89/mailfrontend-5) with esmtp id 1e3pmY-0002sJ-7O; Sun, 15 Oct 2017 22:45:12 +0200 Received: from [130.149.50.251] (aufsichtskiste.physik-pool.tu-berlin.de [130.149.50.251]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.physik.tu-berlin.de (Postfix) with ESMTPSA id 73B3FB441; Sun, 15 Oct 2017 20:45:00 +0000 (UTC) From: Fabian Freyer Subject: Re: kernel process [nfscl] high cpu To: freebsd-stable@freebsd.org Cc: rmacklem@uoguelph.ca, lists@searchy.net, zeha@physik.tu-berlin.de, steff@physik.tu-berlin.de References: <1031959302.30289198.1430594914473.JavaMail.root@uoguelph.ca> <5603AE3D.5090407@searchy.net> <1887696626.8730412.1443097925392.JavaMail.zimbra@uoguelph.ca> <5603FC85.8070105@searchy.net> <924567664.10016007.1443129423733.JavaMail.zimbra@uoguelph.ca> Message-ID: <39012cc6-a527-eb8e-3a6f-7e24cd9d98d8@physik.tu-berlin.de> Date: Sun, 15 Oct 2017 22:45:00 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <924567664.10016007.1443129423733.JavaMail.zimbra@uoguelph.ca> Content-Type: text/plain; charset=utf-8 Content-Language: de-DE Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Oct 2017 20:45:15 -0000 Hi, (I'm not on this list, please CC me in future replies. My apologies to those who get this message twice, I had a typo in the To: header, and have to re-send it to the list.) sorry for reviving such an old thread, but I've run into this problem lately as well, on a 11.1-RELEASE-p1 jailhost mounting NFSv4.0 mounts into jails. On 24.09.2015 23:17, Rick Macklem wrote: > Frank de Bot wrote: >> Rick Macklem wrote: >>> Frank de Bot wrote: >>>> Rick Macklem wrote: >>>>> Frank de Bot wrote: >>>>>> Hi, >>>>>> >>>>>> On a 10.1-RELEASE-p9 server I have several NFS mounts used for a >>>>>> jail. >>>>>> Because it's a server only to test, there is a low load. But the >>>>>> [nfscl] >>>>>> process is hogging a CPU after a while. This happens pretty fast, >>>>>> within >>>>>> 1 or 2 days. I'm noticing the high CPU of the process when I want to >>>>>> do >>>>>> some test after a little while (those 1 or 2 days). Here's my ps ax | grep nfscl: # ps ax | grep nfscl 11111 - DL 932:08.74 [nfscl] 11572 - DL 442:27.42 [nfscl] 30396 - DL 933:44.13 [nfscl] 35902 - DL 442:08.70 [nfscl] 40881 - DL 938:56.04 [nfscl] 43276 - DL 932:38.88 [nfscl] 49178 - DL 934:24.77 [nfscl] 56314 - DL 935:21.55 [nfscl] 60085 - DL 936:37.11 [nfscl] 71788 - DL 933:10.96 [nfscl] 82001 - DL 934:45.76 [nfscl] 86222 - DL 931:42.94 [nfscl] 92353 - DL 1186:53.38 [nfscl] 21105 20 S+ 0:00.00 grep nfscl And this is on a 12-core with Hyperthreading: # uptime 7:28PM up 11 days, 4:50, 4 users, load averages: 25.49, 21.91, 20.25 Most of this load is being generated by the nfscl threads. >>>>>> My jail.conf look like: >>>>>> >>>>>> exec.start = "/bin/sh /etc/rc"; >>>>>> exec.stop = "/bin/sh /etc/rc.shutdown"; >>>>>> exec.clean; >>>>>> mount.devfs; >>>>>> exec.consolelog = "/var/log/jail.$name.log"; >>>>>> #mount.fstab = "/usr/local/etc/jail.fstab.$name"; >>>>>> >>>>>> test01 { >>>>>> host.hostname = "test01_hosting"; >>>>>> ip4.addr = somepublicaddress; >>>>>> ip4.addr += someprivateaddress; >>>>>> >>>>>> mount = "10.13.37.2:/tank/hostingbase /opt/jails/test01 >>>>>> nfs nfsv4,minorversion=1,pnfs,ro,noatime 0 0"; >>>>>> mount += "10.13.37.2:/tank/hosting/test >>>>>> /opt/jails/test01/opt nfs nfsv4,minorversion=1,pnfs,noatime >>>>>> 0 0"; >>>>>> >>>>>> path = "/opt/jails/test01"; >>>>>> } >>>>>> >>>>>> Last test was with NFS 4.1, I also worked with NFS 4.(0) with the >>>>>> same >>>>>> result. In the readonly nfs share there are symbolic links point to >>>>>> the >>>>>> read-write share for logging, storing .run files, etc. When I monitor >>>>>> my >>>>>> network interface with tcpdump, there is little nfs traffic, only >>>>>> when I >>>>>> do try to access the shares there is activity. >>>>>> >>>>>> What is causing nfscl to run around in circles, hogging the CPU (it >>>>>> makes the system slow to respond too) or how can I found out what's >>>>>> the >>>>>> cause? >>>>>> >>>>> Well, the nfscl does server->client RPCs referred to as callbacks. I >>>>> have no idea what the implications of running it in a jail is, but I'd >>>>> guess that these server->client RPCs get blocked somehow, etc... >>>>> (The NFSv4.0 mechanism requires a separate IP address that the server >>>>> can connect to on the client. For NFSv4.1, it should use the same >>>>> TCP connection as is used for the client->server RPCs. The latter >>>>> seems like it should work, but there is probably some glitch.) >>>>> >>>>> ** Just run without the nfscl daemon (it is only needed for delegations >>>>> or >>>>> pNFS). >>>> >>>> How can I disable the nfscl daemon? >>>> >>> Well, the daemon for the callbacks is called nfscbd. >>> You should check via "ps ax", to see if you have it running. >>> (For NFSv4.0 you probably don't want it running, but for NFSv4.1 you >>> do need it. pNFS won't work at all without it, but unless you have a >>> server that supports pNFS, it won't work anyhow. Unless your server is >>> a clustered Netapp Filer, you should probably not have the "pnfs" option.) >>> >>> To run the "nfscbd" daemon you can set: >>> nfscbd_enable="TRUE" >>> in your /etc/rc.conf will start it on boot. >>> Alternately, just type "nfscbd" as root. >>> >>> The "nfscl" thread is always started when an NFSv4 mount is done. It does >>> an assortment of housekeeping things, including a Renew op to make sure the >>> lease doesn't expire. If for some reason the jail blocks these Renew RPCs, >>> it will try to do them over and over and ... because having the lease >>> expire is bad news for NFSv4. How could you tell? >>> Well, capturing packets between the client and server, then looking at them >>> in wireshark is probably the only way. (Or maybe a large count for Renew >>> in the output from "nfsstat -e".) >>> >>> "nfscbd" is optional for NFSv4.0. Without it, you simply don't do >>> callbacks/delegations. >>> For NFSv4.1 it is pretty much required, but doesn't need a separate >>> server->client TCP >>> connection. >>> --> I'd enable it for NFSv4.1, but disable it for NFSv4.0 at least as a >>> starting point. >>> >>> And as I said before, none of this is tested within jails, so I have no >>> idea >>> what effect the jails have. Someone who understands jails might have some >>> insight >>> w.r.t. this? >>> >>> rick >>> >> >> Since last time I haven't tried to use pnfs and just sticked with >> nfsv4.0. nfscbd is not running. The server is now running 10.2. The >> number of renews is not very high (56k, getattr is for example 283M) >> View with wireshark, renew calls look good ,the nfs status is ok. >> >> Is there a way to know what [nfscl] is active with? >> > Not that I can think of. When I do "ps axHl" I see it in DL state and not > doing much of anything. (You could try setting "sysctl vfs.nfs.debuglevel=4", > but I don't think you'll see anything syslog'd that is useful?) > This is what I'd expect for an NFSv4.0 mount without the nfscbd running. nfscbd is not running. I've done a bit of digging with kgdb, by attatching to a thread of one of the nfscl's and grabbed a backtrace: --8<---- snip (kgdb) info threads [...] 678 Thread 101151 (PID=82001: nfscl) 0xffffffff80a9780a in sched_switch () [...] (kgdb) thread 678 [Switching to thread 678 (Thread 101151)]#0 0xffffffff80a9780a in sched_switch () (kgdb) bt #0 0xffffffff80a9780a in sched_switch () #1 0xffffffff80a75a35 in mi_switch () #2 0xffffffff80abaa82 in sleepq_timedwait () #3 0xffffffff80a75435 in _sleep () #4 0xffffffff8095eb7d in nfscl_renewthread () #5 0xffffffff80985204 in start_nfscl () #6 0xffffffff80a2f815 in fork_exit () #7 0xffffffff80ec3b7e in fork_trampoline () #8 0x0000000000000000 in ?? () --8<---- snap So as you said, the nfscl thread is mostly hanging in a sleep. However, every approx. 30-50 seconds (this corresponds quite well with the timing of the renew calls on the wire) the CPU usage spikes to 100% on all 24 threads. dtrace(1m)'ing during those spikes show a huge number (order of 10^5) calls to nfscl_procdoesntexist and nfscl_cleanup_common: Calls nfscl_postop_attr 12 nfscl_loadattrcache 17 nfscl_request 22 nfscl_deleggetmodtime 26 nfscl_reqstart 26 nfscl_mustflush 30 nfscl_nodeleg 34 nfscl_cleanup_common 12005 nfscl_procdoesntexist 12315 Times nfscl_loadattrcache 41949 nfscl_deleggetmodtime 63014 nfscl_postop_attr 65046 nfscl_reqstart 77851 nfscl_procdoesntexist 30187728 nfscl_request 423855128 nfscl_nodeleg 841033772 nfscl_mustflush 4838119753 nfscl_cleanup_common 6436207841 For reference, here's the dtrace(1m) script I'm using: --8<---- snip #!/usr/sbin/dtrace -Cs #pragma D option quiet fbt::nfscl_*:entry { @entries[probefunc] = count(); traceme[probefunc] = 1; ts[probefunc] = timestamp; } fbt::nfscl_*:return /traceme[probefunc]/ { @times[probefunc] = sum(timestamp - ts[probefunc]); } tick-5sec { printa(@times); clear(@times); printa(@entries); clear(@entries); } --8<---- snap For completeness, I guess I *should* synchronize this with the for(;;) loop in nfscl_renewthread and count the actual number of process terminations, but OTOH, I am extremely sure (just by observing the number of running processes and PIDs) that it's nowhere near those counts. Digging a little deeper, I see pfind(9), or more closely pfind_locked is used in nfscl_procdoesntexist. What I do not understand yet is how pfind(9) interacts with jails. Maybe someone(TM) could shed some light on this? > Basically, when the nfscbd isn't running the server shouldn't issue any > delegations, because it shouldn't see a callback path (server->client TCP > connection). Also, if you are using a FreeBSD NFS server, it won't issue > delegations unless you've enabled that, which isn't the default. > > Check to see your Delegs in "nfsstat -e" is 0. It is. > If it is, then all the nfscl should be doing is waking up once per second > and doing very little except a Renew RPC once every 30-60sec. (A fraction of > what the server's lease duration is.) A tcpdump shows at least one renew call/reply pair per minute. > The only thing I can think of that might cause it to run a lot would be some > weirdness related to the TOD clock. It msleep()s for hz and also checks for > time_uptime (which should be in resolution of seconds) != the previous time. > (If the msleep()s were waking up too fequently, then it would loop around > doing not much of anything, over and over and over again...) > > >> I do understand nfs + jails could have issues, but I like to understand >> them. >> Fabian [1] https://lists.freebsd.org/pipermail/freebsd-hackers/2017-June/thread.html#51200 From owner-freebsd-stable@freebsd.org Sun Oct 15 21:25:21 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBC68E4B4B4 for ; Sun, 15 Oct 2017 21:25:21 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0060.outbound.protection.outlook.com [104.47.42.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8997B2484 for ; Sun, 15 Oct 2017 21:25:20 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM (52.132.46.161) by YTOPR0101MB1451.CANPRD01.PROD.OUTLOOK.COM (52.132.47.31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.77.7; Sun, 15 Oct 2017 21:25:18 +0000 Received: from YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM ([fe80::50ab:b8bf:bbb9:81f4]) by YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM ([fe80::50ab:b8bf:bbb9:81f4%13]) with mapi id 15.20.0077.022; Sun, 15 Oct 2017 21:25:18 +0000 From: Rick Macklem To: Fabian Freyer , "freebsd-stable@freebsd.org" CC: "lists@searchy.net" , "zeha@physik.tu-berlin.de" , "steff@physik.tu-berlin.de" Subject: Re: kernel process [nfscl] high cpu Thread-Topic: kernel process [nfscl] high cpu Thread-Index: AQHTRfZ3DNkUvR06Q0enbGk7u4laxqLlaNid Date: Sun, 15 Oct 2017 21:25:18 +0000 Message-ID: References: <1031959302.30289198.1430594914473.JavaMail.root@uoguelph.ca> <5603AE3D.5090407@searchy.net> <1887696626.8730412.1443097925392.JavaMail.zimbra@uoguelph.ca> <5603FC85.8070105@searchy.net> <924567664.10016007.1443129423733.JavaMail.zimbra@uoguelph.ca>, <39012cc6-a527-eb8e-3a6f-7e24cd9d98d8@physik.tu-berlin.de> In-Reply-To: <39012cc6-a527-eb8e-3a6f-7e24cd9d98d8@physik.tu-berlin.de> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB1451; 6:csf354/YU2qXZSo2wgA/QJysq18CbtBlhwdFuqyfxlCJIzbqEohcD/0Bet4LDIcb7x4Q6vHMjWBRW0mbcJG7eYTgpmLUnB/wuVsJyoIIUzW7Rm0RnDMagHdJto3cLsIflCDn8QAMHWaoC9VbtLrvqHOCzieCZrTyK5bllzky5HI3OJ9M7bDBOvdww71+JMMZyu5Nn+oY4zHQ4fJ89mT9y+jZNuvXb2DnmrRu/D2KmwSxq23AwIy0xLDL3o/Innuu+HRL57pDgT6pegsh33oU8zxGK4MnJ9b994Qxs3geY8Krrt6tIzSfUTnELCk9zMztJcUPHR6I1c0Oq7AdJuau+A==; 5:rlazAeCjwrIk3BaNrd4KNzGKRzNrJqSjwrQuErCpJiCTdSnNJul7deqbO+fzpCQXlDeRzGi04A7D55GKx2sz29WIQ/pR+Z0ua0Y85Q9MsRX6EPU84s1cDUP9d1nkfxf9ysz7kr6Jx+scwIh+3fgxw+2XIDTnPI0D77VlSYzJOAg=; 24:Q6Usov6eBT51oGWHKUaxB7MLdSImQObdsz0O8conl+eTo9pfnD8y7gfL7MYdPx6gMvS6gL2+eunPLyDudKP2IT9M6W/7R4WJ1Hp+YTAvFWA=; 7:kXzJF/Fbt3zF0/IxEYKVKzJHl8E8rDx5qcRYitfJsKzhdWNiVvxW6rpmpPFzFDkYREDg7v/jqdN7XJtI/OLArg0tDJTICu4+R7lpe4XnoJAv8z+T9emd1iexfHepBuzyj9xWafXiGlu0bZkHz0OpdxG5rIK2i9XOILPk52uwQylULtYRQdRj2SPGvbr+o4hAI+jUuLjjQDbmJyg42q13VtxECHIU8z8z9rMlhe++sqE= x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: 6d50d38c-7d52-40a1-b119-08d514133c20 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254152)(2017052603199)(201703131423075)(201703031133081)(201702281549075); SRVR:YTOPR0101MB1451; x-ms-traffictypediagnostic: YTOPR0101MB1451: x-exchange-antispam-report-test: UriScan:(158342451672863)(33945880838080)(150554046322364)(75325880899374)(155532106045638)(21532816269658); x-microsoft-antispam-prvs: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(100000703101)(100105400095)(3002001)(10201501046)(93006095)(93001095)(6041248)(20161123560025)(20161123558100)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123562025)(20161123564025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:YTOPR0101MB1451; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:YTOPR0101MB1451; x-forefront-prvs: 046164D5C4 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(376002)(346002)(24454002)(199003)(189002)(377454003)(93886005)(305945005)(81166006)(81156014)(8676002)(786003)(7696004)(2900100001)(55016002)(4326008)(110136005)(54906003)(8936002)(316002)(2950100002)(25786009)(14454004)(9686003)(6306002)(74316002)(53936002)(74482002)(2501003)(102836003)(6506006)(6246003)(5660300001)(33656002)(5250100002)(97736004)(6436002)(3280700002)(966005)(478600001)(53546010)(68736007)(76176999)(54356999)(101416001)(229853002)(189998001)(86362001)(106356001)(50986999)(105586002)(2906002)(3660700001); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB1451; H:YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:3; LANG:en; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Oct 2017 21:25:18.7409 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB1451 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Oct 2017 21:25:22 -0000 Well, a couple of comments: 1 - I have no idea if NFSv4 mounts (or any NFS mount for that matter) will work correctly within jails. (I don't do jails and know nothing about them. Or, at least very little about them.) 2 - I do know that the "nfsuserd" daemon is badly broken when jails are in use. - There are two things you can do about this. 1 - Set vfs.nfsd.enable_stringtouid=3D1 on the server, plus do not run the nfsuserd daemon on either the client or server. (This will require a small change to /etc/rc.d/nfsd to avoid it being starte= d at boot. See the /etc/rc.d/nfsd script in head/current. The chang= e wasn't MFC'd because it was considered a POLA violation.) --> This causes the user/group strings to be just the numbers on the wire and nfsuserd is no longer needed. (The Linux client will do this by default.) If it exists on the client, also set vfs.nfs.enable_uidtostring=3D= 1. (I think this is in stable/11, but not 11.1.) OR 2 - Carry the patches in head/current as r320698, r320757 and r320758 over to the 11.1 sources and build the kernel plus nfsuserd from these patched sources. (These patches make the nfsuserd daemon use an AF_LOCAL socket, which allows it to work within a jail.) As noted at the beginning, I know that nfsuserd breaks when jails are in use, but I do not know what other NFSv4 related things break within jails, so fixing the nfsuserd situation may not resolve your problem= s. rick ________________________________________ From: Fabian Freyer Sent: Sunday, October 15, 2017 4:45:00 PM To: freebsd-stable@freebsd.org Cc: Rick Macklem; lists@searchy.net; zeha@physik.tu-berlin.de; steff@physik= .tu-berlin.de Subject: Re: kernel process [nfscl] high cpu Hi, (I'm not on this list, please CC me in future replies. My apologies to those who get this message twice, I had a typo in the To: header, and have to re-send it to the list.) sorry for reviving such an old thread, but I've run into this problem lately as well, on a 11.1-RELEASE-p1 jailhost mounting NFSv4.0 mounts into jails. On 24.09.2015 23:17, Rick Macklem wrote: > Frank de Bot wrote: >> Rick Macklem wrote: >>> Frank de Bot wrote: >>>> Rick Macklem wrote: >>>>> Frank de Bot wrote: >>>>>> Hi, >>>>>> >>>>>> On a 10.1-RELEASE-p9 server I have several NFS mounts used for a >>>>>> jail. >>>>>> Because it's a server only to test, there is a low load. But the >>>>>> [nfscl] >>>>>> process is hogging a CPU after a while. This happens pretty fast, >>>>>> within >>>>>> 1 or 2 days. I'm noticing the high CPU of the process when I want to >>>>>> do >>>>>> some test after a little while (those 1 or 2 days). Here's my ps ax | grep nfscl: # ps ax | grep nfscl 11111 - DL 932:08.74 [nfscl] 11572 - DL 442:27.42 [nfscl] 30396 - DL 933:44.13 [nfscl] 35902 - DL 442:08.70 [nfscl] 40881 - DL 938:56.04 [nfscl] 43276 - DL 932:38.88 [nfscl] 49178 - DL 934:24.77 [nfscl] 56314 - DL 935:21.55 [nfscl] 60085 - DL 936:37.11 [nfscl] 71788 - DL 933:10.96 [nfscl] 82001 - DL 934:45.76 [nfscl] 86222 - DL 931:42.94 [nfscl] 92353 - DL 1186:53.38 [nfscl] 21105 20 S+ 0:00.00 grep nfscl And this is on a 12-core with Hyperthreading: # uptime 7:28PM up 11 days, 4:50, 4 users, load averages: 25.49, 21.91, 20.25 Most of this load is being generated by the nfscl threads. >>>>>> My jail.conf look like: >>>>>> >>>>>> exec.start =3D "/bin/sh /etc/rc"; >>>>>> exec.stop =3D "/bin/sh /etc/rc.shutdown"; >>>>>> exec.clean; >>>>>> mount.devfs; >>>>>> exec.consolelog =3D "/var/log/jail.$name.log"; >>>>>> #mount.fstab =3D "/usr/local/etc/jail.fstab.$name"; >>>>>> >>>>>> test01 { >>>>>> host.hostname =3D "test01_hosting"; >>>>>> ip4.addr =3D somepublicaddress; >>>>>> ip4.addr +=3D someprivateaddress; >>>>>> >>>>>> mount =3D "10.13.37.2:/tank/hostingbase /opt/jails/test= 01 >>>>>> nfs nfsv4,minorversion=3D1,pnfs,ro,noatime 0 0"; >>>>>> mount +=3D "10.13.37.2:/tank/hosting/test >>>>>> /opt/jails/test01/opt nfs nfsv4,minorversion=3D1,pnfs,noat= ime >>>>>> 0 0"; >>>>>> >>>>>> path =3D "/opt/jails/test01"; >>>>>> } >>>>>> >>>>>> Last test was with NFS 4.1, I also worked with NFS 4.(0) with the >>>>>> same >>>>>> result. In the readonly nfs share there are symbolic links point to >>>>>> the >>>>>> read-write share for logging, storing .run files, etc. When I monito= r >>>>>> my >>>>>> network interface with tcpdump, there is little nfs traffic, only >>>>>> when I >>>>>> do try to access the shares there is activity. >>>>>> >>>>>> What is causing nfscl to run around in circles, hogging the CPU (it >>>>>> makes the system slow to respond too) or how can I found out what's >>>>>> the >>>>>> cause? >>>>>> >>>>> Well, the nfscl does server->client RPCs referred to as callbacks. I >>>>> have no idea what the implications of running it in a jail is, but I'= d >>>>> guess that these server->client RPCs get blocked somehow, etc... >>>>> (The NFSv4.0 mechanism requires a separate IP address that the server >>>>> can connect to on the client. For NFSv4.1, it should use the same >>>>> TCP connection as is used for the client->server RPCs. The latter >>>>> seems like it should work, but there is probably some glitch.) >>>>> >>>>> ** Just run without the nfscl daemon (it is only needed for delegatio= ns >>>>> or >>>>> pNFS). >>>> >>>> How can I disable the nfscl daemon? >>>> >>> Well, the daemon for the callbacks is called nfscbd. >>> You should check via "ps ax", to see if you have it running. >>> (For NFSv4.0 you probably don't want it running, but for NFSv4.1 you >>> do need it. pNFS won't work at all without it, but unless you have a >>> server that supports pNFS, it won't work anyhow. Unless your server is >>> a clustered Netapp Filer, you should probably not have the "pnfs" opti= on.) >>> >>> To run the "nfscbd" daemon you can set: >>> nfscbd_enable=3D"TRUE" >>> in your /etc/rc.conf will start it on boot. >>> Alternately, just type "nfscbd" as root. >>> >>> The "nfscl" thread is always started when an NFSv4 mount is done. It do= es >>> an assortment of housekeeping things, including a Renew op to make sure= the >>> lease doesn't expire. If for some reason the jail blocks these Renew RP= Cs, >>> it will try to do them over and over and ... because having the lease >>> expire is bad news for NFSv4. How could you tell? >>> Well, capturing packets between the client and server, then looking at = them >>> in wireshark is probably the only way. (Or maybe a large count for Rene= w >>> in the output from "nfsstat -e".) >>> >>> "nfscbd" is optional for NFSv4.0. Without it, you simply don't do >>> callbacks/delegations. >>> For NFSv4.1 it is pretty much required, but doesn't need a separate >>> server->client TCP >>> connection. >>> --> I'd enable it for NFSv4.1, but disable it for NFSv4.0 at least as a >>> starting point. >>> >>> And as I said before, none of this is tested within jails, so I have no >>> idea >>> what effect the jails have. Someone who understands jails might have so= me >>> insight >>> w.r.t. this? >>> >>> rick >>> >> >> Since last time I haven't tried to use pnfs and just sticked with >> nfsv4.0. nfscbd is not running. The server is now running 10.2. The >> number of renews is not very high (56k, getattr is for example 283M) >> View with wireshark, renew calls look good ,the nfs status is ok. >> >> Is there a way to know what [nfscl] is active with? >> > Not that I can think of. When I do "ps axHl" I see it in DL state and not > doing much of anything. (You could try setting "sysctl vfs.nfs.debuglevel= =3D4", > but I don't think you'll see anything syslog'd that is useful?) > This is what I'd expect for an NFSv4.0 mount without the nfscbd running. nfscbd is not running. I've done a bit of digging with kgdb, by attatching to a thread of one of the nfscl's and grabbed a backtrace: --8<---- snip (kgdb) info threads [...] 678 Thread 101151 (PID=3D82001: nfscl) 0xffffffff80a9780a in sched_switch () [...] (kgdb) thread 678 [Switching to thread 678 (Thread 101151)]#0 0xffffffff80a9780a in sched_switch () (kgdb) bt #0 0xffffffff80a9780a in sched_switch () #1 0xffffffff80a75a35 in mi_switch () #2 0xffffffff80abaa82 in sleepq_timedwait () #3 0xffffffff80a75435 in _sleep () #4 0xffffffff8095eb7d in nfscl_renewthread () #5 0xffffffff80985204 in start_nfscl () #6 0xffffffff80a2f815 in fork_exit () #7 0xffffffff80ec3b7e in fork_trampoline () #8 0x0000000000000000 in ?? () --8<---- snap So as you said, the nfscl thread is mostly hanging in a sleep. However, every approx. 30-50 seconds (this corresponds quite well with the timing of the renew calls on the wire) the CPU usage spikes to 100% on all 24 threads. dtrace(1m)'ing during those spikes show a huge number (order of 10^5) calls to nfscl_procdoesntexist and nfscl_cleanup_common: Calls nfscl_postop_attr 12 nfscl_loadattrcache 17 nfscl_request 22 nfscl_deleggetmodtime 26 nfscl_reqstart 26 nfscl_mustflush 30 nfscl_nodeleg 34 nfscl_cleanup_common 12005 nfscl_procdoesntexist 12315 Times nfscl_loadattrcache 41949 nfscl_deleggetmodtime 63014 nfscl_postop_attr 65046 nfscl_reqstart 77851 nfscl_procdoesntexist 30187728 nfscl_request 423855128 nfscl_nodeleg 841033772 nfscl_mustflush 4838119753 nfscl_cleanup_common 6436207841 For reference, here's the dtrace(1m) script I'm using: --8<---- snip #!/usr/sbin/dtrace -Cs #pragma D option quiet fbt::nfscl_*:entry { @entries[probefunc] =3D count(); traceme[probefunc] =3D 1; ts[probefunc] =3D timestamp; } fbt::nfscl_*:return /traceme[probefunc]/ { @times[probefunc] =3D sum(timestamp - ts[probefunc]); } tick-5sec { printa(@times); clear(@times); printa(@entries); clear(@entries); } --8<---- snap For completeness, I guess I *should* synchronize this with the for(;;) loop in nfscl_renewthread and count the actual number of process terminations, but OTOH, I am extremely sure (just by observing the number of running processes and PIDs) that it's nowhere near those counts. Digging a little deeper, I see pfind(9), or more closely pfind_locked is used in nfscl_procdoesntexist. What I do not understand yet is how pfind(9) interacts with jails. Maybe someone(TM) could shed some light on this? > Basically, when the nfscbd isn't running the server shouldn't issue any > delegations, because it shouldn't see a callback path (server->client TCP > connection). Also, if you are using a FreeBSD NFS server, it won't issue > delegations unless you've enabled that, which isn't the default. > > Check to see your Delegs in "nfsstat -e" is 0. It is. > If it is, then all the nfscl should be doing is waking up once per second > and doing very little except a Renew RPC once every 30-60sec. (A fraction= of > what the server's lease duration is.) A tcpdump shows at least one renew call/reply pair per minute. > The only thing I can think of that might cause it to run a lot would be s= ome > weirdness related to the TOD clock. It msleep()s for hz and also checks f= or > time_uptime (which should be in resolution of seconds) !=3D the previous = time. > (If the msleep()s were waking up too fequently, then it would loop around > doing not much of anything, over and over and over again...) > > >> I do understand nfs + jails could have issues, but I like to understand >> them. >> Fabian [1] https://lists.freebsd.org/pipermail/freebsd-hackers/2017-June/thread.html#5= 1200 From owner-freebsd-stable@freebsd.org Mon Oct 16 13:58:26 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2D71E3B4CD for ; Mon, 16 Oct 2017 13:58:26 +0000 (UTC) (envelope-from Werner.Griessl@uni-bayreuth.de) Received: from btr0xn.rz.uni-bayreuth.de (btr0xn.rz.uni-bayreuth.de [132.180.8.26]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mailhub-out.uni-bayreuth.de", Issuer "Universitaet Bayreuth CA (UNIBT-CA) G01" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 66C9D81BA7; Mon, 16 Oct 2017 13:58:25 +0000 (UTC) (envelope-from Werner.Griessl@uni-bayreuth.de) Received: from btr0xn-rx.rz.uni-bayreuth.de (localhost [127.0.0.1]) by btr0xn.rz.uni-bayreuth.de (8.13.1/8.13.1) with ESMTP id v9GDwLjT018864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 16 Oct 2017 15:58:21 +0200 (MEST) Received: from btruxs.rz.uni-bayreuth.de (btruxs [132.180.14.11]) by btr0xn-rx.rz.uni-bayreuth.de (8.13.1/8.13.1) with ESMTP id v9GDwKBT018857; Mon, 16 Oct 2017 15:58:20 +0200 (MEST) Reply-To: Werner.Griessl@uni-bayreuth.de Subject: Re: Fwd: ports index after upgrade 10.4 --> 11.1Stable ? To: Gary Palmer Cc: FreeBSD Stable References: <20171013132604.GA96120@in-addr.com> From: Werner Griessl Organization: UNI Bayreuth ITS Message-ID: <173b42d5-60f3-76ac-7622-6aa28e8b4eba@uni-bayreuth.de> Date: Mon, 16 Oct 2017 15:58:20 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171013132604.GA96120@in-addr.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2017 13:58:26 -0000 On 10/13/17 15:26, Gary Palmer wrote: > On Fri, Oct 13, 2017 at 12:59:17PM +0200, Werner Griessl wrote: >> No answer on ports, next try stable >> Werner > >> Date: Wed, 11 Oct 2017 15:48:51 +0200 >> From: Werner Griessl >> To: freebsd-ports@freebsd.org >> Subject: ports index after upgrade 10.4 --> 11.1Stable ? >> >> After an Upgrade from 10.3 Stable --> 11.1 Stable, the >> /usr/ports/INDEX-11 doesnt build after a "portsnap fetch upgrade" >> Have always to do "cd /usr/ports; make index" after a portsnap. >> >> What is wrong with my system ? >> >> Werner > > Did you update /etc with mergemaster? > > Specifically /etc/portsnap.conf contains the list of INDEX files to build > > Regards, > > Gary > Thanks Gary It is solved now, see the conversation in ports Werner -- Werner Grießl D-95440 Bayreuth, Germany Universitaet Bayreuth Tel.: +49 921 55 2685 IT-Servicezentrum/Netze NW2 3.2.U1.143 From owner-freebsd-stable@freebsd.org Tue Oct 17 16:25:22 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B16BE3F54B for ; Tue, 17 Oct 2017 16:25:22 +0000 (UTC) (envelope-from peter@pean.org) Received: from system.jails.se (system.jails.se [IPv6:2001:470:6c08::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CFA4873C73 for ; Tue, 17 Oct 2017 16:25:21 +0000 (UTC) (envelope-from peter@pean.org) Received: from lune.pean.org (213-67-100-148-no110.tbcn.telia.com [213.67.100.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by system.jails.se (Postfix) with ESMTPSA id 002F510F454 for ; Tue, 17 Oct 2017 18:25:17 +0200 (CEST) From: =?utf-8?Q?Peter_Ankerst=C3=A5l?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Subject: 802.1X authenticator for FreeBSD Message-Id: Date: Tue, 17 Oct 2017 18:25:16 +0200 To: FreeBSD Stable X-Mailer: Apple Mail (2.3445.1.7) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 16:25:22 -0000 Hi! I=E2=80=99ve been looking for a 802.1X authenticator for FreeBSD for a = while without any real success. Im pretty familiar with hostapd and use = it my self for WPA2 Enterprise authentications (with the build in RADIUS = server) and it works fine. But what now I would really like to have the = same type of authentication for the wired network, but as far as I can = see there is no way to use the wired driver in FreeBSD.=20 Any pointers on this? Thanks!= From owner-freebsd-stable@freebsd.org Tue Oct 17 17:30:06 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30B35E40EBA for ; Tue, 17 Oct 2017 17:30:06 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C542D7629F for ; Tue, 17 Oct 2017 17:30:05 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id m72so5356415wmc.1 for ; Tue, 17 Oct 2017 10:30:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=yJQnNHyoD2tJF9I13d3atN1yiwWOQj1s28rQo/Demnw=; b=F+c10FW8CllWXsEQP5IvHak7m76ms/Y5Ch3CTDkdwzgguHepr6rY5o9MDHl2S4yH4N K9xD7aPokN+dHs8A8Hl+91cgwSiO88BDVLcEepaQFTaYvxTQdfbaHLrOQ6vtYoxRUmGq EE1sKTTLf/YWB04HAS2dZsYdNBA3IVDHzUGOcfCMgPtnK/sFKz6GPO+BfkyFjq4Uvr92 c2xpJozQXXnaQrHCl2KqvMzOCYn++Xn3QPKdzSdwchuwHrJLzHwCUayQp970BkAmexXC UpYSrJlxB/Jh4VLx39InIAfEIMWRkHfe0zgFutTooufOOG9F2Fkj15apT0NDWMqqho09 p83w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=yJQnNHyoD2tJF9I13d3atN1yiwWOQj1s28rQo/Demnw=; b=jGdr8Pxy9wjkyuL0R6quZAbgvAAsD26R2K5gSEatqPZCxaSpUA/14mJFwQRQFgXCng J5twet9TkrF/xcQ8y+VYIJhdehGe7b2VDF7TWyyhJmHmhzZAJxvQaoBOL9GrGcVy8XrM f/7VXjZCySPBQhf2aiwtIYU7S0l/xxRlBMeS8DQxKDEpB4FnhCoQce+CYe4UDcnGJ5UP Dl/PXyxRdPQt4Zh/dhKXxKZxenqJ47ioG9U3txkDS49oDdFd5jKPloDk2t4pAV6/giA/ XRUMZu3V0iZ/U7eRiqMFDRWDbUjFBpFtm8P2rsTm6CK2k1AKXdPVgrdF+cK+P2e5N4uN gOSg== X-Gm-Message-State: AMCzsaXPZ4aVOmh8tIsRAtAdUdcnPr1lPnSXsKHRwXTAkdjxpKnW/VqI miDZeo9BYz8fYILFqU4GIQ480UriTMeKi+qJZzFG1g== X-Google-Smtp-Source: AOwi7QDN++WQJXaCs4CMsaQKJP/AqcvfdH8JECLKHWe5j6UnKap88bHCphx7SR4j4KJzz+mjqBpjOD+QzYEOxB13T5Y= X-Received: by 10.80.186.33 with SMTP id g30mr18305636edc.206.1508261403942; Tue, 17 Oct 2017 10:30:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.216.6 with HTTP; Tue, 17 Oct 2017 10:29:33 -0700 (PDT) From: Denis Granato Date: Tue, 17 Oct 2017 15:29:33 -0200 Message-ID: Subject: error instaling any ports To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 17:30:06 -0000 Hello everyone I have a 9.1 freebsd server, and every ports I try to install I get the follow error *server# cd /usr/ports/devel/subversionserver# make install clean"/usr/ports/Mk/bsd.port.mk ", line 1045: Unknown directiveUnknown modifier 't'Variable .CURDIR is recursive.server# * From owner-freebsd-stable@freebsd.org Tue Oct 17 17:32:57 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 948E4E411B0 for ; Tue, 17 Oct 2017 17:32:57 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5B2D3767E8 for ; Tue, 17 Oct 2017 17:32:57 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e4Vje-000G9e-Pg; Tue, 17 Oct 2017 19:32:58 +0200 Date: Tue, 17 Oct 2017 19:32:58 +0200 From: Kurt Jaeger To: Denis Granato Cc: freebsd-stable@freebsd.org Subject: Re: error instaling any ports Message-ID: <20171017173258.GZ86601@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 17:32:57 -0000 Hi! > I have a 9.1 freebsd server, and every ports I try to install I get > the follow error 9.1 is no longer supported. Any chance to upgrade ? Do you need help to upgrade that box ? -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-stable@freebsd.org Tue Oct 17 17:37:22 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C45C0E413DA for ; Tue, 17 Oct 2017 17:37:22 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id 2DDF076AC1 for ; Tue, 17 Oct 2017 17:37:21 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Tue, 17 Oct 2017 19:37:14 +0200 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id B7C45C0D-4740-4ADC-927A-EBCDBBFFBB65.1 envelope-from (authenticated bits=0); Tue, 17 Oct 2017 19:37:12 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: error instaling any ports From: Rainer Duffner In-Reply-To: Date: Tue, 17 Oct 2017 19:35:39 +0200 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Denis Granato X-Mailer: Apple Mail (2.3124) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=15 total_conn=5 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 4179, bad: 1, connections: 4618, history: 4178, asn_score: 712, asn_connections: 734, asn_good: 712, asn_bad: 0, pass:asn, asn_all_good, relaying X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 17:37:22 -0000 > Am 17.10.2017 um 19:29 schrieb Denis Granato : >=20 > Hello everyone >=20 > I have a 9.1 freebsd server, and every ports I try to install I get > the follow error >=20 >=20 >=20 >=20 >=20 >=20 >=20 > *server# cd /usr/ports/devel/subversionserver# make install > clean"/usr/ports/Mk/bsd.port.mk ", line 1045: = Unknown > directiveUnknown modifier 't'Variable .CURDIR is recursive.server# * > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" Is this a recent ports-tree? FreeBSD 9.1 has been out of support for probably the better part of = three years. No chance a current ports-tree is usable on it. If for whatever reason you insist on staying with 9.1, you should use a = ports-tree from 9.2-RELEASE or maybe 9.3-RELEASE. From owner-freebsd-stable@freebsd.org Tue Oct 17 17:44:21 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1BD06E418B8 for ; Tue, 17 Oct 2017 17:44:21 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A4EE5770E8 for ; Tue, 17 Oct 2017 17:44:20 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id u138so5407307wmu.5 for ; Tue, 17 Oct 2017 10:44:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eWtgSaHzfR0rnPBYjox2ELjKAHuA3oDu8Jb9gSsE8D0=; b=XdhPT0i9o+rHXtMHfSmE4CDo0KgWekhBplyr4m5m/9E6X+ZAYOE24g4QqvAGRATZdj LlGcNZPKgnqI4L0sjo81gyIwoqS7CiiOXxwTl1GsB+ZhxnhEp4zkgp3fZ0CudziCaWLX gYzxHgBn4SGUoboil5TrWHNn/KdC++o3LXeOxewdeiaGbuekDxXcpLSVAUnl9kzq8JAI DFGobCIfwFRUjyWOOhzKvUWaz4cOmX70WnOtNCLTFpgjdHfMZ0QTPhVqEy0Bs8vbncQr qgmZ6gvQsjYzY9uaqVwWxEglLlLch/TxR/I5mU3Ob89rRDAP+UIqJ+oqvdRhgALauHg4 ReUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=eWtgSaHzfR0rnPBYjox2ELjKAHuA3oDu8Jb9gSsE8D0=; b=a1PUniaJcvL2UPVYkYgAtQnhoYRCB8wpVl7A7w5cFA9AJLSN56G8pj4zCFQAQCsQbB /Fh1+mdpuevFewt5X4LeFwLj4lrpiMFNyjLafzlKUUXqW6W/kPfCt7FTN/U2s2kfbC3w 6M5w2PgyuoarkISmOMa19sFjda3OIEly8s3uZO9HeVO9CaN/uOWBJLf5gycgKuXZz1xH xzAldL0QJ2vyaJ6IJXbPR7aPw2e/7AXU0qb2ysS36Iokl5szP5jUTOXbW3o9xJVtJCcB RdFAPbLeERjv4KP+2BvvvB9cVI0SiRrNpHfWIs2LQtXECV11bdc2dpQPUz1vzbdafPox paNg== X-Gm-Message-State: AMCzsaUOzrbcOBRasUVIFRZfTRPYKHbV3yT0PSxisb4paoTZ2VnwvmhF FGJbvYScGdEq4U0vgOFS8/gpnh6rHHVMNneWKv0= X-Google-Smtp-Source: AOwi7QAjaJF/vH4e2/cidhTC+Qd9OAPigFLP9RxqwjNKsZ0l8cRC/OHrRodoetiAebvVL49Cl/0rUhUX4lUyHINtmAg= X-Received: by 10.80.186.33 with SMTP id g30mr18348938edc.206.1508262259105; Tue, 17 Oct 2017 10:44:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.216.6 with HTTP; Tue, 17 Oct 2017 10:43:48 -0700 (PDT) In-Reply-To: <20171017173258.GZ86601@home.opsec.eu> References: <20171017173258.GZ86601@home.opsec.eu> From: Denis Granato Date: Tue, 17 Oct 2017 15:43:48 -0200 Message-ID: Subject: Re: error instaling any ports To: Kurt Jaeger Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 17:44:21 -0000 Hi Kurt Yes, I need help, its exactly what Im trying to do, upgrade to a newer version tks On Tue, Oct 17, 2017 at 3:32 PM, Kurt Jaeger wrote: > Hi! > > > I have a 9.1 freebsd server, and every ports I try to install I get > > the follow error > > 9.1 is no longer supported. Any chance to upgrade ? Do you need > help to upgrade that box ? > > -- > pi@opsec.eu +49 171 3101372 3 years to > go ! > From owner-freebsd-stable@freebsd.org Tue Oct 17 17:47:06 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C7A7E41A5C for ; Tue, 17 Oct 2017 17:47:06 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 00A2C77371 for ; Tue, 17 Oct 2017 17:47:05 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e4VxM-000GBv-Em; Tue, 17 Oct 2017 19:47:08 +0200 Date: Tue, 17 Oct 2017 19:47:08 +0200 From: Kurt Jaeger To: Denis Granato Cc: freebsd-stable@freebsd.org Subject: Re: error instaling any ports Message-ID: <20171017174708.GA86601@home.opsec.eu> References: <20171017173258.GZ86601@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 17:47:06 -0000 Hi! > Yes, I need help, its exactly what Im trying to do, upgrade > to a newer version So, what does uname -a say ? What does freebsd-version -ku say ? Can you try to do these steps to get to a slightly newer version first ? freebsd-update -r 9.3-RELEASE upgrade # installation kernel freebsd-update install shutdown -r now # installation userspace freebsd-update install # pkg-update freebsd-update install -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-stable@freebsd.org Tue Oct 17 17:54:56 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57710E41EC9 for ; Tue, 17 Oct 2017 17:54:56 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DC53E779FA for ; Tue, 17 Oct 2017 17:54:55 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id b189so5410231wmd.4 for ; Tue, 17 Oct 2017 10:54:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=K4CAa93KhB4rKmpzoOf1547O9Nr5nDwh/GPPWaUG/ME=; b=d2rwKgVFZ51zInyMaJt47EXACb4xPUlxgRgbxre96X7HgWephyKHYtl19U2epBScQ8 fdMpNbZBgUSD1g2LjG1ulnJ2+qhN6tQ27/a5vGub5zGQvC3mKDJXemxju0l7F4Fug9XC CgsnHIYnh/Fo5k5pjjLZ/HdRKIZDwc3Qk1yK/bCeN0XVewz2cTxbIZ5FW99WHJFhck7U BynQ22q8OBXUgO2k4LvRwQLwA3GFnSFnyj0C2qrCM0LwFm0qCr/I76pL4m+RwlnASibu Sj68WG8BN+hAYRooGvZ8D5lg9nTl5yfXs6vvuuB9+5czEQ1xpdlgHPiygUQMLvWTC3Oh QwzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=K4CAa93KhB4rKmpzoOf1547O9Nr5nDwh/GPPWaUG/ME=; b=clKye3K0jfewUUWEP/fDSjxJXRC98SQSW37nOt2XnaZeVAv+rgE5b7f3s8XaLvAeBp K4BdD0QBFsOrH5197NRhqg/dfdtnq23dzd2JMuPwaOEIRMKUPcEtOwk6Sdih1M1b0cAm mBwOgI7tQn4CfDLt5tPmrcnDlRSHlfbisUtsQ2W+yIYpRkgwC6zs4lLKKabJmAuGUhAZ MueIFhYtapng/R0e7znoYJyZ+4jUdnIC0ZPcGnccR0fv030yzjntHz7lWOfFhggiCIaO +rKBM89JakwslJnAKo51Ifg+aFSVJ8J25Dff8SDO77nQvFr6RVst7Ac87ErudEBl5jls 0gdQ== X-Gm-Message-State: AMCzsaWl2g59Me4u2GkA/piD52cVXAGUKDLhpJqY/ZAa1zILYVFNwKt9 iHdaDxPN6L3xy/95FyUG3mVxRCdxRAe5T76caXlJYg== X-Google-Smtp-Source: AOwi7QBliJjSyCEJMQnLXhm66zaGM8vDigPtILF0XEuq4ispZJUwVMEAVlwEz/odxohICsTJhA/DQBzOF2WttUp/qtA= X-Received: by 10.80.222.130 with SMTP id c2mr18303763edl.218.1508262894260; Tue, 17 Oct 2017 10:54:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.216.6 with HTTP; Tue, 17 Oct 2017 10:54:23 -0700 (PDT) In-Reply-To: <20171017174708.GA86601@home.opsec.eu> References: <20171017173258.GZ86601@home.opsec.eu> <20171017174708.GA86601@home.opsec.eu> From: Denis Granato Date: Tue, 17 Oct 2017 15:54:23 -0200 Message-ID: Subject: Re: error instaling any ports To: Kurt Jaeger Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 17:54:56 -0000 > So, what does > > uname -a > > > > *server# uname -aFreeBSD server.avgroup.loc 9.1-PRERELEASE FreeBSD > 9.1-PRERELEASE #0 r238721: Mon Jul 23 17:34:45 BRT 2012 > root@server.avgroup.loc:/usr/obj/usr/stable9/sys/AVVIO_FW i386You have new > mail.* > > What does > > freebsd-version -ku > > *dont have this command* > > Can you try to do these steps to get to a slightly newer version first ? > > freebsd-update -r 9.3-RELEASE upgrade > *server# freebsd-update -r 9.3-RELEASE upgradeLooking up update.freebsd.org mirrors... 3 mirrors found.Fetching public key from update6.freebsd.org... failed.Fetching public key from update5.freebsd.org... failed.Fetching public key from update4.freebsd.org... failed.No mirrors remaining, giving up* # installation kernel > freebsd-update install > > shutdown -r now > # installation userspace > freebsd-update install > # pkg-update > freebsd-update install > > -- > pi@opsec.eu +49 171 3101372 3 years to > go ! > From owner-freebsd-stable@freebsd.org Tue Oct 17 19:11:44 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03CDEE44BB6 for ; Tue, 17 Oct 2017 19:11:44 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B322F7F192 for ; Tue, 17 Oct 2017 19:11:43 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e4XHF-000GRC-8C; Tue, 17 Oct 2017 21:11:45 +0200 Date: Tue, 17 Oct 2017 21:11:45 +0200 From: Kurt Jaeger To: Denis Granato Cc: freebsd-stable@freebsd.org Subject: Re: error instaling any ports Message-ID: <20171017191145.GB86601@home.opsec.eu> References: <20171017173258.GZ86601@home.opsec.eu> <20171017174708.GA86601@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2017 19:11:44 -0000 Hi! > > uname -a [...] > > *server# uname -aFreeBSD server.avgroup.loc 9.1-PRERELEASE FreeBSD So you have a PRERELEASE version and you have a custom kernel. Do you know why that is ? Any specific change that needs to be in that kernel config ? Please check if you have a 'svn' binary somewhere, because it looks like you need to do a source upgrade first. rm -rf /usr/obj /usr/src mkdir /usr/src cd /usr/src svn checkout https://svn.freebsd.org/base/release/9.3.0/ . make buildworld make buildkernel make installkernel make installworld mergemaster -UiP shutdown -r now cd /usr/src make check-old make delete-old make delete-old-libs > *server# freebsd-update -r 9.3-RELEASE upgradeLooking up update.freebsd.org > mirrors... 3 mirrors found.Fetching public key > from update6.freebsd.org... failed.Fetching public key from > update5.freebsd.org... failed.Fetching public key from > update4.freebsd.org... failed.No mirrors remaining, giving up* Well, freebsd-update only works on GENERIC kernels and systems, so your first step needs to be a source upgrade. Please note: Your binaries from 9.1-PRE will work on 9.3, and probably on 10.x, so no need to worry about the packages installed for now. You can rebuild your ports when you're on 10.x. -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-stable@freebsd.org Wed Oct 18 00:01:09 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 73F89E4AE7D for ; Wed, 18 Oct 2017 00:01:09 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [150.101.137.129]) by mx1.freebsd.org (Postfix) with ESMTP id 0FA113B1B for ; Wed, 18 Oct 2017 00:01:08 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from 220-253-32-111.dyn.iinet.net.au (HELO leader.local) ([220.253.32.111]) by ipmail06.adl2.internode.on.net with ESMTP; 18 Oct 2017 10:25:59 +1030 Subject: Re: error instaling any ports To: Denis Granato Cc: freebsd-stable@freebsd.org References: <20171017173258.GZ86601@home.opsec.eu> <20171017174708.GA86601@home.opsec.eu> <20171017191145.GB86601@home.opsec.eu> From: Shane Ambler Message-ID: <8bdf688b-6dc6-0632-4e7e-6f21bfd88237@ShaneWare.Biz> Date: Wed, 18 Oct 2017 10:25:56 +1030 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20171017191145.GB86601@home.opsec.eu> Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 00:01:09 -0000 On 18/10/2017 05:41, Kurt Jaeger wrote: > Please note: Your binaries from 9.1-PRE will work on 9.3, and probably on > 10.x, so no need to worry about the packages installed for now. > > You can rebuild your ports when you're on 10.x. > If you have trouble running anything after the system upgrade, installing misc/compat9x should resolve the issues until you get your ports updated. -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-stable@freebsd.org Wed Oct 18 10:05:40 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25203E335FA for ; Wed, 18 Oct 2017 10:05:40 +0000 (UTC) (envelope-from maurizio.vairani@cloverinformatica.it) Received: from smtpcmd11116.aruba.it (smtpcmd11116.aruba.it [62.149.156.116]) by mx1.freebsd.org (Postfix) with ESMTP id 692DB73025 for ; Wed, 18 Oct 2017 10:05:38 +0000 (UTC) (envelope-from maurizio.vairani@cloverinformatica.it) Received: from host60-31-static.11-79-b.business.telecomitalia.it ([79.11.31.60]) by smtpcmd11.ad.aruba.it with bizsmtp id NxqW1w00o1HplQX01xqWY2; Wed, 18 Oct 2017 11:50:31 +0200 Received: from [192.168.0.60] (maurizio-pc [192.168.0.60]) by host60-31-static.11-79-b.business.telecomitalia.it (Postfix) with ESMTP id 74D0864C72 for ; Wed, 18 Oct 2017 11:50:30 +0200 (CEST) To: FreeBSD stable From: Maurizio Vairani Subject: Cosmetic bug in TOP(1) on i386 Message-ID: <9432b431-0bad-cada-3c2b-47db8eb27037@cloverinformatica.it> Date: Wed, 18 Oct 2017 11:50:30 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Language: it-IT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aruba.it; s=a1; t=1508320231; bh=iFQyESc0/y3XV5lwm5SwPoDtpTbG9piazsK6YWUtaE8=; h=To:From:Subject:Date:MIME-Version:Content-Type; b=DnKtwVg3sIkreGAODd4gHCjVBYvhb0g1CsM4xl9IRaXKIDUnauMf2r/mrIMr4Ry9R wnmWvaq6/exoL3h0J0v6fHG+Gn/U+nxg3opTx1f3LrGmADgA0KYp1bIWHf510xMuG7 X9dlnuEcIOdT+PRPy0r7B5BTGjj7UKBQJvTe32U3EQje4/oolpgmUmfqLwY3Qfg++O LdquV3qBimTl6JcVzlusl5DDJE4JQpxabdNx2Cnz8qtXp1dr+d9zw8HnjAVXqOI4IJ dfVLVhijCFCisD8nY2LaoN/O+FgX8e9DFWIebnZBzN1SLfGArk9g4wjWbjrHlsNd1O aptXJvNiSDTiA== Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 10:05:40 -0000 Running: # uname -a                                                                                                                                                          FreeBSD qbic 11.1-RELEASE-p1 FreeBSD 11.1-RELEASE-p1 #0: Wed Aug  9 11:17:49 UTC 2017     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386 after some minutes running top, I can read: last pid:   853;  load averages:  0.01,  0.09,  0.07                       up 0+00:08:18  14:38:05 27 processes:  1 running, 26 sleeping CPU:  0.0% user,  0.0% nice,  2.2% system,  0.8% interrupt, 97.0% idle Mem: 24M Active, 3980K Inact, 79M Wired, 3137M Free ARC: 36M Total, 17M MFU, 18M MRU, 149K Anon, 870K Header, 800K Other         21ì¿¿20mpressed, 352M Uncompressed, 16.94:1 Ratio Swap: Seconds to delay:  PID USERNAME    THR PRI NICE   SIZE    RES STATE   C   TIME    WCPU COMMAND  839 root          1  20    0  7328K  2160K CPU0    0   0:00   0.04% top where the second ARC line is corrupted. Pressing Ctrl-L corrects the ARC lines. From owner-freebsd-stable@freebsd.org Wed Oct 18 10:13:31 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80E3CE33A1B for ; Wed, 18 Oct 2017 10:13:31 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 12DAB73493 for ; Wed, 18 Oct 2017 10:13:31 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: by mail-wm0-x231.google.com with SMTP id i124so9146217wmf.3 for ; Wed, 18 Oct 2017 03:13:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=iKT+CN95Vd9w+eBpMp2VsmapSdL6neCy8mSAabbwLEw=; b=F/kl8Ep9x3M8zfwcovoPniVseqS+81Tfk2g3yyfM/9mCDVOlqfZcdLtHKukM0Pc2SL YBaG4CGvEB9zfpjs+6o7/nWpFBDK7s74G/Y07YmqiqLdOryQwRGUESjC5SyvfpeVMQAp 4lmsmOPYejzejBTHtOIU6lEInsYiHr0DfIPUOLg86p7KkClLe8z0d2iW7DK4J9rhjmRf 0PTNCn7rSG/5fxsBRXajDLPd0F0okorMaTIBBvlSQ9MvwYr690Bt0WclMfVFI0xBRoe/ DqkZjQWGj36ibxpb11zEsHUVrId7ZaYcMPz9wc1vShk94TB1sEI59iGaYwA4Hu7dM8/R Kq/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=iKT+CN95Vd9w+eBpMp2VsmapSdL6neCy8mSAabbwLEw=; b=CZO1K7elfMfxx3QDu+xAznEtrNwwsZZPwJxEPBzm6ju251xr/ICEoJ71IE66fmohEv psqLYwm/8dxOdkTvKRdby+k+9ls20Br0RpwBRE+OJmVrFNhWbldjqem1TIBZAjW774dD jfjmgs5GJ+CR42e3oiFVV5vm+Xd+JLDaEXJ5iofQOo18IZ/LTptnBDH1vy7yNajXVCOg wWxb1U3XdGg9E2piCzDXafYS+DuCKdelxcXcskC7DVXJHpqSuqcrr7cSJClNjprKWZme UblEhBP17LeFKuu51DXyf8f2kBZ/8cToOqR/bq/aQE9VASshQtrZv5JggybraAkgkKYv RnhA== X-Gm-Message-State: AMCzsaVf3z4AlW7cIWQAnaShUvj5K8bh/5iTn3yhMk16kncExtrUA0Nc i1umhdWwofTtJhEkRVtkXLudXDobx/tkGOzPEuo= X-Google-Smtp-Source: AOwi7QB6SF54Jd1nLJxEMJCEf4o7jMc3vkwNhLOyRmOwJmfj/VpnodoHb9h/2koN7uozaqrwI2I5zaPTPp41Z1zacnk= X-Received: by 10.80.222.130 with SMTP id c2mr20789254edl.218.1508321609504; Wed, 18 Oct 2017 03:13:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.216.6 with HTTP; Wed, 18 Oct 2017 03:12:59 -0700 (PDT) In-Reply-To: <20171017191145.GB86601@home.opsec.eu> References: <20171017173258.GZ86601@home.opsec.eu> <20171017174708.GA86601@home.opsec.eu> <20171017191145.GB86601@home.opsec.eu> From: Denis Granato Date: Wed, 18 Oct 2017 08:12:59 -0200 Message-ID: Subject: Re: error instaling any ports To: Kurt Jaeger Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 10:13:31 -0000 thanks guys , I wil try and let you know about the kernel, I think was for ipfw or something On Tue, Oct 17, 2017 at 5:11 PM, Kurt Jaeger wrote: > Hi! > > > > uname -a > [...] > > > *server# uname -aFreeBSD server.avgroup.loc 9.1-PRERELEASE FreeBSD > > So you have a PRERELEASE version and you have a custom kernel. > > Do you know why that is ? Any specific change that needs to > be in that kernel config ? > > Please check if you have a 'svn' binary somewhere, because it looks > like you need to do a source upgrade first. > > rm -rf /usr/obj /usr/src > mkdir /usr/src > cd /usr/src > svn checkout https://svn.freebsd.org/base/release/9.3.0/ . > make buildworld > make buildkernel > make installkernel > make installworld > mergemaster -UiP > shutdown -r now > cd /usr/src > make check-old > make delete-old > make delete-old-libs > > > *server# freebsd-update -r 9.3-RELEASE upgradeLooking up > update.freebsd.org > > mirrors... 3 mirrors found.Fetching public > key > > from update6.freebsd.org... failed.Fetching public key from > > update5.freebsd.org... failed.Fetching public key from > > update4.freebsd.org... failed.No mirrors remaining, giving up* > > Well, freebsd-update only works on GENERIC kernels and systems, so > your first step needs to be a source upgrade. > > Please note: Your binaries from 9.1-PRE will work on 9.3, and probably on > 10.x, so no need to worry about the packages installed for now. > > You can rebuild your ports when you're on 10.x. > > -- > pi@opsec.eu +49 171 3101372 3 years to > go ! > From owner-freebsd-stable@freebsd.org Wed Oct 18 12:20:16 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E682EE375BF for ; Wed, 18 Oct 2017 12:20:16 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ABFF976F03 for ; Wed, 18 Oct 2017 12:20:16 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e4nKZ-000IoQ-20 for freebsd-stable@freebsd.org; Wed, 18 Oct 2017 14:20:15 +0200 Date: Wed, 18 Oct 2017 14:20:15 +0200 From: Kurt Jaeger To: freebsd-stable@freebsd.org Subject: programm to edit rc.conf key/values ? Message-ID: <20171018122014.GD86601@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 12:20:17 -0000 Hi! I vaguely remember that there's a new way to edit the content of /etc/rc.conf via some command, to be used in scripting system-setups. Can someone point me into the right direction ? -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-stable@freebsd.org Wed Oct 18 12:30:02 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7A5FE37BF5 for ; Wed, 18 Oct 2017 12:30:02 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (vm1982.vellance.net [79.99.187.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5C9B3776B2 for ; Wed, 18 Oct 2017 12:30:02 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (localhost [127.0.0.1]) by vm1982.vellance.net (Postfix) with ESMTP id 4CEA1201AB for ; Wed, 18 Oct 2017 14:24:35 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1508329475; bh=KmzJLQJPsZXg9OevPWwQkn+eYQPEwBdx2fmxInmMn6Y=; h=Subject:To:References:From:Date:In-Reply-To; b=rPypvqlfuc0eyA5pM+leafjuvIXMLZpnuqCM7w9rAuxbOP+wAvZLCY/FG3CJQY0t5 sg8JmGlQ0i2Ejs56bh08DvgwP9X9SMqG3SN7atlIpmSYrdNfAfo8nmUNee97R1Bqdt owf0gcKPebl11r9nHbVTvEzDDuCsirv9aHbv08NZIpTq5c6gkT+FuuEnayvHvEFiMg Ic2SxuMduwnLO8Ald9PTHxDAFOKqY4Uryaha9hVRBB2379SR3MgYCfUIjEnDciOL8a k826CkaX3CmD6KXUp9RNL8l+pENnyRJx5HfDtt9oWHpYzIEPQkC9yQbIJQl9wrpPz5 IqQPRCCQTvY/5JG6OaIU5FxNEW9TXwRLmLe2klV6aCJmOQifbqjF9YcqxYpgaHc7Tu 5pJsms7OO4O6eB8x1x+Nb6qhdsK32VK4pOQjz2SGFgw0+kL08IgIfA46pTg2feso1h JzweQcnxvl0LD5ECp6XIaa6+1NDbQZpryu4FiwGkcQDrja3L2UPcGkcNMWVDmqAkGQ RfzJWF+Ij8oNY4lGhXfctuTJHRxceh904GRB38X36PwKELAK14lVJkExFH84lS0iGf TJS3RngtUD4CGcc7lGVkS5ve7pXZuW/LwC4TtoJR8jNfPEEI8v5lCzw2gMYFjNG2uN ASb6+x3JvlhnxMWVSLnD2o6Y= Received: from vm1982.vellance.net (localhost [127.0.0.1]) by vm1982.vellance.net (Postfix) with ESMTP id B99CD2013A for ; Wed, 18 Oct 2017 14:24:23 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1508329475; bh=KmzJLQJPsZXg9OevPWwQkn+eYQPEwBdx2fmxInmMn6Y=; h=Subject:To:References:From:Date:In-Reply-To; b=rPypvqlfuc0eyA5pM+leafjuvIXMLZpnuqCM7w9rAuxbOP+wAvZLCY/FG3CJQY0t5 sg8JmGlQ0i2Ejs56bh08DvgwP9X9SMqG3SN7atlIpmSYrdNfAfo8nmUNee97R1Bqdt owf0gcKPebl11r9nHbVTvEzDDuCsirv9aHbv08NZIpTq5c6gkT+FuuEnayvHvEFiMg Ic2SxuMduwnLO8Ald9PTHxDAFOKqY4Uryaha9hVRBB2379SR3MgYCfUIjEnDciOL8a k826CkaX3CmD6KXUp9RNL8l+pENnyRJx5HfDtt9oWHpYzIEPQkC9yQbIJQl9wrpPz5 IqQPRCCQTvY/5JG6OaIU5FxNEW9TXwRLmLe2klV6aCJmOQifbqjF9YcqxYpgaHc7Tu 5pJsms7OO4O6eB8x1x+Nb6qhdsK32VK4pOQjz2SGFgw0+kL08IgIfA46pTg2feso1h JzweQcnxvl0LD5ECp6XIaa6+1NDbQZpryu4FiwGkcQDrja3L2UPcGkcNMWVDmqAkGQ RfzJWF+Ij8oNY4lGhXfctuTJHRxceh904GRB38X36PwKELAK14lVJkExFH84lS0iGf TJS3RngtUD4CGcc7lGVkS5ve7pXZuW/LwC4TtoJR8jNfPEEI8v5lCzw2gMYFjNG2uN ASb6+x3JvlhnxMWVSLnD2o6Y= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on vm1982.vellance.net X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.1 Received: from quanza-qhq-pr11.q (engineering.quanza.net [91.208.87.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by vm1982.vellance.net (Postfix) with ESMTPSA for ; Wed, 18 Oct 2017 14:24:23 +0200 (CEST) Subject: Re: programm to edit rc.conf key/values ? To: freebsd-stable@freebsd.org References: <20171018122014.GD86601@home.opsec.eu> From: Ruben Message-ID: <8826cdb0-73e9-f525-62ba-22e1eb548ffa@osfux.nl> Date: Wed, 18 Oct 2017 14:24:22 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171018122014.GD86601@home.opsec.eu> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 12:30:02 -0000 sysrc nrpe2_enable="YES" for instance On 18/10/17 14:20, Kurt Jaeger wrote: > Hi! > > I vaguely remember that there's a new way to edit the content of > /etc/rc.conf via some command, to be used in scripting system-setups. > > Can someone point me into the right direction ? > From owner-freebsd-stable@freebsd.org Wed Oct 18 12:32:56 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 884AAE37EF2 for ; Wed, 18 Oct 2017 12:32:56 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4B15277A6B for ; Wed, 18 Oct 2017 12:32:56 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e4nWq-000IqK-Hg; Wed, 18 Oct 2017 14:32:56 +0200 Date: Wed, 18 Oct 2017 14:32:56 +0200 From: Kurt Jaeger To: Ruben Cc: freebsd-stable@freebsd.org Subject: Re: programm to edit rc.conf key/values ? Message-ID: <20171018123256.GF86601@home.opsec.eu> References: <20171018122014.GD86601@home.opsec.eu> <8826cdb0-73e9-f525-62ba-22e1eb548ffa@osfux.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8826cdb0-73e9-f525-62ba-22e1eb548ffa@osfux.nl> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 12:32:56 -0000 Hi! > sysrc nrpe2_enable="YES" > > for instance Yes, that's it! Thanks! man rc.conf and man rc need a pointer to this! -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-stable@freebsd.org Wed Oct 18 13:30:56 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B8077E392C4 for ; Wed, 18 Oct 2017 13:30:56 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout02.t-online.de (mailout02.t-online.de [194.25.134.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7C0BB7D90F for ; Wed, 18 Oct 2017 13:30:55 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd20.aul.t-online.de (fwd20.aul.t-online.de [172.20.26.140]) by mailout02.t-online.de (Postfix) with SMTP id 1CEAB41A409F for ; Wed, 18 Oct 2017 15:30:53 +0200 (CEST) Received: from Stefans-MBP-2.fritz.box (rSDb3aZDYhFX1cRCJ3tMOTWIplqfw1-WoQSxZ7q1YmNZQ6mEj5sMZaD9lqja6kKZS-@[84.154.120.44]) by fwd20.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1e4oQk-4K20cS0; Wed, 18 Oct 2017 15:30:42 +0200 Subject: Re: programm to edit rc.conf key/values ? To: freebsd-stable@freebsd.org References: <20171018122014.GD86601@home.opsec.eu> <8826cdb0-73e9-f525-62ba-22e1eb548ffa@osfux.nl> <20171018123256.GF86601@home.opsec.eu> From: Stefan Esser Message-ID: Date: Wed, 18 Oct 2017 15:30:42 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171018123256.GF86601@home.opsec.eu> Content-Type: text/plain; charset=windows-1252 Content-Language: de-DE Content-Transfer-Encoding: 7bit X-ID: rSDb3aZDYhFX1cRCJ3tMOTWIplqfw1-WoQSxZ7q1YmNZQ6mEj5sMZaD9lqja6kKZS- X-TOI-MSGID: ec18ca19-f260-4f09-ba59-448683121cbc X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 13:30:56 -0000 Am 18.10.17 um 14:32 schrieb Kurt Jaeger: > Hi! > >> sysrc nrpe2_enable="YES" >> >> for instance > > Yes, that's it! Thanks! > > man rc.conf and man rc need a pointer to this! Yes, I also once searched for sysrc and had appreciated references in some other man pages ... Therefore, I've just added those references to rc.8 and rc.conf.5, as you suggested. I forgot to set a MFC reminder, but I'll see that these references are merged to 10 and 11 before the end of the month. Regards, STefan From owner-freebsd-stable@freebsd.org Wed Oct 18 16:35:43 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4113E3DB95 for ; Wed, 18 Oct 2017 16:35:43 +0000 (UTC) (envelope-from peter@pean.org) Received: from system.jails.se (system.jails.se [52.16.239.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 716BE84FF1 for ; Wed, 18 Oct 2017 16:35:42 +0000 (UTC) (envelope-from peter@pean.org) Received: from lune.pean.org (213-67-100-148-no110.tbcn.telia.com [213.67.100.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by system.jails.se (Postfix) with ESMTPSA id A84BD11FDDC; Wed, 18 Oct 2017 18:35:33 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Subject: Re: 802.1X authenticator for FreeBSD From: =?utf-8?Q?Peter_Ankerst=C3=A5l?= In-Reply-To: Date: Wed, 18 Oct 2017 18:35:32 +0200 Cc: FreeBSD Stable Content-Transfer-Encoding: quoted-printable Message-Id: <2D461E1D-895F-4D31-9834-A40DEF02F121@pean.org> References: To: Chris Ross X-Mailer: Apple Mail (2.3445.1.7) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 16:35:43 -0000 > On 17 Oct 2017, at 22:27, Chris Ross wrote: >=20 >=20 > wpa_supplicant is the client we use at work, on Linux systems. But, = it=E2=80=99s also the tool described in the FreeBSD wireless = configuration pages, so I know it can be used there. >=20 > I haven=E2=80=99t tried FreeBSD with wired 802.1x myself, but just a = thought I had. >=20 > - Chris >=20 Its my understanding that wpa_supplicant is actually a working client in = FreeBSD. But I=E2=80=99m looking for the server side of this.=20 It would be just fine if it worked just like hostapd (control access of = one nic) and dont have any control over switchports or whatever. Another = nice way of doing it would be to have some sort of integration with = authpf or pf itself.= From owner-freebsd-stable@freebsd.org Wed Oct 18 17:03:13 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BE3BE3ED23 for ; Wed, 18 Oct 2017 17:03:13 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2a00:14b0:4200:32e0::1ea]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gilb.zs64.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F1D791ECB for ; Wed, 18 Oct 2017 17:03:12 +0000 (UTC) (envelope-from stb@lassitu.de) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 8D9D019C6EC; Wed, 18 Oct 2017 17:03:09 +0000 (UTC) From: Stefan Bethke Message-Id: <4F45AC20-57F9-4246-836E-4F1C1D01FAC2@lassitu.de> Content-Type: multipart/signed; boundary="Apple-Mail=_48DC4D18-9080-4AC5-A616-8CD416910B8A"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Subject: Re: 802.1X authenticator for FreeBSD Date: Wed, 18 Oct 2017 19:03:07 +0200 In-Reply-To: <2D461E1D-895F-4D31-9834-A40DEF02F121@pean.org> Cc: Chris Ross , FreeBSD Stable To: =?utf-8?Q?Peter_Ankerst=C3=A5l?= References: <2D461E1D-895F-4D31-9834-A40DEF02F121@pean.org> X-Mailer: Apple Mail (2.3445.1.7) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 17:03:13 -0000 --Apple-Mail=_48DC4D18-9080-4AC5-A616-8CD416910B8A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > Am 18.10.2017 um 18:35 schrieb Peter Ankerst=C3=A5l : >=20 >=20 >=20 >> On 17 Oct 2017, at 22:27, Chris Ross = wrote: >>=20 >>=20 >> wpa_supplicant is the client we use at work, on Linux systems. But, = it=E2=80=99s also the tool described in the FreeBSD wireless = configuration pages, so I know it can be used there. >>=20 >> I haven=E2=80=99t tried FreeBSD with wired 802.1x myself, but just a = thought I had. >>=20 >> - Chris >>=20 > Its my understanding that wpa_supplicant is actually a working client = in FreeBSD. But I=E2=80=99m looking for the server side of this. >=20 > It would be just fine if it worked just like hostapd (control access = of one nic) and dont have any control over switchports or whatever. = Another nice way of doing it would be to have some sort of integration = with authpf or pf itself. I=E2=80=99m under the impression that the authenticator function in a = wired network is usually part of the switch, and the switch will talk to = some authentication server like RADIUS, giving it the port number of the = connected device and additional information. If FreeBSD had such a function, I think it would be limited to = point-to-point Ethernet links, 802.1x being a link-layer protocol. Stefan -- Stefan Bethke Fon +49 151 14070811 --Apple-Mail=_48DC4D18-9080-4AC5-A616-8CD416910B8A Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEzBAEBCgAdFiEEJ+hF98o4r3eU/HiPD885WK4W4sEFAlnniUsACgkQD885WK4W 4sGqGgf/eJor+Utv3d7hQhS0AQALyHSGxWAnWfPmqcICw8sqwj7bd95qLeSrgg+d PVNDG9PFd/XJGJUe1qGeiWXOR73S6oj1ByP074AJHkuaDEws6h9tdLzATQkhjSAi TvgiO/yEJu4ChXDoCucDQ07tdep8QTfwQee7H/KpXUuAq5xrd0fR9kZQ/6OUY7/e 6aZ8VFhDUg9YOsjMN508dtWV5fUFpk99aco9iebao++30MrZfsCj4W/vFDWQvtAk o/BN4hlVKPyOX/gsDWpSIiuIRN/Ztq5Pva5c51a/28aO7CgvdwX8jwOOHAFRvAv1 QewVZULwTzPxiQk1zrYkyotvi0o0FQ== =r9ZR -----END PGP SIGNATURE----- --Apple-Mail=_48DC4D18-9080-4AC5-A616-8CD416910B8A-- From owner-freebsd-stable@freebsd.org Wed Oct 18 17:10:10 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B28F7E3F082 for ; Wed, 18 Oct 2017 17:10:10 +0000 (UTC) (envelope-from peter@pean.org) Received: from system.jails.se (system.jails.se [IPv6:2001:470:6c08::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7A2E922B5 for ; Wed, 18 Oct 2017 17:10:10 +0000 (UTC) (envelope-from peter@pean.org) Received: from lune.pean.org (213-67-100-148-no110.tbcn.telia.com [213.67.100.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by system.jails.se (Postfix) with ESMTPSA id BAE92120221; Wed, 18 Oct 2017 19:10:07 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Subject: Re: 802.1X authenticator for FreeBSD From: =?utf-8?Q?Peter_Ankerst=C3=A5l?= In-Reply-To: <4F45AC20-57F9-4246-836E-4F1C1D01FAC2@lassitu.de> Date: Wed, 18 Oct 2017 19:10:06 +0200 Cc: Chris Ross , FreeBSD Stable Content-Transfer-Encoding: quoted-printable Message-Id: <2B2D49E0-F804-4557-9DB5-A915A8578070@pean.org> References: <2D461E1D-895F-4D31-9834-A40DEF02F121@pean.org> <4F45AC20-57F9-4246-836E-4F1C1D01FAC2@lassitu.de> To: Stefan Bethke X-Mailer: Apple Mail (2.3445.1.7) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 17:10:10 -0000 >=20 > I=E2=80=99m under the impression that the authenticator function in a = wired network is usually part of the switch, and the switch will talk to = some authentication server like RADIUS, giving it the port number of the = connected device and additional information. >=20 > If FreeBSD had such a function, I think it would be limited to = point-to-point Ethernet links, 802.1x being a link-layer protocol. >=20 Yes I know, but this is functional in hostapd for Linux and it would be = nice to have it in FreeBSD as well.=20 Thanks anyway!= From owner-freebsd-stable@freebsd.org Wed Oct 18 17:54:57 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28DC4E40157 for ; Wed, 18 Oct 2017 17:54:57 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 82C9063C85; Wed, 18 Oct 2017 17:54:55 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id v9IHsint049533; Thu, 19 Oct 2017 04:54:45 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Thu, 19 Oct 2017 04:54:44 +1100 (EST) From: Ian Smith To: Stefan Esser cc: freebsd-stable@freebsd.org Subject: Re: programm to edit rc.conf key/values ? In-Reply-To: Message-ID: <20171019044906.K34192@sola.nimnet.asn.au> References: <20171018122014.GD86601@home.opsec.eu> <8826cdb0-73e9-f525-62ba-22e1eb548ffa@osfux.nl> <20171018123256.GF86601@home.opsec.eu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 17:54:57 -0000 On Wed, 18 Oct 2017 15:30:42 +0200, Stefan Esser wrote: > Am 18.10.17 um 14:32 schrieb Kurt Jaeger: > > man rc.conf and man rc need a pointer to this! > > Yes, I also once searched for sysrc and had appreciated references > in some other man pages ... > > Therefore, I've just added those references to rc.8 and rc.conf.5, > as you suggested. > > I forgot to set a MFC reminder, but I'll see that these references > are merged to 10 and 11 before the end of the month. What's wrong with you, man? Suggestion to commit took almost an hour! :-) Ian From owner-freebsd-stable@freebsd.org Wed Oct 18 19:39:21 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 955CEE42558 for ; Wed, 18 Oct 2017 19:39:21 +0000 (UTC) (envelope-from spork@bway.net) Received: from smtp1.bway.net (smtp1.v6.bway.net [IPv6:2607:d300:1::27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 706B4673FA for ; Wed, 18 Oct 2017 19:39:21 +0000 (UTC) (envelope-from spork@bway.net) Received: from gaseousweiner.sporklab.com (pool-96-225-84-130.nwrknj.fios.verizon.net [96.225.84.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: spork@bway.net) by smtp1.bway.net (Postfix) with ESMTPSA id 6389995871; Wed, 18 Oct 2017 15:39:10 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: 802.1X authenticator for FreeBSD From: Charles Sprickman In-Reply-To: <2B2D49E0-F804-4557-9DB5-A915A8578070@pean.org> Date: Wed, 18 Oct 2017 15:39:07 -0400 Cc: Stefan Bethke , FreeBSD Stable , Chris Ross Content-Transfer-Encoding: quoted-printable Message-Id: <3F040A9B-B03F-4FD5-B1DC-70BD8AFCC829@bway.net> References: <2D461E1D-895F-4D31-9834-A40DEF02F121@pean.org> <4F45AC20-57F9-4246-836E-4F1C1D01FAC2@lassitu.de> <2B2D49E0-F804-4557-9DB5-A915A8578070@pean.org> To: =?utf-8?Q?Peter_Ankerst=C3=A5l?= X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2017 19:39:21 -0000 > On Oct 18, 2017, at 1:10 PM, Peter Ankerst=C3=A5l = wrote: >=20 >>=20 >> I=E2=80=99m under the impression that the authenticator function in a = wired network is usually part of the switch, and the switch will talk to = some authentication server like RADIUS, giving it the port number of the = connected device and additional information. >>=20 >> If FreeBSD had such a function, I think it would be limited to = point-to-point Ethernet links, 802.1x being a link-layer protocol. >>=20 >=20 > Yes I know, but this is functional in hostapd for Linux and it would = be nice to have it in FreeBSD as well.=20 I=E2=80=99m not seeing this in FreeBSD, but pfsense does claim to = support 802.1x for wifi. I just happen to be reading about radius (last I used it was for dialup) = for wifi auth and the quick overview on the radius side of things is = that the AP software sends your auth info as well as MAC and a bunch of = other stuff, and the radius server (much like dialup) sends back all = sorts of info beyond auth success/fail - session timeout, info on what = VLAN the client may be on, firewall policies, etc. Pretty cool stuff. Charles >=20 > Thanks anyway! > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Thu Oct 19 06:24:03 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F371E2D82C for ; Thu, 19 Oct 2017 06:24:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ua0-x22d.google.com (mail-ua0-x22d.google.com [IPv6:2607:f8b0:400c:c08::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B5F7D80C61 for ; Thu, 19 Oct 2017 06:24:02 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ua0-x22d.google.com with SMTP id s41so5243309uab.10 for ; Wed, 18 Oct 2017 23:24:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=PCwgQA2iKRR+an+lrKQ+NGxnvJWhk21POoRBx0XSCuM=; b=dxcsQ3Wq+tWe/1IxfyW5Ymd7YeW34XWFsdCqge3kHsvJw/i1J0GicsjXusbZNUmib2 ZlLk0wyB/DvBQco0Sron1A+zCrIrYdmSW9TF82ax07CAjcBBYZCaOXPTw9IUVRUGaNFd k2ULiFjDIk4JXL3l2Heaca3ry3ZqxLdFX9GLMiOUs/Ik4Bq8xwlRjLwpjaX2LdfE0DVm SMQWWf/GS9S/BJq+A8o2C8KoIaVZZSbP92sdvJzgSxfCO21s6Brauro2HPvYjyU+g6YI JlhoyAippbieLNiiDX2UADq5VK4fmDfsLghFQVIppNBLhs/qrNbtmS49mjVM1hVGSa7V 2Srw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=PCwgQA2iKRR+an+lrKQ+NGxnvJWhk21POoRBx0XSCuM=; b=PIapqAZm1DXw0b1q4jit528Dn7Zkchg+6TSF3tdwTBMM5wQyzI4TKRJc6GuoZ7gB1l z0i9LWZBVcERCxdilOCPQ+2sE8uuLtpKSNhDbQdJ4YCmMReRLO7QjcwUbmVoCUeTT65V rVrIptBv/cKOaVQVscaOJK+CuvLT3qtjFhrO6X1HhCmi8m7wd9rMnOqiAEh6oEybzozx 3kqGCYrLcDr9SeDfqZ/NNLb+ulwaNUEPNTnGy7+FtfCYsPKiWQtO4DOxKWa05daPdFd+ E4ZVF3Bq6kZJnInrNrrVJYmgMeONLBa9+pqYSMqV6ALaaj+AfUtj1jgjb8PC4DtyeseM PTew== X-Gm-Message-State: AMCzsaVeeM1GfcGRu1BAuktBAkPSx15+2PeUJ1Be+OE63GeRaZf82yFu G1tUfKrnI95NfTxjrE166ig6r/BTLBFtnUifli4qHxF+ X-Google-Smtp-Source: ABhQp+T6zKW1Q3x9cK16whBhFNcwg6uFY1DkJbXk8+ESYhjTHkYnwwjIvn5oiWsy3thsS/p6JjpXyLz9UNwTqrYKCaw= X-Received: by 10.176.27.108 with SMTP id n44mr392518uai.47.1508394241800; Wed, 18 Oct 2017 23:24:01 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.85.8 with HTTP; Wed, 18 Oct 2017 23:24:01 -0700 (PDT) In-Reply-To: References: <20171017173258.GZ86601@home.opsec.eu> <20171017174708.GA86601@home.opsec.eu> <20171017191145.GB86601@home.opsec.eu> From: Kevin Oberman Date: Wed, 18 Oct 2017 23:24:01 -0700 X-Google-Sender-Auth: WxCxDaa8WLqFuNFaqBbK86lh3oY Message-ID: Subject: Re: error instaling any ports To: Denis Granato Cc: Kurt Jaeger , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2017 06:24:03 -0000 On Wed, Oct 18, 2017 at 3:12 AM, Denis Granato wrote: > thanks guys , I will try and let you know > about the kernel, I think was for ipfw or something > No need for a custom kernel for this. If you configure ipfw in rc.conf as per the Handbook (29.4), it will load the module and your configuration using the GENERIC kernel. I might also point out that use of freebsd-update does NOT require that you run a GENERIC kernel. This is discussed in the Handbook (23.2). You MUST have a copy of the GENERIC kernel, either as your boot kernel or by placing a copy of the GENERIC kernel in /boot/GENERIC. (N.B. This is a file name, not a directory.) This does require rebuilding your custom kernel after the update is otherwise complete. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > > > On Tue, Oct 17, 2017 at 5:11 PM, Kurt Jaeger wrote: > > > Hi! > > > > > > uname -a > > [...] > > > > *server# uname -aFreeBSD server.avgroup.loc 9.1-PRERELEASE FreeBSD > > > > So you have a PRERELEASE version and you have a custom kernel. > > > > Do you know why that is ? Any specific change that needs to > > be in that kernel config ? > > > > Please check if you have a 'svn' binary somewhere, because it looks > > like you need to do a source upgrade first. > > > > rm -rf /usr/obj /usr/src > > mkdir /usr/src > > cd /usr/src > > svn checkout https://svn.freebsd.org/base/release/9.3.0/ . > > make buildworld > > make buildkernel > > make installkernel > > make installworld > > mergemaster -UiP > > shutdown -r now > > cd /usr/src > > make check-old > > make delete-old > > make delete-old-libs > > > > > *server# freebsd-update -r 9.3-RELEASE upgradeLooking up > > update.freebsd.org > > > mirrors... 3 mirrors found.Fetching public > > key > > > from update6.freebsd.org... failed.Fetching public key from > > > update5.freebsd.org... failed.Fetching public key from > > > update4.freebsd.org... failed.No mirrors remaining, giving up* > > > > Well, freebsd-update only works on GENERIC kernels and systems, so > > your first step needs to be a source upgrade. > > > > Please note: Your binaries from 9.1-PRE will work on 9.3, and probably on > > 10.x, so no need to worry about the packages installed for now. > > > > You can rebuild your ports when you're on 10.x. > > > > -- > > pi@opsec.eu +49 171 3101372 3 years > to > > go ! > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Thu Oct 19 16:59:10 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA027E408B6 for ; Thu, 19 Oct 2017 16:59:10 +0000 (UTC) (envelope-from melissa.brown@microinfodatasolutions.com) Received: from IND01-MA1-obe.outbound.protection.outlook.com (mail-ma1ind01hn0205.outbound.protection.outlook.com [104.47.100.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C4A7E70FB7 for ; Thu, 19 Oct 2017 16:59:08 +0000 (UTC) (envelope-from melissa.brown@microinfodatasolutions.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT3395813.onmicrosoft.com; s=selector1-microinfodatasolutions-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=1XfrJNh3uQCtgPbuPqlgXGwWqw6AeNmKykwywFiIPX0=; b=dfDQ0tnaedIE5jYoLMvpytalWMqAf6tpVJFKE0fsFRLKtQTCyFrAgkQldkrQyUO9BBaTy7Eis7OoVdEe6zIeRaquMroaPmHtZF4KoGwRm/mTpGLQLdcbVqtVfvRRAO5gZayVjQbVxo24VZ7RPzyWnlfKwRlW3IUul8vp5TgUkmk= Received: from BM1PR0101MB2051.INDPRD01.PROD.OUTLOOK.COM (10.174.221.138) by BM1PR0101MB2049.INDPRD01.PROD.OUTLOOK.COM (10.174.221.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.77.7; Thu, 19 Oct 2017 16:59:06 +0000 Received: from BM1PR0101MB2051.INDPRD01.PROD.OUTLOOK.COM ([fe80::f4e4:a7b1:bc7:bc01]) by BM1PR0101MB2051.INDPRD01.PROD.OUTLOOK.COM ([fe80::f4e4:a7b1:bc7:bc01%18]) with mapi id 15.20.0077.020; Thu, 19 Oct 2017 16:59:06 +0000 From: Melissa Brown To: "freebsd-stable@freebsd.org" Subject: SAP Users Info Thread-Topic: SAP Users Info Thread-Index: AdNI+3p/uQ/b/870THCY5jmnr1LlGg== Date: Thu, 19 Oct 2017 16:58:35 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=melissa.brown@microinfodatasolutions.com; x-originating-ip: [106.51.105.112] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BM1PR0101MB2049; 6:uimGOXpFDW3GeHrAnLGHkC8jN1xIK7g5D9bdsSZpdm2jlSWiyCSNrjjaWV+qQ3ScHPjhJZmV09KG9OZOukcCV5ej0oagn2LtuihztGVSunOX7+emhiM+of2+qNf0OuE1UIe8VQfEklwU6wjZqpSC78R8AaY2t343DiXLj34/J9H9GQ6Sp+eyfR/iYDGOAVLcvxkEQYQGDkweJlYb45a8Uwa4g9NzGtWSK31VxhxObaBGkQQoAMphD9/JhFnXoLCw+8DEwNy+KxYMHjpqmfDVquiPCKd1tnTVXBjweJvbHsnDMibJcSHMW6JdKzyEVkGT5tfE+iTvI1A2rTY3Fbu0MA==; 5:8ErzJE9VEww9ap4grNDYzsTH9GjnLThbl8XEAOTJXaHlkaZQuFjn/C8rrHvM5tFDyYiqwJVofyQ9V6ZZ5Xm1QC3JHm7afwlsxB+QxeWXFSEBfU6/VCKGbbPh8jI3RJrnNMNNCB0RTjDaJPWjIsTuI4PMG7QoYb/dGMDQS6QG2Io=; 24:uG4DdlE8bLT1NwQEEc6Hwwvi1fsGzGd2epOwaGIbNzcNSrSl4nQn88laP1K70pLm5HvnP4KhpAn0oe+lZ65V4Q==; 7:Vq2Q2I4vbqzUP7IEd+C4tg2BH0C8DlbdAu3yUe3tmCTzBbRCRQHbf8J5KoDaR+dZT4UeiepmyC1mMlp9DlZICXYt9YKeA4cvyY7vDcyallXKqZSPb/9nCtbWWWV8ux9MPLLu0TQrZgWYUNTTOouG8SfokMWiNjW7n0eGWsMBMx9ZNw9g7wcYMnjWpGfM8gQpxWFq6OyOitKMNHu0AlcpOEdBdfxqqzPStQ/VZot2HcM= x-ms-office365-filtering-correlation-id: 57c2f797-d209-4d18-c134-08d51712b558 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254171)(2017082002094)(4534019)(4602075)(4603075)(4627075)(201702281549075)(2017052603199)(201703131423094); SRVR:BM1PR0101MB2049; x-ms-traffictypediagnostic: BM1PR0101MB2049: x-exchange-antispam-report-test: UriScan:(21748063052155); x-microsoft-antispam-prvs: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(10201501046)(100000703101)(100105400095)(93006095)(93001095)(3002001)(6041248)(20161123558100)(201703131423075)(201703061421075)(201703151056150)(201703061814153)(20161123564025)(20161123562025)(2016111802025)(20161123560025)(6059035)(20161123555025)(6072148)(6043046)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BM1PR0101MB2049; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BM1PR0101MB2049; x-forefront-prvs: 0465429B7F x-forefront-antispam-report: SFV:SPM; SFS:(10009020)(6009001)(376002)(346002)(448600002)(199003)(189002)(5630700001)(50986999)(3480700004)(8676002)(74316002)(2351001)(586005)(8936002)(106356001)(105586002)(7696004)(81156014)(5640700003)(81166006)(14454004)(3280700002)(6666003)(5660300001)(86362001)(2906002)(45080400002)(6916009)(6436002)(25786009)(3660700001)(6506006)(33656002)(6116002)(2900100001)(101416001)(54356999)(38610400001)(68736007)(189998001)(9476002)(9686003)(55016002)(7736002)(5250100002)(7116003)(102836003)(54896002)(9326002)(66066001)(3846002)(97736004)(53936002)(9406002)(6306002)(9456002)(2501003)(790700001)(8160700003); DIR:OUT; SFP:1501; SCL:5; SRVR:BM1PR0101MB2049; H:BM1PR0101MB2051.INDPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: microinfodatasolutions.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:22 MIME-Version: 1.0 X-OriginatorOrg: microinfodatasolutions.com X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Oct 2017 16:58:35.5887 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: ab0c471b-08a3-49c1-bd6c-b6195e877d87 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BM1PR0101MB2049 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2017 16:59:10 -0000 Hi, Would you be interested in acquiring the list of customers or companies usi= ng SAP? We provide the Database across North America, EMEA, APAC and Latin America. List contains: Name, Company's Name, Phone Number, Job Title, Email address= , Complete Mailing address, Company revenue, size, Web address etc. We can provide contact list from any country/industry/title. We also have list of technology users like: PeopleSoft Intacct Microsoft Infor Sage Group SAP SE RAD Software JD Edwards QAD Infor XA ERP Intuit and Many more... Please review and let me know if you need more information. Await your response! Thanks Melissa Brown Demand Generation- Technology Database To opt out kindly reply back with 'unsu= bscribe' or 'leave out' From owner-freebsd-stable@freebsd.org Thu Oct 19 18:39:38 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FEB3E43E5A for ; Thu, 19 Oct 2017 18:39:38 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1267476A71 for ; Thu, 19 Oct 2017 18:39:37 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e5FjH-000MVn-EH; Thu, 19 Oct 2017 20:39:39 +0200 Date: Thu, 19 Oct 2017 20:39:39 +0200 From: Kurt Jaeger To: Denis Granato Cc: freebsd-stable@freebsd.org Subject: Re: error instaling any ports Message-ID: <20171019183939.GI86601@home.opsec.eu> References: <20171017173258.GZ86601@home.opsec.eu> <20171017174708.GA86601@home.opsec.eu> <20171017191145.GB86601@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2017 18:39:38 -0000 Hi! > I follow the steps (that Kurt sent with his help) > After the mergemaster -UiP > the server stop at boot, after this point (see pictures attached) Can you boot single-mode ? Can you boot the old kernel ? -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-stable@freebsd.org Thu Oct 19 18:40:44 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1DF3E43F8A for ; Thu, 19 Oct 2017 18:40:44 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 85DA076BF3 for ; Thu, 19 Oct 2017 18:40:44 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id i124so18171339wmf.3 for ; Thu, 19 Oct 2017 11:40:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xUkf7UuQmn4A0W4IgY5Hs4wI3XX6pGp59aNlGVmmYgo=; b=eCZYJOXZ7Vv2GO+4j+jLFRwnFrtBCA/woHk+dNG5qMsnfvcOR8+813yQFFNXVVD1rw 6hwCIN7NBN1CQ8y+lCsAtm2g3i0wZGWBF7vCLWUJC+XzSpRplLUO8ZNaSe1STJ09xyDK /GnaqruV9hfOIgi3F1pKZAQwrT+HzL0RQ0c6vgS3//Av4Vbrzyxsk+EZuOAPPS/oS1Z9 v8JZJO124tntevY0kdW8rU7i4NF6UhqsimZZWqrHLtk9A6K3wUaPZPVjSfoyvP9qBz1X y3Ro4N4OHROr7CTJb3rTRdd/yrp2uq3hUs0syOEkzD3FcbPWrTT7Kwo2tkW14bD6JWdR 3SPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xUkf7UuQmn4A0W4IgY5Hs4wI3XX6pGp59aNlGVmmYgo=; b=aECbI2Bx/OE1NI4E8oVLLXGcONmVMqyOhkuL+swVCw6h5VIMXkQHrJD3NzNfCCLGfQ 9mdSx3oyScqeLh060yk8Bq9kq2GLgQ4KMIXry0oXxisuxhhnOCN0W9rN9q5MdpfKqevk dWBr7sLsWUx61I7t7fhazLBvQ/ChxfXg+OdQAUFxqXfXfGl/O20ZzLR3y4gPS9Aftub9 9RTJoQ/9j/FrdcZQru+BGdyeKl+/ziyTxRTIQcOrDFzLTp1qiSvwYCrj2fbclk3F0lMJ X/Ji26q7Br8IRaFWthBgvFwHtmIYPi2IH5BCFR0wOcI1hWWfyu2b2e2dwHNgpHQ9aXek XTSw== X-Gm-Message-State: AMCzsaXqulfC7Ma3FGuvPIxZkC1B5QHhxy9x0KGCu2LhURTWvKnmcrnz TJVN5oaFihY9c6rSO/uvstgGmdBSB9U7p8Qs9AM= X-Google-Smtp-Source: ABhQp+TIl5+v/8n/rmTDqGecFm5CKIhYCLsvafYIgCi/OcLJm3dHiGX6slDVesyiJgNW/ZELWycGXlzbHkr7Lr2hRmw= X-Received: by 10.80.146.200 with SMTP id l8mr3452106eda.13.1508438442901; Thu, 19 Oct 2017 11:40:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.216.6 with HTTP; Thu, 19 Oct 2017 11:40:12 -0700 (PDT) In-Reply-To: <20171017191145.GB86601@home.opsec.eu> References: <20171017173258.GZ86601@home.opsec.eu> <20171017174708.GA86601@home.opsec.eu> <20171017191145.GB86601@home.opsec.eu> From: Denis Granato Date: Thu, 19 Oct 2017 16:40:12 -0200 Message-ID: Subject: Re: error instaling any ports To: Kurt Jaeger Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2017 18:40:45 -0000 Good afternoon Kurt and everyone I follow the steps (that Kurt sent with his help) After the mergemaster -UiP the server stop at boot, after this point cant attach pictures because of the size, follow some messages errors ifconfig: ioctl (set name): file exists /etc/rc warning $ipv6_ifconfig_lo0 is obsolete ifconfig: lo0 bad value eval list_vars: not found eval: sort_lite: not found these last 3, continues repeatly for ever I cant get the login screen On Tue, Oct 17, 2017 at 5:11 PM, Kurt Jaeger wrote: > Hi! > > > > uname -a > [...] > > > *server# uname -aFreeBSD server.avgroup.loc 9.1-PRERELEASE FreeBSD > > So you have a PRERELEASE version and you have a custom kernel. > > Do you know why that is ? Any specific change that needs to > be in that kernel config ? > > Please check if you have a 'svn' binary somewhere, because it looks > like you need to do a source upgrade first. > > rm -rf /usr/obj /usr/src > mkdir /usr/src > cd /usr/src > svn checkout https://svn.freebsd.org/base/release/9.3.0/ . > make buildworld > make buildkernel > make installkernel > make installworld > mergemaster -UiP > shutdown -r now > cd /usr/src > make check-old > make delete-old > make delete-old-libs > > > *server# freebsd-update -r 9.3-RELEASE upgradeLooking up > update.freebsd.org > > mirrors... 3 mirrors found.Fetching public > key > > from update6.freebsd.org... failed.Fetching public key from > > update5.freebsd.org... failed.Fetching public key from > > update4.freebsd.org... failed.No mirrors remaining, giving up* > > Well, freebsd-update only works on GENERIC kernels and systems, so > your first step needs to be a source upgrade. > > Please note: Your binaries from 9.1-PRE will work on 9.3, and probably on > 10.x, so no need to worry about the packages installed for now. > > You can rebuild your ports when you're on 10.x. > > -- > pi@opsec.eu +49 171 3101372 3 years to > go ! > From owner-freebsd-stable@freebsd.org Thu Oct 19 18:44:44 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B45FAE4423D for ; Thu, 19 Oct 2017 18:44:44 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 45E8C76F91 for ; Thu, 19 Oct 2017 18:44:44 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id i124so18190534wmf.3 for ; Thu, 19 Oct 2017 11:44:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yn/+6Y5cutllO4UgNUNOK88RKlGPEOZ+SrdHA3LrFJ4=; b=pC24nrdP7r+Q63MRkTep+PTzoGLft/rI17jysZ+uoxrvX+jIQhNByUqVvKMdGT6U3w 1PRvGxmk9n+Y9T2jSFRgnm9m3v8pLrBw3k16De81bNNvo/csPR3jnDExoJp83xLBGtaZ Aha7VV4nUQTK/q7lv0ZxGbY1rO4Pn47h6mPmyvr6Hj/zxQdP1QpSZ3HkWp5AC1iKSCI+ MHfzPY5t/H/tM7xitD2M/LceP/W+ovkGi8mNpSAP5nQNFY1AUbsMUv9zHjQMSjp+6vIs zj22kWIsgqzfCxs7mLIMEedU0DjDyadLUn20ppjnQXcWWnEcU6ACWtkKb16BZmMZNnY0 indg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yn/+6Y5cutllO4UgNUNOK88RKlGPEOZ+SrdHA3LrFJ4=; b=Aa9hEepOhMX0joQ4RKcNR19dwN1rHwh0kUL9tvMwZHDACdFvtC90gZe4kr12lk2+xv byFB+DDruqh6pG4iabkAqI1ZQo6ZZ4eVgyscCx1+wYGiD+ufZaN7la/RKqhXDc8jlclA WSP+AWk0OVtA9ZyQnA3Ex9NA9/YneOPMfcfKTwKJR6nGGJD3e84Oi4gAy2Ud//DqIzQ9 si9o/5xTEkK1w3a5DZtFt0jwn7gPmNV/Bc7KUcW9pjJNUQHdodHepvFMB0f/cQ5QVdP7 3TlGqIG4B0K13jxFaBXEULykx5DXVMNihCSvdDaShkNttP+oO2lj0kXrFUcgQ6XBgroH K1BQ== X-Gm-Message-State: AMCzsaWei23VMQR47oxrd0vKiwRNjZ9AdNYAroDCE+0Nd6maWmgRj1WJ rN0H7uBkMvMLXTU/vsUxZliFDnzKWetFyB7b8+c= X-Google-Smtp-Source: ABhQp+Qk5ZvPxWYf+atQX/ZTOW1ZJh0Ow7emyrhvRxmcS7c0he4y1MU6lDJAbyw6AqVLKR+euy/3LogmB3ej1qP3cpQ= X-Received: by 10.80.140.203 with SMTP id r11mr3382742edr.299.1508438682886; Thu, 19 Oct 2017 11:44:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.216.6 with HTTP; Thu, 19 Oct 2017 11:44:12 -0700 (PDT) In-Reply-To: <20171019183939.GI86601@home.opsec.eu> References: <20171017173258.GZ86601@home.opsec.eu> <20171017174708.GA86601@home.opsec.eu> <20171017191145.GB86601@home.opsec.eu> <20171019183939.GI86601@home.opsec.eu> From: Denis Granato Date: Thu, 19 Oct 2017 16:44:12 -0200 Message-ID: Subject: Re: error instaling any ports To: Kurt Jaeger Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2017 18:44:44 -0000 yes I can boot single mode, mount / , etc Why you think its a kernel problem not some file that I change in mergemaster questions because, I boot the serve once and the 9.1-> 9.3 worked after mergemaster and reboot that happened On Thu, Oct 19, 2017 at 4:39 PM, Kurt Jaeger wrote: > Hi! > > > I follow the steps (that Kurt sent with his help) > > After the mergemaster -UiP > > the server stop at boot, after this point (see pictures attached) > > Can you boot single-mode ? > > Can you boot the old kernel ? > > -- > pi@opsec.eu +49 171 3101372 3 years to > go ! > From owner-freebsd-stable@freebsd.org Thu Oct 19 19:01:58 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1CD52E448E1 for ; Thu, 19 Oct 2017 19:01:58 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CFC61779F2 for ; Thu, 19 Oct 2017 19:01:57 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e5G4u-000N4Y-Da; Thu, 19 Oct 2017 21:02:00 +0200 Date: Thu, 19 Oct 2017 21:02:00 +0200 From: Kurt Jaeger To: Denis Granato Cc: freebsd-stable@freebsd.org Subject: Re: error instaling any ports Message-ID: <20171019190200.GJ86601@home.opsec.eu> References: <20171017173258.GZ86601@home.opsec.eu> <20171017174708.GA86601@home.opsec.eu> <20171017191145.GB86601@home.opsec.eu> <20171019183939.GI86601@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2017 19:01:58 -0000 Hi! > yes I can boot single mode, mount / , etc Try to boot single user mode with the new kernel, then re-run make installworld mergemaster -UiP The normal way to do it is to reboot after make installkernel If you ran the installworld before the reboot, some files might not be copied. Another thing: Try to run ifconfig and see if it can list the interfaces of the box. Maybe it's the old ifconfig binary still left. > Why you think its a kernel problem not some file that I change > in mergemaster questions I vagely remember that there was an ifconfig thing sometime around 9.x. -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-stable@freebsd.org Thu Oct 19 19:11:29 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91BA7E44AC1 for ; Thu, 19 Oct 2017 19:11:29 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 222C777DDE for ; Thu, 19 Oct 2017 19:11:29 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id k4so18338891wmc.1 for ; Thu, 19 Oct 2017 12:11:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DtTIlNQ2LUK4b2rrGyW2iG1lnwLfEgcowrkJjdQ9xrU=; b=tarXZUJvQi4zOHWakp2fRtx4K7nOWfVKvYnYZXCBEDrROAIHXcZ+9vDQHVdhQOUT89 oGon55oNUm40GmwKo+T35WNqiC8aOiKFs7POJOmqthZpo7JVHtDGO664rcwThwvyGrxw 6lZlNNoMpjkF4kD8KBaGmYRbI3TLHwzcurxBOH0LqtyOdaOKbF0lK1azaI90v87a2jDy K4V7MZrdXkT+GWsYpG0xIoRwUqxn3FtYO8F+breqjrSdkvfNEqZYqEGejgJVVLrLMY4q YQJyRQCWoNcU+KLIE/Mv/Trp2/7wTE6SdPsDGSOHEEjVDO73eIpLr8/+M2CUuRdqRysk o5+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DtTIlNQ2LUK4b2rrGyW2iG1lnwLfEgcowrkJjdQ9xrU=; b=OYAnsRnMaImlqQnjO30JI2WywksbDBHCJQl3dtQ5YlzzVV9zWdUTcwPYypQWE5Qp/o hCXpY/kYiL09ueWvd5YCUYezHi3p/7Qt5Nj50Q3ZyqD2duRrDpr4+YkJtwSFbTBkP2JJ POAW5nwp7l1KxZLijuNzBc1+U6UgrbD/l+SCSiAek5GdaLhFxbS9bNvcb87w9zrH71Zo 1GXPAHdhQDTw/Wg6VvzL6O+7Q7ea+7YqIRJOFLLtSrknrg7+vfATz/XmWdx8jJS/ZCFq TqbhvcChuKxzGZe1FfGXULkowmf5EHaAnPAIv7Vf/eRmX8ZJQ6fQexD0VEZuADysrjPD HnVQ== X-Gm-Message-State: AMCzsaWH/+FRRwKQX8BCzhU9OWyZAja7JBmuh7yC+3aZs/9iUEggcF7g L1LeaNKIOOR6gVKWGIhkWnYiRCHgKO4SmgaVBSw= X-Google-Smtp-Source: ABhQp+T4jEauhTcyMCWFejvUIo6up+ryVNTsSQVOA6z5NZjqcAhZT+CXVEar7vbfGVudhKB6/Xisf4u/+1ZtaN39yBA= X-Received: by 10.80.222.130 with SMTP id c2mr3573201edl.218.1508440287456; Thu, 19 Oct 2017 12:11:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.216.6 with HTTP; Thu, 19 Oct 2017 12:10:56 -0700 (PDT) In-Reply-To: <20171019190200.GJ86601@home.opsec.eu> References: <20171017173258.GZ86601@home.opsec.eu> <20171017174708.GA86601@home.opsec.eu> <20171017191145.GB86601@home.opsec.eu> <20171019183939.GI86601@home.opsec.eu> <20171019190200.GJ86601@home.opsec.eu> From: Denis Granato Date: Thu, 19 Oct 2017 17:10:56 -0200 Message-ID: Subject: Re: error instaling any ports To: Kurt Jaeger Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2017 19:11:29 -0000 ok, I will try this, becausa I did everthing, then I reboot, like this steps svn checkout https://svn.freebsd.org/base/release/9.3.0/ . make buildworld make buildkernel make installkernel make installworld mergemaster -UiP shutdown -r now On Thu, Oct 19, 2017 at 5:02 PM, Kurt Jaeger wrote: > Hi! > > > yes I can boot single mode, mount / , etc > > Try to boot single user mode with the new kernel, then re-run > > make installworld > mergemaster -UiP > > The normal way to do it is to reboot after > > make installkernel > > If you ran the installworld before the reboot, some files might > not be copied. > > Another thing: Try to run > > ifconfig > > and see if it can list the interfaces of the box. Maybe it's the > old ifconfig binary still left. > > > Why you think its a kernel problem not some file that I change > > in mergemaster questions > > I vagely remember that there was an ifconfig thing sometime around > 9.x. > > -- > pi@opsec.eu +49 171 3101372 3 years to > go ! > From owner-freebsd-stable@freebsd.org Thu Oct 19 17:30:42 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A619BE41F43 for ; Thu, 19 Oct 2017 17:30:42 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 719F873B5C for ; Thu, 19 Oct 2017 17:30:36 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: by mail-wm0-x22e.google.com with SMTP id m72so16865919wmc.0 for ; Thu, 19 Oct 2017 10:30:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9vuLWItc+dnvyFT+GYAJtAh250NfoCWzKw266SJu9mU=; b=UcfFY/iKXWlxjnq2EBd/QTq0FUnD7qHeRg72dJe/gH15oFTp9S/znypffnz80ip6I1 Z3as/iqLmMt81qjVwO6hzjhy1GOi/kM+g1WlxofJ1zoXhNKzvPhig6KdbKFhsrli62io 9LOs8lxOcezE8TEuenWFHtFJMB98dKNdUQ6BT7cqNMr+WuzovnQSQQZbiAhrQDQplH12 VExdP4jZRFDZBeFyipFSRj7iSKsAcKAvOfF6K3RIUYdcdhEj+zhAhT/kxFmyptPdLA6z 430ZUZsnyFsFR3AnfnrscBG77UNmr58ogibiWKBbLTWmMQ7zoNv1c7IYawjOn64mdtfT vB8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=9vuLWItc+dnvyFT+GYAJtAh250NfoCWzKw266SJu9mU=; b=nr/e8UJVDE8eqe3q6Yh6dQDkrgUbBtAYOE+a18kZX08Jq338Z7zK3N7TqImUvfN+GR aZR9XetS+iQU8uLuQ8Cn6RHyQF1jLefKbXsH2+nrtKp5clshqTqWyvzyNIp94x+51vUd 0AD48akjPzLoNuioyxzv053RfihX7rAlSxCSQxWUd93s2W67dBLBaMgWF6wIeYUBrKLr j2dZwkk8jO4swVH4U7NLmQ00hLXqGc1OeAitPSbzVieEhhAKzimjLuq95PagLO87Vwu/ 6dLnmsTGh9K6Hh1GkkoKCh6RXwgvdFfgDOMdT3KUVZ248pylAXKq9FshVp/CfHRYH6eQ GBJQ== X-Gm-Message-State: AMCzsaVIQy793vDIERTP1F95Tv065AHujwcRFXuL4gmP/hDkevTOLo4M ye40JcRWPVtnRLZSaovBhebRiGMcOraMb/4z/b8= X-Google-Smtp-Source: ABhQp+SGsO7wT133SNqmGa8dNEIA05+mlZVgvrAV8KBF7y/BPpAjf+QejTM15boy/V3QC4/2d1ADMpwA0hH/K+89eZw= X-Received: by 10.80.134.37 with SMTP id o34mr3217154edo.306.1508434231977; Thu, 19 Oct 2017 10:30:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.216.6 with HTTP; Thu, 19 Oct 2017 10:30:01 -0700 (PDT) In-Reply-To: <20171017191145.GB86601@home.opsec.eu> References: <20171017173258.GZ86601@home.opsec.eu> <20171017174708.GA86601@home.opsec.eu> <20171017191145.GB86601@home.opsec.eu> From: Denis Granato Date: Thu, 19 Oct 2017 15:30:01 -0200 Message-ID: Subject: Re: error instaling any ports To: Kurt Jaeger Cc: freebsd-stable@freebsd.org X-Mailman-Approved-At: Thu, 19 Oct 2017 19:30:52 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2017 17:30:42 -0000 Good afternoon Kurt and everyone I follow the steps (that Kurt sent with his help) After the mergemaster -UiP the server stop at boot, after this point (see pictures attached) On Tue, Oct 17, 2017 at 5:11 PM, Kurt Jaeger wrote: > Hi! > > > > uname -a > [...] > > > *server# uname -aFreeBSD server.avgroup.loc 9.1-PRERELEASE FreeBSD > > So you have a PRERELEASE version and you have a custom kernel. > > Do you know why that is ? Any specific change that needs to > be in that kernel config ? > > Please check if you have a 'svn' binary somewhere, because it looks > like you need to do a source upgrade first. > > rm -rf /usr/obj /usr/src > mkdir /usr/src > cd /usr/src > svn checkout https://svn.freebsd.org/base/release/9.3.0/ . > make buildworld > make buildkernel > make installkernel > make installworld > mergemaster -UiP > shutdown -r now > cd /usr/src > make check-old > make delete-old > make delete-old-libs > > > *server# freebsd-update -r 9.3-RELEASE upgradeLooking up > update.freebsd.org > > mirrors... 3 mirrors found.Fetching public > key > > from update6.freebsd.org... failed.Fetching public key from > > update5.freebsd.org... failed.Fetching public key from > > update4.freebsd.org... failed.No mirrors remaining, giving up* > > Well, freebsd-update only works on GENERIC kernels and systems, so > your first step needs to be a source upgrade. > > Please note: Your binaries from 9.1-PRE will work on 9.3, and probably on > 10.x, so no need to worry about the packages installed for now. > > You can rebuild your ports when you're on 10.x. > > -- > pi@opsec.eu +49 171 3101372 3 years to > go ! > From owner-freebsd-stable@freebsd.org Thu Oct 19 19:36:18 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D3A4E45637 for ; Thu, 19 Oct 2017 19:36:18 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C1D1C7CE06 for ; Thu, 19 Oct 2017 19:36:17 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e5Gc8-000NCK-Ib; Thu, 19 Oct 2017 21:36:20 +0200 Date: Thu, 19 Oct 2017 21:36:20 +0200 From: Kurt Jaeger To: Denis Granato Cc: freebsd-stable@freebsd.org Subject: Re: error instaling any ports Message-ID: <20171019193620.GK86601@home.opsec.eu> References: <20171017173258.GZ86601@home.opsec.eu> <20171017174708.GA86601@home.opsec.eu> <20171017191145.GB86601@home.opsec.eu> <20171019183939.GI86601@home.opsec.eu> <20171019190200.GJ86601@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2017 19:36:18 -0000 Hi! > ok, I will try this, becausa I did everthing, then I reboot, like this steps > > svn checkout https://svn.freebsd.org/base/release/9.3.0/ . > make buildworld > make buildkernel > make installkernel > make installworld > > mergemaster -UiP > shutdown -r now Yes, this works for small upgrades, most of the time. Sometimes it fails. I was lazy when I listed it that way. The reboot should have been between installkernel and installworld. -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-stable@freebsd.org Thu Oct 19 20:10:05 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4B55E460EB for ; Thu, 19 Oct 2017 20:10:05 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 538177DCA4 for ; Thu, 19 Oct 2017 20:10:05 +0000 (UTC) (envelope-from denisgranato@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id u138so18143896wmu.5 for ; Thu, 19 Oct 2017 13:10:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=R96gzN1+TN3tRpGqJYkfyMC5SuZW4ig/mZvEUp9jXQU=; b=rO/iZmSxQ/A0sjBbc/uTn3gVkOwbR9eP3Rhg7x5/1s9dEfk8GxfD8DEedpJ6/guiLt llfYxZdX9kZ3+oHUlRiP1bsjCmousVC0aVWhdoETsUnkH1GDHvJFNmmcFwK6VmpGgChS 4S5qj5y+qO8Ku7DnYV8mTJX5FWAi8hqZvONW3oQbrROjsay+43wrNJkfq4XmVfR7UaUG ehuQAz86SFPxuRW/j7W6p/MZlmVle88uo6FbobOa7oz/fAWMEQpH1kjE2EhU48f0qCsc qlCPvtTgLYjiUNEzitAGJA4hLoSWIDAVnbAaLY5hut8xLiaL1gGK5QzCc5a8Pk+bPgaQ 8Clw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=R96gzN1+TN3tRpGqJYkfyMC5SuZW4ig/mZvEUp9jXQU=; b=DhAwl5WlFfYfPkv60HBrnLIi5Jq4vbG2RdNDI8domDb/BckD0m6JtulPrpME1VRNlC h8JxBwNbI1RuxtvJJU/bBBOwdz1CTHQUw0HJLo4bjPbn1Qt/smmMj/ZCNilU3D+PqTD5 jot195bpufiZ1LN3Idx882fvznLxOSWT+ATK7uDtR2VAnGcm0xy+la7Jd11eXURziknz kr+iZ85oEc8u/OETyWp+r7x7EtmyRuhT+Z1A4HbszV8luXAyvSMXm7N8dTMiQCtsh5AD kanzRLoJivSEGN9SG3vOGv3E7upL/5rkvJIjB/2l+NBQzyAQto3gw+A4d5t3A8IdwMVG Dz9w== X-Gm-Message-State: AMCzsaX98kKPpyKTcwZmWlgS8s44OchU0J+E51WRxgjx6OdhBnS7b5lS KMMxMXpB+0ej4qHgHKsFQ0P01iFlzAOWNBrpPSs= X-Google-Smtp-Source: ABhQp+Tt19y/qswsbKyodzjmLO351YLns1xeqjZaDCiD8OGOtg/uRZEoVZQ4s6d4SxYkSm2t8bRDI9bpsubHazLaZFQ= X-Received: by 10.80.186.61 with SMTP id g58mr3731317edc.206.1508443803706; Thu, 19 Oct 2017 13:10:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.216.6 with HTTP; Thu, 19 Oct 2017 13:10:03 -0700 (PDT) Received: by 10.80.216.6 with HTTP; Thu, 19 Oct 2017 13:10:03 -0700 (PDT) In-Reply-To: <20171019193620.GK86601@home.opsec.eu> References: <20171017173258.GZ86601@home.opsec.eu> <20171017174708.GA86601@home.opsec.eu> <20171017191145.GB86601@home.opsec.eu> <20171019183939.GI86601@home.opsec.eu> <20171019190200.GJ86601@home.opsec.eu> <20171019193620.GK86601@home.opsec.eu> From: Denis Granato Date: Thu, 19 Oct 2017 18:10:03 -0200 Message-ID: Subject: Re: error instaling any ports To: Kurt Jaeger Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2017 20:10:05 -0000 Ok its worked Entered in single mode Make installworld Mergemaster -UiP now server is alive in 9.3 Tomorrow I check the ports On Oct 19, 2017 5:36 PM, "Kurt Jaeger" wrote: > Hi! > > > ok, I will try this, becausa I did everthing, then I reboot, like this > steps > > > > svn checkout https://svn.freebsd.org/base/release/9.3.0/ . > > make buildworld > > make buildkernel > > make installkernel > > make installworld > > > > mergemaster -UiP > > shutdown -r now > > Yes, this works for small upgrades, most of the time. Sometimes > it fails. > > I was lazy when I listed it that way. > > The reboot should have been between installkernel and installworld. > > -- > pi@opsec.eu +49 171 3101372 3 years to > go ! > From owner-freebsd-stable@freebsd.org Fri Oct 20 05:33:08 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E2F9E504A5 for ; Fri, 20 Oct 2017 05:33:08 +0000 (UTC) (envelope-from peter@pean.org) Received: from system.jails.se (system.jails.se [52.16.239.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E111569323 for ; Fri, 20 Oct 2017 05:33:07 +0000 (UTC) (envelope-from peter@pean.org) Received: from lune.pean.org (213-67-100-148-no110.tbcn.telia.com [213.67.100.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by system.jails.se (Postfix) with ESMTPSA id F2F4212058E; Fri, 20 Oct 2017 07:32:59 +0200 (CEST) From: =?utf-8?Q?Peter_Ankerst=C3=A5l?= Message-Id: <82E419D4-4FB4-402A-ACC9-C58D498461BE@pean.org> Content-Type: multipart/signed; boundary="Apple-Mail=_68D90BAD-AF91-4C37-95F7-4BDBB263CD00"; protocol="application/pkcs7-signature"; micalg=sha1 Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Subject: Re: 802.1X authenticator for FreeBSD Date: Fri, 20 Oct 2017 07:32:55 +0200 In-Reply-To: <3F040A9B-B03F-4FD5-B1DC-70BD8AFCC829@bway.net> Cc: Stefan Bethke , FreeBSD Stable , Chris Ross To: Charles Sprickman References: <2D461E1D-895F-4D31-9834-A40DEF02F121@pean.org> <4F45AC20-57F9-4246-836E-4F1C1D01FAC2@lassitu.de> <2B2D49E0-F804-4557-9DB5-A915A8578070@pean.org> <3F040A9B-B03F-4FD5-B1DC-70BD8AFCC829@bway.net> X-Mailer: Apple Mail (2.3445.1.7) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2017 05:33:08 -0000 --Apple-Mail=_68D90BAD-AF91-4C37-95F7-4BDBB263CD00 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 18 Oct 2017, at 21:39, Charles Sprickman wrote: >=20 >=20 >> On Oct 18, 2017, at 1:10 PM, Peter Ankerst=C3=A5l = wrote: >>=20 >>>=20 >>> I=E2=80=99m under the impression that the authenticator function in = a wired network is usually part of the switch, and the switch will talk = to some authentication server like RADIUS, giving it the port number of = the connected device and additional information. >>>=20 >>> If FreeBSD had such a function, I think it would be limited to = point-to-point Ethernet links, 802.1x being a link-layer protocol. >>>=20 >>=20 >> Yes I know, but this is functional in hostapd for Linux and it would = be nice to have it in FreeBSD as well.=20 >=20 > I=E2=80=99m not seeing this in FreeBSD, but pfsense does claim to = support 802.1x for wifi. >=20 > I just happen to be reading about radius (last I used it was for = dialup) for wifi auth and the quick overview on the radius side of = things is that the AP software sends your auth info as well as MAC and a = bunch of other stuff, and the radius server (much like dialup) sends = back all sorts of info beyond auth success/fail - session timeout, info = on what VLAN the client may be on, firewall policies, etc. Pretty cool = stuff. 802.1X (or WPA2 Enterprise) works fine with hostapd for wireless in = FreeBSD. Well, the authentication at least. I havent tried assigning = clients to specific vlans and so on but according to the documentation = it is possible.= --Apple-Mail=_68D90BAD-AF91-4C37-95F7-4BDBB263CD00 Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIL1TCCBeIw ggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwx FjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmlj YXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4X DTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0 YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEP ADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmvmCSsu1d52DXsCR58zJQbCtB2/A5uFqNx WacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnmVkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+C evdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx 7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PIdopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8U lVS8pkIsoGGJtMuWjLL4tq2hYQuuN0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1Ud DwEB/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB /wIBADAyBgNVHR8EKzApMCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmww ZgYIKwYBBQUHAQEEWjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYI KwYBBQUHMAKGJGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQU JIFsOWG+SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYD VR0gBDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY0JdO ruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpFNjDmQbcM 3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9uRbhjTu/b0x2 Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p6q/CW+uVrZiSW57+ q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOvZ3UDsTDTagXpRDIKQLZo 02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOumZhLP+SWJQnjpLpSlUOj95uf 1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7RX6gVr0fQoCyMczNzCTcRXYHY0tq 2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO/ZskmSY8wtAk24orAc0vwXgYanqNsBX5 Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsNJQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1 UeGp/2deoprGevfnxWB+vHNQiu85o6MwggXrMIIE06ADAgECAhAVg7EhX8r2LDRKhDrOrr8zMA0G CSqGSIb3DQEBCwUAMHUxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYD VQQLEyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20g Q2xhc3MgMSBDbGllbnQgQ0EwHhcNMTcwMTI2MjAxNDMwWhcNMjAwNDI2MjAxNDMwWjA4MRcwFQYD VQQDDA5wZXRlckBwZWFuLm9yZzEdMBsGCSqGSIb3DQEJARYOcGV0ZXJAcGVhbi5vcmcwggIiMA0G CSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDcqYms37M3iO33p6LWK/fj7JFLGVacfvZf4CaHyg8m jY4sVP9HzeB6A/FOk0fvxDvK0Q7dIkoQdniS7DKcsBXpJ5s+tpszOhQ36RpD3B0xao3z0sI+9MyK 6IDu7pjxunC5qLYnVkcDjBPJ0X8qyR/bSvUQ3kBEOppPs8ol8GHsiRSy3TJL2wGapAdA+1r2KCqe eHrrCTGj4Dl7xvgUkfii6wShPH0yu66raHvdN6DHUyb1EFgS70HZ22+HuffqGvOB+iZZUeE9UQT0 pbzgCcHfkXfgRtNkzKDzrfYmJi9oTIpfyvusu8F9B9L3rZM6V2Stag4LLAo+zhsX1quM20Ilo71U GPhLgvDNjJnx1qli3tAyddxMhqJMhcRYDScIoIi6xZ4jNJvMlHJGTq29oH+A2TjAmM+gJY+0p4RB vVhNf7e0jSaVeHei+H+q9OlQmylXC1GzcUrzFDqWLDB70Sta20rQakZEFsQ+e+shxmj4AakCxY4D x5PvyWk48JWtmfaXboDG8Lr5RaULjHGEtg6ULVQdYakJDuCkjyYtZSZtC8PKk1uFzJu4yhfX9vOb VEabLeO5dSvNWYllUQdOP9nuNh5ZnHxEIHA1k/UgRvdwootCJ4TrTfHp7fQLbMP7AE53x88/M++A wNofKHoNqE7iPh1s9Os0ZWi/czCiFRI7wwIDAQABo4IBsjCCAa4wDgYDVR0PAQH/BAQDAgSwMB0G A1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBSxDZ1/nnS6 biObk7mYFx6CSYKuFzAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBvBggrBgEFBQcB AQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5BggrBgEFBQcwAoYt aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEuY3J0MDgGA1UdHwQxMC8w LaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGllbnQxLmNybDAZBgNVHREEEjAQ gQ5wZXRlckBwZWFuLm9yZzAjBgNVHRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wRwYD VR0gBEAwPjA8BgsrBgEEAYG1NwECBTAtMCsGCCsGAQUFBwIBFh9odHRwczovL3d3dy5zdGFydHNz bC5jb20vcG9saWN5MA0GCSqGSIb3DQEBCwUAA4IBAQCbKZGNOgGhchJ0IcN9rOEy8cwnHlBVDBTc kCdh6HPTeb7SiPmDLxJ1mp2ptKMjVDItkV9golRi4zWW0Q+aT8lJSbmLRWnTJflQB8zhbvSHwFzU VlsYEJBBUrMrfBeowZIcDLTr5VjmC7WysSSIAPyOLtbbIhYWVDiRc7FR3cMzMx0JHByg8iZqJ5/d S7CXj5NiRb8jp3Uo9Wo5o8qwuA0YQ/7ld7tZbE47jAQ6gOQ/J+yBNWCXOjklFmXeI6fxITO5XTq/ +SN1rp4lMR5KfahwYBf0m0jeZQbxek8XTTa1qHfDuZWdKP9Nab2LPYhOs+ShIMb3BNBgiJe7a3H7 yCwjMYIETjCCBEoCAQEwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x KTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFy dENvbSBDbGFzcyAxIENsaWVudCBDQQIQFYOxIV/K9iw0SoQ6zq6/MzAJBgUrDgMCGgUAoIIBmTAY BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNzEwMjAwNTMyNTZaMCMG CSqGSIb3DQEJBDEWBBQWCU1J5WKfE2KKhMBe0OoDsih9ZzCBmgYJKwYBBAGCNxAEMYGMMIGJMHUx CzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGllbnQg Q0ECEBWDsSFfyvYsNEqEOs6uvzMwgZwGCyqGSIb3DQEJEAILMYGMoIGJMHUxCzAJBgNVBAYTAklM MRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBDZXJ0aWZpY2F0aW9u IEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGllbnQgQ0ECEBWDsSFfyvYs NEqEOs6uvzMwDQYJKoZIhvcNAQEBBQAEggIAJucTKm/EfQKRNwB29V//xON0xrwczdBwwzRlStnq TZ8/WDn4kHr3drfrmN/cVEKZNBxlaZLI8jiegr+n6WyuZS54+G8M5mC8jliiVHdx7kUGQM/xgATx W9tMHZmagMh5ei4k4xXBF1LQT+0Y7Q6h6V9cknK5xwe6nIokr9+WcBX94u9sR3TFLeY/nloQwMBr qbn8yz6o3bj0stH4cIq/N+vGVLe4NFprud2NbqNVjz+a7hSBWDc92J7EHvlNb7LqTd92+ZNDCUXS WoE/Uk7zm8pjLMm40vpdPF2s8J167wEtA1HjJHUGwks81R6o1R2l6Huy2Fg/28Y/Z5xu40gE0pxb IgtH8JqoiwY8GoOJ9C/u5F+9PAu96w+cbAEoI+JXkZxpp8K/YO6h6taLaYDbiQY0JqD+hHp2DaHw ZRtdb3tNLslLvpGn6oSbC/ZroG68NMUIjNn4t2xlWsMJhLLPXHlEO6AGw3IkYcULzixkREAVozDo OW4GUQgUuClOLt9FJHbo6fM1nFKw0Idxowj850x8ADCBq5tb5dWoaQPb6MmfJ9j8mO8H3+3U5Wbi 8ZwG7pBc4aX1/hzZ6dt0BFy9g3Us/nZDC+ZmIbNJs1YLwv+FT+Ufj+TqGtJZj6k4dlX5RrESe6Aa QnMnWUFaXsjlenSaXbfoFhJxxsBL13vlnxoAAAAAAAA= --Apple-Mail=_68D90BAD-AF91-4C37-95F7-4BDBB263CD00-- From owner-freebsd-stable@freebsd.org Fri Oct 20 15:19:07 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EEB6DE386AE for ; Fri, 20 Oct 2017 15:19:07 +0000 (UTC) (envelope-from mw@dudes.ch) Received: from mail.dudes.ch (mail.dudes.ch [193.73.211.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.dudes.ch", Issuer "StartCom Class 3 OV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 963317EF6C for ; Fri, 20 Oct 2017 15:19:07 +0000 (UTC) (envelope-from mw@dudes.ch) Received: from mwoffice.virtualtec.office (pippin.virtualtec.ch [93.189.66.120]) (authenticated bits=0) by mail.dudes.ch (8.15.2/8.15.2) with ESMTPSA id v9KFDjl0077741 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 20 Oct 2017 17:13:46 +0200 (CEST) (envelope-from mw@dudes.ch) X-Authentication-Warning: mail.dudes.ch: Host pippin.virtualtec.ch [93.189.66.120] claimed to be mwoffice.virtualtec.office Date: Fri, 20 Oct 2017 17:13:45 +0200 From: Markus Wild To: freebsd-stable@freebsd.org Subject: System fails to boot with zfs root on nvme mirror when not using full disks Message-ID: <20171020171345.073bd9b1@mwoffice.virtualtec.office> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 193.73.211.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2017 15:19:08 -0000 Hello list, I have a particularly odd problem, where I can't figure out what's going on, or whether I'm possibly doing something stupid... Short summary: - Supermicro X10DRI-T motherboard, using UEFI boot, 128G RAM, 2 CPUs - 2 Intel DC P3700 NVME cards, to be used as mirrored zfs root and mirrored log devices for a data pool - FreeBSD-11.1 release installs fine off memstick, and the built system boots correctly, but this system uses the entire disks (so I need to shrink the system to make room for log partitions) - so I then rebooted into usb live system, and did a gpart backup of the nvme drives (see later). zfs snapshot -r, zfs send -R > backup, gpart delete last index and recreate with shorter size on both drives, recreate zroot pool with correct ashift, restore with zfs receive from backup, set bootfs, reboot - the rebooting system bootloader finds the zroot pool correctly, and proceeds to load the kernel. However, when it's supposed to mount the root filesystem, I get: Trying to mount root from zfs:zroot/ROOT/default []... Mounting from zfs:zroot/ROOT/default failed with error 6. - when I list the available boot devices, all partitions of the nvme disks are listed - I can import this pool without any issues with the usb live system, there are no errors on import. - I then redid the whole exercise, but restored the previously backed up partition tables (full size zfs partition), did exactly the same steps as described above to restore the previous zfs filesystem, rebooted, and the system started up normally. So, my impression is: the kernel is doing something odd when trying to import the zroot pool, if that pool isn't using the whole physical disk space. Is there some way to enable debugging for the "mount a root zfs pool" process of the kernel, so see where this is failing? Here's a more detailled history of my commands to reduce the pool size: {I'm on a data pool directory here, where I can store stuff. I've booted from usb stick into live system} zpool import -Nf zroot zfs snapshot -r zroot@backup zfs send -R zroot@backup > zroot.zfs zpool destroy zroot gpart delete -i 3 nvd0 gpart delete -i 3 nvd1 gpart add -a 4k -s 50G -t freebsd-zfs -l zfs0 nvd0 gpart add -a 4k -s 50G -t freebsd-zfs -l zfs1 nvd1 sysctl vfs.zfs.min_auto_ashift=12 zpool create -f -o altroot=/mnt -o cachefile=/var/tmp/zpool.cache zroot mirror /dev/gpt/zfs0 /dev/gpt/zfs1 zfs receive -Fud zroot < zroot.zfs zpool set bootfs=zroot/ROOT/default zroot reboot Also, here's a diff between full and partial gpart backup: --- nvd0.gpart 2017-10-20 14:04:26.583846000 +0200 +++ nvd0.gpart.new 2017-10-20 15:39:20.184445000 +0200 @@ -1,4 +1,4 @@ GPT 152 1 efi 40 409600 efiboot0 2 freebsd-swap 411648 33554432 swap0 -3 freebsd-zfs 33966080 747456512 zfs0 +3 freebsd-zfs 33966080 104857600 zfs0 I'm really at a loss to see the reason why this is failing. I can provide detailled dmesg output of the booting system, and screenshots of the kvm-efi-console of the failing boot. Thanks for any help:) Cheers, Markus From owner-freebsd-stable@freebsd.org Fri Oct 20 16:51:47 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE2D1E3A889 for ; Fri, 20 Oct 2017 16:51:47 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8B8A38285B for ; Fri, 20 Oct 2017 16:51:47 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1e5aWO-0007pv-VY; Fri, 20 Oct 2017 17:51:44 +0100 Date: Fri, 20 Oct 2017 17:51:44 +0100 From: Gary Palmer To: Markus Wild Cc: freebsd-stable@freebsd.org Subject: Re: System fails to boot with zfs root on nvme mirror when not using full disks Message-ID: <20171020165144.GC96120@in-addr.com> References: <20171020171345.073bd9b1@mwoffice.virtualtec.office> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171020171345.073bd9b1@mwoffice.virtualtec.office> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Oct 2017 16:51:47 -0000 On Fri, Oct 20, 2017 at 05:13:45PM +0200, Markus Wild wrote: > Hello list, > > I have a particularly odd problem, where I can't figure out what's going on, or whether I'm possibly doing something > stupid... > > Short summary: > - Supermicro X10DRI-T motherboard, using UEFI boot, 128G RAM, 2 CPUs > - 2 Intel DC P3700 NVME cards, to be used as mirrored zfs root and mirrored log devices for a data pool > - FreeBSD-11.1 release installs fine off memstick, and the built system boots correctly, but this system uses the entire > disks (so I need to shrink the system to make room for log partitions) > - so I then rebooted into usb live system, and did a gpart backup of the nvme drives (see later). zfs snapshot -r, zfs > send -R > backup, gpart delete last index and recreate with shorter size on both drives, recreate zroot pool with > correct ashift, restore with zfs receive from backup, set bootfs, reboot > - the rebooting system bootloader finds the zroot pool correctly, and proceeds to load the kernel. However, when it's > supposed to mount the root filesystem, I get: > Trying to mount root from zfs:zroot/ROOT/default []... > Mounting from zfs:zroot/ROOT/default failed with error 6. > - when I list the available boot devices, all partitions of the nvme disks are listed My suspicion is that you didn't make a backup of the new /boot/zfs/zpool.cache >From the USB live booted system, when you recreated the zpool you likely changed parameters that live in the cache. You need to copy that to the new boot pool or ZFS can get angry Just a suspicion Regards, Gary From owner-freebsd-stable@freebsd.org Sat Oct 21 16:05:06 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0055E31E9A for ; Sat, 21 Oct 2017 16:05:06 +0000 (UTC) (envelope-from pblok@bsd4all.org) Received: from smtpq1.mnd.mail.iss.as9143.net (smtpq1.mnd.mail.iss.as9143.net [212.54.34.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A6EBE34F4 for ; Sat, 21 Oct 2017 16:05:06 +0000 (UTC) (envelope-from pblok@bsd4all.org) Received: from [212.54.34.117] (helo=smtp9.mnd.mail.iss.as9143.net) by smtpq1.mnd.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1e5vy3-0002ZT-7t; Sat, 21 Oct 2017 17:45:43 +0200 Received: from 5ed15678.cm-7-2b.dynamic.ziggo.nl ([94.209.86.120] helo=wan0.bsd4all.org) by smtp9.mnd.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1e5vy3-0002ux-65; Sat, 21 Oct 2017 17:45:43 +0200 Received: from newnas (localhost [127.0.0.1]) by wan0.bsd4all.org (Postfix) with ESMTP id B61FC1587; Sat, 21 Oct 2017 17:45:41 +0200 (CEST) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from wan0.bsd4all.org ([127.0.0.1]) by newnas (newnas.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IDpPX11tRCo9; Sat, 21 Oct 2017 17:45:40 +0200 (CEST) Received: from [192.168.1.65] (unknown [192.168.1.65]) by wan0.bsd4all.org (Postfix) with ESMTPSA id 672C5157E; Sat, 21 Oct 2017 17:45:40 +0200 (CEST) From: Peter Blok Message-Id: <90C2260F-D7E1-4EF6-824C-EA90C09F0B82@bsd4all.org> Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Subject: Re: 802.1X authenticator for FreeBSD Date: Sat, 21 Oct 2017 17:45:39 +0200 In-Reply-To: <82E419D4-4FB4-402A-ACC9-C58D498461BE@pean.org> Cc: Charles Sprickman , FreeBSD Stable , Stefan Bethke , Chris Ross To: =?utf-8?Q?Peter_Ankerst=C3=A5l?= References: <2D461E1D-895F-4D31-9834-A40DEF02F121@pean.org> <4F45AC20-57F9-4246-836E-4F1C1D01FAC2@lassitu.de> <2B2D49E0-F804-4557-9DB5-A915A8578070@pean.org> <3F040A9B-B03F-4FD5-B1DC-70BD8AFCC829@bway.net> <82E419D4-4FB4-402A-ACC9-C58D498461BE@pean.org> X-Mailer: Apple Mail (2.3445.1.7) X-SourceIP: 94.209.86.120 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.2 cv=Ien3YSia c=1 sm=1 tr=0 a=IkzOOneQUJP1+bAPekPvBg==:17 a=02M-m0pO-4AA:10 a=gzIrl_mWAAAA:8 a=lRtnlflVAAAA:8 a=j7r-GKrtSyq1zGFfhBcA:9 a=FO2cA_3j9GB_WUFG:21 a=xlTNuSEipGDSkxwY:21 a=QEXdDO2ut3YA:10 a=Fr6vun-eYi2vG8jWhf4A:9 a=_77-ApVQDMQAEWkF:21 a=U2UqtHgbd42aNc5_:21 a=qgJ7nPtozRJkc6WM:21 a=_W_S_7VecoQA:10 a=fbBnRoMp3JsphMan6DzI:22 a=203WYvXZLHx0qCticVN7:22 none X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2017 16:05:07 -0000 Although WPA2 enterprise authentication works perfectly on FreeBSD with = free radius, some functionality (like the built in DHCP) is not = implemented due to lack of PF_LINK, SOCK_RAW. FreeBSD uses bpf for this. Don=E2=80=99t know if this is required for what you want, but be aware. I am interested in switch port authentication, but haven=E2=80=99t found = the time to dig into the matter. And I refuse to use Linux=E2=80=A6. Peter > On 20 Oct 2017, at 07:32, Peter Ankerst=C3=A5l wrote: >=20 >=20 >=20 >> On 18 Oct 2017, at 21:39, Charles Sprickman wrote: >>=20 >>=20 >>> On Oct 18, 2017, at 1:10 PM, Peter Ankerst=C3=A5l = wrote: >>>=20 >>>>=20 >>>> I=E2=80=99m under the impression that the authenticator function in = a wired network is usually part of the switch, and the switch will talk = to some authentication server like RADIUS, giving it the port number of = the connected device and additional information. >>>>=20 >>>> If FreeBSD had such a function, I think it would be limited to = point-to-point Ethernet links, 802.1x being a link-layer protocol. >>>>=20 >>>=20 >>> Yes I know, but this is functional in hostapd for Linux and it would = be nice to have it in FreeBSD as well.=20 >>=20 >> I=E2=80=99m not seeing this in FreeBSD, but pfsense does claim to = support 802.1x for wifi. >>=20 >> I just happen to be reading about radius (last I used it was for = dialup) for wifi auth and the quick overview on the radius side of = things is that the AP software sends your auth info as well as MAC and a = bunch of other stuff, and the radius server (much like dialup) sends = back all sorts of info beyond auth success/fail - session timeout, info = on what VLAN the client may be on, firewall policies, etc. Pretty cool = stuff. >=20 > 802.1X (or WPA2 Enterprise) works fine with hostapd for wireless in = FreeBSD. Well, the authentication at least. I havent tried assigning = clients to specific vlans and so on but according to the documentation = it is possible. From owner-freebsd-stable@freebsd.org Sat Oct 21 23:22:45 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8797E3CC63 for ; Sat, 21 Oct 2017 23:22:45 +0000 (UTC) (envelope-from howard@leadmon.net) Received: from leadmon.net (mail.leadmon.net [IPv6:2001:550:102:5::130]) by mx1.freebsd.org (Postfix) with ESMTP id 84FAB6F223 for ; Sat, 21 Oct 2017 23:22:45 +0000 (UTC) (envelope-from howard@leadmon.net) Received: from localhost (localhost [127.0.0.1]) by leadmon.net (Postfix) with ESMTP id E9DC411238 for ; Sat, 21 Oct 2017 19:22:43 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at leadmon.net Received: from leadmon.net ([127.0.0.1]) by localhost (mail.leadmon.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qorSoWkmWPNo for ; Sat, 21 Oct 2017 19:22:39 -0400 (EDT) Received: from [IPv6:2001:559:80fd:0:4c93:1786:c892:5868] (unknown [IPv6:2001:559:80fd:0:4c93:1786:c892:5868]) by leadmon.net (Postfix) with ESMTPSA id 4C28D11221 for ; Sat, 21 Oct 2017 19:22:39 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.10.3 leadmon.net 4C28D11221 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=leadmon.net; s=default; t=1508628159; bh=BDrzOba5BYRVv1cfMRnIDOz3ZHO3n2Tn7YBkX2QEnSA=; h=To:From:Subject:Date:From; b=NdAoLTxDesFhqnyimUOcdgZzK7DBLKNvp6V0Y1qZUMD3z1jM/4kMwd4ofvoYG9LtZ DzEXjrK77UrDI1K6TSibteUxL1x0myFHVwaytaY+yAQdSoxnMDDVqOsDjI/WIa/vBz EvctzESFtjM1GHJyGuSPmQiPD73rB66giPn/qu/8= To: freebsd-stable@freebsd.org From: Howard Leadmon Subject: Freebsd 10 to 11 sendmail compile issues.. Organization: PBW Communications Message-ID: <7a4b5f15-1bab-9ab4-1ecf-8ffbf8546758@leadmon.net> Date: Sat, 21 Oct 2017 19:22:40 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2017 23:22:45 -0000  Hopefully someone can help or give me a pointer to a solution to this one.   Running FreeBSD 10.3 and figured I would do a source build and jump to FreeBSD 11.1.  For the most part this seemed to be going well, but when it goes to compile sendmail, it spits out the following error: bmake[4]: "/usr/src/share/mk/src.libnames.mk" line 391: /usr/src/libexec/mail.local: These libraries should be LIBADD+=foo rather than DPADD/LDADD+=-lfoo:  ssl crypto I have the following flags in /etc/make.conf: SENDMAIL_CFLAGS= -I/usr/local/include -DSASL=2 -DDNSMAP -DSTARTTLS SENDMAIL_LDFLAGS= -L/usr/local/lib SENDMAIL_LDADD= -lsasl2 -lssl -lcrypto  So I trhought OK, simple enough looking at the error and changed this over to the following: SENDMAIL_CFLAGS= -I/usr/local/include -DSASL=2 -DDNSMAP -DSTARTTLS SENDMAIL_LDFLAGS= -L/usr/local/lib SENDMAIL_LIBADD+= sasl2 ssl crypto  After that the error received was that I didn't has sasl2: --- ELF/Arch/AMDGPU.o --- c++   -O2 -pipe -march=nocona -I/usr/src/contrib/llvm/tools/lld/ELF -I/usr/src/contrib/llvm/tools/lld/include -I/usr/obj/usr/src/usr.bin/clang/lld -I/usr/obj/usr/src/lib/clang/libllvm -I/usr/src/lib/clang/include -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DNDEBUG -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd11.1\" -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd11.1\" -DDEFAULT_SYSROOT=\"\" -ffunction-sections -fdata-sections -g -MD -MF.depend.ELF_Arch_AMDGPU.o -MTELF/Arch/AMDGPU.o -fstack-protector-strong -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -std=c++11 -fno-exceptions -fno-rtti -stdlib=libc++ -Wno-c++11-extensions  -c /usr/src/contrib/llvm/tools/lld/ELF/Arch/AMDGPU.cpp -o ELF/Arch/AMDGPU.o --- all_subdir_usr.sbin --- deliver.o: In function `endmailer': /usr/src/contrib/sendmail/src/deliver.c:3874: undefined reference to `sasl_dispose' deliver.o: In function `deliver': /usr/src/contrib/sendmail/src/deliver.c:3137: undefined reference to `sasl_getprop' main.o: In function `main': /usr/src/contrib/sendmail/src/main.c:2303: undefined reference to `sasl_server_init' /usr/src/contrib/sendmail/src/main.c:2305: undefined reference to `sasl_errstring' sasl.o: In function `sm_sasl_init': /usr/src/contrib/sendmail/src/sasl.c:146: undefined reference to `sasl_set_alloc' sfsasl.o: In function `sasl_read': /usr/src/contrib/sendmail/src/sfsasl.c:224: undefined reference to `sasl_decode' sfsasl.o: In function `sasl_write': /usr/src/contrib/sendmail/src/sfsasl.c:311: undefined reference to `sasl_getprop' /usr/src/contrib/sendmail/src/sfsasl.c:316: undefined reference to `sasl_encode' srvrsmtp.o: In function `smtp': /usr/src/contrib/sendmail/src/srvrsmtp.c:951: undefined reference to `sasl_server_new' /usr/src/contrib/sendmail/src/srvrsmtp.c:1004: undefined reference to `sasl_setprop' /usr/src/contrib/sendmail/src/srvrsmtp.c:1018: undefined reference to `sasl_setprop' /usr/src/contrib/sendmail/src/srvrsmtp.c:1069: undefined reference to `sasl_setprop' /usr/src/contrib/sendmail/src/srvrsmtp.c:1081: undefined reference to `sasl_setprop' /usr/src/contrib/sendmail/src/srvrsmtp.c:1083: undefined reference to `sasl_setprop' srvrsmtp.o:/usr/src/contrib/sendmail/src/srvrsmtp.c:2254: more undefined references to `sasl_setprop' follow  So apparently that change seems to be including ssl and crypto but not sasl2 for some reason.    I have googled looking for examples of how to correct it, but everything I find shows the original way I had it to start with, and clearly that is no longer working.  Any ideas on how I need to define this would be most appreciated.. --- Howard Leadmon PBW Communications, LLC http://www.pbwcomm.com From owner-freebsd-stable@freebsd.org Sat Oct 21 23:40:28 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1482EE3D1E6 for ; Sat, 21 Oct 2017 23:40:28 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ECEDB6F871 for ; Sat, 21 Oct 2017 23:40:27 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 3d523b24-b6b9-11e7-a938-4f970e858fdb X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 3d523b24-b6b9-11e7-a938-4f970e858fdb; Sat, 21 Oct 2017 23:40:37 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v9LNeJek014381; Sat, 21 Oct 2017 17:40:19 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1508629219.1383.113.camel@freebsd.org> Subject: Re: Freebsd 10 to 11 sendmail compile issues.. From: Ian Lepore To: Howard Leadmon , freebsd-stable@freebsd.org Date: Sat, 21 Oct 2017 17:40:19 -0600 In-Reply-To: <7a4b5f15-1bab-9ab4-1ecf-8ffbf8546758@leadmon.net> References: <7a4b5f15-1bab-9ab4-1ecf-8ffbf8546758@leadmon.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2017 23:40:28 -0000 On Sat, 2017-10-21 at 19:22 -0400, Howard Leadmon wrote: >   Hopefully someone can help or give me a pointer to a solution to this  > one.   Running FreeBSD 10.3 and figured I would do a source build and  > jump to FreeBSD 11.1.  For the most part this seemed to be going well,  > but when it goes to compile sendmail, it spits out the following error: > > bmake[4]: "/usr/src/share/mk/src.libnames.mk" line 391:  > /usr/src/libexec/mail.local: These libraries should be LIBADD+=foo  > rather than DPADD/LDADD+=-lfoo:  ssl crypto > > > I have the following flags in /etc/make.conf: > > SENDMAIL_CFLAGS= -I/usr/local/include -DSASL=2 -DDNSMAP -DSTARTTLS > SENDMAIL_LDFLAGS= -L/usr/local/lib > SENDMAIL_LDADD= -lsasl2 -lssl -lcrypto > > >   So I trhought OK, simple enough looking at the error and changed this  > over to the following: > > SENDMAIL_CFLAGS= -I/usr/local/include -DSASL=2 -DDNSMAP -DSTARTTLS > SENDMAIL_LDFLAGS= -L/usr/local/lib > SENDMAIL_LIBADD+= sasl2 ssl crypto > >   After that the error received was that I didn't has sasl2: > > --- ELF/Arch/AMDGPU.o --- > c++   -O2 -pipe -march=nocona -I/usr/src/contrib/llvm/tools/lld/ELF  > -I/usr/src/contrib/llvm/tools/lld/include  > -I/usr/obj/usr/src/usr.bin/clang/lld  > -I/usr/obj/usr/src/lib/clang/libllvm -I/usr/src/lib/clang/include  > -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL  > -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DNDEBUG  > -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd11.1\"  > -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd11.1\" -DDEFAULT_SYSROOT=\"\"  > -ffunction-sections -fdata-sections -g -MD -MF.depend.ELF_Arch_AMDGPU.o  > -MTELF/Arch/AMDGPU.o -fstack-protector-strong -Wno-empty-body  > -Wno-string-plus-int -Wno-unused-const-variable  > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality  > -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef  > -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum  > -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments  > -std=c++11 -fno-exceptions -fno-rtti -stdlib=libc++  > -Wno-c++11-extensions  -c  > /usr/src/contrib/llvm/tools/lld/ELF/Arch/AMDGPU.cpp -o ELF/Arch/AMDGPU.o > --- all_subdir_usr.sbin --- > deliver.o: In function `endmailer': > /usr/src/contrib/sendmail/src/deliver.c:3874: undefined reference to  > `sasl_dispose' > deliver.o: In function `deliver': > /usr/src/contrib/sendmail/src/deliver.c:3137: undefined reference to  > `sasl_getprop' > main.o: In function `main': > /usr/src/contrib/sendmail/src/main.c:2303: undefined reference to  > `sasl_server_init' > /usr/src/contrib/sendmail/src/main.c:2305: undefined reference to  > `sasl_errstring' > sasl.o: In function `sm_sasl_init': > /usr/src/contrib/sendmail/src/sasl.c:146: undefined reference to  > `sasl_set_alloc' > sfsasl.o: In function `sasl_read': > /usr/src/contrib/sendmail/src/sfsasl.c:224: undefined reference to  > `sasl_decode' > sfsasl.o: In function `sasl_write': > /usr/src/contrib/sendmail/src/sfsasl.c:311: undefined reference to  > `sasl_getprop' > /usr/src/contrib/sendmail/src/sfsasl.c:316: undefined reference to  > `sasl_encode' > srvrsmtp.o: In function `smtp': > /usr/src/contrib/sendmail/src/srvrsmtp.c:951: undefined reference to  > `sasl_server_new' > /usr/src/contrib/sendmail/src/srvrsmtp.c:1004: undefined reference to  > `sasl_setprop' > /usr/src/contrib/sendmail/src/srvrsmtp.c:1018: undefined reference to  > `sasl_setprop' > /usr/src/contrib/sendmail/src/srvrsmtp.c:1069: undefined reference to  > `sasl_setprop' > /usr/src/contrib/sendmail/src/srvrsmtp.c:1081: undefined reference to  > `sasl_setprop' > /usr/src/contrib/sendmail/src/srvrsmtp.c:1083: undefined reference to  > `sasl_setprop' > srvrsmtp.o:/usr/src/contrib/sendmail/src/srvrsmtp.c:2254: more undefined  > references to `sasl_setprop' follow > > > >   So apparently that change seems to be including ssl and crypto but not  > sasl2 for some reason.    I have googled looking for examples of how to  > correct it, but everything I find shows the original way I had it to  > start with, and clearly that is no longer working.  Any ideas on how I  > need to define this would be most appreciated.. > > --- > Howard Leadmon > PBW Communications, LLC > http://www.pbwcomm.com > >From looking at the sendmail makefile, it looks like the ssl and crypto libraries are now added automatically unless you use the WITHOUT_OPENSSL build option, it contains this: .if ${MK_OPENSSL} != "no" # STARTTLS support CFLAGS+= -DSTARTTLS -D_FFR_TLS_1 LIBADD+= ssl crypto .endif I think that means you can now reduce the settings in your make.conf to SENDMAIL_CFLAGS= -I/usr/local/include -DSASL=2 -DDNSMAP SENDMAIL_LDFLAGS= -L/usr/local/lib SENDMAIL_LDADD= -lsasl2 and I think you won't get the LIBADD warning for -lsasl2 because it's not a standard base library (but I'm not sure of that). -- Ian