My command is:
telepresence --swap-deployment {project_name} --expose 8080 --namespace {project_namespace}
And the error msg is:
connector.Connect: rpc error: code = Unknown desc = unsupported traffic-manager version 2.4.0. Minimum supported version is 2.4.5
How could I upgrade the traffic-manager?
Related
I'm having a problem connecting to a remote instance of Influx 2.0 OSS using the influx client.
First, I'm pretty sure it's not the server:
curl http://192.168.1.7:8086/health
{"name":"influxdb", "message":"ready for queries and writes", "status":"pass", "checks":[], "version": "2.0.7", "commit": "2a45f0c037"}
I have a config set, when I try to use it to ping the server:
❯ influx config
Active Name URL Org
* myinfluxd http://192.168.1.7 my_org
❯ influx ping
Error: Invalid character '<' looking for beginning of value.
Error: Invalid character '<' looking for beginning of value.
See 'influx ping -h' for help
Other commands also don't work
❯ influx query 'show databases;'
Error: Failed to read metadata: missing expected annotation datatype.
Error: Invalid character '<' looking for beginning of value.
See 'influx query -h' for help
I'm using the client on a Mac with BigSur (installed with homebrew), the client version and server version are the same (2.0.7).
Client
❯ influx version
Influx CLI 2.0.7 (git: none) build_date: 2021-07-02T03:23:38Z
Server
❯ influx version
Influx CLI 2.0.7 (git: none) build_date: 2021-07-02T03:23:38Z
root#influxdb2:/# influx config
Active Name URL Org
* default http://localhost:8086 my_org
Any ideas?
I am trying to install the Elastic Cloud on Kubernetes (ECK) Kubernetes operator with the all-in-one.yaml file, as per the tutorial: https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-install-all-in-one.html
But I am getting an error:
Error from server: error when creating "https://download.elastic.co/downloads/eck/1.3.1/all-in-one.yaml": the server responded with the status code 413 but did not return more information (post customresourcedefinitions.apiextensions.k8s.io)
I am a bit lost as to how to proceed solving this issue...
Command:
kubectl apply -f https://download.elastic.co/downloads/eck/1.3.1/all-in-one.yaml --insecure-skip-tls-verify
complete log:
namespace/elastic-system unchanged
serviceaccount/elastic-operator unchanged
secret/elastic-webhook-server-cert unchanged
configmap/elastic-operator unchanged
customresourcedefinition.apiextensions.k8s.io/apmservers.apm.k8s.elastic.co configured
customresourcedefinition.apiextensions.k8s.io/beats.beat.k8s.elastic.co configured
customresourcedefinition.apiextensions.k8s.io/enterprisesearches.enterprisesearch.k8s.elastic.co configured
customresourcedefinition.apiextensions.k8s.io/kibanas.kibana.k8s.elastic.co configured
clusterrole.rbac.authorization.k8s.io/elastic-operator unchanged
clusterrole.rbac.authorization.k8s.io/elastic-operator-view unchanged
clusterrole.rbac.authorization.k8s.io/elastic-operator-edit unchanged
clusterrolebinding.rbac.authorization.k8s.io/elastic-operator unchanged
service/elastic-webhook-server unchanged
statefulset.apps/elastic-operator configured
validatingwebhookconfiguration.admissionregistration.k8s.io/elastic-webhook.k8s.elastic.co configured
Error from server: error when creating "https://download.elastic.co/downloads/eck/1.3.1/all-in-one.yaml": the server responded with the status code 413 but did not return more information (post customresourcedefinitions.apiextensions.k8s.io)
UPDATE 1:
Running the command (with windows powershell):
curl https://download.elastic.co/downloads/eck/1.3.1/all-in-one.yaml | kubectl apply --insecure-skip-tls-verify -f-
I get:
error: error parsing STDIN: error converting YAML to JSON: yaml: line 7: mapping values are not allowed in this context
UPDATE 2:
current versions:
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6", GitCommit:"dff82dc0de47299ab66c83c626e08b245ab19037", GitTreeState:"clean", BuildDate:"2020-07-15T16:51:04Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
I managed to fix the issue by setting the proxy-body-size config map value in the system nginx config map to 8m.
proxy-body-size=8m
Namespace=ingress-nginx
Config Map=nginx-configuration
thank you #juan-carlos-alafita for providing the relevant links!
413 error with Kubernetes and Nginx ingress controller
https://www.digitalocean.com/community/questions/413-request-entity-too-large-nginx
I have been trying to install phpredis to my aws ec2 instance, but i keep on encountering same error when running 'sudo make test' in the phpredis folder.
PHP Warning: PHP Startup: Unable to load dynamic library '/tmp/phpredis-phpredis-59503a8/modules/redis.so' - /tmp/phpredis-phpredis-59503a8/modules/redis.so: undefined symbol: json_globals in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library '/tmp/phpredis-phpredis-59503a8/modules/redis.so' - /tmp/phpredis-phpredis-59503a8/modules/redis.so: undefined symbol: json_globals in Unknown on line 0
=====================================================================
PHP : /usr/bin/php
Warning: PHP Startup: Unable to load dynamic library '/tmp/phpredis-phpredis-59503a8/modules/redis.so' - /tmp/phpredis-phpredis-59503a8/modules/redis.so: undefined symbol: json_globals in Unknown on line 0
PHP_SAPI : cli
PHP_VERSION : 7.0.33
ZEND_VERSION: 3.0.0
PHP_OS : Linux - Linux ip-172-31-4-98 4.14.128-87.105.amzn1.x86_64 #1 SMP Thu Jun 20 00:43:44 UTC 2019 x86_64
INI actual : /tmp/phpredis-phpredis-59503a8/tmp-php.ini
More .INIs :
CWD : /tmp/phpredis-phpredis-59503a8
Extra dirs :
VALGRIND : Not used
TIME START 2019-07-10 16:20:09
With this error keep on occuring, there's no way for the Redis to be working at all if I copied redis.so to my php7.0 modules.
I'm currently using Amazon Linux with php7.0, redis5.0.5 and phpredis from https://github.com/nicolasff/phpredis/zipball/master.
I've successfully installed redis before with similar configuration, but i've no idea why i cant seem to solve this problem at all.
Redis will not show in phpinfo as well.
Hi I try to use this awesome Gradle plugin: https://github.com/bmuschko/gradle-docker-plugin
I use the following URL obtained from my docker-machine / kitematic installation on osx:
docker-machine url default
tcp://192.168.99.100:2376
However using:
url = "tcp://192.168.99.100:2376"
results in the error:
org.apache.http.conn.UnsupportedSchemeException: tcp protocol is not supported
When I change the tcp to httpI get a different error:
INFO org.apache.http.impl.execchain.RetryExec - I/O exception (java.net.SocketException) caught when processing request: Broken pipe
[pool-4-thread-1] ERROR com.github.dockerjava.core.async.ResultCallbackTemplate - Error during callback
org.apache.http.client.ClientProtocolException
in case the gradle dockerBuildImage task is run.
But manually building the Dockerfile created by gradle works without any problems.
The following code can be used to replicate the problem. https://github.com/geoHeil/lab04/blob/master/build.gradle
Docker-machine enables TLS by default. I Switching to the TLSmode should be a good solution:
url = 'https://192.168.59.103:2376'
certPath = new File(System.properties['user.home'], '.boot2docker/certs/boot2docker-vm')
I am tring to connect HBASE with jasperreports-server-cp-6.0.1. I have hadoop 2.5.2 and hbase-1.0.1 installed on my system.
I have installed HBasePlugin-0.5.1.nbm plugin in iReport 5.6.0.
I have followed all the steps given in: http://community.jaspersoft.com/wiki/hadoop-hbase
When I write the following Query:
{ "tableName" : "blogposts", "deserializerClass" : "com.jaspersoft.hbase.deserialize.impl.ShellDeserializer" }
In iReport, I am getting the following error:
Message:
net.sf.jasperreports.engine.JRException: No deserializer defined
Level:
SEVERE
Stack Trace:
No deserializer defined
com.jaspersoft.hadoop.hbase.query.HBaseQueryWrapper.<init>(HBaseQueryWrapper.java:152)
com.jaspersoft.hadoop.hbase.HBaseFieldsProvider.getFields(HBaseFieldsProvider.java:50)
com.jaspersoft.ireport.hbase.designer.HBaseFieldsProvider.getFields(HBaseFieldsProvider.java:57)
com.jaspersoft.ireport.hbase.connection.HBaseConnection.readFields(HBaseConnection.java:185)
com.jaspersoft.ireport.designer.wizards.ConnectionSelectionWizardPanel.validate(ConnectionSelectionWizardPanel.java:146)
org.openide.WizardDescriptor$7.run(WizardDescriptor.java:1357)
org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572)
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997)
Could you please help me with this error (I also tried with iReport 4.0.2, but I received the same error)?
Both iReport and the HBase connector are outdated.
Try using the Apache Phoenix JDBC driver which is compatible with the latest release (6.2) of the Jaspersoft products:
http://community.jaspersoft.com/wiki/how-use-apache-phoenix-jdbc-driver-run-reports-hbase
Thanks!