i'm change the php73-fpm port from 9000 into 9001, because the port of 9000 is used by another service, but when i start the icingaweb2 service it shows that the php73-fpm is not started, so i assumed that the icingaweb2 still use the old port that 9000 and not 9001, how to change the configuration for php73-fpm port in icingaweb2 ?
systemctl status rh-php73-php-fpm.service
the result :
enter image description here
php73-fpm active port : enter image description here
IcingaWeb2 error :
enter image description here
IcingaWeb2 error :
Backend unavailable
It seems that the PHP FPM service is not running. Make sure to start PHP FPM service in order to access Icinga Web 2. If you upgraded Icinga Web 2 recently, make sure to read the docs regarding PHP FPM, also locally available under /usr/share/icingaweb2/doc/02-Installation.md.
So I have a domain http://leafapi.co.uk/ linked to my elastic beanstalk environment successfully and I'm trying to set it up with HTTPS. I've set up a load balancer listener on 443 in my elastic beanstalk configuration using an SSL certificate.
I think the last thing I need to do is configure a security group from my project file with a config file that looks like this:
Resources:
sslSecurityGroupIngress:
Type: AWS::EC2::SecurityGroupIngress
Properties:
GroupId: {"Fn::GetAtt" : ["AWSEBSecurityGroup", "GroupId"]}
IpProtocol: tcp
ToPort: 443
FromPort: 443
SourceSecurityGroupName: {"Fn::GetAtt" : ["AWSEBLoadBalancer" , "SourceSecurityGroup.GroupName"]}
However when I try to deploy I get the following error:
Service:AmazonCloudFormation, Message:Template error: instance of Fn::GetAtt references undefined resource AWSEBLoadBalancer
Any suggestions would be greatly appreciated, thanks.
The problem was actually that I prepended my SSL certificate domain name with 'www.'. After getting the right SSL certificate it worked without the config above.
I got this when trying to update from a Classic Load Balancer to an Application Load Balancer - in this case AWSEBLoadBalancer was no longer defined but AWSEBV2LoadBalancer now was.
See https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customize-containers-format-resources-eb.html
I am able to connect elasticsearch. However, I am unable to access kibana on 5601. Can anyone please help out this to work? Thanks in advance.
In the kibana.yml file, I have modified the server.host parameter to point to my domain.
Elasticsearch Version: 7.7.0
Kibana Version: kibana-7.7.0-1.x86_64
OS: Centos 7
JAVA Version: 11
kibana.yml
server.port: 5601
server.host: "my_domain"
elasticsearch.hosts: ["http://my_domain:9200"]
Kibana Logs
{"type":"log","#timestamp":"2020-06-02T14:08:03Z","tags":["warning","plugins-discovery"],"pid":2844,"message":"Expect plugin \"id\" in camelCase, but found: apm_oss"}
{"type":"log","#timestamp":"2020-06-02T14:08:03Z","tags":["warning","plugins-discovery"],"pid":2844,"message":"Expect plugin \"id\" in camelCase, but found: file_upload"}
{"type":"log","#timestamp":"2020-06-02T14:08:03Z","tags":["warning","plugins-discovery"],"pid":2844,"message":"Expect plugin \"id\" in camelCase, but found: triggers_actions_ui"}
{"type":"log","#timestamp":"2020-06-02T14:08:09Z","tags":["info","plugins-service"],"pid":2844,"message":"Plugin \"infra\" has been disabled since some of its direct or transitive dependencies are missing or disabled."}
{"type":"log","#timestamp":"2020-06-02T14:08:27Z","tags":["warning","plugins-discovery"],"pid":2941,"message":"Expect plugin \"id\" in camelCase, but found: apm_oss"}
{"type":"log","#timestamp":"2020-06-02T14:08:27Z","tags":["warning","plugins-discovery"],"pid":2941,"message":"Expect plugin \"id\" in camelCase, but found: file_upload"}
{"type":"log","#timestamp":"2020-06-02T14:08:27Z","tags":["warning","plugins-discovery"],"pid":2941,"message":"Expect plugin \"id\" in camelCase, but found: triggers_actions_ui"}
{"type":"log","#timestamp":"2020-06-02T14:08:32Z","tags":["info","plugins-service"],"pid":2941,"message":"Plugin \"infra\" has been disabled since some of its direct or transitive dependencies are missing or disabled."}
{"type":"log","#timestamp":"2020-06-02T14:08:35Z","tags":["fatal","root"],"pid":2941,"message":"{ Error: listen EADDRNOTAVAIL: address not available localhost:5601\n at Server.setupListenHandle [as _listen2] (net.js:1263:19)\n at listenInCluster (net.js:1328:12)\n at doListen (net.js:1461:7)\n at process._tickCallback (internal/process/next_tick.js:63:19)\n code: 'EADDRNOTAVAIL',\n errno: 'EADDRNOTAVAIL',\n syscall: 'listen',\n address: 'localhost',\n port: 5601 }"}
Kibana runs on port 5601 by default. This error message says that, when Kibana tried to start up & bind to port 5601, it couldn't because something else was already bound to port 5601.
Check if some application is already bound to port 5601. If yes, Try
another port.
If No, Then It would be easy to investigate the issue, if you could attach the contents of your /etc/hosts file.
While attempting to create index with Elastalert using command elastalert-create-index for a basic-auth secured instance using port:5601 ,it fails with error:
elasticsearch.exceptions.SerializationError: Unknown mimetype, unable to deserialize: text/html
It seems that the default port to use for the authenticantication is where Kibana is running on port 9200
I'm currently runnning Elasticsearch (ES) 5.5 inside a Docker container. (See below)
curl -XGET 'localhost:9200'
{
"name" : "THbbezM",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "CtYdgNUzQrS5YRTRT7xNJw",
"version" : {
"number" : "5.5.0",
"build_hash" : "260387d",
"build_date" : "2017-06-30T23:16:05.735Z",
"build_snapshot" : false,
"lucene_version" : "6.6.0"
},
"tagline" : "You Know, for Search"
}
I've changed the elasticsearch.yml file to look like this:
http.host: 0.0.0.0
# Uncomment the following lines for a production cluster deployment
#transport.host: 0.0.0.0
#discovery.zen.minimum_master_nodes: 1
network.host: 0.0.0.0
http.port: 9200
I can currently get my indexes through curl -XGET commands. The thing here is that I wanted to be able to do http requests to this ES instance using it's Ip Address instead of the 'localhost:9200' setting starting from my machine (Mac OS X).
So, what I've tried already:
1) I've tried doing it in Postman getting the following response:
Could not get any response
There was an error connecting to X.X.X.X:9200/.
Why this might have happened:
The server couldn't send a response:
Ensure that the backend is working properly
Self-signed SSL certificates are being blocked:
Fix this by turning off 'SSL certificate verification' in Settings > General
Client certificates are required for this server:
Fix this by adding client certificates in Settings > Certificates
Request timeout:
Change request timeout in Settings > General
2) I also tried in Sense (Plugin for Chrome):
Request failed to get to the server (status code: 0):
3) Running a curl from my machine's terminal won't do it too.
What am I missing here?
Docker for Mac provides a DNS name you can use:
docker.for.mac.localhost
You should use the value specified under container name in the YML file to connect to your cluster. Example:
services:
elasticsearch:
container_name: 'example_elasticsearch'
image: 'docker.elastic.co/elasticsearch/elasticsearch:6.6.1'
In this case, elastic search is located at http://example_elasticsearch:9200. Note that example_elasticsearch is the name of the container and may be used the same way as machine name or host name.