Am 18.07.19 um 13:49 schrieb Stefan G. Weichinger:
> Am 18.07.19 um 13:45 schrieb Stefan G. Weichinger:
>> Am 18.07.19 um 10:44 schrieb Diego Zuccato:
>>> Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:
>>>
Add the same pattern near line 757:
return if $line =~ /^Unable to initialize
Am 18.07.19 um 13:45 schrieb Stefan G. Weichinger:
> Am 18.07.19 um 10:44 schrieb Diego Zuccato:
>> Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:
>>
>>> Add the same pattern near line 757:
>>> return if $line =~ /^Unable to initialize messaging context/;
>> Tks! Applied. Hope it gets
Am 18.07.19 um 10:44 schrieb Diego Zuccato:
> Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:
>
>> Add the same pattern near line 757:
>> return if $line =~ /^Unable to initialize messaging context/;
> Tks! Applied. Hope it gets included in next update!
>
Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:
> Add the same pattern near line 757:
> return if $line =~ /^Unable to initialize messaging context/;
Tks! Applied. Hope it gets included in next update!
--
Diego Zuccato
Servizi Informatici
Dip. di Fisica e Astronomia (DIFA) - Università di
Am 17.07.19 um 19:04 schrieb Jean-Louis Martineau:
> Add the same pattern near line 757:
> return if $line =~ /^Unable to initialize messaging context/;
Oh, Jean-Louis, nice to read you!
thanks for the missing line, yes, now my first test dump is free of that
error.
Do we have a PR somewhere
-client: HOST localhost ERROR: //192.168.0.250/ftp:
Application 'amsamba': exited with status 1
Am 16.07.19 um 10:07 schrieb Stefan G. Weichinger:
> Am 16.07.19 um 09:14 schrieb Diego Zuccato:
>> Il 16/07/19 08:46, Stefan G. Weichinger ha scritto:
>>
>>> I never figur
Am 16.07.19 um 10:07 schrieb Stefan G. Weichinger:
> Am 16.07.19 um 09:14 schrieb Diego Zuccato:
>> Il 16/07/19 08:46, Stefan G. Weichinger ha scritto:
>>
>>> I never figured out the correct patch ;-)
>>> Pls show your change, I want to give it another try.
>> Here it is.
>> -8<--
>> # diff -u
Am 16.07.19 um 09:14 schrieb Diego Zuccato:
> Il 16/07/19 08:46, Stefan G. Weichinger ha scritto:
>
>> I never figured out the correct patch ;-)
>> Pls show your change, I want to give it another try.
> Here it is.
> -8<--
> # diff -u amsamba.ori amsamba
> --- amsamba.ori 2019-07-16
Il 12/07/19 15:23, Diego Zuccato ha scritto:
> define dumptype win {
> auth "local"
> #estimate client
> #compress server custom
> #server-custom-compress "/usr/bin/pigz"
> program "APPLICATION"
> application {
> plugin "amsamba"
> property "AMANDAPASS"
Il 16/07/19 08:46, Stefan G. Weichinger ha scritto:
> I never figured out the correct patch ;-)
> Pls show your change, I want to give it another try.
Here it is.
-8<--
# diff -u amsamba.ori amsamba
--- amsamba.ori 2019-07-16 09:09:28.430585521 +0200
+++ amsamba 2019-07-10 11:02:13.352987193
Am 10.07.19 um 14:17 schrieb Diego Zuccato:
> Too bad the patch given here:
> http://www.backupcentral.com/forum/14/292396/smbclient_usage_fails_with__unable_to_initialize_messaging_context_
> is not in packaged version (3.5.1) yet.
>
> Adding the two lines, in my case, fixes the amcheck issue.
Il 10/07/19 14:23, Diego Zuccato ha scritto:
>> Too bad amdump fails after quite a long time with:
>> FAILED [data timeout]
>> FAILED [Error accepting incoming connection: Connection timed out]
>> Which incoming connection is it referring to???
I tried trplacing tcpd (default dep of Debian
Il 10/07/19 14:17, Diego Zuccato ha scritto:
> Too bad amdump fails after quite a long time with:
> FAILED [data timeout]
> FAILED [Error accepting incoming connection: Connection timed out]
>
> Which incoming connection is it referring to???
Forgot to say that:
1) if I place the wrong password
Il 09/07/19 18:22, Tobias Koeck ha scritto:
> It seems to break only 'amcheck a2g-2' right now. The 'amdump' command
> seems to be dumping and writing it anway so it doesn't seem that super
> urgent.
I just upgraded to Debian 10, too, to check if that would fix my issues
with amsamba.
Too bad the
On Mon, 8 Jul 2019 17:51:44 +0200
Tobias Koeck wrote:
> Hi,
>
> since I have upgraded to Debian 10 I get strange amsamba errors.
>
> Any ideas why?
I'm no expert on Samba. However, while upgrading from Debian stretch
(9.x) to buster (10.0), I saw the following notices which may be
relevant
Hi Jose,
thank's for responding.
It seems to break only 'amcheck a2g-2' right now. The 'amdump' command
seems to be dumping and writing it anway so it doesn't seem that super
urgent.
Still amcheck won't work for Windows network shares so no way to know if
it works before you tried amdump.
Hi,
I do not have a setup for testing amsamba, but I will do my the best
next week. I am going to DebConf19 and should have time to look into
it.
Kind regards
Jose M Calhariz
On Mon, Jul 08, 2019 at 05:51:44PM +0200, Tobias Koeck wrote:
> Hi,
>
> since I have upgraded to Debian 10 I get
On Mon, Jul 08, 2019 at 17:51:44 +0200, Tobias Koeck wrote:
> Hi,
>
> since I have upgraded to Debian 10 I get strange amsamba errors.
>
> Any ideas why?
[...]
> Mon Jul 08 12:01:25.616890194 2019: pid 2466: thd-0x55b9ce332000: Amsamba:
> execute: /usr/bin/smbclient /usr/bin/smbclient
Hi,
since I have upgraded to Debian 10 I get strange amsamba errors.
Any ideas why?
---
for amcheck a2g-2 I'll get for the samba checks
HOST localhost ERROR: smbclient: Unable to initialize messaging context
HOST localhost ERROR: //192.168.0.250/ftp: Application 'amsamba': exited
with status
19 matches
Mail list logo
