Displaying 20 results from an estimated 300 matches similar to: "CTDB startup issue"
2020 Nov 05
0
CTDB startup issue
Hi Bob,
On Fri, 23 Oct 2020 16:40:10 -0400, Robert Buck via samba
<samba at lists.samba.org> wrote:
> We've only seen this error once, just occurred. We were having domain join
> issues.
>
> Enter ******@*******.local's password:
> ../../source3/lib/dbwrap/dbwrap_ctdb.c:855 ERROR: new_seqnum[10] !=
> old_seqnum[8] + (0 or 1) after failed TRANS3_COMMIT - this
2018 Sep 18
4
CTDB potential locking issue
Hi All
I have a newly implemented two node CTDB cluster running on CentOS 7, Samba
4.7.1
The node network is a direct 1Gb link
Storage is Cephfs
ctdb status is OK
It seems to be running well so far but I'm frequently seeing the following
in my log.smbd:
[2018/09/18 19:16:15.897742, 0]
> ../source3/lib/dbwrap/dbwrap_ctdb.c:1207(fetch_locked_internal)
> db_ctdb_fetch_locked for
2018 Sep 19
3
CTDB potential locking issue
Hi Martin
Many thanks for the detailed response. A few follow-ups inline:
On Wed, Sep 19, 2018 at 5:19 AM Martin Schwenke <martin at meltin.net> wrote:
> Hi David,
>
> On Tue, 18 Sep 2018 19:34:25 +0100, David C via samba
> <samba at lists.samba.org> wrote:
>
> > I have a newly implemented two node CTDB cluster running on CentOS 7,
> Samba
> > 4.7.1
2014 Aug 15
1
smbd crash: 4.1.11
Hi
Random crashes. It looks as if it's cups, but we aren't printing, nor
have it configured.
[global]
workgroup = ALTEA
realm = ALTEA.SITE
security = ADS
kerberos method = secrets and keytab
netbios name = SMBCLUSTER
#disable netbios = Yes
clustering = Yes
ctdbd socket = /usr/local/var/run/ctdb/ctdbd.socket
[users]
path = /cluster/users
read only = No
[profiles]
path = /cluster/profiles
2010 Apr 30
1
Winbind issues with CTDB
I am attempting to configure a Samba cluster using DRBD and CTDB. I am
currently having some issues with winbind. Everytime I start winbind or
attempt to join my server to the domain the machine stalls and the ctdb
error log is filled with the following:
2010/04/30 14:49:59.367076 [ 8394]: server/ctdb_control.c:445 Unknown CTDB
control opcode 119
I have not been able to find a description of
2020 Jul 23
2
vfs_shadow_copy2: permission denied - SMB_VFS_NEXT_OPENDIR() failed for '/snapshots'
Hello. I am trying to get the windows "previous versions" / shadow copies
to work with our setup (samba+winbind over objectivefs).
I have setup a test where I manually mounted two objectivefs snapshots in
the /snapshots/ directory. Objectivefs filesystem is mounted on /ofs. When
I try and look at the "previous version" in windows I get the error "there
are no previous
2018 Sep 19
0
CTDB potential locking issue
Hi David,
On Tue, 18 Sep 2018 19:34:25 +0100, David C via samba
<samba at lists.samba.org> wrote:
> I have a newly implemented two node CTDB cluster running on CentOS 7, Samba
> 4.7.1
>
> The node network is a direct 1Gb link
>
> Storage is Cephfs
>
> ctdb status is OK
>
> It seems to be running well so far but I'm frequently seeing the following
>
2018 Sep 18
0
CTDB potential locking issue
How did you mount your cephfs filesystem?
Am 18. September 2018 20:34:25 MESZ schrieb David C via samba <samba at lists.samba.org>:
>Hi All
>
>I have a newly implemented two node CTDB cluster running on CentOS 7,
>Samba
>4.7.1
>
>The node network is a direct 1Gb link
>
>Storage is Cephfs
>
>ctdb status is OK
>
>It seems to be running well so far but
2018 Sep 19
0
CTDB potential locking issue
Hi Martin
I just found the file, it's a config file that about 250 hosts read every
half an hour so it makes sense this is getting some contention. However,
the strange thing is, the share the file is in is a read-only share:
[dist$]
comment = Windows dist
path = /path/to/share
wide links = Yes
browseable = Yes
read only = Yes
guest only = Yes
2020 Sep 29
2
[CTDB] "use mmap = no" Causes wibind to fail
Hello all,
I'm currently running samba on debian buster, version 2:4.9.5+dsfg-5 with
lustre 2.13.0.
The problem I'm experiencing is pretty straightforward, if I set "use mmap
= no" in my global config (as suggested by the wiki), winbind fails to
start and the cluster grinds to a halt. Here is the error messages from
systemd:
Sep 28 22:14:17 tenzin systemd[1]: Starting Samba
2011 Jul 15
0
S3 and CTDB errors in logs
I am seeing these errors every night in the logs. Should I be worried
about any of them? The only thing I have noticed is slow log ons.
Jonn
CentOS 5.6 x86_64
Samba 3.5.8
CTDB 1.0.114
DRBD/GVFS
--------------------- samba Begin ------------------------
**Unmatched Entries**
auth/token_util.c:525(debug_nt_user_token) NT user token: (NULL) : 1 Time(s)
2020 Nov 19
0
PANIC outstanding aio + key does not exist
Our samba server in ap-east-1 is running very slow today
I noticed three things in log.smb, and I don't understand any of them
----------
#1 roughly every 80 seconds what appears to be a reconnect loop
[2020/11/19 17:35:46.283315, 2]
../../source3/lib/tallocmsg.c:87(register_msg_pool_usage)
Registered MSG_REQ_POOL_USAGE
[2020/11/19 17:35:46.287132, 1]
2015 May 19
0
ctdb_client.c control timed out - banning nodes
Hello,
We are using CTDB / Samba to serve a number of windows users, at this point around 1200. We have a 4 node CTDB setup.
CTDB version - ctdb-1.0.114.7-1
Samba Version - sernet-samba-4.1.16-10
In recent months we've seen a big problem when 1 of the CTDB nodes is stopped or disconnected either manually or resulting from a problem. On some occasions, all other nodes get banned if a node
2003 Jul 16
0
LDAP and Multiple Samba Hosts Issue
OK, I'm trying to get Samba working with LDAP. And I have it... sort of.
I have a Samba server TESTBOX, and I can authenticate to it just fine.
It seems taht if I change the "netbios name" (which I was doing to
simulate "connecting from some other samba server in our network"), I
get:
$ smbclient //FS01/files 'foo' -U dballing -I
testbox.byramhealthcare.com -N
2017 Sep 21
4
[Announce] Samba 4.7.0 Available for Download
======================================================
"Debugging is like being the detective
in a crime movie where you are also
the murderer."
Filipe Fortes
======================================================
Release Announcements
---------------------
This is the first stable release of Samba 4.7.
Please read the release notes carefully before upgrading.
UPGRADING
2017 Sep 21
4
[Announce] Samba 4.7.0 Available for Download
======================================================
"Debugging is like being the detective
in a crime movie where you are also
the murderer."
Filipe Fortes
======================================================
Release Announcements
---------------------
This is the first stable release of Samba 4.7.
Please read the release notes carefully before upgrading.
UPGRADING
2016 Jun 07
0
[Announce] Samba 4.4.4 Available for Download
======================================================
"Service to others is the rent
you pay for your room here on
earth."
Muhammad Ali
======================================================
Release Announcements
---------------------
This is the latest stable release of Samba 4.4.
Changes since 4.4.3:
--------------------
o Michael Adam <obnox at samba.org>
2016 Jun 07
0
[Announce] Samba 4.4.4 Available for Download
======================================================
"Service to others is the rent
you pay for your room here on
earth."
Muhammad Ali
======================================================
Release Announcements
---------------------
This is the latest stable release of Samba 4.4.
Changes since 4.4.3:
--------------------
o Michael Adam <obnox at samba.org>
2016 Jun 06
2
Samba AD member lost domain join after reboot
Hello,
After each reboot, my Samba AD member server lost domain join after
reboot, I have to re-enter the server in the domain with the "net ads
join -U administrator".
I use version 4.4.3 of samba.
The domain controller is a Samba AD server.
After reboot, when I exectute "net ads testjoin" I have:
kerberos_kinit_password SMB2$@AD.SAMDOM.LOCAL failed: failed
2017 Jul 25
0
[Announce] Samba 4.7.0rc3 Available for Download
Release Announcements
=====================
This is the third release candidate of Samba 4.7. This is *not*
intended for production environments and is designed for testing
purposes only. Please report any defects via the Samba bug reporting
system at https://bugzilla.samba.org/.
Samba 4.7 will be the next version of the Samba suite.
UPGRADING
=========
smbclient changes
-----------------