-
Notifications
You must be signed in to change notification settings - Fork 118
Cron finished (with errors) after upgrading to v8.2.0 #989
Description
Ever since I upgraded from v8.1.1 to v8.2.0 (and newer), I started noticing a lot of errors in my log, which prevent the latest image versions from appearing in the app. Here's a short excerpt of the errors (with the actual hostname redacted):
WARN whats-up-docker/watcher.docker.[HOST 1]: Error when processing (Error) (container=[HOST 1]_adguard-home)
WARN whats-up-docker/watcher.docker.[HOST 1]: Error when processing (Error) (container=[HOST 1]_glances)
WARN whats-up-docker/watcher.docker.[HOST 2]: Error when processing (Error) (container=[HOST 2]_whats-up-docker)
WARN whats-up-docker/watcher.docker.[HOST 2]: Error when processing (Error) (container=[HOST 2]_guacamole-server)
WARN whats-up-docker/watcher.docker.[HOST 2]: Error when processing (Error) (container=[HOST 2]_romvault)
WARN whats-up-docker/watcher.docker.[HOST 2]: Error when processing (Error) (container=[HOST 2]_uptime-kuma-db)
INFO whats-up-docker/watcher.docker.[HOST 1]: Cron finished (6 containers watched, 2 errors, 0 available updates)
INFO whats-up-docker/watcher.docker.[HOST 2]: Cron finished (42 containers watched, 4 errors, 5 available updates)
I'm also seeing this Deprecation Warning, which may or may not be the cause of the issue:
(node:7) [DEP0169] DeprecationWarning:
url.parse()behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued forurl.parse()vulnerabilities.
What's more is that the images' hash appears instead of the version number, but the images that appear that appear to have updates don't actually need to be updated.
When I downgrade back to v8.1.1, the errors disappear and everything appears to work as before. I checked the release notes for breaking changes to see if there was anything I needed to do or update in my configs, but I didn't see anything that stood out.