Bareos has been working for several weeks on a new install of 18.2 but suddenly has quit working for some clients and started throwing errors.
I do not run TLS and did not have the Enable and Require entries inj my /etc/bareos/bareos-dir.d/director/bareos-dir.conf. I noticed one of my clients stopped backing up. A systemctl -l bareos-dir showed errors about not being able to write to /var/log/bareos logfile. I've checked passwords for the director on both systems and they are good. I have another system that backs up but if I run status client=workingsystem in bconsole I get the errors below in the log (they show up with the bad client, too). and then I get kicked out of bconsole. systemctl status bareos-dir shows these messages but bareos-dir is still running. Jun 14 12:59:47 srv-1-bkup1a.corp.l1049h.net systemd[1]: Starting Bareos Director Daemon service... Jun 14 12:59:49 srv-1-bkup1a.corp.l1049h.net systemd[1]: Started Bareos Director Daemon service. Jun 14 12:59:50 srv-1-bkup1a.corp.l1049h.net bareos-dir[6862]: Connected Storage daemon at srv-1-bkup1a.corp.l1049h.net:9103, encryption: PSK-AES256-CBC-SHA Jun 14 13:00:43 srv-1-bkup1a.corp.l1049h.net bareos-dir[6862]: Connected Client: ranger at ranger:9102, encryption: None Jun 14 13:00:43 srv-1-bkup1a.corp.l1049h.net bareos-dir[6862]: TLS read/write failure.: ERR=error:140E0197:SSL routines:SSL_shutdown:shutdown while in init I'm at a loss to explain why it suddenly stopped working. Any ideas would be appreciated. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/223891af-c510-44c5-94a0-1fdde6f1b234%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
