From owner-freebsd-hackers@freebsd.org Mon Feb 1 19:04:21 2016 Return-Path: Delivered-To: freebsd-hackers@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 3C14BA97577 for ; Mon, 1 Feb 2016 19:04:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A8FCA8A7 for ; Mon, 1 Feb 2016 19:04:20 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u11J4FeO032423 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 1 Feb 2016 21:04:16 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u11J4FeO032423 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u11J4FPm032422; Mon, 1 Feb 2016 21:04:15 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 1 Feb 2016 21:04:15 +0200 From: Konstantin Belousov To: Jov Cc: freebsd-hackers@freebsd.org Subject: Re: Fwd: [BUGS] BUG #13900: stop standby failed with writer process hang(happen 3 times in 2 days) Message-ID: <20160201190415.GO91220@kib.kiev.ua> References: <20160130071346.31022.37189@wrigleys.postgresql.org> <20160131162929.GI91220@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2016 19:04:21 -0000 On Mon, Feb 01, 2016 at 10:07:18AM +0800, Jov wrote: > Thanks Belousov! this is the output: > root@fb:~ # ps axlHww | grep 979 > 1001 979 1 0 4 0 196940 8236 - Ds - 0:06.03 > postgres: writer process (postgres) > 0 48614 48587 0 20 0 18824 2252 piperd S+ 0 0:00.00 > grep 979 > > > I use PostgreSQL on FreeBSD more than 3 years and this is the first time I > have problems. > I am suspicious of this problem related with the harden of the security of > the FreeBSD, I add these entry to all of my server aouble one month ago: I doubt that this is related. The problem you reported is somewhat known, I am not sure about the state of it on stable/9. There were some fixes on HEAD and stable/10, there were many attempts of changes. I currently believe that it is mostly fixed, and ony pending fix is a minor patch I provided for several people. But this is only for HEAD and 10. > > security.bsd.see_other_uids=0 > security.bsd.see_other_gids=0 > security.bsd.unprivileged_read_msgbuf=0 > security.bsd.unprivileged_proc_debug=0 > security.bsd.hardlink_check_uid=1 > security.bsd.hardlink_check_gid=1 > security.bsd.stack_guard_page=1 This setting would do nothing for you. > security.bsd.unprivileged_mlock=0 And this one causes less 'security' since programs like gpg no longer can allocate non-swappable memory for sensitive data without setuid.