BugCast BBC#8489: Thousands of Errors

12 views

Skip to first unread message

p...@citylink.dinoex.sub.org

unread,

Apr 23, 2020, 6:53:23 PM4/23/20

to bareos-users

Hello all,

and welcome to the BugCast of today!

Today we have a difficult situation, as we still do not have an idea where the bug ist - because, honestliy, we do not even know where the error is! We just get errors reported. Thousands of errors:

<daemon.err> edge bconsole: Connected Director daemon at admn-e: 9101, encryption: None
<daemon.err> edge syslogd: last message repeated 1 times
<daemon.err> edge syslogd: last message repeated 1 times
<daemon.err> edge syslogd: last message repeated 1 times
<daemon.err> edge syslogd: last message repeated 1 times
<daemon.err> edge syslogd: last message repeated 1 times
<daemon.err> edge syslogd: last message repeated 2 times
<daemon.err> edge syslogd: last message repeated 1 times
<daemon.err> edge syslogd: last message repeated 1 times
<daemon.err> edge syslogd: last message repeated 2 times
<daemon.err> edge syslogd: last message repeated 1 times
<daemon.err> edge syslogd: last message repeated 1 times
<daemon.err> edge syslogd: last message repeated 2 times
<daemon.err> edge syslogd: last message repeated 1 times
<daemon.err> edge syslogd: last message repeated 1 times
<daemon.err> edge syslogd: last message repeated 2 times
<daemon.err> edge syslogd: last message repeated 1 times
<daemon.err> edge syslogd: last message repeated 1 times

This goes on and on, and the whole logfile is full of it (and you cant just switch off the daemon.err facility in syslog, as this is one of those you should actually read!). But worse is, we don't get any clue what the error actually is.

We know already that console connected director, because we programmed that - but, WHAT IS IN ERROR WITH THAT??

This question, dear reader, we must leave up to You. The only thing we can say is: something here is *BROKEN*.

Now we all hope that we will soon have matters with more of a clue to present here.