My issue seems peculiar. First i'll explain my setup. I'm using CentOS with Apache and Resin service. Thing is my application log seems to work perfectly fine configured with log4j but velocity log is not working (logger name = org.apache.velocity).
My local environment with the above specified settings works great (incuding the velocity log).
However in my dev environment configured with the same environment only the velocity log fails to roll or write any data.
I have very limited access to the dev environment and am unable to simulate this issue in the similar local env. hence unable to find the root cause or a solution to this.
Any help/suggestions on this would be greatly appreciated..
Thanks in advance!!
It was an issue with a corrupted jar file on the dev end...fixed now... hope this serves some help to any person with similar fate...
Related
Hi so basically what I am trying to do is get my spring web-application to run on port 80. I have installed tomcat8 and apache on a Ubuntu server and everything is running smoothly on myDomainName.com:8080, I have tried installing Authbind to help but it says I must set AUTHBIND=yes in the file location /etc/default/tomcat but for some reason this file is not present.
I have read previously that this file is not created if the installation was done from extracting the target file, this was my approach and this seems to me why the file is not there, I have no other solution.
Is there another way to set this authbind to yes or will I have to use Ip tables, or forward requests from Apache to tomcat. if i cant set authbind what in your opinion is the best solution.
Sorry if I left anything out, any help/suggestions would be of great help.
Thanks!
I would just completely reinstall the Tomcat on to your system. I had a similar problem and this was the only solution for me.
This is a very simple question, but I have struggled for two days to start up my WebObjects on a deployment Debian server. Everything has worked fine so far with Eclipse and Direct Connect, and an apachectl -M shows that the webobjects module (http server) is installed, running and shared. But when I try to run something as simple as a Hello World the browser returns a 404.
My applications are in /usr/share/webobjects/Library/WebObjects/JavaApplications/
Any pointers as to how I should configure (symbolic links and .conf entries) to make this work?
Much appreciated.
Luis
Have you had a look at the Deploying on Linux page on the WOCommunity wiki? If that doesn't help, you may need to post the relevant sections of your httpd.conf here for inspection.
Sometimes, for no real reason I get the following console message and a completely blank screen after deploying code to the server:
net::ERR_INCOMPLETE_CHUNKED_ENCODING
An Apache restart fixes it but I can't see why it happens. The file system changes but not any config. I've never encountered it when not doing a deployment, so something about the file system changing whilst apache is running seems to cause it.
The document root is a symlink (current/) to the latest release folder.
This might not be your problem, but it solved it for me so i'm going to throw it out there anyway - setting opcache.fast_shutdown=0 fixed it. It is disabled by default according to the php docs
but had been enabled in our setup.
I had this problem with phpmyadmin. Try disabling your antivirus.
I downloaded latest version of Odoo (Openerp v8) from GitHub. When installed on my localhost (my pc) it works fine. Now whenever I tried to install it on my remote server, database is created but not loaded and I have a blank page when it comes to my-remote-ip:8072/web (I launched it openerp-gevent along my config file but the same happens with the openerp-server command too).
When I check the log file, the process is stuck at:
.... INFO my-db-username openerp.addons.base.ir.ir_http: Generating
routing map
The last request processed by the system is:
'werkzeug.request': http://my-remote-ip:8072/web/js/web.assets_backend/77f77e2' [GET]>
This request is not served and leads to a blank page. I'm on ubuntu 14.04.
I wonder if there is protection in the coding that prevents odoo to be used from a remote server.
Please, can someone help me how to bypass this issue?
Use different DB for your remote server not same as localhost.
try to run remote server using this command
./openerp-server --xmlrpc-port=8072
you can change the port number.
Hope this will help... :)
I've been testing in virtual machines recently. IMHO check the postgress database and if all is working fine, then check python dependences, perhaps you missed some?
I've used this quick guide with success for my ubuntu 14.04 Vm with odoo 8
Thanks but your answer is not satisfying. I said that it works well on a local installation. And I know quite well about the installation process whatsoever.
Now, try to install Odoo on a remote server using your IP adress (which is my case as I haven't given a domain name to my VPS yet). You will notice that the installation process is not going to its end and points to a blank screen. I need to have feedbacks from persons who have tried the same operation. Again, thanks for all your valuable contributions to this issue.
I'm trying to get Mercurial going with IIS6 on Windows Server 2003 following the tutorial on this blog
My setup is
c:\inetpub\HG_web_interface\
and the folder containing repositories is in
d:\HG_repo\
My hgweb.config looks like this
[paths]
test = D:\HG_rep\**
[web]
style = monoblue
I tried pretty much every combination of forward/backward slashes, no slashed and whatnot, the only way I get it to work is to put my repository in the c: drive, then it works like a charm by simply putting this n hgweb.config
[paths]
test = \HG_rep\**
[web]
style = monoblue
Any idea on what's wrong?
p.s.: could it be some weird permission problem? If so, how can I troubleshoot it?
I figured it out: the user configured in the IIS application pool didn't have read/write access to the repository folder!
Sometimes things are much easier than we think... Now I'm trying to troubleshoot why I can't connect to my repository with TortoiseHG...
I guess the ":" is interpreted by the configparser.
Can you try to escape it ? A newer hg version should solve it too, since it includes it's own configuration file parser.