From owner-freebsd-questions@freebsd.org Sun May 28 06:13:35 2017 Return-Path: Delivered-To: freebsd-questions@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 85DC5D852A2 for ; Sun, 28 May 2017 06:13:35 +0000 (UTC) (envelope-from lie@eecg.toronto.edu) Received: from m2.ece.utoronto.ca (mail.ece.utoronto.ca [128.100.10.107]) by mx1.freebsd.org (Postfix) with ESMTP id 602F91621 for ; Sun, 28 May 2017 06:13:34 +0000 (UTC) (envelope-from lie@eecg.toronto.edu) Received: from mail.ece.utoronto.ca (mail.ece.utoronto.ca [128.100.10.107]) by m2.ece.utoronto.ca (8.15.1/8.14.5) with ESMTP id v4S6DS2i005282; Sun, 28 May 2017 02:13:28 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eecg.toronto.edu; s=mail; t=1495952008; bh=mPO6dACNEqFStsRy0CE5JEwDqxK5WVoXRbJYurVHjQE=; h=From:To:Cc:References:In-Reply-To:Subject:Date; b=Qknlg1kZvWOSVe6h9NPpmSQgxfbITWZd1sOqBwF3HVImRGUt4+TUCFhfQbXhoC0Qm ucw7dej2NoithfNpPKuVoKwl8y6sLRC9X5eY83/LzgBL6TUmQPRlWwb+IBdCOzvQMJ +kW1u1OeOxTxt3E00dyx4RcFBH8mHuumQ4J1EziA= Received: from Heavenly (c-73-15-64-253.hsd1.ca.comcast.net [73.15.64.253]) (authenticated bits=0) by mail.ece.utoronto.ca (8.15.1/8.14.5) with ESMTPSA id v4S6DRRK005278 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 28 May 2017 02:13:27 -0400 (EDT) From: "David Lie" To: "'Dylan Williams'" Cc: "'Mingyue Yang'" , References: <083a01d2d69b$c66a0ec0$533e2c40$@eecg.toronto.edu> In-Reply-To: Subject: RE: Help For Getting Bug Reports in Issue Tracker Date: Sat, 27 May 2017 23:13:26 -0700 Message-ID: <099d01d2d779$85738200$905a8600$@eecg.toronto.edu> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQHS1nM8KkExPKG6c0+yTAeCOuQ+u6IHnxsAgAFlA2OAAED9QA== Content-Language: en-us Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2017 06:13:35 -0000 Hi Dylan: Thank you for taking the time to explain. We certainly don't need access to that personal information, but we are interested in the text and discussions describing the bugs. Of course, I understand that it could be a difficult task to separate the text in the bug descriptions from the personal data in a database in a way that ensured that no personal data was being shared. We will think about other ways we could conduct our study. Thanks again for your help. David From: Dylan Williams [mailto:freebsd@host852.com] Sent: Saturday, May 27, 2017 7:17 PM To: David Lie Cc: Mingyue Yang ; freebsd-questions@FreeBSD.org Subject: Re: Help For Getting Bug Reports in Issue Tracker Hi David, My concern is to do with any personal data that may be held in the database - names, email addresses, telephone numbers, addresses DOB, etc. Unfortunately this is a complex and evolving area of law around the world and your request is likely more challenging because it involves cross-border data transfer issues. However, there are couple of universal concepts/concerns to consider: DATA CONTROLLER - As a data controller, the FreeBSD project must be careful about simply passing on a database containing the personal data of a large number of individuals to a third party without the consent of those users. DATA PROCESSING - Your team would be a data processor and you risk exposing yourselves to breaches in data privacy laws if you process the personal data of the FreeBSD community without consent from users. The general rule is that individuals must give unambiguous consent after being fully informed. In this case FreeBSD developers may have consented to having their personal data available to the FreeBSD community but they did not consent to having it processed as part of a university study. Hope that helps. Dylan. On 27 May 2017, at 11:46 AM, David Lie > wrote: Hi Dylan: Privacy and personal data issues were not something we anticipated. I understand the need for caution around these. Can you elaborate on what the issues are? I had thought that since the bug data bases are publicly searchable anyways, there was no more information being revealed by sharing. Is there information in the dumps that isn't available in the web interface? Or is it more the concern of having all of the information shared at once? We are public university in Canada and as such adhere to norms governing research involving human subjects and personal information. If we sought Ethics Review Board review for this research, would this allay concerns? Thanks, David Lie -- Professor Canada Research Chair in Secure and Reliable Computer Systems Department of Electrical and Computer Engineering University of Toronto From: Dylan Williams [mailto:freebsd@host852.com] Sent: Friday, May 26, 2017 5:59 PM To: Mingyue Yang > Cc: freebsd-questions@FreeBSD.org ; David Lie > Subject: Re: Help For Getting Bug Reports in Issue Tracker I see potential data privacy/personal data issues associated with this request. Suggest to proceed with caution. On 27 May 2017, at 6:57 AM, Mingyue Yang > wrote: Hello FreeBSD Team, I am a student from University of Toronto doing research. My research topic is to automatically detect security vulnerabilities using machine learning techniques. As part of my research, I need to obtain bug samples and fixes related to security vulnerabilities. I am currently looking into bug reports in the issue tracker of your project: https://bugs.freebsd.org/bugzilla/. However, crawling the bug tracking repository may not be the best thing to do, as it may be harmful to the website. Thus I am wondering if it is possible to obtain the entire bug tracking database including summary, comments and other status fields for all bug reports? Help is really appreciated! Thank you, Shirley Yang _______________________________________________ freebsd-questions@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org " _______________________________________________ freebsd-questions@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org " From owner-freebsd-questions@freebsd.org Sun May 28 15:31:00 2017 Return-Path: Delivered-To: freebsd-questions@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 A7046D84B7E; Sun, 28 May 2017 15:31:00 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-qt0-x242.google.com (mail-qt0-x242.google.com [IPv6:2607:f8b0:400d:c0d::242]) (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 65B9814B3; Sun, 28 May 2017 15:31:00 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-qt0-x242.google.com with SMTP id r58so6697165qtb.2; Sun, 28 May 2017 08:31:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:subject :content-transfer-encoding; bh=7a+7qJ00GC7x83Qv3XHM+C++qvouC3E8tRTKmM9JMBA=; b=R/ojHz51LfTAaP9+IarryWgVCDmh/iYsI+L/PnfSNl4H5QNwFCDZG464KfLjwQHt5/ Q+T17mrePB2Fd3/J2DlDl+qZdyo2jyEMs9AauUG9NtQsANzM2AgBvz6ajjdWlbwCL99l uLBp0NSz79CofR9P94Ls1ejrqlQ0qax5MRwmYW1Ul35t2+ZnCi9eQ6NsqS5UZr8E7Zhv Cn1UOKpWeglIlnsU2PgVQHOSSc/kaG3E91GWiYlbipqfkc8rbZ89V7vurtvTAcKaFOkA Fh3MUJ2z0Us0E8dVWQBR/A7SZsWd11zP577UVphLgTc1HDQ2nRcbJgNO38WM9vN/WEOH hC6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-transfer-encoding; bh=7a+7qJ00GC7x83Qv3XHM+C++qvouC3E8tRTKmM9JMBA=; b=sy0OYgcbVcN3wsS5Qet9QQ2M+X2M+tqX20ZdZduW+c9V5hfnd8+j08tgNtlYthLu0c 64mzBoNLjFpUgfvBHKMK2JV+hrl2WEJ8kf/33szmuB89Rn7yVepzFRhwLJW1w+uSiNLt acnk7RlUvEqEDjuwCDnbpyV0RzcVWzk7EoN0RvGuvl37lK5quX0rJBh/ccaRBNCJy3fW biFatt0WV0K2odPPerf1Z5OxplktYBtHJDIH+Xcppa1Bd2Q4F17b4q4IwyfwAW0ocayW /qngfnOnEi7Ef4mKohwX//Mqn+j90VKZTK3LWLlpcWlcojdpCJF/QoJY9f3a2vvAByeL 6PbQ== X-Gm-Message-State: AODbwcAig0H2fJ2OSg1od53DfNRr6WaHvX6Xjskyl4iHxlXOR5vkNEFe vgwOa8NN+2D0sKXH X-Received: by 10.200.36.162 with SMTP id s31mr14225683qts.224.1495985459280; Sun, 28 May 2017 08:30:59 -0700 (PDT) Received: from [10.0.10.3] (cpe-74-141-88-57.neo.res.rr.com. [74.141.88.57]) by smtp.googlemail.com with ESMTPSA id a70sm1427203qkj.47.2017.05.28.08.30.58 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 28 May 2017 08:30:58 -0700 (PDT) Message-ID: <592AED43.3090007@gmail.com> Date: Sun, 28 May 2017 11:31:15 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: "freebsd-doc@freebsd.org" , "freebsd-questions@freebsd.org" Subject: handbook TOC Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2017 15:31:00 -0000 Been working on updating a chapter in the English version of the handbook. I deleted a section from the chapter.xml file and now keep getting an error code 4 from the "make". How is the TOC [table of contents] built? Is it a file that contains all the chapter sect headers? When I delete a section from a chapter do I also have to remove said section header from some file that the build of the TOC uses? The igor pgm does not seem to test for open and close of sections headers like it does for other tags. Is there some reason for this? From owner-freebsd-questions@freebsd.org Sun May 28 21:53:43 2017 Return-Path: Delivered-To: freebsd-questions@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 1D3C8D86730; Sun, 28 May 2017 21:53:43 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-ua0-x234.google.com (mail-ua0-x234.google.com [IPv6:2607:f8b0:400c:c08::234]) (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 CFBB21DC0; Sun, 28 May 2017 21:53:42 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: by mail-ua0-x234.google.com with SMTP id u10so27479950uaf.1; Sun, 28 May 2017 14:53:42 -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:cc; bh=SwTRVluGy3Y1VAZuZiQEvlLJL+6FDpEMtS7ZjKes6dU=; b=riTI8VG7VlQCoEFwwDmScJf4tPnUFubV1Fx79dk2En17a8Zu240Bg92OXAjU/SnMlT aAAnagGngcrDb1/Esomvsb/v2jCgmCJ25O9q6m8nsVgyRw55sBL8YlreC/pxhGLjn1yI KZL0O38fpJAFW+LIshdJcN/UswbQXfCr4RQ75/szYUn2I3UrTg0xgeJlj0WqpXygJEYb aoMXZjSky99zcGxO2xjRyE7JtFO3wGFqBn77Dl2rbId8vojDliPUyXycDeKIXfLCJjj8 dcSHvb+s+DGiOXjKgs3se1VMaBzKpVRd6//4zw3renUlone2e4yATdiGZPpuQyGzB6W/ vZhA== 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:cc; bh=SwTRVluGy3Y1VAZuZiQEvlLJL+6FDpEMtS7ZjKes6dU=; b=sN40JFyoSxj+3doXY2j9ZUYEEy2TO3SNfOMUFbnFFoQL4j0MKKCBjba9f3BnPnrMJF 3dneHjUVzRG6UU7HJU5738Gy4FwnaQq5fcJvi7vLsAoFrPLfHTismRd7ScmYy3NylUqp 4yx2dER6FZZ4GZhcWyNPXdfK2103ayHLbkDL22Wono6+dHb+/VDZrjmn8ImTbnRd9dgy 7mZDttXnILDhozF/erYQzeHOyaw/Yxr0bE2a9ABJxf7O17fOFwvweKmOsMDr4KdrKoDh aI8M64Rl8kGjcvxukRgfnd4t6sL0POA/zuGY74OL/5Bc1tbHKuaUI5TcISWL5H5lj/RW cxpg== X-Gm-Message-State: AODbwcCtFpc1adCP3gQdiRUjnVknwFnCYC0aMIT3l7DSfgyDxFf8NvM8 G9ErjLBStQ7yk0ke3UCHk8Tb4psgv0Ve X-Received: by 10.159.48.213 with SMTP id k21mr6410901uab.6.1496008421851; Sun, 28 May 2017 14:53:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.159.35.85 with HTTP; Sun, 28 May 2017 14:53:01 -0700 (PDT) From: grarpamp Date: Sun, 28 May 2017 17:53:01 -0400 Message-ID: Subject: Intel / AMD CPU Microcode Updates Required For Security To: freebsd-questions@freebsd.org Cc: freebsd-security@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2017 21:53:43 -0000 Blobs that fix exploitable things may be slightly better than blobs. Awareness should be raised, and updates applied to systems. # sysutils/devcpu-data New Microcode Released for Intel / AMD https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219268 From owner-freebsd-questions@freebsd.org Sun May 28 22:34:35 2017 Return-Path: Delivered-To: freebsd-questions@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 66BB1D86F9D for ; Sun, 28 May 2017 22:34:35 +0000 (UTC) (envelope-from pipfstarrd@openmailbox.org) Received: from mail.openmailbox.org (lb1.openmailbox.org [5.79.108.160]) (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 21EE710AE for ; Sun, 28 May 2017 22:34:34 +0000 (UTC) (envelope-from pipfstarrd@openmailbox.org) Received: by mail.openmailbox.org (Postfix, from userid 20002) id B118D50E517; Mon, 29 May 2017 00:34:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org; s=openmailbox; t=1496010865; bh=pYArSvzHAyaADN6/7izqo7ZOTrZ9cmLI6WRtvGE1hgY=; h=Subject:To:References:From:Date:In-Reply-To:From; b=BlTnqJHqoL6spY9ji892ebvDamDhrGdmERJaixaqlbzhxgoG2cBZ8p0qw/IiOPcil IaFbbaDmWdNZ/T9+o0mZeivYhzfIs4OF54BzYPL9tt8RGk4JwnogTZlnYMvEG6uABC FdCAhvBUu28vf6FrS4VooNwnJnAwR5tYOf1SWVmA= Subject: Re: Intel / AMD CPU Microcode Updates Required For Security DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org; s=openmailbox; t=1496010865; bh=pYArSvzHAyaADN6/7izqo7ZOTrZ9cmLI6WRtvGE1hgY=; h=Subject:To:References:From:Date:In-Reply-To:From; b=BlTnqJHqoL6spY9ji892ebvDamDhrGdmERJaixaqlbzhxgoG2cBZ8p0qw/IiOPcil IaFbbaDmWdNZ/T9+o0mZeivYhzfIs4OF54BzYPL9tt8RGk4JwnogTZlnYMvEG6uABC FdCAhvBUu28vf6FrS4VooNwnJnAwR5tYOf1SWVmA= To: freebsd-questions@freebsd.org References: From: Daniil Berendeev Message-ID: <38857797-1322-ddf8-7a21-3907d7ffaf29@openmailbox.org> Date: Sun, 28 May 2017 22:34:16 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2017 22:34:35 -0000 Little baby Blobby was a cute little baby when we found him on the beach, there was nothin' shady ... On 28.05.2017 21:53, grarpamp wrote: > Blobs that fix exploitable things may be slightly better than blobs. > Awareness should be raised, and updates applied to systems. -- Cheers~ PGP key fingerprint: 07B3 2177 3E27 BF41 DC65 CC95 BDA8 88F1 E9F9 CEEF You can retrieve my public key at pgp.mit.edu. From owner-freebsd-questions@freebsd.org Sun May 28 23:34:56 2017 Return-Path: Delivered-To: freebsd-questions@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 97154D8612E; Sun, 28 May 2017 23:34:56 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (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 2BC671DCC; Sun, 28 May 2017 23:34:56 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wm0-x241.google.com with SMTP id k15so13827305wmh.3; Sun, 28 May 2017 16:34:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=KhdDARm5imrXSfn+OIpxXwu21vQ4QkErvLk3MZqnc3o=; b=aqF5oxNCTj7dp7SXl7fSFkh91/WKEihATu701a3gis4920zm5xUll507yCA26smrTB uHbnO657FD7Mly1F792P8vBY/y/e8T9uPmf2jIWA+g9yjxdBmFdanHO9qOEGK8t1ZCJZ qLwyqDSrFwSdnXc2bzzD+IHVFTnbamDGA8nrH7GkbtLBfqmdOUylGGkjv10nqYNjbjnv nne6Tk+5Cy5H6ccxJFGE9T5INENRNOnVm5N9yv8+FuCAewrReJ0aneTDhoqWTBgMEf2O lYBYB6Zmcy3Ijk4ORhEaX46t7m8pFM6wkT01albChvjfK3l6bFXHBpzWgSpqLKaciDMQ 2X6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=KhdDARm5imrXSfn+OIpxXwu21vQ4QkErvLk3MZqnc3o=; b=hEEcQ8gq3QKdXZcZUtO8Cjd6Kjfu5GeTCVvyx51fFVoYpzEhCcf9UHDRo5kmsOlOa6 0kZWaNnr4UiklHwBTlLJMwNOK6b7o3yhCN3TcJRz+gYk6utgKC2kkK3vAcDZfVzchZJs fT//0D/cpsl/XwdJZ4mqk0jOifCqggNl/+qxW44iZ5kU3Fh7SAFQGXSZSfhpM8anHwGj PY4qAht/dzSwd3uTirXHMnqy0+mM1/prIioK4MO34MVi5aNtr4gomSaAuPhMa1W+ZdtB m5TjJeYRk14CN3T5anLCNKgR8wd/zc5PTOB7TUbZHz9f7GHBuZ5AkzNc65l9d0xs13Pk ze+A== X-Gm-Message-State: AODbwcBn1RBAmGjL/5zI9aWXcE80IkRwE43VsqrxDRMB8Qmjm8kvV2pI AoUcjAEbmuKCxVNz X-Received: by 10.28.26.208 with SMTP id a199mr21168494wma.116.1496014494441; Sun, 28 May 2017 16:34:54 -0700 (PDT) Received: from gumby.homeunix.com ([81.17.24.158]) by smtp.gmail.com with ESMTPSA id k18sm6019512wre.9.2017.05.28.16.34.52 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 28 May 2017 16:34:53 -0700 (PDT) Date: Mon, 29 May 2017 00:34:51 +0100 From: RW To: freebsd-questions@freebsd.org, freebsd-security@freebsd.org Subject: Re: Intel / AMD CPU Microcode Updates Required For Security Message-ID: <20170529003451.7835d616@gumby.homeunix.com> In-Reply-To: References: X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2017 23:34:56 -0000 On Sun, 28 May 2017 17:53:01 -0400 grarpamp wrote: > Blobs that fix exploitable things may be slightly better than blobs. > Awareness should be raised, and updates applied to systems. > > # sysutils/devcpu-data New Microcode Released for Intel / AMD > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219268 Is there a standard way to run cpucontrol? There doesn't seem to be an rc.d script. From owner-freebsd-questions@freebsd.org Sun May 28 23:52:58 2017 Return-Path: Delivered-To: freebsd-questions@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 D960CD86733; Sun, 28 May 2017 23:52:58 +0000 (UTC) (envelope-from woodsb02@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 4E60B9D2; Sun, 28 May 2017 23:52:58 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-wm0-x22e.google.com with SMTP id e127so38357760wmg.1; Sun, 28 May 2017 16:52:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=FE4zTVEfFdOCNENfgiDzpRom8z2vM+bv1uQ81QnYJrU=; b=plX4VBeqdM7OdWtp3uJgspKXbdfSvb5wycNDgJlphlzQk4lNfiX9x1n3YRHLHt/Wf7 rzzEJlI3lyIZbAzhas32CLq44ZXppPouiIIeEcw9/SzycBdkwph5L8fw9RbaNDeFQugg IzMeEJ9BqHWUoHz4gOUMYIcoW8G1YsY0RVf3pXX1X60/atJUR3RycYrM+hsZ2t20FEg9 J5MxxIF/77CDjeaYTBK62+HbbSbHKzxcZYOHEQIIeYy/DLSmGP39sQw3KvyqAFKviNYL SqYoGKTZxjOtQ4wSSuXBnj5JdUt1KWJYTYuPvxi76zvgIaqivG9ZL101Vm1gG1PoHb59 4CSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=FE4zTVEfFdOCNENfgiDzpRom8z2vM+bv1uQ81QnYJrU=; b=oHkGL6Y0rCLbs54EKEyWsyCcFua9Ubw6kqzyDUkG7d+tdBOo2qcjYJgPxMP9W7UU/Z ZW7sWIaqLd346zgBMoS2dyCfJBCCnnD4hIciPzPpzQ+GnH4VbMT2AbDJjnvyUYWFbtMg MJBEzvS/3j3b6g4JEUyhaXsjK8ZnDzQjUnVCVEecp6d76nITDicEK0dybq37//tiZsBX kvK1u3X9w5LqqWPvuik8JdoQud5OETDOWTrW1F6ujI2C1xNKDpcj8a+A3kwzxLRF5fm2 0tJNvBKDQQrr0itFDCbINNv+LtoYEhxxamkKttS6aBCaaC2Jcu9/XmDWwE62TP7kAWU/ ct+w== X-Gm-Message-State: AODbwcD7oaVZ4zmui870Y1tTvc1xGVohZHKiW2Kq53ldsoQFX9sOAIhy oDZ8bQzXuDFpWD1OSwSlMbyCgXDGX6Bo X-Received: by 10.80.163.131 with SMTP id s3mr10571215edb.156.1496015576705; Sun, 28 May 2017 16:52:56 -0700 (PDT) MIME-Version: 1.0 References: <20170529003451.7835d616@gumby.homeunix.com> In-Reply-To: <20170529003451.7835d616@gumby.homeunix.com> From: Ben Woods Date: Sun, 28 May 2017 23:52:46 +0000 Message-ID: Subject: Re: Intel / AMD CPU Microcode Updates Required For Security To: RW , freebsd-questions@freebsd.org, freebsd-security@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2017 23:52:59 -0000 On Mon, 29 May 2017 at 7:35 am, RW via freebsd-questions < freebsd-questions@freebsd.org> wrote: > On Sun, 28 May 2017 17:53:01 -0400 > grarpamp wrote: > > > Blobs that fix exploitable things may be slightly better than blobs. > > Awareness should be raised, and updates applied to systems. > > > > # sysutils/devcpu-data New Microcode Released for Intel / AMD > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219268 > > Is there a standard way to run cpucontrol? There doesn't seem to be an > rc.d script. There is an rc script installed with this port: https://svnweb.freebsd.org/ports/head/sysutils/devcpu-data/files/microcode_update.in?view=markup Regards, Ben > -- -- From: Benjamin Woods woodsb02@gmail.com From owner-freebsd-questions@freebsd.org Mon May 29 09:20:48 2017 Return-Path: Delivered-To: freebsd-questions@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 C3AC9CF6788 for ; Mon, 29 May 2017 09:20:48 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 5508F724A8 for ; Mon, 29 May 2017 09:20:47 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) X-AuditID: c1b4fb25-73a9f9a0000055fe-4d-592be7ebec85 Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id C7.F5.22014.BE7EB295; Mon, 29 May 2017 11:20:44 +0200 (CEST) Received: from duper.otp.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.62) with Microsoft SMTP Server id 14.3.339.0; Mon, 29 May 2017 11:20:43 +0200 Received: from duper.otp.ericsson.se (localhost [127.0.0.1]) by duper.otp.ericsson.se (8.15.2/8.15.2) with ESMTP id v4T9KhkU091538 for ; Mon, 29 May 2017 11:20:43 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) Received: (from raimo@localhost) by duper.otp.ericsson.se (8.15.2/8.15.2/Submit) id v4T9KhbY091537 for freebsd-questions@freebsd.org; Mon, 29 May 2017 11:20:43 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) X-Authentication-Warning: duper.otp.ericsson.se: raimo set sender to raimo+freebsd@erix.ericsson.se using -f Date: Mon, 29 May 2017 11:20:43 +0200 From: Raimo Niskanen To: Subject: Advice on kernel panics Message-ID: <20170529092043.GA89682@erix.ericsson.se> Mail-Followup-To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline User-Agent: Mutt/1.7.2 (2016-11-26) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUyM2K7je6b59qRBvfPMVm8/LqJxYHRY8an +SwBjFFcNimpOZllqUX6dglcGeceP2YtmCRVsWDqdLYGxnnCXYycHBICJhLvrvaxg9hCAkcY JU5/Du9i5AKyNzJK7JuzmgXCaWeSmHxtP1sXIweQ85RR4r4aRHOOxNtPR5lAbBYBVYlZ064w gthsAqYSjT/PsILYIgLKEv+uXWQGsYUFFCTWf17PBmLzAtVsbXjDAmHrS3xc8YoVwhaUODnz CVicWUBHYsHuT2BrmQWkJZb/4wAxRUFGfmWFOFlbYsKbA6wTGAVnIWmehaR5FkLzAkbmVYyi xanFSbnpRsZ6qUWZycXF+Xl6eaklmxiBQXlwy2/VHYyX3zgeYhTgYFTi4f10QjtSiDWxrLgy 9xCjBAezkgjv7cdAId6UxMqq1KL8+KLSnNTiQ4zSHCxK4ryO+y5ECAmkJ5akZqemFqQWwWSZ ODilGhhldmufMWR8/2tnwO7sGJ/aL74rzrz9tvXo/KXn3uWuzOb61lEcIjxRZa/zcwEONqG4 O2YS9xf8Stn6XignYd29okPeJjx+Hj+EpzcsLui5Nakx9+NHv9VXUiILOp2iFr+XyP2u4rWv Z9bkk/xdByd92Mi/+MvvurMX32kzhZ8SOpeQpeC+6ORSJZbijERDLeai4kQALAfSOkYCAAA= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 May 2017 09:20:48 -0000 Hello list. I have a server that panics about every 3 days and need some advice on how to handle that. It currently has 7 dumps in /var/crash/, head of the latest core.txt.4 looks like this: ======= sasquatch.otp.ericsson.se dumped core - see /var/crash/vmcore.4 Mon May 29 03:15:32 CEST 2017 FreeBSD sasquatch.otp.ericsson.se 10.3-RELEASE-p18 FreeBSD 10.3-RELEASE-p18 #0: Tue Apr 11 10:31:00 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 panic: page fault GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor write data, page not present instruction pointer = 0x20:0xffffffff809fb017 stack pointer = 0x28:0xfffffe04673a18c0 frame pointer = 0x28:0xfffffe04673a1900 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 18 (syncer) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0xffffffff8098e7e0 at kdb_backtrace+0x60 #1 0xffffffff809514b6 at vpanic+0x126 #2 0xffffffff80951383 at panic+0x43 #3 0xffffffff80d5646b at trap_fatal+0x36b #4 0xffffffff80d5676d at trap_pfault+0x2ed #5 0xffffffff80d55dea at trap+0x47a #6 0xffffffff80d3bdb2 at calltrap+0x8 #7 0xffffffff809f9b23 at vfs_msync+0x203 #8 0xffffffff809fb858 at sync_fsync+0x108 #9 0xffffffff80e81ed7 at VOP_FSYNC_APV+0xa7 #10 0xffffffff809fc27b at sched_sync+0x3ab #11 0xffffffff8091a93a at fork_exit+0x9a #12 0xffffffff80d3c2ee at fork_trampoline+0xe Uptime: 2d19h53m15s ======= What sticks out later in core.txt.4 is the fstat section that contains a lot of errors, but I can not tell if that is just a secondary symptom... Looks like this: ======= fstat fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 fstat: can't read znode_phys at 0x1 : USER CMD PID FD MOUNT INUM MODE SZ|DV R/W root sed 78401 root - - error - root sed 78401 wd - - error - root sed 78401 text - - error - root sed 78401 0* pipe fffff8001800f000 <-> fffff8001800f160 0 rw root grep 78400 root - - error - root grep 78400 wd - - error - root grep 78400 text - - error - : ======= To me the other core.txt.? files does not look exactly the same. All have an fstat section with many errors, though. Does anyone have some advice on how to proceed? -- / Raimo Niskanen, Erlang/OTP, Ericsson AB From owner-freebsd-questions@freebsd.org Tue May 30 03:38:06 2017 Return-Path: Delivered-To: freebsd-questions@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 F3B59AFA499; Tue, 30 May 2017 03:38:05 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) (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 8A364755DC; Tue, 30 May 2017 03:38:05 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074422-a3dff70000006d80-74-592ce91a151d Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id B1.17.28032.A19EC295; Mon, 29 May 2017 23:38:03 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id v4U3c1fU016061; Mon, 29 May 2017 23:38:01 -0400 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v4U3bv2Y006271 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 29 May 2017 23:38:00 -0400 Date: Mon, 29 May 2017 22:37:57 -0500 From: Benjamin Kaduk To: Ernie Luzar Cc: "freebsd-doc@freebsd.org" , "freebsd-questions@freebsd.org" Subject: Re: handbook TOC Message-ID: <20170530033757.GK39245@kduck.kaduk.org> References: <592AED43.3090007@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <592AED43.3090007@gmail.com> User-Agent: Mutt/1.7.1 (2016-10-04) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrIIsWRmVeSWpSXmKPExsUixG6noiv9UifS4OB9ZotTZ7pYLV5+3cRi cf30JHYHZo8Zn+azeOycdZc9gCmKyyYlNSezLLVI3y6BK+PSsX6mgk7OikNzfjM3MHawdzFy ckgImEjM+rgKyObiEBJYzCSxess6VghnI6PEtr8vmCCcq0wSTy/fZwFpYRFQlVi1tYsZxGYT UJFo6L4MZosA2Zu3PGUDaWAWaGSU6Pt/GGyHsICkxK3T69hAbF6gfTsOrgVrEBLQkOi8twQq LihxcuYTsAXMAloSN/69BNrMAWRLSyz/xwES5hTQlDj84xNYq6iAssTfw/dYJjAKzELSPQtJ 9yyE7gWMzKsYZVNyq3RzEzNzilOTdYuTE/PyUot0TfVyM0v0UlNKNzGCQ9ZFaQfjxH9ehxgF OBiVeHg3qOhECrEmlhVX5h5ilORgUhLl3XgMKMSXlJ9SmZFYnBFfVJqTWnyIUYKDWUmEt/oU UI43JbGyKrUoHyYlzcGiJM4rrtEYISSQnliSmp2aWpBaBJOV4eBQkuCd8hyoUbAoNT21Ii0z pwQhzcTBCTKcB2j4G5Aa3uKCxNzizHSI/ClGRSlx3jUgCQGQREZpHlwvKKVIZO+vecUoDvSK MO9tkCoeYDqC634FNJgJaPCuHdogg0sSEVJSDYyt+ne1bfdoN+4U3XT8m4ug5YslqoanHC70 rk/cU9pw6si8aIYHrVtzdheKi1fwNMzP+zjrWLPHd9m/2Tvtzyz4t+PQ95PNuampk0558Vy1 9Xp68yrn0qu7e23WaNSIHDRdf2pPd9LW0Lz5V6Uz8144TLuYZe3Bzie/yrlut2VMmtO/BZGW hgVKLMUZiYZazEXFiQDVvBqJBAMAAA== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 03:38:06 -0000 On Sun, May 28, 2017 at 11:31:15AM -0400, Ernie Luzar wrote: > Been working on updating a chapter in the English version of the > handbook. I deleted a section from the chapter.xml file and now keep > getting an error code 4 from the "make". Without looking at the actual patch and build log in question, my guess would be that here is something somewhere else in the handbook that tries to refer to the now-deleted section (by id) producing the error. > How is the TOC [table of contents] built? > Is it a file that contains all the chapter sect headers? > When I delete a section from a chapter do I also have to remove said > section header from some file that the build of the TOC uses? I do not believe you need to delete a section header from the TOC specifically when deleting a section. But, the XML id for that section may be referenced from a different part of the document, so it would be worth grepping through to see if it is still referenced. > The igor pgm does not seem to test for open and close of sections > headers like it does for other tags. Is there some reason for this? I don't know, sorry. -Ben From owner-freebsd-questions@freebsd.org Tue May 30 10:44:46 2017 Return-Path: Delivered-To: freebsd-questions@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 B4F3BB79092 for ; Tue, 30 May 2017 10:44:46 +0000 (UTC) (envelope-from 0101015c58b3dc58-1b936a1a-8412-472b-a257-c436a40e89f2-000000@us-west-2.amazonses.com) Received: from a27-35.smtp-out.us-west-2.amazonses.com (a27-35.smtp-out.us-west-2.amazonses.com [54.240.27.35]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 93FED806F6 for ; Tue, 30 May 2017 10:44:46 +0000 (UTC) (envelope-from 0101015c58b3dc58-1b936a1a-8412-472b-a257-c436a40e89f2-000000@us-west-2.amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=stdm37fqbypyvw6iolbo3nkyd73es3w7; d=vmeta.jp; t=1496136801; h=MIME-Version:Content-Type:Content-Transfer-Encoding:Date:From:To:Subject:Message-ID; bh=+sbgQiHzPcqL2tzRt/vVTMDKByiWCD3VkG1sHOiffsE=; b=mPD7Mk0aAWH3SAX3eP7WVc7RN448gfjlrDwD3TjrpFmxOQRM2SzAEZL2B9zwa9FW 4MY3VWkI89TJHbC0GZvIUwLtCwyZOrh7auTgXJuTcuZ7XUk+bD4f+JMRjCEaGpQptas jubfWxIhSoRxCYIuwrBBayOxve/4spUr9DfO4fH8= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=hsbnp7p3ensaochzwyq5wwmceodymuwv; d=amazonses.com; t=1496136801; h=MIME-Version:Content-Type:Content-Transfer-Encoding:Date:From:To:Subject:Message-ID:Feedback-ID; bh=+sbgQiHzPcqL2tzRt/vVTMDKByiWCD3VkG1sHOiffsE=; b=MuDhE6XevUR2bQgYX/gojjBjO5wpvg4oonOLe8VZu+rNUnNr7YDRQ2PAbz2f2Lqo fKGcsNI6/CqAKPvm05y32yYTSlX1K31sc+3J8NeWz6z2D0f9Zo7/dH1tx1ybhF/Thpw 97VMYzD+hQfcTRdkR9Ws3DtbfysDwYsw5VsTGeKA= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on glory.vmeta.jp X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.1 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 30 May 2017 09:33:21 +0000 From: Koichiro IWAO To: freebsd-questions@freebsd.org Subject: Is it possible to use more than 1 CPUs during pkg create? Message-ID: <0101015c58b3dc58-1b936a1a-8412-472b-a257-c436a40e89f2-000000@us-west-2.amazonses.com> X-Sender: meta@vmeta.jp User-Agent: Roundcube Webmail/1.2.4 X-SES-Outgoing: 2017.05.30-54.240.27.35 Feedback-ID: 1.us-west-2.ngRt4x2U/cWqug8pbfjwMxB6pcDw1fmN73bGmMLYyRI=:AmazonSES X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 10:44:46 -0000 Hi, is it possible to use more than 1 CPU cores during xz compression done in pkg create? I know XZ Utils in base system can use more than 1 CPUs if -T option given. I guess pkg internally calls APIs of XZ Utils. I think it is potentially possible. Or is it restricted to use only 1 CPU core for some reasons? -- `whois vmeta.jp | nkf -w` meta From owner-freebsd-questions@freebsd.org Tue May 30 10:52:22 2017 Return-Path: Delivered-To: freebsd-questions@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 7B489B7939F for ; Tue, 30 May 2017 10:52:22 +0000 (UTC) (envelope-from jim@mailman-hosting.com) Received: from maurice.jlkmail.com (maurice.jlkmail.com [23.111.151.218]) (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 4F56780CA9 for ; Tue, 30 May 2017 10:52:22 +0000 (UTC) (envelope-from jim@mailman-hosting.com) Received: from maurice.jlkmail.com (localhost [127.0.0.1]) by maurice.jlkmail.com (Postfix) with ESMTP id D3FBD1889C5C for ; Tue, 30 May 2017 06:52:14 -0400 (EDT) Authentication-Results: maurice.jlkmail.com (amavisd-new); dkim=pass (1024-bit key) reason="pass (just generated, assumed good)" header.d=mailman-hosting.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= mailman-hosting.com; h=content-transfer-encoding:mime-version :x-mailer:content-type:content-type:references:in-reply-to:date :date:to:from:from:subject:subject:message-id; s=dkim; t= 1496141533; x=1497005534; bh=r8fv8RKFz4DD94s6ODmI5eBNkVyzniEjcow TVbcdXA4=; b=jJF05yPfkVncMC3tALC/TZ9EYzC4ooimhxjpZur2BTSCt4pzWRG RoLRL7YKBjc8DI/G4V9Mmsyn+10S4O/lMqTzGlCPLvyPLyN00zHTsLq1Jgl2lHSX 71GtWrkx4N0hTl+oIIkmJKQOXC4l5tGkFnU9nxidqJBLXvpwHA0+Ja5I= X-Virus-Scanned: Debian amavisd-new at maurice.jlkmail.com X-Spam-Flag: NO X-Spam-Score: 4.296 X-Spam-Level: **** X-Spam-Status: No, score=4.296 tagged_above=-9999 required=6.31 tests=[ALL_TRUSTED=-1, RAZOR2_CF_RANGE_51_100=0.365, RAZOR2_CF_RANGE_E8_51_100=2.43, RAZOR2_CHECK=2.5, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Received: from maurice.jlkmail.com ([127.0.0.1]) by maurice.jlkmail.com (maurice.jlkmail.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id B0xo4PTMbSia for ; Tue, 30 May 2017 06:52:13 -0400 (EDT) Received: from hogwarts.fios-router.home (static-70-104-198-154.nrflva.fios.verizon.net [70.104.198.154]) by maurice.jlkmail.com (Postfix) with ESMTPSA id 7379C1889A3C; Tue, 30 May 2017 06:52:13 -0400 (EDT) Message-ID: <1496141532.1095.41.camel@mailman-hosting.com> Subject: Re: Is it possible to use more than 1 CPUs during pkg create? From: Jim Ohlstein To: Koichiro IWAO , freebsd-questions@freebsd.org Date: Tue, 30 May 2017 06:52:12 -0400 In-Reply-To: <0101015c58b3dc58-1b936a1a-8412-472b-a257-c436a40e89f2-000000@us-west-2.amazonses.com> References: <0101015c58b3dc58-1b936a1a-8412-472b-a257-c436a40e89f2-000000@us-west-2.amazonses.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 10:52:22 -0000 On Tue, 2017-05-30 at 09:33 +0000, Koichiro IWAO wrote: > Hi, > > is it possible to use more than 1 CPU cores during xz compression > done in pkg create? I know XZ Utils in base system can use more > than 1 CPUs if -T option given. I guess pkg internally calls APIs > of XZ Utils. I think it is potentially possible. > > Or is it restricted to use only 1 CPU core for some reasons? For those using poudriere or synth this might be a disadvantage with multiple parallel builds going on. That said, I imagine the code could be patched to allow it. > > -- Jim Ohlstein Professional Mailman Hosting https://mailman-hosting.com/ From owner-freebsd-questions@freebsd.org Tue May 30 10:55:11 2017 Return-Path: Delivered-To: freebsd-questions@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 DEC11B794F3 for ; Tue, 30 May 2017 10:55:11 +0000 (UTC) (envelope-from milios@ccsys.com) Received: from cargobay.net (cargobay.net [168.235.81.21]) (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 BE51380DF0 for ; Tue, 30 May 2017 10:55:11 +0000 (UTC) (envelope-from milios@ccsys.com) Received: from [192.168.1.47] (c-73-255-128-224.hsd1.fl.comcast.net [73.255.128.224]) by iron.ccsys.com (Postfix) with ESMTPSA id D07B4524; Tue, 30 May 2017 10:55:03 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Is it possible to use more than 1 CPUs during pkg create? From: "Chad J. Milios" In-Reply-To: <0101015c58b3dc58-1b936a1a-8412-472b-a257-c436a40e89f2-000000@us-west-2.amazonses.com> Date: Tue, 30 May 2017 06:55:02 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <0101015c58b3dc58-1b936a1a-8412-472b-a257-c436a40e89f2-000000@us-west-2.amazonses.com> To: Koichiro IWAO , freebsd-questions X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 10:55:12 -0000 > On May 30, 2017, at 5:33 AM, Koichiro IWAO wrote: >=20 > Hi, >=20 > is it possible to use more than 1 CPU cores during xz compression > done in pkg create? I know XZ Utils in base system can use more > than 1 CPUs if -T option given. I guess pkg internally calls APIs > of XZ Utils. I think it is potentially possible. >=20 > Or is it restricted to use only 1 CPU core for some reasons? >=20 >=20 > --=20 > `whois vmeta.jp | nkf -w` > meta Threading forfeits a bit of xz=E2=80=99s great compression ratio. An xz = file created with -T greater than 1 will necessarily be some amount = larger. Operating with just one thread achieves the maximal compression = ratio. (The multiple compression threads fail to share the dictionaries = they are currently building.) When you are transferring GBytes to yourself once, use -T0. When you are = compressing something one time that hundreds or thousands of people will = potentially download and/or store, use -T1 (the default).= From owner-freebsd-questions@freebsd.org Tue May 30 11:10:43 2017 Return-Path: Delivered-To: freebsd-questions@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 7AEA8B799F3 for ; Tue, 30 May 2017 11:10:43 +0000 (UTC) (envelope-from eduardo.lemosdesa@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 10BF981451 for ; Tue, 30 May 2017 11:10:43 +0000 (UTC) (envelope-from eduardo.lemosdesa@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id 7so87417741wmo.1 for ; Tue, 30 May 2017 04:10:42 -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=ALB41x82+7l26nqTIvin6w7SsTuS1//ifqnL/UHyRHo=; b=czb5NqnqseYa815fYxLIel3iKKs4b19oHz/EvJJWmz0m3tb800S68F8ONEICCTBvwt 8EvPf+s84u5u2lpbVkdhtBhEoJKuFYSObZnwU9a91G49nqlpTInDVecKqCw+kVZxCZQQ o07/78ZrkmEgbJXowDWjosJyOqs0DDHNg938o9p7ykNoNeDorGhiZjsAU4RaS5NhVEcP 6aww/inaGJq8VDodCzdsiOIVwyRGxX2PZyYWf5F2VgPQVied4tV/Pjo1fcs7qE0Lv7KB JQA9mHO7UtkzaTsCg4iVjKW5413we4tLvyLQI6+8ApYMsPL9QdK4QxKCs3QClj3TtwPh d1hg== 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=ALB41x82+7l26nqTIvin6w7SsTuS1//ifqnL/UHyRHo=; b=cGdWP0l/te6WwW3UgPI2Q5dAuem6+rpjC2bIc0cWvpqEJADCchnWLHGbcBKAdlu7da 5hS8HA22AAcG4T+aB/D3gHLTEt5d3ooOAExsCTzROgVdHOgghxWXI6WHe1Z3Qc/6hb1O JFDeCS1Lwc6Q7nMrgOKGj6YqBYqGqEZHBzAmUUm7fskTwpm7Tp3KldBFVMwcT79RjBZS 4RvO0nzXvcQu/DHOswyTiCD3YlzJB9AYMStTPU/fPelx8pgVjQu900UgLq64ZWGaamKI hnHHs+hzMQv4essjmb7wbTFsmVx69V4dHKtrr/WO7NY/78Hqw/Ci9rlJ8k17JbkgcCmb AMHg== X-Gm-Message-State: AODbwcByDolNFpa3I9HLclpDRz5ufTRwB616+0LScIjK7LZ2EFPXMXkT OEZEzSIU1RmU/b+6PiInOEVAaGvCUX3NU50= X-Received: by 10.80.222.133 with SMTP id c5mr16770357edl.130.1496142641311; Tue, 30 May 2017 04:10:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.163.149 with HTTP; Tue, 30 May 2017 04:10:40 -0700 (PDT) From: Eduardo Lemos de Sa Date: Tue, 30 May 2017 08:10:40 -0300 Message-ID: Subject: Trying to boot from a zfs external disk To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 11:10:43 -0000 Dear I installed FreeBSD-10.3-RELEASE in a internal hard disk (named, that time, as ada0) in a zpool called zeeroot. Now, I move this hard disk to a case (so, it is a external drive now) and it is recognized as da0. When I tried to boot it, the process start normally but stopped at the moment to mount partitions. Later, I used to solve problems like this (in UFS/UFS2 file systems) booting in a live system (memory stick or CD) and editing /etc/fstab, renaming devices. But now, there is only in my /etc/fstab: # Device Mountpoint FStype Options Dump Pass# #/dev/ada0p2 none swap sw 0 0 md99 none swap sw,file=3D/usr/swap0,late 0 0 I read https://wiki.freebsd.org/ZFSQuickStartGuide and https://wiki.illumos.org/display/illumos/ZFS, further FreeBSD Handbook. In the two first, there is no mention about problems in boot stage using zfs. Further, I tried to find files under /etc/ called zfs.conf or zpool.conf or other mentions to ada0 (grep -r -i ada0 *): nothing. Thus, I do not how can solve this mount booting problem. Please, could you give some hint about? Thank you in advance Yours Eduardo --=20 Eduardo Lemos de Sa Professor Titular Dep. Quimica da Universidade Federal do Paran=C3=A1 fone: +55(41)3361-3300 fax: +55(41)3361-3186 From owner-freebsd-questions@freebsd.org Tue May 30 13:48:04 2017 Return-Path: Delivered-To: freebsd-questions@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 DA395B7D4A0 for ; Tue, 30 May 2017 13:48:04 +0000 (UTC) (envelope-from adam.gibbs@weboptimizes.com) Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::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 A866F25C7 for ; Tue, 30 May 2017 13:48:04 +0000 (UTC) (envelope-from adam.gibbs@weboptimizes.com) Received: by mail-oi0-x229.google.com with SMTP id b204so111579541oii.1 for ; Tue, 30 May 2017 06:48:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=weboptimizes.com; s=google; h=mime-version:sender:from:date:message-id:subject:to; bh=ui5C0FnfXg5HHTvY1z8ys814hCzx/3nW4vd6vp+mg/4=; b=B1vmFrU+YM+TJCqshydR4pTr/gO+BvS+12nXDeMxP2AIqQo+aQYozhwR4Cb5zEP7ry 2Quos1Ga63yxJIknT4wc9Vtl+qr/UpX3t1cpop8GHmvtSNzOUI+G9jJvxjU30xjc/zaO MDaxYzQ9oL8bDk0C+BYbBq+Wu+DFHEhjod5HE= 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:from:date:message-id:subject :to; bh=ui5C0FnfXg5HHTvY1z8ys814hCzx/3nW4vd6vp+mg/4=; b=EkEcmO4REbnLglo6EtLh8RDaa+ft1UNYaZMZ4TUhR7fE9KDEjpko/OftngBuXWNbwb 4Xuq5oCJE6Gw8QTFsM8A2IaVbEJcDhFAUE4hkdGZEvegKMt++Q+edlGpr6U2eqQbvKnm 95cklUkPgiSyVDPaJGnU5y9oymVtX4AU4fMlaUrXhekUiOhf99/Z9cqyPDypcSikY/5q PvfBmHfVE9vXTIYTtDjUpjyAuh2oDYFvSL9Oy3VZDuDscfqcgSeQBKt8+l2LWRW6zfBe vxyOsknYpEhCMPwUslu4CAYC/v6Sjd03ZmfJMYebOirYIel3vjtOdEQbmPKgQiXSGc07 9emw== X-Gm-Message-State: AODbwcCs6w20heZ0s9ivVwrA2pCBHFzRTLxy0tXFRLRHaETRxuNl1twT ur75Bd7GOl2hNe/V8j1SCR/40T53xshI X-Received: by 10.157.63.73 with SMTP id m67mr9402088otc.63.1496152083541; Tue, 30 May 2017 06:48:03 -0700 (PDT) Received: from 52669349336 named unknown by gmailapi.google.com with HTTPREST; Tue, 30 May 2017 06:48:02 -0700 MIME-Version: 1.0 Sender: Adam Gibbs From: Adam Gibbs Date: Tue, 30 May 2017 06:48:02 -0700 X-Google-Sender-Auth: FBYHb_oA5acHWLoHVb9qjJfJ5_o Message-ID: Subject: What has happened to your freebsd.org ? To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 13:48:04 -0000 *Hello freebsd.org Team, * *Get your website on Google=E2=80=99s Front Page search:* We would like to have a discussion with you regarding the web promotion strategy for your website. We wish to work out a proposal to strengthen the online presence of your website, via, a strategically planned web promotion campaign. In today=E2=80=99s online era, you should be focusing on the new revolutionary ways of generating traffic. *We were curious to know if you were aware that are a few issues bugging your website. Sorting out these will help you get the best returns out of your website.* 1. Your website seems to be attracting traffic, but this traffic is almost stagnant and limited, which affects potential sales as you move forward. 2. Your website doesn't feature in Google's first search page for some of the major keywords in your niche, which affects visibility. 3. Your website has been diagnosed with coding issues, which affects ranking. 4. Your back links profile is not efficient enough to help your search engine visibility. 5. Your website is currently not being properly promoted online, which is affecting your marketing strategy and goals. 6. Your presence in social media platform (Face book, Twitter, etc.) is minimal. This is depriving you of a huge market of prospective referral clients. We excel in running promotional online marketing campaign for websites. We have a host of ethical services and techniques, which you can utilize to improve your website's performance. We could send you more details regarding your present website status; we would be glad to share =E2=80=9C = *PRE SEO* *REPORT =E2=80=9D or =E2=80=9CWEBSITE ANALYSIS REPORT for FREE=E2=80=9D. K= indly revert back if you are interested, then we can send you more detail about package/action and which will improve your sales & website ranking too.* Let me know your thoughts and looking forward to work together. *Best Regards, * *Adam Gibbs** | Senior SEO Adviser* ------------------------------------------------------------ ------------------------------ *PS1:* If you are interested I will send more details on our =E2=80=9Ccorpo= rate identity=E2=80=9D, =E2=80=9Ccompany profile=E2=80=9D, =E2=80=9Cwhy you shou= ld choose us?=E2=80=9D, =E2=80=9CPrice list=E2=80=9D, *FREE SITE ANALYSIS REPORT or PRE SEO REPORT or WEBSITE ANALYSIS REPORT* =E2=80= =9Cmoney back guarantee=E2=80=9D. *PS2:* I found your site using Google search and after having a look over your website I recommend you to implement future technologies such as HTML 5 and Responsive Design to make your site more accessible in mobile phone, tablets, desktop etc. From owner-freebsd-questions@freebsd.org Tue May 30 14:21:23 2017 Return-Path: Delivered-To: freebsd-questions@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 4F882B7E15E for ; Tue, 30 May 2017 14:21:23 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay05.ispgateway.de (smtprelay05.ispgateway.de [80.67.31.97]) (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 1468E3B93 for ; Tue, 30 May 2017 14:21:22 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from [78.35.161.172] (helo=fabiankeil.de) by smtprelay05.ispgateway.de with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (Exim 4.84) (envelope-from ) id 1dFi00-0004Yg-36; Tue, 30 May 2017 16:19:52 +0200 Date: Tue, 30 May 2017 16:19:45 +0200 From: Fabian Keil To: Eduardo Lemos de Sa Cc: freebsd-questions@freebsd.org Subject: Re: Trying to boot from a zfs external disk Message-ID: <20170530161945.6ef8f3de@fabiankeil.de> In-Reply-To: References: Reply-To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/is7rX+0zDPZshmstIs41yXa"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 14:21:23 -0000 --Sig_/is7rX+0zDPZshmstIs41yXa Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Eduardo Lemos de Sa wrote: > I installed FreeBSD-10.3-RELEASE in a internal hard disk (named, that > time, as ada0) in a zpool called zeeroot. Now, I move this hard disk to > a case (so, it is a external drive now) and it is recognized as da0. > When I tried to boot it, the process start normally but stopped at the > moment to mount partitions. Later, I used to solve problems like this > (in UFS/UFS2 file systems) booting in a live system (memory stick or CD) > and editing /etc/fstab, renaming devices. But now, there is only in > my /etc/fstab: >=20 > # Device Mountpoint FStype Options Dump Pass# > #/dev/ada0p2 none swap sw 0 0 > md99 none swap sw,file=3D/usr/swap0,late 0 = 0 >=20 > I read https://wiki.freebsd.org/ZFSQuickStartGuide and > https://wiki.illumos.org/display/illumos/ZFS, further FreeBSD Handbook. >=20 > In the two first, there is no mention about problems in boot stage using > zfs. >=20 > Further, I tried to find files under /etc/ called zfs.conf or zpool.conf > or other mentions to ada0 (grep -r -i ada0 *): nothing. In case of ZFS the root pool is specified in /boot/loader.conf with a line like: vfs.root.mountfrom=3D"zfs:tank" ZFS is supposed to figure out the location of the disk(s) itself. > Thus, I do not how can solve this mount booting problem. Please, could > you give some hint about? This bug could explain why booting fails when you use an external disk: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208882 Fabian --Sig_/is7rX+0zDPZshmstIs41yXa Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTKUNd6H/m3+ByGULIFiohV/3dUnQUCWS1/gwAKCRAFiohV/3dU nSzvAKC4C8NQ5I4nDmWpAcQqIjmQChGDUwCgwi0Oyoo6R7B/DxTVcFy0ekEFUUo= =5KD0 -----END PGP SIGNATURE----- --Sig_/is7rX+0zDPZshmstIs41yXa-- From owner-freebsd-questions@freebsd.org Tue May 30 14:35:29 2017 Return-Path: Delivered-To: freebsd-questions@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 85E81B7E707 for ; Tue, 30 May 2017 14:35:29 +0000 (UTC) (envelope-from smartnew@n2s.mobi) Received: from zoniac5.nmsrv.com (zoniac5.nmsrv.com [204.187.13.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.nmsrv.com", Issuer "EssentialSSL CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6718C6459F for ; Tue, 30 May 2017 14:35:29 +0000 (UTC) (envelope-from smartnew@n2s.mobi) Received: (qmail 26531 invoked from network); 30 May 2017 14:32:59 -0000 Received: from ec2-54-197-242-119.compute-1.amazonaws.com (HELO ip-10-141-7-163.ec2.internal) (smartnew@n2s.mobi@54.197.242.119) by zoniac5.nmsrv.com with ESMTPA; 30 May 2017 14:32:59 -0000 Date: Tue, 30 May 2017 14:32:58 +0000 (UTC) From: Avinash Bakka Reply-To: avi@smtworks.com To: freebsd-questions@freebsd.org Message-ID: <1496154778413.9966657688256303.avi@smtworks.com> Subject: My candidates won't stay long in market!!!! Hurry up!!! Importance: Normal X-Mailer: Zoniac Mailer System X-Zoniac-TrackerID: 0365e3b17938609949993632910d32c0ebf32571e520554e25b8f030f59d4b389a94c5d365a57a8806e60e04cec1f03586ff7319814be833 MIME-Version: 1.0 Content-Type: text/plain; charset="ANSI_X3.4-1968" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 14:35:29 -0000 From owner-freebsd-questions@freebsd.org Tue May 30 16:49:51 2017 Return-Path: Delivered-To: freebsd-questions@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 289A6B87E06 for ; Tue, 30 May 2017 16:49:51 +0000 (UTC) (envelope-from eduardo.lemosdesa@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 AA89A6F145 for ; Tue, 30 May 2017 16:49:50 +0000 (UTC) (envelope-from eduardo.lemosdesa@gmail.com) Received: by mail-wm0-x22e.google.com with SMTP id 7so96891959wmo.1 for ; Tue, 30 May 2017 09:49:50 -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; bh=W65uoKHM6Dn0m/zjauD7WClE8CyqsZ/hXN4IZqNovYo=; b=g9Z3e3HnwmudKIq0TMNzV2LBTV118NXV/svRoqer4qNMhDpdC/iB3++Iu9dVJS41B0 tGmyPTke6X4Qb2hXkaatcY7ncDZZjdEXrxqOvqkKcvRDW0OpniiO7gwK+/76dB1wBPwl AAlLWzbtkK3z9To/8lkT62ucIS+oLyVwK+LWat+dt8/NRGotIRGBhDsBI6TFZzfV1oHA lwL18S6RRRXenVQODjpKMBiniPkZM3f8/je2swpljrswpNDi8QHrWfOr5pPWW7WKvaAq 1H6wj7qj8CVTOMPsmnjTUoGDmGCgMvT1OFUfCSJgf6FhFqYXZnaw1Y+3FWPvwyP7yFd9 8LGg== 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; bh=W65uoKHM6Dn0m/zjauD7WClE8CyqsZ/hXN4IZqNovYo=; b=dHku+R8uSQMOtd8KVgwcy2Fm1Q4Cd5SZwprQZ6Fg9XwUg5lILP79Zu5VLVYtSqxFkP +dRChJTbIwJntz9Rr/7DHSAD20u/yJ/FY5bDIC8oORSqli38++l5XYL7Mk/RRG+qkCOZ ThYdFCbzsHGPQ+9zmipYirTIFjT7Ot6mVW754iDaeK2lo9U+mgUdUa5rbfkJ7BkRX5KQ YOvw/EhCW74niwu1jnlBBFnUMJidZz+Z3OeOTVp9ihj3gEL1G3Hk3mNbq0pFg4wjjkdq 5JZEa1WOj2HwWE3KZ13GJg38Bj8bGkeQ151vX4R+H2tdJsTMPjdRLwC70w+vZupgrO8C 2lyw== X-Gm-Message-State: AODbwcD9Mb8FAET+MP0tkWN2KHfs+0fHByDThszMaz44mBE4fiYJpPWu wE/ZR91DK7CvXMGpywOK2t2TkeaVuNiIq+Y= X-Received: by 10.80.222.133 with SMTP id c5mr17805350edl.130.1496162988925; Tue, 30 May 2017 09:49:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.163.149 with HTTP; Tue, 30 May 2017 09:49:48 -0700 (PDT) In-Reply-To: <20170530161945.6ef8f3de@fabiankeil.de> References: <20170530161945.6ef8f3de@fabiankeil.de> From: Eduardo Lemos de Sa Date: Tue, 30 May 2017 13:49:48 -0300 Message-ID: Subject: Re: Trying to boot from a zfs external disk To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 16:49:51 -0000 Dear Fabien On Tue, May 30, 2017 at 11:19 AM, Fabian Keil wrote: > Eduardo Lemos de Sa wrote: > > > I installed FreeBSD-10.3-RELEASE in a internal hard disk (named, that > > time, as ada0) in a zpool called zeeroot. Now, I move this hard disk to > > a case (so, it is a external drive now) and it is recognized as da0. > > When I tried to boot it, the process start normally but stopped at the > > moment to mount partitions. Later, I used to solve problems like this > > (in UFS/UFS2 file systems) booting in a live system (memory stick or CD= ) > > and editing /etc/fstab, renaming devices. But now, there is only in > > my /etc/fstab: > > > > # Device Mountpoint FStype Options Dump Pass# > > #/dev/ada0p2 none swap sw 0 0 > > md99 none swap sw,file=3D/usr/swap0,late 0 = 0 > > > > I read https://wiki.freebsd.org/ZFSQuickStartGuide and > > https://wiki.illumos.org/display/illumos/ZFS, further FreeBSD Handbook. > > > > In the two first, there is no mention about problems in boot stage usin= g > > zfs. > > > > Further, I tried to find files under /etc/ called zfs.conf or zpool.con= f > > or other mentions to ada0 (grep -r -i ada0 *): nothing. > > In case of ZFS the root pool is specified in /boot/loader.conf > with a line like: > vfs.root.mountfrom=3D"zfs:tank" > > ZFS is supposed to figure out the location of the disk(s) itself. > > > Thus, I do not how can solve this mount booting problem. Please, could > > you give some hint about? > > This bug could explain why booting fails when you use an external disk: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208882 > > Fabian > Thank you very much for share your expertise. Please, forgive me to ask one more thing: I searched (using grep) where a "mountfrom" is located or nomitade in a another 10.3-RELEASE. The result was: defaults/loader.conf:#vfs.root.mountfrom=3D"" # Specify root partiti= on in a way the Binary file kernel/kernel matches Binary file kernel.old/kernel matches Binary file loader matches Binary file loader.efi matches Binary file loader.old matches menu-commands.4th: s" set menu_caption[1]=3D${bemenu_current}${vfs.root.mountfrom}" evaluate menu-commands.4th: s" set ansi_caption[1]=3D${beansi_current}${vfs.root.mountfrom}" evaluate menu-commands.4th: dup s" set vfs.root.mountfrom=3D${bootenv_root[E]}" 3= 8 +c! evaluate menu-commands.4th: s" set currdev=3D${vfs.root.mountfrom}:" evaluate Binary file pxeboot matches Binary file userboot.so matches Binary file zfsloader matches Binary file zfsloader.old matches In this machine, zroot (the name of zpool) is mounted in /dev/ada0 (p3, mainly), but this information is not avaliable in ASCII files (apparently, it is in one or more binary files (zfsloader, as example). Thus, how to booting system "knows" where root shoud be mount? I will try to mount this hard disk, edit loader.conf and explicitly specify vfs.root.mountfrom=3D"zfs:zeeroot" Thank you again. My best regards Eduardo --=20 Eduardo Lemos de Sa Professor Titular Dep. Quimica da Universidade Federal do Paran=C3=A1 fone: +55(41)3361-3300 fax: +55(41)3361-3186 From owner-freebsd-questions@freebsd.org Wed May 31 01:06:19 2017 Return-Path: Delivered-To: freebsd-questions@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 4BF1BBF25E3 for ; Wed, 31 May 2017 01:06:19 +0000 (UTC) (envelope-from asv@inhio.net) Received: from cz-prg-mx-01.inhio.eu (mail.inhio.eu [178.238.36.226]) by mx1.freebsd.org (Postfix) with ESMTP id 18C6982215 for ; Wed, 31 May 2017 01:06:17 +0000 (UTC) (envelope-from asv@inhio.net) Received: from [192.168.0.19] (unknown [179.210.101.12]) by cz-prg-mx-01.inhio.eu (Postfix) with ESMTPSA id 957341ADFE for ; Wed, 31 May 2017 00:57:41 +0000 (UTC) Message-ID: <1496192259.6870.12.camel@inhio.net> Subject: FreeBSD 11.0 RELEASE - FREEZE!! From: ASV To: freebsd-questions@freebsd.org Date: Tue, 30 May 2017 21:57:39 -0300 Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 May 2017 01:06:19 -0000 Hi everyone, I've been using FreeBSD on my Thinkpad T430 for about 3 years upgrading from release to release encountering minor issues from time to time. Since I've upgraded to FreeBSD 11 the OS freezes every time I: - close the lid - use any function buttons Cannot be recovered in any way, doesn't respond to anything and, obviously I cannot access to the terminal (no vty access). I couldn't check if I can actually login via ssh from another box as I cannot do this test at the moment nonetheless I doubt that would be possible. My current version is 11.0-RELEASE-p9. The only log I can see after restarting is pasted below (in case of closing lid). I'm wondering if anybody is experiencing the same. It is very frustrating. Tnx. May 30 20:50:51 localhost dbus[1114]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper) May 30 20:50:51 localhost dbus[1114]: [system] Successfully activated service 'org.freedesktop.UPower' May 30 20:50:51 localhost dbus[1114]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.11" (uid=1001 pid=2449 comm="/usr/local/bin/xfce4-session ") interface="org.freedesktop.ConsoleKit.Manager"member="CanSuspend" error name="(unset)" requested_reply="0"destination=":1.1" (uid=0 pid=1231 comm="/usr/local/sbin/console-kit-daemon --no-daemon ") May 30 20:50:51 localhost dbus[1114]: [system] Rejected send message, 2 matched rules; type="method_call",sender=":1.13" (uid=1001 pid=2482 comm="xfce4-power-manager --restart --sm-client-id 2d98a")interface="org.freedesktop.ConsoleKit.Manager" member="CanSuspend" error name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=1231 comm="/usr/local/sbin/console-kit- daemon --no-daemon ") May 30 20:50:51 localhost dbus[1114]: [system] Rejected send message, 2 matched rules; type="method_call",sender=":1.13" (uid=1001 pid=2482 comm="xfce4-power-manager --restart --sm-client-id 2d98a")interface="org.freedesktop.ConsoleKit.Manager" member="CanHibernate" error name="(unset)" requested_reply="0"destination=":1.1" (uid=0 pid=1231 comm="/usr/local/sbin/console-kit-daemon --no-daemon ") May 30 20:50:51 localhost dbus[1114]: [system] Rejected send message, 2 matched rules; type="method_call",sender=":1.11" (uid=1001 pid=2449 comm="/usr/local/bin/xfce4-session ")interface="org.freedesktop.ConsoleKit.Manager" member="CanHibernate" error name="(unset)" requested_reply="0"destination=":1.1" (uid=0 pid=1231 comm="/usr/local/sbin/console-kit-daemon --no-daemon ") May 30 20:50:52 localhost dbus[1114]: [system] Rejected send message, 2 matched rules; type="method_call",sender=":1.11" (uid=1001 pid=2449 comm="/usr/local/bin/xfce4-session ")interface="org.freedesktop.ConsoleKit.Manager" member="CanSuspend" error name="(unset)" requested_reply="0"destination=":1.1" (uid=0 pid=1231 comm="/usr/local/sbin/console-kit-daemon --no-daemon ") May 30 20:50:52 localhost dbus[1114]: [system] Rejected send message, 2 matched rules; type="method_call",sender=":1.11" (uid=1001 pid=2449 comm="/usr/local/bin/xfce4-session ")interface="org.freedesktop.ConsoleKit.Manager" member="CanHibernate" error name="(unset)" requested_reply="0"destination=":1.1" (uid=0 pid=1231 comm="/usr/local/sbin/console-kit-daemon --no-daemon ") From owner-freebsd-questions@freebsd.org Wed May 31 02:27:49 2017 Return-Path: Delivered-To: freebsd-questions@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 EE93ABF352B for ; Wed, 31 May 2017 02:27:49 +0000 (UTC) (envelope-from 0101015c5c5498c3-84377171-9e30-40da-a58b-1c4af755f602-000000@us-west-2.amazonses.com) Received: from a27-35.smtp-out.us-west-2.amazonses.com (a27-35.smtp-out.us-west-2.amazonses.com [54.240.27.35]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C265183E81 for ; Wed, 31 May 2017 02:27:49 +0000 (UTC) (envelope-from 0101015c5c5498c3-84377171-9e30-40da-a58b-1c4af755f602-000000@us-west-2.amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=stdm37fqbypyvw6iolbo3nkyd73es3w7; d=vmeta.jp; t=1496197667; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:Content-Type:In-Reply-To; bh=OGZKEOpGu9g6egw3CU0aXB4Tr0g3WTZoR08CawBVreA=; b=FAJeTCtItXDX5H3C+ul8ZDy6VBru6n+zJ1j49yUbzwoE/uHMKdCsHyrA9pScLqmE F6GA4483IFRewe7ng3ybvsuAYVK5tNjg0THfDzM74tl3kYIXLGCMhfJp6KsBRKfBcB0 sqYSkhSRw/NbT13LxVPuAqk9KdqQB2ZZ/7/3yUaQ= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=hsbnp7p3ensaochzwyq5wwmceodymuwv; d=amazonses.com; t=1496197667; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:Content-Type:In-Reply-To:Feedback-ID; bh=OGZKEOpGu9g6egw3CU0aXB4Tr0g3WTZoR08CawBVreA=; b=SGrxrH6oIZ8jBdUW6KEd6hhENTH5v7KiaL5Ni7bgzB9+G98WPdwXdySAitYDVaSM QfETp+eLkcdzsnZWs+Xu24q/lgcSlI/aHqaG+D18XFbkgEYjgWDoSok4kSBhBBJPXCn kWAPl0nH6UtDtriWsE7UreH2PsfqPxV9mzPX9W8U= Date: Wed, 31 May 2017 02:27:47 +0000 From: meta To: "Chad J. Milios" Cc: freebsd-questions Subject: Re: Is it possible to use more than 1 CPUs during pkg create? Message-ID: <0101015c5c5498c3-84377171-9e30-40da-a58b-1c4af755f602-000000@us-west-2.amazonses.com> References: <0101015c58b3dc58-1b936a1a-8412-472b-a257-c436a40e89f2-000000@us-west-2.amazonses.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 10.3-RELEASE-p18 amd64 User-Agent: Mutt/1.8.2 (2017-04-18) X-SES-Outgoing: 2017.05.31-54.240.27.35 Feedback-ID: 1.us-west-2.ngRt4x2U/cWqug8pbfjwMxB6pcDw1fmN73bGmMLYyRI=:AmazonSES X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 May 2017 02:27:50 -0000 On Tue, May 30, 2017 at 06:55:02AM -0400, Chad J. Milios wrote: > Threading forfeits a bit of xz$B!G(Bs great compression ratio. An xz file created with -T greater than 1 will necessarily be some amount larger. Operating with just one thread achieves the maximal compression ratio. (The multiple compression threads fail to share the dictionaries they are currently building.) > Yes, compressing with one thread achieves the best ratio. However, it is really a little bit. I created a package of x11-fonts as example of a big package. Its size is 813230580 bytes. Then I recompressed the package with -T0 option, the archive is just 1% larger. # make -C /usr/ports/x11-fonts/noto package $ ls noto* -rw-r--r-- 1 meta wheel 813230580 May 30 21:30 noto-1.0.5_1.txz $ zcat noto-1.0.5_txz | xz -T0 -c > noto-1.0.5_1.txz.T0 $ ls noto* -rw-r--r-- 1 meta wheel 813230580 May 30 21:30 noto-1.0.5_1.txz -rw-r--r-- 1 meta wheel 821921768 May 30 21:45 noto-1.0.5_1.txz.T0 I understand the merit of compressing package in single thread distributed by pkg.freebsd.org. However, I'd rather save time than storage or network bandwidth. I want to make `make package` faster on my host. The build can use multi cores but pkg create process uses only one so package stage is the bottle neck. > When you are transferring GBytes to yourself once, use -T0. When you are compressing something one time that hundreds or thousands of people will potentially download and/or store, use -T1 (the default). Do you mean I can use -T0 during pkg create? AFAIK it is not possible but if possible, how? -- `whois vmeta.jp | nkf -w` meta From owner-freebsd-questions@freebsd.org Wed May 31 02:40:17 2017 Return-Path: Delivered-To: freebsd-questions@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 E5A81BF3779 for ; Wed, 31 May 2017 02:40:17 +0000 (UTC) (envelope-from 0101015c5c6007b6-0633a1f3-b800-431f-a784-e931afd64ba3-000000@us-west-2.amazonses.com) Received: from a27-35.smtp-out.us-west-2.amazonses.com (a27-35.smtp-out.us-west-2.amazonses.com [54.240.27.35]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C464084207 for ; Wed, 31 May 2017 02:40:17 +0000 (UTC) (envelope-from 0101015c5c6007b6-0633a1f3-b800-431f-a784-e931afd64ba3-000000@us-west-2.amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=stdm37fqbypyvw6iolbo3nkyd73es3w7; d=vmeta.jp; t=1496198416; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:Content-Type:In-Reply-To; bh=EDuvaymqRjQELMnLY0o0uwbVF1co8ROzlIXD0Ejt2KU=; b=SfnJMVN6cyQ9DFR+UWtv7IJZhZYnbKGxrcUud56iX+lXK0CcHXfdnIvDlDWOzx8H zBem/ny1hKpWSDWVPYTVdj7o8pDzhuqrBn2wyz4yC/rVT5bMXOashU2Jswy0IhocjyW 3JzjRf+PV8InPl15l9CIrglW5THRsOr25pT28fiw= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=hsbnp7p3ensaochzwyq5wwmceodymuwv; d=amazonses.com; t=1496198416; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:Content-Type:In-Reply-To:Feedback-ID; bh=EDuvaymqRjQELMnLY0o0uwbVF1co8ROzlIXD0Ejt2KU=; b=a5F+jeuLVUN5YbdNgTllfrKGUKhSfc0Fny+WxrRj/ycGKVEPZBWr5rR4DuCksDXL +aoQJtUP+J0gModp8BeOVfUTCZjAjHxpxB/xQ8f8G05mQ1Ojxt8YYZ3Gum9mVfUSxx1 GIgiejU6yhpj3JvpXvUJ8ojMegywn1UKr4sztoAw= Date: Wed, 31 May 2017 02:40:16 +0000 From: meta To: Jim Ohlstein Cc: freebsd-questions@freebsd.org Subject: Re: Is it possible to use more than 1 CPUs during pkg create? Message-ID: <0101015c5c6007b6-0633a1f3-b800-431f-a784-e931afd64ba3-000000@us-west-2.amazonses.com> References: <0101015c58b3dc58-1b936a1a-8412-472b-a257-c436a40e89f2-000000@us-west-2.amazonses.com> <1496141532.1095.41.camel@mailman-hosting.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Disposition: inline In-Reply-To: <1496141532.1095.41.camel@mailman-hosting.com> X-Operating-System: FreeBSD 10.3-RELEASE-p18 amd64 User-Agent: Mutt/1.8.2 (2017-04-18) X-SES-Outgoing: 2017.05.31-54.240.27.35 Feedback-ID: 1.us-west-2.ngRt4x2U/cWqug8pbfjwMxB6pcDw1fmN73bGmMLYyRI=:AmazonSES X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 May 2017 02:40:18 -0000 On Tue, May 30, 2017 at 06:52:12AM -0400, Jim Ohlstein wrote: > On Tue, 2017-05-30 at 09:33 +0000, Koichiro IWAO wrote: > > Hi, > > > > is it possible to use more than 1 CPU cores during xz compression > > done in pkg create? I know XZ Utils in base system can use more > > than 1 CPUs if -T option given. I guess pkg internally calls APIs > > of XZ Utils. I think it is potentially possible. > > > > Or is it restricted to use only 1 CPU core for some reasons? > > For those using poudriere or synth this might be a disadvantage with > multiple parallel builds going on. That said, I imagine the code could > be patched to allow it. Yes, using more than 1 CPU cores might be both an advantage and a disadvantage. I think allow multithread and keep default to only 1 thread will be acceptable for everyone. -- `whois vmeta.jp | nkf -w` meta From owner-freebsd-questions@freebsd.org Thu Jun 1 02:23:59 2017 Return-Path: Delivered-To: freebsd-questions@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 19C2EBF0E79 for ; Thu, 1 Jun 2017 02:23:59 +0000 (UTC) (envelope-from parker.louis@weboptimizes.com) Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::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 D76FC75D71 for ; Thu, 1 Jun 2017 02:23:58 +0000 (UTC) (envelope-from parker.louis@weboptimizes.com) Received: by mail-qt0-x235.google.com with SMTP id f55so26557682qta.3 for ; Wed, 31 May 2017 19:23:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=weboptimizes.com; s=google; h=mime-version:sender:from:date:message-id:subject:to; bh=0cSEalpVp2sVRzncOUylJwP6xw1wm0SHB587dBodEjw=; b=COPxuF67w81Igs6zEox1eoCbpHMk6wpKcJy1aK0cruDy55YfoJuhYM1UalBi5nYWEp uNk4M/ewUY31U6JAkVXBSUrzhZpXVUDMAuz7RDLM34c1o/dSK5wEY3agkUv4uBUVGP/2 eDBkDweBIsk/o1GU4Wts97I2nzaWb9EhcIpNk= 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:from:date:message-id:subject :to; bh=0cSEalpVp2sVRzncOUylJwP6xw1wm0SHB587dBodEjw=; b=X5heyg/b06gFyeXAiFrNfYw4TydsZ6iBCR8pS/U+YjwDPLt24v92ejL/Zyb420eMnU GMARR5aouo7H0s6SD0o2ZMHLNkwmPJctOFcZXtje0MVcvEreZX2EU/LV0MPReu81qmME 8BXmejCjwZJiauDj+bZdHnE4qWRjK/c0vnIbI5LHhKTYIwp2hUuK3s6psxAkbnTha9C2 FKTRiC8N6FwSN1ZdoGHnSFd5qCVshYA87xYET8auS9vP8uMFVxIIYfGLQ89BNhrSUoXT eg0HPthhp1zsHtamuZDUAWTxzgZeaUw0AADmSQih/e8I2w+Cx5CExrez1eAl9DepiRFd jZGA== X-Gm-Message-State: AODbwcBzb1v1ygAx5Kp7LuNfuOPskYScdybviUTjnBUQrNeFzO6C9tGK miDvHBIZKy7GvrBrTWiIiVywnAKS58Hg9Ew= X-Received: by 10.200.37.129 with SMTP id e1mr32684002qte.21.1496283837672; Wed, 31 May 2017 19:23:57 -0700 (PDT) Received: from 52669349336 named unknown by gmailapi.google.com with HTTPREST; Wed, 31 May 2017 22:23:57 -0400 MIME-Version: 1.0 Sender: Louis Parker From: Louis Parker Date: Wed, 31 May 2017 22:23:57 -0400 X-Google-Sender-Auth: 8jJuksP_vORpWsdnDNBAajzuGcc Message-ID: Subject: =?UTF-8?Q?It=E2=80=99s_time_to_make_a_decision_about_this?= To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 02:23:59 -0000 Hello freebsd.org Team, *Get your website on Google=E2=80=99s Front Page search:*We would like to h= ave a discussion with you regarding the web promotion strategy for your website. We wish to work out a proposal to strengthen the online presence of your website, via, a strategically planned web promotion campaign. In today=E2= =80=99s online era, you should be focusing on the new revolutionary ways of generating traffic. We were curious to know if you were aware that are a few issues bugging your website. Sorting out these will help you get the best returns out of your website. Your website seems to be attracting traffic, but this traffic is almost stagnant and limited, which affects potential sales as you move forward. Your website doesn't feature in Google's first search page for some of the major keywords in your niche, which affects visibility. Your website has been diagnosed with coding issues, which affects ranking. Your back links profile is not efficient enough to help your search engine visibility. Your website is currently not being properly promoted online, which is affecting your marketing strategy and goals Your presence in social media platform (*Facebook, Twitter, etc.*) is minimal. This is depriving you of a huge market of prospective referral clients. We excel in running promotional online marketing campaign for websites. We have a host of ethical services and techniques, which you can utilize to improve your website's performance. We could send you more details regarding your present website status; we would be glad to share =E2=80=9C*= PRE SEO REPORT=E2=80=9D* or =E2=80=9C*WEBSITE ANALYSIS REPORT* for *FREE=E2=80=9D*. *Kindly revert back if you are interested, then we can send you more detail about package which will improve your sales & website ranking too.*Hope to get early response. Best Regards, *Louis Parker | Senior Sales Advisor*______________________________ ___________________________________________ *PS1:* Please answer to our email with *=E2=80=9CInterested*=E2=80=9D or *= =E2=80=9CNot Interested*=E2=80=9D so that we will know the status of your inquiry and act accordingly. If you are interested then I will send more details on our *=E2=80=9Ccorporate ide= ntity=E2=80=9D, =E2=80=9Ccompany profile=E2=80=9D, =E2=80=9Cwhy you should choose us?=E2=80= =9D, =E2=80=9CPrice list=E2=80=9D, =E2=80=9Cmoney back guarantee=E2=80=9D*. *PS2:* I found your site using Google search and after having a look over your website I recommend you to implement future technologies such as HTML5 and Responsive Design to make your site more accessible in mobile phone, tablets, desktop etc. From owner-freebsd-questions@freebsd.org Thu Jun 1 05:10:39 2017 Return-Path: Delivered-To: freebsd-questions@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 72200AF89A8 for ; Thu, 1 Jun 2017 05:10:39 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (mail.geeks.org [IPv6:2001:4980:3333:1::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 5366284C8A for ; Thu, 1 Jun 2017 05:10:39 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (localhost [127.0.0.1]) by after-clamsmtpd.geeks.org (Postfix) with ESMTP id 5A34F11022A for ; Thu, 1 Jun 2017 00:10:31 -0500 (CDT) Received: by mail.geeks.org (Postfix, from userid 1003) id 34561110229; Thu, 1 Jun 2017 00:10:31 -0500 (CDT) Date: Thu, 1 Jun 2017 00:10:30 -0500 From: Doug McIntyre To: freebsd-questions@freebsd.org Subject: Re: Advice on kernel panics Message-ID: <20170601051030.GA39861@geeks.org> References: <20170529092043.GA89682@erix.ericsson.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170529092043.GA89682@erix.ericsson.se> User-Agent: Mutt/1.8.2 (2017-04-18) X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 05:10:39 -0000 On Mon, May 29, 2017 at 11:20:43AM +0200, Raimo Niskanen wrote: > I have a server that panics about every 3 days and need some advice on how > to handle that. I'd expect it is some sort of hardware failure, as I would expect kernel panics more on the order of once a decade with FreeBSD. Ie. I've seen one or two on my hundred or so servers, but its pretty rare. Check and recheck your hardware items. Runup memtest86+. Check your drive hardware, turn on SMART checking. From owner-freebsd-questions@freebsd.org Thu Jun 1 05:11:09 2017 Return-Path: Delivered-To: freebsd-questions@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 A0A8AAF8D28 for ; Thu, 1 Jun 2017 05:11:09 +0000 (UTC) (envelope-from chelsea@mybannerbillboard.com) Received: from a2nlsmtp01-05.prod.iad2.secureserver.net (a2nlsmtp01-05.prod.iad2.secureserver.net [198.71.225.49]) (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 4E57F884 for ; Thu, 1 Jun 2017 05:11:09 +0000 (UTC) (envelope-from chelsea@mybannerbillboard.com) Received: from a2plcpnl0854.prod.iad2.secureserver.net ([107.180.109.53]) by : HOSTING RELAY : with SMTP id GIN4dXyVmCQzGGIN4d3wzp; Wed, 31 May 2017 22:10:06 -0700 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mybannerbillboard.com; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:Subject:Reply-To:From:To:Date:Sender:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=WZAdUOgz/d2tqgwbudw72cSiGSnPMwd2TExMxJhUzOE=; b=04Y0xQX+7iJXKHHYceG0/Eeg2c jbw0vikNiKpZz1Zq10BDfOJVlJ8L+irc7DuJJU7k7vkRbvW/BHcRJSSq+zNtC3CvxJCjA9C+zDvRl uc9b+xnFHbhg0+Qir1IdExiaWC3eQSTifVasiek1NzuZwPocLtpzDzRxBI8TM663tR72qZARguKUH 3MrDlNdAL5v5Fzxdap1C8rIhLG75hGU1jlY15NbPR7vNS0Q5/8j8Q8RPucbDhig6ZazN4A0JUeDi6 v6JFXLXNrFuv4QnVZsCTsHUmV4YhDce0Awu5sJOwECzivkJ55hqW5SSkyFU6w1Q46wasyxald5Il8 XSBqZQXw==; Received: from [127.0.0.1] (port=51807 helo=mybannerbillboard.com) by a2plcpnl0854.prod.iad2.secureserver.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.88) (envelope-from ) id 1dGIN4-003tYd-6M for freebsd-questions@freebsd.org; Wed, 31 May 2017 22:10:06 -0700 Date: Thu, 1 Jun 2017 05:10:01 +0000 To: "freebsd-questions@freebsd.org" From: "chelsea@mybannerbillboard.com" Reply-To: "chelsea@mybannerbillboard.com" Subject: Best practice of high rank and much profit for your web page Message-ID: <22ba35f765cd82cd4f3b76453ab8dc1f@mybannerbillboard.com> X-Mailer: PHPMailer 5.2.22 (https://github.com/PHPMailer/PHPMailer) MIME-Version: 1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a2plcpnl0854.prod.iad2.secureserver.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - mybannerbillboard.com X-Get-Message-Sender-Via: a2plcpnl0854.prod.iad2.secureserver.net: authenticated_id: chelsea@mybannerbillboard.com X-Authenticated-Sender: a2plcpnl0854.prod.iad2.secureserver.net: chelsea@mybannerbillboard.com X-Source: X-Source-Args: X-Source-Dir: X-CMAE-Envelope: MS4wfMhzYUi9HG+olcZipG91vyZ5ca53XoCLdGYR3/ftIIREyC/mD8fDvQTWscRbeNcG9yVRmFkvruFn9/8/ReBd/Drmr5XzV/AZwT3yaAgUGbiyhM0lTbbL ZQYemHJMLtwhFKL5503Hny0uSzA/+KVufrrRA9+hmL8nOuE11KdvZWBkJwaJi6MPA2D31L2zjZ1ticVgawrAhA62s4Ue5HjVh4zdZqFUOZ0uZq+br1M1D/bZ Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 05:11:09 -0000 Hi Freebsd-questions! My Name is Chelsea. To have a big impact on the results of your ad campaigns with digital marketing models is reachable but is very crucial. Managing even the simplest PPC campaign takes time and effort. To have your ad appear higher on a page will take many efforts and energy. You don't need to be a marketing genius to realize that it is going to be extremely hard to rank your website keywords for the long-term period. If you want to get your website on top of search engine results without paying higher price than your competitors per each click to your ads, then we have right technology for you. We can place your website on top portion of search engine results during whole year with your keywords without paying for each click and you will have exclusive rights on your keywords after you select them and lock them for whole year! You can do online demo in 3 easy steps: - Go to our website and click on the DEMO link. - Put in your website freebsd org address and your keyword. - Click VIEW ONLINE DEMO and see result. With Anticipation, Chelsea Keith From owner-freebsd-questions@freebsd.org Thu Jun 1 08:32:09 2017 Return-Path: Delivered-To: freebsd-questions@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 AAF5ABF1ED3 for ; Thu, 1 Jun 2017 08:32:09 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 3A0A06EDE4 for ; Thu, 1 Jun 2017 08:32:08 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) X-AuditID: c1b4fb2d-5a49e9a000000d37-d4-592fd105b20d Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 53.79.03383.501DF295; Thu, 1 Jun 2017 10:32:05 +0200 (CEST) Received: from duper.otp.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.47) with Microsoft SMTP Server id 14.3.339.0; Thu, 1 Jun 2017 10:27:51 +0200 Received: from duper.otp.ericsson.se (localhost [127.0.0.1]) by duper.otp.ericsson.se (8.15.2/8.15.2) with ESMTP id v518Rnm6080710 for ; Thu, 1 Jun 2017 10:27:49 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) Received: (from raimo@localhost) by duper.otp.ericsson.se (8.15.2/8.15.2/Submit) id v518RnZJ080709 for freebsd-questions@freebsd.org; Thu, 1 Jun 2017 10:27:49 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) X-Authentication-Warning: duper.otp.ericsson.se: raimo set sender to raimo+freebsd@erix.ericsson.se using -f Date: Thu, 1 Jun 2017 10:27:49 +0200 From: Raimo Niskanen To: Subject: Re: Advice on kernel panics Message-ID: <20170601082749.GA80543@erix.ericsson.se> Mail-Followup-To: freebsd-questions@freebsd.org References: <20170529092043.GA89682@erix.ericsson.se> <20170601051030.GA39861@geeks.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20170601051030.GA39861@geeks.org> User-Agent: Mutt/1.7.2 (2016-11-26) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLLMWRmVeSWpSXmKPExsUyM2K7ri7rRf1Ig+OPxCxeft3E4sDoMePT fJYAxigum5TUnMyy1CJ9uwSujCcf2tgKJnBUHN1whbWBcQlbFyMnh4SAicTWuUsYuxi5OIQE jjBKnPy8kw3C2cAosfr1BXYIp41J4tPKKywgLUICTxgljm/kgmjPkXj76SgTiM0ioCKx98kh MJtNwFSi8ecZVhBbREBZ4t+1i8wgtjBQzYqt9xhBbF6gmg83jzJD2PoSH1e8YoWYHyWx8fx7 doi4oMTJmU/A9jIL6Egs2P0J6DoOIFtaYvk/DpAwJ1Br19yJTCBhUZBVX6GmaEtMeHOAdQKj 8Cwkg2YhGTQLYdACRuZVjKLFqcXFuelGxnqpRZnJxcX5eXp5qSWbGIGBfHDLb90djKtfOx5i FOBgVOLhFdyvHynEmlhWXJl7iFGCg1lJhJevEijEm5JYWZValB9fVJqTWnyIUZqDRUmc12Hf hQghgfTEktTs1NSC1CKYLBMHp1QDoxzHQzY9gZWtsSmq8YoPn8Ta3XXgDry4/WZNxqSK47fE K58US19PuLK1n9H0+g3nW63PPZfvO8O88cXhzCyfgOUba4NauM65fi7v1158yWC95bQFajkT dGXl/zDLJO0yZ2deznPK+OShWoYSpyu3l7GteajzcgPrk2t3Jrp/exjadV5BaEKbmhJLcUai oRZzUXEiAGYvSsVgAgAA X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 08:32:09 -0000 On Thu, Jun 01, 2017 at 12:10:30AM -0500, Doug McIntyre wrote: > On Mon, May 29, 2017 at 11:20:43AM +0200, Raimo Niskanen wrote: > > I have a server that panics about every 3 days and need some advice on how > > to handle that. > > I'd expect it is some sort of hardware failure, as I would expect > kernel panics more on the order of once a decade with FreeBSD. Ie. > I've seen one or two on my hundred or so servers, but its pretty rare. > > Check and recheck your hardware items. I have removed one of four memory capsules - panicked again. Will rotate through all of them... > > Runup memtest86+. Check your drive hardware, turn on SMART checking. I have run memtest86+ over night - no errors found. I have installed smartmontools - no errors found, short and long self tests on both disks run fine. zpool scrub repaired 0 errors and has no known data errors. Any further hints on how to "Check your drive hardware"? Thank you for your advice. -- / Raimo Niskanen, Erlang/OTP, Ericsson AB From owner-freebsd-questions@freebsd.org Thu Jun 1 10:05:17 2017 Return-Path: Delivered-To: freebsd-questions@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 98837AF8365 for ; Thu, 1 Jun 2017 10:05:17 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp209.alice.it (smtp209.alice.it [82.57.200.105]) by mx1.freebsd.org (Postfix) with ESMTP id 2FC6F7396B for ; Thu, 1 Jun 2017 10:05:16 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (79.26.54.44) by smtp209.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 58D1259E37A64AF7 for freebsd-questions@freebsd.org; Thu, 1 Jun 2017 11:58:48 +0200 Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) by soth.ventu (8.15.2/8.15.2) with ESMTP id v519wmPp082568 for ; Thu, 1 Jun 2017 11:58:48 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu Subject: Re: Advice on kernel panics To: freebsd-questions@freebsd.org References: <20170529092043.GA89682@erix.ericsson.se> From: Andrea Venturoli Message-ID: Date: Thu, 1 Jun 2017 11:58:48 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170529092043.GA89682@erix.ericsson.se> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 10:05:17 -0000 On 05/29/17 11:20, Raimo Niskanen wrote: > Hello list. > > I have a server that panics about every 3 days and need some advice on how > to handle that. As Doug suggested, it's probably an hardware fault. However, I've many times seen boxes crash every day or two when an UFS+SU filesystem gets corrupted. Background fsck won't detect this. In order to stop the crashes, I always had to boot into single user mode and do a fsck -y (twice if asked) on every UFS+SU filesystem. Furthermore, if you are using SU+J, you'll have to run fsck first to deal with the journal and then fsck it again (ignoring the journal). This has brought several boxes I manage back on track on many occasions. You might want to try this, since the only downside is downtime. HTH. bye av. From owner-freebsd-questions@freebsd.org Thu Jun 1 10:07:38 2017 Return-Path: Delivered-To: freebsd-questions@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 6D7C1AF8802 for ; Thu, 1 Jun 2017 10:07:38 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (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 C6DC373C45 for ; Thu, 1 Jun 2017 10:07:37 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-oi0-x22b.google.com with SMTP id w10so47959705oif.0 for ; Thu, 01 Jun 2017 03:07:37 -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; bh=0Z/IfeL+JvI81rxMnOWmSOiTCK0VXYWVywDRirJ0m/4=; b=QKEEfvhtmKoMd1/8Uu7i4aravat4UG33lgaPv407GTngYM2C6dtj46+8cR0Fs0kDNo HqwjJwbIh3r8lAl5N69u+79UiPPk1ILNhwYp5Cs9SV986QN2agqrMB8BTpIGpBgHtRvR XngeB+Nr6ThbJsv0v5XZPKacz9P5WAKv6uPpMnv3OwRf4vETTjGG7xATnlvh5gSAuCAT P3voozFsKnjWUi4nP9nQccbVGVfojv7L/ieb44c0lbBH+jhcoaT1WqSJx3ZW2hvkF/7g lSpyAr2nayyQaaDjTNqgF3mw8yUpzLesJonXQuiSDgsLFUN8ShpPPh+ruQaz39WZ3hMw Xtbg== 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; bh=0Z/IfeL+JvI81rxMnOWmSOiTCK0VXYWVywDRirJ0m/4=; b=oz74LMI9t5Re96wdX8DTjU5ZDd2aeOOOoW7ThNGaLFPOqr6lM5NSp/bl9kcjLaZMF7 hjU0gkxWpvEvPkN9YlkvUYufqh/yJ8pDBZkuPMvBMraDLSuZPlKDzVmMzoFznEeirUWc txpcjHzqbWLwSUQ1zKHNjswB+1jSCFboZjuAr5bCXVC07KEZtaTlIQSMGUsY0eZgi2bZ BPJ34NJ8XJXeVh34eo0QpN32HSxIG9iFucaLcMGtWIShsmxoUgbmyk/5MCExnKbew2bC LL1uFvfx/UVXLdZRrVtu6O2kHS/lNu5ooTjAV5PDVUQkuhB5AOGtvJjiww9EihP+DED4 nj1A== X-Gm-Message-State: AODbwcCrgSVsm3fLzrYg6uhazFWub7MaZspY4W8a8jXBhiXZeGit8BVA bOLSbDSIbTA3VazThHSzQBXkjBGwxg== X-Received: by 10.202.62.70 with SMTP id l67mr438247oia.46.1496311656745; Thu, 01 Jun 2017 03:07:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.29.69 with HTTP; Thu, 1 Jun 2017 03:07:36 -0700 (PDT) In-Reply-To: <20170601082749.GA80543@erix.ericsson.se> References: <20170529092043.GA89682@erix.ericsson.se> <20170601051030.GA39861@geeks.org> <20170601082749.GA80543@erix.ericsson.se> From: Mehmet Erol Sanliturk Date: Thu, 1 Jun 2017 03:07:36 -0700 Message-ID: Subject: Re: Advice on kernel panics To: FreeBSD Questions Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 10:07:38 -0000 On Thu, Jun 1, 2017 at 1:27 AM, Raimo Niskanen < raimo+freebsd@erix.ericsson.se> wrote: > On Thu, Jun 01, 2017 at 12:10:30AM -0500, Doug McIntyre wrote: > > On Mon, May 29, 2017 at 11:20:43AM +0200, Raimo Niskanen wrote: > > > I have a server that panics about every 3 days and need some advice on > how > > > to handle that. > > > > I'd expect it is some sort of hardware failure, as I would expect > > kernel panics more on the order of once a decade with FreeBSD. Ie. > > I've seen one or two on my hundred or so servers, but its pretty rare. > > > > Check and recheck your hardware items. > > I have removed one of four memory capsules - panicked again. Will rotate > through all of them... > > > > > Runup memtest86+. Check your drive hardware, turn on SMART checking. > > I have run memtest86+ over night - no errors found. > > I have installed smartmontools - no errors found, short and long self tests > on both disks run fine. zpool scrub repaired 0 errors and has no known > data > errors. > > > Any further hints on how to "Check your drive hardware"? > > > Thank you for your advice. > -- > > / Raimo Niskanen, Erlang/OTP, Ericsson AB > _______________________________________________ > f > Also check cables , because , sometimes , some connector parts are not transmitting data properly . Another possibility may be a faulty executable binary because some bits may be changed in place . Another possibility may be power level ( Watts ) of power supply : Adding some new hardware part(s) may exceed capacity of existing power supply : When executed programs require more power , due to insufficient power level , circuits may be corrupted . If it is possible , by removing connectors of existing HDDs and installing a new OS on a spare disk may show possibility of modified binary existence . If the new install is not panicking , then existing installed parts may have defective parts . If the new install is also panicking , then your hardware ( for example , main board , circuits in main board ) has some trouble points . Mehmet Erol Sanliturk From owner-freebsd-questions@freebsd.org Thu Jun 1 10:27:28 2017 Return-Path: Delivered-To: freebsd-questions@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 BCCEEAF95FC for ; Thu, 1 Jun 2017 10:27:28 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp206.alice.it (smtp206.alice.it [82.57.200.102]) by mx1.freebsd.org (Postfix) with ESMTP id 54E93745BB for ; Thu, 1 Jun 2017 10:27:28 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (79.26.54.44) by smtp206.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 592F7DE10076DF1E for freebsd-questions@freebsd.org; Thu, 1 Jun 2017 12:21:29 +0200 Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) by soth.ventu (8.15.2/8.15.2) with ESMTP id v51ALTrK084662 for ; Thu, 1 Jun 2017 12:21:29 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu Subject: Re: Advice on kernel panics To: freebsd-questions@freebsd.org References: <20170529092043.GA89682@erix.ericsson.se> <20170601051030.GA39861@geeks.org> <20170601082749.GA80543@erix.ericsson.se> From: Andrea Venturoli Message-ID: <7372da18-cebf-ab0b-abfa-6dd8b8503b6a@netfence.it> Date: Thu, 1 Jun 2017 12:21:29 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170601082749.GA80543@erix.ericsson.se> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 10:27:28 -0000 On 06/01/17 10:27, Raimo Niskanen wrote: > Any further hints on how to "Check your drive hardware"? Try and change the PSU. I found out some PSU, when getting older, don't provide as much power as they used to do. Disk tests will work because they stress one disk at a time, but when all disks work together, they'll choke due to not getting enough power. Also memtest86+ checks memory when all other components are idle: again when disks and CPUs start playing, the memory banks may fail due to insufficient power. bye av. From owner-freebsd-questions@freebsd.org Thu Jun 1 13:38:06 2017 Return-Path: Delivered-To: freebsd-questions@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 37A1FAFD159 for ; Thu, 1 Jun 2017 13:38:06 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 B7F1D79D3C for ; Thu, 1 Jun 2017 13:38:04 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) X-AuditID: c1b4fb2d-5a49e9a000000d37-19-593018b3f077 Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.183.36]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 22.C7.03383.3B810395; Thu, 1 Jun 2017 15:37:55 +0200 (CEST) Received: from duper.otp.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.38) with Microsoft SMTP Server id 14.3.339.0; Thu, 1 Jun 2017 15:35:34 +0200 Received: from duper.otp.ericsson.se (localhost [127.0.0.1]) by duper.otp.ericsson.se (8.15.2/8.15.2) with ESMTP id v51DZWUM002457 for ; Thu, 1 Jun 2017 15:35:32 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) Received: (from raimo@localhost) by duper.otp.ericsson.se (8.15.2/8.15.2/Submit) id v51DZVgM002456 for freebsd-questions@freebsd.org; Thu, 1 Jun 2017 15:35:31 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) X-Authentication-Warning: duper.otp.ericsson.se: raimo set sender to raimo+freebsd@erix.ericsson.se using -f Date: Thu, 1 Jun 2017 15:35:31 +0200 From: Raimo Niskanen To: Subject: Re: Advice on kernel panics Message-ID: <20170601133531.GA2256@erix.ericsson.se> Mail-Followup-To: freebsd-questions@freebsd.org References: <20170529092043.GA89682@erix.ericsson.se> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrDLMWRmVeSWpSXmKPExsUyM2K7iu5mCYNIg8t9VhYvv25icWD0mPFp PksAYxSXTUpqTmZZapG+XQJXxqPXx9gLdnNUrPpg38B4hK2LkZNDQsBE4lPXbsYuRi4OIYEj jBIHJ29jhXA2MEq0HjzGBOG0MUlMWzCFGcJ5wihxauFJdoj+HIm3n44ygdgsAioS37fMZgax 2QRMJRp/nmEFsUUElCX+XbsIFhcGqlmx9R4jiM0LtPvrtDPMELa+xMcVr8DqhQSyJJ73tEHV CEqcnPmEBcRmFtCRWLD7E9DdHEC2tMTyfxwgJqeAvcSvRcEgpijIpq9QQ7QlJrw5wDqBUXgW kjmzkMyZhTBnASPzKkbR4tTi4tx0I2O91KLM5OLi/Dy9vNSSTYzAMD645bfuDsbVrx0PMQpw MCrx8NoIGkQKsSaWFVfmHmKU4GBWEuFtZQQK8aYkVlalFuXHF5XmpBYfYpTmYFES53XYdyFC SCA9sSQ1OzW1ILUIJsvEwSnVwFhvNWurjyivnUpt/2ej80nH4pj2SD3YHuZ+3jrbskqrnjPp 71fD+Bu9O146TEx1801/tqDvJfeNk+7/ZG0PBrqJ79loWbRfbHpn9/MrvhapE5LcCs4KyfAb /WLcVSaV2NawocAjvvdyB/uUVBENqdhJm8rj/Qq+pgRuO7Q8b3W97Y0L7n5nlViKMxINtZiL ihMBYsgMUV8CAAA= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 13:38:06 -0000 On Thu, Jun 01, 2017 at 11:58:48AM +0200, Andrea Venturoli wrote: > On 05/29/17 11:20, Raimo Niskanen wrote: > > Hello list. > > > > I have a server that panics about every 3 days and need some advice on how > > to handle that. > > As Doug suggested, it's probably an hardware fault. > > > > However, I've many times seen boxes crash every day or two when an > UFS+SU filesystem gets corrupted. Background fsck won't detect this. > > In order to stop the crashes, I always had to boot into single user mode > and do a fsck -y (twice if asked) on every UFS+SU filesystem. > > Furthermore, if you are using SU+J, you'll have to run fsck first to > deal with the journal and then fsck it again (ignoring the journal). > > This has brought several boxes I manage back on track on many occasions. > > You might want to try this, since the only downside is downtime. Good advice, but I should have given more details from the start. I have only ZFS and NFS filesystems (and devfs andalso fdescfs). -- / Raimo Niskanen, Erlang/OTP, Ericsson AB From owner-freebsd-questions@freebsd.org Thu Jun 1 13:44:25 2017 Return-Path: Delivered-To: freebsd-questions@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 95A52AFD3E6 for ; Thu, 1 Jun 2017 13:44:25 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 21E907A1A8 for ; Thu, 1 Jun 2017 13:44:24 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) X-AuditID: c1b4fb2d-5a49e9a000000d37-ab-59301a35a6f4 Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.183.54]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 67.0A.03383.53A10395; Thu, 1 Jun 2017 15:44:22 +0200 (CEST) Received: from duper.otp.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.56) with Microsoft SMTP Server id 14.3.339.0; Thu, 1 Jun 2017 15:41:31 +0200 Received: from duper.otp.ericsson.se (localhost [127.0.0.1]) by duper.otp.ericsson.se (8.15.2/8.15.2) with ESMTP id v51DfS0c002632 for ; Thu, 1 Jun 2017 15:41:28 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) Received: (from raimo@localhost) by duper.otp.ericsson.se (8.15.2/8.15.2/Submit) id v51DfSnM002631 for freebsd-questions@freebsd.org; Thu, 1 Jun 2017 15:41:28 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) X-Authentication-Warning: duper.otp.ericsson.se: raimo set sender to raimo+freebsd@erix.ericsson.se using -f Date: Thu, 1 Jun 2017 15:41:28 +0200 From: Raimo Niskanen To: Subject: Re: Advice on kernel panics Message-ID: <20170601134128.GB2256@erix.ericsson.se> Mail-Followup-To: freebsd-questions@freebsd.org References: <20170529092043.GA89682@erix.ericsson.se> <20170601051030.GA39861@geeks.org> <20170601082749.GA80543@erix.ericsson.se> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: "To: freebsd-questions@freebsd.org" User-Agent: Mutt/1.7.2 (2016-11-26) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrFLMWRmVeSWpSXmKPExsUyM2K7ma6ZlEGkQfsTHouXXzexODB6zPg0 nyWAMYrLJiU1J7MstUjfLoEr48Hm5SwFh0Urnr67zN7AuF+gi5GTQ0LARGJbx0SWLkYuDiGB I4wSBz+cZ4ZwNjBKrH5/mh3CaWOSuPzvIlTZE0aJjv132CD6cyTefjrKBGKzCKhIzHp3kxnE ZhMwlWj8eYYVxBYRUJb4d+0iWFwYqGbF1nuMIDYv0O6+NWtZIGx9iY8rXrFCLDjLKHH/9FKo hKDEyZlPwGxmAR2JBbs/AS3mALKlJZb/4wAJcwoESuy9uYAJJMwAtKvtlBCIKQqy9ivYBUIC 2hIT3hxgncAoMgvJzFlIZs5CmLmAkXkVo2hxanFxbrqRsV5qUWZycXF+nl5easkmRmCIH9zy W3cH4+rXjocYBTgYlXh4bQQNIoVYE8uKK3MPMUpwMCuJ8ApIAoV4UxIrq1KL8uOLSnNSiw8x SnOwKInzOuy7ECEkkJ5YkpqdmlqQWgSTZeLglGpg7Dhy23PBWb7V7iGPgx7MmtWTL8any7pc x8+ieV3ZidkSPrujhH571+jfPP/QN+E9Y3gV0xyfxSHFb4+fydL+eFN31ZaGxUFXZFWua37c lc4e//dzSAKv9p2uR6dd0r6uapDalX0mQkAs4nZ25v/gY/PzzzBv0P6a8WHjmco3O6Lfnsy3 nfKRU4mlOCPRUIu5qDgRAHNFQkJtAgAA X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 13:44:25 -0000 On Thu, Jun 01, 2017 at 03:07:36AM -0700, Mehmet Erol Sanliturk wrote: > On Thu, Jun 1, 2017 at 1:27 AM, Raimo Niskanen < > raimo+freebsd@erix.ericsson.se> wrote: > > > On Thu, Jun 01, 2017 at 12:10:30AM -0500, Doug McIntyre wrote: > > > On Mon, May 29, 2017 at 11:20:43AM +0200, Raimo Niskanen wrote: > > > > I have a server that panics about every 3 days and need some advice on > > how > > > > to handle that. > > > > > > I'd expect it is some sort of hardware failure, as I would expect > > > kernel panics more on the order of once a decade with FreeBSD. Ie. > > > I've seen one or two on my hundred or so servers, but its pretty rare. > > > > > > Check and recheck your hardware items. > > > > I have removed one of four memory capsules - panicked again. Will rotate > > through all of them... > > > > > > > > Runup memtest86+. Check your drive hardware, turn on SMART checking. > > > > I have run memtest86+ over night - no errors found. > > > > I have installed smartmontools - no errors found, short and long self tests > > on both disks run fine. zpool scrub repaired 0 errors and has no known > > data > > errors. > > > > > > Any further hints on how to "Check your drive hardware"? > > > > > > Thank you for your advice. > > -- > > > > / Raimo Niskanen, Erlang/OTP, Ericsson AB > > _______________________________________________ > > f > > > > > > Also check cables , because , sometimes , some connector parts are not > transmitting data properly . I'll see if I can do that. > Another possibility may be a faulty executable binary because some bits may > be changed in place . > Another possibility may be power level ( Watts ) of power supply : Adding > some new hardware part(s) may exceed capacity of existing power supply : > When executed programs require more power , due to insufficient power level > , circuits may be corrupted . This is a standard Dell Power Edge R320 with two disks of four and no extras except for an extension board with two more Ethernet ports, so that is rather unlikely, but worth looking into. > > If it is possible , by removing connectors of existing HDDs and installing > a new OS on a spare disk may show possibility of modified binary existence > . I will try "freebsd-update IDS" and see if it finds a checksum error. > > If the new install is not panicking , then existing installed parts may > have defective parts . > If the new install is also panicking , then your hardware ( for example , > main board , circuits in main board > ) has some trouble points . > > > Mehmet Erol Sanliturk Thank you for your advice. -- / Raimo Niskanen, Erlang/OTP, Ericsson AB From owner-freebsd-questions@freebsd.org Thu Jun 1 13:45:36 2017 Return-Path: Delivered-To: freebsd-questions@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 6055DAFD4B3 for ; Thu, 1 Jun 2017 13:45:36 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 DFF537A2D3 for ; Thu, 1 Jun 2017 13:45:35 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) X-AuditID: c1b4fb3a-6e3519a000004a6a-e6-59301a7692ae Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id CD.2B.19050.67A10395; Thu, 1 Jun 2017 15:45:26 +0200 (CEST) Received: from duper.otp.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.74) with Microsoft SMTP Server id 14.3.339.0; Thu, 1 Jun 2017 15:42:34 +0200 Received: from duper.otp.ericsson.se (localhost [127.0.0.1]) by duper.otp.ericsson.se (8.15.2/8.15.2) with ESMTP id v51DgWC0002651 for ; Thu, 1 Jun 2017 15:42:32 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) Received: (from raimo@localhost) by duper.otp.ericsson.se (8.15.2/8.15.2/Submit) id v51DgWaf002650 for freebsd-questions@freebsd.org; Thu, 1 Jun 2017 15:42:32 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) X-Authentication-Warning: duper.otp.ericsson.se: raimo set sender to raimo+freebsd@erix.ericsson.se using -f Date: Thu, 1 Jun 2017 15:42:32 +0200 From: Raimo Niskanen To: Subject: Re: Advice on kernel panics Message-ID: <20170601134232.GC2256@erix.ericsson.se> Mail-Followup-To: freebsd-questions@freebsd.org References: <20170529092043.GA89682@erix.ericsson.se> <20170601051030.GA39861@geeks.org> <20170601082749.GA80543@erix.ericsson.se> <7372da18-cebf-ab0b-abfa-6dd8b8503b6a@netfence.it> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <7372da18-cebf-ab0b-abfa-6dd8b8503b6a@netfence.it> "To: freebsd-questions@freebsd.org" User-Agent: Mutt/1.7.2 (2016-11-26) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrJLMWRmVeSWpSXmKPExsUyM2K7h26ZlEGkwd4DFhYvv25icWD0mPFp PksAYxSXTUpqTmZZapG+XQJXxss9d9gKWtgqLq59wt7AeIali5GTQ0LARKLvxH8gm4tDSOAI o8SaSXsYQRJCAhsYJeadFYdItDFJzDvzGKrqCaPEyun/mSDacyTefjoKZrMIqEgcuPYNbCyb gKlE488zrCC2iICyxL9rF5lBbGGgmhVb74Ft4AVa3bJhMpStL/FxxStWiAW7GSVmzd3ABJEQ lDg58wnYUGYBHYkFuz+xdTFyANnSEsv/cYCEOQXsJWZ/OMUOEmYA2tV2SgjEFAVZ+5UV4hdt iQlvDrBOYBSZhWTmLCQzZyHMXMDIvIpRtDi1uDg33chIL7UoM7m4OD9PLy+1ZBMjMMAPbvlt tYPx4HPHQ4wCHIxKPLzKggaRQqyJZcWVuYcYJTiYlUR4BSSBQrwpiZVVqUX58UWlOanFhxil OViUxHkd9l2IEBJITyxJzU5NLUgtgskycXBKNTCWShpIm7+qSet0mvRNkl9ueu/x45J50UnC Jlr7ePafWvSQp14u17ZciP+uH8/kBd557L/TDEQPb/Vamee/63+w7MmJV06aZfBsq8t89fN2 2Z0wmVkZsdMXWjxwZrqj9+hVzyqJCekLVBcrc6oYVxmazfyolnVnZ17K0+elJ34uW/uBvUL1 a7USS3FGoqEWc1FxIgAIGAcPbAIAAA== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 13:45:36 -0000 On Thu, Jun 01, 2017 at 12:21:29PM +0200, Andrea Venturoli wrote: > On 06/01/17 10:27, Raimo Niskanen wrote: > > > Any further hints on how to "Check your drive hardware"? > > Try and change the PSU. > > I found out some PSU, when getting older, don't provide as much power as > they used to do. I will check if the PSU(s) is/are pluggable. Good advice. > > Disk tests will work because they stress one disk at a time, but when > all disks work together, they'll choke due to not getting enough power. > Also memtest86+ checks memory when all other components are idle: again > when disks and CPUs start playing, the memory banks may fail due to > insufficient power. > > bye > av. -- / Raimo Niskanen, Erlang/OTP, Ericsson AB From owner-freebsd-questions@freebsd.org Thu Jun 1 14:00:00 2017 Return-Path: Delivered-To: freebsd-questions@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 CDD40AFD848 for ; Thu, 1 Jun 2017 14:00:00 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 320247A9E3 for ; Thu, 1 Jun 2017 13:59:59 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) X-AuditID: c1b4fb2d-5a49e9a000000d37-a1-59301ddcc9a9 Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 60.5E.03383.CDD10395; Thu, 1 Jun 2017 15:59:57 +0200 (CEST) Received: from duper.otp.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.86) with Microsoft SMTP Server id 14.3.339.0; Thu, 1 Jun 2017 15:53:39 +0200 Received: from duper.otp.ericsson.se (localhost [127.0.0.1]) by duper.otp.ericsson.se (8.15.2/8.15.2) with ESMTP id v51DrbRi005116; Thu, 1 Jun 2017 15:53:37 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) Received: (from raimo@localhost) by duper.otp.ericsson.se (8.15.2/8.15.2/Submit) id v51Draa4005115; Thu, 1 Jun 2017 15:53:36 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) X-Authentication-Warning: duper.otp.ericsson.se: raimo set sender to raimo+freebsd@erix.ericsson.se using -f Date: Thu, 1 Jun 2017 15:53:36 +0200 From: Raimo Niskanen To: Subject: Re: Advice on kernel panics Message-ID: <20170601135336.GD2256@erix.ericsson.se> Mail-Followup-To: freebsd-questions@freebsd.org References: <20170529092043.GA89682@erix.ericsson.se> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20170529092043.GA89682@erix.ericsson.se> "To: freebsd-questions@freebsd.org" User-Agent: Mutt/1.7.2 (2016-11-26) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBLMWRmVeSWpSXmKPExsUyM2J7iO5dWYNIg6d72Cxeft3E4sDoMePT fJYAxigum5TUnMyy1CJ9uwSujFtn4grOlFcc+byOuYHxf0IXIyeHhICJxI2pTSxdjFwcQgJH GCVOvZrKBuFsYJT40H0WKvOIUaJh8TNWCOcAo8TpL0sYIfpzJN5+OsoEYrMIqEh8OPaFBcRm EzCVaPx5hhXEFhFQlvh37SIziC0MVLNi6z2wXl6g3VPfzmOGsPUlPq54BVYvBNR77s4Udoi4 oMTJmU/AZjIL6Egs2P0J6DwOIFtaYvk/DpAwp4CZxJ2uJmaQMAPQqrZTQiCmKMjWr1ADtSUm vDnAOoFRZBaSmbOQzJyFMHMBI/MqRtHi1OLi3HQjY73Uoszk4uL8PL281JJNjMDwPrjlt+4O xtWvHQ8xCnAwKvHw2ggaRAqxJpYVV+YeYpTgYFYS4RWQBArxpiRWVqUW5ccXleakFh9ilOZg URLnddh3IUJIID2xJDU7NbUgtQgmy8TBKdXAOOPrxpsZ+imyax6ks61qtJC677R92nUNK6dz bv0u6y/UzXU8UGPn07nELO5q+fSt8/p3rLqm8Ste4o7zqtzQNvbir/ffdq0NjDnz4YXLwy8s 385/DV07M9FJp/l15e0Dst9MzaVvnynqOnOmf9otg8I5s2SXJskcerbH6RSzts28shKjGzOe lSqxFGckGmoxFxUnAgCbfFCjawIAAA== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 14:00:00 -0000 Hello again. I gave to little details in my original post; this concerns a Dell Power Edge R320 server with motherboard disk controller and ZFS only install. The dmsg is at the end of this mail. On Mon, May 29, 2017 at 11:20:43AM +0200, Raimo Niskanen wrote: > Hello list. > > I have a server that panics about every 3 days and need some advice on how > to handle that. > > It currently has 7 dumps in /var/crash/, head of the latest core.txt.4 > looks like this: > > > ======= > sasquatch.otp.ericsson.se dumped core - see /var/crash/vmcore.4 > > Mon May 29 03:15:32 CEST 2017 > > FreeBSD sasquatch.otp.ericsson.se 10.3-RELEASE-p18 FreeBSD 10.3-RELEASE-p18 > #0: Tue Apr 11 10:31:00 UTC 2017 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > panic: page fault > > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "amd64-marcel-freebsd"... > > Unread portion of the kernel message buffer: > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x0 > fault code = supervisor write data, page not present > instruction pointer = 0x20:0xffffffff809fb017 > stack pointer = 0x28:0xfffffe04673a18c0 > frame pointer = 0x28:0xfffffe04673a1900 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 18 (syncer) > trap number = 12 > panic: page fault > cpuid = 0 > KDB: stack backtrace: > #0 0xffffffff8098e7e0 at kdb_backtrace+0x60 > #1 0xffffffff809514b6 at vpanic+0x126 > #2 0xffffffff80951383 at panic+0x43 > #3 0xffffffff80d5646b at trap_fatal+0x36b > #4 0xffffffff80d5676d at trap_pfault+0x2ed > #5 0xffffffff80d55dea at trap+0x47a > #6 0xffffffff80d3bdb2 at calltrap+0x8 > #7 0xffffffff809f9b23 at vfs_msync+0x203 > #8 0xffffffff809fb858 at sync_fsync+0x108 > #9 0xffffffff80e81ed7 at VOP_FSYNC_APV+0xa7 > #10 0xffffffff809fc27b at sched_sync+0x3ab > #11 0xffffffff8091a93a at fork_exit+0x9a > #12 0xffffffff80d3c2ee at fork_trampoline+0xe > Uptime: 2d19h53m15s > ======= > > > What sticks out later in core.txt.4 is the fstat section that contains a > lot of errors, but I can not tell if that is just a secondary symptom... > > Looks like this: > ======= > fstat > > fstat: can't read file 1 at 0x200007fffffffff > fstat: can't read file 2 at 0x4000000001fffff > fstat: can't read znode_phys at 0x1 > fstat: can't read znode_phys at 0x1 > fstat: can't read znode_phys at 0x1 > : > USER CMD PID FD MOUNT INUM MODE SZ|DV R/W > root sed 78401 root - - error - > root sed 78401 wd - - error - > root sed 78401 text - - error - > root sed 78401 0* pipe fffff8001800f000 <-> fffff8001800f160 > 0 rw > root grep 78400 root - - error - > root grep 78400 wd - - error - > root grep 78400 text - - error - > : > ======= > > To me the other core.txt.? files does not look exactly the same. All have > an fstat section with many errors, though. > > Does anyone have some advice on how to proceed? > -- Copyright (c) 1992-2016 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.3-RELEASE-p18 #0: Tue Apr 11 10:31:00 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 CPU: Intel(R) Xeon(R) CPU E5-2407 v2 @ 2.40GHz (2400.06-MHz K8-class CPU) Origin="GenuineIntel" Id=0x306e4 Family=0x6 Model=0x3e Stepping=4 Features=0xbfebfbff Features2=0x7fbee3ff AMD Features=0x2c100800 AMD Features2=0x1 Structured Extended Features=0x281 XSAVE Features=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr TSC: P-state invariant, performance statistics real memory = 12884901888 (12288 MB) avail memory = 12380942336 (11807 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 random: initialized ioapic1: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 32-55 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 atrtc0: port 0x70-0x7f irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 attimer0: port 0x40-0x5f irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 550 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 Event timer "HPET3" frequency 14318180 Hz quality 440 Event timer "HPET4" frequency 14318180 Hz quality 440 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 53 at device 1.0 on pci0 pci1: on pcib1 pcib2: irq 53 at device 3.0 on pci0 pci8: on pcib2 bge0: mem 0xd90a0000-0xd90affff,0xd90b0000-0xd90bffff,0xd90c0000-0xd90cffff irq 48 at device 0.0 on pci8 bge0: APE FW version: NCSI v1.2.33.0 bge0: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: Using defaults for TSO: 65518/35/2048 bge0: Ethernet address: 00:0a:f7:52:b1:1a bge1: mem 0xd90d0000-0xd90dffff,0xd90e0000-0xd90effff,0xd90f0000-0xd90fffff irq 52 at device 0.1 on pci8 bge1: APE FW version: NCSI v1.2.33.0 bge1: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E miibus1: on bge1 brgphy1: PHY 2 on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge1: Using defaults for TSO: 65518/35/2048 bge1: Ethernet address: 00:0a:f7:52:b1:1b pcib3: irq 16 at device 17.0 on pci0 pci9: on pcib3 pci0: at device 22.0 (no driver attached) pci0: at device 22.1 (no driver attached) ehci0: mem 0xde8fd000-0xde8fd3ff irq 23 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 pcib4: at device 28.0 on pci0 pci10: on pcib4 pcib5: irq 16 at device 28.4 on pci0 pci2: on pcib5 bge2: mem 0xd91a0000-0xd91affff,0xd91b0000-0xd91bffff,0xd91c0000-0xd91cffff irq 16 at device 0.0 on pci2 bge2: APE FW version: NCSI v1.2.33.0 bge2: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E miibus2: on bge2 brgphy2: PHY 1 on miibus2 brgphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge2: Using defaults for TSO: 65518/35/2048 bge2: Ethernet address: c8:1f:66:bc:10:cd bge3: mem 0xd91d0000-0xd91dffff,0xd91e0000-0xd91effff,0xd91f0000-0xd91fffff irq 17 at device 0.1 on pci2 bge3: APE FW version: NCSI v1.2.33.0 bge3: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E miibus3: on bge3 brgphy3: PHY 2 on miibus3 brgphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge3: Using defaults for TSO: 65518/35/2048 bge3: Ethernet address: c8:1f:66:bc:10:ce pcib6: irq 19 at device 28.7 on pci0 pci3: on pcib6 pcib7: at device 0.0 on pci3 pci4: on pcib7 pcib8: at device 0.0 on pci4 pci5: on pcib8 pcib9: at device 0.0 on pci5 pci6: on pcib9 vgapci0: mem 0xd8000000-0xd8ffffff,0xddffc000-0xddffffff,0xdd000000-0xdd7fffff irq 19 at device 0.0 on pci6 vgapci0: Boot video device pcib10: at device 1.0 on pci4 pci7: on pcib10 ehci1: mem 0xde8fe000-0xde8fe3ff irq 22 at device 29.0 on pci0 usbus1: EHCI version 1.0 usbus1 on ehci1 pcib11: at device 30.0 on pci0 pci11: on pcib11 isab0: at device 31.0 on pci0 isa0: on isab0 ahci0: port 0xfce8-0xfcef,0xfcf8-0xfcfb,0xfcf0-0xfcf7,0xfcfc-0xfcff,0xfcc0-0xfcdf mem 0xde8ff000-0xde8ff7ff irq 20 at device 31.2 on pci0 ahci0: AHCI v1.30 with 6 3Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich2: at channel 2 on ahci0 ahcich3: at channel 3 on ahci0 ahcich4: at channel 4 on ahci0 ahciem0: on ahci0 pcib12: on acpi0 pci63: on pcib12 pcib13: on acpi0 pci127: on pcib13 uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 orm0: at iomem 0xc0000-0xc7fff,0xec000-0xeffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ppc0: cannot reserve I/O port range est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 1d4d00001800 device_attach: est0 attach returned 6 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 1d4d00001800 device_attach: est1 attach returned 6 est2: on cpu2 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 1d4d00001800 device_attach: est2 attach returned 6 est3: on cpu3 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 1d4d00001800 device_attach: est3 attach returned 6 ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 1.000 msec random: unblocking device. usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ses0 at ahciem0 bus 0 scbus5 target 0 lun 0 ses0: SEMB S-E-S 2.00 device ses0: SEMB SES Device ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA8-ACS SATA 2.x device ada0: Serial Number WD-WMAYP8034312 ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 476940MB (976773168 512 byte sectors) ada0: Previously was known as ad4 ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: ACS-2 ATA SATA 3.x device ada1: Serial Number WD-WCC4JDU1EVHN ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 953869MB (1953525168 512 byte sectors) ada1: quirks=0x1<4K> ada1: Previously was known as ad6 cd0 at ahcich4 bus 0 scbus4 target 0 lun 0 cd0: Removable CD-ROM SCSI device cd0: Serial Number S1596YBF3001M9 cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! Timecounter "TSC-low" frequency 1200028244 Hz quality 1000 GEOM_MIRROR: Device mirror/swap launched (2/2). Root mount waiting for: usbus1 usbus0 uhub1: 2 ports with 2 removable, self powered uhub0: 2 ports with 2 removable, self powered Root mount waiting for: usbus1 usbus0 ugen1.2: at usbus1 uhub2: on usbus1 ugen0.2: at usbus0 uhub3: on usbus0 Root mount waiting for: usbus1 usbus0 uhub3: 6 ports with 6 removable, self powered uhub2: 8 ports with 8 removable, self powered Root mount waiting for: usbus1 usbus0 ugen0.3: at usbus0 uhub4: on usbus0 ugen1.3: at usbus1 uhub5: on usbus1 uhub5: 4 ports with 4 removable, self powered uhub4: 6 ports with 6 removable, self powered Root mount waiting for: usbus1 usbus0 ugen0.4: at usbus0 ukbd0: on usbus0 kbd0 at ukbd0 ugen1.4: at usbus1 ukbd1: on usbus1 kbd2 at ukbd1 Trying to mount root from zfs:zroot/ROOT/default []... -- / Raimo Niskanen, Erlang/OTP, Ericsson AB From owner-freebsd-questions@freebsd.org Thu Jun 1 14:35:04 2017 Return-Path: Delivered-To: freebsd-questions@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 43EE4AFE36D for ; Thu, 1 Jun 2017 14:35:04 +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 8E1E77C0D6 for ; Thu, 1 Jun 2017 14:35:03 +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 v51EYh78061963; Fri, 2 Jun 2017 00:34:44 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 2 Jun 2017 00:34:43 +1000 (EST) From: Ian Smith To: Raimo Niskanen cc: freebsd-questions@freebsd.org Subject: Re: Advice on kernel panics In-Reply-To: Message-ID: <20170601235447.C98304@sola.nimnet.asn.au> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 14:35:04 -0000 In freebsd-questions Digest, Vol 678, Issue 4, Message: 4 On Thu, 1 Jun 2017 10:27:49 +0200 Raimo Niskanen wrote: > On Thu, Jun 01, 2017 at 12:10:30AM -0500, Doug McIntyre wrote: > > On Mon, May 29, 2017 at 11:20:43AM +0200, Raimo Niskanen wrote: > > > I have a server that panics about every 3 days and need some advice on how > > > to handle that. > > > > I'd expect it is some sort of hardware failure, as I would expect > > kernel panics more on the order of once a decade with FreeBSD. Ie. > > I've seen one or two on my hundred or so servers, but its pretty rare. > > > > Check and recheck your hardware items. > > I have removed one of four memory capsules - panicked again. Will rotate > through all of them... > > > > > Runup memtest86+. Check your drive hardware, turn on SMART checking. > > I have run memtest86+ over night - no errors found. > > I have installed smartmontools - no errors found, short and long self tests > on both disks run fine. zpool scrub repaired 0 errors and has no known data > errors. Everyone's suggesting hardware problems, and it's certainly worthwhile eliminating that possibility - but this could be a software/OS issue. If it were me and hardware all checks out, I'd try posting the original report - plus other details about the box and setup that you've since mentioned - to freebsd-stable@, or maybe freebsd-fs@ since those fstat reports seem to point to possible FS/zfs issues? at a wild guess .. One other hardware tester you might try is sysutils/stress which can pound CPU, I/O, VM, disk as hard and for as long as you like, without having to bring the box down. I've used this lots to generate heavy loads. Keep a close eye on system temperatures during longer tests. Ah, just before posting, I see your latest with dmesg. Just on a quick scan, I wonder if these are a bad indication? Maybe just a side-issue, but powerd might not work, so again heat might be something to watch: est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. cheers, Ian From owner-freebsd-questions@freebsd.org Thu Jun 1 14:57:55 2017 Return-Path: Delivered-To: freebsd-questions@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 1F5FFAFEB92 for ; Thu, 1 Jun 2017 14:57:55 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 9DC957D1EA for ; Thu, 1 Jun 2017 14:57:53 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) X-AuditID: c1b4fb25-73a9f9a0000055fe-f8-59302b68dc53 Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 35.6F.22014.86B20395; Thu, 1 Jun 2017 16:57:45 +0200 (CEST) Received: from duper.otp.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.80) with Microsoft SMTP Server id 14.3.339.0; Thu, 1 Jun 2017 16:53:19 +0200 Received: from duper.otp.ericsson.se (localhost [127.0.0.1]) by duper.otp.ericsson.se (8.15.2/8.15.2) with ESMTP id v51ErIxH009008 for ; Thu, 1 Jun 2017 16:53:18 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) Received: (from raimo@localhost) by duper.otp.ericsson.se (8.15.2/8.15.2/Submit) id v51ErIx9009007 for freebsd-questions@freebsd.org; Thu, 1 Jun 2017 16:53:18 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) X-Authentication-Warning: duper.otp.ericsson.se: raimo set sender to raimo+freebsd@erix.ericsson.se using -f Date: Thu, 1 Jun 2017 16:53:17 +0200 From: Raimo Niskanen To: Subject: Re: Advice on kernel panics Message-ID: <20170601145317.GE2256@erix.ericsson.se> Mail-Followup-To: freebsd-questions@freebsd.org References: <20170601235447.C98304@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20170601235447.C98304@sola.nimnet.asn.au> "To: freebsd-questions@freebsd.org" User-Agent: Mutt/1.7.2 (2016-11-26) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBLMWRmVeSWpSXmKPExsUyM2K7n26mtkGkQesBbouXXzexODB6zPg0 nyWAMYrLJiU1J7MstUjfLoErY8+6xUwFk4Qrjv56xtrAeImvi5GTQ0LAROLX+xesXYxcHEIC Rxglfj5pZYFwNjBKdO2bDJVpY5LYMusXI4TzhFHi0MwLzBD9ORJvPx1l6mLk4GARUJGYesQA JMwmYCrR+PMMK4gtIqAs8e/aRbByYaCSFVvvMYLYvECr1z1+ygxh60t8XPEKrF5IoFRi7uNT 7BBxQYmTM5+wgNjMAjoSC3Z/YgNZxSwgLbH8HwdImFPAXOL4yRVgFzAArWo7JQRiioJs/Qo1 UFtiwpsDrBMYRWYhmTkLycxZCDMXMDKvYhQtTi1Oyk03MtZLLcpMLi7Oz9PLSy3ZxAgM74Nb fqvuYLz8xvEQowAHoxIP70otg0gh1sSy4srcQ4wSHMxKIrxHNIFCvCmJlVWpRfnxRaU5qcWH GKU5WJTEeR33XYgQEkhPLEnNTk0tSC2CyTJxcEo1MNZfZZodnzq7JYC5xCnh5m3pMxP79B/6 POuYMWPZhi+5d/xuT9+Q+ca88MaSLzfOHLhrujjs+aR7R3L90vvr1hYazTjO7hMd8Vm+4VLv gZYT2Y6+25cd3rDm+T3z5DzOHVZRjROuHpfxyvn8cb+QnvF1g6i41THblme9eDTz/8OCULnv fu+Eq28psRRnJBpqMRcVJwIAze7y3GsCAAA= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 14:57:55 -0000 On Fri, Jun 02, 2017 at 12:34:43AM +1000, Ian Smith wrote: > In freebsd-questions Digest, Vol 678, Issue 4, Message: 4 > On Thu, 1 Jun 2017 10:27:49 +0200 Raimo Niskanen wrote: > > On Thu, Jun 01, 2017 at 12:10:30AM -0500, Doug McIntyre wrote: > > > On Mon, May 29, 2017 at 11:20:43AM +0200, Raimo Niskanen wrote: > > > > I have a server that panics about every 3 days and need some advice on how > > > > to handle that. > > > > > > I'd expect it is some sort of hardware failure, as I would expect > > > kernel panics more on the order of once a decade with FreeBSD. Ie. > > > I've seen one or two on my hundred or so servers, but its pretty rare. > > > > > > Check and recheck your hardware items. > > > > I have removed one of four memory capsules - panicked again. Will rotate > > through all of them... > > > > > > > > Runup memtest86+. Check your drive hardware, turn on SMART checking. > > > > I have run memtest86+ over night - no errors found. > > > > I have installed smartmontools - no errors found, short and long self tests > > on both disks run fine. zpool scrub repaired 0 errors and has no known data > > errors. > > Everyone's suggesting hardware problems, and it's certainly worthwhile > eliminating that possibility - but this could be a software/OS issue. > > If it were me and hardware all checks out, I'd try posting the original > report - plus other details about the box and setup that you've since > mentioned - to freebsd-stable@, or maybe freebsd-fs@ since those fstat > reports seem to point to possible FS/zfs issues? at a wild guess .. > > One other hardware tester you might try is sysutils/stress which can > pound CPU, I/O, VM, disk as hard and for as long as you like, without > having to bring the box down. I've used this lots to generate heavy > loads. Keep a close eye on system temperatures during longer tests. Worth a try. > > Ah, just before posting, I see your latest with dmesg. Just on a quick > scan, I wonder if these are a bad indication? Maybe just a side-issue, > but powerd might not work, so again heat might be something to watch: > > est0: on cpu0 > est: CPU supports Enhanced Speedstep, but is not recognized. This I will definitely look into! > > cheers, Ian -- / Raimo Niskanen, Erlang/OTP, Ericsson AB From owner-freebsd-questions@freebsd.org Thu Jun 1 15:15:15 2017 Return-Path: Delivered-To: freebsd-questions@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 84EF3AFF1B0 for ; Thu, 1 Jun 2017 15:15:15 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 0F2387E067 for ; Thu, 1 Jun 2017 15:15:14 +0000 (UTC) (envelope-from raimo+freebsd@erix.ericsson.se) X-AuditID: c1b4fb25-73a9f9a0000055fe-2b-59302f7f7db2 Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id B3.74.22014.F7F20395; Thu, 1 Jun 2017 17:15:11 +0200 (CEST) Received: from duper.otp.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.80) with Microsoft SMTP Server id 14.3.339.0; Thu, 1 Jun 2017 17:14:27 +0200 Received: from duper.otp.ericsson.se (localhost [127.0.0.1]) by duper.otp.ericsson.se (8.15.2/8.15.2) with ESMTP id v51FEPkE010342 for ; Thu, 1 Jun 2017 17:14:25 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) Received: (from raimo@localhost) by duper.otp.ericsson.se (8.15.2/8.15.2/Submit) id v51FEPSR010341 for freebsd-questions@freebsd.org; Thu, 1 Jun 2017 17:14:25 +0200 (CEST) (envelope-from raimo+freebsd@erix.otp.ericsson.se) X-Authentication-Warning: duper.otp.ericsson.se: raimo set sender to raimo+freebsd@erix.ericsson.se using -f Date: Thu, 1 Jun 2017 17:14:25 +0200 From: Raimo Niskanen To: Subject: Re: Advice on kernel panics Message-ID: <20170601151425.GF2256@erix.ericsson.se> Mail-Followup-To: freebsd-questions@freebsd.org References: <20170601235447.C98304@sola.nimnet.asn.au> <33501.128.135.52.6.1496329407.squirrel@cosmo.uchicago.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <33501.128.135.52.6.1496329407.squirrel@cosmo.uchicago.edu> "To: freebsd-questions@freebsd.org" User-Agent: Mutt/1.7.2 (2016-11-26) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrFLMWRmVeSWpSXmKPExsUyM2K7n269vkGkwdQn+hYvv25icWD0mPFp PksAYxSXTUpqTmZZapG+XQJXxsH1v9gKpklXrL+0ibmBsVu0i5GTQ0LAROJQ/xq2LkYuDiGB I4wST7sfM0M4Gxgljm2+wQ7htDFJrJ/0nwnCecIocf/FZVaI/hyJt5+OMoHYLAIqEgc+f2AE sdkETCUaf54BqxERUJb4d+0iM4gtDFSzYus9sBpeoN07d3xkg7D1JT6ueMUKsWAzo8TbA2eZ IRKCEidnPmEBsZkFdCQW7P4E1MABZEtLLP/HARLmFPCQuN3+lx0kzAC0q+2UEIgpCrL2K9gF QgLaEhPeHGCdwCgyC8nMWUhmzkKYuYCReRWjaHFqcVJuupGxXmpRZnJxcX6eXl5qySZGYIgf 3PJbdQfj5TeOhxgFOBiVeHhXahlECrEmlhVX5h5ilOBgVhLhPaIJFOJNSaysSi3Kjy8qzUkt PsQozcGiJM7ruO9ChJBAemJJanZqakFqEUyWiYNTqoHRZDvr4xqdCO6Wq3IzV+SLRxQatc8q X+Hgr5/ow//vwA+Hq++3mtXHthepvVvUuGqmrtG7QyWafzeKfgooLPhsefD2yerHXkWNB/Xq +pTWSvNNDf/z+5JIb+n/x71LDhz8y9gS5TZJLSvQdEsEo6DRpH0X5q8z1Y/XmH/y+6kbv0I2 8mzd/b1fiaU4I9FQi7moOBEAn2AxLm0CAAA= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 15:15:15 -0000 On Thu, Jun 01, 2017 at 10:03:27AM -0500, Valeri Galtsev wrote: > On Thu, June 1, 2017 9:34 am, Ian Smith wrote: > > In freebsd-questions Digest, Vol 678, Issue 4, Message: 4 > > On Thu, 1 Jun 2017 10:27:49 +0200 Raimo Niskanen > > wrote: > > > On Thu, Jun 01, 2017 at 12:10:30AM -0500, Doug McIntyre wrote: > > > > On Mon, May 29, 2017 at 11:20:43AM +0200, Raimo Niskanen wrote: > > > > > I have a server that panics about every 3 days and need some > advice > > on how > > > > > to handle that. > > > > > > > > I'd expect it is some sort of hardware failure, as I would expect > kernel panics more on the order of once a decade with FreeBSD. Ie. > I've seen one or two on my hundred or so servers, but its pretty > > rare. > > > > > > > > Check and recheck your hardware items. > > > > > > I have removed one of four memory capsules - panicked again. Will > > rotate > > > through all of them... > > > > > > > > > > > Runup memtest86+. Check your drive hardware, turn on SMART > checking. > > > > > > I have run memtest86+ over night - no errors found. > > > > > > I have installed smartmontools - no errors found, short and long self > > tests > > > on both disks run fine. zpool scrub repaired 0 errors and has no > known > > data > > > errors. > > > > Everyone's suggesting hardware problems, and it's certainly worthwhile > eliminating that possibility - but this could be a software/OS issue. > > I would agree with Ian, it can be software, though it is less likely. I > have seen a few times that SCSI attached external RAID (attached to LSI > SCSI HBA) was announcing change of its status (like rebuilt finished or > drive timed out/failed) which simultaneously with other traffic on SCSI > bus confused adapter and led to kernel panic. > > That said, I will first check hardware thoroughly. Andrea mentioned aged > PS under heavy load. And these are prime suspects. Of all components > electrolytic capacitors are the ones degraded most, may even leak, and > they don't filter ripple sufficiently, thus leading to ripple beyond > tolerable at high currents. So: > > 1. open the box, and inspect interior. System board ("motherboard" is its > jargon name for over 30 years): inspect electrolytic capacitors around > CPU(s), and those that filter PCI (or PCI-X, or PCI-E) bus power leads. > Any of them bulged, or even have traces of leaked electrolyte (brown > residue usually) - throw away system board. The model of your box fall > into the time span when they used worst electrolytic capacitors. I did not think this machine was old, but it has apparently been a few years... > > 2. re-seat all components (including expansion boards, memory, CPU is less > likely, but I would do that too), disconnect and reconnect all connectors. > Contacts, even gold plated, sometimes do oxidize Will try. > > 3. Get new power supply, not necessarily designed for this machine, but > with the same connectors to the system board, and with higher power > rating. disconnect box's own PS, and power it from new PS; see if it stops > failing (PSes do have electrolytic capacitors inside as well; other > components do not degrade but do not die totally, except for ultra high > frequency diodes and transistors, and very high voltage diodes) > > Good luck! > > Valeri Thank you! -- / Raimo Niskanen, Erlang/OTP, Ericsson AB From owner-freebsd-questions@freebsd.org Thu Jun 1 15:21:45 2017 Return-Path: Delivered-To: freebsd-questions@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 08593AFF35E for ; Thu, 1 Jun 2017 15:21:45 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.20.71]) by mx1.freebsd.org (Postfix) with ESMTP id BE0467E476 for ; Thu, 1 Jun 2017 15:21:44 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 476ABCB8CBD; Thu, 1 Jun 2017 10:21:43 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Thu, 1 Jun 2017 10:21:43 -0500 (CDT) Message-ID: <56274.128.135.52.6.1496330503.squirrel@cosmo.uchicago.edu> In-Reply-To: <20170601151425.GF2256@erix.ericsson.se> References: <20170601235447.C98304@sola.nimnet.asn.au> <33501.128.135.52.6.1496329407.squirrel@cosmo.uchicago.edu> <20170601151425.GF2256@erix.ericsson.se> Date: Thu, 1 Jun 2017 10:21:43 -0500 (CDT) Subject: Re: Advice on kernel panics From: "Valeri Galtsev" To: freebsd-questions@freebsd.org Reply-To: galtsev@kicp.uchicago.edu User-Agent: SquirrelMail/1.4.8-5.el5.centos.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 15:21:45 -0000 On Thu, June 1, 2017 10:14 am, Raimo Niskanen wrote: > On Thu, Jun 01, 2017 at 10:03:27AM -0500, Valeri Galtsev wrote: >> On Thu, June 1, 2017 9:34 am, Ian Smith wrote: >> > In freebsd-questions Digest, Vol 678, Issue 4, Message: 4 >> > On Thu, 1 Jun 2017 10:27:49 +0200 Raimo Niskanen >> > wrote: >> > > On Thu, Jun 01, 2017 at 12:10:30AM -0500, Doug McIntyre wrote: >> > > > On Mon, May 29, 2017 at 11:20:43AM +0200, Raimo Niskanen wrote: >> > > > > I have a server that panics about every 3 days and need some >> advice >> > on how >> > > > > to handle that. >> > > > >> > > > I'd expect it is some sort of hardware failure, as I would expect >> kernel panics more on the order of once a decade with FreeBSD. Ie. >> I've seen one or two on my hundred or so servers, but its pretty >> > rare. >> > > > >> > > > Check and recheck your hardware items. >> > > >> > > I have removed one of four memory capsules - panicked again. Will >> > rotate >> > > through all of them... >> > > >> > > > >> > > > Runup memtest86+. Check your drive hardware, turn on SMART >> checking. >> > > >> > > I have run memtest86+ over night - no errors found. >> > > >> > > I have installed smartmontools - no errors found, short and long >> self >> > tests >> > > on both disks run fine. zpool scrub repaired 0 errors and has no >> known >> > data >> > > errors. >> > >> > Everyone's suggesting hardware problems, and it's certainly worthwhile >> eliminating that possibility - but this could be a software/OS issue. >> >> I would agree with Ian, it can be software, though it is less likely. I >> have seen a few times that SCSI attached external RAID (attached to LSI >> SCSI HBA) was announcing change of its status (like rebuilt finished or >> drive timed out/failed) which simultaneously with other traffic on SCSI >> bus confused adapter and led to kernel panic. >> >> That said, I will first check hardware thoroughly. Andrea mentioned aged >> PS under heavy load. And these are prime suspects. Of all components >> electrolytic capacitors are the ones degraded most, may even leak, and >> they don't filter ripple sufficiently, thus leading to ripple beyond >> tolerable at high currents. So: >> >> 1. open the box, and inspect interior. System board ("motherboard" is >> its >> jargon name for over 30 years): inspect electrolytic capacitors around >> CPU(s), and those that filter PCI (or PCI-X, or PCI-E) bus power leads. >> Any of them bulged, or even have traces of leaked electrolyte (brown >> residue usually) - throw away system board. The model of your box fall >> into the time span when they used worst electrolytic capacitors. > > I did not think this machine was old, but it has apparently been a few > years... If it is manufactured less than 5 years ago, then I'm mistaken (I do not follow Dell server models closely...) > >> >> 2. re-seat all components (including expansion boards, memory, CPU is >> less >> likely, but I would do that too), disconnect and reconnect all >> connectors. >> Contacts, even gold plated, sometimes do oxidize > > Will try. > >> >> 3. Get new power supply, not necessarily designed for this machine, but >> with the same connectors to the system board, and with higher power >> rating. disconnect box's own PS, and power it from new PS; see if it >> stops >> failing (PSes do have electrolytic capacitors inside as well; other >> components do not degrade but do not die totally, except for ultra high >> frequency diodes and transistors, and very high voltage diodes) >> >> Good luck! >> >> Valeri > > Thank you! > > > -- > > / Raimo Niskanen, Erlang/OTP, Ericsson AB > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@freebsd.org Thu Jun 1 15:25:37 2017 Return-Path: Delivered-To: freebsd-questions@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 4EBC3AFF55E for ; Thu, 1 Jun 2017 15:25:37 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.20.71]) by mx1.freebsd.org (Postfix) with ESMTP id 151DA7E686 for ; Thu, 1 Jun 2017 15:25:36 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 2E4A2CB8CB5; Thu, 1 Jun 2017 10:03:27 -0500 (CDT) Received: from 128.135.52.6 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Thu, 1 Jun 2017 10:03:27 -0500 (CDT) Message-ID: <33501.128.135.52.6.1496329407.squirrel@cosmo.uchicago.edu> Date: Thu, 1 Jun 2017 10:03:27 -0500 (CDT) Subject: Re: Advice on kernel panics From: "Valeri Galtsev" To: "Ian Smith" Cc: "Raimo Niskanen" , freebsd-questions@freebsd.org Reply-To: galtsev@kicp.uchicago.edu User-Agent: SquirrelMail/1.4.8-5.el5.centos.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal References: <20170601235447.C98304@sola.nimnet.asn.au> In-Reply-To: <20170601235447.C98304@sola.nimnet.asn.au> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 15:25:37 -0000 On Thu, June 1, 2017 9:34 am, Ian Smith wrote: > In freebsd-questions Digest, Vol 678, Issue 4, Message: 4 > On Thu, 1 Jun 2017 10:27:49 +0200 Raimo Niskanen > wrote: > > On Thu, Jun 01, 2017 at 12:10:30AM -0500, Doug McIntyre wrote: > > > On Mon, May 29, 2017 at 11:20:43AM +0200, Raimo Niskanen wrote: > > > > I have a server that panics about every 3 days and need some advice > on how > > > > to handle that. > > > > > > I'd expect it is some sort of hardware failure, as I would expect kernel panics more on the order of once a decade with FreeBSD. Ie. I've seen one or two on my hundred or so servers, but its pretty > rare. > > > > > > Check and recheck your hardware items. > > > > I have removed one of four memory capsules - panicked again. Will > rotate > > through all of them... > > > > > > > > Runup memtest86+. Check your drive hardware, turn on SMART checking. > > > > I have run memtest86+ over night - no errors found. > > > > I have installed smartmontools - no errors found, short and long self > tests > > on both disks run fine. zpool scrub repaired 0 errors and has no known > data > > errors. > > Everyone's suggesting hardware problems, and it's certainly worthwhile eliminating that possibility - but this could be a software/OS issue. I would agree with Ian, it can be software, though it is less likely. I have seen a few times that SCSI attached external RAID (attached to LSI SCSI HBA) was announcing change of its status (like rebuilt finished or drive timed out/failed) which simultaneously with other traffic on SCSI bus confused adapter and led to kernel panic. That said, I will first check hardware thoroughly. Andrea mentioned aged PS under heavy load. And these are prime suspects. Of all components electrolytic capacitors are the ones degraded most, may even leak, and they don't filter ripple sufficiently, thus leading to ripple beyond tolerable at high currents. So: 1. open the box, and inspect interior. System board ("motherboard" is its jargon name for over 30 years): inspect electrolytic capacitors around CPU(s), and those that filter PCI (or PCI-X, or PCI-E) bus power leads. Any of them bulged, or even have traces of leaked electrolyte (brown residue usually) - throw away system board. The model of your box fall into the time span when they used worst electrolytic capacitors. 2. re-seat all components (including expansion boards, memory, CPU is less likely, but I would do that too), disconnect and reconnect all connectors. Contacts, even gold plated, sometimes do oxidize 3. Get new power supply, not necessarily designed for this machine, but with the same connectors to the system board, and with higher power rating. disconnect box's own PS, and power it from new PS; see if it stops failing (PSes do have electrolytic capacitors inside as well; other components do not degrade but do not die totally, except for ultra high frequency diodes and transistors, and very high voltage diodes) Good luck! Valeri > > If it were me and hardware all checks out, I'd try posting the original report - plus other details about the box and setup that you've since mentioned - to freebsd-stable@, or maybe freebsd-fs@ since those fstat reports seem to point to possible FS/zfs issues? at a wild guess .. > > One other hardware tester you might try is sysutils/stress which can pound CPU, I/O, VM, disk as hard and for as long as you like, without having to bring the box down. I've used this lots to generate heavy loads. Keep a close eye on system temperatures during longer tests. > > Ah, just before posting, I see your latest with dmesg. Just on a quick scan, I wonder if these are a bad indication? Maybe just a side-issue, but powerd might not work, so again heat might be something to watch: > > est0: on cpu0 > est: CPU supports Enhanced Speedstep, but is not recognized. > > cheers, Ian > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@freebsd.org Thu Jun 1 20:42:43 2017 Return-Path: Delivered-To: freebsd-questions@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 75B5CB7E6A0 for ; Thu, 1 Jun 2017 20:42:43 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [207.172.210.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 341C8674FE for ; Thu, 1 Jun 2017 20:42:42 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:470:1f07:15ff::1f] (haymarket.m5p.com [IPv6:2001:470:1f07:15ff::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id v51KAtZB099832 for ; Thu, 1 Jun 2017 16:11:00 -0400 (EDT) (envelope-from george+freebsd@m5p.com) To: freebsd-questions@freebsd.org From: George Mitchell Subject: Ancient Hardware Message-ID: Date: Thu, 1 Jun 2017 16:10:48 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4SovujXmMwt3tADK6mGwDoSSNKgDpkUP3" X-Spam-Status: No, score=0.2 required=10.0 tests=HELO_MISC_IP, RP_MATCHES_RCVD autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2 (mailhost.m5p.com [IPv6:2001:470:1f07:15ff::f7]); Thu, 01 Jun 2017 16:11:01 -0400 (EDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 20:42:43 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --4SovujXmMwt3tADK6mGwDoSSNKgDpkUP3 Content-Type: multipart/mixed; boundary="KPAe68pHqrFnufDU7dCWhIEM42i16eDoX"; protected-headers="v1" From: George Mitchell To: freebsd-questions@freebsd.org Message-ID: Subject: Ancient Hardware --KPAe68pHqrFnufDU7dCWhIEM42i16eDoX Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable What is the minimum recommended RAM for FreeBSD 10 systems? Is there any chance it would run on an i386 with only 128MB of RAM? -- George --KPAe68pHqrFnufDU7dCWhIEM42i16eDoX-- --4SovujXmMwt3tADK6mGwDoSSNKgDpkUP3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlkwdM8ACgkQwRES3m+p 4fkflxAAlypWbJdWLFZ9p2Nbpl0zrM8mxtAqdq+SnmyIJt9GAnkSZblEMAE+sg8H nnsZJewl+tZzGyD6pjEihi2ijXp1jX9f3/5w4XuIGwVuWpUOuPVmtkWj5s6xBzm2 6qAf8w2Nb03GTS64Z5X7Qvm1JwgUjQgRcISZ06T5jq430cKel4TikCtwkSlzBVzt Ip8XsWEwkHEY4IqxZkR3dyXokWXvZWGx8fdxdRC8hc4HxCyNgdJ6IiypLpp/LsJK 2Ct4U0VH70EWPPsc2HPlIwmbtBgo+pwu18F5ARKGOmO/dWzdyc0SAj7dh8EUEzBT lW3v+2k948XYj3BxZVngmKSw1cmh8RWiiKM33YfYSJFs/r8+uLF3F7LAB3lN35md wdmF8yyEujmbdYP3Gk+UxHW3Tld7im4ddt3cFT0lRSecsRrPmJZapWWeyM43EOzD oqTmK5HYHVDExeP0qQeskaQhFQ9uvIrv8NIDlv4MnXEnR1w8NCe30Frn4ldHQ1yF JjrNz1rCkzR37wOz1/z9DZLjgDspSdCuBXOM3GudXFeNRmmwX20stxRJEOLFq4dY KMcKjemyDH3F3fwTVgpCittMEYT7UL+qncJXdxpbvMfcYX0kUnwyNPWyEpq+VIvO L0Isuba3Qco1cwMZngPIXz26SjWEqTh62asottKvAqMLZf/OTVE= =A5mi -----END PGP SIGNATURE----- --4SovujXmMwt3tADK6mGwDoSSNKgDpkUP3-- From owner-freebsd-questions@freebsd.org Thu Jun 1 22:00:26 2017 Return-Path: Delivered-To: freebsd-questions@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 3CD1BB7FA5C for ; Thu, 1 Jun 2017 22:00:26 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay10.qsc.de (mailrelay10.qsc.de [212.99.163.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A7136E6BD for ; Thu, 1 Jun 2017 22:00:24 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay10.qsc.de; Thu, 01 Jun 2017 23:59:38 +0200 Received: from r56.edvax.de (port-92-195-153-207.dynamic.qsc.de [92.195.153.207]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 61C1A3CBF9; Thu, 1 Jun 2017 23:59:36 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v51LxaZF003827; Thu, 1 Jun 2017 23:59:36 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Thu, 1 Jun 2017 23:59:36 +0200 From: Polytropon To: George Mitchell Cc: freebsd-questions@freebsd.org Subject: Re: Ancient Hardware Message-Id: <20170601235936.73cf4e92.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay10.qsc.de with C69CE683D90 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1200 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 22:00:26 -0000 On Thu, 1 Jun 2017 16:10:48 -0400, George Mitchell wrote: > What is the minimum recommended RAM for FreeBSD 10 systems? Is there > any chance it would run on an i386 with only 128MB of RAM? I've been running FreeBSD 9 on a Pentium I with 150 MHz and 128 MB RAM (FreeBSD 5 with 64 MB RAM before that), so I'd say 128 MB RAM sounds possible; however, do you mean "a real Intel 80386" when you say i386, or is a Pentium-class CPU within your scope? Also consider the difference between "(basically) runs on" vs. "is usable (for)". ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@freebsd.org Thu Jun 1 22:29:57 2017 Return-Path: Delivered-To: freebsd-questions@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 A4DC4B8209A for ; Thu, 1 Jun 2017 22:29:57 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [207.172.210.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5EA6A6F399 for ; Thu, 1 Jun 2017 22:29:56 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:470:1f07:15ff::1f] (haymarket.m5p.com [IPv6:2001:470:1f07:15ff::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id v51MSSpx000895; Thu, 1 Jun 2017 18:28:33 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Subject: Re: Ancient Hardware To: Polytropon Cc: freebsd-questions@freebsd.org References: <20170601235936.73cf4e92.freebsd@edvax.de> From: George Mitchell Message-ID: Date: Thu, 1 Jun 2017 18:28:22 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <20170601235936.73cf4e92.freebsd@edvax.de> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1XQOv1D15fpHunVFx8Jso8mU2SldWDi0R" X-Spam-Status: No, score=0.2 required=10.0 tests=HELO_MISC_IP, RP_MATCHES_RCVD autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2 (mailhost.m5p.com [IPv6:2001:470:1f07:15ff::f7]); Thu, 01 Jun 2017 18:28:34 -0400 (EDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 22:29:57 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --1XQOv1D15fpHunVFx8Jso8mU2SldWDi0R Content-Type: multipart/mixed; boundary="2wkKAiat1lXuDuBAFkvhxLO92N1wPEeMx"; protected-headers="v1" From: George Mitchell To: Polytropon Cc: freebsd-questions@freebsd.org Message-ID: Subject: Re: Ancient Hardware References: <20170601235936.73cf4e92.freebsd@edvax.de> In-Reply-To: <20170601235936.73cf4e92.freebsd@edvax.de> --2wkKAiat1lXuDuBAFkvhxLO92N1wPEeMx Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 06/01/17 17:59, Polytropon wrote: > On Thu, 1 Jun 2017 16:10:48 -0400, George Mitchell wrote: >> What is the minimum recommended RAM for FreeBSD 10 systems? Is there >> any chance it would run on an i386 with only 128MB of RAM? >=20 > I've been running FreeBSD 9 on a Pentium I with 150 MHz and > 128 MB RAM (FreeBSD 5 with 64 MB RAM before that), so I'd > say 128 MB RAM sounds possible; however, do you mean "a real > Intel 80386" when you say i386, or is a Pentium-class CPU > within your scope? >=20 > Also consider the difference between "(basically) runs on" > vs. "is usable (for)". ;-) It's an AMD Geode in an old Netgate box I'm trying to revive. It does run old pfSense images, but I hoped I might be able to use it to run a newer pfSense. Thanks for your response. -- George --2wkKAiat1lXuDuBAFkvhxLO92N1wPEeMx-- --1XQOv1D15fpHunVFx8Jso8mU2SldWDi0R Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAlkwlQwACgkQwRES3m+p 4fn3nBAAiYYq8tdK//XLhr3yr9PdiZPtXYrCtWprE7uIuzV9QOzv3PFy110Hnl1M YHSZ/icZg/48V2Apyzazv8MpJJlVZ/7N3n1Did4g+yMOsAuOEEbYnVaLVlrYaT6U omN3fM6KJ4sHbrB8soyqPoJvc/J2WDoSQsc61AKwHP/pe89uFIuoThQdHjhnbUra oe3N1aFUkWzryqN0n2ekknoU1NRvlUSYgL3nJxI1A5zBj/OYKEOdloaKTKUBRFd6 5jNAC7QNX0r3Q2d00JUrrhrWb6/WhjLs614WQITmWVq6OdJcq4/Z3LZn4Hy4aA1x RSsGRQvI8e5OFfdcqYkiJ6Tv29OZ+of7KCaizAK8k+JzVm587lSkCAvKEzDG/Fmr x3i8nmyM+grrT9jQHq4BFR1W5vXF3DmdvQ5qJICF7HNZB/sGzybDk/SuiD5w3k9y CRWuAx4ALPyrunf/3VAZq/cP2nngMi4XDRz2nmSv+7TsJpJt90pXTLm4EtpvVXa5 AbVL8xpDH6zNInB3f1sG3OM2g9JvJaVLa/LzU6V3kMFBjVgVD9V2mhtisnw3cavx TTev6T1/xo6ScJz6gZ706q7eN3pc+GxzQbE6Cyl23w8ffFCQC34y4LrUd1qRGQXm K26ekCUeRDv6lhZhGHcYtDHNGFvbE+MH8joORH4Zu0r1WlxenjQ= =MZmf -----END PGP SIGNATURE----- --1XQOv1D15fpHunVFx8Jso8mU2SldWDi0R-- From owner-freebsd-questions@freebsd.org Fri Jun 2 10:02:28 2017 Return-Path: Delivered-To: freebsd-questions@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 B91D5BF3E96 for ; Fri, 2 Jun 2017 10:02:28 +0000 (UTC) (envelope-from bblister@gmail.com) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1.freebsd.org (Postfix) with ESMTP id A7AD681E30 for ; Fri, 2 Jun 2017 10:02:28 +0000 (UTC) (envelope-from bblister@gmail.com) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mwork.nabble.com (Postfix) with ESMTP id 2B42C46A96B84 for ; Fri, 2 Jun 2017 03:02:28 -0700 (MST) Date: Fri, 2 Jun 2017 03:02:28 -0700 (MST) From: BBlister To: freebsd-questions@freebsd.org Message-ID: <1496397748172-6189171.post@n6.nabble.com> Subject: Wrong Handling of pid files (example: fcgiwrap) forces single user mode. Am I correct? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 10:02:28 -0000 Hello, One of my servers (running 10.3-RELEASE-p18) faced a serious problem out of the blue. It booted normally multiuser, but after a while it switched to single user only, terminating all networking sevices (like SSHD). This was done automatically. I was able to access it only via remote serial port. I found out the culprit: In my setup I have all the services disable in /etc/rc.conf to speed up the booting process, and when the system is up, then a crontab entry for every service like "@reboot (delay 120;/usr/local/etc/rc.d/fcgiwrap onerestart )" issues the command to initiate the specific service. All the services start from @reboot entries at crontab. But I discovered that the init script for fcgiwrap (and possible other ports that use similar rc files) has a serious bug, when the command 'onerestart' is applied. If the command line parameter onerestart is used, then this script first tries to terminate the process and then restarts it. The problem is that in the termination function has this code: ... fcgiwrap_stop() { fcgiwrap_pgrp=$(/bin/ps -o ppid= $(cat ${pidfile})) ... The problem is that if the ${pidfile} does not exist then this command returns the PID 1 among other PIDS, like this: /bin/ps -o ppid= $(cat /var/run/fcgiwrap/fcgiwrap.pid) cat: /var/run/fcgiwrap/fcgiwrap.pid: No such file or directory 72303 1 71730 72092 1 1 1 and then using a command kill -TERM -- -${fcgiwrap_pgrp} terminates all these pids. But, PID 1 is the /sbin/init and according to init(8) ...init will signal the original (PID 1) init as follows: .... 1 SIGTERM Go to single-user mode So the fastcgiwrap sends SIGTERM to /sbin/init and then systems reverts to single user mode. The fix is to first check the existance of the file, like if [ -f ${pidfile} ] ; then .... and not just 'cat' and 'kill' whatever it returns. Took me a while to debug it and found the solution, and I post it here to help future admins... -- View this message in context: http://freebsd.1045724.x6.nabble.com/Wrong-Handling-of-pid-files-example-fcgiwrap-forces-single-user-mode-Am-I-correct-tp6189171.html Sent from the freebsd-questions mailing list archive at Nabble.com. From owner-freebsd-questions@freebsd.org Fri Jun 2 10:15:28 2017 Return-Path: Delivered-To: freebsd-questions@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 B7D4ABF42C2 for ; Fri, 2 Jun 2017 10:15:28 +0000 (UTC) (envelope-from jim@mailman-hosting.com) Received: from maurice.jlkmail.com (maurice.jlkmail.com [23.111.151.218]) (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 8C1AB82307 for ; Fri, 2 Jun 2017 10:15:28 +0000 (UTC) (envelope-from jim@mailman-hosting.com) Received: from maurice.jlkmail.com (localhost [127.0.0.1]) by maurice.jlkmail.com (Postfix) with ESMTP id B9E3919401EF for ; Fri, 2 Jun 2017 06:15:20 -0400 (EDT) Authentication-Results: maurice.jlkmail.com (amavisd-new); dkim=pass (1024-bit key) reason="pass (just generated, assumed good)" header.d=mailman-hosting.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= mailman-hosting.com; h=content-transfer-encoding:mime-version :x-mailer:content-type:content-type:references:in-reply-to:date :date:to:from:from:subject:subject:message-id; s=dkim; t= 1496398519; x=1497262520; bh=6EN77+t/m0ovMJkUWRq+WoM8OFMIzVT3s2t 0+cVvHko=; b=MJ6hzocZrvlhgWWUTTr3cTYm10+HoQlxB8RqItCaTviIzf5+AT5 G17KdqVtJVn0Nb+BX10uFuVkrf8Gloq1I8ioFXhqmpy+CjqcUrMhEm04SOJlwzaT vFkJ5/iJLsgX1+8QugKCer4KGXNd6qzf6L3+U4P4qIHdJ/2CSQsyucDI= X-Virus-Scanned: Debian amavisd-new at maurice.jlkmail.com X-Spam-Flag: NO X-Spam-Score: 4.296 X-Spam-Level: **** X-Spam-Status: No, score=4.296 tagged_above=-9999 required=6.31 tests=[ALL_TRUSTED=-1, RAZOR2_CF_RANGE_51_100=0.365, RAZOR2_CF_RANGE_E8_51_100=2.43, RAZOR2_CHECK=2.5, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Received: from maurice.jlkmail.com ([127.0.0.1]) by maurice.jlkmail.com (maurice.jlkmail.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id rKJiCkzeSEch for ; Fri, 2 Jun 2017 06:15:19 -0400 (EDT) Received: from yertle.fios-router.home (static-70-104-198-154.nrflva.fios.verizon.net [70.104.198.154]) by maurice.jlkmail.com (Postfix) with ESMTPSA id B040518806A0; Fri, 2 Jun 2017 06:15:18 -0400 (EDT) Message-ID: <1496398510.1994.2.camel@mailman-hosting.com> Subject: Re: Wrong Handling of pid files (example: fcgiwrap) forces single user mode. Am I correct? From: Jim Ohlstein To: BBlister , freebsd-questions@freebsd.org Date: Fri, 02 Jun 2017 06:15:10 -0400 In-Reply-To: <1496397748172-6189171.post@n6.nabble.com> References: <1496397748172-6189171.post@n6.nabble.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 10:15:28 -0000 On Fri, 2017-06-02 at 03:02 -0700, BBlister wrote: > Hello, > > One of my servers (running 10.3-RELEASE-p18) faced a serious problem > out of > the blue. It booted normally multiuser, but after a while it switched > to > single user only, terminating all networking sevices (like SSHD). > This was > done automatically. I was able to access it only via remote serial > port.  > > I found out the culprit: > In my setup I have all the services disable in /etc/rc.conf to speed > up the > booting process, and when the system is up, then a crontab entry for > every > service like "@reboot (delay 120;/usr/local/etc/rc.d/fcgiwrap > onerestart )"   > issues the command to initiate the specific service. > > All the services start from @reboot entries at crontab. But I > discovered > that the init script for fcgiwrap  (and possible other ports that use > similar rc files) has a serious bug, when the command 'onerestart' is > applied. > > If the command line parameter onerestart is used, then this script > first > tries to terminate the process and then restarts it. The problem is > that in > the termination function has this code: > > ... > fcgiwrap_stop() { >         fcgiwrap_pgrp=$(/bin/ps -o ppid= $(cat ${pidfile})) >  ... > > The problem is that if the ${pidfile} does not exist then this > command > returns the PID 1 among other PIDS, like this: > > /bin/ps -o ppid= $(cat /var/run/fcgiwrap/fcgiwrap.pid) > > cat: /var/run/fcgiwrap/fcgiwrap.pid: No such file or directory > 72303 >     1 > 71730 > 72092 >     1 >     1 >     1 >   > and then using a command  kill -TERM -- -${fcgiwrap_pgrp} > terminates all these pids. > > But, PID 1 is the /sbin/init  and according to init(8)  > ...init will signal the original (PID 1) init as follows: > .... > 1            SIGTERM    Go to single-user mode > > > So the fastcgiwrap sends SIGTERM to /sbin/init and then systems > reverts to > single user mode. > > > The fix is to first check the existance of the file, like > > if [ -f  ${pidfile} ] ; then .... > > > and not just 'cat' and 'kill' whatever it returns. Does the same thing happen if you use 'onestart' instead of 'one restart'? > > > Took me a while to debug it and found the solution, and I post it > here to > help future admins... > -- Jim Ohlstein Professional Mailman Hosting https://mailman-hosting.com/ From owner-freebsd-questions@freebsd.org Fri Jun 2 10:57:11 2017 Return-Path: Delivered-To: freebsd-questions@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 D0B59BF4FA9 for ; Fri, 2 Jun 2017 10:57:11 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B8E983506 for ; Fri, 2 Jun 2017 10:57:11 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from host-4-75.office.adestra.com (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id A1854380A for ; Fri, 2 Jun 2017 10:57:08 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/A1854380A; dkim=none; dkim-atps=neutral Subject: Re: Wrong Handling of pid files (example: fcgiwrap) forces single user mode. Am I correct? To: freebsd-questions@freebsd.org References: <1496397748172-6189171.post@n6.nabble.com> From: Matthew Seaman Message-ID: Date: Fri, 2 Jun 2017 11:56:58 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <1496397748172-6189171.post@n6.nabble.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dV7glM6KVk09qDb0L38XWw5ifNuhPqvSO" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 10:57:11 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --dV7glM6KVk09qDb0L38XWw5ifNuhPqvSO Content-Type: multipart/mixed; boundary="3DQXJGtMHIwxhcd0CoVWsH9snSdkgmgfS"; protected-headers="v1" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: Subject: Re: Wrong Handling of pid files (example: fcgiwrap) forces single user mode. Am I correct? References: <1496397748172-6189171.post@n6.nabble.com> In-Reply-To: <1496397748172-6189171.post@n6.nabble.com> --3DQXJGtMHIwxhcd0CoVWsH9snSdkgmgfS Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017/06/02 11:02, BBlister wrote: > The problem is that if the ${pidfile} does not exist then this command > returns the PID 1 among other PIDS, like this: >=20 > /bin/ps -o ppid=3D $(cat /var/run/fcgiwrap/fcgiwrap.pid) >=20 > cat: /var/run/fcgiwrap/fcgiwrap.pid: No such file or directory > 72303 > 1 > 71730 > 72092 > 1 > 1 > 1 > =20 > and then using a command kill -TERM -- -${fcgiwrap_pgrp} > terminates all these pids. Please can you open a PR at https://bugs.freebsd.org/bugzilla/ detailing your findings? This is something that should be fixed in the fcgiwrap port, and it is quite possible that other RC scripts also have the same flaw. Cheers, Matthew --3DQXJGtMHIwxhcd0CoVWsH9snSdkgmgfS-- --dV7glM6KVk09qDb0L38XWw5ifNuhPqvSO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJZMUSEXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnghcP/0P6PqIdUEEwnPxo+Lk2OR3k 0JBbzEOlpowqWnyxMtsO8KDEHWIHL+156IkX/PYAIYny8W8WnRFqSJDV+4JEq5GP XAz3vZYu6zo50FmHJAdbb+sYPfkgs3YPQ9mV9R6eudfet7hpjNU3xHEGC9YT4Qh1 tScOAIK85OPkhNOKo4u9J+GMoMvh8KPwJCcB4hha0Kwxt/B1PW91sG9yiQtPPSw5 NEo80LYzAvLp9i0RYYZIEpEK28Ym74QLPZYplztQidCmsx+khFefJzyQLDMw5LqM JBfqxyThkfYJHmeN8g5FHYWkvsnV1jm5SONVoLVryiqIwWgYG2FD2k2R2/Tq9MRe 3uGJc+m0nJ5omaeGycmQGC/VgTqdODEEaQSGefwyV2lCZNg3/cpp74w86Abto2oO WccZDzjxYDlS77k13JaAwF7Qvd/yrjtdSZSDPbsVKoSpmUc7j2Vq5Jwvrpfkmm/p R1hrEQKEddLFPX35MZdj15HGM+QJlmtn2mThz4uTrbIl+kG0xiGMhUg+AKn4MFB9 na9IYsbBPZLKJBSzSSA9zQRjFRpJ8vkeWkBpeNJkfDNTHpODZSUsoE5pdPzUs972 KqKl5yZlWqX+7YQSDveCsnW0bB+sGUHEEC43jiTGRF+zFYrqw3apX9yud9XFezJD aTztzIx99CZzHH5PZJGp =Nbt8 -----END PGP SIGNATURE----- --dV7glM6KVk09qDb0L38XWw5ifNuhPqvSO-- From owner-freebsd-questions@freebsd.org Fri Jun 2 14:32:09 2017 Return-Path: Delivered-To: freebsd-questions@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 17D4BBF8D75 for ; Fri, 2 Jun 2017 14:32:09 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D1F34644EA for ; Fri, 2 Jun 2017 14:32:08 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id 1ADD760834 for ; Fri, 2 Jun 2017 10:26:14 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c-lXQpYdTyW2 for ; Fri, 2 Jun 2017 10:26:12 -0400 (EDT) Received: from inet07.hamilton.harte-lyne.ca (inet07.hamilton.harte-lyne.ca [216.185.71.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "imap.hamilton.harte-lyne.ca", Issuer "CA HLL ISSUER 01" (not verified)) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPS for ; Fri, 2 Jun 2017 10:26:12 -0400 (EDT) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (verified OK)) by inet07.hamilton.harte-lyne.ca (Postfix) with ESMTPS id 891688A4EA for ; Fri, 2 Jun 2017 10:26:11 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id DD96D61EC3 for ; Fri, 2 Jun 2017 10:26:10 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GMrCjLZIrPgD for ; Fri, 2 Jun 2017 10:26:09 -0400 (EDT) Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca [216.185.71.24]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPSA id A6C6E60834 for ; Fri, 2 Jun 2017 10:26:08 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=harte-lyne.ca; s=dkim_hll; t=1496413568; bh=NoveD+Wjm4nFBXmUHdc1k4thR8b0Y51QU7HEHKwdAH0=; h=Date:Subject:From:To:Reply-To; b=JY+MGFui2mKlQErhnmzlauXg6wRH0E3W5LgvkIfHeU9NxDAPyGcOhHmwBqMjKQ8+v 2j0PosaUojIZm+JzFxHWpH/B8ewvgxfr9iVqBo5XcE6QIcz3bLVaLzc7jvBVjAD8x9 bF9/ZvLYGuhRXzs+e4Kff8TeaNDTrIDCGASBMGgaQZ8Say9/qte12bgpNkQmpimD+v /A/qggTrirRJ+OXb4vexA8DeDf/Z90u7gcxb4rkokJ9JhG9R8dSXD0rDVANGdL6URo jj3vScuaqSzPfq5/l8nnUtdn2uE6Z3FhqqfHe5IgfijAK+pA1y3ln4cYDLGt/GxSys YdBA6lmGTUXkA== Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Fri, 2 Jun 2017 10:26:08 -0400 Message-ID: <74b7b58aa45cc01585338ef2270ccc57.squirrel@webmail.harte-lyne.ca> Date: Fri, 2 Jun 2017 10:26:08 -0400 Subject: IPv4 to IPv6 From: "James B. Byrne" To: freebsd-questions@harte-lyne.ca Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.22-4.el6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 14:32:09 -0000 We are beginning the process of transitioning to IPv6. I have read a great deal respecting the difficulty of moving from IPv4 to IPv6 and maintaining general Internet connectivity. If any reading this have gone through the process upon which we are embarking then I would be grateful if you share your experience. Particularly any 'gotchas' that cropped up. We will be using FreeBSD-11 as the platform for our Internet connectivity. The main services we provide publicly are SMTP and DNS. We will maintain IPv4 addresses for these together with IPv6. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 From owner-freebsd-questions@freebsd.org Fri Jun 2 15:48:50 2017 Return-Path: Delivered-To: freebsd-questions@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 ED3B1BFA30E for ; Fri, 2 Jun 2017 15:48:50 +0000 (UTC) (envelope-from bblister@gmail.com) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1.freebsd.org (Postfix) with ESMTP id DBA1867B03 for ; Fri, 2 Jun 2017 15:48:50 +0000 (UTC) (envelope-from bblister@gmail.com) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mwork.nabble.com (Postfix) with ESMTP id 7F1BF46B9E9FE for ; Fri, 2 Jun 2017 08:48:50 -0700 (MST) Date: Fri, 2 Jun 2017 08:48:50 -0700 (MST) From: BBlister To: freebsd-questions@freebsd.org Message-ID: <1496418530514-6189230.post@n6.nabble.com> In-Reply-To: References: <1496397748172-6189171.post@n6.nabble.com> Subject: Re: Wrong Handling of pid files (example: fcgiwrap) forces single user mode. Am I correct? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 15:48:51 -0000 OK, I filled a report https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219724 If you issue onestart the bug is not triggered. Also, the bug with onerestart is not triggered all the time. For example, if you do rm /var/run/fcgiwrap/fcgiwrap.pid and then issue as root from the shell: /usr/local/etc/rc.d/fcgiwrap onerestart then you see usually: cat: /var/run/fcgiwrap/fcgiwrap.pid: No such file or directory Stopping fcgiwrap. kill: illegal process id: - Starting fcgiwrap. But, there is a race condition, because if you do a number of times: rm /var/run/fcgiwrap/fcgiwrap.pid and then debug the rc script with: rm /var/run/fcgiwrap/fcgiwrap.pid ; bash -x /usr/local/etc/rc.d/fcgiwrap onerestart you will eventually hit the single user mode, because the PID 1 is somewhere in the list: kill -TERM -- - 1 17009 17607 17654 1 1 1 1 1 86584 4245 5166 5929 80402 86559 if it is the first one like the previous example, then it will hit user mode immediately, otherwise the script may exit first before hitting the PID 1, like kill -TERM -- - 17009 17607 17654 1 1 1 1 1 86584 4245 5166 5929 80402 86559 -- View this message in context: http://freebsd.1045724.x6.nabble.com/Wrong-Handling-of-pid-files-example-fcgiwrap-forces-single-user-mode-Am-I-correct-tp6189171p6189230.html Sent from the freebsd-questions mailing list archive at Nabble.com. From owner-freebsd-questions@freebsd.org Fri Jun 2 16:00:53 2017 Return-Path: Delivered-To: freebsd-questions@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 22134BFA70E for ; Fri, 2 Jun 2017 16:00:53 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B26686819E for ; Fri, 2 Jun 2017 16:00:52 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from host-4-75.office.adestra.com (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id BC72B3886 for ; Fri, 2 Jun 2017 16:00:49 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/BC72B3886; dkim=none; dkim-atps=neutral Subject: Re: IPv4 to IPv6 To: freebsd-questions@freebsd.org References: <74b7b58aa45cc01585338ef2270ccc57.squirrel@webmail.harte-lyne.ca> From: Matthew Seaman Message-ID: <0c5727a2-05ea-51e0-21bd-ded1c2b831b5@FreeBSD.org> Date: Fri, 2 Jun 2017 17:00:44 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <74b7b58aa45cc01585338ef2270ccc57.squirrel@webmail.harte-lyne.ca> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="jxOOvFxSlRdL8fwic9Mk3aQn9G2dewdcM" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 16:00:53 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --jxOOvFxSlRdL8fwic9Mk3aQn9G2dewdcM Content-Type: multipart/mixed; boundary="kn3VCakPK3d8tLb7ej1TgTifruoR10wmG"; protected-headers="v1" From: Matthew Seaman To: freebsd-questions@freebsd.org Message-ID: <0c5727a2-05ea-51e0-21bd-ded1c2b831b5@FreeBSD.org> Subject: Re: IPv4 to IPv6 References: <74b7b58aa45cc01585338ef2270ccc57.squirrel@webmail.harte-lyne.ca> In-Reply-To: <74b7b58aa45cc01585338ef2270ccc57.squirrel@webmail.harte-lyne.ca> --kn3VCakPK3d8tLb7ej1TgTifruoR10wmG Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017/06/02 15:26, James B. Byrne via freebsd-questions wrote: > We are beginning the process of transitioning to IPv6. I have read a > great deal respecting the difficulty of moving from IPv4 to IPv6 and > maintaining general Internet connectivity. If any reading this have > gone through the process upon which we are embarking then I would be > grateful if you share your experience. Particularly any 'gotchas' that > cropped up. >=20 > We will be using FreeBSD-11 as the platform for our Internet > connectivity. The main services we provide publicly are SMTP and DNS.=20 > We will maintain IPv4 addresses for these together with IPv6. I've /added/ IPv6 capability to an existing network -- there's no way we're going to be dropping IPv4 any time soon. It is really quite straightforward. Exactly how you get an IPv6 address allocation and get that routed to your hosts depends very much on where in the world you are and what your ISP is prepared to provide. Most ISPs nowadays should be able to set up IPv6 routing into your systems for you as a standard service offering. Failing that, there are IPv6 "tunnel brokers" who will happily sell you a service. Now, assuming you've got to the stage where you have IPv6 being routed to your network gateway, it is mostly plain sailing. In general, it just works. You configure your IPv6 addressing in parallel to your IPv4 addressing scheme. There are a number of, well, not gotchas per se, but ways of thinking you will need to adjust. First of all, you have to re-educate yourself from the mindset of IP numbers being a scarce resource. Forget about NAT. Everything gets its own address. In fact, you have so many addresses to play with you can allocate an address to each host chassis (the SLAAC address works well for this) plus a separate address for each different network service you're running on it -- that way, moving a service onto different hardware is mostly a matter of syncing the data and moving one IPv6 address. Without NAT you will need to write an effective firewall ruleset to block unwanted traffic. This isn't particularly difficult and a correctly configured firewall is just as secure, if not more so than what you'ld get from a NAT gateway. It is true that IPv6 addresses are a bit of a pain to type, compared to IPv4. So allocate "short" addresses -- mostly runs of zeroes -- to your DNS servers and possibly your default router, as those are the addresses you get to type most frequently. Otherwise rely on the DNS to turn hostnames into addresses. If you want to make it impossible for people to nmap your network range, scatter your allocated addresses across the whole range available to you. If you're allocating a few hundred addresses out of a /64 you can just generate addresses randomly without fear of collisions. Note there are some bits in an IPv6 address that flag certain different address usages which you should be aware of -- see RFC 4291. If nmap is not a concern, then fill up most of the host part of each address with zeroes to make the typing a bit easier. Second of all, the smallest sub-net prefix you should consider using is a /64. A typical IPv6 allocation to a company would be a /48, possibly going up to a /32 for a really big installation[*]. If your allocation is a /48, that means you have 2^16 =3D=3D 65536 possible different /64 subnets available to you. Considering that a /64 network gives you about 18446744073709551615 different possible host addresses, it is not really intrinsically more wasteful to allocate a /64 for a hand-off network with only two active addresses as it is to allocate a /64 to a LAN segment full of servers using a hundred or so addresses. Forget about NAT. Everything gets its own address. In fact, you have *so* many addresses to play with you can allocate an address to each host chassis (the SLAAC address works well for this) plus a separate address for each different network service you're running on it -- that way, moving a service onto different hardware is mostly a matter of syncing the data and moving one IPv6 address. Without NAT you will need to write an effective firewall ruleset to block unwanted traffic. This isn't particularly difficult and a correctly configured firewall offers just as much security, if not more so, than you'ld get through a NAT gateway. It is true that IPv6 addresses are a bit of a pain to type, compared to IPv4. So allocate "short" addresses -- mostly runs of zeroes -- to your DNS servers and possibly your default router, as those are the addresses you get to type most frequently. Otherwise rely on the DNS to turn hostnames into addresses. If you want to make it impossible for people to nmap your network range, scatter your allocated addresses across the whole range available to you. If you're allocating a few hundred addresses out of a /64 you can just generate addresses randomly without fear of collisions. If nmap is not a concern, then fill up most of the host part of each address with zeroes to make the typing a bit easier. You will find that FreeBSD defaults to preferring IPv6 over IPv4 when both are available. This is mostly a good thing -- IPv6 typically offers ping times a few milliseconds faster than IPv4 across the Internet nowadays -- but if you need to be particularly cautious while you are introducing IPv6, then look at ip6addrctrl(8) and /etc/rc.d/ip6addrctl which will let you prioritize IPv4 over IPv6 during the transitional period. On the whole though setting up IPv6 networks is really no harder than setting up IPv4 networks. Cheers, Matthew [*] At least, this is the case in the RIPE region. I don't think the other regional bodies do things significantly differently. If you're getting a sub-allocation from an ISP, then they really should be prepared to be similarly generous. --kn3VCakPK3d8tLb7ej1TgTifruoR10wmG-- --jxOOvFxSlRdL8fwic9Mk3aQn9G2dewdcM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJZMYuxXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnmb4QAJBUi3kPT71ExmxY731PeeZi K6aiZQdZVz6nMHpcPyapEkGlq0nZgGHWKPW3/ZEdsqUmDL3J6c3lsKxuLO9vh41G OJM8QmBl2RtYbw+/aa93mrtBrFAoUw1x6OsI5rw6kzkT7vqpT5sonfqb9YK6qz70 +sh+frB12vVy+TRR3E9o699kRvwqX/31JmohOWP9FeYtSL+oMKEdrA1X65vGKrLW UFpGCF0l5S79rL9OGhClkk4LiGFHIyf57TZbt9abs/2R1+JCaac+KzOkpe31+asi w0P66k5ujahmn+s8oBY4GTTiz4EwMYEyefZPmueimVb5/tiHg0wdz67RmeU2s1FA DP9TYlsKd2eLww4pRx/ixKWUBBgGj4KKYui0ZrLwNbgJ+4fKiLdHx+7XSUJlBXaU VhB4vPZmyrQQxaqpb5C2oL3EDQV7V4MJ/GyAB9O9OPqXli/CR1IrQi9NNjX1h0v+ Mx1xTEMQMoF4ie+nO5altxV/khJt9/a8gOI5S31HVWf07GRQ5xtFUytvBAtixWlD TX2xTe2QzBvR9px9G2IVsNF/yENMYyJDYtDWA0+mGuc4QfykQ0fP77QMAtZcrxd4 XG0Svsk5JPht3QnAJU0nm+w9wFwRS8X33Kg4lLbZHwgrRTLk87XK1hWvmzS19SM2 l7lg3lLN7Ue8/CNSN81N =552k -----END PGP SIGNATURE----- --jxOOvFxSlRdL8fwic9Mk3aQn9G2dewdcM-- From owner-freebsd-questions@freebsd.org Fri Jun 2 16:31:56 2017 Return-Path: Delivered-To: freebsd-questions@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 61D18BFAD5C for ; Fri, 2 Jun 2017 16:31:56 +0000 (UTC) (envelope-from tjg@ucsc.edu) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::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 013006A02E for ; Fri, 2 Jun 2017 16:31:55 +0000 (UTC) (envelope-from tjg@ucsc.edu) Received: by mail-lf0-x22d.google.com with SMTP id a136so31329805lfa.0 for ; Fri, 02 Jun 2017 09:31:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google; h=mime-version:from:date:message-id:subject:to; bh=/Z/4+EpMv3S061rVS8Jg+XJTUcjhETFOd7Ff3RVlY1E=; b=e/Qy6yAVT5mKtgB/Th3JB1N2SCC0xIkVcZ9TYrcahtRtTgFEpJD9gCaHa04S4dvN6S 2hoTg1sHX5XaJ9uzKjjgI7sEQrmIjM6Al/SQrVWcXUOCt3eXQiibsjIymLVGUXjXUHkL mywgHjjXfmFBAyXWM0g7PhtZBmTiDRn4I8bc0= 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=/Z/4+EpMv3S061rVS8Jg+XJTUcjhETFOd7Ff3RVlY1E=; b=XvSwut/K/d06rB1oFtV1jpnSHFdllXg8/8qXt9WzQwAORLTOwTsnhPnrGP3bl9OnT/ BAiG8tQF+jstYFcliBQyadSPYDOb26Y6fSaFMrugcfgQJUacN8gYg17M0FVUbu5tE07G WhQEpcnrpMLc8CnkbC97am3wG8MXtCXg2OdlgNyLOBMoSEhT6U3n/21RkhKytUXQS9Xi B2mkf2H4wQM31/btVD9KAJv17wq0i4+dd/4Swl6GO9H00TXTImHObkrpoyc3PhRHyGIr Ub3qs5yPh8Ye2bTNcNKB1hg4g06IIPubRa+7+ot+AxmtnBVYe593J9+eYBZjNgXLpKNQ il+A== X-Gm-Message-State: AODbwcAvvk2UzV4ANzA6aUhjIOc2qtqFnfHcEnGT/NLDQmiXnMbki62q I75IDTxqCm8ryAnkufUHNqzT5w/YJdp9z4yrgg== X-Received: by 10.46.5.130 with SMTP id 124mr1201750ljf.95.1496421113983; Fri, 02 Jun 2017 09:31:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.16.31 with HTTP; Fri, 2 Jun 2017 09:31:53 -0700 (PDT) From: Tim Gustafson Date: Fri, 2 Jun 2017 09:31:53 -0700 Message-ID: Subject: Excluding File Systems from 100.chksetuid and 110.neggrpperm To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 16:31:56 -0000 Hi, We have several FreeBSD 10.x and 11.x servers that host about 150TB of ZFS file systems each. Each day, the 100.chksetuid and 110.neggrpperm run against our entire data set, which has hundreds of millions of files in it, and winds up slowing everything down and using up all our resources. Looking at those scripts, they don't seem to take any parameters, and I can't configure them to exclude certain folders that really just don't need to be scanned. I did find this post which suggested a patch for FreeBSD 9.x, but it does not appear to have even been implemented: https://forums.freebsd.org/threads/31846/ Is there any hope of getting these options added? -- Tim Gustafson BSOE Computing Director tjg@ucsc.edu 831-459-5354 Baskin Engineering, Room 313A To request BSOE IT support, please visit https://support.soe.ucsc.edu/ or send e-mail to help@soe.ucsc.edu. From owner-freebsd-questions@freebsd.org Fri Jun 2 16:44:08 2017 Return-Path: Delivered-To: freebsd-questions@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 D3DF4BFB196 for ; Fri, 2 Jun 2017 16:44:08 +0000 (UTC) (envelope-from jon@radel.com) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C6066A7CB for ; Fri, 2 Jun 2017 16:44:07 +0000 (UTC) (envelope-from jon@radel.com) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id 4EB3A60263 for ; Fri, 2 Jun 2017 12:44:06 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Apu3atCr8Y4m for ; Fri, 2 Jun 2017 12:44:03 -0400 (EDT) Received: from inet07.hamilton.harte-lyne.ca (inet07.hamilton.harte-lyne.ca [216.185.71.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "imap.hamilton.harte-lyne.ca", Issuer "CA HLL ISSUER 01" (not verified)) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPS for ; Fri, 2 Jun 2017 12:44:03 -0400 (EDT) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (verified OK)) by inet07.hamilton.harte-lyne.ca (Postfix) with ESMTPS id BCFA58A581; Fri, 2 Jun 2017 12:44:02 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id 1FC3B60263; Fri, 2 Jun 2017 12:44:02 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VnCEuTiMRm3s; Fri, 2 Jun 2017 12:43:59 -0400 (EDT) X-Greylist: delayed 3601 seconds by postgrey-1.34 at inet08.hamilton.harte-lyne.ca; Fri, 02 Jun 2017 12:43:59 EDT Received: from radel.com (fly.radel.com [70.184.242.170]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.radel.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPS; Fri, 2 Jun 2017 12:43:58 -0400 (EDT) X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.19.2 (ClamAV engine v0.99.2) X-ExtFilter: Niversoft's DomainKeys Helper DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; d=radel.com; s=20170108.radel; h=Subject:To:References:From:Message-ID:Date:User-Agent: MIME-Version:In-Reply-To:Content-Type; b=h1pAwSLOLLBy5QhGLDojwETt4kd7UYJD9AyNxbcn7bm7BMD+fZ19kQp/fxAb+PTKl4 pSL5F2aFW0lmwgQha5+RXA2KsuJ3jIR8Xe+G1ocHps0EdmW77yZuwqzv80isT/UIXSNw Dx9uJ7lWaTknHTZTgRJ73HSTB5DRiMlfXa3hH6txKqlbMLkf3GBL/4+XyZLvHl6npRek vQOEre0iL2FPvLjdpObB1+UujRnU7+OBeRsKluyZ1pfOI3g+0A+qLnv2YJ0mzNDcu8+A FOOlVJ1E1md2HDbfKxoB25nEMwcH6BW0zCripPLGRRAnPHkfSbrbCeRj8Rut8nBWFUsF Sn6Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=radel.com; s=20170108.radel; t=1496418235; x=1497023035; q=dns/txt; h=Subject:To:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type; bh=LyMqk+MtAtb 74fJsjlX1DmhxKcWV9lRKjFjszBWOWUs=; b=0gA1jwWR1X6Drsy0J3PwklAe/rQ 7GQHNkyqRZNPR1DGQN6hhV/10YxwnO94B/YCfqUQoimyS/KAQ9Q07vYRxwuxIYTE XmuZenFZd3bAIxgW+HQH2z/CQRmNl4QjmasZgp5KIIZiTxfZbmPaGyAY++DKg6H5 XuJMrvDD9fjAe1yDn+f2g2hpZAbYcUOdZOiztcCZzuNnZyRav6EflblnUpB9BUVr x+cRCwaPg4k5x6CmeIek7+wx4+CkoI9BaoWD0HVXsO+wzkZgxHVf9Je8vy5WCc4N VUkUoc+NgyikwB9+IM0JuSJQAwy9Lp4RNgSVb5GuTh0EcXIdxGU59doKgCw== Received: from [2001:470:880a:4389:fc8d:48e7:c9f:95e7] (account jon@radel.com HELO haralson.local) by radel.com (CommuniGate Pro SMTP 6.1.14 _community_) with ESMTPSA id 1337652; Fri, 02 Jun 2017 15:43:55 +0000 Subject: Re: IPv4 to IPv6 To: byrnejb@harte-lyne.ca, freebsd-questions@harte-lyne.ca References: <74b7b58aa45cc01585338ef2270ccc57.squirrel@webmail.harte-lyne.ca> From: Jon Radel Message-ID: <691d853e-e2f7-b5f3-d281-73511845bd6a@radel.com> Date: Fri, 2 Jun 2017 11:43:55 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <74b7b58aa45cc01585338ef2270ccc57.squirrel@webmail.harte-lyne.ca> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms010006010309090507060101" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 16:44:08 -0000 This is a cryptographically signed message in MIME format. --------------ms010006010309090507060101 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US On 6/2/17 10:26, James B. Byrne via freebsd-questions wrote: > We are beginning the process of transitioning to IPv6. I have read a > great deal respecting the difficulty of moving from IPv4 to IPv6 and > maintaining general Internet connectivity. If any reading this have > gone through the process upon which we are embarking then I would be > grateful if you share your experience. Particularly any 'gotchas' that > cropped up. > > We will be using FreeBSD-11 as the platform for our Internet > connectivity. The main services we provide publicly are SMTP and DNS.=20 > We will maintain IPv4 addresses for these together with IPv6. > > Do you really plan to remove IPv4 from everything other than your SMTP and DNS servers? If so, how will your users [assuming you have such] reach resources on the IPv4 Internet? Or have I misunderstood? An orderly migration to being dual-stacked on everything would probably be a lot less painful than what I think you're planning. While there are possible mechanisms for an IPv6-only client to reach resources on the IPv4 Internet, I'm unclear on the benefits of bothering with such an architecture. --=20 --Jon Radel jon@radel.com --------------ms010006010309090507060101 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC Cq8wggSvMIIDl6ADAgECAhEA4CPLFRKDU4mtYW56VGdrITANBgkqhkiG9w0BAQsFADBvMQsw CQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4 dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290 MB4XDTE0MTIyMjAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZsxCzAJBgNVBAYTAkdCMRswGQYD VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNP TU9ETyBDQSBMaW1pdGVkMUEwPwYDVQQDEzhDT01PRE8gU0hBLTI1NiBDbGllbnQgQXV0aGVu dGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAImxDdp6UxlOcFIdvFamBia3uEngludRq/HwWhNJFaO0jBtgvHpRQqd5jKQi3xdh TpHVdiMKFNNKAn+2HQmAbqUEPdm6uxb+oYepLkNSQxZ8rzJQyKZPWukI2M+TJZx7iOgwZOak +FaA/SokFDMXmaxE5WmLo0YGS8Iz1OlAnwawsayTQLm1CJM6nCpToxDbPSBhPFUDjtlOdiUC ISn6o3xxdk/u4V+B6ftUgNvDezVSt4TeIj0sMC0xf1m9UjewM2ktQ+v61qXxl3dnUYzZ7ifr vKUHOHaMpKk4/9+M9QOsSb7K93OZOg8yq5yVOhM9DkY6V3RhUL7GQD/L5OKfoiECAwEAAaOC ARcwggETMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0GA1UdDgQWBBSSYWuC 4aKgqk/sZ/HCo/e0gADB7DAOBgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADAd BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEQYDVR0gBAowCDAGBgRVHSAAMEQGA1Ud HwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFs Q0FSb290LmNybDA1BggrBgEFBQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVz ZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQELBQADggEBABsqbqxVwTqriMXY7c1V86prYSvACRAj mQ/FZmpvsfW0tXdeDwJhAN99Bf4Ss6SAgAD8+x1banICCkG8BbrBWNUmwurVTYT7/oKYz1gb 4yJjnFL4uwU2q31Ypd6rO2Pl2tVz7+zg+3vio//wQiOcyraNTT7kSxgDsqgt1Ni7QkuQaYUQ 26Y3NOh74AEQpZzKOsefT4g0bopl0BqKu6ncyso20fT8wmQpNa/WsadxEdIDQ7GPPprsnjJT 9HaSyoY0B7ksyuYcStiZDcGG4pCS+1pCaiMhEOllx/XVu37qjIUgAmLq0ToHLFnFmTPyOInl tukWeh95FPZKEBom+nyK+5swggX4MIIE4KADAgECAhBzVOU8fWu0zQ1gaQ38zgEbMA0GCSqG SIb3DQEBCwUAMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVy MRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h aWwgQ0EwHhcNMTUwMzMwMDAwMDAwWhcNMTgwMzI5MjM1OTU5WjCB+jELMAkGA1UEBhMCVVMx DjAMBgNVBBETBTIyMTUwMQswCQYDVQQIEwJWQTEUMBIGA1UEBxMLU3ByaW5nZmllbGQxGjAY BgNVBAkTETY5MTcgUmlkZ2V3YXkgRHIuMRUwEwYDVQQKEwxKb24gVC4gUmFkZWwxMjAwBgNV BAsTKUlzc3VlZCB0aHJvdWdoIEpvbiBULiBSYWRlbCBFLVBLSSBNYW5hZ2VyMR8wHQYDVQQL ExZDb3Jwb3JhdGUgU2VjdXJlIEVtYWlsMRIwEAYDVQQDEwlKb24gUmFkZWwxHDAaBgkqhkiG 9w0BCQEWDWpvbkByYWRlbC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDe 1Rth9hbQqaODn++C5dVAQH9nM2VH3oPazZufOwmIG2SXI/v3PuemcQQ3JkhmpQ06gYszyXbk TCLsqvEfalYj81jdt/K5lT4aVdj0LfJIWyTcU95V2rsCuHsSvn/PnIcsEtXg53rCtqS4EOtJ 9u3rY2hP8YCiyz1yY3mn4nKJs93MHG4AkXYuVpzfaIADETcVrA+razvXEfnDJXXDZZ9ZuuV1 06yIovOvhYWSlaVu8nrSHJjXFZI2IXwgIeVBoMih3yu6LLj14I/YdZ0rIA8K+UNB+NW6Ri3u wHXBbr4jh3ZqkrqIVUrf1VeybhdrJcdqXdMNHjKDSlCoaxYRbLy1AgMBAAGjggHVMIIB0TAf BgNVHSMEGDAWgBSSYWuC4aKgqk/sZ/HCo/e0gADB7DAdBgNVHQ4EFgQUz9YB10WEfBNHskRw o/0vh8qaQuwwDgYDVR0PAQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwHQYDVR0lBBYwFAYIKwYB BQUHAwQGCCsGAQUFBwMCMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQMFMCswKQYIKwYBBQUH AgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMF0GA1UdHwRWMFQwUqBQoE6GTGh0 dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1NIQTI1NkNsaWVudEF1dGhlbnRpY2F0aW9u YW5kU2VjdXJlRW1haWxDQS5jcmwwgZAGCCsGAQUFBwEBBIGDMIGAMFgGCCsGAQUFBzAChkxo dHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9TSEEyNTZDbGllbnRBdXRoZW50aWNhdGlv bmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5jb21vZG9j YS5jb20wGAYDVR0RBBEwD4ENam9uQHJhZGVsLmNvbTANBgkqhkiG9w0BAQsFAAOCAQEAS1Pe +gBgP+SQ/a5I5e7zX0Rg0DhH378LHlZixJgS6LfCPL2edKMUQi3Th9GXfLjdeyeWuMWoz925 ZzBHcPwkBeH+iM/AEhu0Dhi0kop/p66g9tEPJUZ/KDsqxddNDrD0Typn3/33pHTjJEDqydzA gwB0Nn8blpMbqSwT+j8wuPakfLsj1cSDzXrTLLsmIQB7auAyaYXdWyW8Yqw336rLUCvjOUfn qOOyjVsieTw/0PLoOHJaGyez+VtV4eyi6p1SNiX32A+fvxBMzKQLCokE43cXItc9Okzq//f2 fuvGp17r8mpm4OjjM5E2kwsg9bBPUBMR4/sxosKVLn0o9rxlozGCBEEwggQ9AgEBMIGwMIGb MQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdT YWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNI QS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEHNU5Tx9 a7TNDWBpDfzOARswDQYJYIZIAWUDBAIBBQCgggJhMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B BwEwHAYJKoZIhvcNAQkFMQ8XDTE3MDYwMjE1NDM1NVowLwYJKoZIhvcNAQkEMSIEILU4zYVA DDgkmHNGqtD+2h8hxPCXF0EWwPyJ91G6rQeeMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUD BAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcN AwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgcEGCSsGAQQBgjcQBDGBszCBsDCBmzEL MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEt MjU2IENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhBzVOU8fWu0 zQ1gaQ38zgEbMIHDBgsqhkiG9w0BCRACCzGBs6CBsDCBmzELMAkGA1UEBhMCR0IxGzAZBgNV BAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09N T0RPIENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50 aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhBzVOU8fWu0zQ1gaQ38zgEbMA0GCSqGSIb3 DQEBAQUABIIBAD/JnNG1PZGY4zkHBJXzPvwf53inbV8bZaIc+bFhSK+pRQwwAOodiG1lBwzO 49VY0k2nezVYATjiZVumPAql4f3N7/tDis7UNdHjFncVLdV98A1f/oK1VgL9hsYODNJuiGCo DuilpeTqDpib48+tBNPkx5GZeFb3YCA/OiAuZqvhWJgchLQlYXJz4rtHpPB1nEBFkyAGvOxN R4sK2dst940Z9tKpHEXsYAB0Hf31iGTqlW1/tYev+JDpZS8wBwfZahctz6twnsJ9l97HxI5z Pnz09xcFxqg6suH9GWdo5t+R8KrnV+4QV4haAmmssoIbyYPkEoeU3lK9K5LwHf8YDuQAAAAA AAA= --------------ms010006010309090507060101-- From owner-freebsd-questions@freebsd.org Fri Jun 2 16:48:19 2017 Return-Path: Delivered-To: freebsd-questions@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 7F909BFB285 for ; Fri, 2 Jun 2017 16:48:19 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (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 4181B6A905 for ; Fri, 2 Jun 2017 16:48:19 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-oi0-x22a.google.com with SMTP id s3so8200460oia.0 for ; Fri, 02 Jun 2017 09:48:19 -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=xlzKj3MAybW5ZSYqMhfgR9YJY63LFKPfYEik2iX5oXg=; b=ey0KwWLRhJDrrDh1XIynCBE2QgYyncOEYKyH2R14jFGpyPo6it33adCwM27ag3g2Ow 6vNvolFS1ZYC7YNH4ZcPSWSH5I+7zmXxBVTcrgHeFPNpkzEs734yqPmphnZETYE0QJuK f05udVBZFPVVuVRaLE/ZomzdreKY3Gf8keFSuxwx7j8hN6Vmn6DeJ+Cf+RDR5eaiLeoP 66l4FL0KBMVY3QHFN3QSvRTr1B3SBB960GHwWQrojrqes+8hFfAwCl8UVtHXMZ4//YR6 Z1X0SmXS1lcTVFZNKRj5sO3EpwWiFoxvD9C05VdcoD8swC0CbmSrooaf0Vu0xdct02oz 8l/w== 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=xlzKj3MAybW5ZSYqMhfgR9YJY63LFKPfYEik2iX5oXg=; b=SQK60NhaQWRUsNDx17qNvpxtxtPms2rU1rN34dq1h8XcVuil7E6KqKJS2D6kEiM72Y 01IWJz0O7ynr88lXjCRKsenwWGwtIzKWz1Izvh4q0JK0flxlwFqnCMupj9MuO+S+YTFq AjwpgJE7Nz5eBGT+N9t0G67M2uHAa915u9OtJK5xif4VSswn/9Ur2hCE83BIjMtAkB4T R9larqYttX0zNAvK60i4L2x7UdPefzKXA/EXI8rfHcLSTzZy2Pw5itKtk2A6Hg4DElZb wlSkz8j8TPgZZRDqUcWKW9Yvk6fOU7kLLdPZ58AM16+l+aX+/N1nU97KRvxqV7w6Kxdm 0q5g== X-Gm-Message-State: AKS2vOzAPAAq+Al2Uvkmr/xfQtOOAGWVzJ5eUliigiNzx/PPfOXk20fu TFD0MAu6p6+KtAGv5/27GoPXNiuJ3DhT X-Received: by 10.157.39.14 with SMTP id r14mr5445441ota.11.1496422098358; Fri, 02 Jun 2017 09:48:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.29.69 with HTTP; Fri, 2 Jun 2017 09:48:17 -0700 (PDT) In-Reply-To: <20170601235447.C98304@sola.nimnet.asn.au> References: <20170601235447.C98304@sola.nimnet.asn.au> From: Mehmet Erol Sanliturk Date: Fri, 2 Jun 2017 09:48:17 -0700 Message-ID: Subject: Re: Advice on kernel panics To: Ian Smith Cc: Raimo Niskanen , FreeBSD Questions Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 16:48:19 -0000 On Thu, Jun 1, 2017 at 7:34 AM, Ian Smith wrote: > In freebsd-questions Digest, Vol 678, Issue 4, Message: 4 > On Thu, 1 Jun 2017 10:27:49 +0200 Raimo Niskanen < > raimo+freebsd@erix.ericsson.se> wrote: > > On Thu, Jun 01, 2017 at 12:10:30AM -0500, Doug McIntyre wrote: > > > On Mon, May 29, 2017 at 11:20:43AM +0200, Raimo Niskanen wrote: > > > > I have a server that panics about every 3 days and need some advice > on how > > > > to handle that. > > > > > > I'd expect it is some sort of hardware failure, as I would expect > > > kernel panics more on the order of once a decade with FreeBSD. Ie. > > > I've seen one or two on my hundred or so servers, but its pretty rare. > > > > > > Check and recheck your hardware items. > > > > I have removed one of four memory capsules - panicked again. Will > rotate > > through all of them... > > > > > > > > Runup memtest86+. Check your drive hardware, turn on SMART checking. > > > > I have run memtest86+ over night - no errors found. > > > > I have installed smartmontools - no errors found, short and long self > tests > > on both disks run fine. zpool scrub repaired 0 errors and has no known > data > > errors. > > Everyone's suggesting hardware problems, and it's certainly worthwhile > eliminating that possibility - but this could be a software/OS issue. > > If it were me and hardware all checks out, I'd try posting the original > report - plus other details about the box and setup that you've since > mentioned - to freebsd-stable@, or maybe freebsd-fs@ since those fstat > reports seem to point to possible FS/zfs issues? at a wild guess .. > > One other hardware tester you might try is sysutils/stress which can > pound CPU, I/O, VM, disk as hard and for as long as you like, without > having to bring the box down. I've used this lots to generate heavy > loads. Keep a close eye on system temperatures during longer tests. > > Ah, just before posting, I see your latest with dmesg. Just on a quick > scan, I wonder if these are a bad indication? Maybe just a side-issue, > but powerd might not work, so again heat might be something to watch: > > est0: on cpu0 > est: CPU supports Enhanced Speedstep, but is not recognized. > > cheers, Ian > _______________________________________________ > > "Panics about every three days" may suggest another software problem : With respect to your executed programs , system resources , especially memory or OS data structures , may be allocated , but not freed properly without any warning message ( or message may be missed ) . When OS requires to do a process , but there is no a sufficient resource , a panic may be triggered ( without background reasons ) . To isolate this possibility , if ever is possible to find the panic point ( in the sense of a routine in a source file ) , it may show an important clue to proceed a more fruitful way to solve the problem . Mehmet Erol Sanliturk From owner-freebsd-questions@freebsd.org Fri Jun 2 17:28:51 2017 Return-Path: Delivered-To: freebsd-questions@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 34D81BFBC15 for ; Fri, 2 Jun 2017 17:28:51 +0000 (UTC) (envelope-from kudzu@tenebras.com) Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::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 E262C6E9D6 for ; Fri, 2 Jun 2017 17:28:50 +0000 (UTC) (envelope-from kudzu@tenebras.com) Received: by mail-qt0-x235.google.com with SMTP id f55so64285343qta.3 for ; Fri, 02 Jun 2017 10:28:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tenebras-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=l31ikBJsns4nZ2j7PiTwvqW+ysq49J5Lb861ZfnrGFY=; b=ayR8XdB8ypfVtKPSWopF/Qn33PE5KmvpgOznpDqOWchPuoPNdEP83sqX093fiUWsN4 +UVVmTYtpFr3NGhVdlI4Vc/7hCyiPr6LsiXanN6WCYkJccdTJxvzqQXm2J1mYeuoDu6X 9CWz6fes4jFeNaIVGM21qoOtVeH0aUPWSMjxUpxEBw5yiMHEkKpffR4/V/Nn6R+zd60o /dmAleHG47lHAQtFXzXtlAZmVrVM6DHelhsld3n7dDAL1/nsmoIRtVhQ/FtK3vrnPIus g+ppfZIPBtAkjD6GgOqPNUqFjN7y2ydWiaukGWGYoPH3HNC7LzoOqq0xgHMVfYq6JX63 Qgtg== 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=l31ikBJsns4nZ2j7PiTwvqW+ysq49J5Lb861ZfnrGFY=; b=USrHyOVXD8NyBV7m3LDGxiRYAvrny6aDPYKOdvPLIER4yA21QOVen3LJ5gbEjXgf8q NBQbjUgop5K+UOfikH9P/0m9EJBIFndzpWVhAmXqJBqOuNGQeLkAsuqeJhKW/svoWw8K oOVxe23sVhyxJKo4hhLkP3LVesWW0mjg3JSpzz3ZVT1OPPKdHY3jlBJaKJbMvYyVmSd1 uaqXAfFVlfgwVkwjGMP3rQekbz9Vap/QEmyvQIN2PnwwTqooboYsxUQGXG/R6UaYJ1FB z5tTrGo5+og7y1qLBbT62W6y+Yuyx/ad+K/ofNsismX9wn4addo/fh/OVTrZsdqZMwOC kpVg== X-Gm-Message-State: AODbwcCdv2SWU11gYsGRKH7cDf2Z3X4oRu+6z24SgqNcZrmbh/fUHLT2 dEEqvY0RH8V51rEZv28CxZYJb70Q+1oouSo= X-Received: by 10.237.62.229 with SMTP id o34mr9797705qtf.4.1496424529992; Fri, 02 Jun 2017 10:28:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.40.20 with HTTP; Fri, 2 Jun 2017 10:28:49 -0700 (PDT) In-Reply-To: References: From: Michael Sierchio Date: Fri, 2 Jun 2017 10:28:49 -0700 Message-ID: Subject: Re: Excluding File Systems from 100.chksetuid and 110.neggrpperm To: Tim Gustafson Cc: FreeBSD Questions Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 17:28:51 -0000 Move them to weekly? Renice them to very low priority? - M On Fri, Jun 2, 2017 at 9:31 AM, Tim Gustafson wrote: > Hi, > > We have several FreeBSD 10.x and 11.x servers that host about 150TB of > ZFS file systems each. > > Each day, the 100.chksetuid and 110.neggrpperm run against our entire > data set, which has hundreds of millions of files in it, and winds up > slowing everything down and using up all our resources. > > Looking at those scripts, they don't seem to take any parameters, and > I can't configure them to exclude certain folders that really just > don't need to be scanned. I did find this post which suggested a > patch for FreeBSD 9.x, but it does not appear to have even been > implemented: > > https://forums.freebsd.org/threads/31846/ > > Is there any hope of getting these options added? > > -- > > Tim Gustafson > BSOE Computing Director > tjg@ucsc.edu > 831-459-5354 > Baskin Engineering, Room 313A > > To request BSOE IT support, please visit https://support.soe.ucsc.edu/ > or send e-mail to help@soe.ucsc.edu. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org" > --=20 "Well," Brahma said, "even after ten thousand explanations, a fool is no wiser, but an intelligent person requires only two thousand five hundred." - The Mah=C4=81bh=C4=81rata From owner-freebsd-questions@freebsd.org Fri Jun 2 17:50:42 2017 Return-Path: Delivered-To: freebsd-questions@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 14245AF81F0 for ; Fri, 2 Jun 2017 17:50:42 +0000 (UTC) (envelope-from amvandemore@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 9CB7F6F74E for ; Fri, 2 Jun 2017 17:50:41 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id b84so31164131wmh.0 for ; Fri, 02 Jun 2017 10:50:41 -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=XdpO8GOcQeezYB5sWpAVhz286KcTcrne1tvGyBNowns=; b=Q5zi+IJo3CLU3wESioccY2jEyyARH5EF5uyLnUlBZajQZZikD2id3kJuFpBDCfnyF7 VzXlmZNiR6gBjGbgZ/PIkhGAIcdddronBMj+X9eMD4uvdg7jJ7BNUKwVKNDp1FiWzewx Skx+fEcK4kiFEP9mot7dG0AnmjYu6K7r7pRRe9ItwZgZ0t/WUbxOBSPKn5ZnCrXnkbga q8GhzO+A7LBWQaT7v95B+tNGGGSldilpY+Zat8lUdrGWSjKODAwVKvfGlBl9jckLLYXS brhcNwXxKREXYZ+kmbSx2FNDQ8Kq1hZp49d0OTMGXb9RLMtz0efy4pNy8Eojbxq/PY6N A38g== 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=XdpO8GOcQeezYB5sWpAVhz286KcTcrne1tvGyBNowns=; b=Ft2RYNXPbnVBzyx1469hG8giFys4LWS7tBB2BsG3Kbee7ocU5+vu5pogL+PQs/SEGo DUOMUSOmkLgUCOMKNQnS58f5J4ZKy3kLE1F6l+tx+OWVre24IFRxu1GwU/JTeNZx3MCk 4/IsKWURmkcAfptmH74gh/14hW5O6FBZFhTKF+/qIQCoLXkdvJtfu8EnOEH1gzF1bCln dpn7ymAnYkI25tfJ1aydwIQGSjNZmvctD0S27DPdvUoyaoMdaw106rxTx25Xg/FbAVP3 ohF483pMDnmJoOF6fIa/UDxawnrldQx0XCI1O8e6hz4QSr6fkh27Ua/y8JzHYcYzd4dA 3bfA== X-Gm-Message-State: AODbwcDogOcIhaPSmXSXgDbEmjOKmTqC5uvHM30eZZI3nv/igBYav0n6 dQFV/fd/ZzVmfWs5yjpkG3RK82EgKMyU X-Received: by 10.80.144.200 with SMTP id d8mr6749388eda.162.1496425840279; Fri, 02 Jun 2017 10:50:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.175.65 with HTTP; Fri, 2 Jun 2017 10:50:39 -0700 (PDT) In-Reply-To: References: From: Adam Vande More Date: Fri, 2 Jun 2017 12:50:39 -0500 Message-ID: Subject: Re: Excluding File Systems from 100.chksetuid and 110.neggrpperm To: Tim Gustafson Cc: FreeBSD Questions Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 17:50:42 -0000 On Fri, Jun 2, 2017 at 11:31 AM, Tim Gustafson wrote: > Hi, > > We have several FreeBSD 10.x and 11.x servers that host about 150TB of > ZFS file systems each. > > Each day, the 100.chksetuid and 110.neggrpperm run against our entire > data set, which has hundreds of millions of files in it, and winds up > slowing everything down and using up all our resources. > > Looking at those scripts, they don't seem to take any parameters, and > I can't configure them to exclude certain folders that really just > don't need to be scanned. I did find this post which suggested a > patch for FreeBSD 9.x, but it does not appear to have even been > implemented: > > https://forums.freebsd.org/threads/31846/ > > Is there any hope of getting these options added? > That thread mentions this posting which contains responses as to why it likely was never pursued further: https://docs.freebsd.org/cgi/getmsg.cgi?fetch=275969+0+/usr/local/www/mailindex/archive/2012/freebsd-stable/20120506.freebsd-stable -- Adam From owner-freebsd-questions@freebsd.org Fri Jun 2 17:59:22 2017 Return-Path: Delivered-To: freebsd-questions@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 053F6AF8457 for ; Fri, 2 Jun 2017 17:59:22 +0000 (UTC) (envelope-from demis@yandex.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E0BCD6FC2D for ; Fri, 2 Jun 2017 17:59:21 +0000 (UTC) (envelope-from demis@yandex.ru) Received: by mailman.ysv.freebsd.org (Postfix) id DCC3AAF8456; Fri, 2 Jun 2017 17:59:21 +0000 (UTC) Delivered-To: questions@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 DC245AF8455 for ; Fri, 2 Jun 2017 17:59:21 +0000 (UTC) (envelope-from demis@yandex.ru) Received: from forward14p.cmail.yandex.net (forward14p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::be]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8104A6FC2C for ; Fri, 2 Jun 2017 17:59:21 +0000 (UTC) (envelope-from demis@yandex.ru) Received: from mxback14j.mail.yandex.net (mxback14j.mail.yandex.net [IPv6:2a02:6b8:0:1619::90]) by forward14p.cmail.yandex.net (Yandex) with ESMTP id 672B721A58 for ; Fri, 2 Jun 2017 20:59:09 +0300 (MSK) Received: from web25j.yandex.ru (web25j.yandex.ru [5.45.198.66]) by mxback14j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id C5HZNpPFX6-x85OqrY9; Fri, 02 Jun 2017 20:59:08 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1496426348; bh=ucU98U1bCGAOdk4wa6g2a9cIgmORgaNbx4Q2VPCFQOk=; h=From:To:Subject:Message-Id:Date; b=FdMmUXu7UZJGEHyJMOSBXol12HmlA7tojuuElNM6nKMSrBAfOcp0Ljx+wslC0T3aW 8JbVmjMkrFv7OkK2j28TRe49Yp10n9KQXOn1Ww3pBDhgg9/VxLjd1UUjjVwFCsAnaq Sw3W1mNwg3l5enItAIzM97lIfUARSjLxfFvtOFwA= Authentication-Results: mxback14j.mail.yandex.net; dkim=pass header.i=@yandex.ru Received: by web25j.yandex.ru with HTTP; Fri, 02 Jun 2017 20:59:08 +0300 From: DemIS To: questions@freebsd.org Subject: Resetup FreeBSD 11.0 amd64 killing system boot. MIME-Version: 1.0 Message-Id: <3908861496426348@web25j.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Fri, 02 Jun 2017 20:59:08 +0300 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 17:59:22 -0000 Sorry for my English. Can someone check? Resetup FreeBSD 11.0 amd64 killing system boot. How to reproduce? The description is long. The source data: 1. Physical computer Dell OptiPlex 790 bios A18 RAM 4Gb, internal video, hdd 80GB 2,5" 2. FreeBSD-11.0-RELEASE-amd64-disc1.iso 3. Boot type in BIOS "Legacy" (not UEFI) 4. Network adapter is connect to lan and Internet 5. The virtual machine has not been tested Make setup on factory clean hdd. boot from CD install keymap selection set hosname distribution select add doc add src Partitioning Manual Create Select GPT Create -> freebsd-boot 64KB Create -> freebsd-ufs 4GB / (uncheck journal in options) Create -> freebsd-swap 4GB Create -> freebsd-ufs 16GB /var (uncheck journal in options) Create -> freebsd-ufs 40GB /usr (uncheck journal in options) (Not all space) Finish Commit Wait to end setup. (set root pass, network, time zone,date,time, ntpd) System hardening select all but NOT selected only "randomize the PID" and "disable sendmail" Adding one user witch invate "wheel" Reboot. Remove CD. logon as root. Ok. Good. It's working ================= Next step. I want reconfigure my setup. Reboot. Load again from CD ================= install keymap selection set hosname distribution select add doc add src Partitioning Manual See old partition, delete all, no touch GPT sheme. select freebsd-ufs 40GB /usr -> delete select freebsd-ufs 16GB /var -> delete select freebsd-swap 4GB -> delete select freebsd-ufs 4GB / -> delete select freebsd-boot 64KB -> delete Create -> freebsd-boot 64KB Create -> freebsd-ufs 3GB / (uncheck journal in options) Create -> freebsd-swap 3GB (auto recalc to 2Gb) Create -> freebsd-ufs 15GB /var (auto recalc to 13Gb) (uncheck journal in options) Create -> freebsd-ufs 30GB /usr (auto recalc to 27Gb) (uncheck journal in options) (Not all space) Finish Commit Wait to end setup. (set root pass, network, time zone,date,time, ntpd) System hardening select all but NOT selected only "randomize the PID" and "disable sendmail" Adding one user witch invate "wheel" Reboot. Remove CD. Fail boot. Get messages: Starting file system checks: /dev/ada0p2: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ada0p2: clean, 724414 free (342 frags, 90509 blocks, 0.0% fragmentation) Cannot find file system super block Cannot find file system super block Cannot find file system super block Cannot find file system super block THE FOLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENCY: ufs: /dev/ada0p4 (/var), ufs: /dev/ada0p5 (/usr) Warning! Some of the devices might not be available : retrying Waiting 30s for the root mount holders: usbus1 usbus0 ... (white message from usb, keyboard, etc (no errors) ... Restarting file system checks: /dev/ada0p2: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ada0p2: clean, 724414 free (342 frags, 90509 blocks, 0.0% fragmentation) Cannot find file system super block Cannot find file system super block Cannot find file system super block Cannot find file system super block THE FOLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENCY: ufs: /dev/ada0p4 (/var), ufs: /dev/ada0p5 (/usr) Unknown error 3: help! ERRROR: ABORTING BOOT (sending GIGTERM to parent)! [date] [time] init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: Cannot read termcap database: using dumb terminal settings. # THE END For get next good setup use "gdisk 2 /wipedisk" from Norton utilities to clean disk. What's wrong? It's normaly? Demis From owner-freebsd-questions@freebsd.org Fri Jun 2 19:33:37 2017 Return-Path: Delivered-To: freebsd-questions@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 3D495AFA1F2 for ; Fri, 2 Jun 2017 19:33:37 +0000 (UTC) (envelope-from tjg@ucsc.edu) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::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 BA5D274B8D for ; Fri, 2 Jun 2017 19:33:36 +0000 (UTC) (envelope-from tjg@ucsc.edu) Received: by mail-lf0-x22d.google.com with SMTP id h4so48113788lfj.3 for ; Fri, 02 Jun 2017 12:33:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/hG+iAF6EWmh8CwFN1GB4Fz3+U2LyMWWpUVzHyDKDgc=; b=GldTBWDFPyfzEayRYvT0prBzLUctqOZqLaVNRZxwX+yeXqmUKtm7ddNMRku56TuTlt wxy1FwTgu10CJGWDGkDnDF1DCdIhu7JtnEl4pqgJoGfB2pT8ZVS5ecDYuZVVGqAxsjPO VmGn2Y3RDW9bIQZ5Mcevy/KNc9lTfwFyfu7wg= 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=/hG+iAF6EWmh8CwFN1GB4Fz3+U2LyMWWpUVzHyDKDgc=; b=h/BL2iSUwdUC31Va+QiQWB5XatjJvrvEU1P+e/aLIxCvFLbAJFKbEtInpvJL5hI5rd O6K9TW4mY8eYegBFSKInzjBVfZTxTiFN4iL/0KFYAhU2vPe5VfkbBF4XvFDAfp7l2AwQ 15R/J5ZaYxi5sQwU6fF1J9boaB9sHFiycBAaB+BlDEY8hx3Eh7MmvlnRl3kwzV4tH6Pi azgKYSNCVAMBgXfhJeLPzd3GofqJI9CF8vflMpHb3+mU/ytKKb3rbSH5Mid2MJwMmFYf ZGo1hW/QF5wWf7yDp+/4fdZr3Arecix+dvcyNXjezmRM4cBNY3SI36BK1YEjjU7kAMFj SM4w== X-Gm-Message-State: AODbwcBDhhOUU8jpI0b7URs9xSqHkDNULGr26K0LJ9xy6txLbsxFlS0U MtDH8UylFSkJtcfk9UCnkKdMnZuDCLH8 X-Received: by 10.46.81.89 with SMTP id b25mr2777810lje.33.1496432014904; Fri, 02 Jun 2017 12:33:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.16.31 with HTTP; Fri, 2 Jun 2017 12:33:34 -0700 (PDT) In-Reply-To: References: From: Tim Gustafson Date: Fri, 2 Jun 2017 12:33:34 -0700 Message-ID: Subject: Re: Excluding File Systems from 100.chksetuid and 110.neggrpperm To: Adam Vande More Cc: FreeBSD Questions Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 19:33:37 -0000 >> https://forums.freebsd.org/threads/31846/ > That thread mentions this posting which contains responses as to why it > likely was never pursued further: > > https://docs.freebsd.org/cgi/getmsg.cgi?fetch=275969+0+/usr/local/www/mailindex/archive/2012/freebsd-stable/20120506.freebsd-stable Sorry, I think I'm missing something. I don't see anything in that thread that suggests why it wouldn't be implemented. There's some chatter about not excluding all ZFS filesystems, but I'm not asking about that. I'm asking about excluding individual filesystems. In the original post I shared, the suggested patch included the ability to exclude by mount point, rather than by file system type. My desired settings would be: daily_status_security_chksetuid_fs_ignore="/export" daily_status_security_neggrpperm_fs_ignore="/export" As these are just NFS servers, users never log into them and can't run processes on them. I could mount them locally with nosuid and noexec but then it's not clear to me how that would affect NFS clients that mount these file systems, but I think setting nosuid and noexec on the server wouldn't have any effect on the NFS clients. Also, there are certainly legitimate suid and non-suid binaries in those file systems that need to be run on the clients that mount them. I suppose if these processes should really run for security purposes, it would be better to have them run on a particular day. For example, having them start late on Friday night or very early Saturday morning would avoid our heaviest workload periods. But that also seems to not be an option, unless there is something fancy I can do in periodic.conf that's not immediately apparent to me, or by hacking files in /etc/periodic, which I'd rather not do if I can avoid it. -- Tim Gustafson BSOE Computing Director tjg@ucsc.edu 831-459-5354 Baskin Engineering, Room 313A To request BSOE IT support, please visit https://support.soe.ucsc.edu/ or send e-mail to help@soe.ucsc.edu. From owner-freebsd-questions@freebsd.org Fri Jun 2 19:46:21 2017 Return-Path: Delivered-To: freebsd-questions@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 4E71FAFA57D for ; Fri, 2 Jun 2017 19:46:21 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 08399752C9 for ; Fri, 2 Jun 2017 19:46:20 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id 1128062082 for ; Fri, 2 Jun 2017 15:46:19 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id piivQ8utu4KW for ; Fri, 2 Jun 2017 15:46:17 -0400 (EDT) Received: from inet07.hamilton.harte-lyne.ca (inet07.hamilton.harte-lyne.ca [216.185.71.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "imap.hamilton.harte-lyne.ca", Issuer "CA HLL ISSUER 01" (not verified)) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPS for ; Fri, 2 Jun 2017 15:46:17 -0400 (EDT) Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca [216.185.71.28]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "inet08.hamilton.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (verified OK)) by inet07.hamilton.harte-lyne.ca (Postfix) with ESMTPS id CD6788A541 for ; Fri, 2 Jun 2017 15:46:16 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id B0EF862087 for ; Fri, 2 Jun 2017 15:46:16 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1]) by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hmgTK8zuCsCC; Fri, 2 Jun 2017 15:46:15 -0400 (EDT) Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca [216.185.71.24]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPSA id 7BD7C62082; Fri, 2 Jun 2017 15:46:14 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=harte-lyne.ca; s=dkim_hll; t=1496432774; bh=V6xWQshznb5J3xWEsv8SuyYGBT+lbmBO3H3jUodDII0=; h=In-Reply-To:References:Date:Subject:From:To:Cc:Reply-To; b=arr2vh+Dg0B56tJCMh2eYZtkD3cXNtaLthoiHv+oQciWHrg6zaahklv6KSm+xD+Hx HwneMTh7gnP73oKMv9Zh/+HzKnbRIRHtyxOZl6isecnDj4TIP9gG6UXhJDqd+R9VdX XmzrYK5KLKeoR59dKm3b/eCy3PH2J93JqK2xvQB1km+GjwhDwbShZpQHTg7d6KA5Bo 7zAr2ZV8GJ6qEAQzteNVbw83tc+sdmmnFFaFJyF2CSGaH1bSlIRAJDmYp/WpnQ4d9+ pZHSHWCYN2y8Z7qWxBijlviggiL55n+iJ8UqJ8y8RBuBerjVKjift1bb3OP5uDsq8X IXFyfnjjS+1ig== Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Fri, 2 Jun 2017 15:46:14 -0400 Message-ID: In-Reply-To: <691d853e-e2f7-b5f3-d281-73511845bd6a@radel.com> References: <74b7b58aa45cc01585338ef2270ccc57.squirrel@webmail.harte-lyne.ca> <691d853e-e2f7-b5f3-d281-73511845bd6a@radel.com> Date: Fri, 2 Jun 2017 15:46:14 -0400 Subject: Re: IPv4 to IPv6 From: "James B. Byrne" To: "Jon Radel" Cc: freebsd-questions@harte-lyne.ca Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.22-4.el6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 19:46:21 -0000 On Fri, June 2, 2017 11:43, Jon Radel wrote: > Do you really plan to remove IPv4 from everything other than your SMTP > and DNS servers? If so, how will your users [assuming you have such] > reach resources on the IPv4 Internet? Or have I misunderstood? > > An orderly migration to being dual-stacked on everything would > probably be a lot less painful than what I think you're planning. > While there are possible mechanisms for an IPv6-only client to > reach resources on the IPv4 Internet, I'm unclear on the benefits > of bothering with such an architecture. > We will be running dual stack for a while, possibly into the next century. Internally we will move to IPv6 as equipment is replaced or reconfigured. There seems little point in disturbing that which already works. Externally, the first services to be IPv6 enabled will be DNS followed closely by SMTP. Then we will start looking at SSH and VPN. Finally, we will enable HTTP services on IPv6. It still strikes me as odd that the ITEF managed to come up with a replacement addressing scheme that is not zero configuration compatible with the existing IPv4 one. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 From owner-freebsd-questions@freebsd.org Sat Jun 3 04:04:16 2017 Return-Path: Delivered-To: freebsd-questions@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 228D1B7ECF0 for ; Sat, 3 Jun 2017 04:04:16 +0000 (UTC) (envelope-from mason@blisses.org) Received: from phlegethon.blisses.org (phlegethon.blisses.org [50.56.97.101]) (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 07E2C82FD6 for ; Sat, 3 Jun 2017 04:04:15 +0000 (UTC) (envelope-from mason@blisses.org) Received: from blisses.org (cocytus.blisses.org [64.223.129.151]) by phlegethon.blisses.org (Postfix) with ESMTPSA id E216374004 for ; Sat, 3 Jun 2017 00:04:13 -0400 (EDT) Date: Sat, 3 Jun 2017 00:04:12 -0400 From: Mason Loring Bliss To: freebsd-questions@freebsd.org Subject: Linuxulator / Chrome Message-ID: <20170603040412.GA8701@blisses.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jun 2017 04:04:16 -0000 --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all. Will Chrome work on Linuxulator if I chase down enough dependencies? I'm trying to get BlueJeans running, and it's balking in both Firefox and Chromium on FreeBSD (11-STABLE) so I figured I'd give Chrome under the Linuxulator a try. I hit several missing libraries until I realized I needed to install the whole linux-c6 (also tried linux-c7) suite. Once that was done, I hit this: ./chrome: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory We don't seem to have a package for it. I tried running ldd to see what other libraries I'd need, but the ldd in /compat bailed out, saying "missing file". I suspect it's not intended to be used, as it has /bin/bash in the shebang line. The native LDD was unhappy with the Chrome binary. I've now pulled out a list of libraries from a Linux machine where I could run ldd, and I can collect the libraries by hand from Linux to populate /compat, but I'm really interested in knowing if anyone's gotten Chrome working this way, or if I'll run into known obstacles once I have all the libraries in place. Thanks! --=20 Mason Loring Bliss mason@blisses.org Ewige Blumenkra= ft! (if awake 'sleep (aref #(sleep dream) (random 2))) -- Hamlet, Act III, Scen= e I --h31gzZEtNLTqOjlF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJZMjU8AAoJEJ6yV3B27yVV7cAP/j0Nd5rZDsBJkN9T7LAp+cl9 /p4fR+z2Wv0oB95QTxrlPG3o5A8ZDpAAuwqLv0HML/MCJHW+XQwpsN6pM1Q+pxRJ UViTwHSkWDftYyvrrlEBPNdbGMgyHUXECHQ0sRJJ5c5Ps059kKpmDeyFE8K94XGc WzVhzYvqQgK1II7NrSJf7qDg9QR8oafCcb4jYew2J3YSrj2cyItYCE7HtIWTQFFe xFZIVkxSdS+EkCCbxkLMXLZnHHO3kRZ0Oje/0P+ttWQYbrbjeh/rhq2irB1aUfab oqVbxIIAPgDhhABY+MU2bWTEISRiwz75yrnBluM8xUNcEFPY2cKtb5I1JdVporSP tflWtdi1Jc4VM0aLIbEpRRridzHUxcOLTeQR7IBEZS8Zs6iCBg6hpLhRAwnOrswo rIuAIxmeyDvzmOYkZVPsgOla2epJ5sm8wD7Ep0jRlpdbJW91ngJhzksPRWu5agVd m5Il5SXWTUimPoEqgmbwhghYX7cyZEsbHiK7z81XiNev9d9/79eKZFMQOKV89KHW Vz4MqG1i+jpG3ZQUkbHTwcqrpQmetb2jC/a9W0zb7UAZUW6ap8XpZkW51sQoAmba 3LI/BXK13gJIFHg7/qcgIm3v7n0wyxS6NYf385X0hk8Tq7anIe7H1fnYy1WlGT30 0Pieq5N2HHOv1uJqSCK/ =EamG -----END PGP SIGNATURE----- --h31gzZEtNLTqOjlF--