Bug 224017 - security/py-certbot: "Another instance of Certbot is already running."
Summary: security/py-certbot: "Another instance of Certbot is already running."
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Kubilay Kocak
Keywords: needs-qa
Depends on:
Reported: 2017-12-01 13:29 UTC by Gerard Seibert
Modified: 2020-05-18 09:25 UTC (History)
1 user (show)

See Also:
koobs: maintainer-feedback+


Note You need to log in before you can comment on or make changes to this bug.
Description Gerard Seibert 2017-12-01 13:29:24 UTC
~ $ uname -a
FreeBSD scorpio.seibercom.net 11.1-RELEASE-p4 FreeBSD 11.1-RELEASE-p4 #0: Tue Nov 14 06:12:40 UTC 2017     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

~ $ freebsd-version



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 have confirmed that at least one other user is experiencing this problem. He stated that the problem does not occur if the command is only run via the command line. He believes that certbot is waiting on the post-hook command, but only when it was ran from cron. I have not confirmed this, however.
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2020-05-18 02:05:08 UTC
@Gerard Is this still an issue with an up to date ports tree / package repository and certbot version?
Comment 2 Gerard Seibert 2020-05-18 09:14:49 UTC
(In reply to Kubilay Kocak from comment #1)

I had forgotten about this PR. It is 3 years old. I any case, I believe the problem has been taken care of. This PR can be closed.