similar to: frequent tdb corruption

Hi All, My site has two separate clustered Samba instances (managed by two independent CTDB instances) running over GPFS. In the last couple of weeks, we have seen a recurring issue that causes the `smbd` process in *one* of these instances to become unresponsive (as seen by CTDB), which results in flapping of CTDB and multiple IP takeover runs. The symptoms that we observe are: 1) Samba

Hi, I have an issue with Samba version 3.0.25b on Debian. I am receiving a number of mails from my server with the following: > The Samba 'panic action' script, /usr/share/samba/panic-action, > was called for PID 18483 (). > This means there was a problem with the program, such as a segfault. > However, the executable could not be found for process 18483. > It may have

Hi there, isn't there really anybody who can give hints about this problem? Thanks, Ralf ==================BEGIN FORWARDED MESSAGE================== >From: "Ralf G. R. Bergs" <rabe@RWTH-Aachen.DE> >To: "samba@lists.samba.org" <samba@lists.samba.org> >Cc: "Eloy A. Paris" <peloy@debian.org> >Date: Sat, 03 Aug 2002 12:19:24 +0200

Hi Jeremy, Thanks so much for your reply! As a matter of fact, we did just that around 3:45p yesterday when our CTDB cluster was unable to self-heal from the latest in this series of failover events. Here's how the situation went down: 1) We saw flapping identical to that described in my original post 2) After about 30 minutes of waiting, CTDB was just spinning with `smbd` repeatedly

Hi All, Firstly, I know this is a MacOS X issue and not sure if you guys can help, but I'm really hoping you can since I don't appear to be getting any joy elsewhere. Running OSX 10.5.4 and recently (last week) nmbd is hogging the CPU. I know this is a part of the Samba server on OSX, hence the post to this mail-list. When I disconnect from the network, nmbd goes away and doesn't

Sometimes (rarely, very rarely) i spot a <printername>.tdb error that seems to prevent the communication between samba and CUPS. In log i see: [2019/06/26 15:15:49.633876, 0] ../source3/lib/util_tdb.c:316(tdb_log) tdb(/var/cache/samba/printing/sml5010-2.tdb): tdb_rec_read bad magic 0x25 at offset=26096 the only solution i've found, pretty drastic, is: systemctl stop

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.

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

Hi, Does someone know a document which explains the TDB structure. functionalites, and format of the TDB files etc. I need to understand why some of the TDBs like messages.tdb, unexpected.tdb, brlock if not read_only, locking.tdb, session.tdb, wins.tdb are called with TDB_CLEAR_IF_FIRST tdb flags. Why some TDBs are opend with O_RDWR|O_CREAT flags viz. gencache.tdb, group_mapping.tdb,

> -----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

On Sat, Apr 22, 2006 at 06:15:31PM +0100, Daniel J Blueman wrote: > As a test, I changed the opening of the locking.tdb and brlock.tdb > files to use the TDB_INTERNAL flag, avoiding use of the fcntl(F_SETLK) > syscall for locking individual database records. Performance was a lot > snappier, with quite a bit less system time used. > > What is the scope of implementing shared

> -----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 >

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: > > ------------------------------------------------------------------------------------------------------------------- >

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

[CC to Debian package maintainer] Hi there, I'm still experiencing this worrysome tdb corruption even after I upgraded to 2.2.5. I built this package myself from the officially released 2.2.5 source. Here's a log snippet: Aug 3 11:15:04 Server smbd[23307]: [2002/08/03 11:15:04, 0] tdb/tdbutil.c:tdb_log(492) Aug 3 11:15:04 Server smbd[23307]: tdb(/var/run/samba/connections.tdb):

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:

using samba 4.1.4 syslog have alot of those in log: [2014/07/22 13:24:12.22351, 0] ../lib/ldb-samba/ldb_wrap.c:71(ldb_wrap_debug) ldb: ltdb: tdb(/usr/local/samba/private/sam.ldb.d/DC=DOMAINDNSZONES,DC=MYDOMAIN,DC=LOCAL.ldb): tdb_rec_read bad magic 0x0 at offset=516897176 Anything I can do to fix it?

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

============================================================= "Just play. Have fun. Enjoy the game." Michael Jordan ============================================================= Release Announcements ===================== This is is the latest stable release of Samba 3.6. Major enhancements in Samba 3.6.14 include: o Certain xattrs cause Windows error 0x800700FF

============================================================= "Just play. Have fun. Enjoy the game." Michael Jordan ============================================================= Release Announcements ===================== This is is the latest stable release of Samba 3.6. Major enhancements in Samba 3.6.14 include: o Certain xattrs cause Windows error 0x800700FF