I'm getting not found error for combine_css
Below is my apache config:
ModPagespeedMapRewriteDomain domain.com.au 10.3.12.2
This seems to work sometimes but not all the time and it keeps on creating file that is not found occasionally.
Whenever this happens, I have to do below:
touch /var/cache/mod_pagespeed/cache.flush
Is there a reason why this is happening?
Related
I have two curls, one that comes with the OS, and another that comes with an application I installed. When I try run the one that comes with the application, I get "`curl: (2) Failed initialization", what is the problem here?
Even though I have Websocket installed, at build time, using the Meteor build tool, I’m getting this console error:
Unable to resolve some modules:
"../build/Release/bufferutil" in /Volumes/RAM Disk/myWebApp/node_modules/websocket/lib/BufferUtil.js (os.osx.x86_64)
"../build/default/bufferutil" in /Volumes/RAM Disk/myWebApp/node_modules/websocket/lib/BufferUtil.js (os.osx.x86_64)
"../build/Release/validation" in /Volumes/RAM Disk/myWebApp/node_modules/websocket/lib/Validation.js (os.osx.x86_64)
"../build/default/validation" in /Volumes/RAM Disk/myWebApp/node_modules/websocket/lib/Validation.js (os.osx.x86_64)
What might be causing this?
It looks like this is just a warning, not a fatal error.
https://github.com/meteor/meteor/issues/6601
I'm trying to host and distribute xbmc addon on my site. I've made a repository which points to the directory where the addon zip file is. At the same folder I have an xml which describes the addon and so the addon name and description are being recognized by xbmc.
However when trying to install the addon it shows 0% downloading progress and then the progress disappears - resulting in the following error inside xbmc.log file:
ERROR: CCurlFile::FillBuffer - Failed: HTTP response code said error(22)
according to curl errors page, this happens when -
CURLE_HTTP_RETURNED_ERROR (22)
This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP
server returns an error code that is >= 400.
by that I assume the error may be caused by a misconfigured access permissions (perhaps I need to change some htaccess configuration?).
please help
I solved this on my own eventually. Apparently, the file structure was wrong - I needed to follow the file structure as mentioned in section 4.3 here in order for it to work
I have followed the install instructions and gone over them multiple times with a fine comb and I am still unable to determine why I cannot resolve the NameService. I have the omniNames service running, but when I run omniEvents I get the following
omniEvents: [32190]: Warning - failed to resolve initial reference 'NameService'. Exception NO_RESOURCES
I receive this same error message when I attempt to connect within the Sandbox in the IDE, but I am still able to run components and connect them while running in the IDE Sandbox.
I ran nameclt list and received the following output
Cannot resolve the root context.
Have you set up the configuration file properly?
my config file contains the following
InetRef = NameService=corbaname::127.0.0.1
InetRef = EventService=corbaloc::127.0.0.1:11169/omniEvents
I have also verified that the services are being started on the correct ports using netstat.
What am i missing to get connected to the name service?
It appears that your error might be due to a typo in /etc/omniORB.cfg. In your example you use "InetRef" when it should be "InitRef".
Double check the settings and then restart omniNames and omniEvents and try nameclt again. If you get an error such as this:
$ nameclt list
Caught a TRANSIENT exception when trying to validate the type of the
NamingContext. Is the naming service running?
Double check that omniNames is indeed running (i.e. ps -ef | grep omniNames).
I'm using web.py 0.3 / apache2 / mod_wsgi and the cgitb module doesn't seem to work out of the box (I still just get 'internal server error' from web.py and the usual output goes to apache's error_log). The web.py install guide suggested a workaround which didn't work for me - I could probably hack it into working, but is there something better (perhaps designed for web.py or wsgi) that I should use instead?
Set web.config.debug = True before creating your app. That enables debug error, which contains the stack trace of exception along with values of locals.
When debugging apache2 and web.py, it's usually good to catch errors in the apache error log. When you get an internal server error, for instance, it means nothing was returned for whatever reason by your app.
On Linux, I just watch the error log in a separate terminal...
tail -f /var/log/apache2/error_log
or
tail -f /var/log/httpd/error_log
or something depending on your distribution. If there's a typo or error message or what not, you'll get the typical python stack trace in your error log even if you get an internal server error in your browser.
Lack of cgitb was really slowing me down, too. This did it for me:
try:
Output+=TroublesomeScript(etc)
except:
import traceback;
Output+=str(traceback.format_exc())
You can beautify the output if you like but this should give you the information you need for debugging. You can also just output sys.exc_info(), but the traceback module seems to be recommended.