Re: [graylog2] problems connecting to the Graylog server with OVA

[victorfeng1973]

tried again. same.

I can log into the VM with Putty from my desktop. 

I tried it with both FireFox and Chrome, same error. 

But when I tried it on IE, I got login page(the login page is on port 80. 
It did not change to port 443). After entering admin/admin, click on 
Signing in button, the button turned into gray  gray, and not able to 
log in.

Port 443 is not up running.
ubuntu@graylog:~$ netstat -an | egrep -w "80|443" | grep LISTEN
tcp0  0 0.0.0.0:80  0.0.0.0:*   LISTEN

Is your 443 up? 

Thanks

On Wednesday, January 4, 2017 at 6:30:08 PM UTC-5, Nico Zanferrari wrote:
>
> Hello,
>
> I've just tried what you've described, and it works fine. 
>
> Did you reboot the VM before the "sudo graylog-ctl reconfigure"? If not, 
> can you do it now and reconfigure again?
> Can you ping the VM from your desktop?
>
> Nico
>
> 2017-01-04 21:29 GMT+01:00 :
>
>> Hi,
>>
>> I downloaded lastest graylog-2.1.2-1.ova and deployed it. We do not have 
>> DHCP server. After the OVA was deployed, I set static network for it.
>>
>> root@graylog:~# cat /etc/network/interfaces
>> # This file describes the network interfaces available on your system
>> # and how to activate them. For more information, see interfaces(5).
>>
>> # The loopback network interface
>> auto lo
>> iface lo inet loopback
>>
>> # The primary network interface
>> auto eth0
>> iface eth0 inet static
>>address 172.16.124.48
>>netmask 255.255.255.0
>>gateway 172.16.124.1
>>dns-nameservers 10.50.22.2 10.40.22.2
>>dns-domain van.com
>>dns-search van.com
>> pre-up sleep 2
>>
>> Then ssh to the IP as user ubuntu, and ran 
>>
>> sudo graylog-ctl reconfigure
>>
>> Then try http://172.16.124.48/ from my desktop, I got following message:
>>
>> We are experiencing problems connecting to the Graylog server running on 
>> *http://172.16.124.48:9000/api/ 
>> *. Please verify that the server is 
>> healthy and working correctly.
>>
>> You will be automatically redirected to the previous page once we can 
>> connect to the server.
>>
>>
>>  What did I miss? I also tried to run as user root, and sudo graylog-ctl 
>> restart
>>
>>
>> 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+u...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/graylog2/86e979aa-3695-4036-99b0-0188aa767584%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/283fdfa6-9c37-40b8-a2d1-817b281c4a49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [graylog2] problems connecting to the Graylog server with OVA

[Nico Zanferrari]

Hello,

I've just tried what you've described, and it works fine.

Did you reboot the VM before the "sudo graylog-ctl reconfigure"? If not,
can you do it now and reconfigure again?
Can you ping the VM from your desktop?

Nico

2017-01-04 21:29 GMT+01:00 :

> Hi,
>
> I downloaded lastest graylog-2.1.2-1.ova and deployed it. We do not have
> DHCP server. After the OVA was deployed, I set static network for it.
>
> root@graylog:~# cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> auto eth0
> iface eth0 inet static
>address 172.16.124.48
>netmask 255.255.255.0
>gateway 172.16.124.1
>dns-nameservers 10.50.22.2 10.40.22.2
>dns-domain van.com
>dns-search van.com
> pre-up sleep 2
>
> Then ssh to the IP as user ubuntu, and ran
>
> sudo graylog-ctl reconfigure
>
> Then try http://172.16.124.48/ from my desktop, I got following message:
>
> We are experiencing problems connecting to the Graylog server running on 
> *http://172.16.124.48:9000/api/
> *. Please verify that the server is
> healthy and working correctly.
>
> You will be automatically redirected to the previous page once we can
> connect to the server.
>
>
>  What did I miss? I also tried to run as user root, and sudo graylog-ctl
> restart
>
>
> 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/86e979aa-3695-4036-99b0-0188aa767584%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/CAAE8D_CywYqKTyW%3DUvAJjvn_35qre8wXBagvPJp-NQvia%2BCTLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] problems connecting to the Graylog server with OVA

[victorfeng1973]

Hi,

I downloaded lastest graylog-2.1.2-1.ova and deployed it. We do not have 
DHCP server. After the OVA was deployed, I set static network for it.

root@graylog:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
   address 172.16.124.48
   netmask 255.255.255.0
   gateway 172.16.124.1
   dns-nameservers 10.50.22.2 10.40.22.2
   dns-domain van.com
   dns-search van.com
pre-up sleep 2

Then ssh to the IP as user ubuntu, and ran 

sudo graylog-ctl reconfigure

Then try http://172.16.124.48/ from my desktop, I got following message:

We are experiencing problems connecting to the Graylog server running on 
*http://172.16.124.48:9000/api/ 
*. Please verify that the server is healthy 
and working correctly.

You will be automatically redirected to the previous page once we can 
connect to the server.


 What did I miss? I also tried to run as user root, and sudo graylog-ctl 
restart


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/86e979aa-3695-4036-99b0-0188aa767584%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] We are experiencing problems connecting to the Graylog server running on with OVA

[victorfeng1973]

Hi,

I downloaded graylog-2.1.2-1.ova and deployed it. We do not have DHCP 
server. After the OVA was deployed, I set static network for it.

root@graylog:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
   address 172.16.124.48
   netmask 255.255.255.0
   gateway 172.16.124.1
   dns-nameservers 10.50.30.2 10.40.30.2
   dns-domain corp.seic.com
   dns-search corp.seic.com
pre-up sleep 2

Then ssh to the IP as user ubuntu, and ran 

sudo graylog-ctl reconfigure

Then try http://172.16.124.48/ from my desktop, I got following message.  

We are experiencing problems connecting to the Graylog server running on 
*http://172.16.124.48:9000/api/*. Please verify that the server is healthy 
and working correctly.

You will be automatically redirected to the previous page once we can 
connect to the server.


 What did I miss? I also tried to run as user root, and sudo graylog-ctl 
restart


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/77b4c609-615e-4798-9bd6-695e304c35d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [graylog2] Re: 30% CPU usage

[Stefano Tranquillini]

I may have found (so far 1 day without the problem) the problem, i had the
zencast enabled in the conf.

On Tue, Jan 3, 2017 at 3:04 PM, Stefano Tranquillini <
stefano.tranquill...@gmail.com> wrote:

> To explain better:
> i've two phisical servers on which we manage VMs
> server A has 12 VMs, server B has 6 VMs. Graylog is 1 VMs on both, and
> receives data from 1 VMs. same amount of memory and space.
> Both graylog version are Graylog 2.1.1+01d50e5, installed pretty much the
> same day.
> configuration wise it the same, if there's anything in particular that I
> should check out pls let me know. There's nothing special, just 1 single
> input (UDP) with a JSON extractor. 8 indices retetion of 1week time.
> the only thing is that the server with 30% has a slightly more traffic,
> but not so much to have such a high cpu..
>
> On Tue, Jan 3, 2017 at 2:52 PM, Jochen Schalanda 
> wrote:
>
>> Hi Stefano,
>>
>> On Tuesday, 3 January 2017 14:15:23 UTC+1, Stefano Tranquillini wrote:
>>>
>>> any idea? it keeps replicating the behaviour and I don't get why.
>>>
>>
>> what does "pretty much the same load and configuration" mean exactly?
>> What do the logs of both Graylog nodes say?
>>
>> Cheers,
>> Jochen
>>>
>>> --
>> 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/to
>> pic/graylog2/GS5rJubNRBg/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/ms
>> gid/graylog2/89cff080-be1b-446f-84b7-74db52b4fd25%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Stefano
>



-- 
Stefano

-- 
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/CAPQ1%3DkAYV-8F4hbowvU1N%3DRWqCB%3D1G7T-JejaRq3gSgoZGx0%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [graylog2] Plugin API documentation?

[Dennis Oelkers]

Hey,

> On 04.01.2017, at 15:05, dhef...@gmail.com wrote:
> 
> I've installed the Jabber Alarm Callback plugin and found it to be of little 
> use and would like to make it a little more informative. It really only tells 
> you about a specific stream triggered an alert for some reason but you have 
> no idea about the event context.
> 
> Is there a better source of plugin API documentation (available function 
> calls, callbacks, variables, etc) than this? 
> http://docs.graylog.org/en/2.1/pages/plugins.html. 

unfortunately not, although we try to create as much documentation for plugin 
authors as we can. If you are not satisfied with our documentation for plugin 
authors (have you seen the part about the example alarm callback plugin - 
http://docs.graylog.org/en/2.1/pages/plugins.html#example-alarm-callback-plugin 
?) you could start by taking a look at the source code of other plugins (for 
example the email alarm callback - 
https://github.com/Graylog2/graylog2-server/blob/master/graylog2-server/src/main/java/org/graylog2/alarmcallbacks/EmailAlarmCallback.java
 or the code of the jabber alarm callback plugin itself). If you make progress, 
we would love to have you creating a PR for the documentation repo 
(https://github.com/graylog2/documentation) including the missing pieces.

If you have any more specific questions about plugin development details, feel 
free to ask them here.

Kind regards,
D.

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

TORCH GmbH - A Graylog company
Poolstrasse 21
20355 Hamburg
Germany

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/EBBDE5F3-5213-4CFE-8A15-2B8876C18F8B%40graylog.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Plugin API documentation?

[dheffem]

I've installed the Jabber Alarm Callback plugin and found it to be of 
little use and would like to make it a little more informative. It really 
only tells you about a specific stream triggered an alert for some reason 
but you have no idea about the event context.

Is there a better source of plugin API documentation (available function 
calls, callbacks, variables, etc) than this? 
http://docs.graylog.org/en/2.1/pages/plugins.html. 

-- 
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/bcf6fd53-4c10-4a5b-9752-23db674d8801%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Postfix

[Jochen Schalanda]

Hi Janis,

you could use simple syslog to send these messages to 
Graylog: 
https://github.com/Graylog2/graylog-guide-syslog-linux/blob/master/README.md

Cheers,
Jochen

On Wednesday, 4 January 2017 12:09:35 UTC+1, Janis Apsitis wrote:
>
> Hi folks
>
>
> i am new in Graylog and looking for small help i want to send all postfix 
> logs (freebsd server) to Graylog server(Linux)!
>
>
> thx
>
>
>
>
>
>

-- 
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/b362ac45-fc39-47f5-b47a-3f84219ce590%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Postfix

[Janis Apsitis]

Hi folks


i am new in Graylog and looking for small help i want to send all postfix 
logs (freebsd server) to Graylog server(Linux)!


thx





-- 
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/05b66133-8e2e-46ce-9403-24ceb81b7af3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Slow web interface and overly large JS files

[Jochen Schalanda]

Hi Richard,

On Wednesday, 4 January 2017 04:43:27 UTC+1, Richard S. Westmoreland wrote:
>
> Also is this the best place to post this?  Or is there a dev/eng specific 
> forum I can put these kinds of requests on?
>

You can file bug reports and feature requests as issues on GitHub at 
https://github.com/Graylog2/graylog2-server/issues/

Cheers,
Jochen 

-- 
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/d5ec7225-b3e3-432c-be66-6d9230a39ec8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Feature Request: JS client only calls Web URI

[Jochen Schalanda]

Hi Richard,

the Graylog web interface (in version 2.x) has been designed to be a 
single-page application (SPA) which, once it has been loaded by the user's 
web browser, will only communicate with the Graylog REST API.

You can override the default URI the web interface is using with the 
web_endpoint_uri setting or the X-Graylog-Server-URL HTTP request header, 
see 
http://docs.graylog.org/en/2.1/pages/configuration/web_interface.html#how-does-the-web-interface-connect-to-the-graylog-server
 
for details.

In general, rest_transport_uri should be the URI of the Graylog REST API, 
which other Graylog nodes are able to connect to (i. e. not the URI of your 
load balancer), while web_endpoint_uri should be the URI of the Graylog 
REST API, which the web interface should connect to (i. e. the URI of your 
load balancer).

Cheers,
Jochen

On Wednesday, 4 January 2017 07:13:01 UTC+1, Richard S. Westmoreland wrote:
>
> I've just figured out how to get my reverse proxy working properly to 
> fully support the web client, but it leads me to another dilemma.  When the 
> JS application loads, it tries to talk to the REST API URI rather than just 
> the Web API URI.  This poses a problem when I want to publicly expose and 
> proxy the web interface, but not the main rest interface (or vice versa).  
> I have to set both the web_endpoint_uri and rest_transport_uri to the same 
> domain due to use of https.  This means that all of my graylog nodes are 
> going to try and connect to my public IP which is then handled by my 
> reverse proxy and has to redistribute again - which causes an unnecessary 
> resource bottleneck on my main node running the reverse proxy.
>
> So my feature request is that the JS client only ever talks to the api via 
> web_endpoint_uri.  That way the web and rest can be setup for different use 
> cases.
>
> 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/17cfe6af-3e9f-45bc-89ce-14763cb1a52c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Chatty ajax

[Jochen Schalanda]

Hi Richard,

On Wednesday, 4 January 2017 07:53:43 UTC+1, Richard S. Westmoreland wrote:
>
> Is there anyway to change the ajax request time from 1s to something like 
> 5s?  I looked around the documentation and configuration but couldn't find 
> any options for setting this.
>

There's currently no configuration setting for this.

Feel free to file a feature request 
at https://github.com/Graylog2/graylog2-server/issues

Cheers,
Jochen

-- 
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/3b824dfa-24db-43f2-8b4e-5a552f9296bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.