Unable to connect to Elasticsearch at http://jhipster-elasticsearch:9200/.. May be is something simple, but I've been trying to sort this out since yesterday.
Caused by: com.github.vanroy.springdata.jest.exception.JestElasticsearchException: Cannot execute jest action , response code : 400 , error : {"root_cause":[{"type":"resource_already_exists_exception","reason":"index [user/EugWgt89SFmIpJj0IVFuUg] already exists","index_uuid":"EugWgt89SFmIpJj0IVFuUg","index":"user"}],"type":"resource_already_exists_exception","reason":"index [user/EugWgt89SFmIpJj0IVFuUg] already exists","index_uuid":"EugWgt89SFmIpJj0IVFuUg","index":"user"} , message : null
ERROR: for jhipster-alerter Cannot start service jhipster-alerter: b'OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \\"rootfs_linux.go:58: mounting \\\\\\"/Users/alejandro/IdeaProjects/jhipster-alerter/config.yaml\\\\\\" to rootfs \\\\\\"/var/lib/docker/overlay2/88d45f6803afafd0f0f1b13e1d922a0b915c6b1c07b40b5cab4c57b76806cfa2/merged\\\\\\" at \\\\\\"/var/lib/docker/overlay2/88d45f6803afafd0f0f1b13e1d922a0b915c6b1c07b40b5cab4c57b76806cfa2/merged/opt/elastalert/config.yaml\\\\\\" caused \\\\\\"not a directory\\\\\\"\\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type’
thank!!!
As far as I could understand jhipster.metrics.jmx.enabled properties is used only for third-party monitoring systems (such as Prometheus). In fact, setting that property causes microservice springboot fail because no other third party monitoring system in in the classpath.
I'm running with jhipster-framework.version 3.0.5.
Did anybody got the same problem?
Hello Guys, I am trying to create the microservice with spring web flux using Jhispter generate with version 6.10.1.
generation works fine, however, when I start service and try to call it from the registry swagger UI, I get "Forbidden /services/reactivemicroservice/reactivemicroservice:75f727caed86aac2799c3322a21b0261/v2/api-docs". I tried with plain microservice(without spring web flux) it works absolutely fine. Can anyone guide me on this ti slove it?.
Thanks,
Kiran
[INFO]
[INFO] ESLint couldn't find the config "jhipster" to extend from. Please check that the name of the config is correct.
[INFO]
[INFO] The config "jhipster" was referenced from the config file in "C:.eslintrc.json".
[INFO]
[INFO] If you still have problems, please stop by https://gitter.im/eslint/eslint to chat with the team.
[INFO]
[INFO] npm ERR! code ELIFECYCLE
[INFO] npm ERR! errno 2
[INFO] npm ERR! sandboxreg@0.0.1-SNAPSHOT lint:
eslint . --ext .js,.ts[INFO] npm ERR! Exit status 2
[INFO] npm ERR!
[INFO] npm ERR! Failed at the sandboxreg@0.0.1-SNAPSHOT lint script.
[INFO] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
C:\WORKSPACE\sandboxreg\node_modules\generator-jhipster\generators\generator-base.js:1590
throw new Error(${msg});
^
Error: Error: Command failed: mvnw -ntp verify -B -Pwar -Pprod
at module.exports.error (C:\WORKSPACE\sandboxreg\node_modules\generator-jhipster\generators\generator-base.js:1590:15)
at C:\WORKSPACE\sandboxreg\node_modules\generator-jhipster\generators\aws\index.js:119:30
at ChildProcess.exithandler (child_process.js:310:5)
at ChildProcess.emit (events.js:311:20)
at ChildProcess.EventEmitter.emit (domain.js:482:12)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)C:\WORKSPACE\sandboxreg>eslint . --ext .ts --quiet --fix
'eslint' não é reconhecido como um comando interno
ou externo, um programa operável ou um arquivo em lotes.
I have used docker and kubernetes for a solid 2 years now. I noticed that jhipster-console only looks for microservice containers on localhost. How or where do I change the IP address so it doesn't use localhost?
I can trick it by modifying the containers hosts file and replace the localhost IP with the cluster IP. It picks up the service, but then it freaks out and say the service is down, even though it's running.
I kinda want to change our microservice log level at realtime.
For testing purposes I used the latest Jhipster-console docker image and also this sample project on GitHub:
https://github.com/jhipster/jhipster-sample-app-microservice
I containerized the jar with this docker base: openjdk:8-jre-alpine
I also made use of Docker swarm to simulate a cluster, created a simple network overlay called "my_net".
docker swarm init
docker network create -d overlay –-attachable my_net
docker service create --replicas=1 --name jregistry --network my_net -p 8761:8761 jhipster/jhipster-registry
docker service create --replicas=1 --name sample --network my_net -p 8081:8081 sample:test
Jhipster-registry don't seem to pick up the microservice, but if I run the jar on my local machine on localhost then the registry picks up the service.
If you use this command:
docker network inspect my_net
You should notice a Peer IP at the bottom of the json file, that's the simulated "cluster" IP. If I go into either containers modify the /etc/hosts file and make localhost point to that IP, then the Jhipster-registry suddenly picks up the service.
I modified the hosts file just to see what the reaction would be. Unfortunately like I said, jhipster-registry thinks the service is down as soon as you click on it and when you refresh it's magically up again.
So I just need to know where I can change the IP address to point to that "cluster"/Peer IP?