similar to: Some strange errors in logs

Displaying 20 results from an estimated 2000 matches similar to: "Some strange errors in logs"

2017 Nov 10
1
Some strange errors in logs
+1 "penny" :-) :-) for my thoughts.. :-p But yes, that should fix it. I also suggest, review your logs, you wil notice more messages. Rsyslog/apt/snmp/postfix/ntp need manual changes after the upgrade. At least these, maybe more but these are the one i've encountered. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at
2017 Nov 10
0
Some strange errors in logs
On Fri, 10 Nov 2017 02:55:44 -0700 (MST) Mariusz80 via samba <samba at lists.samba.org> wrote: > Hello there. > I need consultation and any advice about my log file. > > I have some strange errors in my log file about "invalid zone > operation" and "pad length mismatch. Calculated 44 got 0" on my DC1 > and DC2 samba Version 4.5.12-Debian >
2017 Nov 10
3
Some strange errors in logs
Hai, cat "/var/lib/samba/private/named.conf" also please. And check if the correct bind9_dlz is enabled. dpkg -l | grep bind9 Jessie, should be 9.9 Stretch should be 9.10 If this server was upgraded then you need to manualy adjust the file above. Looks to my bind9-dlz is enable in smb.conf but not loaded. cat /var/log/daemon.log | grep dlz You should see thing like: samba_dlz:
2020 Apr 22
3
pad length mismatch error message
Hi, I found the following error message in the log.samba: [2020/04/20 16:32:33.168921, 1] ../../librpc/rpc/dcerpc_util.c:373(dcerpc_pull_auth_trailer) ../../librpc/rpc/dcerpc_util.c:373: ERROR: pad length mismatch. Calculated 44 got 0 It happens on all nodes on different times, but unfortunately I have no specific situation or action which causes this. We are currently using Samba version
2018 Oct 30
3
RPC and NDR errors in log file
On 10/29/2018 1:57 PM, Rowland Penny via samba wrote: > On Mon, 29 Oct 2018 13:20:18 -0400 > James Atwell via samba <samba at lists.samba.org> wrote: > >> Hello List, >> I'm receiving several of these messages in my samba >> log file. I'm not entirely sure what the errors are referencing >> either. I'm under the assumption DNS
2013 Sep 01
1
Samba4/Windows DNS replication and administration issue
Hi all, I am having trouble with DNS replication between a Linux/Samba 4.0.9 box and Windows Server 2012 domain controller, as well as administering the Linux DNS from the Windows DNS Manager snap-in. First a little background. I am trying to integrate a Samba 4.0.9 server as a domain controller in an existing Windows Active Directory domain. The domain and forest are at Windows 2008R2
2020 Oct 07
3
Often errors in logs
Hi, i got many errors like [2020/10/05 10:18:45.257966, 1] ../../librpc/rpc/dcerpc_util.c:373(dcerpc_pull_auth_trailer) ../../librpc/rpc/dcerpc_util.c:373: ERROR: pad length mismatch. Calculated 44 got 0 what it may be? Thanks
2020 Apr 22
2
pad length mismatch error message
Hi Louis, it happens on the AC-DC nodes on Debian 10, running with BIND9_DLZ backend... dpkg -l |grep bind9 ii bind9 1:9.11.5.P4+dfsg-5.1 amd64 Internet Domain Name Server ii bind9-host 1:9.11.5.P4+dfsg-5.1 amd64 DNS lookup utility (deprecated) ii bind9utils 1:9.11.5.P4+dfsg-5.1 amd64
2018 Nov 09
2
Samba panic when accessing DNS domain entry with RSAT DNS tool
Hi everybody, for some time now I have an issue with our samba/bind9-DLZ setup which became worse lately. I use the RSAT DNS tool to configure DNS records. In the past it sometimes happened, that DNS died when accessing the domain zone. This condition could only be resolved by restarting samba on the affected DC. Unfortunately the situation got worse and configuration/modification of entries
2018 Nov 09
2
Samba panic when accessing DNS domain entry with RSAT DNS tool
Hello Daniel, thank you for the fast reply. I am also using Windows 10. I'll setup a temporary Win7 VM to test if this will make any difference. Do you know if this a known issue with RSAT on Windows 10 ? Best regards Andreas Am 09.11.2018 um 11:23 schrieb Mueller: > I had this error when I did it from Windows 10. > I usede a Windows 7 PC and everything was fine again. > >
2016 Aug 19
2
User accounts being blocked
Dear James, Thanks for the input. Even increasing from 5 to 10, the amount of times to miss the password and lock the account (after changing, I wheeled a gpupdate / force), if you miss 3 times the account is locked. I changed smb.conf log level to 9. I tried to unlock the account using the samba-tool command line, but without success, because I can only unlock using the RSAT. I get these
2019 Jun 26
3
Reverse DNS
On 26/06/2019 04:38, Praveen Ghimire via samba wrote: > Hi Louis, > > Thank you for that > > I have made the changes as per below , some items might have duplicated. I then reload apparmor restarted the samba-ad-dc and bind9 services and get the same issue. Every time the forward DNS update works but the reverse doesn't > > I found a really interesting samba post going
2018 Nov 02
0
RPC and NDR errors in log file
Hai, Based on : IsSigneddnsserver: Invalid zone operation Are you running against a ( forwarded ) DNSSEC server or DNS Crypt server. Try an other forward if are. If you running internal samba DNS, try bind9_DLZ Handy list for dnssec and dns crypt: https://wiki.ipfire.org/dns/public-servers https://dnscrypt.info/public-servers Greetz, Louis > -----Oorspronkelijk bericht-----
2015 Jul 30
2
Failed to bind to uuid ???
Dear All, Recently I notice that sometime the AD DC will die sometime. Any one have see this issue before? And yesterday case lead me to believes that this error message was the issue... They are repetitive and thus I only show 2... [2015/07/29 00:00:04.620033, 0] ../source4/librpc/rpc/dcerpc_util.c:681(dcerpc_pipe_auth_recv) Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for
2019 Mar 13
2
replication fails
Am 13.03.19 um 12:49 schrieb Rowland Penny via samba: >> Should /etc/hosts contain pointers to own FQDN or not? To DCs? >> > > /etc/hosts should contain a line that points 127.0.0.1 to localhost and > a line that points the DC's ipaddress to its FQDN and shorthostname > > EXAMPLE: > > 127.0.0.1 localhost > 192.168.0.6 dc4.samdom.example.com dc4 >
2015 Aug 02
1
Failed to bind to uuid ???
What Samba version are you using? I have seen a similar problem triggered by connectivity issues between the DCs. What's the output from samba-tool drs showrepl? Still, I haven't found a solution... On Sat, Aug 1, 2015 at 5:30 AM, Min Wai Chan <dcmwai at gmail.com> wrote: > Just to ask. > Anyone can shard some light on that wrong is that? > > Thank you. > > Min
2015 Jul 02
2
Rejoin dc to domain
Hallo When rejoining a dc to the domain I get the following error message: [2015/07/02 11:51:44.089786, 0] ../source4/librpc/rpc/dcerpc_util.c:729(dcerpc_pipe_auth_recv) Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for
2020 Apr 22
4
pad length mismatch error message
Well, If you running with bind9_DLZ, you also should enable it. Based on what i see below, its not enable, you installed it your not done yet. ;-) Verify the settings ( debianize the paths ) https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End Then then its all done, reboot the server. Run this script, anonimized it and post the content to the list. Then i know all i want to know.
2016 Apr 01
4
Samba suddenly restart and replication does not works anymore
Hello Samba team ! On my network I have three Samba-4.1.17 domain controllers (Debian Jessie) : -> One PDC : pdc01 -> Two "slave" DC : sdc02, sdc03 I don't know why, but sometimes Samba receive the SIGTERM signal and restart even if I remove it from the logrotate configuration. On "pdc01" I see : ---------- pdc01 (log.samba) ---------- SIGTERM: killing children
2020 Mar 04
2
Can't use DNS Manager in MMC on Samba 4.12.0
On Samba 4.12.0, I receive the error "ndr_pull_uint32: ndr_pull_error(Buffer Size Error): Pull bytes 4 (../../librpc/ndr/ndr_basic.c:152) at ../../librpc/ndr/ndr_basic.c:152" when opening the DNS Manager in MMC. This jumped out at me from the log-level 10 output (I'm happy to send the full logs but would rather do that somewhere more private): /dnsserver: Found DNS zone