I am using centos 6.4, I find the notice as attached picture.
Then I try to find the log file in /var/log, but there's no result. Where is the log file of out of memory, i need to know what cause this problem.
Related
Keep getting error when I try to run the Protégé server. I had it working already but can no longer get it running. I have attached an image of the error and I have made sure the path to the protege.jar file in the run_protoge_server.bat file is correct. Any help appreciated.
enter image description here
I've been had hard times trying to fix this problem, the message error log does not appear. I've tried to reinstall to a old version, changing configuration that I've found here, changed location, changed conf file to message and nothing helped. So I'd like to know if someone can help me.
Thank you
[enter image description here]
Same problem here, not sure what's happening. But the work around is by opening the physical log here: C:\Users<user>\AppData\Roaming\pgAdmin\sessions\process_logs
When the pop up dialog still open, a temporary folder will be created and inside the folder you will get some files, then open the "err" file, this is where you can see the detail
pgadmin error process log
I am using Zendstudio 13.6 from past 2-3 weeks. I am facing hang issue on my linux system while comparing js files using team synchronization svn compare. Similar issue happens when opening xsd file in editor.
I just checked process using top command. I saw cpu usage gets 100% in such case and memory usage is normal 18% max. If there were memory issue I could try to increase heap memory using eclipse.ini file.
Does anyone faced this issue? If yes how can we solve this issue?
I also faced the same problem. And I solved it like this.
Possibly what happens is that when you try to open a XSD file, the editor tries to find a print feature to build up the design solution.
-Dorg.eclipse.swt.internal.gtk.disablePrinting
Enter the line mentioned above in the ZendStudio.ini file of your Zend Installation folder. And restart your ZendStudio Editor.
You will be easily able to open the xsd file and it will not freeze your editor.
And about the JS freeze problem, There is some other solution to JS freeze problem. Will update you once I find it.
When I start the server with below command its showing below error, java path and all are good still showing like this please help with this issue.
D:\Softwares\kafka\kafka-0.10.0.0-src>.\bin\windows\kafka-server-start.bat
.\config\server.properties '#' is not recognized as an internal or
external command, operable program or batch file. Error: Could not
find or load main class kafka.Kafka
Taking a leap here, but you directory ends in src. Mine does not. Any chance you downloaded the source distribution instead of the binary ?
for more recent version, juts define the CLASSPATH in
./bin.windows/kafka-run-class.bat:
line 17 for example
set CLASSPATH=/confluent-5.3.1.TAR\share\java\kafka*
I'm kinda puzzled how does a unix path looks like. I have followed an example to write a simple fileuploader using GWT. But the guide was written with Windows in mind. Say if I have C drive. In windows I would told the program to save the files to C:\save_here\
But in unix, I'm using ubuntu, there are no C drives or other drives with a single letter representation. So I wonder what do I write instead? I'm getting error 500 all the time now. And I can't figure out how the path should be.
The guide I've been following is found here
EDIT
It was not some problem duo to the path. Still need help though with fixing this problem. I basically followed the steps in the url I posted on this question.
unix paths start at a common root , denoted / and separates directories with a /
e.g. /home/starcom might be your home directory. So create a new directory, mkdir /home/starcom/uploaded and use that as the path. Or for testing you could perhaps just use /tmp
You can get more info here
When you get a 500 return code, that means the server encountered an error. This means that you should see an error message from the server somewhere. If you're running from Eclipse, you'll see the error on the Console tab. If you're running Tomcat, look for those logs.
You want to find the error message, since it'll probably explain what went wrong.