Is letsencrypt running twice?


#1

I have two logs for letsencrypt:
letsencrypt.log and renew.log

They have different times in them and I was wondering if the update was running twice. I run a cron update script at 0100, but the letsencrypt.log says an update ran at 0600. Can someone tell me what is going on here?

renew.log:
2016-09-19 01:00:05,946:DEBUG:certbot.main:Root logging level set at 10
2016-09-19 01:00:05,946:INFO:certbot.main:Saving debug log to /var/log/letsencrypt/letsencrypt.log
2016-09-19 01:00:05,946:DEBUG:certbot.main:certbot version: 0.8.1
2016-09-19 01:00:05,946:DEBUG:certbot.main:Arguments: [’-nvv’, ‘–standalone’]
2016-09-19 01:00:05,947:DEBUG:certbot.main:Discovered plugins: PluginsRegistry…
2016-09-19 01:00:05,988:DEBUG:certbot.plugins.selection:Requested authenticator standalone and…
2016-09-19 01:00:05,988:DEBUG:certbot.cli:Default Detector is Namespace…
2016-09-19 01:00:06,012:INFO:certbot.renewal:Cert not yet due for renewal
2016-09-19 01:00:06,012:DEBUG:certbot.renewal:no renewal failures


Processing /etc/letsencrypt/renewal/allpingers.net-0001.conf

The following certs are not due for renewal yet:
/etc/letsencrypt/live/allpingers.net-0001/fullchain.pem (skipped)
No renewals were attempted.


letsencrypt.log:
2016-09-19 06:00:05,946:DEBUG:certbot.main:Root logging level set at 10
2016-09-19 06:00:05,946:INFO:certbot.main:Saving debug log to /var/log/letsencrypt/letsencrypt.log
2016-09-19 06:00:05,946:DEBUG:certbot.main:certbot version: 0.8.1
2016-09-19 06:00:05,946:DEBUG:certbot.main:Arguments: [’-nvv’, ‘–standalone’]
2016-09-19 06:00:05,947:DEBUG:certbot.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#…
2016-09-19 06:00:05,988:DEBUG:certbot.plugins.selection:Requested authenticator standalone and…
2016-09-19 06:00:05,988:DEBUG:certbot.cli:Default Detector is Namespace(account=…
2016-09-19 06:00:06,012:INFO:certbot.renewal:Cert not yet due for renewal
2016-09-19 06:00:06,012:DEBUG:certbot.renewal:no renewal failures


#2

Given that the timestamps are exactly the same (down to the miliseconds) other than the hour, this does seem like a timezone issue. I’d suspect one of the log files is using UTC (I seem to recall that the client defaults to UTC for letsencrypt.log), while the other uses your system timezone. Does that account for the 5 hour difference?

Not sure if there’s a good reason for why it works that way. Out of curiosity: Is this a OS-packaged version of certbot (like the one in debian backports), or are you using certbot-auto?


#3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.