search for: unhealthy

...fficulty with getting a table to show with multiple rows and columns. Below is the commands that I've typed in and errors that I am getting. Thank you. Laura Table trying to enter: Diet: Binger-yes: Binger-No: Total: None 24 134 158 Healthy 9 52 61 Unhealthy 23 72 95 Dangerous 12 15 27 > diet=matrix(c(24,134,9,52,23,72,12,15),ncol=4,byrow=TRUE) > rownames(diet)=c("none", "healthy", "unhealthy", "dangerous") Error in dimnames(x) <- dn : length of 'dimnames' [1] not equal to array extent &gt...

RH 7.2 using samba 2.2.7 (installed from samba built RPM) for now... Security=domain using winbind to authenticate against windows PDC. Testparm says: winbind uid = 10000-20000 winbind gid = 10000-20000 template homedir = /home/%D/%U template shell = /bin/false winbind separator = + winbind cache time = 15 winbind enum users = No

Hi, I have a table in R with data I needed and need to create a contingency table out of it. The table I have so far looks like this: Binger r DietType No Yes Dangerous 15 12 Healthy 52 9 None 134 24 Unhealthy 72 23 These are the error messages that I keep getting whenever I try to get a contingency table. I'm not sure why it won't work for me, any help would be appreciated! > nametable<-table(excat,recat) Error in table(excat, recat) : object 'excat' not found [[a...

...pt to set up a cluster, I'm reading around and see some howto writers would say to put "private dir on the FS cluster" - one question I have: is this correct? necessary? I have partial success, I get: $ ctdb status Number of nodes:2 pnn:0 10.5.6.32 OK pnn:1 10.5.6.49 UNHEALTHY (THIS NODE) Generation:323266562 Size:2 hash:0 lmaster:0 hash:1 lmaster:1 Recovery mode:NORMAL (0) Recovery master:0 I use: passdb backend = ldapsam:"ldapi:///var/run/ldapi" idmap backend = ldap:"ldapi:///var/run/ldapi" and on that one "unhealthy" node I see:...

...db status. All nodes are "OK" and connected. To test the failover behaviour, I brought down one of the nodes. "ctdb status" when run on one of the (up) nodes gave the following status, [root@<nodename>~]# ctdb status Number of nodes:4 pnn:0 x.y.z.a DISCONNECTED|BANNED|UNHEALTHY|INACTIVE pnn:1 x.y.z.b BANNED|UNHEALTHY|INACTIVE (THIS NODE) pnn:2 x.y.z.c DISCONNECTED|UNHEALTHY|INACTIVE pnn:3 x.y.z.d OK Generation:INVALID Size:3 hash:0 lmaster:0 hash:1 lmaster:1 hash:2 lmaster:3 Recovery mode:RECOVERY (1) Recovery master:3 In the above (edited) output, pnn: 2 is the...

Hi, I?ve setup a simple ctdb cluster. Actually copied the config file from an existing system. Thats what happens: Node 1, alone Number of nodes:2 pnn:0 10.0.0.1 OK (THIS NODE) pnn:1 10.0.0.2 DISCONNECTED|UNHEALTHY|INACTIVE Generation:1369816268 Size:1 hash:0 lmaster:0 Recovery mode:NORMAL (0) Recovery master:0 Node1, after start of ctdb on Node 2 Number of nodes:2 pnn:0 10.0.0.1 OK (THIS NODE) pnn:1 10.0.0.2 UNHEALTHY Generation:1369816268 Size:1 hash:0 lmaster:0 Recovery mode:NORMAL (0) Re...

...: 49.winbind: could not ping winbindd! 2023-01-26T16:14:30.603458+01:00 glfs3 ctdb-eventd[15763]: 49.winbind: Ping to winbindd failed 2023-01-26T16:14:30.603580+01:00 glfs3 ctdbd[15762]: monitor event failed - disabling node 2023-01-26T16:14:30.604273+01:00 glfs3 ctdbd[15762]: Node became UNHEALTHY. Ask recovery master to reallocate IPs 2023-01-26T16:14:31.302861+01:00 glfs3 ctdb-recoverd[15867]: Disabling takeover runs for 60 seconds 2023-01-26T16:14:31.323234+01:00 glfs3 ctdbd[15762]: Release of IP 192.168.0.227/24 on interface ens18 node:0 2023-01-26T16:14:31.409901+01:00 glfs3 ct...

Hi, I was wondering if anyone could provide me with help in entering the attached dataset into R? I've been having a hard time in trying to figure out how to assemble it into both a frequency table and a bar graph within R. I've been trying to present the way I have the data arranged in Excel Spreadsheet into R. I am uncertain what the correct commands and exact techniques are into

...ling List - Non-Commercial Discussion > Subject: Re: [Asterisk-Users] What is acceptable network latency for > voipconnection? > > Well there is nothing much you can do if you don't own all the routes. > But in > concept you can, and this is purely just theoritical and a very unhealthy > thing for the Internet, is to write a program running on your router that > constantly streams traffic to your end point, this will maintain a > constant > bandwidth from your network to your far-end. Then, your program should > detect > within a few ms that you are setting a c...

...g Debian Buster, with Lustre+ZFS as the clustered file system for the recovery lock, and using upstream's Samba and CTDB. The lustre clients are mounted with flock, and I've confirmed the lock is being held with `lslock`. Here is the debug information from the "healthy node" (the unhealthy one just says it can't take the lock as it is under contention, so I thought it would be of little use): https://drive.google.com/drive/folders/1yzFdwGKfDAHiVbsj7pcOe-jX4KHpFO2U?usp=sharing Best regards and thank you all for your time, Christian -- <https://opendrives.com/wp-content/upl...

...und and see > some howto writers would say to put "private dir on the FS > cluster" - one question I have: is this correct? necessary? > > I have partial success, I get: > > $ ctdb status > Number of nodes:2 > pnn:0 10.5.6.32 OK > pnn:1 10.5.6.49 UNHEALTHY (THIS NODE) > Generation:323266562 > Size:2 > hash:0 lmaster:0 > hash:1 lmaster:1 > Recovery mode:NORMAL (0) > Recovery master:0 > > I use: > passdb backend = ldapsam:"ldapi:///var/run/ldapi" > idmap backend = ldap:"ldapi:///var/run/ldapi" >...

Hi, I've been involved in developing a fairly complex site at http://tilt.ft.com recently, and have acquired an unhealthy interest in faceting. I couldn't find any good non-academic guides to faceting strategy on the web, so I thought I'd have a stab at writing one. I'm not completely happy with it, but it's been sitting in my drafts for long enough that I thought it worth at least putting it out...

...file!!!: /etc/sysconfig/ctdb. I had to use my old one. After starting ctdb recognizing that ctdb wants his state directory in /usr/local/var/ctdb/state I could not fix that in /etc/sysconfig/ctdb file. So I had do mkdir /usr/local/var/ctdb manually. After starting ctdb on both nodes all nodes rest unhealthy. And my public addresses rest [-1]!? In my log file I find, ERROR: No link on the public network interface eth0 Or, 2010/05/20 09:36:14.767144 [31866]: server/ctdb_takeover.c:162 public address '192.168.134.101' now unassigned (old iface '__none__' refs[0]) 2010/05/20 09:36:14.767...

...server coming up > in a few weeks. I think I will implement that. Thank you! There are pros and cons to an easy recovery mechanism. Sure, at first it eases the life of the people who manage the system, but some users may start relying to heavily on the recovery service, in a way that becomes unhealthy, back-up being used as a secondary storage instead of being what it is meant to be: a back-up. That is why I rather beleive in a strong policy that defines what are the valid motives for restoration: crashes, etc. (reckless file deletion not being a valid one) and a loosy enforcement of the policy...

...> 2023-01-26T16:14:30.603458+01:00 glfs3 ctdb-eventd[15763]: 49.winbind: > Ping to winbindd failed > > 2023-01-26T16:14:30.603580+01:00 glfs3 ctdbd[15762]: monitor event > failed - disabling node > > 2023-01-26T16:14:30.604273+01:00 glfs3 ctdbd[15762]: Node became > UNHEALTHY. Ask recovery master to reallocate IPs > > 2023-01-26T16:14:31.302861+01:00 glfs3 ctdb-recoverd[15867]: Disabling > takeover runs for 60 seconds > > 2023-01-26T16:14:31.323234+01:00 glfs3 ctdbd[15762]: Release of IP > 192.168.0.227/24 on interface ens18 node:0 > > 2...

...ice outage until the administrator has manually performed IP failover to replacement nodes using the 'ctdb moveip' command. NoIPFailback Default: 0 When set to 1, ctdb will not perform failback of IP addresses when a node becomes healthy. When a node becomes UNHEALTHY, ctdb WILL perform failover of public IP addresses, but when the node becomes HEALTHY again, ctdb will not fail the addresses back. Use with caution! Normally when a node becomes available to the cluster ctdb will try to reassign public IP addresses onto the new node as...

Hi everybody, I just updated my ctdb node from Samba version 4.9.4-SerNet-Debian-11.stretch to Samba version 4.9.8-SerNet-Debian-13.stretch. After restarting the sernet-samba-ctdbd service the node doesn't come back and remains in state "UNHEALTHY". I can find that in the syslog: May 16 11:25:40 ctdb-lbn1 ctdb-eventd[13184]: 50.samba: samba not listening on TCP port 445 May 16 11:25:40 ctdb-lbn1 ctdb-eventd[13184]: monitor event failed May 16 11:25:42 ctdb-lbn1 ctdb-eventd[13184]: 50.samba: samba not listening on TCP port 445 May 16 1...

...le > > network latency for > > > voipconnection? > > > > > > Well there is nothing much you can do if you don't > > own all the routes. > > > But in > > > concept you can, and this is purely just > > theoritical and a very > > unhealthy > > > thing for the Internet, is to write a program > > running on your router > > that > > > constantly streams traffic to your end point, this > > will maintain a > > > constant > > > bandwidth from your network to your far-end. > > Then...

...e:0 2015/05/18 14:24:23.375257 [ 6031]: Async wait failed - fail_count=1 2015/05/18 14:24:23.375263 [ 6031]: server/ctdb_takeover.c:1475 Async control CTDB_CONTROL_RELEASE_IP failed. We saw a different pattern yesterday when the smb.conf was edited ahead of the path being created and node 0 became unhealthy for a moment. Node 0: 2015/05/18 14:24:17.694058 [ 5972]: ERROR: samba directory /path/to/directory" not available 2015/05/18 14:24:17.694435 [ 5972]: Node became UNHEALTHY. Ask recovery master 0 to perform ip reallocation 2015/05/18 14:24:23.375195 [ 6031]: client/ctdb_client.c:759 control t...

...next switch label. This kind of mistake is sometimes difficult to spot by manual code examination, and the compiler can't provide any help either. It's common to mark fall-through locations with a comment, but parsing comments would incur a significant performance penalty and is probably an unhealthy approach overall. So the use of comment-only annotations is limited to manual inspections. Some time ago I've added the 'Unintended fall-through in switch statement' diagnostics to clang ( http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20120430/057180.html ). This is a pro...