Absence of updates is labelled a critical error in syslog

[ALinuxUser]

My syslog contains, regularly:

storehelpers.go:441: cannot refresh snap "fwupd": snap has no updates available

That log entry is labelled 'critical' and I see the entry flash by when I shutdown the computer. Yet, this is hardly a critical problem or indeed a problem at all. What should happen is that at most an event logged as informational should occur.

Snapd 2.38+18.04
Linux Mint 19.1 Cinnamon
EDITED to fix a typo.

[Zygmunt Krynicki (zyga)]

I agree this should not be a critical error in any way. It's just a side effect of, if I understand this correctly, how we interact with the journal.

[Claudio Matsuoka (cmatsuoka)]

Could you confirm this still happens with snapd 2.42? I quickly tested it and this type of message was logged in the system journal as `info` (level 6).

[ALinuxUser (buntulongername-new)]

Yes, it still occurs with snap2 2.42. See below and the two screenshots that I attach.

$ snap --version
snap 2.42
snapd 2.42
series 16
linuxmint 19.2
kernel 5.3.7-050307-generic

[Claudio Matsuoka (cmatsuoka)]

Interesting. This is what I see here with Ksystemlog.

[Claudio Matsuoka (cmatsuoka)]

Oh, but I see you read from `/var/log/syslog` instead of the systemd journal. I don't have snapd entries in the syslog file.

[ALinuxUser (buntulongername-new)]

I find that in my journald (the systemd journal) the entries at issue are indeed marked as informational. So seemingly the problem is in whatever translation that goes on (or, given that you don't have this translation, *can* go on) between journald and syslog.