search for: public_addresses

...b status 2014/08/16 15:32:03.248034 [23255]: client/ctdb_client.c:267 Failed to connect client socket to daemon. Errno:Connection refused(111) common/cmdline.c:156 Failed to connect to daemon 2014/08/16 15:32:03.261221 [23255]: Failed to init ctdb /etc/default/ctdb CTDB_NODES=/etc/ctdb/nodes CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=yes CTDB_SYSLOG=yes CTDB_DEBUGLEVEL=NOTICE CTDB_SOCKET=/usr/local/var/run/ctdb/ctdbd.socket /usr/local/samba/etc/smb.conf [global] workgroup = ALTEA realm = ALTEA.SITE security = ADS kerberos method = secrets and keytab netbios name = SMBCLUSTER disab...

...Takeover run unsuccessful Node 0 reached 4 banning credits - banning it for 300 seconds Banning node 0 for 300 seconds Unassigned IP 10.206.2.124 can be served by this node Unassigned IP 10.200.1.230 can be served by this node IP 10.206.2.124 incorrectly on an interface Last night we truncated the public_addresses file, then everything started working. And so we've been rereading the doc on the public addresses file. So it may be we have gravely misunderstood the *public_addresses* file, we never read that part of the documentation carefully. The *nodes* file made perfect sense, and the point we missed...

...d to read nodes file "/usr/local/samba/etc/ctdb/nodes" 2018/05/07 12:56:44.363546 ctdbd[4503]: Failed to load nodes file "/usr/local/samba/etc/ctdb/nodes" I thought, thats nice, lets create some config files like: /usr/local/samba/etc/ctdb/*nodes* /usr/local/samba/etc/ctdb/*public_addresses* **** /usr/local/samba/etc/ctdb/*ctdbd.conf* After creation, i tried to start CTDB: /usr/local/samba/sbin/ctdbd First I thought it works, but CTDB ignored my ctdbd.conf and public_addresses files. logfile shows: ################################################################################...

...amba/etc/ctdb/nodes" > 2018/05/07 12:56:44.363546 ctdbd[4503]: Failed to load nodes file > "/usr/local/samba/etc/ctdb/nodes" > > I thought, thats nice, lets create some config files like: > > /usr/local/samba/etc/ctdb/*nodes* > > /usr/local/samba/etc/ctdb/*public_addresses* > **** > > /usr/local/samba/etc/ctdb/*ctdbd.conf* > > After creation, i tried to start CTDB: > > /usr/local/samba/sbin/ctdbd > > First I thought it works, but CTDB ignored my ctdbd.conf and > public_addresses files. > > logfile shows: > > ##########...

Hi All, I''ve been trying to use Hiera for node classification, my sit.pp is simple: node default { hiera_include("classes") } which has been working well with simple class definitions like: user@host$ cat testagent.yaml 2012-06-18 14:55:48 jon pts/13 --- classes: - motd Is anyone doing this in production? I''ve seen a little about this on line but it

> we point them to somedom.contoso.com which is then > resolved to both and the client can pick I want to avoid Round-Robin DNS > You cannot use CTDB with AD DCs You can. /etc/ctdb/nodes 192.168.30.11 192.168.30.12 /etc/ctdb/public_addresses 192.168.30.10/24 ens18 /etc/ctdb/events/legacy/20.samba-ad.script #!/usr/bin/env bash function monitor_ldap() { ldbsearch -H ldap://127.0.0.1 -s base -b "" vendorName 2>/dev/null | grep -qi samba if [[ $? -eq 0 ]]; then return 0 else echo "ldbsearch receive...

...quot;kl01.amtb-m.org.my" routes_enp2s0="default via 192.168.11.10" routes_enp2s2="default via 192.168.11.10" routes_enp2s3="default via 192.168.11.10" routes_enp2s4="default via 192.168.11.10" */etc/conf.d/ctdb* CTDB_RECOVERY_LOCK=/amtb/.ctdb.lock CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=yes CTDB_SAMBA_SKIP_SHARE_CHECK=yes CTDB_NFS_SKIP_SHARE_CHECK=yes CTDB_MANAGES_WINBIND=yes CTDB_MANAGES_VSFTPD=no CTDB_MANAGES_ISCSI=no CTDB_MANAGES_NFS=no CTDB_MANAGES_HTTPD=no CTDB_SYSLOG=yes CTDB_DEBUGLEVEL=NOTICE CTDB_INIT_STYLE= CTDB_SERVICE_SMB=sa...

Could I impose upon someone to provide some guidance? Some hint? Thank you Is a shared file system actually required? If etcd is used to manage the global recovery lock, is there any need at that point for a shared file system? In other words, are there samba or CTDB files (state) that must be on a shared file system, or can each clustered host simply have these files locally? What must be

...ess you know exactly what you are # doing. # # Please see the RECOVERY LOCK section in ctdb(7) for more # details. # # recovery lock = !/bin/false RECOVERY LOCK NOT CONFIGURED recovery lock = /mnt/audio/.ctdb/recovery_lock ^ /mnt/audio is the CephFS mount I am reexporting. CTDB has a single IP in public_addresses that is moving around between the gateway nodes as expected--from what I can tell that is all working well. The only other issue I've identified is that I seem to have to create the user (and set the password with smbpasswd) on each of the gateways... even though I expected that the 'passd...

...ers. gluster volume info <- is OK on both machines ctdb status <- is OK on both machines wbinfo -t <- is OK on both machines net ads info <- is OK on both machines /etc/sysconfig/ctdb CTDB_RECOVERY_LOCK=/media/gluster/system/ctdblockfile CTDB_NODES=/media/gluster/system/nodes #CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses #CTDB_MANAGES_SAMBA=yes #CTDB_MANAGES_WINBIND=yes # CTDB_MANAGES_NFS=yes ulimit -n 10000 CTDB_LOGFILE=/var/log/log.ctdb CTDB_SYSLOG=no CTDB_DEBUGLEVEL=NOTICE /etc/ctdb/nodes 192.168.10.232 192.168.10.233 I do not use /etc/ctdb/public_addresses because I do not want HA or...

Hi Bob, On Thu, 6 Aug 2020 06:55:31 -0400, Robert Buck <robert.buck at som.com> wrote: > And so we've been rereading the doc on the public addresses file. So it may > be we have gravely misunderstood the *public_addresses* file, we never read > that part of the documentation carefully. The *nodes* file made perfect > sense, and the point we missed is that CTDB is using floating > (unreserved/unused) addresses and assigning them to a SECOND public > interface (aliases). We did not plan a private subnet fo...

...first enable the events and then start ctdb. In both cases ctdb will start and it's working. The only difference between my test environment and the production system is, that I have two server with Ubuntu and one with Debian, BUT both with the same sernet-packages, and the same nodes- and public_addresses-files. Still ctdb is running IP-failover works, but as soon I enable one of the events there is no way to get ctdb restarting again.

Hi Stefan, On 1/27/23 16:16, Stefan Kania wrote: > The only difference between my test environment and the production > system is, that I have two server with Ubuntu and one with Debian, BUT > both with the same sernet-packages, and the same nodes- and > public_addresses-files. Still ctdb is running IP-failover works, but as > soon I enable one of the events there is no way to get ctdb restarting > again. in the case of runnig different distributions in one cluster, it's required to set "allow unsafe cluster upgrade = yes". This is required,...

I am using asterisk 1.8.3. I am getting this error: [Mar 15 09:49:12] NOTICE[1049]: chan_sip.c:21358 handle_request_invite: Call from 'mndemo_to_vizioconfrm104' to extension '1104' rejected because extension not found in context 'smvoice-mediaport'. "dialplan show" gives me that the context is present: [ Context 'smvoice-mediaport' created by

All, I have a 3 node CTDB cluster which serves 4 'public addresses'. /etc/ctdb/public_addresses file is node specific and present in the above path in participating nodes. All the nodes run RHEL 6.2. Other ctdb config files such as "nodes" and "public_addresses" are placed on a shared filesystem mounted on a known location (say, /gluster/lock) On starting CTDB service in...

I am attempting to enable IPv6 on our CTDB setup. I have placed the IPv6 address in the public_addresses file with the correct prefix. The addresses never come up and I recieve these messages in the log 2012/06/28 10:54:43.313227 [ 1820]: Async operation failed with ret=0 res=1 opcode=0 2012/06/28 10:54:43.313918 [ 1820]: Async operation failed with ret=0 res=1 opcode=0 2012/06/28 10:54:43.313929...

drbd ctdb ocfs2 Hi Everything seems OK apart from the IP takeover. public_addresses 192.168.1.80/24 enp0s3 192.168.1.81/24 enp0s3 ctdb status Number of nodes:2 pnn:0 192.168.1.10 PARTIALLYONLINE pnn:1 192.168.1.11 PARTIALLYONLINE (THIS NODE) Generation:2090727463 Size:2 hash:0 lmaster:0 hash:1 lmaster:1 Recovery mode:NORMAL (0) Recovery master:1 but we are getting: 2014/...

.... I installed on my Centos 5.3 sernet package samba 3.5.2. Also working well. But after setting up ctdb and samba und running it my two nodes freezing for a while And ctdb and samba are down again. On Both nodes My /etc/sysconfig/ctdb: CTDB_RECOVERY_LOCK="/cluster/recovery/recovery" CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=yes ulimit -n 10000 CTDB_NOTIFY_SCRIPT=/etc/ctdb/notify.sh CTDB_DBDIR=/var/ctdb CTDB_DBDIR_PERSISTENT=/var/ctdb/persistent CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d CTDB_SOCKET=/tmp/ctdb.socket CTDB_TRANSPORT="tcp" CTDB_MONITOR_FREE_MEMORY=100...

...again oss02:~ # ctdb enable -n 1 `/bin/ls.exe' -> `ls.4539.exe' `/bin/ls.exe' -> `ls.4540.exe' My config is: oss02:/ # perl -ne '/^#|^\s*$/ and next;print' /etc/sysconfig/ctdb CTDB_RECOVERY_LOCK="/net/lmd01/space/ctdb.lock" CTDB_PUBLIC_INTERFACE=eth3 CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_LVS_PUBLIC_IP=10.200.180.180 CTDB_NODES=/etc/ctdb/nodes CTDB_DBDIR=/var/ctdb CTDB_DBDIR_PERSISTENT=/var/ctdb/persistent CTDB_LOGFILE=/var/log/ctdb.log CTDB_DEBUGLEVEL=1 oss02:/ # cat /etc/ctdb/public_addresses 10.200.180.181/16 10.200.180.182/16 10.200.180.183/16 o...

ok switching to "Console/default" does show the text --- <("<) --- Call to device 'default' on console from 'default' <2564286000> --- (>")> --- --- <("<) --- Auto-answered --- (>")> --- However I don't hear any audio. Thanks Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: