Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] FoxxMD - elasticsearch

Featured Replies

Even after adding the labels and changing the perms, v8 still won't run:

 

{"@timestamp":"2023-08-22T13:50:46.792Z", "log.level":"ERROR", "message":"fatal exception while booting Elasticsearch", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"main","log.logger":"org.elasticsearch.bootstrap.Elasticsearch","elasticsearch.node.name":"c02e0ef699aa","elasticsearch.cluster.name":"docker-cluster","error.type":"java.lang.IllegalStateException","error.message":"Cannot start this node because it holds metadata for indices created with version [6.6.2] with which this node of version [8.8.1] is incompatible. Revert this node to version [7.17.10] and delete any indices created in versions earlier than [7.0.0] before upgrading to version [8.8.1]. If all such indices have already been deleted, revert this node to version [7.17.10] and wait for it to join the cluster to clean up any older indices from its metadata.","error.stack_trace":"java.lang.IllegalStateException: Cannot start this node because it holds metadata for indices created with version [6.6.2] with which this node of version [8.8.1] is incompatible. Revert this node to version [7.17.10] and delete any indices created in versions earlier than [7.0.0] before upgrading to version [8.8.1]. If all such indices have already been deleted, revert this node to version [7.17.10] and wait for it to join the cluster to clean up any older indices from its metadata.\n\tat [email protected]/org.elasticsearch.env.NodeEnvironment.checkForIndexCompatibility(NodeEnvironment.java:537)\n\tat [email protected]/org.elasticsearch.env.NodeEnvironment.upgradeLegacyNodeFolders(NodeEnvironment.java:414)\n\tat [email protected]/org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:307)\n\tat [email protected]/org.elasticsearch.node.Node.<init>(Node.java:483)\n\tat [email protected]/org.elasticsearch.node.Node.<init>(Node.java:327)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch$2.<init>(Elasticsearch.java:216)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch.initPhase3(Elasticsearch.java:216)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:67)\n"}

 

V7 works fine...

  • Replies 59
  • Views 35.5k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Just found this thread after I fixed my elasticsearch container. I didn't know about the TAKE_FILE_OWNERSHIP Variable, will have to check this later. I just went to the /mnt/user/appdata/ folder,

  • Probably not the best way but I ssh’d in and created the node folder and did a chown nobody:users

  • I fixed this by adding a variable for "TAKE_FILE_OWNERSHIP" with a value of "true":

Posted Images

@irishjd Do you need the old data in elasticsearch or will it be re-populated? The easiest option would be to delete all files in the current elasticsearch data folder. The log says that there are indices from v7 and they aren't compatible with v8.

Ah Ha... somehow I completely missed that. Let me uninstall/reinstall as there is no persistent data that I need to keep.

@lucahammer thanks for the catch in the error log. I stopped the container, deleted the data from appdata, and restart with v8. All is working fine now.

  • 4 months later...

Any updated instructions for this?

 

I can't get it to work. I have tried another variation of the ElasticSearch docker and just can of get this to work.

 

I'm wondering if there any additional steps required or perhaps some parts of the current instructions are redundant.

  • 4 weeks later...

Hi ! :)

 

I, too, can't run this docker properly :/
Tried several different versions (but in 7.** flavor because wikijs only accept 6.* or 7.*)

- userscript is in place and running

 

Here's the conf:

Capture_decran_2024-01-25_a_13_38_38.png.69da7c100ee912aeefc3946cc4003655.png

 

The short log from elasticsearch docker related to wikijs is joined

 

And the error in WikiJS docker :

Capture_decran_2024-01-25_a_13_33_47.png.33ec6aa1e75a6adb2bd1812435b5a9f4.png

 

If anyone have an idea, thank you ! :)

DockerLog.txt

  • 1 year later...

I just got this working for Nextcloud 30 after some trial and error. Highly recommend copying error logs (with sensitive information removed, of course) to ChatGPT for debugging.

 

 

I followed this video tutorial, but made the following changes below:

  • Do not use elasticsearch:latest in docker pull; it's unsupported. Instead manually enter the latest version. I used elasticsearch:8.17.2
  • Use a custom bridge network. The default bridge network will not resolve container name as hostnames. Use:
     docker network create -d bridge my-bridge-network

    Then change the "Network Type" to match.

  • Allegedly, ES8 and above defaults to SSL, which is wonky with Nextcloud. Disable this by adding a variable   
    xpack.security.enabled=false
    image.png.df8c5b57deb3eb5ed72407d2829ab77b.png
  • In the Nextcloud apps, serverlet address should be: http://elasticsearch:9200

image.png

  • 9 months later...
On 1/25/2024 at 11:48 PM, AinzOolGown said:

Hi ! :)

 

I, too, can't run this docker properly :/
Tried several different versions (but in 7.** flavor because wikijs only accept 6.* or 7.*)

- userscript is in place and running

 

Here's the conf:

Capture_decran_2024-01-25_a_13_38_38.png.69da7c100ee912aeefc3946cc4003655.png

 

The short log from elasticsearch docker related to wikijs is joined

 

And the error in WikiJS docker :

Capture_decran_2024-01-25_a_13_33_47.png.33ec6aa1e75a6adb2bd1812435b5a9f4.png

 

If anyone have an idea, thank you ! :)

DockerLog.txt

Any update on this issue?

  • 2 weeks later...
  • 4 months later...

Managed to get 9.4.1 to not crash instantly by appending -u 99:100 --group-add 0 to Extra Parameters.

Edited by 2meito

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.