Tried many ways to resolve the error. But couldn't. Can anyone tell me what needs to be done to resolve the error. Nifi is running in Linux server.
Related
I am facing the error 1297 when trying to start the oraclevsswriter service. The error is like a privilege that the service requires to function properly doesn't exist in the service account configuration. It is also given to use services.mnc and secpol.mnc to view the service configuration and account configuration.
Please help me solve this...
Tried a week ago but couldn't solve this. Badly need a solution for this.
I setup Apache Openwhisk locally following this guide: http://jamesthom.as/blog/2018/01/19/starting-openwhisk-in-sixty-seconds/. In general it seems to work correctly, but whenever I'm trying to execute any commands related to api, e.g.
wsk -i api list
it gives me an error,
Unable to obtain the API list: The requested resource does not exist. (code 153)
Any idea how to fix this?
This is unfortunately a temporary issue with docker-compose, and work is in progress to fix this.
I'm currently trying to deploy Eremetic (version 0.28.0) on top of Marathon using the configuration provided as an example. I actually have been able to deploy it once, but suddenly, after trying to redeploy it, the framework stays inactive.
By inspecting the logs I noticed a constant attempt to connect to some service that apparently never succeeds because of some authentication problem.
2017/08/14 12:30:45 Connected to [REDACTED_MESOS_MASTER_ADDRESS]
2017/08/14 12:30:45 Authentication failed: EOF
It looks like the service returning an error is ZooKeeper and more precisely it looks like the error can be traced back to this line in the Go ZooKeeper library. ZooKeeper however seems to work: I've tried to query it directly with zkCli and to run a small Spark job (where the Mesos master is given with zk:// URL) and everything seems to work.
Unfortunately I'm not able to diagnose the problem further, what could it be?
It turned out to be a configuration problem. The master URL was simply wrong and this is how the error was reported.
I encountered an error while adding a new service (Service Type = HDFS) using Cloudera Manager (Free Edition). The error message says as follows:
Could not create process: com.cloudera.cmf.service.config.ConfigFileSpec$GenerateException: Unable to process template:couldn't find the template hadoop/topology.py.vm
I checked /var/log/cloudera-scm-server/cloudera-scm-server.log and found a line like below.
org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource '/WEB-INF/templates/hadoop/topology.py.vm'
I guess that a certain war file does not contain hadoop-metrics.properties.vm (Velocity template file?) although it should do and that this might be related to WHIRR-370.
Could you help me to solve this problem, please?
May I ask which version of Cloudera Manager is being used? Does this error occurred just after you try to add add the service of after some time when the service is added?
Based on the error, it seems some of the configuration is missing that why service addition failed. So I would like to know how did you install Hadoop on this cluster?
If you download the virtual machine and compare from your installation, you can compare the folder for completeness and missing content. It does work for me always.
i have a server with a bunch of tomcat, springs applications, and i can´t load a particular one that uses quartz. The main problem is that i can´t find an error anywhere that tells me what went wrong. And the same application runs fine in the test server, which uses de samde 1.6 jdk, tomcat 5.5. The only difference is that the productions server is in debian lenny, the test server in Centos. I only get a HTTP Status 404: requested resource not available.
Nothing usefull in catalina.out, configured log4j using this tutorial: http://tomcat.apache.org/tomcat-5.5-doc/logging.html , but can´t find any error there either. So i was wondering where can i get a hint of the problem ? tomcat starts succesfully and the other applications load without any problem.
Thank you very much
tail -f the catalina.out when you load the application, even it fails you still should able to see the output of tomcat trying to load the classes.
You might want to adjust to log level to info to see that tho.
*with 404 error, you could also try check the apache log, if you are using mod jk or proxy linking them.