I have a spark (version 2.2.0) cluster with 7 nodes and url spark://master:7077. I setup Apache Zeppelin 0.7.2 on the master node using the following configuration:
zeppelin.env.sh
export JAVA_HOME=/usr/local/java/jdk1.8.0_144
export SPARK_HOME=/usr/local/spark-2.2.0
export MASTER=spark://master:7077
export ZEPPELIN_PORT=8082
In zeppelin-site.xml I changed zeppelin.server.port from 8080 to 8082, also tried with other ports like 8090, 8091.
After starting zeppelin when I try to access web UI using master:8082 I got the following error but zeppelin status shows it is running:
HTTP ERROR: 500
Problem accessing /. Reason: javax.servlet.HttpServletRequest.isAsyncStarted()Z
I checked the logs and found that java.lang.NoSuchMethodError:javax.servlet.HttpServletRequest.isAsyncStarted()Z
Related
I'm following RedwoodJS Tutorial - Getting Dynamic and there's a proxy error when requesting localhost:8910/posts
api | API listening on http://localhost:8911/
api | GraphQL endpoint at /graphql
api | 11:14:25 đ˛ Server listening at http://[::]:8911
web | <e> [webpack-dev-server] [HPM] Error occurred while proxying request localhost:8910/graphql to http://[::1]:8911/ [ENETUNREACH] (https://nodejs.org/api/errors.html#errors_common_system_errors)
Ensure that your node and yarn versions match the prerequisites;
node: ">=14.19 <=16.x"
yarn: ">=1.15"
you can add RWJS_DEV_API_URL="http://localhost" to your environment variable; either by running RWJS_DEV_API_URL=âhttp://localhostâ yarn rw dev or as a new line to your .env file
I'm trying to connect to google sql cloud instance from custom runtime environment in App Engine.
When I follow the doc to connect using unix domain socket, it works. The problem is when I try to connect using a TCP connect. It shows:
Warning: mysqli_connect(): (HY000/2002): Connection refused in
/var/www/html/index.php on line 3
Connect error: Connection refused
This is my app.yaml file:
runtime: custom
env: flex
beta_settings:
cloud_sql_instances: testing-mvalcam:europe-west1:testdb=tcp:3306
resources:
cpu: 1
memory_gb: 0.5
disk_size_gb: 10
The Dockerfile:
FROM php:7.0-apache
ENV PORT 8080
CMD sed -i "s/80/$PORT/g" /etc/apache2/sites-available/000-default.conf /etc/apache2/ports.conf && docker-php-entrypoint apache2-foreground
RUN docker-php-ext-install mysqli
RUN a2enmod rewrite
COPY ./src /var/www/html
EXPOSE $PORT
And index.php:
<?php
$link = mysqli_connect('127.0.0.1', 'root', 'root', 'test');
if (!$link){
die('Connect error: '. mysqli_connect_error());
}
echo 'successfully connected';
mysqli_close($link);
?>
What am I doing Wrong?
The ip address â172.17.0.1â is related with the docker container where the webserver is running, you can get more context on that in this documentation.
The documentation page youâre using might be lacking on adjusting the use case if youâre deploying with a presence of a Dockerfile. In the following documentation you can read more information about App Engine flexible runtimes.
As demonstrated by the documentation youâre using (remember to click on the TCP CONNECTION tab on this page), on the section of the app.yaml related to Cloud SQL instances information about the TCP port in use by the database server is needed.
I am using pike release of openstack and ceilometer version 2.9.0 and keystone v3.
$ceilometer meter-list gives HTTP 404 Not Found error
$gnocchi metric list --> HTTP 401
$openstack metric list ---> lists the meters (works) . However in yaml file(for autoscaling) I am unable to get metrics using type OS:Ceilometer::Alarm
How to go about it, please guide. Is there any workaround for the issue I am facing?
I've trouble in connecting to a wss secured socket server via google appengine frontend with managed VM support.
buy default google exposes only port 8080 in docker image google/nodejs-runtime, Even if expose port 8443 in Dockerfile like below i can connect only to http://localhost:8080 not https://localhost:8443
FROM google/nodejs
WORKDIR /app
ADD package.json /app/
RUN npm install
ADD . /app
EXPOSE 8443
CMD []
ENTRYPOINT ["/nodejs/bin/npm", "start"]
Still i can see port 8080 include in the container
"/nodejs/bin/npm start 8443/tcp, 0.0.0.0:8080->8080/tcp
If i log in to my managed vm instance and run the container image with
docker run -d -p 8443:8443 nodejs.default.wss-check:latest
and try
$curl https://localhost:8443
I get curl: (60) SSL certificate problem: unable to get local issuer certificate, It looks like its connecting but i've to use realdomain name
I've created a issue in github aswell https://github.com/GoogleCloudPlatform/appengine-nodejs-quickstart/issues/13, but not that helpful.
Same set up works like a charm in normal compute instance. but it doesn't auto scale.
Any help on this issue will be appreciated.
The reason you can't curl to https on localhost (curl: (60) SSL certificate problem: unable to get local issuer certificate) is because "localhost" is unknown to any CA. You need to run curl -k https://localhost:8443 to get it to ignore the lack of a certificate for localhost.
Looks like currently Google Managed VM supports Websocket connection only on JAVA
Even if you try websocket connection on with nodejs on GMV it defaults to polling transport. if you wanna see this in live you can use set socket transports, deploy to live and look in to console- network and see which transport its using!
socket.set('transports', [
'websocket'
, 'flashsocket'
, 'htmlfile'
, 'xhr-polling'
, 'jsonp-polling'
]);
We have to wait untill google implements websocket support in Managed VM. If anyone get this working on GMV, Please comment here :)
I am trying to upload some data to my local datastore in appengine.
The command I am using is the next one:
appcfg.py upload_data --config_file="C:\config.yml" --filename="C:\mycsv.csv" --url=http://localhost:8888/remote_api --kind=MyEntity
The problem is that I'm working behind my company proxy and I am getting the next ERROR even trying to connect to the localhost server:
Error Code: 502 Proxy Error. The ISA Server denied the specified Uniform Resource Locator (URL). (12202)
It seems the authentication is ok, but somehow the proxy tries to filter my connection to my own computer.
Some ideas about how can I solve this?
Thanks.
Remove/disable proxy settings of your network then try the above command.
I was facing the similar issue and this issue resolved when i disable my proxy settings.