I've just installed Elasticsearch and Kibana's latest versions (same versions) on Windows. When I launch Elasticsearch it starts just as normal and I can check through the browser that it's on the required port. But when I launch Kibana it gives me the error "\config was unexpected". I checked the configurations and made sure that Kibana knew where to connect to ES and tried re-installs but nothing changed. When I tried it on an Ubuntu virtual machine the two worked normally. I don't know where the issue is. Hope someone can help.
Thanks.
I solved the problem. I'll just leave this for future reference:
Some people solved this by downgrading their Java: I did the same thing going from Java 15 to Java 8 but it didn't solve the issue for me. But still something to try.
What solved this for me was simply to change the path of the Kibana directory. Apparently Windows had some trouble reading its own default name for the parent directory. Moving the kibana folder to a simpler directory (like C:) and even renaming the folder to simply "kibana" instead of including the version etc. made it run as normal.
Related
I've downloaded Apache nifi 1.17.0 and tried to start it by bin/run0nifi.bat, but it didn't work. When I click on it window open and disappear in the same time.
I'm working on windows 11 pro
What should i do?
I tried to start it by console and tried to start 1.19.1 and unfortunately it didn't help
I'm a beginner so I might not have done some obvious things
Thx for help)
You need to do two things first of all:
you need to make sure that you have installed JAVA on your machine and set the PATH for the JDK in the Environment Variables (JAVA_HOME).
If JAVA is configured correctly you need to open CMD and go within the NiFi Folder. From there, you should execute the run-nifi.bat manually and see if anythings gets written in the CMD window.
Besides that, you can go within the logs folder and see if any logs are being generated. Most likely you will find something in the nifi-app.log.
I am trying to install Elasticsearch on my computer. I am following this tutorial for the purpose. The steps mentioned in this tutorial works fine in one computer. But when I am trying to install ElasticSearch in another computer, I found that the config file is entirely commented unlike the config file of the previous computer in which I could install the Elastic search. I have tried downloading elasticsearch multiple times, but every time I found that the config file is commented. I have also tried manually pasting the config file in the second system, but that attempt fails as well. Is there any issue with my system that prevents the config file from getting downloaded in the right manner? Also what should be done in my case. Any help in this regard will be of great value.
I've been having an issue lately. My XAMPP folder used to be on C:, right at the very top, but I want the XAMPP folder to be located somewhere else. The problem is, if I do that, I can't start up Apache or MySQL. It works completely fine as long as XAMPP is at C:/xampp/, but as soon as I move it anywhere else that is not at the very top of the given partition, it no longer works. The error log is also not very helpful.
The version I'm using is 7.4.6 on Windows, specifically the portable version (xampp-portable-windows-x64-7.4.6-0-VC15). Is this some sort of quirk from the portable version? Or do I need to change some settings to make it work on other folders?
The same thing happens when I installed XAMPP in ubuntu 20.04, the solution to this issue is by creating a symbolic link to connect the root directory C:/xampp/ with a target directory you choose or create.
Here is a useful link to create symbolic links in Windows.
symbolic_links_windows
I'm running an instance of Galaxy NGS in an Ubuntu server, with a basic configuration, postgresql database, and apache.
When I log in as Admin in the Galaxy interface, and try to add a new tool through the tool shed, the tool is installed and I can use it without problems
However, if Galaxy needs to be restarted, the tool does not appear anymore
I followed the instructions here to configure a folder to keep the installed tools, like it explains there, adding a line in config.ini with the desired folder
tool_dependency_dir = dependency_dir
But that doesn't do the trick and the tools are not stored in the folder anyway
Does somebody have a clue on what could I be missing?
The problem was solved after switching from apache to nginx, and changing the line I posted to
tool_dependency_dir = /home/galaxy/tool_deps
I found a nice resource that helped me with the configuration in case somebody faces the same issue.
https://wiki.galaxyproject.org/Events/BioITWorld2014/W14#Setting_up_a_Local_Galaxy_Tutorial_.28Part_I.29
I’m using JBoss 7.1.3.Final on my dev machine, a Mac 10.9.1. I’m trying to get my /tmp/vfs directory to clean itself up (with a max caching time of a day), so I added this line to my $JBOSS_HOME/bin/standalone.conf file …
JAVA_OPTS="$JAVA_OPTS -Djboss.vfs.cache=org.jboss.virtual.plugins.cache.IterableTimedVFSCache -Djboss.vfs.cache.TimedPolicyCaching.lifetime=86400"
I confirmed that the system properties are getting loaded when I start my server. However, after restart, I still see directories in the $JBOSS_HOME/standalone/tmp/vfs that are more than a day old. Is something about the above wrong or is there another parameter I need to add to get that directory to clean out?
You do not need to set VFS system properties.
Also your properties come from VFS2 that was used AS5/6 times.
AS7+ has newer/different implementation of VFS and handles this things differently.
There ware few bugs in 7.1.x in this area and ware fixed in WildFly 8 Beta1.
See jira for more info about this.
I would recommend you upgrading to WildFly 8.