Demos not working on Windows 10 - corda

I have been trying to run all the examples and demos provided by R3 Corda on my local machine which has windows 10 in it.
https://docs.corda.net/releases/release-V1.0/running-the-demos.html
While example 1 and 2 are working fine, but I am unable to run the demos. While the nodes are getting deployed, but once I run the nodes using runnodes command from command-line, they open in terminals and immediately close. Please can someone from #r3corda #corda team may help to sort this out.

I was running into the similar issue on Win 10.
Running the following:
>java -jar corda.jar
Exception in thread "main" java.lang.UnsatisfiedLinkError: Could not load library. Reasons: [no jansi64-1.14 in java.library.path, no jansi-1.14 in java.library.path, no jansi in java.library.path,
C:\Users\<user>\AppData\Local\Temp\jansi-64-1-6925657630491746639.14: Access is denied]
Downloading the missing library to C:\windows reloved it.
Download Link:
http://www.java2s.com/Code/Jar/j/Downloadjansi14jar.htm

Related

mpirun error of oneAPI with Slurm (and PBS) in old cluster

Recently I installed Intel OneAPI including c compiler, FORTRAN compiler and mpi library and complied VASP with it.
Before presenting the question, there are some tricks I need to clarify during the installation of VASP:
GLIBC2.14: the cluster is an old machine with a glibc version of 2.12, where OneAPI needs a version of 2.14. So I compile the GLIBC2.14 and export the ld_path: export LD_LIBRARY_PATH="~/mysoft/glibc214/lib:$LD_LIBRARY_PATH"
ld 2.24: The ld version is 2.20 in the cluster, while a higher version is needed. So I installed binutils 2.24.
There is one master computer connected with 30 calculating nodes in the cluster. The calculation is executed with 3 ways:
When I do the calculation in the master, it's totally OK.
When I login the nodes manually with rsh command, the calculation in the logged node is also no problem.
But usually I submit the calculation script from the master (with slurm or pbs), and then do the calculation in the node. In that case, I met following error message:
[mpiexec#node3.alineos.net] poll_for_event (../../../../../src/pm/i_hydra/libhydra/demux/hydra_demux_poll.c:159): check exit codes error
[mpiexec#node3.alineos.net] HYD_dmx_poll_wait_for_proxy_event (../../../../../src/pm/i_hydra/libhydra/demux/hydra_demux_poll.c:212): poll for event error
[mpiexec#node3.alineos.net] HYD_bstrap_setup (../../../../../src/pm/i_hydra/libhydra/bstrap/src/intel/i_hydra_bstrap.c:1062): error waiting for event
[mpiexec#node3.alineos.net] HYD_print_bstrap_setup_error_message (../../../../../src/pm/i_hydra/mpiexec/intel/i_mpiexec.c:1015): error setting up the bootstrap proxies
[mpiexec#node3.alineos.net] Possible reasons:
[mpiexec#node3.alineos.net] 1. Host is unavailable. Please check that all hosts are available.
[mpiexec#node3.alineos.net] 2. Cannot launch hydra_bstrap_proxy or it crashed on one of the hosts. Make sure hydra_bstrap_proxy is available on all hosts and it has right permissions.
[mpiexec#node3.alineos.net] 3. Firewall refused connection. Check that enough ports are allowed in the firewall and specify them with the I_MPI_PORT_RANGE variable.
[mpiexec#node3.alineos.net] 4. pbs bootstrap cannot launch processes on remote host. You may try using -bootstrap option to select alternative launcher.
I only met this error with oneAPI compiled codes but Intel® Parallel Studio XE compiled. Do you have any idea of this error? Your response will be highly appreciated.
Best,
Léon
Could it be a permissions error with the Slurm agent not having the correct permissions or library path?

Information shows in browser, not "R Help" pane, when using StatET

I am using Eclipse 2018-09 and StatET 3.6.1. I have two R environments: one for R 3.3.2, another for R 3.5.1. When I execute a command like ?lm to call up a help page in v3.3.2, the page appears in the StatET "R Help" pane, as I want it to. But when I execute the same command to call up a help page in v3.5.1, the console tells me "starting httpd help server," and the help page loads in my browser. How can I get help to load in the "R Help" pane when using v3.5.1?
The problem arises whether or not I run Eclipse as an administrator, and whether or not I "Auto Run" R 3.5.1 upon booting. And as far as I can tell, the configurations for the two versions of R are nearly identical:
Both are running Windows 10 and JRE 1.8.0_121.
Both with version 2.1 of the rj package.
For both, I've checked every box in "Run Configurations > R Console > R Console > Eclipse Integration," including "Enable R Help for StatET."
For both, options("help_type") == 'html'.
Inspection of the different log files that I get when using Auto Run with the two versions of R suggests that there is some sort of StatET config problem that has to do with Derby. These messages appear only when I boot R 3.5.1:
!ENTRY de.walware.statet.r.core 4 -1 2018-11-16 02:50:29.092
!MESSAGE An error occurred when initializing DB for model.
!STACK 1
org.eclipse.core.runtime.CoreException: An error occurred when loading embedded DB (Derby + DBCP)
DB ConnectionURL=[path redacted]\eclipse-workspace\.metadata\.plugins\de.walware.statet.r.core\db
[...]
Caused by: java.sql.SQLException: Another instance of Derby may have already booted the database C:\[path redacted]\eclipse-workspace\.metadata\.plugins\de.walware.statet.r.core\db.
[...]
Caused by: ERROR XSDB6: Another instance of Derby may have already booted the database C:\[path redacted]\eclipse-workspace\.metadata\.plugins\de.walware.statet.r.core\db.
But I don't know what to make of this problem or how to fix it.
Stephan Wahlbrink, the creator of StatET, recommended running this command at startup:
registerS3method("print", "help_files_with_topic", rj::print.help_files_with_topic)
I ran the command, and it solved the problem.
(Stephan added that the Derby errors that I saw in the logs were unrelated to the problem of displaying help in the "R Help" pane.)

multiple version of spark on CDH5.10 is failing to launch spark-submit

I have installed spark with 2.0 on CDH5.10 By following the link https://www.cloudera.com/documentation/spark2/latest/topics/spark2_installing.html
after all configuration when I hit spark2-submit --version it gives me correct version which is 2.0
however when I submit a spark job . First it says
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/hadoop/fs/FSDataInputStream
This is clearly indicating that hadoop libs are not in classpath. My question is it something wrong with my installation of spark 2. ? also once we add jars with sparkExtralibCLasspath for driver and core then it says SPARK_HADOOP_CONF Is not set.
How can I verify my installation is correct ?
I am also trying to understand where are my spark2 conf dirs
I saw few previous question on stackoverflow like https://community.cloudera.com/t5/Cloudera-Manager-Installation/CHD-5-7-spark-shell-java-lang-ClassNotFoundException-org-apache/td-p/42209 and NoClassDefFoundError com.apache.hadoop.fs.FSDataInputStream when execute spark-shell but this doesnt help
I am using spark2-shell and spark2-submit command
some more investigation with https://community.cloudera.com/t5/Cloudera-Manager-Installation/CDH-5-5-pyspark-java-lang-NoClassDefFoundError-org-apache-hadoop/td-p/34424 shows might be If I can correctly set SPARK_EXTRA_LIB_PATH for spark2 then I can fix this issue. can somebody guide me please. Thanks

An error occurred while processing the signatures for the file

I have Java EE Eclipse Indigo installed and am trying to use Help->Install New Software to install the SpringSource Tool Suite from the update site http://dist.springsource.com/release/TOOLS/update/e3.7
I have java 1.7.0_45 installed in use by Eclipse.
When I click "Finish", the Installing Software progress indicator displays and it goes about 49% of the way to completion before getting
An error occurred while collecting items to be installed
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Problems downloading artifact: osgi.bundle,org.grails.ide.eclipse.core,3.6.3.201411271013-RELEASE.
Error reading signed content:C:\Users\BARRET~1.REE\AppData\Local\Temp\signatureFile3011079682847967573.jar
An error occurred while processing the signatures for the file: C:\Users\BARRET~1.REE\AppData\Local\Temp\signatureFile3011079682847967573.jar
The last 3 lines are duplicated for around 20 different artifacts/jar files.
In my C:\Users directory, I have both a BARRETT~1~REE\AppData\Local\Temp directory and a barrett.reed\AppData\Local\Temp directory. It looks like the files are being downloaded to barrett.reed\AppData\Local\Temp. Perhaps that is the issue? Any way to resolve this?
Thanks in advance,
B.J. Reed

Install dcm4chee on Centos

I followed the instructions from here and when I executed sudo cp /opt/dcm4chee-psql-2.14.7/bin/dcm4chee_init_redhat.sh /etc/init.d/dcm4chee on server, it appeared the follow:
15:25:36,602 WARN [BasicMBeanRegistry] javax.management.MBeanRegistrationException: preRegister() failed: [ObjectName='dcm4chee.archive:service=WADOService', Class=org.dcm4chex.wado.mbean.WADOService (org.dcm4chex.wado.mbean.WADOService#234f79cb)]
15:25:36,602 INFO [WADOService] Registration is not done -> stop
15:25:36,606 ERROR [MainDeployer] Could not create deployment: file:/opt/dcm4chee-2.17.2-mysql/server/default/deploy/dcm4chee-wado-service.xml
org.jboss.deployment.DeploymentException: - nested throwable: (java.lang.reflect.InvocationTargetException)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at sun.proxy.$Proxy4.install(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:251)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
Do anyone know what is the problem?
I am right now trying to install dcm4chee on CentOS and I experienced the same problem. When I was looking for a solution I saw your message here, as well as your message on the newsgroups with some hints about possible causes and solutions.
It would be interesting to point from here to the newsgroups thread with answers and additional information, since that could help to other users having the same problem
In short: The problem is WADO service unable to start due to the JAI Image IO library not being properly installed.
You should download the 64 bit version of the library for Linux, extract the files and replace just the original (32 bit) ones from those that you downloaded.
$ cp clibwrapper_jiio.jar $DCM4CHEE_HOME/server/default/lib
$ cp jai_imageio.jar $DCM4CHEE_HOME/server/default/lib
$ cp libclib_jiio.so $DCM4CHEE_HOME/bin/native
Now, your DCM4CHEE installation should be able to run on your 64 bit Linux machine.
In addition to #jap1968 fix, please verify the Java version you are using typing java -version on console.
If you are using Java 8+, install a Java 7 SDK and configure DCM4CHEE to use it adding at line 106 of $DCM4CHEE/bin/run.sh the following line (modify it to match your Java 7 directory):
JAVA=/etc/alternatives/java_sdk_1.7.0/bin/java

Resources