The synchronization failure displayed on the primary node does not match that on the secondary node, and synchronization never completes. Why?

We have started a full resynchronization on the DRB secondary node.
Later, the primary DRBD node will indicate 100% synchronization status, but on the secondary node, the synchronization errors are still around 25 GB.

There are still bytes being received on the secondary node, which I can see from drbdtop on the secondary node. Also, the primary node is active and is used, and therefore the bytes received on node 2 may be the most recent writes.

This is the second attempt, and the same problem occurred the first time I tried to restart the DRBD service. Then the synchronization status returned to 0%. So it's scary that I can not even stop and start the DRBD service.

On node1 (primary node):

DRBDTOP v0.2.2 (kernel: v9.0.13; utils: v9.3.1; host: node1) - Details for opt_new
│Resource: opt_new: (Overall danger score: 1)                                                                                                            │
│ Local Disc(Primary):                                                                                                                                   │
│  volume 0 (/dev/drbd2): UpToDate(normal disk state)                                                                                                    │
│    size: 663.0GiB total-read:50.6GiB read/Sec:34.3MiB total-written:431.0MiB written/Sec:291.7KiB                                                      │
│                                                                                                                                                        │
│ Connection to node2(Secondary): Connected(connected to node2)                                                                                          │
│  volume 0:                                                                                                                                             │
│   Replication:SyncSource(synchronizing node2 with local data) 0.0% remaining   Inconsistent(data is not accessible or usable until resync is complete) │
│   Sent: total:431.0MiB Per/Sec:291.7KiB                                                                                                                │
│   Received: total:0.0KiB Per/Sec:0.0KiB                                                                                                                │
│   OutOfSync: current:0.0KiB average:0.0KiB min:0.0KiB max:0.0KiB                                                                                       │
│   PendingWrites: current:0.0 average:0.7 min:0.0 max:279.0                                                                                             │
│   UnackedWrites: current:0.0 average:0.0 min:0.0 max:0.0                                                                                               │

On node 2 (secondary node):

DRBDTOP v0.2.2 (kernel: v9.0.13; utils: v9.3.1; host: node2) - Details for opt_new
│Resource: opt_new: (Overall danger score: 18)                                                                                                           │
│ Local Disc(Secondary):                                                                                                                                 │
│  volume 0 (/dev/drbd2): Inconsistent(data is not accessible or usable until resync is complete)                                                        │
│    size: 663.0GiB total-read:0.0KiB read/Sec:0.0KiB total-written:494.8MiB written/Sec:282.9KiB                                                        │
│                                                                                                                                                        │
│ Connection to node1(Primary): Connected(connected to node1)                                                                              │
│  volume 0:                                                                                                                                             │
│   Replication:SyncTarget(local volume is being synchronized with data from node1) 3.8% remaining   UpToDate(normal disk state)                  │
│   Sent: total:0.0KiB Per/Sec:0.0KiB                                                                                                                    │
│   Received: total:494.8MiB Per/Sec:282.9KiB                                                                                                            │
│   OutOfSync: current:25.1GiB average:25.0GiB min:25.0GiB max:25.1GiB                                                                                   │
│   PendingWrites: current:0.0 average:0.0 min:0.0 max:0.0                                                                                               │
│   UnackedWrites: current:0.0 average:0.1 min:0.0 max:128.0                                                                                             │

The general hazard value shows 1 and 18 for primary and secondary. I do not know what that means.

But the following is funny. Peer disks indicate 1 and 17 on nodes 1 and 2, respectively. What does this number mean? Could it be the reason for the infinite synchronization:

DRBDTOP v0.2.2 (kernel: v9.0.13; utils: v9.3.1; host: node2)
┌◉ (LIVE UPDATING) Resource List─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│  Name      | Role      | Disks | Peer Disks | Connections | Overall | Quorum                                                                           │
│  opt_new   | Secondary | ✗ (1) | ✗ (17)     | ✓           | ✗ (18)  | ✓               

DRBDTOP v0.2.2 (kernel: v9.0.13; utils: v9.3.1; host: node1)
┌◉ (LIVE UPDATING) Resource List─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│  Name      | Role    | Disks | Peer Disks | Connections | Overall | Quorum                                                                             │
│  opt_new   | Primary | ✓     | ✗ (1)      | ✓           | ✗ (1)   | ✓                                                                                  │

7 – Node as a field in content type

I have one type of custom node named "Concerts" and another type named "Conductors". I would like to add a box to Concerts indicating which conductor conducted the concert. However, the field types I can choose from are just basic things like date, floating-point number, integer, text, etc. – nothing about references to other nodes.

The reason for this would be that I would assume that I would generate content such as "Conducted by this conductor" on the concert pages and "Concerts of this conductor" on the conductor pages.

Can I achieve this with a module? I have not found anyone who suits me.

I use Drupal 7.

Bitcoin server / node

My simple question is: Is a miner or node a server for Bicoin, such as a socket? Does anyone start mining / does he have a server? Because I think nobody can kill Btc because only 1 knot / miner is alive, Btc will be it So all Nodes / Miners are BTC simulated servers right?

theming – Determines the relative path to the node by title in a topic

Using Drupal 8: I want to get the relative path to a node through the Title field. Is that possible? Throughout the Twig documentation I found, the node id is used, for example:

Are there any other arguments that could be used instead of entity.node.canonical and {'node': 6 } to search for nodes with different parameters?

7 – Anonymous permissions with Node Access

  1. Content Type: Webform
  2. Permitted grants: View, Edit
  3. Permitted roles: Anon, authorized, admin

  1. Go to the Webform node, eg. Node / 20
  2. Click on the Grants tab
  3. Enable "Authenticated" and "Admin users can view", "Anonymous" is disabled
  4. The site is still accessed anonymously?

Node / 20:
Enter image description here

Global node access settings:
Enter image description here
At the bottom of Webform, for anon / authenticated / admin, the Show check box is selected, because anonymous users should by default show all web forms except those who need to be logged in page ?!

Database – 8 – To create a query node that queries content with more than one comment

Consider this example:

  $query = Drupal::entityTypeManager()->getStorage('node')->getQuery();
  $nids = $query->condition('type', 'question')
    ->condition('status', 1)
    ->condition('field_category', $tid)
    ->sort('created', 'DESC')
  $questions = Drupal::entityTypeManager()->getStorage('node')->loadMultiple($nids);

I just want to query the questions with answers. (these are comments)
I was hoping to add ->condition('comment_node_question.0.comment_count', '0', '>') would work, but no luck.

java – How do I get a bounding box from the accessibilty node information?

I'm trying to fetch screen boundaries of a particular node in my Accessibilty service with getBoundsInScreen (), but every time an empty response is returned, I just want to retrieve the boundaries of a node and draw into a rectangular bounding box at that position in my app
Here is my code:

private fun printAllViews(mNodeInfo: AccessibilityNodeInfo?) {
        if (mNodeInfo == null) return
        var log = ""
        log +=  mNodeInfo.getBoundsInScreen(Rect(0,0,0,0))
        Log.d("hmm", log)
        if (mNodeInfo.childCount < 1) return
        for (i in 0 until mNodeInfo.childCount) {

here, if I do it nodeinfo.gettext() It successfully gives me the text back, but not the limits. My question is, how can I get that?

In the Docker Selenium node can not be registered in the Selenium hub

I am trying to register a selenium node for the selenium hub in a Docker container, but get the following exception

INFO (SelfRegisteringRemote $ – Could not register this node: Failed to submit enrollment request: Selenium Hub

INFO (SelfRegisteringRemote $ – Could not register this node: The hub has failed or does not respond: Selenium Hub

INFO (SelfRegisteringRemote $ – Could not register this node: The hub has failed or does not respond: Selenium Hub: Name or service unknown

I tried the following Docker commands

$ docker run -d -net = host -p 4444: 4444 –name selenium hub selenium / hub

$ docker run -d -net host -e HUB_HOST = selenium hub – name selenium node selenium / node chrome

but if I change the –net = host to –net = my-grid-name, I am able to see that node gets registered to the hub

Please let me know why I can not register the node for the hub with the –net = host option

Locate the logs for the Docker node

2019-09-17 12: 45: 50,106 INFO Contains the additional file "/etc/supervisor/conf.d/selenium.conf" during parsing
2019-09-17 12: 45: 50,107 The INFO supervisor started with PID 7
2019-09-17 12: 45: 51,095 INFO generates: & # 39; xvfb & # 39; with pid 10
2019-09-17 12: 45: 51,097 INFO generates: & # 39; Selenium node & # 39; with PID 11
Connects to the hub through the host selenium hub and port 4444
2019-09-17 12: 45: 51,141 INFO Success: xvfb has entered the status RUNNING, the process is in operation for more than 0 seconds (start seconds)
2019-09-17 12: 45: 51,142 INFO Success: Selenium node in RUNNING state, process in operation for more than 0 seconds (start seconds)
12: 45: 51.295 INFO (GridLauncherV3.parse) – Selenium server version: 3.141.59, revision: e82be7d358
12: 45: 51.373 INFO (GridLauncherV3.lambda $ buildLaunchers $ 7) – Starting a Selenium Grid node on port 5555
2019-09-17 12: 45: 51.432: INFO :: main: Logging initialized at 285 ms under org.seleniumhq.jetty9.util.log.StdErrLog
12: 45: 51.582 INFO (WebDriverServlet.) – WebDriverServlet is being initialized
12: 45: 51.633 INFO (SeleniumServer.boot) – Selenium Server is running on port 5555
12: 45: 51.633 INFO (GridLauncherV3.lambda $ buildLaunchers $ 7) – The Selenium Grid node is active and can be registered in the Hub
12: 45: 51.663 INFO (SelfRegisteringRemote $ – Starts the auto-registration thread. Will try to register every 5000 ms.
12: 45: 51.818 WARN (SelfRegisteringRemote.registerToHub) – Error retrieving parameters from the hub. The node may have an incorrect timeout. Selenium hub: name or service unknown
12: 45: 51.818 INFO (SelfRegisteringRemote.registerToHub) – Register the node in the hub: http: // selenium hub: 4444 / grid / register
12: 45: 51.825 INFO (SelfRegisteringRemote $ – This node could not be registered: Failed to submit enrollment request: Selenium Hub

bitcoind – How to Separate the Wallet from the Bitcoin Core | Run multiple wallets on different servers on a single Bitcoin node

I'm using a Bitcoin full node on a central server. I have many web applications that run in different places. I want to connect these web applications to a central full bitcoin node. To install Wallet in these web application servers connected to a central Bitcoin full node. I would like to use the wallet to generate an address in these web application servers, perform transactions, and independently sign and send transactions to the application server. The application server must communicate with the wallet via rest apis. Finally, this scrapped transaction should be sent to a central Bitcoin full node. How do you do that?

8 – How do I extend a specific node type form?

I'm looking for a way to override that NodeForm to get one class per bundle.

Indeed EntityForm manages the form for all entities.
NodeForm extends it and manages the forms for all nodes.

I enrolled CustomNodeForm replace NodeForm Behavior for all nodes.

 * Implements hook_entity_type_build().
function ftvisi_main_entity_type_build(array &$entity_types) {
  $entity_types('node')->setFormClass('default', CustomNodeForm::class);

Now I want to get a class per bundle that extends that CustomNodeForm but I do not feel able to do it.

CustomNodeForm Maybe a form is instantiated for each bundle – but I do not like this approach and we still have only one constructor that can cause problems like:

"OK, my first bundle form needs this service, and my second bundle form needs another. Should I inject the full container myself and then use services on the fly?" => Pretty bad idea, I know.

Anyway, if CustomNodeForm instantiating other classes themselves, it will be difficult to mock and test. I definitely do not like this approach.

I then thought about using the form modes, but the same problem: A form mode can be used for any node type, so we still do not have a class per bundle and only one constructor for all forms that use this form mode.

Any idea to help?