My second node cannot access the repository

Elastic Stack Elasticsearch
1

My second node cannot access the repository, on every Elasticsearch.yml (node1 & node 2) I have the same line

path.repo: /home/lab/sambashare

On node 1 y created a shared folder with samba that's is located on /home/lab/sambashare and on node 2 y mounted that shared folder with "mount" on the same location ( /home/lab/sambashare)

Samba config here:

[sambashare]
comment= Network Shared Folder by Samba Server on Ubuntu
path = /home/lab/sambashare
force user = elasticsearch
force group = elasticsearch
create mask = 0664
force create mode = 0664
directory mask = 0775
force directory mode = 0775
public = yes
read only = no

So I confirmed I can create files on the folder and use it

That folder

I create the repository on kibana and verify the repository and I get that output

{
  "name": "ResponseError",
  "meta": {
    "body": {
      "error": {
        "root_cause": [
          {
            "type": "repository_verification_exception",
            "reason": "[LAB-PRACTICA] [[skQq2u8WTl6_1nzR7Lw0Qg, 'RemoteTransportException[[node-2][192.168.56.102:9300][internal:admin/repository/verify]]; nested: RepositoryVerificationException[[LAB-PRACTICA] store location [/home/lab/sambashare] is not accessible on the node [{node-2}{skQq2u8WTl6_1nzR7Lw0Qg}{unyajCp4RKu3bNIbWdXIzw}{192.168.56.102}{192.168.56.102:9300}{cdfhilmrstw}{ml.machine_memory=4122726400, xpack.installed=true, transform.node=true, ml.max_open_jobs=512, ml.max_jvm_size=2063597568}]]; nested: AccessDeniedException[/home/lab/sambashare/tests-4fcTigkMQ3GiZz-Nnzi-Dg/data-skQq2u8WTl6_1nzR7Lw0Qg.dat];']]"
          }
        ],
        "type": "repository_verification_exception",
        "reason": "[LAB-PRACTICA] [[skQq2u8WTl6_1nzR7Lw0Qg, 'RemoteTransportException[[node-2][192.168.56.102:9300][internal:admin/repository/verify]]; nested: RepositoryVerificationException[[LAB-PRACTICA] store location [/home/lab/sambashare] is not accessible on the node [{node-2}{skQq2u8WTl6_1nzR7Lw0Qg}{unyajCp4RKu3bNIbWdXIzw}{192.168.56.102}{192.168.56.102:9300}{cdfhilmrstw}{ml.machine_memory=4122726400, xpack.installed=true, transform.node=true, ml.max_open_jobs=512, ml.max_jvm_size=2063597568}]]; nested: AccessDeniedException[/home/lab/sambashare/tests-4fcTigkMQ3GiZz-Nnzi-Dg/data-skQq2u8WTl6_1nzR7Lw0Qg.dat];']]"
      },
      "status": 500
    },
    "statusCode": 500,
    "headers": {
      "x-opaque-id": "8e594919-bb10-41a6-a65d-168e30eaf676",
      "x-elastic-product": "Elasticsearch",
      "warning": "299 Elasticsearch-7.17.2-de7261de50d90919ae53b0eff9413fd7e5307301 \"Elasticsearch built-in security features are not enabled. Without authentication, your cluster could be accessible to anyone. See https://www.elastic.co/guide/en/elasticsearch/reference/7.17/security-minimal-setup.html to enable security.\"",
      "content-type": "application/json; charset=UTF-8",
      "content-length": "1383"
    },
    "meta": {
      "context": null,
      "request": {
        "params": {
          "method": "POST",
          "path": "/_snapshot/LAB-PRACTICA/_verify",
          "body": "",
          "querystring": "",
          "headers": {
            "user-agent": "elasticsearch-js/7.16.0-canary.7 (linux 5.4.0-107-generic-x64; Node.js v16.14.2)",
            "x-elastic-product-origin": "kibana",
            "x-opaque-id": "8e594919-bb10-41a6-a65d-168e30eaf676",
            "x-elastic-client-meta": "es=7.16.0p,js=16.14.2,t=7.16.0p,hc=16.14.2"
          },
          "timeout": 30000
        },
        "options": {},
        "id": 1
      },
      "name": "elasticsearch-js",
      "connection": {
        "url": "http://192.168.56.106:9200/",
        "id": "http://192.168.56.106:9200/",
        "headers": {},
        "deadCount": 0,
        "resurrectTimeout": 0,
        "_openRequests": 0,
        "status": "alive",
        "roles": {
          "master": true,
          "data": true,
          "ingest": true,
          "ml": false
        }
      },
      "attempts": 0,
      "aborted": false
    }
  }
}

Edit:
Every time i run the verify the repository on kibana, i get a new folder on the shared folder with 2 files -> master.dat and {folder name}.dat

2

Just to be sure regarding verification. Have you tried creating files/folders on the exact same host that Elasticsearch is running on as the user Elasticsearch is running at?

3

U mean make a "sudo login" as Elasticsearch user? I tried but i don't know the password

4

Indeed. It's important to exactly retry this before claiming 'it works', otherwise you are trying out a completely different thing.

5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.