From owner-freebsd-stable@freebsd.org Sun Mar 18 16:33:24 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F2CAF615C8 for ; Sun, 18 Mar 2018 16:33:24 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BAD9579E08 for ; Sun, 18 Mar 2018 16:33:23 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from [192.168.243.11] ([192.168.243.11]) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTP id w2IGXJeC061230 for ; Sun, 18 Mar 2018 21:33:19 +0500 (YEKT) (envelope-from emz@norma.perm.ru) To: freebsd-stable@freebsd.org From: "Eugene M. Zheganin" Subject: HAST, configuration, this actually looks insane Message-ID: Date: Sun, 18 Mar 2018 21:33:20 +0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Language: ru Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 16:33:24 -0000 Hi, I'm trying to configure a HAST on FreeBSD, and suddenly it appears to be a mind-breaking procedure. I totally don't get it, thus it doesn't work, dumps cores and behaves weirdly. First of all, in an existing configuration files paradigm, used widely in the whole IT industry, the local view is usually described, and then remote mentioned. Here both local and remote views are described and the configuration file (and they aren't named explicitely local and remote since they are both "remote"), like I understand the handbook article, must be _the_same_ on both nodes. So, given that the sections are named arbitrarily, the local hostname isn't mentioned or linked anywhere - how do I configure it considering that I have _different_ GEOM providers of different machines ? So, let's consider I have written this configutaion file: resource hasta {     on gw0 { local /dev/ada2p3 remote 192.168.0.247     }     on gw1 { local /dev/ada0p4 remote 192.168.0.248     } } resource hastb {     on gw0 { local /dev/ada3p3 remote 192.168.0.247     }     on gw1 {              local /dev/ada1p4 remote 192.168.0.248     } } The main question which IP do I mention where ? As far as I understand I should mention "remote" IP in the "local" device block, and vice-versa, but first of all - this doesn't work (dumps cores, complains bout FIFOs, and so on ) - second of all - how the hastd itself finds who's local and who's remote ? Thank god I have a GEOM configuration which cannot be applied on both nodes, so only the correct node wouyld have the GEOM provider mentions - otherwise I suggest this would corrupt my data and make a total mess of it. With thsi configuration file hastd doesn't work. "create" stage goes smoothly, but then on one node (the one with /dev/ada1p4 and /dev/ada0p4) hastd just loops crashing: Mar 18 20:48:47 gw1 hastd[92215]: [hasta] (primary) Descriptor 7 is open (pipe or FIFO), but should be closed. Mar 18 20:48:47 gw1 hastd[92215]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Mar 18 20:48:47 gw1 kernel: pid 92215 (hastd), uid 0: exited on signal 6 (core dumped) Mar 18 20:48:52 gw1 hastd[92204]: [hasta] (primary) Worker process killed (pid=92215, signal=6). Mar 18 20:48:53 gw1 hastd[92222]: [hasta] (primary) Descriptor 7 is open (pipe or FIFO), but should be closed. Mar 18 20:48:53 gw1 hastd[92222]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Mar 18 20:48:53 gw1 kernel: pid 92222 (hastd), uid 0: exited on signal 6 (core dumped) Mar 18 20:48:58 gw1 hastd[92204]: [hasta] (primary) Worker process killed (pid=92222, signal=6). Mar 18 20:48:59 gw1 hastd[92223]: [hasta] (primary) Descriptor 7 is open (pipe or FIFO), but should be closed. Mar 18 20:48:59 gw1 hastd[92223]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Mar 18 20:48:59 gw1 kernel: pid 92223 (hastd), uid 0: exited on signal 6 (core dumped) Mar 18 20:49:01 gw1 hastd[92204]: [hasta] (primary) Worker process killed (pid=92223, signal=6). Mar 18 20:49:02 gw1 hastd[92225]: [hasta] (primary) Descriptor 7 is open (pipe or FIFO), but should be closed. Mar 18 20:49:02 gw1 hastd[92225]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Mar 18 20:49:02 gw1 hastd[92204]: Unable to receive control header: Socket is not connected. Mar 18 20:49:02 gw1 kernel: pid 92225 (hastd), uid 0: exited on signal 6 (core dumped) Mar 18 20:49:02 gw1 hastd[92204]: Unable to send control response: Broken pipe. Mar 18 20:49:07 gw1 hastd[92204]: [hasta] (primary) Worker process killed (pid=92225, signal=6). Mar 18 20:49:08 gw1 hastd[92230]: [hasta] (primary) Descriptor 7 is open (pipe or FIFO), but should be closed. Mar 18 20:49:08 gw1 hastd[92230]: [hasta] (primary) Aborted at function descriptors_assert, file /usr/src/sbin/hastd/hastd.c, line 303. Mar 18 20:49:08 gw1 kernel: pid 92230 (hastd), uid 0: exited on signal 6 (core dumped) Thanks. Eugene.