From owner-freebsd-questions@freebsd.org Fri Dec 1 12:04: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 6988DDFEB2B; Fri, 1 Dec 2017 12:04:48 +0000 (UTC) (envelope-from marek@mky.waw.pl) Received: from poczta.mky.waw.pl (poczta.mky.waw.pl [IPv6:2001:41d0:604:159::25]) (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 2F4C17F2DE; Fri, 1 Dec 2017 12:04:48 +0000 (UTC) (envelope-from marek@mky.waw.pl) Received: from poczta.mky.waw.pl (localhost [193.70.126.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by poczta.mky.waw.pl (Postfix) with ESMTPSA id 20483434FB2; Fri, 1 Dec 2017 13:04:36 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Fri, 01 Dec 2017 13:04:36 +0100 From: Marek Krawczyk To: FreeBSD Cc: "koobs@FreeBSD.org" , owner-freebsd-questions@freebsd.org, Carmel NY Subject: Re: PROBLEM: Another instance of Certbot is already running. In-Reply-To: References: Message-ID: <553fa03e7865a31ac5cf789c7e537a1d@mky.waw.pl> X-Sender: marek@mky.waw.pl User-Agent: Roundcube Webmail/1.3.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 12:04:48 -0000 Hi! W dniu 2017-12-01 12:27, Carmel NY napisaƂ(a): > FreeBSD 11.1 RELEASE-p5 > > I have been using the p5-certbot port without a problem until > recently. It is being run via cron: /usr/local/bin/certbot -q renew > --pre-hook "service dovecot stop" --post-hook "service dovecot start". > Until recently that worked fine. Now I have started receiving this > error message: "Another instance of Certbot is already running." Try > as I might, I cannot find another instance of "certbot" running. > > Apparently, the only way to correct the problem is to reboot the > system. This only works until after the cron command has run one time, > after which the problem resurfaces. I am hoping that someone might > have a suggestion. I have the same issue with dovecot. The certbot is waiting on the post-hook command, but only when it was ran from cron. If it is running from the shell, the dovecot is restarted properly. Unfortunatelly I did not found solution for this but I can also confirm that the issue exist. Regards, Marek