[graylog2] Re: Web Interface - Get Login Page and Then Error
So if I understand correctly, Graylog 2.0.0 requires access to two ports from the browser whereas the older versions only required one. Is that correct? Thanks, Bill On Wednesday, May 25, 2016 at 12:35:33 AM UTC-7, Jochen Schalanda wrote: > > Hi Bill, > > starting with Graylog 2.0.0, the web interface has been merged in to the > Graylog server and has been been rewritten as a single-page application > (SPA). Thus, your browser needs access to the Graylog REST API. > > Please refer to > http://docs.graylog.org/en/2.0/pages/configuring_webif.html for > instructions how to configure Graylog and for example configurations for > using nginx or Apache httpd as reverse proxy. > > Cheers, > Jochen > > On Wednesday, 25 May 2016 00:24:24 UTC+2, bbrazell wrote: >> >> I see messages like this in the Chrome console: >> >> Unhandled rejection SuperagentPromiseError: Bad request >> at eval (webpack:///./~/superagent-bluebird-promise/index.js?:70:18) >> at Request.callback (webpack:///./~/superagent/lib/client.js?:804:3) >> at Request.crossDomainError >> (webpack:///./~/superagent/lib/client.js?:821:8) >> at XMLHttpRequest.xhr.onreadystatechange >> (webpack:///./~/superagent/lib/client.js?:884:19) >> Caused by: Error: Request has been terminated >> Possible causes: the network is offline, Origin is not allowed by >> Access-Control-Allow-Origin, the page is being unloaded, etc. >> at Request.crossDomainError >> (webpack:///./~/superagent/lib/client.js?:814:13) >> at XMLHttpRequest.xhr.onreadystatechange >> (webpack:///./~/superagent/lib/client.js?:884:19) >> >> Is it possible that with version 2.0.0 that the browser needs to be able >> to connect to the REST API directly? With earlier versions, I only need >> one port open. >> >> Thanks, >> >> Bill >> >> On Saturday, May 21, 2016 at 3:15:25 AM UTC-7, Jochen Schalanda wrote: >>> >>> Hi, >>> >>> which problem do you have specifically? Are there any error messages in >>> the Developer Console ( >>> https://developers.google.com/web/tools/chrome-devtools/debug/console/) >>> of your web browser? >>> >>> Cheers, >>> Jochen >>> >>> On Friday, 20 May 2016 23:54:52 UTC+2, bbrazell wrote: >>>> >>>> Setup: >>>> >>>> elasticsearch-2.3.2-1.noarch >>>> mongodb-linux-x86_64-rhel62-3.2.6 >>>> graylog-2.0.0 >>>> >>>> When I browse to the graylog site, I'm presented with the login dialog >>>> and splash screen. I enter the credentials and about a minute later, I >>>> get >>>> this message: >>>> >>>> We are experiencing problems connecting to the Graylog server running >>>> on*http://public_address:12900// >>>> <http://public_address:12900//>*. Please verify that the server is >>>> healthy and working correctly. >>>> >>>> The REST services are listening and available on port 12900. (curl >>>> http://127.0.0.1:12900/system/cluster/node or curl >>>> http://public_address:12900/system/cluster/node) >>>> >>>> All of the processes are running on the same server and the firewall >>>> has been disabled. I've tried using both the loopback and public >>>> addresses >>>> for the rest_listen_uri >>>> >>>> #rest_listen_uri = http://127.0.0.1:12900/ >>>> rest_listen_uri = http://public_address:12900/ >>>> >>>> Same error in either case, only that the error message shows the URL of >>>> the configured address. I've also changed the rest_transport_uri to use >>>> the public address. Made no difference. >>>> >>>> The web_listen_uri is set to http://public_address:8443/ I couldn't >>>> use 9000, but don't think that should matter. I'm able to get a response >>>> from the server on port 8443 as it serves up the login page. >>>> >>>> The logs look clean, from what I can tell. I'll post them below. >>>> >>>> I have a Graylog 1.3.4 server that's working fine. I've compared the >>>> configurations and the new server just won't work. Any help is >>>> appreciated. >>>> >>>> 2016-05-20 21:45:09,460 WARN : org.graylog2.shared.plugins.PluginLoader >>>> - Plugin directory /etc/plugin does not exist, not loading plugins. >>>> 2016-05-20 21:45:09,462 INFO : org.graylog
[graylog2] Re: Web Interface - Get Login Page and Then Error
I see messages like this in the Chrome console:
Unhandled rejection SuperagentPromiseError: Bad request
at eval (webpack:///./~/superagent-bluebird-promise/index.js?:70:18)
at Request.callback (webpack:///./~/superagent/lib/client.js?:804:3)
at Request.crossDomainError
(webpack:///./~/superagent/lib/client.js?:821:8)
at XMLHttpRequest.xhr.onreadystatechange
(webpack:///./~/superagent/lib/client.js?:884:19)
Caused by: Error: Request has been terminated
Possible causes: the network is offline, Origin is not allowed by
Access-Control-Allow-Origin, the page is being unloaded, etc.
at Request.crossDomainError
(webpack:///./~/superagent/lib/client.js?:814:13)
at XMLHttpRequest.xhr.onreadystatechange
(webpack:///./~/superagent/lib/client.js?:884:19)
Is it possible that with version 2.0.0 that the browser needs to be able to
connect to the REST API directly? With earlier versions, I only need one
port open.
Thanks,
Bill
On Saturday, May 21, 2016 at 3:15:25 AM UTC-7, Jochen Schalanda wrote:
>
> Hi,
>
> which problem do you have specifically? Are there any error messages in
> the Developer Console (
> https://developers.google.com/web/tools/chrome-devtools/debug/console/)
> of your web browser?
>
> Cheers,
> Jochen
>
> On Friday, 20 May 2016 23:54:52 UTC+2, bbrazell wrote:
>>
>> Setup:
>>
>> elasticsearch-2.3.2-1.noarch
>> mongodb-linux-x86_64-rhel62-3.2.6
>> graylog-2.0.0
>>
>> When I browse to the graylog site, I'm presented with the login dialog
>> and splash screen. I enter the credentials and about a minute later, I get
>> this message:
>>
>> We are experiencing problems connecting to the Graylog server running
>> on*http://public_address:12900//
>> <http://public_address:12900//>*. Please verify that the server is
>> healthy and working correctly.
>>
>> The REST services are listening and available on port 12900. (curl
>> http://127.0.0.1:12900/system/cluster/node or curl
>> http://public_address:12900/system/cluster/node)
>>
>> All of the processes are running on the same server and the firewall has
>> been disabled. I've tried using both the loopback and public addresses for
>> the rest_listen_uri
>>
>> #rest_listen_uri = http://127.0.0.1:12900/
>> rest_listen_uri = http://public_address:12900/
>>
>> Same error in either case, only that the error message shows the URL of
>> the configured address. I've also changed the rest_transport_uri to use
>> the public address. Made no difference.
>>
>> The web_listen_uri is set to http://public_address:8443/ I couldn't use
>> 9000, but don't think that should matter. I'm able to get a response from
>> the server on port 8443 as it serves up the login page.
>>
>> The logs look clean, from what I can tell. I'll post them below.
>>
>> I have a Graylog 1.3.4 server that's working fine. I've compared the
>> configurations and the new server just won't work. Any help is appreciated.
>>
>> 2016-05-20 21:45:09,460 WARN : org.graylog2.shared.plugins.PluginLoader -
>> Plugin directory /etc/plugin does not exist, not loading plugins.
>> 2016-05-20 21:45:09,462 INFO : org.graylog2.bootstrap.CmdLineTool -
>> Loaded plugins: []
>> 2016-05-20 21:45:09,555 INFO : org.graylog2.bootstrap.CmdLineTool -
>> Running with JVM arguments: -Djava.library.path=/etc/init.d/../lib/sigar
>> -Xms1g -Xmx1g -XX:NewRatio=1 -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC
>> -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC
>> -XX:-OmitStackTraceInFastThrow
>> 2016-05-20 21:45:10,158 INFO :
>> org.graylog2.shared.system.stats.SigarService - Failed to load SIGAR.
>> Falling back to JMX implementations.
>> 2016-05-20 21:45:11,595 INFO :
>> org.graylog2.shared.buffers.InputBufferImpl - Message journal is enabled.
>> 2016-05-20 21:45:11,765 INFO : kafka.log.LogManager - Loading logs.
>> 2016-05-20 21:45:11,871 INFO : kafka.log.LogManager - Logs loading
>> complete.
>> 2016-05-20 21:45:11,871 INFO : org.graylog2.shared.journal.KafkaJournal -
>> Initialized Kafka based journal at data/journal
>> 2016-05-20 21:45:11,890 INFO :
>> org.graylog2.shared.buffers.InputBufferImpl - Initialized InputBufferImpl
>> with ring size <65536> and wait strategy , running 2
>> parallel message handlers.
>> 2016-05-20 21:45:11,943 INFO : org.mongodb.driver.cluster - Cluster
>> created with settings {hosts=[localhost:27017], mode=SINGLE,
>> requiredClusterType=UNKNOWN, serverSelectionTimeout='3 ms',
>> maxWaitQueueSize=5000}
>> 2016-05-20 21:45:11,987 INFO : org.mongodb.drive
[graylog2] Re: Graylog 1.3.4 and 2.0.0 Web Interface Port(s)
This is inline with https://groups.google.com/forum/?hl=en#!searchin/graylog2/bbrazell/graylog2/jpGAprU_j28/Ms1mFluSCAAJ Just wanted to tie these thread together. On Monday, May 23, 2016 at 4:31:50 PM UTC-7, bbrazell wrote: > > I have a Graylog 1.3.4 instance setup in the DMZ. I'm able to access it > successfully on port 8443. Recently, I setup a Graylog 2.0.0 server and > was getting the: > > We are experiencing problems connecting to the Graylog server running on > *http://public_address:443/ > <http://public_address:443/>*. Please verify that the server is healthy > and working correctly. > > After trying what appeared to be every combination of addresses like > 0.0.0.0, 127.0.0.0.1, localhost, and the public address, I was only able to > get it working when I bound the REST service to a port that the browser > could access directly. Is this a new requirement of version 2.0.0 or is > there a way to make it work like it does in 1.3.4? > > Thanks, > > Bill > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/9ad875d2-51e0-4e5d-8ea8-4782f05ff80e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Web Interface - Get Login Page and Then Error
Here is some more info:
server.conf
node_id_file = /etc/graylog/server/node-id
password_secret = XXX
root_password_sha2 = XXX
plugin_dir = plugin
rest_listen_uri = http://public_address:12900/
rest_transport_uri = http://public_address:12900/
web_listen_uri = http://public_address:8443/
elasticsearch_shards = 4
elasticsearch_replicas = 0
elasticsearch_index_prefix = graylog
allow_leading_wildcard_searches = false
allow_highlighting = false
elasticsearch_cluster_name = graylog2
elasticsearch_analyzer = standard
output_batch_size = 500
output_flush_interval = 1
output_fault_count_threshold = 5
output_fault_penalty_seconds = 30
processbuffer_processors = 5
outputbuffer_processors = 3
processor_wait_strategy = blocking
ring_size = 65536
inputbuffer_ring_size = 65536
inputbuffer_processors = 2
inputbuffer_wait_strategy = blocking
message_journal_enabled = true
message_journal_dir = data/journal
lb_recognition_period_seconds = 3
mongodb_uri = mongodb://localhost/graylog
mongodb_max_connections = 1000
mongodb_threads_allowed_to_block_multiplier = 5
content_packs_auto_load = grok-patterns.json
elasticsearch.yml
cluster.name: graylog2
network.host: 127.0.0.1
elasticsearch_discovery_zen_ping_multicast_enabled : false
discovery.zen.ping.unicast.hosts: ["127.0.0.1"]
Output from curl http://localhost:9200
{
"name" : "Hero",
"cluster_name" : "graylog2",
"version" : {
"number" : "2.3.2",
"build_hash" : "b9e4a6acad4008027e4038f6abed7f7dba346f94",
"build_timestamp" : "2016-04-21T16:03:47Z",
"build_snapshot" : false,
"lucene_version" : "5.5.0"
},
"tagline" : "You Know, for Search"
}
Output from http://public_address:12900/system/cluster/node:
{"cluster_id":"86fae1a8-10bf-4026-ab90-936f3b866da7","node_id":"2b606ffe-98a8-41b7-8117-6b4e9c354f08","type":"server","transport_address":"http://public_address:12900/","last_seen":"2016-05-20T22:15:02.000Z","short_node_id":"2b606ffe","hostname":"localhost.localdomain","is_master":true}[r...@hostname.com
2016-05-20--22-15-03 server #]
On Friday, May 20, 2016 at 2:54:52 PM UTC-7, bbrazell wrote:
>
> Setup:
>
> elasticsearch-2.3.2-1.noarch
> mongodb-linux-x86_64-rhel62-3.2.6
> graylog-2.0.0
>
> When I browse to the graylog site, I'm presented with the login dialog and
> splash screen. I enter the credentials and about a minute later, I get
> this message:
>
> We are experiencing problems connecting to the Graylog server running
> on*http://public_address:12900//
> <http://public_address:12900//>*. Please verify that the server is
> healthy and working correctly.
>
> The REST services are listening and available on port 12900. (curl
> http://127.0.0.1:12900/system/cluster/node or curl
> http://public_address:12900/system/cluster/node)
>
> All of the processes are running on the same server and the firewall has
> been disabled. I've tried using both the loopback and public addresses for
> the rest_listen_uri
>
> #rest_listen_uri = http://127.0.0.1:12900/
> rest_listen_uri = http://public_address:12900/
>
> Same error in either case, only that the error message shows the URL of
> the configured address. I've also changed the rest_transport_uri to use
> the public address. Made no difference.
>
> The web_listen_uri is set to http://public_address:8443/ I couldn't use
> 9000, but don't think that should matter. I'm able to get a response from
> the server on port 8443 as it serves up the login page.
>
> The logs look clean, from what I can tell. I'll post them below.
>
> I have a Graylog 1.3.4 server that's working fine. I've compared the
> configurations and the new server just won't work. Any help is appreciated.
>
> 2016-05-20 21:45:09,460 WARN : org.graylog2.shared.plugins.PluginLoader -
> Plugin directory /etc/plugin does not exist, not loading plugins.
> 2016-05-20 21:45:09,462 INFO : org.graylog2.bootstrap.CmdLineTool - Loaded
> plugins: []
> 2016-05-20 21:45:09,555 INFO : org.graylog2.bootstrap.CmdLineTool -
> Running with JVM arguments: -Djava.library.path=/etc/init.d/../lib/sigar
> -Xms1g -Xmx1g -XX:NewRatio=1 -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC
> -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC
> -XX:-OmitStackTraceInFastThrow
> 2016-05-20 21:45:10,158 INFO :
> org.graylog2.shared.system.stats.SigarService - Failed to load SIGAR.
> Falling back to JMX implementations.
> 2016-05-20 21:45:11,595 INFO : org.graylog2.shared.buffers.InputBufferImpl
> - Message journal is enabled.
> 2016-05-2
[graylog2] Web Interface - Get Login Page and Then Error
Setup:
elasticsearch-2.3.2-1.noarch
mongodb-linux-x86_64-rhel62-3.2.6
graylog-2.0.0
When I browse to the graylog site, I'm presented with the login dialog and
splash screen. I enter the credentials and about a minute later, I get
this message:
We are experiencing problems connecting to the Graylog server running on
*http://public_address:12900//*. Please verify that the server is healthy
and working correctly.
The REST services are listening and available on port 12900. (curl
http://127.0.0.1:12900/system/cluster/node or curl
http://public_address:12900/system/cluster/node)
All of the processes are running on the same server and the firewall has
been disabled. I've tried using both the loopback and public addresses for
the rest_listen_uri
#rest_listen_uri = http://127.0.0.1:12900/
rest_listen_uri = http://public_address:12900/
Same error in either case, only that the error message shows the URL of the
configured address. I've also changed the rest_transport_uri to use the
public address. Made no difference.
The web_listen_uri is set to http://public_address:8443/ I couldn't use
9000, but don't think that should matter. I'm able to get a response from
the server on port 8443 as it serves up the login page.
The logs look clean, from what I can tell. I'll post them below.
I have a Graylog 1.3.4 server that's working fine. I've compared the
configurations and the new server just won't work. Any help is appreciated.
2016-05-20 21:45:09,460 WARN : org.graylog2.shared.plugins.PluginLoader -
Plugin directory /etc/plugin does not exist, not loading plugins.
2016-05-20 21:45:09,462 INFO : org.graylog2.bootstrap.CmdLineTool - Loaded
plugins: []
2016-05-20 21:45:09,555 INFO : org.graylog2.bootstrap.CmdLineTool - Running
with JVM arguments: -Djava.library.path=/etc/init.d/../lib/sigar -Xms1g
-Xmx1g -XX:NewRatio=1 -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC
-XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC
-XX:-OmitStackTraceInFastThrow
2016-05-20 21:45:10,158 INFO :
org.graylog2.shared.system.stats.SigarService - Failed to load SIGAR.
Falling back to JMX implementations.
2016-05-20 21:45:11,595 INFO : org.graylog2.shared.buffers.InputBufferImpl
- Message journal is enabled.
2016-05-20 21:45:11,765 INFO : kafka.log.LogManager - Loading logs.
2016-05-20 21:45:11,871 INFO : kafka.log.LogManager - Logs loading complete.
2016-05-20 21:45:11,871 INFO : org.graylog2.shared.journal.KafkaJournal -
Initialized Kafka based journal at data/journal
2016-05-20 21:45:11,890 INFO : org.graylog2.shared.buffers.InputBufferImpl
- Initialized InputBufferImpl with ring size <65536> and wait strategy
, running 2 parallel message handlers.
2016-05-20 21:45:11,943 INFO : org.mongodb.driver.cluster - Cluster created
with settings {hosts=[localhost:27017], mode=SINGLE,
requiredClusterType=UNKNOWN, serverSelectionTimeout='3 ms',
maxWaitQueueSize=5000}
2016-05-20 21:45:11,987 INFO : org.mongodb.driver.cluster - No server
chosen by ReadPreferenceServerSelector{readPreference=primary} from cluster
description ClusterDescription{type=UNKNOWN, connectionMode=SINGLE,
all=[ServerDescription{address=localhost:27017, type=UNKNOWN,
state=CONNECTING}]}. Waiting for 3 ms before timing out
2016-05-20 21:45:12,044 INFO : org.mongodb.driver.connection - Opened
connection [connectionId{localValue:1, serverValue:163}] to localhost:27017
2016-05-20 21:45:12,048 INFO : org.mongodb.driver.cluster - Monitor thread
successfully connected to server with description
ServerDescription{address=localhost:27017, type=STANDALONE,
state=CONNECTED, ok=true, version=ServerVersion{versionList=[3, 2, 6]},
minWireVersion=0, maxWireVersion=4, maxDocumentSize=16777216,
roundTripTimeNanos=2684296}
2016-05-20 21:45:12,061 INFO : org.mongodb.driver.connection - Opened
connection [connectionId{localValue:2, serverValue:164}] to localhost:27017
2016-05-20 21:45:12,263 INFO : org.graylog2.plugin.system.NodeId - Node ID:
2b606ffe-98a8-41b7-8117-6b4e9c354f08
2016-05-20 21:45:12,336 INFO : org.elasticsearch.node -
[graylog-2b606ffe-98a8-41b7-8117-6b4e9c354f08] version[2.3.1], pid[19838],
build[bd98092/2016-04-04T12:25:05Z]
2016-05-20 21:45:12,336 INFO : org.elasticsearch.node -
[graylog-2b606ffe-98a8-41b7-8117-6b4e9c354f08] initializing ...
2016-05-20 21:45:12,342 INFO : org.elasticsearch.plugins -
[graylog-2b606ffe-98a8-41b7-8117-6b4e9c354f08] modules [], plugins
[graylog-monitor], sites []
2016-05-20 21:45:14,062 INFO : org.elasticsearch.node -
[graylog-2b606ffe-98a8-41b7-8117-6b4e9c354f08] initialized
2016-05-20 21:45:14,144 INFO :
org.hibernate.validator.internal.util.Version - HV01: Hibernate
Validator 5.2.4.Final
2016-05-20 21:45:14,289 INFO : org.graylog2.shared.buffers.ProcessBuffer -
Initialized ProcessBuffer with ring size <65536> and wait strategy
.
2016-05-20 21:45:16,262 INFO :
org.graylog2.bindings.providers.RulesEngineProvider - No static rules file
loaded.
2016-05-20
[graylog2] Graylog Web - Unable to Add Nodes
I just setup my first Graylog server. After getting the config files right
(or what I think is right) I'm able to log into the web interface. The
problem is that when I select System/Nodes -> Nodes, I get this error:
(You caused a org.graylog2.restclient.lib.APIException. API call failed GET
http://@127.0.0.1:12900/system/radios returned 404 Not Found body:
{"type":"ApiError","message":"HTTP 404 Not Found"})
I am starting the Graylog web interface on port 8443. All other ports are
default. I verified that the Graylog REST API is responding by issuing
this command:
curl -v -u admin:password http://localhost:12900/users
It knows how to find the /users directory. It also finds the /system
directory. Get a 404 when it tries to load /system/radios every time.
Does anyone know what's wrong and how to get it working? I've Googled the
problem to death.
Thanks!
Bill
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/graylog2/9c448782-102f-46ed-81c6-24b7ba2fab01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
