1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Kibana error when starting the service

Discussion in 'Install Logstash and Kibana on a Windows server.' started by Rick Tuck, Aug 13, 2015.

  1. Rick Tuck

    Rick Tuck New Member Member

    I have deployed ELK on Windows 8.1 VM. All of the other services are running except Kibana.

    When I start the Kibana service a message displays "Windows could not start the kibana service on Local Computer. The service did not return an error. This could be an internal Windows error or an internal service error."

    I looked in the eventnwr and saw no issues
     
  2. sbagmeijer

    sbagmeijer Machine

    Did you first start all your other services such as Logstash/Elasticsearch?

    If you did then try start Kibana from CMD prompt it should show some more details as why it breaks, if you can post the error perhaps here then I can have a look.

    I am not at a pc right now with this installed but if I remember correctly you can run this:
    Code:
    C:\ulyaoth\kibana\bin\kibana.bat
    Or else have a look with notepad in that bat file to see how they start it, and do that manually from the terminal.
     
    Last edited: Aug 13, 2015
  3. Rick Tuck

    Rick Tuck New Member Member

    [Rick]

    Here is the error when I run the bat file
    moduke.js:340
    throw err;
    Error: Cannot find module 'commander'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (C:\logging\kibana\src\bin\kibana.js:3:15)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)


    I also forgot to mention that I did not setup the website with SSL(443). It is using http(80)
     
  4. sbagmeijer

    sbagmeijer Machine

    Sorry Rick, I made a mistake with the buttons and your post was gone.

    Just to continue it sounds that your are missing a module which is strange as it should come with Kibana, what version and package did you download?
     
  5. Rick Tuck

    Rick Tuck New Member Member

    kibana-4.1.1-windows
    JDK-8u51-windows-x64
    elasticsearch-1.6.0
    logstash-1.5.2
     
  6. sbagmeijer

    sbagmeijer Machine

    Alright, I am home now I will perform the guide once more to see if something changed.
    I don't have Windows 8.1 anymore so I will try it on Windows 10 but I hope that should not be a to big difference.

    I let you know.
     
  7. sbagmeijer

    sbagmeijer Machine

    It is very strange I am not very sure why it not works for you I tried it on Windows 10 and on Windows 2012 standard and it work for me:

    [​IMG]

    Are you perhaps trying to run it with a user that has no write right to the folder? (try as test run it with admin account)

    If that does not work I could try assist you with Team Viewer if you wish to have a look.
     
  8. Rick Tuck

    Rick Tuck New Member Member


    I was putting together a document to upload but the upload does not accept Word documents so I create png file to upload. Unfortunately I can't allow TeamViewer to access the companies system.

    I did create the SSL key and crt but I did not add it to the site. I am running as HTTP
     

    Attached Files:

  9. Rick Tuck

    Rick Tuck New Member Member

    It looks like you have changed the instructions a bit. I don't see the installation of logstash-forwarder and now we are installing nxlog.

    I set this up on a windows 2012 server and received the same error?

    in the nxlog.conf, does the HOST need to be the Web server IP address?

    <Output out_logstash>
    Module om_tcp
    Host 127.0.0.1
    Port 5544
    OutputType LineBased
    </Output>
     
  10. sbagmeijer

    sbagmeijer Machine

    Yes I updated the whole guide yesterday as the logstash-forwarder does not really work that great.
    nxlog is a more tested log shipper and supports windows event logs which logstash-forwarder does not so win win.

    The host needs to be the ip of the logstash agent.

    So logstash runs on port 5544 and 127.0.0.1 (for me), then nxlogs ships the logs to logstash, logstash does its magic and then puts the logs in elasticsearch.
    Kibana in turn reads then from elasticsearch.

    I am still looking trough your post :).
     
  11. sbagmeijer

    sbagmeijer Machine

    Perhaps a obvious question but did you extract the full zip file? and did you try to redownload if it is not a corrupt zip?

    I am right now on a Windows 8.1 vm and it worked also out of box nothing special.

    Does this exist for you for example?:
    Code:
    C:\ulyaoth\kibana\src\node_modules\commander>dir
    
    Directory of C:\ulyaoth\kibana\src\node_modules\commander
    
    2015-06-29  20:07    <DIR>          .
    2015-06-29  20:07    <DIR>          ..
    2015-06-29  20:07             6 266 History.md
    2015-06-29  20:07            24 300 index.js
    2015-06-29  20:07             1 098 LICENSE
    2015-06-29  20:07    <DIR>          node_modules
    2015-06-29  20:07            10 947 package.json
    2015-06-29  20:07             9 547 Readme.md
                   5 File(s)         52 158 bytes
                   3 Dir(s)  379 428 896 768 bytes free
    Also something to try is the older version:
    https://download.elastic.co/kibana/kibana/kibana-4.0.3-windows.zip

    Are you on a 64 bit or 32 bit os?
     
  12. Rick Tuck

    Rick Tuck New Member Member

    It looks like there were a lot of folders under src that were missing. So upzipped the file against and reinstalled kibana. Ran the elasticsearch.bat, logstash.bat and kibana.bat and no errors were produced.

    I am now able to start all windows services(elasticsearch, logstash, kibana and nxlog).

    When I went to http://loghost.logging.net I am receiving a 502.
    502 - Web server received an invalid response while acting as a gateway or proxy server.
    There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the content server.

    I looked in the event log but did not see anything. Let me look through you setup instructions to see if anything else was missed
     
  13. sbagmeijer

    sbagmeijer Machine

    Great that it was something simple to fix!

    If you Followed the guide exactly then the reverse proxy I added is on the top level of iis, you probably have to enable the original vhost (Default web site) and disable the newly created one to get it to work.

    You can make the vhost work but you probably would need to do some rewrite on the vhost level then. (I could not get it to work so I left it out the guide and made some notes I hope they are clear)

    You can always test kibana locally by going to http://KIBANAIP:5601 just to bypass IIS and test it all works.
     
  14. Rick Tuck

    Rick Tuck New Member Member

    Almost there. I was able to bring up the kibana site. I am not receiving an error but there are no indices found based on the Pattern. Do you have any idea of what this may be?
    Pattern does not match any existing indices
     

    Attached Files:

  15. sbagmeijer

    sbagmeijer Machine

    It means there is no information shipped to elasticearch yet, logstash makes that pattern when it receives data.

    Normally if all is good then you refresh the kibana page a few times to generate some logs that nxlog will ship.

    If it not works you a have to go trough the whole chain:
    1. Check if nxlog is reading the correct log.
    2. Is nxlog reaching logstash.
    3. Is logstash reaching elasticsearch.
    4. Is kibana reaching elasticsearch.

    You probably have to start it all with cmd to debug the output it gives in the console each app.

    Also double check "logstash.conf" if the output to elasticsearch is the correct ip.
     
    Last edited: Aug 15, 2015
  16. Rick Tuck

    Rick Tuck New Member Member

    It looks like there is nothing listening on 5544: Here is some detail
    I am trying input one file at this time. All Windows services are running

    1). ** nxlog.conf **
    define ROOT C:\Program Files (x86)\nxlog

    Moduledir %ROOT%\modules
    CacheDir %ROOT%\data
    Pidfile %ROOT%\data\nxlog.pid
    SpoolDir %ROOT%\data
    LogFile %ROOT%\data\nxlog.log

    <Extension json>
    Module xm_json
    </Extension>
    <Input iis_logging>
    Module im_file
    File "D:\logging\logs\smps.log"
    ReadFromLast True
    SavePos True
    Exec if $raw_event =~ /^#/ drop();
    </Input>
    <Output out_logstash>
    Module om_tcp
    Host loghost.logging.net
    Port 5544
    OutputType LineBased
    </Output>

    <Route IIS>
    Path iis_logging => out_logstash
    </Route>


    2). ** nxlog.log ** Error
    2015-08-16 06:33:12 ERROR couldn't connect to tcp socket on loghost.logging.net:5544; No connection could be made because the target machine actively refused it.

    3). ** Portqry **

    It can resolve the IP address but there is nothing listening on for 5544
    =============================================

    Starting portqry.exe -n loghost.logging.net -e 5544 -p TCP ...


    Querying target system called:

    loghost.logging.net

    Attempting to resolve name to IP address...

    Name resolved to loghost.logging.net

    querying...

    TCP port 5544 (unknown service): NOT LISTENING
    portqry.exe -n loghost.logging.net -e 5544 -p TCP exits with return code 0x00000001.

    4). ** logstash.conf **
    input {
    tcp {
    port => 5544
    }
    }

    output {
    elasticsearch {
    host => "loghost.logging.net"
    protocol => "http"
    }
    }



    5). ** kibana.yml **
    # Kibana is served by a back end server. This controls which port to use.
    port: 5601

    # The host to bind the server to.
    host: "loghost.logging.net"

    # The Elasticsearch instance to use for all your queries.
    elasticsearch_url: "http://loghost.logging.net:9200"

    # preserve_elasticsearch_host true will send the hostname specified in `elasticsearch`. If you set it to false,
    # then the host you use to connect to *this* Kibana instance will be sent.
    elasticsearch_preserve_host: true

    # Kibana uses an index in Elasticsearch to store saved searches, visualizations
    # and dashboards. It will create a new index if it doesn't already exist.
    kibana_index: ".kibana"

    # If your Elasticsearch is protected with basic auth, this is the user credentials
    # used by the Kibana server to perform maintence on the kibana_index at statup. Your Kibana
    # users will still need to authenticate with Elasticsearch (which is proxied thorugh
    # the Kibana server)
    # kibana_elasticsearch_username: user
    # kibana_elasticsearch_password: pass

    # If your Elasticsearch requires client certificate and key
    # kibana_elasticsearch_client_crt: /path/to/your/client.crt
    # kibana_elasticsearch_client_key: /path/to/your/client.key

    # If you need to provide a CA certificate for your Elasticsarech instance, put
    # the path of the pem file here.
    # ca: /path/to/your/CA.pem

    # The default application to load.
    default_app_id: "discover"

    # Time in milliseconds to wait for elasticsearch to respond to pings, defaults to
    # request_timeout setting
    # ping_timeout: 1500

    # Time in milliseconds to wait for responses from the back end or elasticsearch.
    # This must be > 0
    request_timeout: 300000

    # Time in milliseconds for Elasticsearch to wait for responses from shards.
    # Set to 0 to disable.
    shard_timeout: 0

    # Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying
    # startup_timeout: 5000

    # Set to false to have a complete disregard for the validity of the SSL
    # certificate.
    verify_ssl: false

    # SSL for outgoing requests from the Kibana Server (PEM formatted)
    # ssl_key_file: /path/to/your/server.key
    # ssl_cert_file: /path/to/your/server.crt

    # Set the path to where you would like the process id file to be created.
    # pid_file: /var/run/kibana.pid

    # If you would like to send the log output to a file you can set the path below.
    # This will also turn off the STDOUT log output.
    # log_file: ./kibana.log

    # Plugins that are included in the build, and no longer found in the plugins/ folder
    bundled_plugin_ids:
    - plugins/dashboard/index
    - plugins/discover/index
    - plugins/doc/index
    - plugins/kibana/index
    - plugins/markdown_vis/index
    - plugins/metric_vis/index
    - plugins/settings/index
    - plugins/table_vis/index
    - plugins/vis_types/index
    - plugins/visualize/index


    6). ** portqry **
    It is showing that port 5601 is listening
    =============================================

    Starting portqry.exe -n loghost.logging.net -e 5601 -p TCP ...


    Querying target system called:

    loghost.logging.net

    Attempting to resolve name to IP address...

    Name resolved to loghost.logging.net

    querying...

    TCP port 5601 (unknown service): LISTENING
    portqry.exe -n loghost.logging.net -e 5601 -p TCP exits with return code 0x00000000.

    7). elasticsearch.yml
    ##################### Elasticsearch Configuration Example #####################

    # This file contains an overview of various configuration settings,
    # targeted at operations staff. Application developers should
    # consult the guide at <http://elasticsearch.org/guide>.
    #
    # The installation procedure is covered at
    # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html>.
    #
    # Elasticsearch comes with reasonable defaults for most settings,
    # so you can try it out without bothering with configuration.
    #
    # Most of the time, these defaults are just fine for running a production
    # cluster. If you're fine-tuning your cluster, or wondering about the
    # effect of certain configuration option, please _do ask_ on the
    # mailing list or IRC channel [http://elasticsearch.org/community].

    # Any element in the configuration can be replaced with environment variables
    # by placing them in ${...} notation. For example:
    #
    #node.rack: ${RACK_ENV_VAR}

    # For information on supported formats and syntax for the config file, see
    # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html>


    ################################### Cluster ###################################

    # Cluster name identifies your cluster for auto-discovery. If you're running
    # multiple clusters on the same network, make sure you're using unique names.
    #
    cluster.name: elasticsearch_DEV


    #################################### Node #####################################

    # Node names are generated dynamically on startup, so you're relieved
    # from configuring them manually. You can tie this node to a specific name:
    #
    node.name: "DEV_NODE"

    # Every node can be configured to allow or deny being eligible as the master,
    # and to allow or deny to store the data.
    #
    # Allow this node to be eligible as a master node (enabled by default):
    #
    #node.master: true
    #
    # Allow this node to store data (enabled by default):
    #
    #node.data: true

    # You can exploit these settings to design advanced cluster topologies.
    #
    # 1. You want this node to never become a master node, only to hold data.
    # This will be the "workhorse" of your cluster.
    #
    #node.master: false
    #node.data: true
    #
    # 2. You want this node to only serve as a master: to not store any data and
    # to have free resources. This will be the "coordinator" of your cluster.
    #
    #node.master: true
    #node.data: false
    #
    # 3. You want this node to be neither master nor data node, but
    # to act as a "search load balancer" (fetching data from nodes,
    # aggregating results, etc.)
    #
    #node.master: false
    #node.data: false

    # Use the Cluster Health API [http://localhost:9200/_cluster/health], the
    # Node Info API [http://localhost:9200/_nodes] or GUI tools
    # such as <http://www.elasticsearch.org/overview/marvel/>,
    # <http://github.com/karmi/elasticsearch-paramedic>,
    # <http://github.com/lukas-vlcek/bigdesk> and
    # <http://mobz.github.com/elasticsearch-head> to inspect the cluster state.

    # A node can have generic attributes associated with it, which can later be used
    # for customized shard allocation filtering, or allocation awareness. An attribute
    # is a simple key value pair, similar to node.key: value, here is an example:
    #
    #node.rack: rack314

    # By default, multiple nodes are allowed to start from the same installation location
    # to disable it, set the following:
    #node.max_local_storage_nodes: 1


    #################################### Index ####################################

    # You can set a number of options (such as shard/replica options, mapping
    # or analyzer definitions, translog settings, ...) for indices globally,
    # in this file.
    #
    # Note, that it makes more sense to configure index settings specifically for
    # a certain index, either when creating it or by using the index templates API.
    #
    # See <http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html> and
    # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html>
    # for more information.

    # Set the number of shards (splits) of an index (5 by default):
    #
    #index.number_of_shards: 5

    # Set the number of replicas (additional copies) of an index (1 by default):
    #
    #index.number_of_replicas: 1

    # Note, that for development on a local machine, with small indices, it usually
    # makes sense to "disable" the distributed features:
    #
    #index.number_of_shards: 1
    #index.number_of_replicas: 0

    # These settings directly affect the performance of index and search operations
    # in your cluster. Assuming you have enough machines to hold shards and
    # replicas, the rule of thumb is:
    #
    # 1. Having more *shards* enhances the _indexing_ performance and allows to
    # _distribute_ a big index across machines.
    # 2. Having more *replicas* enhances the _search_ performance and improves the
    # cluster _availability_.
    #
    # The "number_of_shards" is a one-time setting for an index.
    #
    # The "number_of_replicas" can be increased or decreased anytime,
    # by using the Index Update Settings API.
    #
    # Elasticsearch takes care about load balancing, relocating, gathering the
    # results from nodes, etc. Experiment with different settings to fine-tune
    # your setup.

    # Use the Index Status API (<http://localhost:9200/A/_status>) to inspect
    # the index status.


    #################################### Paths ####################################

    # Path to directory containing configuration (this file and logging.yml):
    #
    #path.conf: /path/to/conf

    # Path to directory where to store index data allocated for this node.
    #
    #path.data: /path/to/data
    #
    # Can optionally include more than one location, causing data to be striped across
    # the locations (a la RAID 0) on a file level, favouring locations with most free
    # space on creation. For example:
    #
    #path.data: /path/to/data1,/path/to/data2

    # Path to temporary files:
    #
    #path.work: /path/to/work

    # Path to log files:
    #
    #path.logs: /path/to/logs

    # Path to where plugins are installed:
    #
    #path.plugins: /path/to/plugins


    #################################### Plugin ###################################

    # If a plugin listed here is not installed for current node, the node will not start.
    #
    #plugin.mandatory: mapper-attachments,lang-groovy


    ################################### Memory ####################################

    # Elasticsearch performs poorly when JVM starts swapping: you should ensure that
    # it _never_ swaps.
    #
    # Set this property to true to lock the memory:
    #
    bootstrap.mlockall: true

    # Make sure that the ES_MIN_MEM and ES_MAX_MEM environment variables are set
    # to the same value, and that the machine has enough memory to allocate
    # for Elasticsearch, leaving enough memory for the operating system itself.
    #
    # You should also make sure that the Elasticsearch process is allowed to lock
    # the memory, eg. by using `ulimit -l unlimited`.


    ############################## Network And HTTP ###############################

    # Elasticsearch, by default, binds itself to the 0.0.0.0 address, and listens
    # on port [9200-9300] for HTTP traffic and on port [9300-9400] for node-to-node
    # communication. (the range means that if the port is busy, it will automatically
    # try the next port).

    # Set the bind address specifically (IPv4 or IPv6):
    #
    network.bind_host: loghost.logging.net

    # Set the address other nodes will use to communicate with this node. If not
    # set, it is automatically derived. It must point to an actual IP address.
    #
    #network.publish_host: 192.168.0.1

    # Set both 'bind_host' and 'publish_host':
    #
    #network.host: 192.168.0.1

    # Set a custom port for the node to node communication (9300 by default):
    #
    #transport.tcp.port: 9300

    # Enable compression for all communication between nodes (disabled by default):
    #
    #transport.tcp.compress: true

    # Set a custom port to listen for HTTP traffic:
    #
    #http.port: 9200

    # Set a custom allowed content length:
    #
    #http.max_content_length: 100mb

    # Disable HTTP completely:
    #
    #http.enabled: false


    ################################### Gateway ###################################

    # The gateway allows for persisting the cluster state between full cluster
    # restarts. Every change to the state (such as adding an index) will be stored
    # in the gateway, and when the cluster starts up for the first time,
    # it will read its state from the gateway.

    # There are several types of gateway implementations. For more information, see
    # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html>.

    # The default gateway type is the "local" gateway (recommended):
    #
    #gateway.type: local

    # Settings below control how and when to start the initial recovery process on
    # a full cluster restart (to reuse as much local data as possible when using shared
    # gateway).

    # Allow recovery process after N nodes in a cluster are up:
    #
    #gateway.recover_after_nodes: 1

    # Set the timeout to initiate the recovery process, once the N nodes
    # from previous setting are up (accepts time value):
    #
    #gateway.recover_after_time: 5m

    # Set how many nodes are expected in this cluster. Once these N nodes
    # are up (and recover_after_nodes is met), begin recovery process immediately
    # (without waiting for recover_after_time to expire):
    #
    #gateway.expected_nodes: 2


    ############################# Recovery Throttling #############################

    # These settings allow to control the process of shards allocation between
    # nodes during initial recovery, replica allocation, rebalancing,
    # or when adding and removing nodes.

    # Set the number of concurrent recoveries happening on a node:
    #
    # 1. During the initial recovery
    #
    #cluster.routing.allocation.node_initial_primaries_recoveries: 4
    #
    # 2. During adding/removing nodes, rebalancing, etc
    #
    #cluster.routing.allocation.node_concurrent_recoveries: 2

    # Set to throttle throughput when recovering (eg. 100mb, by default 20mb):
    #
    #indices.recovery.max_bytes_per_sec: 20mb

    # Set to limit the number of open concurrent streams when
    # recovering a shard from a peer:
    #
    #indices.recovery.concurrent_streams: 5


    ################################## Discovery ##################################

    # Discovery infrastructure ensures nodes can be found within a cluster
    # and master node is elected. Multicast discovery is the default.

    # Set to ensure a node sees N other master eligible nodes to be considered
    # operational within the cluster. This should be set to a quorum/majority of
    # the master-eligible nodes in the cluster.
    #
    #discovery.zen.minimum_master_nodes: 1

    # Set the time to wait for ping responses from other nodes when discovering.
    # Set this option to a higher value on a slow or congested network
    # to minimize discovery failures:
    #
    #discovery.zen.ping.timeout: 3s

    # For more information, see
    # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html>

    # Unicast discovery allows to explicitly control which nodes will be used
    # to discover the cluster. It can be used when multicast is not present,
    # or to restrict the cluster communication-wise.
    #
    # 1. Disable multicast discovery (enabled by default):
    #
    #discovery.zen.ping.multicast.enabled: false
    #
    # 2. Configure an initial list of master nodes in the cluster
    # to perform discovery when new nodes (master or data) are started:
    #
    #discovery.zen.ping.unicast.hosts: ["host1", "host2:port"]

    # EC2 discovery allows to use AWS EC2 API in order to perform discovery.
    #
    # You have to install the cloud-aws plugin for enabling the EC2 discovery.
    #
    # For more information, see
    # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html>
    #
    # See <http://elasticsearch.org/tutorials/elasticsearch-on-ec2/>
    # for a step-by-step tutorial.

    # GCE discovery allows to use Google Compute Engine API in order to perform discovery.
    #
    # You have to install the cloud-gce plugin for enabling the GCE discovery.
    #
    # For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-gce>.

    # Azure discovery allows to use Azure API in order to perform discovery.
    #
    # You have to install the cloud-azure plugin for enabling the Azure discovery.
    #
    # For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-azure>.

    ################################## Slow Log ##################################

    # Shard level query and fetch threshold logging.

    #index.search.slowlog.threshold.query.warn: 10s
    #index.search.slowlog.threshold.query.info: 5s
    #index.search.slowlog.threshold.query.debug: 2s
    #index.search.slowlog.threshold.query.trace: 500ms

    #index.search.slowlog.threshold.fetch.warn: 1s
    #index.search.slowlog.threshold.fetch.info: 800ms
    #index.search.slowlog.threshold.fetch.debug: 500ms
    #index.search.slowlog.threshold.fetch.trace: 200ms

    #index.indexing.slowlog.threshold.index.warn: 10s
    #index.indexing.slowlog.threshold.index.info: 5s
    #index.indexing.slowlog.threshold.index.debug: 2s
    #index.indexing.slowlog.threshold.index.trace: 500ms

    ################################## GC Logging ################################

    #monitor.jvm.gc.young.warn: 1000ms
    #monitor.jvm.gc.young.info: 700ms
    #monitor.jvm.gc.young.debug: 400ms

    #monitor.jvm.gc.old.warn: 10s
    #monitor.jvm.gc.old.info: 5s
    #monitor.jvm.gc.old.debug: 2s

    ################################## Security ################################

    # Uncomment if you want to enable JSONP as a valid return transport on the
    # http server. With this enabled, it may pose a security risk, so disabling
    # it unless you need it is recommended (it is disabled by default).
    #
    #http.jsonp.enable: true




    8). ** portqry **
    It is showing that port 9200 is listening
    =============================================

    Starting portqry.exe -n loghost.logging.net -e 9200 -p TCP ...


    Querying target system called:

    loghost.logging.net

    Attempting to resolve name to IP address...

    Name resolved to 10.101.100.38

    querying...

    TCP port 9200 (unknown service): LISTENING
    portqry.exe -n loghost.logging.net -e 9200 -p TCP exits with return code 0x00000000.
     

    Attached Files:

  17. Rick Tuck

    Rick Tuck New Member Member

    Adding another screenshot
     

    Attached Files:

  18. sbagmeijer

    sbagmeijer Machine

    It looks all fine and judging from your previous screenshots I would say Logstash did start fine.

    Silly question but is your Firewall or some kind of antivirus not blocking it?

    On the server where logstash runs try this:
    Code:
    telnet 127.0.0.1 5544
    Or perhaps you have to fix the ip but do it on the server itself.
     
  19. Rick Tuck

    Rick Tuck New Member Member

    Thanks for working through this with me.

    I found out why logstash was not listening on port 5544. When setting up the windows service using nssm, I selected logstash.bat not run.bat

    Now I see that 5544 is being listened. I an guessing that it is logstash.

    looking at the nxlog.log. Is shows that is connecting
    2015-08-16 12:35:48 INFO connecting to loghost.logging.net:5544

    I still don't know how to change kibana to return the log info from the file smps.log. It is point back to logstash-* when I do a page refresh.
     

    Attached Files:

  20. sbagmeijer

    sbagmeijer Machine


    That should be correct mind that the page you see in Kibana is the "setup" page the name "logstash-*" this is the index name that Logstash creates in Elasticsearch.

    The index "logstash-*" in return contains the information of the log file "smps.log", so unless you do advanced indexing in Elasticsearch you should the leave the Kibana setup default (as it shows in my guide).
     

Share This Page