Re: [graylog2] Problem upgrading to Graylog 1.2 on Debian 8

Hi! the repository packages for Debian 7 and 8 are currently not upgradeable. Please remove the graylog-1.1-repository-debian7 first and then install the graylog-1.2-repository-debian8 package. Regards, Bernd Fisz [Tue, Sep 15, 2015 at 10:57:38PM -0700] wrote: >Hello, >I have problem

Re: [graylog2] Re: Problem with streeam alerts after updating to graylog1.2

Hi Edmundo, It was a rpm upgrade from the latest stable version: 1.1.6-1.noarch.rpm No modifications to the config file. Arie. Op woensdag 16 september 2015 11:22:52 UTC+2 schreef Edmundo Alvarez: > > Hi Arie, > > From which version did you upgrade to 1.2? It would also be helpful to > know

Re: [graylog2] Re: Problem with streeam alerts after updating to graylog1.2

Hi Arie, >From which version did you upgrade to 1.2? It would also be helpful to know if >that was a clean installation or an upgrade from an even earlier version. Regards, Edmundo > On 16 Sep 2015, at 11:10, Arie wrote: > > I'dd had an error on producing the clone,

[graylog2] Re: create inputs using config file

So far i know input configuration are stored in mongo data and mapped to node id, so if you keep you mongo db and use same node id it should work Am Mittwoch, 16. September 2015 11:01:35 UTC+2 schrieb Ming Fang: > > Is there a way to create inputs using a config file? > > I want a set of inputs

[graylog2] create inputs using config file

Is there a way to create inputs using a config file? I want a set of inputs to be automatically create if necessary based on settings in a config file. Currently I creating the inputs using the REST Api. See the end of my Dockerfile here

[graylog2] Updated Graylog Appliance 1.1.6

Hi All, Apologies if this has been asked previously. Is this still the correct guidance to upgrade the Graylog appliance from 1.1.6 to the new 1.2GA? http://docs.graylog.org/en/1.2/pages/installation/graylog_ctl.html#upgrade-graylog Many Thanks, James. -- You received this message because

Re: [graylog2] graylog extractor regular expression

Thanks Kay ! That worked On Sunday, September 13, 2015 at 6:29:06 PM UTC+5:30, Kay Röpke wrote: > > Hi! > > You can use standard regular expression syntax here (the Java flavor). > Simply anchor the regex at the end of the string. > > /(\w+)$ > > That should do the trick, you can verify in the

[graylog2] Re: Problem with streeam alerts after updating to graylog1.2

Cloning the stream is not possible either Op woensdag 16 september 2015 10:53:47 UTC+2 schreef Arie: > > Hi, > > we are encountering problems with stream alerts after the update. > When editing/testing the alert condition we get this message in the GUI. > > *Could not retrieve AlarmCallbacks* >

[graylog2] Re: Problem with streeam alerts after updating to graylog1.2

I'dd had an error on producing the clone, but it appeard to be there. After putting the receivers in it, il looks like it is worrking. So whot is wrong with the original alerts. ? Op woensdag 16 september 2015 10:55:54 UTC+2 schreef Arie: > > Cloning the stream is not possible either > > Op

[graylog2] Problem with streeam alerts after updating to graylog1.2

Hi, we are encountering problems with stream alerts after the update. When editing/testing the alert condition we get this message in the GUI. *Could not retrieve AlarmCallbacks* *Fetching AlarmCallbacks failed with status: Internal Server Error* server logfile (partial): ERROR

Re: [graylog2] Re: Problem with streeam alerts after updating to graylog1.2

And second: In the alert the "callbacks" part in the GUI keeps "loading" going on endlesly. I remember editing the calback email condition so we are closer intho the problem I guess Arie Op woensdag 16 september 2015 11:22:52 UTC+2 schreef Edmundo Alvarez: > > Hi Arie, > > From which

Re: [graylog2] extending disk of OVA deployed Graylog server (a newbie How-To)

Thanks for the detailed walk through! I have added this to the documentation: http://docs.graylog.org/en/1.2/pages/installation/graylog_ctl.html On 15 September 2015 at 21:29, Lasse Taul Bjerre wrote: > Hi, > > New to Graylog, and not really a Linux user/admin. > > My LAB

Re: [graylog2] Re: Problem with streeam alerts after updating to graylog1.2

That is very well possible, 1.0 or 1.01 but not totally shore of it. In one of the upgrades I had a problem with some data that was the result of a Yum update from repository where old data was deleted an a wrong/missing node-id file. We use the contend-pack function for backup of a lot of

[graylog2] Re: create inputs using config file

Hi, Graylog currently doesn't support a "bootstrap" configuration file with entity configurations (e. g. inputs, streams, outputs, etc.) but you can use the content pack feature to export a content pack containing your entity configurations and import/apply that to your Graylog setup via the

Re: [graylog2] Re: Problem with streeam alerts after updating to graylog1.2

Hi Edmundo, The (email) calback alerts that fail where made in a version prior to 1.1. A callback alert recently made in the latest version (1.1.6) was fine after the update. hth,, Arie Op woensdag 16 september 2015 11:22:52 UTC+2 schreef Edmundo Alvarez: > > Hi Arie, > > From which

Re: [graylog2] upgrading graylog-server from 1.16 to 1.2rc4 totally broke all LDAP access

For the sake of keeping a public record: We discussed this privately and in the end Graylog 1.2 works as expected in this environment, but due to the specific constraints the page showing the Group mapping timed out waiting for an answer. To work around this you can set this in the

[graylog2] Re: Updated Graylog Appliance 1.1.6

Hi James, yes. Cheers, Jochen On Wednesday, 16 September 2015 11:01:35 UTC+2, rogersmanau wrote: > > Hi All, > > Apologies if this has been asked previously. Is this still the correct > guidance to upgrade the Graylog appliance from 1.1.6 to the new 1.2GA? >

[graylog2] Re: Anyone attempted to use AWS cloudsearch service to back graylog rather than clustering elasticsearch?

Hi Cory, Graylog is currently pretty much tied in with Elasticsearch as its default output and for searches. Since AWS Cloudsearch isn't compatible with Elasticsearch, it's probably not easily possible to use that as a backend right now. It should be possible, though, to write a relatively

Re: [graylog2] Problem with streeam alerts after updating to graylog1.2

We saw a similar problem with an alert callback that was created in 1.0, it could be the same problem that you are experiencing. Could you share with us your "alarmcallbackconfigurations" MongoDB collection in order to further investigate the issue? Please send it to edmu...@graylog.com if it

[graylog2] Re: Search Issue ...

Are you using the prebuilt filter via this method? Also are you using a relative or absolute time range search? 1. Find message that contains the field you want to filter by 2. Expand message by clicking (to show all fields with the Magnifying logo) 3. Click on the Magnifying logo for the field

Re: [graylog2] Graylog shows no menu after login

Hi Anant, By the way you described the problem, there must be some error loading Javascript. Could you please take a look at the Javascript console in your browser and share any errors that you might see there? It would also be helpful knowing the browser and OS you use. Please also ensure

[graylog2] Re: Updated Graylog Appliance 1.1.6

Thanks Jochen. Went flawlessly. Very impressed! On Wednesday, September 16, 2015 at 7:07:02 PM UTC+8, Jochen Schalanda wrote: > > Hi James, > > yes. > > Cheers, > Jochen > > On Wednesday, 16 September 2015 11:01:35 UTC+2, rogersmanau wrote: >> >> Hi All, >> >> Apologies if this has been asked