Hello Martin. You are right!
I was sure that binaries were stored in nfs share, instead they are stored in local disk. So, during last upgrade only one node has been updated, the other was the wrong version. Sorry for my mistake 🙂🙂 Thank you and regards. ________________________________ Da: Martin Simmons <mar...@lispworks.com> Inviato: martedì 6 agosto 2019 19:25 A: Roberto Menti <roberto_me...@otb.net> Cc: bacula-users@lists.sourceforge.net <bacula-users@lists.sourceforge.net> Oggetto: Re: [Bacula-users] Strange behaviour storage daemon in clustered configuration >>>>> On Tue, 6 Aug 2019 12:47:40 +0000, Roberto Menti said: > > We have a storage daemon in a cluster environment, all daemons are the same > version ( 9.4.2 ) > > Virtual tapes are stored in a nfs share, same options and permissions for > both nodes. > > > > When daemon is running on node 1 all is working well, when daemon is on the > other node, we get an "invalid catalog request" error when starting to write > to tape (after having correctly identify the tape to use ): Double check the version running on the other node (e.g. use "status storage"). The "invalid catalog request" has a missing field, so looks older. __Martin ATTENTION: this email comes from outside the OTB organization. Do not click on links or open attachments unless you acknowledge the sender and know that the content is secure. IMPORTANT NOTICE This message may contain privileged or confidential information. If you are not the intended recipient please notify the sender and delete the message from your computer immediately. Any dissemination, distribution or copy is strictly forbidden. Please note that e-mails may be faked, contain viruses or not assure receipt, without any responsibility for our company.
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
