Re: [graylog2] Graylog shows no menu after login

2015-09-17 Thread Anant Sawant
Hi Edmundo,

Thanks!!
The cause of this issue was the "app.js" file which graylog was no able to 
load. I fixed it and now the graylog is working fine.
Though it is working fine, when I start the Graylog server component I get 
the following lines on console "Failed to load sigar falling back to jmx 
implementation". Is this something I should be worried about as with this 
still everything works fine. Can you please suggest me something on this. 
As I have no idea about this.

Thanks in advance!!
Anant :-)

On Wednesday, 16 September 2015 23:23:55 UTC+5:30, Edmundo Alvarez wrote:
>
> 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 that you are 
> not using any plugin blocking Javascript execution for Graylog. 
>
> Regards, 
>
> Edmundo 
>
> > On 16 Sep 2015, at 18:58, Anant Sawant  > wrote: 
> > 
> > Hi! 
> > 
> > I am running Graylog 1.1.6 server component and Graylog web component 
> 1.1.6 which I have setup manually. 
> > I am running this on ubuntu 14.04.1. For this I have installed 
> Elasticsearch 1.7.2, mongodb version v3.0.6 and Java 1.8.0_60. The Graylog 
> 1.1.6 server component, Graylog web component 1.1.6, Mongod and 
> Elasticsearch are on the same machine. For configuration I have referred  
> http://docs.graylog.org/en/1.2/pages/installation/manual_setup.html#configuring-the-web-interface.
>  
> As per this document Graylog 1.1.6 server component and Graylog web 
> component 1.1.6 both are running well/as expected as I can see the expected 
> result on the console, also the logs shows no errors/exception. It also 
> shows the graylog login screen, but when I login using the credentials I 
> see no menu's, all I get is a simple page saying "graylog-web-interface 
> v1.1.6 (2e264c2) (Oracle Corporation 1.8.0_60 / Linux 3.13.0-32-generic) on 
> ubuntu ". Why are the menus not visible?? 
> > Is it because as I have not pointed the configured elasticsearch to 
> syslog or any other log system. Or is the issue with the configuration?? 
> > I have attached the configuration files. 
> > 
> > Please suggest or give me a idea to where to look for this issue. 
> > 
> > Thanks in advance 
> > 
> > Anant:-) 
> > 
> > -- 
> > 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/6683ee44-dda1-4869-b72e-d43471f8d81e%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/ae5d6b2f-6a5d-467b-adf8-bba225b17509%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [graylog2] Graylog shows no menu after login

2015-09-16 Thread Edmundo Alvarez
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 that you are not using 
any plugin blocking Javascript execution for Graylog.

Regards,

Edmundo

> On 16 Sep 2015, at 18:58, Anant Sawant  wrote:
> 
> Hi!
> 
> I am running Graylog 1.1.6 server component and Graylog web component 1.1.6 
> which I have setup manually.
> I am running this on ubuntu 14.04.1. For this I have installed Elasticsearch 
> 1.7.2, mongodb version v3.0.6 and Java 1.8.0_60. The Graylog 1.1.6 server 
> component, Graylog web component 1.1.6, Mongod and Elasticsearch are on the 
> same machine. For configuration I have referred  
> http://docs.graylog.org/en/1.2/pages/installation/manual_setup.html#configuring-the-web-interface.
>  As per this document Graylog 1.1.6 server component and Graylog web 
> component 1.1.6 both are running well/as expected as I can see the expected 
> result on the console, also the logs shows no errors/exception. It also shows 
> the graylog login screen, but when I login using the credentials I see no 
> menu's, all I get is a simple page saying "graylog-web-interface v1.1.6 
> (2e264c2) (Oracle Corporation 1.8.0_60 / Linux 3.13.0-32-generic) on ubuntu 
> ". Why are the menus not visible??
> Is it because as I have not pointed the configured elasticsearch to syslog or 
> any other log system. Or is the issue with the configuration??
> I have attached the configuration files.
> 
> Please suggest or give me a idea to where to look for this issue.
> 
> Thanks in advance
> 
> Anant:-)
> 
> -- 
> 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/6683ee44-dda1-4869-b72e-d43471f8d81e%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/B118AA69-46B4-44B2-9644-C1010E29F80B%40graylog.com.
For more options, visit https://groups.google.com/d/optout.


[graylog2] Graylog shows no menu after login

2015-09-16 Thread Anant Sawant
Hi!

I am running Graylog 1.1.6 server component and Graylog web component 1.1.6 
which I have setup manually.
I am running this on ubuntu 14.04.1. For this I have installed 
Elasticsearch 1.7.2, mongodb version v3.0.6 and Java 1.8.0_60. The Graylog 
1.1.6 server component, Graylog web component 1.1.6, Mongod and 
Elasticsearch are on the same machine. For configuration I have referred  
http://docs.graylog.org/en/1.2/pages/installation/manual_setup.html#configuring-the-web-interface.
 
As per this document Graylog 1.1.6 server component and Graylog web 
component 1.1.6 both are running well/as expected as I can see the expected 
result on the console, also the logs shows no errors/exception. It also 
shows the graylog login screen, but when I login using the credentials I 
see no menu's, all I get is a simple page saying "graylog-web-interface 
v1.1.6 (2e264c2) (Oracle Corporation 1.8.0_60 / Linux 3.13.0-32-generic) on 
ubuntu ". Why are the menus not visible??
Is it because as I have not pointed the configured elasticsearch to syslog 
or any other log system. Or is the issue with the configuration??
I have attached the configuration files.

Please suggest or give me a idea to where to look for this issue.

Thanks in advance

Anant:-)

-- 
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/6683ee44-dda1-4869-b72e-d43471f8d81e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
# 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 = 
vfgnTDSZHrK2ptWuVtqgkc30g91JN5zAGgMINl1jXzOyohhlZwQF9wf9ruV1jw5o4SpyxcvwBCMUW8cTk2h7xq9ybmmFuDiK

# 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 = ""

# The time zone setting of the root user.
# The configured time zone must be parseable by 
http://www.joda.org/joda-time/apidocs/org/joda/time/DateTimeZone.html#forID-java.lang.String-
# Default is UTC
#root_timezone = UTC

# Set plugin directory here (relative or absolute)
plugin_dir = plugin

# REST API listen URI. Must be reachable by other graylog2-server nodes if you 
run a cluster.
rest_listen_uri = http://127.0.0.1:12900/

# REST API transport address. Defaults to the value of rest_listen_uri. 
Exception: If rest_listen_uri
# is set to a wildcard IP address (0.0.0.0) the first non-loopback IPv4 system 
address is used.
# If set, his will be promoted in the cluster discovery APIs, so other nodes 
may try to connect on
# this address and it is used to generate URLs addressing entities in the REST 
API. (see rest_listen_uri)
# You will need to define this, if your Graylog server is running behind a HTTP 
proxy that is rewriting
# the scheme, host name or URI.
#rest_transport_uri = http://192.168.1.1:12900/
 rest_transport_uri = http://127.0.0.1:12900/

# Enable CORS headers for REST API. This is necessary for JS-clients accessing 
the server directly.
# If these are disabled, modern browsers will not be able to retrieve resources 
from the server.
# This is disabled by default. Uncomment the next line to enable it.
#rest_enable_cors = true

# Enable GZIP support for REST API. This compresses API responses and therefore 
helps to reduce
# overall round trip times. This is disabled by default. Uncomment the next 
line to enable it.
#rest_enable_gzip = true

# Enable HTTPS support for the REST API. This secures the communication with 
the REST API with
# TLS to prevent request forgery and eavesdropping. This is disabled by 
default. Uncomment the
# next line to enable it.
#rest_enable_tls = true

# The X.509 certificate file to use for securing the REST API.
#rest_tls_cert_file =