I tried to install Context Broker version 1.7.0 on my Centos 6 VM.
I successfully installed it but while the service is running ,when i make a request with curl i get the message "couldn't connect to host"
I checked the port 1026 and the firewall and everything is ok.
Any ideas what may be the problem?
The best way to install Orion is using Docker to test or study: (https://hub.docker.com/r/fiware/orion/).
Docker and docker-compose. You install Orion and Mongodb together, in a quick time. (https://github.com/telefonicaid/fiware-orion/tree/master/docker)
Have you tried using this method?
With it you can use the last stable version (1.10.0).
Related
I recently upgraded Zabbix to 5.4.1 and I wanted to start using scheduled report, but I've got some problems with conifguration (error Cannot connect to web service: couldn't connect to server).
My Zabbix is running in Docker on Debian Buster. Everything is based on official containers:
Zabbix Server (PostgreSQL), Zabbix Frontend (Apache, PostreSQL) and PostgreSQL12.
According do documentation (https://www.zabbix.com/documentation/current/manual/appendix/install/web_service) I installed Google Chrome browser:
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo apt install ./google-chrome-stable_current_amd64.deb
and Zabbix Web Service
wget https://repo.zabbix.com/zabbix/5.4/debian/pool/main/z/zabbix-release/zabbix-release_5.4-1+debian10_all.deb
dpkg -i zabbix-release_5.4-1+debian10_all.deb
apt install zabbix-web-service
I eddited zabbix_web_service.conf:
AllowedIP=127.0.0.1,::1,0.0.0.0/0,zabbix
I edited zabbix_server.conf:
StartReportWriters=1
WebServiceURL=http://localhost:10053/report
I eddited settings in Zabbix Frontend - Administration -> General -> Other
Frontend URL: http://localhost:8085 (frontend is available at port 8085)
But when I try to test report generating i get error:
Cannot connect to web service: couldn't connect to server
I've already tried with other Frontend URLs, but nothings seems to work. I tried with:
http://localhost:10053/report
http://192.168.10.18:8085/
http://192.168.10.18:10053/report
I've verified that I get answear from http://192.168.10.18:10053/report :
{"detail":"Method is not supported."}
What else can I check/try?
I found the problem. In server configuration I was usinng address http://localhost:10053/report it was wrong because in my case Zabbix server is running in docker and Zabbix web service is not running in docker. Zabbix server wasn't albe to connect to web servcie because it was in the other network. I changed the configuration and now everything works fine. Reports are beeing generated and send
I am getting the connection time out when running the command in bootstrap.
Any configuration suggestions on networking part if I am missing
It’s says kubernetes api calling time out
This is obviously very hard to debug without having access to your environment. Some tips to debug the OKD installation:
Before starting the installation, make sure your environment meets all the prerequisites. Often, the problem lies with a faulty DNS / DHCP / networking setup. Potentially deploy a separate VM into the network to check if everything works as expected.
The bootstrap node and the Master Nodes are deployed with the SSH key you specify, so in vCenter, get the IP of the machines that are already deployed and use SSH to connect to them. Once on the machine, use sudo crictl ps and sudo crictl logs <container-id> to review the logs for the running containers, focussing on the components:
kube-apiserver
etcd
machine-controller
In your case, the API is not coming up, so reviewing the logs of the above components will likely show the root cause.
I recently deployed an instance of Ubuntu 16.04 on FIWARE Lab and accessed it using putty, I downloaded docker & docker-compose, I successfully installed fiware-orion & mongo-db as I followed the tutorial, I tried to follow the iot sensor tutorial but whenever I try to start the service it keeps stucking in this infinte loop -> Context Broker HTTP state : 000 (waiting for 200).
Any suggestions?
Details
region:crete
image: ubuntu 16.04
putty infinite loop
The problem was that the docker-compose did not include Orion (and MongoDB) instance which are required dependencies for this tutorial. We have updated the corresponding docker-compose file in order to include both dependencies and now it is working properly. Tips: do not forget to open the corresponding port (3000) in the security and assign a floating IP to the virtual machine to access to the /device/monitor (do not use localhost for accessing it).
Trying to install Gerrit on a Mac that has also Jenkins installed. So far:
Installed MySQL via Brew successfully.
Added user & db for Gerrit to MySQL.
D/l of gerrit.war from https://gerrit-releases.storage.googleapis.com/index.html
Installed gerrit.war into ~/Applications/Gerrit
Set canonicalWebUrl to http://localhost:8080/gerrit/ in gerrit.config
Restart Gerrit with ~/Applications/Gerrit/bin/gerrit.sh restart
But restart fails. There seems to be no consistent Mac Gerrit setup guide whatsoever and I feel I'm stuck with this issue.
Gerrit error_log says:
ERROR com.google.gerrit.pgm.Daemon : Unable to start daemon
java.lang.IllegalStateException: Cannot start HTTP daemon
Has anyone running this config on a Mac and can give me some help?
on a Mac that has also Jenkins installed
Most likely the cause is that Jenkins is already running on the same port (8080). Try to change Gerrit's canonicalWebUrl to another port (or change Jenkins' port).
This might be a very simple question for those who are running Mule on linux. I have developed Mule ESB 3.3 app on a windows 8 machine and tested to get desired results by calling my app at
http://localhost:8081/myFlowPath
Now I have deployed same app on to a linux machine behind a firewall successfully but am unable to hit it at http://linuxDomainname.com:8081/myFlowPath. The connection is refused. Am I missing something in configuring mule to run on linux?
We are running Mule CE 3.3 standalone as a linux demon. Do I have to explicitly specify something like the port or hostname in the wrapper.conf? Please let me know. Any help is highly appreciated.
Thanks,
Jenni
You have to configure HTTP Listener host to 0.0.0.0 (change from localhost).
Check log mule at HOME_MULE/logs/mule.log or webservice.log
After deploy your app you must have in HOME_MULE/apps/nameofyourapp/webservice.xml (or filename defined in "config.resources" in file mule-deploy.properties) this:
It work for me. I deploying my mule apps on Ubuntu 16.04 LTS, Mule ESB 3.8.1.
If this not work, it mean that you blocked that port (8081) on this machine (or firewall). Check iptables or another your 3th-party firewall.
Mule handle it easily by using the application properties. Create property files for each environment local|develop|prod.
local.properties
api.host=0.0.0.0
api.port=8080
prod.properties
api.host=127.0.0.1
api.port=9090
Read more about the mule service configuration management at https://docs.mulesoft.com/mule-runtime/3.9/configuring-properties.