CERTMONGER(1)
β¨ NAME β¨
getcert β bestie, this is the certmonger(1) corner of the manual, and we're forcing certmonger to go check on stuff right now π
π¦ SYNOPSIS π¦
getcert refresh [options]
π DESCRIPTION π
okay so, this literally forces certmonger to immediately go check on the status of an enrollment request. which requests? the ones where it either couldn't reach the CA at all, or the ones where it's just sitting there waiting on the CA like π. no cap, it's the "hey. hey bestie. go look again" command.
π SPECIFYING REQUESTS BY NICKNAME π
-i NAME,--id=NAMEβ check on the status of the signing request that has this nickname. If you don't pass this option, and a tracking entry that matches the certificate storage options you did specify already exists, then that entry gets used instead. And if you still haven't specified anything? then you gotta point at where the certificate lives, either with a combo of-dand-n, or with-f. iykyk πΈ
π SPECIFYINGIDIR,E--dbdir=DIRIFICATE LOCATION π
(this heading is iconic and we are NOT touching it, it's part of the lore π)
-dβ the certificate lives in the NSS database in the directory you specify.-n NAME,--nickname=NAMEβ the certificate in the NSS database named with-dhas this nickname. only valid alongside-d, fr fr.-t TOKEN,--token=TOKENβ if the NSS database has more than one token available, the certificate is stored in this token. lowkey you will almost never need to pass this. only valid with-d.-f FILE,--certfile=FILEβ the certificate is stored in the named file. simple as that π
π OPTIONS π
-a,--allβ refresh the info about all requests where the service is gonna need to try contacting the CA again. every single one. slay.
π BUGS π
found a bug? π please file tickets for anything you find right here:
https://fedorahosted.org/certmonger/
π«Ά SEE ALSO π«Ά
certmonger(8) getcert(1) getcert-add-ca(1) getcert-add-scep-ca(1) getcert-list-cas(1) getcert-list(1) getcert-modify-ca(1) getcert-refresh-ca(1) getcert-rekey(1) getcert-remove-ca(1) getcert-request(1) getcert-resubmit(1) getcert-start-tracking(1) getcert-status(1) getcert-stop-tracking(1) certmonger-certmaster-submit(8) certmonger-dogtag-ipa-renew-agent-submit(8) certmonger-dogtag-submit(8) certmonger-ipa-submit(8) certmonger-local-submit(8) certmonger-scep-submit(8) certmonger_selinux(8)
and that's the whole page bestie π
this one came from the certmonger Manual, dated July 24, 2014, and it lives under CERTMONGER(1). go forth and refresh, periodt β¨π
π¦ where this page comes from
- alpine 3.24: certmonger-doc 0.79.21-r0 Β· GPL-3.0-or-later
- centos-stream 10: certmonger 0.79.21-1.el10 Β· GPL-3.0-or-later
- centos-stream 9: certmonger 0.79.21-1.el9 Β· GPLv3+
- debian bookworm: certmonger 0.79.17-2 Β· GPL-3.0-or-later WITH OpenSSL exception
- debian trixie: certmonger 0.79.20-2 Β· GPL-3.0-or-later WITH OpenSSL exception
- fedora 43: certmonger 0.79.20-5.fc43 Β· GPL-3.0-or-later
- fedora 43: certmonger 0.79.21-1.fc43 Β· GPL-3.0-or-later
- fedora 44: certmonger 0.79.21-4.fc44 Β· GPL-3.0-or-later
- opensuse-leap 16.0: certmonger 0.79.19-160000.2.2 Β· GPL-3.0-or-later
- opensuse-leap 16.0: certmonger 0.79.19-160000.2.2 Β· GPL-3.0-or-later
- opensuse-leap 16.0: certmonger 0.79.19-160000.2.2 Β· GPL-3.0-or-later
- opensuse-leap 16.0: certmonger 0.79.19-160000.2.2 Β· GPL-3.0-or-later
- ubuntu jammy: certmonger 0.79.14+git20211010-2ubuntu1 Β· GPL-3.0-or-later WITH OpenSSL exception
- ubuntu noble: certmonger 0.79.19-1build4 Β· GPL-3.0-or-later WITH OpenSSL exception
- ubuntu questing: certmonger 0.79.20-2build1
- ubuntu resolute: certmonger 0.79.21-1 Β· GPL-3.0-or-later WITH OpenSSL exception
- ubuntu stonking: certmonger 0.79.21-1build1 Β· GPL-3.0-or-later WITH OpenSSL exception
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms