I am using solr-7.2.1 version and it has embedded jetty server, verison-9.
I have tried to enable requestlog module to configure request logs but did not work.
I have installed http,https modules. Failed to install the remaining modules like webapp,deploy,requestlog.
Could someone suggest a fix?
Output of these modules:
Steps:
-bash-4.1$ sudo java -jar start.jar --add-to-start=http
INFO: http initialised in ${jetty.base}/start.ini
INFO: Base directory was modified
-bash-4.1$ sudo java -jar start.jar --add-to-start=https
INFO: https initialised in ${jetty.base}/start.ini
INFO: Base directory was modified
-bash-4.1$
-bash-4.1$
-bash-4.1$
-bash-4.1$ sudo java -jar start.jar --add-to-start=webapp
org.eclipse.jetty.start.graph.GraphException: Missing referenced dependency: webapp
at org.eclipse.jetty.start.graph.Graph.selectNodes(Graph.java:470)
at org.eclipse.jetty.start.BaseBuilder.build(BaseBuilder.java:152)
at org.eclipse.jetty.start.Main.start(Main.java:407)
at org.eclipse.jetty.start.Main.main(Main.java:75)
Usage: java -jar start.jar [options] [properties] [configs]
java -jar start.jar --help # for more information
-bash-4.1$
-bash-4.1$
-bash-4.1$ sudo java -jar start.jar --add-to-start=deploy
org.eclipse.jetty.start.graph.GraphException: Missing referenced dependency: deploy
at org.eclipse.jetty.start.graph.Graph.selectNodes(Graph.java:470)
at org.eclipse.jetty.start.BaseBuilder.build(BaseBuilder.java:152)
at org.eclipse.jetty.start.Main.start(Main.java:407)
at org.eclipse.jetty.start.Main.main(Main.java:75)
Usage: java -jar start.jar [options] [properties] [configs]
java -jar start.jar --help # for more information
-bash-4.1$
-bash-4.1$
-bash-4.1$ sudo java -jar start.jar --add-to-start=requestlog
org.eclipse.jetty.start.graph.GraphException: Missing referenced dependency: requestlog
at org.eclipse.jetty.start.graph.Graph.selectNodes(Graph.java:470)
at org.eclipse.jetty.start.BaseBuilder.build(BaseBuilder.java:152)
at org.eclipse.jetty.start.Main.start(Main.java:407)
at org.eclipse.jetty.start.Main.main(Main.java:75)
Usage: java -jar start.jar [options] [properties] [configs]
java -jar start.jar --help # for more information
-bash-4.1$
-bash-4.1$
Related
I'm trying to build QuestDB from source on a newly setup machine and I get warnings about javac:
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) # questdb ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 1292 source files to /home/pi/questdb/core/target/classes
[WARNING] Unable to autodetect 'javac' path, using 'javac' from the environment.
What's a fix for this?
It looks like JAVA_HOME env var is not set. You can check by running the following in your shell:
echo $JAVA_HOME
On macOS, I have the following:
/Library/Java/JavaVirtualMachines/openjdk-11.jdk/Contents/Home
To check which runtime maven (brew install) is referencing:
mvn --version
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /Users/me/maven/apache-maven-3.6.3
Java version: 11.0.9, vendor: Oracle Corporation, runtime: /usr/local/Cellar/openjdk#11/11.0.9/libexec/openjdk.jdk/Contents/Home
In ~/.zshrc (you may use ~/.bashrc) I have set JAVA_HOME with
export JAVA_HOME="/Library/Java/JavaVirtualMachines/openjdk-11.jdk/Contents/Home"
then try building again:
source ~/.zshrc
mvn clean package -DskipTests -P build-web-console,build-binaries
I have a Django application which it's deployed to Amazon Elastic Beanstalk. I have to install anaconda for installing pythonocc-core package. I have created a .config file in .ebextensions folder and add the anaconda path in my wsgi.py file such as below and I have deployed it successfully.
.config file:
commands:
00_download_conda:
command: 'wget https://repo.anaconda.com/archive/Anaconda3-2020.02-Linux-x86_64.sh'
test: test ! -d /anaconda
01_install_conda:
command: 'bash Anaconda3-2020.02-Linux-x86_64.sh -b -f -p /anaconda'
test: test ! -d /anaconda
02_create_home:
command: 'mkdir -p /home/wsgi'
03_conda_activate_installation:
command: 'source ~/.bashrc'
wsgi.py:
sys.path.append('/anaconda/lib/python3.7/site-packages')
However when I add the 04_conda_install_pythonocc command below to the continuation of this .config file, I got command failed error.
04_conda_install_pythonocc:
command: 'conda install -c dlr-sc pythonocc-core=7.4.0'
I ssh into the instance for checking. I saw the /anaconda folder has occured. When I checked with the conda --version command, I got the -bash: conda: command not found error.
Afterwards, I thought there might be a problem with the PATH and I edited the .config file as follows and I have deployed this .config file successfully.
commands:
00_download_conda:
command: 'wget https://repo.anaconda.com/archive/Anaconda3-2020.02-Linux-x86_64.sh'
test: test ! -d /anaconda
01_install_conda:
command: 'bash Anaconda3-2020.02-Linux-x86_64.sh -b -f -p /anaconda'
test: test ! -d /anaconda
02_create_home:
command: 'mkdir -p /home/wsgi'
03_add_path:
command: 'export PATH=$PATH:$HOME/anaconda/bin'
04_conda_activate_installation:
command: 'source ~/.bashrc'
But when I add the conda_install_pythonocc command again to the continuation of this edited version of .config file, it failed again and I got command failed.
In manually, all the commands work but they don't work in my .config file.
How can I fix this issue and install package with conda?
I tried to replicated the issue on my sandbox account, and I successful installed conda using the following (simplified) config file on 64bit Amazon Linux 2 v3.0.3 running Python 3.7:
.ebextensions/60_anaconda.config
commands:
00_download_conda:
command: 'wget https://repo.anaconda.com/archive/Anaconda3-2020.02-Linux-x86_64.sh'
01_install_conda:
command: 'bash Anaconda3-2020.02-Linux-x86_64.sh -b -f -p /anaconda'
05_conda_install:
command: '/anaconda/bin/conda install -y -c dlr-sc pythonocc-core=7.4.0'
Note the use off absolute path /anaconda/bin/conda and -y to not ask for manual confirmations. I only verified installation procedure, not how to use it afterwards (e.g. not how to use it in python application). Thus you will probably need to adjust it to your needs.
The EB log file showing successful installation is also provided for your reference (shortened for simplicity):
/var/log/cfn-init-cmd.log
I'm creating a hyperledger contract similar to the commercial paper example in typescript and publishing it in a AWS Managed Blockchain Service using this command:
docker exec -e "CORE_PEER_TLS_ENABLED=true" \
-e "CORE_PEER_TLS_ROOTCERT_FILE=/opt/home/managedblockchain-tls-chain.pem" \
-e "CORE_PEER_LOCALMSPID=$MSP" \
-e "CORE_PEER_MSPCONFIGPATH=$MSP_PATH" \
-e "CORE_PEER_ADDRESS=$PEER" \
cli peer chaincode instantiate -o $ORDERER \
-C ourchannel --lang node -n papercontract -v v0 \
-c '{"Args":["org.papernet.commercialpaper:instantiate"]}' \
--cafile /opt/home/managedblockchain-tls-chain.pem --tls \
-P "AND ('$ORG1','$ORG2')"
I already installed the contract using this command in both organizations:
docker exec -e "CORE_PEER_TLS_ENABLED=true" \
-e "CORE_PEER_TLS_ROOTCERT_FILE=/opt/home/managedblockchain-tls-chain.pem" \
-e "CORE_PEER_LOCALMSPID=$MSP" \
-e "CORE_PEER_MSPCONFIGPATH=$MSP_PATH" \
-e "CORE_PEER_ADDRESS=$PEER" \
cli peer chaincode install --lang node -n papercontract -v v0 \
-p chaincode
But I'm getting this error:
$ checkChaincodeCmdParams -> INFO 001 Using default escc
$ checkChaincodeCmdParams -> INFO 002 Using default vscc
$ Error: could not assemble transaction, err Proposal response was not successful, error code 500, msg failed to execute transaction f0803ce6160119859cedd426e5d4d35dfba3ee6fa0653078ef917546b1854ea7: error starting container: error starting container: Failed to generate platform-specific docker build: Error returned from build: 1 "npm ERR! code ETARGET
npm ERR! notarget No matching version found for fabric-shim#^1.4.2
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'transference-contract'
npm ERR! notarget
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-08-15T18_22_42_519Z-debug.log
"
I have run npm install and npm run build in my client and everything works fine. The problem seems to be that the library isn't downloaded in the peer inside the blockchain, but as it is managed I can't really see inside of it to see what's happening.
Can you give me some ideas to whats happening? what can I do to fix it?
Thanks
The peer nodes do not support the fabric-shim 1.4 version
According to the AWS docs:
Managed Blockchain peer nodes use version 1.2 of the fabric-shim library to provide the low-level chaincode interface between applications, peers, and the Hyperledger Fabric system for chaincode applications using Node.js. All chaincode has a dependency on this library. Dependencies on other versions or other library packages are not supported because peer nodes currently do not have access to the NPM repository.
Snippet is from this page from aws: https://docs.aws.amazon.com/managed-blockchain/latest/managementguide/managed-blockchain-hyperledger-write-and-run-chaincode.html
I try to setup nativescript-vue on linux by following steps on nativescript website. when I use this command
sudo update-alternatives --config java
but have an error
update-alternatives: error: no alternatives for java
Please tell me how to fix this problem......
Try
sudo update-alternatives --install /usr/bin/java java path_to_java 1
In my case the path was /usr/lib/jvm/java-8-openjdk-amd64
Do you have java installed?
Check if you do by running java -version in the command line/terminal
I had installed Jetty 9.1.2 in ubuntu 12.04. But it fails to start.
$ sudo service jetty start
Starting Jetty: FAILED Thu Apr 10 11:28:43 IST 2014
I feel the error should be in jetty.sh file in /ete/iniit.d. Do let me know how to start the jetty server.
Even java -jar start.jar doesn't works.