I tried installing Hue in Amazon EMR using the link https://github.com/cloudera/hue .I am seeing the status
development server running at http://127.0.0.1:8000/
Am also able to curl the url and but getting blank page. The curl content.
"<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<meta http-equiv="refresh" content="0; url=/beeswax">
</head>
<body>
</body>
</html>"
But when I hit the browser using the public dns url with port 8000 i am getting error page. Am i missing any steps.
Thanks
What error page are you seeing? It could be just that you did no open 8000 or binded the server on runserver 0.0.0.0:8000 when started it. Also it is recommended to start Hue with runcpserver instead of the development server.
You are running on the loopback interface 127.0.0.1. This is only accessible from the host not externally. You need to change you hue.ini
and set:
http_host=0.0.0.0
Related
From this link, it says :
Once an application is cached, it remains cached until one of the
following happens:
The user clears the browser's cache
The manifest file is modified (see tip below)
The application cache is programmatically updated
Following the instruction from the internet, for the manifest file I use a version number. When I change the content of the index.html with 01.jpg to 02.jpg - I also changed the version number of the manifest file.
With the steps above, it works within my Win7 Wamp Server Local Host. But once I do the same steps in my web server (after uploading the file to the web server) - it doesn't work.
Can somebody please help me what did I do wrong ?
Document was loaded from Application Cache with manifest http://www.example.com/test/offline.appcache
Application Cache Checking event
Navigated to http://www.example.com/test/
Application Cache NoUpdate event
Above is from the Chrome browser console after I modified the version number of the manifest file (from #01 to #02) and the jpg file (from 01.jpg to 02.jpg) in the index.html file.
The offline.appcache CACHE file list no change, except the version number :
CACHE MANIFEST
# 2017-03-25 version#01
uploads/event.jpg
uploads/baby.jpg
/favicon.ico
NETWORK:
indexPHP.php
The index.html file :
<!DOCTYPE html>
<html manifest="offline.appcache">
<head>
<meta name="viewport" content="width=device-width, initial-scale=1">
<style></style>
</head>
<body>
<img src="uploads/01.jpg">
</body>
</html>
<script type="text/javascript">
function onUpdateReady() {
alert("offline files will be updated");
window.location.reload();
}
window.applicationCache.addEventListener('updateready', onUpdateReady);
if(window.applicationCache.status === window.applicationCache.UPDATEREADY) {
onUpdateReady();}
</script>
the .htaccess file :
AddType text/cache-manifest .appcache
the "tree" :
example.com/.htaccess
example.com/favicon.ico
example.com/test/index.html
example.com/test/offline.appcache
example.com/test/uploads/01.jpg
example.com/test/uploads/02.jpg
Thank you in advanced.
I am using CentOS 6.5, when I am giving the following command, curl is working fine and it returns me a proper output:
curl --data "atoken=0564af8vabe91f2d1a82fb1j375345733e35b707" http://www.mywebsite.com/something.json
However, I need the same thing on my local machine. In this case, it's not working:
curl --data "atoken=0564af8vabe91f2d1a82fb1j375345733e35b707" http://localhost/something.json
It gives errors and the output like:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>Action Controller: Exception caught</title>
<style>
body {...
Please help.
Also, how can I get the atoken for localhost?
Curl is working... what's not working is the JSON service. It's expecting data that it's not getting, or it's not configured correctly on localhost.
I am reading documentation of symfony1.4 becouse I've to learn it due to a legacy code. At some point documentation says:
Then, download the symfony configuration checker script at the following URL:
So I'd tried to run
$ curl -d "" http://sf-to.org/1.4/check.php
I received the message:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved here.</p>
</body></html>
Then, I've tried to run
$ curl -d "" http://svn.symfony-project.com/branches/1.4/data/bin/check_configuration.php
getting this error:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>401 Authorization Required</title>
</head><body>
<h1>Authorization Required</h1>
<p>This server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.</p>
</body></html>
In my opinion it's best to use the git repository of symfony:
https://github.com/symfony/symfony1
The check_configuration.php file can be found here:
https://github.com/symfony/symfony1/blob/1.4/data/bin/check_configuration.php
or if you want just the contents of the file:
https://raw.github.com/symfony/symfony1/1.4/data/bin/check_configuration.php
I'm working with a small app on Heroku and I'm wondering if a heroku run rake db:migrate will affect the production database. Any thoughts?
I tried heroku db:pull but the pull stopped midway (not to mention that it screwed up my local db):
Schema: 60% |==================================================================================== | ETA: 00:00:16
Saving session to pull_201207010723.dat..
!!! Caught Server Exception
HTTP CODE: 503
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<style type="text/css">
html, body, iframe { margin: 0; padding: 0; height: 100%; }
iframe { display: block; width: 100%; border: none; }
</style>
<title>Application Error</title></head>
</head>
<body>
<iframe src="//s3.amazonaws.com/heroku_pages/error.html">
<p>Application Error</p>
</iframe>
</body>
</html>
Additional notes: local development db is sqlite3 and production db (by Heroku standard is postgresql). The devel db was like that by default and I couldn't find a nice tutorial to convert to postgresql.
Thanks a bunch!
Running heroku run rake db:migrate will indeed alter your database on Heroku -- so it will change your production database.
Whenever I try to push my local mysql database to Amazon RDS I get a 503 application error:
bundle exec heroku db:push
...
Sending schema
Schema: 40% |================ | ETA: 00:00:38
Saving session to push_201106170529.dat..
!!! Caught Server Exception
HTTP CODE: 503
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<style type="text/css">
html, body, iframe { margin: 0; padding: 0; height: 100%; }
iframe { display: block; width: 100%; border: none; }
</style>
<title>Application Error</title></head>
</head>
<body>
<iframe src="https://s3.amazonaws.com/heroku_pages/error.html">
<p>Application Error</p>
</iframe>
</body>
</html>
I'm using taps 0.3.23
While the error message is similar to the one reported here : Heroku help Amazon RDS rails push database error my problem is not related to Amazon's security group as this is already configured.
Anybody else encountering this issue?
I got the same HTML response message and HTTP error code using Heroku with a CURL POST request.
Executing heroku logs | tail gave me more insights:
2016-04-20T10:56:17.509354+00:00 heroku[router]:
at=error code=H12 desc="Request timeout" method=POST [...]
The H12 error denotes a request timeout. That means an "HTTP request took longer than 30 seconds to complete" [1].
More on request timeouts on https://devcenter.heroku.com/articles/request-timeout.
[1] https://devcenter.heroku.com/articles/error-codes#h12-request-timeout
I had the same response with heroku db:push, the first time I attempted.
However, when I ran it a second time, there was no error, and the db pushed.