Displaying 20 results from an estimated 1200 matches similar to: "tdb_rec_read bad magic"
2023 Mar 03
2
DomainDnsZones bad magic
I've been called back to an old workplace to try to help with some issues
that they have and have found that the DomainDnsZones database is not
replicating. Everything else in the replication seems to be fine.
I ran a samba-tool dbcheck on the affected server and it returns:
ltdb:
tdb(/var/lib/samba/private/sam.ldb.d/DC=DOMAINDNSZONES,DC=MYDOMAIN,DC=MYCOMPANY.ldb):
tdb_rec_read bad magic
2009 Jan 21
1
error: tdb_rec_read bad magic
I am running Samba version 3.0.30 on AIX 5.3 and I got the following output
when using smbstatus:
tdb(/var/samba/locks/connections.tdb): tdb_rec_read bad magic 0x25a5b1e4 at
offset=278920
tdb(/var/samba/locks/locking.tdb): tdb_rec_read bad magic 0x0 at
offset=2547712
locked file list truncated
I am wondering what causes this and how to fix it. Thanks.
2017 Aug 26
2
DC Upgrade from 4.1.7 to 4.6.7
> -----Message d'origine-----
> De : samba [mailto:samba-bounces at lists.samba.org] De la part de Rowland
> Penny via samba
> Envoyé : samedi 26 août 2017 12:00
> À : samba at lists.samba.org
> Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7
>
...
> On Sat, 26 Aug 2017 11:28:00 +0400
> > Hi,
> >
> > I have begun to add a new 4.6.7 DC (following
2023 Mar 03
1
DomainDnsZones bad magic
On 03/03/2023 19:36, Peter Pollock via samba wrote:
> I've been called back to an old workplace to try to help with some issues
> that they have and have found that the DomainDnsZones database is not
> replicating. Everything else in the replication seems to be fine.
>
> I ran a samba-tool dbcheck on the affected server and it returns:
>
> ltdb:
>
2017 Aug 26
2
DC Upgrade from 4.1.7 to 4.6.7
> -----Message d'origine-----
> De : Andrew Bartlett [mailto:abartlet at samba.org]
> Envoyé : samedi 26 août 2017 12:40
> À : HB; samba at lists.samba.org
> Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7
>
> On Sat, 2017-08-26 at 12:32 +0400, HB via samba wrote:
> > >
> > Here is the output of samba-tool dbcheck :
> > # samba-tool dbcheck
>
2018 Jul 31
2
samba-tool dbcheck "Indexed and full searches both failed"
On Tue, 31 Jul 2018 07:37:38 -0500
Denis Morejon via samba <samba at lists.samba.org> wrote:
> Hi:
>
> I have two samba 4.7.4 DCs. One of them has problems. I can not use
> samba-tool on it. Then, when I try to fix It's database It returns:
>
> -------------------------------------------------------------------------------------------------------------------
>
2024 Jun 22
2
Failed to fetch machine account password for MYDOMAIN from both secrets.ldb
On Fri, 21 Jun 2024 17:08:39 +0100
Luis Peromarta via samba <samba at lists.samba.org> wrote:
>
> LP
> On Jun 21, 2024 at 12:02 +0100, Rowland Penny via samba
> <samba at lists.samba.org>, wrote:
> >
> > Up until here it was 'DC=mydomain,DC=int', then it becomes something
> > different, bad sanitisation ?
> >
>
> Yes :(
> >
2017 May 22
4
Samba4 AD Corrupted Member
Hi Guys.
Today i experienced a problem with my samba 4 AD.
I have a master(AD1) and a member(AD2) in a replicated environment.
I´ve just checked that my AD2 has some issues when i did this test:
----------------------------------------------------------------------------------
ldbsearch --url=/usr/local/samba/private/sam.ldb '(invocationid=*)'
--cross-ncs objectguid
# record 1
dn:
2018 Jul 31
2
Internal DNS migrate to Bind9_DLZ
On Tue, 31 Jul 2018 11:39:56 +0200
Michal <Michal67M at seznam.cz> wrote:
> > /etc/named.conf
> > # Global Configuration Options
> >
> > include "/var/lib/samba/bind-dns/named.conf";
> >
> > options {
> >
> > dump-file "/var/named/data/cache_dump.db";
> > statistics-file
2015 Mar 20
0
connections.tdb.0:tdb_rec_read bad magic and fd leak
Hi,
I have a samba (3.6.20) + ctdb cluster running on FreeBSD 8.2 and recently it run into problems.
log.ctdb increased very quickly and consumed 100% of the disk space, the log is full of message like:
2015/03/19 08:09:06.070897 [26053]: 00.ctdb: OPERATION: monitor
2015/03/19 08:09:06.278859 [26053]: 50.samba: [info] cy_samba_control monitor : 0
2015/03/19 08:09:07.054677
2018 Mar 12
1
Problem with data base after abnormal shutdown
Hello;
last week the power (energy) of the servers fail and it shutdown all.
When the power restart in the check I find that the samba4 AD DC have
problems. It work, but the users in some of the container or OU
dissapear, I mean, when I check with the RSAT the OU in with the user
most be, is empty
When I try to run # samba-tool dbcheck this is what I have:
[root at gtmad ~]# samba-tool
2017 Feb 08
2
DNS problems in my domain
The users in our network are experiencing some dns problems.
When i take closer look to our samba configuration I see that we have a corrupted ldb file (/var/lib/samba/private/sam.ldb.d/DC=DOMAINDNSZONES,DC=********,DC=COM.ldb).
I can still access the DNS entries from the Microsoft remote server administration tools.
What are my best options?
I have a backup of the ldb files from 2 months
2014 Jul 08
2
samba4 replication issues | sam.ldb inconsistency
Hi all,
We seem to have some issues with our samba4 ad setup. I posted about
this last week already but had received no replies at all so far. :-(
What is our situation:
two domain controllers (dc1 and dc2), one (separate) fileserver, all
running sernet-4.1.7. From the workstations perspective, everything is
running as it should, there appear to be no issues.
However: something in my
2020 Oct 14
1
Can I restore a Samba instance from an rsync backup?
Hello,
I have Samba 4.3.11 running as an ADDC on Ubuntu 14.04.
When I run samba-tool dbcheck, I get the following output:
ltdb:
tdb(/var/lib/samba/private/sam.ldb.d/DC=CORP,DC=EXAMPLE,DC=CO,DC=NZ.ldb):
tdb_rec_read bad magic 0x3f3f3f3f at offset=2993916
ERROR(ldb): uncaught exception - Indexed and full searches both failed!
File
2024 Jun 15
1
Issues joining DC
Dear all.
Let me make a shot brief of the issue I'm currently experiencing that
has been published in a couple of threads. Now I'm going to join them here.
Current scenario.
Centos7 running a Samba 4.6.5. Any kind of problem at client side, all
seems to runs fine. But in some cases the AD objects appears on Windows
clients as their SID instead of their name.
Rowland has suggested to
2015 Feb 02
1
Windows users can't change password 4.1.6
Just to be sure: Your real realm does not end with .local, right? In an another thread it was not recommended to use TLD .local. The wiki says this also.
Am 2. Februar 2015 12:25:46 MEZ, schrieb "Micha? P??rolniczak" <michal.polrolniczak at warp.org.pl>:
>the smb.conf for samba 4.1.6-Ubuntu
>[global]
> workgroup = DOMAIN
> realm = DOMAIN.LOCAL
>
2015 Jan 28
1
Windows users can't change password 4.1.6
On Wed, Jan 28, 2015 at 2:09 AM, Micha? P??rolniczak <
michal.polrolniczak at warp.org.pl> wrote:
>
>
> W dniu 2015-01-27 o 18:42, Marc Muehlfeld pisze:
>
>> Hello Micha?,
>>
>> Am 27.01.2015 um 07:08 schrieb Micha? P??rolniczak:
>>
>>> When changing password via Windows Logon it doesn't say it change it, it
>>> say that new password
2015 Jan 28
2
Windows users can't change password 4.1.6
W dniu 2015-01-27 o 18:42, Marc Muehlfeld pisze:
> Hello Micha?,
>
> Am 27.01.2015 um 07:08 schrieb Micha? P??rolniczak:
>> When changing password via Windows Logon it doesn't say it change it, it
>> say that new password that I entered is not valid with password politic
>> settings, and wasn't change.
> Does it met the requirements?
>
2020 Feb 05
2
ldb errors after upgrade, cause?
Hi!
recently we upgraded a Debian jessie server to Debian buster, with Samba
being upgraded from 4.5.12 (+dfsg-2+deb9u3) to 4.9.5 (+dfsg-5+deb10u1).
A few hours later we saw these errors in syslog:
smbd[26024]: [2020/02/03 11:13:13.631613, 0] ../lib/ldb-samba/ldb_wrap.c:79(ldb_wrap_debug)
smbd[26024]: ldb: Failure during ltdb_lock_read(): Locking error ? Busy
smbd[26024]:
2020 Feb 06
2
ldb errors after upgrade, cause?
L.P.H. van Belle via samba writes:
> Is samba-dsdb-modules installed ?
Yes, I checked again, and all packages are installed, all of them with the
proper version, and no leftovers.
This server works fine for a half a day, and then these errors happen, so I
think it's unlikely that it's related to the install itself.
I have already made a backup of all tdb files with tdbbackup and