mirror of
https://github.com/RD17/ambar.git
synced 2026-04-25 15:35:49 +03:00
[GH-ISSUE #188] "Oops... sometyhing get wrong, reload the page" index_not_found_exception #185
Labels
No labels
$$ Paid Support
bug
bug
enhancement
help wanted
invalid
pull-request
question
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ambar#185
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @RogersNelson on GitHub (Aug 31, 2018).
Original GitHub issue: https://github.com/RD17/ambar/issues/188
Hi,
As Ambar seems to do exactly what I need, I wanted to test it on my laptop fir a first test.
Unfortunately, when I go on http://localhost/, I see the message "Oops... sometyhing get wrong, reload the page"
The browser console shows :
The page http://192.168.128.70:8080/api/tags shows:
And the docker-compose.yml contains :
Can someone help me?
Cheers,
Rogers.
@RogersNelson commented on GitHub (Aug 31, 2018):
And in the log, I see this for all files :
@m-hennig commented on GitHub (Sep 3, 2018):
Run exactly in the same problem... (same error messages!)
Only major difference in setup: I set in docker-compose.yml - name=${crawlerName} to the name of the crawler service.
Any other debug info required?
Regards,
Markus
@sochix commented on GitHub (Sep 6, 2018):
@m-hennig @RogersNelson check the logs of ambar_es, and also check that you set vm_max_map_count
@iladrero commented on GitHub (Sep 14, 2018):
Same error message. Set vm.max_map_count=262144 but no success so far. Any ideas @sochix ?
{"message":"[index_not_found_exception] no such index, with { resource.type=\"index_or_alias\" & resource.id=\"ambar_file_data\" & index_uuid=\"_na_\" & index=\"ambar_file_data\" }\n Error: [index_not_found_exception] no such index, with { resource.type=\"index_or_alias\" & resource.id=\"ambar_file_data\" & index_uuid=\"_na_\" & index=\"ambar_file_data\" }\n at respond (/node_modules/elasticsearch/src/lib/transport.js:289:15)\n at checkRespForFailure (/node_modules/elasticsearch/src/lib/transport.js:248:7)\n at HttpConnector.<anonymous> (/node_modules/elasticsearch/src/lib/connectors/http.js:164:7)\n at IncomingMessage.wrapper (/node_modules/lodash/lodash.js:4994:19)\n at emitNone (events.js:111:20)\n at IncomingMessage.emit (events.js:208:7)\n at endReadableNT (_stream_readable.js:1064:12)\n at _combinedTickCallback (internal/process/next_tick.js:138:11)\n at process._tickCallback (internal/process/next_tick.js:180:9)"}@iladrero commented on GitHub (Sep 14, 2018):
In case it helps from the web log:
[webapi] [error] Cannot read property 'max_score' of undefined TypeError: Cannot read property 'max_score' of undefined at /dist/services/EsProxy/EsProxy.js:310:56 at tryCallOne (/node_modules/promise/lib/core.js:37:12) at /node_modules/promise/lib/core.js:123:15 at flush (/node_modules/asap/raw.js:50:29) at _combinedTickCallback (internal/process/next_tick.js:131:7) at process._tickCallback (internal/process/next_tick.js:180:9)@iladrero commented on GitHub (Sep 21, 2018):
hi all, anybody sorted out this error yet? @RogersNelson @m-hennig @sochix
@dschutterop commented on GitHub (Sep 23, 2018):
Chipping in with a +1 on this issue, getting the exact same error after a plain vanilla spin-up with docker-compose...Yeah, about that +1... it turns out that overlooking the language setting in the docker-compose file doesn't really help, going through the file with a fine toothed comb helped me out there...
@isido993 commented on GitHub (Oct 8, 2018):
Hello everyone,
Try removing everything from your ES storage folder, it's /home/myname/opt/ambar/dataPath/es for @RogersNelson. Stop Ambar, clear the folder and then start it again.
Also, could you share the business issue you're solving/trying to solve with Ambar with me? It'll help us develop it into a better product. Thanks.
@stale[bot] commented on GitHub (Oct 23, 2018):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.