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: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id BA1E01F4D7 for ; Tue, 3 May 2022 15:24:08 +0000 (UTC) Received: by mail-pg1-x531.google.com with SMTP id 202so4017733pgc.9 for ; Tue, 03 May 2022 08:24:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=Qyv4APKFRr/lg7bmWUlLgrMVZc1sikCs9ZQbujdZXJs=; b=MMC8ENvAhRZHvXxzcjaL4ZzMDVb+kzD1OR6FlWX0dEp1b1eRIocqXPDD4KuttTTSQ5 YXWd7GYniZPw0gVz+VZYp0viC+LE2zLMAxcXLrIKHS5egkGYtjASr9kFveT1aZLEkkMy SmRqjI7q5H/xqjgCYvodUns2Ka+oefnZIugOw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=Qyv4APKFRr/lg7bmWUlLgrMVZc1sikCs9ZQbujdZXJs=; b=VW/qwg0HsSHkrS+/CI9TRelqthP6nviXSIQg/XaXA8niurgj6hpKp8zcpVutH+xd9C aQWnyiea0niSnJScZqQJukwnv2j5dqWTqds+HUBm2VC0g2z2wV/J8TK5WExrtilVq9w8 l08EliViVZLs4xEpGlqZRcdIOSUwBNzzQA/mZuuT+ntvFz0Y/4W9Q+282MA0STQ6BOpD FQgkvU44UfN0438/c1rruEtX2+xp8wNqsK/Dvf6tDg6YST4MEDszgNFbiieMjy3/ioc5 fsKb/qqt4FaBrmfFLKY079Caa5SZ5Fqv+zzk9nm849D+i/MaPgnn2dWuCTdsSjurh/69 xIbw== X-Gm-Message-State: AOAM533IQ8qtvT4Ywonh5d4oJo715yWvwlfFPELutm2OIpZTxacJKmvf 3wDx6/FDfT+JgO6mNQBHY1cpHQ== X-Google-Smtp-Source: ABdhPJz4jrqxhY255ye3a87KvTfyGTXp9+tJ9LDSgkdbqaAiZYtr3Fs9hPUvFUnmdeMRT5XDBqhZSg== X-Received: by 2002:a63:5b49:0:b0:39d:261c:b416 with SMTP id l9-20020a635b49000000b0039d261cb416mr14202237pgm.61.1651591447761; Tue, 03 May 2022 08:24:07 -0700 (PDT) Received: from nitro.local (wsip-70-166-189-147.ph.ph.cox.net. [70.166.189.147]) by smtp.gmail.com with ESMTPSA id j24-20020aa79298000000b0050dc7628164sm6446260pfa.62.2022.05.03.08.24.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 03 May 2022 08:24:07 -0700 (PDT) Date: Tue, 3 May 2022 11:24:05 -0400 From: Konstantin Ryabitsev To: Filipe Manana Cc: Eric Wong , meta@public-inbox.org Subject: Re: Trouble running lei Message-ID: <20220503152405.xu6bluflfow3yehg@nitro.local> References: <20220503113709.GA6803@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: List-Id: 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. 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? Regards, -K'