similar to: Problems with TDBs on CTDB-managed Samba instance

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

On Fri, Oct 16, 2015 at 02:44:36PM +0000, Howard, Stewart Jameson wrote: > 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

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

smbd version 3.0.25b-0.4E.5 Our server was functioning very well for several months. Our SAN crapped out and the LUN the server was using was gone. Everything is back up except SAMBA is acting crazy. I am looking at the logs and I am getting /var/log/samba/winbindd.log winbindd: Exceeding 200 client connections, no idle connection found and ads_krb5_mk_req: krb5_get_credentials failed for

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

On Sat, Oct 17, 2015 at 04:13:30PM +0000, Howard, Stewart Jameson wrote: > gencache_notrans.tdb > gencache.tdb > mutex.tdb Just a side-remark: These tdbs have nothing to do with ctdb, they are purely local. > Because of the current steady size of this file compared > to its repeated, intermittent, and rapid inflation, we > suspect that there is some operational condition which

This log is repeatedly appearing: [2012/10/10 18:42:47.088584, 1] lib/util_tdb.c:385(tdb_log) tdb(unnamed): tdb_open_ex: /var/lib/samba/unexpected.tdb (64768,921067) is already open in this process Anybody knows if it's true tha it's harmless? Thanks, -- Marcio Oliveira. "Tudo concorre para o bem daqueles que amam ? Deus." (Rom 8,28)

Rowland, I commented out what you asked me to, no change. # Global parameters [global] workgroup = TRUEVINE realm = TRUEVINE.LAN netbios name = DC01 server role = active directory domain controller server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbi$ # idmap_ldb:use rfc2307 = yes # idmap config *:backend = tdb # idmap

Is there any way to suppress the message: tdb(unnamed): tdb_open_ex: /var/samba/locks/unexpected.tdb (110,101) is already open in this process They are filling my nmbd.log and I have read that they should be ignored (Jerry,Carter post, Sun Aug 7 16:43:26 GMT 2005) We are running Samba 3.0.28 on FreeBSD 6.2. From util_tdb.c, it looks like this message could be suppressed with a

Hi all, After much grief today, we'd like to support the 'TODO' note in source/lib/util_tdb.c :- /* TODO: If we time out waiting for a lock, it might * be nice to use F_GETLK to get the pid of the * process currently holding the lock and print that * as part of the debugging message. -- mbp */ It could have saved us a whole-sale restart of Samba if we could have more easily

Hello, I have a problem with samba 3.0.26a (from ports) on FreeBSD (amd64, SMP, 6.2 RELEASE). My log.smbd looks like below: --- samba starts normally: [2007/11/24 16:55:22, 0] smbd/server.c:main(944) smbd version 3.0.26a started. Copyright Andrew Tridgell and the Samba Team 1992-2007 --- but an error is reported: [2007/11/24 16:55:22, 0]

I'm trying to get my CentOS 5.6 machine setup as a Active Directory Domain Member with Windows 2008 level domain and samba 3.5. I haven't tried this before. I can successfully join the domain and return users using 'wbinfo -u' and groups with 'wbinfo -g' but when I try 'getent passwd' I only get the local users. I'm not sure what element that indicates is

Hi folks, # uname -srvo Linux 2.6.18-194.el5xen #1 SMP Tue Mar 16 22:01:26 EDT 2010 GNU/Linux # cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.5 (Tikanga) # smbd --version Version 3.3.8-0.51.el5 I'm trying to run a backup samba server using some custom in-house scripts which I inherited and am stuck with. Essentially the primary server periodically rsyncs a bunch of

Hello I got a bunch of PANIC messages this morning on a FreeBSD 6.3 host, and had to restart Samba: ======== [2008/05/10 10:28:51, 0] lib/util.c:smb_panic(1633) PANIC (pid 43086): tdb_reopen_all failed. [2008/05/10 10:28:51, 0] lib/util.c:log_stack_trace(1737) BACKTRACE: 3 stack frames: #0 0x8220341 <smb_panic+73> at /usr/local/sbin/smbd #1 0x82b9389 <main+4773> at

Hello, upgraded to Samba 3.2.6, and immediately printing went into coma. Observed that printers lose their configurations (driver models, locations, etc). And if I reset the printer drivers on each share, eventually they will be lost again. Looking at the logs we are getting panics like this: --- [2008/12/16 05:12:51, 0] lib/util_tdb.c:tdb_log(682) tdb(/var/lib/samba/printing/CanonC1.tdb):

Hi, I'm seeing regular tdb corruption; typical log messages are: tdb(/var/db/samba/sessionid.tdb): tdb_rec_read bad magic 0x42424242 at offset=672032 tdb(/var/db/samba/connections.tdb): tdb_rec_read bad magic 0x0 at offset=1111638594 tdb(/var/db/samba/locking.tdb): tdb_rec_read bad magic 0x42424242 at offset=1034396 which then prevents fileserving from working properly (N.B. the bad magic

Dear Samba friends, I have recently upgraded from Samba 3.0.36 to Samba 3.5.6. After upgrade I encounter the following error in log.smbd: [2011/06/03 10:09:43, 0] smbd/server.c:1119(main) smbd version 3.5.6 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 [2011/06/03 10:09:43.379106, 1] param/loadparm.c:7605(lp_do_parameter) WARNING: The "share modes" option is

Hello, Sorry for take so long to answer, but I was not able to do the tests because the computer is in use and out of my office. Finally I've progressed in this topic with realmd, sssd and autofs, but now I'm locked on mounting shares from my member server. I'm able to use autofs and smbclient to mount and connect to sysvol share on my DC server, but when I try to connect to my

Team, Few of my Redhat Hosts runs CPU at 100% due to winbind. Does anyone have script or any idea how to restart the winbind daemon if it consumes 100% CPU automatically? ~LA

Hi, I recently updated my Samba from 3.3 to 3.5, and while that worked fine, I can no longer access my shares - it asks for a password, which fails even if I do enter a correct one. Here is one of my shares - very simple, I think: [myshare] comment = My Share path = /path/to/myshare public = yes read only = yes writable = no browseable = yes printable = no guest ok = yes