[graylog2] Re: graylog 1.2.2 ldap not saving settings

[Mike Daoust]

graylog-web/application.2016-03-04.log:org.graylog2.restclient.lib.APIException:
 
API call failed GET 
http://@loggingglsrv02.apps.appriver.corp:12900/system/ldap/settings 
returned 404 Not Found body: {"type":"ApiError","message":"HTTP 404 
 Not Found"}




On Friday, March 4, 2016 at 11:58:02 PM UTC-6, Mike Daoust wrote:
>
> where do the ldap settings get saved?
>
> On Friday, March 4, 2016 at 6:02:05 PM UTC-6, Mike Daoust wrote:
>>
>> graylog 1.2.2 ldap not saving settings, any ideas?
>>
>

-- 
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/882a2544-2a36-4b9b-8ab0-f221b8e5c85f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: graylog 1.2.2 ldap not saving settings

[Mike Daoust]

where do the ldap settings get saved?

On Friday, March 4, 2016 at 6:02:05 PM UTC-6, Mike Daoust wrote:
>
> graylog 1.2.2 ldap not saving settings, any ideas?
>

-- 
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/18aa8393-e562-4f07-8f03-91d045af9be3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] [ANNOUNCE] Graylog v2.0-alpha.5 has been released

[Lennart Koopmann]

Hi everyone,

I am happy to announce that we have just released alpha.5 of Graylog
v2.0 and it includes especially exciting new features.

You can find the announcement blog post here:
https://www.graylog.org/blog/48-fifth-alpha-of-graylog-v2-0-released-with-message-processor-pipeline-and-collector-sidecar

Thanks,
Lennart

-- 
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/CADRA1nnWVdjH%3D4ehRC23DjPzf6RMKoGV1hVAOJSrQcfJ2XMhDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] graylog 1.2.2 ldap not saving settings

[Mike Daoust]

graylog 1.2.2 ldap not saving settings, any ideas?

-- 
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/ea8b3a0b-8f08-4a08-9031-a25d9910cad4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Graylog server is using lots of RAM

[Peter Loron]

We have a single machine install of Graylog (1.3.2). It is a VM running in 
our VMware cluster and is built on Ubuntu 14.04. The vm has 4 cores and 
16GB of ram. We get 2-5 messages per second. There are 5 inputs running, a 
couple of streams with simple rules, and the services (mongo, elastic) are 
running with default settings.

Over the span of 20 days, the graylog and elastic processes take up all of 
the available RAM and start consuming some swap.

This feels like a leak to me.

Any input/pointers?

Thanks.

-Pete

-- 
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/b84b6f99-185b-4443-9ecd-9be41101a446%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Graylog 2.0.0 Alpha - connection error from web-gui

[Jayica]

After displaying the login page, it than fails with this:
We are experiencing problems connecting to the Graylog server running on 
*http://127.0.0.1:12900//*. Please verify that the server is healthy and 
working correctly.


Graylog service is up and running though (on AWS instance - Ubuntu 14.04).
2016-03-04 21:27:01,688 INFO : org.graylog2.bootstrap.ServerBootstrap - 
Graylog server up and running.


Here's what i currently have set in /etc/graylog/server/server.conf

is_master = true
node_id_file = /etc/graylog/server/node-id
password_secret = xx
root_username = admin
root_password_sha2 = xxx
plugin_dir = plugin

rest_listen_uri = http://127.0.0.1:12900/
rest_transport_uri = http://127.0.0.1:12900/
web_listen_uri = http://0.0.0.0:9000/

elasticsearch_config_file = /etc/elasticsearch/elasticsearch.yml
rotation_strategy = count
elasticsearch_max_docs_per_index = 2000
elasticsearch_max_number_of_indices = 20
retention_strategy = delete
elasticsearch_shards = 4
elasticsearch_replicas = 0
elasticsearch_index_prefix = graylog
allow_leading_wildcard_searches = false
allow_highlighting = false
elasticsearch_cluster_name = graylog2
elasticsearch_discovery_zen_ping_multicast_enabled = false
elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300
elasticsearch_cluster_discovery_timeout = 1
elasticsearch_analyzer = standard


Per JS console in Chrome:

http://127.0.0.1:12900/system/cluster/node Failed to load resource: 
net::ERR_CONNECTION_REFUSED

client.js:1026 GET http://127.0.0.1:12900/system/cluster/node 
net::ERR_CONNECTION_REFUSEDRequest.end @ client.js:1026(anonymous function) 
@ index.js:61tryCatcher @ bluebird.js:4589Promise._resolveFromResolver @ 
bluebird.js:2668Promise @ bluebird.js:2258Request.promise @ 
index.js:60Request.then @ index.js:95ping @ ServerAvailabilityStore.js:39


appConfig.gl2ServerUrl

"http://127.0.0.1:12900/";


I've opened these ports through the firewall.


Specs:

   - Graylog Version: graylog-2.0.0-alpha
   - Elasticsearch Version: elasticsearch-2.2.0
   - MongoDB Version: mongodb-org-3.2
   - Operating System: ubuntu-trusty-14.04-amd64 AWS instance (single node)

-- 
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/f15a3933-d0a9-4248-974b-cd9b04401165%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [graylog2] Re: Setting graylog2's heap size.

[nd]

I would also like to know if this affects the WebUI, beacause i have taken 
several measures to set ES_HEAP_SIZE, ES_MIN_MEM, ES_MAX_MEM and do NOT see 
a change in the WebUI.  I'm beginning to think, the WebUI is solely for the 
graylog services, not ElasticSearch.

On Thursday, November 19, 2015 at 3:47:51 PM UTC-6, Matthew Simon wrote:
>
> HI 
>
> Does this fix update the web interface.
>
> Or does it remain to state bellow.
>
> The JVM is using * 159.3 MB of  972.8 MB* heap space and will not attempt 
> to use more than * 1.4 GB*
>
>
> On Thursday, June 20, 2013 at 12:15:20 AM UTC+2, lennart wrote:
>>
>> Increasing the graylog2-server heap size can be necessary especially 
>> in high volume setups. The way you solved it is the currently 
>> officially recommended way! :) 
>>
>> Cheers, 
>> Lennart 
>>
>>
>> On Wed, Jun 19, 2013 at 5:20 PM, Alex B.  wrote: 
>> > I don't know then ... i thought you were running a standalone server 
>> > (Graylog2 + ES), like i do. I had out of memory errors too and resolved 
>> it 
>> > increasing ES (not the graylog2 one) heap size. 
>> > 
>> > Le mardi 18 juin 2013 19:28:27 UTC+2, Christian Hedegaard a écrit : 
>> >> 
>> >> Since Graylog is using the embedded ES client, how would that work? We 
>> >> have a pretty big 5-node ES cluster running on AWS m1.xl’s and do not 
>> run 
>> >> ANY ES on the graylog server itself, except for the embedded one which 
>> we 
>> >> have no choice over. 
>> >> 
>> >> 
>> >> 
>> >> We’re using 12RC of Graylog2 
>> >> 
>> >> 
>> >> 
>> >> From: Alex B. [mailto:alexandr...@gmail.com] 
>> >> 
>> >> Sent: Tuesday, June 18, 2013 4:34 AM 
>> >> To: gray...@googlegroups.com 
>> >> 
>> >> Cc: Christian Hedegaard 
>> >> Subject: Re: Setting graylog2's heap size. 
>> >> 
>> >> 
>> >> 
>> >> I think your memory errors were generated by ES, not graylog2, there's 
>> >> nothing to change in graylog2 script. Tune ES heap size instead. 
>> >> 
>> >> Le lundi 17 juin 2013 20:52:32 UTC+2, Christian Hedegaard a écrit : 
>> >> 
>> >> Is there a “correct” way to set the heap size for graylog2? I just 
>> >> manually edited the graylog2ctl script like so: 
>> >> 
>> >> 
>> >> 
>> >> HEAP_SIZE='-Xms8192M -Xmx8192M' 
>> >> 
>> >> 
>> >> 
>> >> start() { 
>> >> 
>> >> echo "Starting graylog2-server ..." 
>> >> 
>> >> cd "$GRAYLOG2CTL_DIR/.." 
>> >> 
>> >> $NOHUP java ${HEAP_SIZE} -jar ${GRAYLOG2_SERVER_JAR} -f 
>> >> ${GRAYLOG2_CONF} -p ${GRAYLOG2_PID} >> ${LOG_FILE} & 
>> >> 
>> >> } 
>> >> 
>> >> 
>> >> 
>> >> But I wanted to make sure there wasn’t a more “official” way to do it 
>> like 
>> >> it picking up some environment variables or other process. 
>> >> 
>> >> 
>> >> 
>> >> We had our log server process hard lock over the weekend and it 
>> appears 
>> >> that the default heap settings were too low. There were thousands and 
>> >> thousands of “out of heap memory” errors in the log and then it just 
>> stopped 
>> >> processing and had to be kill -9’ed. 
>> >> 
>> >> 
>> >> 
>> >> Before the setting above, our Log server was flatlined at 5G memory 
>> usage. 
>> >> 90% of that was graylog. Now it’s at 9.5G or so. I just hope this is 
>> enough. 
>> >> We’re currently getting about 1100 messages/sec and that number will 
>> >> increase in the future. 
>> > 
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> Groups 
>> > "graylog2" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> an 
>> > email to graylog2+u...@googlegroups.com. 
>> > For more options, visit https://groups.google.com/groups/opt_out. 
>> > 
>> > 
>>
>

-- 
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/2cf10bf8-b4ce-4717-b67c-656dc78014a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Upgrading to 1.3.3

[Francois Franck]

Hi Jochen,

Thanks a lot for your reply but many points are unclear to me at this time.

1. The web interface shows "*graylog-web-interface v1.1.5*" and I actually 
remember having downloaded and upgraded (both server and web interface) to 
1.1.5 some months ago !!! That's odd...
Is there a command to display the graloy version number ?

2. The system overview displays this message: "*The most recent stable 
Graylog version is 1.2.0 (Augustiner) released at 2015-09-15*". Does it 
mean I'm not supposed to install the 1.3.3 version ? Or shall I first 
upgrade to 1.2.0 ?

3. If I uninstall as suggested, will I lose all my settings and data ? 
Needless to say I prefer not...

ThanX again.

Francois





-- 
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/54c4720a-6633-4a5d-837d-0f6ccf3fb0e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Having trouble installing/starting graylog-server

[Jochen Schalanda]

Hi Clayton,

at a first glance the permissions seem to be correct. Make sure that the 
user "graylog" is really the one being used to start Graylog on your system 
(you can check the Upstart script and /etc/default/graylog-server).

Also try deleting the empty /var/log/graylog-server/server.log file and 
restart the graylog-server service.


Cheers,
Jochen

On Thursday, 3 March 2016 20:00:42 UTC+1, Clayton Tavernier wrote:
>
> I'm using this guide: 
> https://www.digitalocean.com/community/tutorials/how-to-install-graylog-1-x-on-ubuntu-14-04
>
> Everything seems to install fine but my graylog-server is constantly 
> restarting.
>
> * Mar  3 10:27:25 logs kernel: [267313.798284] init: graylog-server 
> main process (23744) terminated with status 1*
> * Mar  3 10:27:25 logs kernel: [267313.798302] init: graylog-server 
> main process ended, respawning*
> * Mar  3 10:27:26 logs kernel: [267314.433766] init: graylog-server 
> main process (23758) terminated with status 1*
> * Mar  3 10:27:26 logs kernel: [267314.433775] init: graylog-server 
> main process ended, respawning*
>
> So I look in */var/log/graylog-server/server.log* and it's empty.
>
> Then I look in */var/log/upstart/graylog-server.log *and I find:
>
> * java.io.FileNotFoundException: /var/log/graylog-server/server.log 
> (Permission denied)*
>
> And I look:
>
> *$ sudo ls -la /var/log/graylog-server*
> *total 8*
> *drwxr-xr-x  2 graylog graylog 4096 Dec  9 11:06 .*
> *drwxrwxr-x 18 syslog  syslog  4096 Mar  3 07:07 ..*
> *-rw-r--r--  1 graylog graylog0 Dec  9 11:06 server.log*
>
> which seems right to me but I guess it's not?
>
> Any help would be appreciated.
>
>

-- 
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/b97e6ec5-1849-4246-896f-2ae3c9ede957%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Upgrading to 1.3.3

[Jochen Schalanda]

Hi Francois,

according to the output you've posted, you've upgraded from Graylog 1.0.0 
to 1.3.3. If I remember correctly, there have been some serious bug fixes 
in between those versions regarding the Omnibus packaging.

Did you simply restart the virtual machine after upgrading Graylog? Maybe 
some {pre,post}-{install,uninstall}-script has been broken? Try 
reinstalling the Graylog package (first uninstall the old one with apt-get 
uninstall graylog, then install the new one with dpkg -i graylog_latest.deb
).


Cheers,
Jochen

On Friday, 4 March 2016 13:54:01 UTC+1, Francois Franck wrote:
>
> Hi all,
>
> I am currently running an OVA version 1.1.5 and was in the process to 
> upgrade to version 1.3.3. Seems things are not as simple as the 
> documentation says.
>
> wget 
> https://packages.graylog2.org/releases/graylog2-omnibus/ubuntu/graylog_latest.deb
> sudo graylog-ctl stop
> sudo dpkg -G -i graylog_latest.deb
> sudo graylog-ctl reconfigure
>
>
> This is my output:
>
> ubuntu@rhlog:/tmp$ *sudo graylog-ctl stop*
>> ok: down: elasticsearch: 0s, normally up
>> ok: down: etcd: 1s, normally up
>> ok: down: graylog-server: 0s, normally up
>> ok: down: graylog-web: 0s, normally up
>> ok: down: mongodb: 0s, normally up
>> ok: down: nginx: 1s, normally up
>>
>  
>
>> ubuntu@rhlog:/tmp$ *sudo dpkg -G -i graylog_latest.deb*
>> (Reading database ... 70379 files and directories currently installed.)
>> Preparing to unpack graylog_latest.deb ...
>> You're about to install Graylog!
>> Unpacking graylog (1.3.3-1) over (1.0.0-1) ...
>> Graylog has been uninstalled!
>> Setting up graylog (1.3.3-1) ...
>> By installing this package, you accept the terms of the Oracle Binary 
>> Code License Agreement for the Java SE Platform Products and JavaFX, which 
>> can be found at 
>> http://www.oracle.com/technetwork/java/javase/terms/license/index.html
>>
>> Thank you for installing Graylog!
>> The next step in the install process is to run: sudo graylog-ctl 
>> reconfigure 
>
> ubuntu@rhlog:/tmp$ *sudo graylog-ctl reconfigure*
>> sudo: graylog-ctl: *command not found*
>> ubuntu@rhlog:/tmp$
>>
>
> I surely miss something but where ?
> Never been so happy to rollback from a previous snapshot :-)
>
> Thanks.
>

-- 
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/533b4d35-441a-4b12-9a5d-a234f83d5b80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Upgrading to 1.3.3

[Francois Franck]

Hi all,

I am currently running an OVA version 1.1.5 and was in the process to 
upgrade to version 1.3.3. Seems things are not as simple as the 
documentation says.

wget 
https://packages.graylog2.org/releases/graylog2-omnibus/ubuntu/graylog_latest.deb
sudo graylog-ctl stop
sudo dpkg -G -i graylog_latest.deb
sudo graylog-ctl reconfigure


This is my output:

ubuntu@rhlog:/tmp$ *sudo graylog-ctl stop*
> ok: down: elasticsearch: 0s, normally up
> ok: down: etcd: 1s, normally up
> ok: down: graylog-server: 0s, normally up
> ok: down: graylog-web: 0s, normally up
> ok: down: mongodb: 0s, normally up
> ok: down: nginx: 1s, normally up
>
 

> ubuntu@rhlog:/tmp$ *sudo dpkg -G -i graylog_latest.deb*
> (Reading database ... 70379 files and directories currently installed.)
> Preparing to unpack graylog_latest.deb ...
> You're about to install Graylog!
> Unpacking graylog (1.3.3-1) over (1.0.0-1) ...
> Graylog has been uninstalled!
> Setting up graylog (1.3.3-1) ...
> By installing this package, you accept the terms of the Oracle Binary Code 
> License Agreement for the Java SE Platform Products and JavaFX, which can 
> be found at 
> http://www.oracle.com/technetwork/java/javase/terms/license/index.html
>
> Thank you for installing Graylog!
> The next step in the install process is to run: sudo graylog-ctl 
> reconfigure 

ubuntu@rhlog:/tmp$ *sudo graylog-ctl reconfigure*
> sudo: graylog-ctl: *command not found*
> ubuntu@rhlog:/tmp$
>

I surely miss something but where ?
Never been so happy to rollback from a previous snapshot :-)

Thanks.

-- 
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/f825962a-b34f-4a0c-920d-c3a8cb985846%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [graylog2] Re: RC1: Invalid credentials authentication exception

[Sagar Nikam]

Hi Jochen,


Thanks your trick just works !!!   :)
I remove the trailing "  -" in the line with root_password_sha2...& it
works fine.


Thanks a lot !
Happy logging !!!


On Fri, Mar 4, 2016 at 3:21 PM, Jochen Schalanda  wrote:

> Hi Sagar,
>
> you'll have to remove the trailing "  -" in the line with
> root_password_sha2 so that only the hash is in that line, i. e.:
>
> root_password_sha2 =
> 8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918
>
>
> Cheers,
> Jochen
>
>
> On Friday, 4 March 2016 07:27:46 UTC+1, Sagar Nikam wrote:
>>
>> Hi Jochen,
>>
>> I tried to make the same password in following files password_secret (in
>> /etc/graylog/server/server.conf) & application.secret (in
>> /etc/graylog/web/web.conf).
>>
>>- *root_password_sha2* is generated using echo -n admin | shasum -a
>>256
>>
>> please find two file configurations.
>>
>>- */etc/graylog/server/server.conf*
>>
>> # If you are running more than one instances of graylog2-server you have to 
>> select one of these
>> # instances as master. The master will perform some periodical tasks that 
>> non-masters won't perform.
>> is_master = true
>>
>> # The auto-generated node ID will be stored in this file and read after 
>> restarts. It is a good idea
>> # to use an absolute file path here if you are starting graylog2-server from 
>> init scripts or similar.
>> node_id_file = /etc/graylog/server/node-id
>>
>> # You MUST set a secret to secure/pepper the stored user passwords here. Use 
>> at least 64 characters.
>> # Generate one by using for example: pwgen -N 1 -s 96
>> password_secret=X2oHR7K6a30wcNUEjeP3TgO1pPs8LKxfecZHe4k0fjUqv9vNI3TWsg659nSUdh6XKqvMuO9NSYU2yEIriFqjf4uXU0c4EwVR
>>
>> # The default root user is named 'admin'
>> root_username = admin
>>
>> # You MUST specify a hash password for the root user (which you only need to 
>> initially set up the
>> # system and in case you lose connectivity to your authentication backend)
>> # This password cannot be changed using the API or via the web interface. If 
>> you need to change it,
>> # modify it in this file.
>> # Create one by using for example: echo -n yourpassword | shasum -a 256
>> # and put the resulting hash value into the following line
>> root_password_sha2 
>> =8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918  -
>>
>> # The email address of the root user.
>> # Default is empty
>> #root_email = ""
>>
>>
>>- */etc/graylog/web/web.conf*
>>
>> # graylog2-server REST URIs (one or more, comma separated) For example: 
>> "http://127.0.0.1:12900/,http://127.0.0.1:12910/";
>> graylog2-server.uris="http://127.0.0.1:12900/";
>>
>> # Learn how to configure custom logging in the documentation:
>> #
>> http://docs.graylog.org/en/latest/pages/installation.html#manual-setup-graylog-web-interface-on-linux
>>
>> # Secret key
>> # ~
>> # The secret key is used to secure cryptographics functions. Set this to a 
>> long and randomly generated string.
>> # If you deploy your application to several instances be sure to use the 
>> same key!
>> # Generate for example with: pwgen -N 1 -s 96
>> application.secret="HR7K6a30wcNUEjeP3TgO1pPs8LKxfecZHe4k0fjUqv9vNI3TWsg659nSUdh6XKqvMuO9NSYU2yEIriFqjf4uXU0c4EwVR"
>>
>> # Web interface timezone
>> # Graylog stores all timestamps in UTC. To properly display times, set the 
>> default timezone of the interface.
>> # If you leave this out, Graylog will pick your system default as the 
>> timezone. Usually you will want to configure it explicitly.
>> # timezone="Europe/Berlin"
>>
>> --
>>
>> *The problem still continues…*
>> is there any setting I have to change, something in elasticsearch or
>> mongodb ?
>>
>> Thanks in advance !!!
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Graylog Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/graylog2/IJ8-YckGH04/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> graylog2+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/graylog2/535a55a7-16a5-4ef2-8e3a-ba67cc0f5f8f%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAEbE3x67fNhyQ6d%3DNaYcxJncORXZ0oQW%2B%3DZKrH1ypSH1MzRVcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [graylog2] Re: RC1: Invalid credentials authentication exception

[Jochen Schalanda]

Hi Sagar,

you'll have to remove the trailing "  -" in the line with root_password_sha2 
so that only the hash is in that line, i. e.:

root_password_sha2 = 
8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918


Cheers,
Jochen

On Friday, 4 March 2016 07:27:46 UTC+1, Sagar Nikam wrote:
>
> Hi Jochen,
>
> I tried to make the same password in following files password_secret (in 
> /etc/graylog/server/server.conf) & application.secret (in 
> /etc/graylog/web/web.conf).
>
>- *root_password_sha2* is generated using echo -n admin | shasum -a 256 
>
> please find two file configurations.
>
>- */etc/graylog/server/server.conf* 
>
> # If you are running more than one instances of graylog2-server you have to 
> select one of these
> # instances as master. The master will perform some periodical tasks that 
> non-masters won't perform.
> is_master = true
>
> # The auto-generated node ID will be stored in this file and read after 
> restarts. It is a good idea
> # to use an absolute file path here if you are starting graylog2-server from 
> init scripts or similar.
> node_id_file = /etc/graylog/server/node-id
>
> # You MUST set a secret to secure/pepper the stored user passwords here. Use 
> at least 64 characters.
> # Generate one by using for example: pwgen -N 1 -s 96
> password_secret=X2oHR7K6a30wcNUEjeP3TgO1pPs8LKxfecZHe4k0fjUqv9vNI3TWsg659nSUdh6XKqvMuO9NSYU2yEIriFqjf4uXU0c4EwVR
>
> # The default root user is named 'admin'
> root_username = admin
>
> # You MUST specify a hash password for the root user (which you only need to 
> initially set up the
> # system and in case you lose connectivity to your authentication backend)
> # This password cannot be changed using the API or via the web interface. If 
> you need to change it,
> # modify it in this file.
> # Create one by using for example: echo -n yourpassword | shasum -a 256
> # and put the resulting hash value into the following line
> root_password_sha2 
> =8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918  -
>
> # The email address of the root user.
> # Default is empty
> #root_email = ""
>
>
>- */etc/graylog/web/web.conf* 
>
> # graylog2-server REST URIs (one or more, comma separated) For example: 
> "http://127.0.0.1:12900/,http://127.0.0.1:12910/";
> graylog2-server.uris="http://127.0.0.1:12900/";
>
> # Learn how to configure custom logging in the documentation:
> #
> http://docs.graylog.org/en/latest/pages/installation.html#manual-setup-graylog-web-interface-on-linux
>
> # Secret key
> # ~
> # The secret key is used to secure cryptographics functions. Set this to a 
> long and randomly generated string.
> # If you deploy your application to several instances be sure to use the same 
> key!
> # Generate for example with: pwgen -N 1 -s 96
> application.secret="HR7K6a30wcNUEjeP3TgO1pPs8LKxfecZHe4k0fjUqv9vNI3TWsg659nSUdh6XKqvMuO9NSYU2yEIriFqjf4uXU0c4EwVR"
>
> # Web interface timezone
> # Graylog stores all timestamps in UTC. To properly display times, set the 
> default timezone of the interface.
> # If you leave this out, Graylog will pick your system default as the 
> timezone. Usually you will want to configure it explicitly.
> # timezone="Europe/Berlin"
>
> --
>
> *The problem still continues…*
> is there any setting I have to change, something in elasticsearch or 
> mongodb ?
>
> Thanks in advance !!!
>

-- 
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/535a55a7-16a5-4ef2-8e3a-ba67cc0f5f8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [graylog2] Graylog installation

[Marius Sturm]

Hi,
you can download a prepared VM with everything configured. Just start it in
Virtualbox and try Graylog out:
http://docs.graylog.org/en/1.3/pages/installation/virtual_machine_appliances.html

Cheers,
Marius


On 4 March 2016 at 09:58,  wrote:

> Hi,
>
> Can we install graylog on windows? I am getting may errors when I try to
> start the graylog collector.
>
> I tried to install graylog on Redhat Vm, sounds like the service is not
> getting started because of space issue. Can anyone tell me how to avoid
> this ?
>
> Is there any way I could play with open source webservice graylog?  Please
> do let me in installing graylog. I want to see how it works.
>
>
>
> Thank you
>
> --
> 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/39e8d454-7c64-40c8-a689-8bf3d5719f74%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Developer

Tel.: +49 (0)40 609 452 077
Fax.: +49 (0)40 609 452 078

TORCH GmbH - A Graylog Company
Steckelhörn 11
20457 Hamburg
Germany

https://www.graylog.com 

Commercial Reg. (Registergericht): Amtsgericht Hamburg, HRB 125175
Geschäftsführer: Lennart Koopmann (CEO)

-- 
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/CAMqbBbJFogS-o6LrwmSZ_O60SY7Q9TqYqw3wiVzKax4yr4tu7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Graylog installation

[sikender . mohammad]

Hi,

Can we install graylog on windows? I am getting may errors when I try to 
start the graylog collector. 

I tried to install graylog on Redhat Vm, sounds like the service is not 
getting started because of space issue. Can anyone tell me how to avoid 
this ? 

Is there any way I could play with open source webservice graylog?  Please 
do let me in installing graylog. I want to see how it works. 



Thank you

-- 
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/39e8d454-7c64-40c8-a689-8bf3d5719f74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.