Ever since the 9.6 update I constantly have issues with high CPU on my UTM basically causing timeout errors with al web browsing, even a check for new email using GMail on my phone which seems odd as that I wouldn't think would be HTTP(S) traffic but SMTP. I've seen the following in my logs:
2019:05:13-10:04:07 fw letsencrypt[25547]: E Renew certificate: aborting, failed to acquire an exclusive lock: Resource temporarily unavailable
2019:05:13-10:06:01 fw letsencrypt[25744]: E Renew certificate: aborting, failed to acquire an exclusive lock: Resource temporarily unavailable
2019:05:13-10:17:16 fw letsencrypt[26937]: E Renew certificate: aborting, failed to acquire an exclusive lock: Resource temporarily unavailable
2019:05:13-10:18:02 fw letsencrypt[27001]: E Renew certificate: aborting, failed to acquire an exclusive lock: Resource temporarily unavailable
2019:05:13-10:03:01 fw /usr/sbin/cron[25497]: (dehydrated) CMD (/var/chroot-reverseproxy/usr/dehydrated/bin/renew_certificate.pl > /dev/null)
2019:05:13-10:03:01 fw /usr/sbin/cron[25498]: (root) CMD (/usr/local/bin/create_rrd_graphs.plx --mode daily)
2019:05:13-10:03:17 fw postgres[3800]: [55-1] LOG: using stale statistics instead of current ones because stats collector is not responding
2019:05:13-10:03:27 fw postgres[3800]: [56-1] LOG: using stale statistics instead of current ones because stats collector is not responding
2019:05:13-10:03:38 fw postgres[3800]: [57-1] LOG: using stale statistics instead of current ones because stats collector is not responding
2019:05:13-10:04:01 fw /usr/sbin/cron[25544]: (dehydrated) CMD (/var/chroot-reverseproxy/usr/dehydrated/bin/renew_certificate.pl > /dev/null)
2019:05:13-10:04:27 fw postgres[3800]: [58-1] LOG: using stale statistics instead of current ones because stats collector is not responding
2019:05:13-10:04:22 fw postgres[25548]: [3-1] LOG: using stale statistics instead of current ones because stats collector is not responding
2019:05:13-10:04:50 fw postgres[3800]: [59-1] LOG: using stale statistics instead of current ones because stats collector is not responding
2019:05:13-10:10:11 fw system-reporter.pl: WARN - can't read sysmon data '/etc/sysmond.ph':
2019:05:13-10:10:11 fw system-reporter.pl: WARN - Error updating sysmon based data
2019:05:13-10:10:41 fw postgres[3800]: [64-1] LOG: using stale statistics instead of current ones because stats collector is not responding
So I'm not sure if this issue is a PostgreSQL, a Let's Encrypt SSL renewal issue, or what is going on. I do know that if I manage to get logged into my UTM via IP access and turn off the Web Filtering things start working. It's getting annoying as I connect to my work via an HTML5 Citrix Client and it freezes up my remote Citrix desktop connection multiple times a day when I'm working. If anyone has any ideas or path to go down to resolve this I'd appreciate it.
This thread was automatically locked due to age.
