Well, there are thousands of them, as I said, and they are much different.
For instance, yesterday, I tried to install Berkeley Quartery 2020Q2, and part of it is this:
> admn pkg: bareos-client upgraded: 18.2.7 -> 19.2.6
> admn pkg: bareos-webui upgraded: 18.2.7 -> 19.2.6
> admn pkg: bareos-server upgraded: 18.2.7 -> 19.2.6
Next thing I got was another error message, this time:
> admn root: /etc/rc: WARNING: failed precmd routine for bareos_dir
Config error: Cannot open config file
"/usr/local/etc/bareos/bareos-dir.d/*/*.conf": Permission denied
Now that one was easy to find:
root@admn:/usr/local/etc/bareos/bareos-dir.d/profile # dir
total 31
drwxr-x--- 2 root bareos 6 Apr 23 02:03 .
drwxr-x--- 17 root bareos 17 Apr 7 09:11 ..
-rw-r----- 1 root bareos 0 Apr 3 14:54 operator.conf
-rw-r----- 1 root bareos 467 Feb 11 16:58 operator.conf.sample
-rw-r----- 1 www www 382 Apr 15 04:49 webui-admin.conf
-rw-r----- 1 www www 382 Apr 15 04:49 webui-admin.conf.sample
So the webui had spit some useless config into the tree with bogus perms. Obviousely programs running as bareos:bareos cannot read a file with www:www 640 - and instead of ignoring it, it then throws EPERM and fails.
So here is the workaround, after any install:
# find /usr/local/etc/bareos/bareos-*.d/[a-z]* -name "*.conf" \
-exec truncate -s 0 {} \; \
-exec chown root:bareos {} \; \
-exec chmod 640 {} \;
Now, You see the principle: these error messages are useless on themselves because You won't get any clue from them. One always needs to track down the matter in each case to find the bug.
So what I am looking for is the catalog of all the error messages, their respective bugs and the workarounds. As there are lots of people using this piece of sw, there must already be workarounds - and I don't want to make them up all on my own!
Cheerio,
PMc