From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00, T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 12E6E1F4D7; Tue, 3 May 2022 20:32:25 +0000 (UTC) Date: Tue, 3 May 2022 20:32:24 +0000 From: Eric Wong To: Konstantin Ryabitsev Cc: Filipe Manana , meta@public-inbox.org Subject: Re: Trouble running lei Message-ID: <20220503203224.M963575@dcvr> References: <20220503113709.GA6803@dcvr> <20220503152405.xu6bluflfow3yehg@nitro.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20220503152405.xu6bluflfow3yehg@nitro.local> List-Id: Konstantin Ryabitsev wrote: > On Tue, May 03, 2022 at 01:50:52PM +0100, Filipe Manana wrote: > > > Perhaps it's already running lei-daemon as an older version? > > > "lei daemon-kill" should kill it and it'll restart on the next > > > command, unless something else got wedged. > > > > Ah, running "lei daemon-kill" fixed it. > > I don't know if I did something wrong before, but after running that, > > lei is now working fine. Good to know! > I think this is actually a common occurrence. Any way lei-daemon can recognize > when there's a version mismatch between itself and the binary talking to it? Sorta, but even I manage to lose track of which commits cause protocol or internal API changes since everything is lazy-loaded. I think the best way would be to have inotify/kqueue watch the /PublicInbox/ directory and auto-restart iff no active commands are running...