smbclient usage fails with "Unable to initialize messaging context"
at first: happy new year to all you amanda-users! -- Today I noticed that one server running Debian 9.6 and Samba-4.8.8 fails to amcheck/amdump: Amanda Backup Client Hosts Check HOST backup ERROR: smbclient: Unable to initialize messaging context HOST backup ERROR: //192.168.16.230/ELBA5: Application 'amsamba': exited with status 1 HOST backup ERROR: smbclient: Unable to initialize messaging context HOST backup ERROR: //192.168.16.230/BMDDocs: Application 'amsamba': exited with status 1 HOST backup ERROR: smbclient: Unable to initialize messaging context etc I googled and found issues with samba, reported it already: https://lists.samba.org/archive/samba/2019-January/220209.html maybe it is safe and working to ignore it, I will try to let amsamba ignore that message. Anyone else hitting this?
Re: smbclient usage fails with "Unable to initialize messaging context"
Am 02.01.19 um 11:19 schrieb Stefan G. Weichinger: at first: happy new year to all you amanda-users! -- Today I noticed that one server running Debian 9.6 and Samba-4.8.8 fails to amcheck/amdump: Amanda Backup Client Hosts Check HOST backup ERROR: smbclient: Unable to initialize messaging context HOST backup ERROR: //192.168.16.230/ELBA5: Application 'amsamba': exited with status 1 HOST backup ERROR: smbclient: Unable to initialize messaging context HOST backup ERROR: //192.168.16.230/BMDDocs: Application 'amsamba': exited with status 1 HOST backup ERROR: smbclient: Unable to initialize messaging context etc I googled and found issues with samba, reported it already: https://lists.samba.org/archive/samba/2019-January/220209.html maybe it is safe and working to ignore it, I will try to let amsamba ignore that message. I'd be thankful for any help with patching amsamba.
Re: smbclient usage fails with "Unable to initialize messaging context"
On 1/2/19 8:19 PM, Stefan G. Weichinger wrote: >> at first: happy new year to all you amanda-users! Happy new year as well! >> Today I noticed that one server running Debian 9.6 and Samba-4.8.8 fails >> to amcheck/amdump: >> >> Amanda Backup Client Hosts Check >> >> HOST backup ERROR: smbclient: Unable to initialize messaging context >> HOST backup ERROR: //192.168.16.230/ELBA5: Application 'amsamba': exited >> with status 1 [...] >> https://lists.samba.org/archive/samba/2019-January/220209.html >> >> maybe it is safe and working to ignore it, I will try to let amsamba >> ignore that message. > > I'd be thankful for any help with patching amsamba. I don't use smb or amsamba, so I don't know what it does in depth. But I don't yet understand from your e-mail what's happening at all. Is this an error that prevents it from working or just a message you want to get rid of? Exit status 1 (from amsamba, but probably also from smbclient?) indicates more than a nuisance. Do you get the same error from a shell when trying smbclient command that amanda/amsamba produces? Maybe the issue needs to be analyzed and solved underneath amanda. Yours, Uwe
Re: smbclient usage fails with "Unable to initialize messaging context"
Am 03.01.19 um 09:56 schrieb Uwe Menges: > On 1/2/19 8:19 PM, Stefan G. Weichinger wrote: >>> at first: happy new year to all you amanda-users! > > Happy new year as well! thank you ;) > I don't use smb or amsamba, so I don't know what it does in depth. > But I don't yet understand from your e-mail what's happening at all. > > Is this an error that prevents it from working or just a message you > want to get rid of? Exit status 1 (from amsamba, but probably also from > smbclient?) indicates more than a nuisance. > > Do you get the same error from a shell when trying smbclient command > that amanda/amsamba produces? Maybe the issue needs to be analyzed and > solved underneath amanda. Yes, it is also given back by smbclient on the shell, when run by the backup/amanda user. Rowland Penny on the samba-mailing-list told me that it can be ignored, but amanda does not do that yet. So far I noticed that amdumps work, but the reports are "tainted" (is that the word?) by the ugly message and therefore marked as FAILED. I couldn't find a way to exclude/ignore such messages from smbclient within amsamba. And browsing the script itself it wasn't clear to me non-coder how and where to add that. Filing an issue at github seems non-working to me, as I wait for a single beep of feedback for two weeks now after filing my last issue there (additionally to posting here). Stefan
Re: smbclient usage fails with "Unable to initialize messaging context"
On 1/4/19 7:51 PM, Stefan G. Weichinger wrote: > I couldn't find a way to exclude/ignore such messages from smbclient > within amsamba. And browsing the script itself it wasn't clear to me > non-coder how and where to add that. I'm not able to test that, my perl is rusty, I didn't take a close look, yadda yadda.. Try to add to amsamba after both (L433 + L521): next if /^WARNING/g; + next if /^Unable to initialize messaging context/g; Or if the message doesn't really start at first column, omit the ^. Yours, Uwe
Re: smbclient usage fails with "Unable to initialize messaging context"
Am 05.01.19 um 00:31 schrieb Uwe Menges: > On 1/4/19 7:51 PM, Stefan G. Weichinger wrote: >> I couldn't find a way to exclude/ignore such messages from smbclient >> within amsamba. And browsing the script itself it wasn't clear to me >> non-coder how and where to add that. > > I'm not able to test that, my perl is rusty, I didn't take a close look, > yadda yadda.. > > Try to add to amsamba after both (L433 + L521): > next if /^WARNING/g; > + next if /^Unable to initialize messaging context/g; > > Or if the message doesn't really start at first column, omit the ^. Thanks for the suggestion, I tried three variations now without success. Always the warning in the email reports. I tried: next if /^Unable to initialize messaging context/g; next if /Unable to initialize messaging context/g; next if /Unable to initialize messaging context/;
Re: smbclient usage fails with "Unable to initialize messaging context"
Am 06.01.19 um 10:53 schrieb Stefan G. Weichinger: > Am 05.01.19 um 00:31 schrieb Uwe Menges: >> On 1/4/19 7:51 PM, Stefan G. Weichinger wrote: >>> I couldn't find a way to exclude/ignore such messages from smbclient >>> within amsamba. And browsing the script itself it wasn't clear to me >>> non-coder how and where to add that. >> >> I'm not able to test that, my perl is rusty, I didn't take a close look, >> yadda yadda.. >> >> Try to add to amsamba after both (L433 + L521): >> next if /^WARNING/g; >> +next if /^Unable to initialize messaging context/g; >> >> Or if the message doesn't really start at first column, omit the ^. > > Thanks for the suggestion, I tried three variations now without success. > Always the warning in the email reports. > > I tried: > > next if /^Unable to initialize messaging context/g; > > next if /Unable to initialize messaging context/g; > > next if /Unable to initialize messaging context/; Did someone solve this? I get it again today on a fresh Debian 10.4 installation. Maybe I have to use a non-standard samba from another repo (I have an idea ...)
Re: smbclient usage fails with "Unable to initialize messaging context"
Am 29.06.20 um 19:19 schrieb Stefan G. Weichinger: >> I tried: >> >> next if /^Unable to initialize messaging context/g; >> >> next if /Unable to initialize messaging context/g; >> >> next if /Unable to initialize messaging context/; > > Did someone solve this? > > I get it again today on a fresh Debian 10.4 installation. > > Maybe I have to use a non-standard samba from another repo (I have an > idea ...) samba-4.10.15 from the van-belle repo https://apt.van-belle.nl/ solved this. nice
