# Web interface not available **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [June 11, 2018, 9:21am UTC](https://community.graylog.org/t/web-interface-not-available/5539 "2018-06-11T09:21:22Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![ale1](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@ale1](https://community.graylog.org/u/ale1)\ **Post date:** [June 11, 2018, 9:21am UTC](https://community.graylog.org/t/web-interface-not-available/5539/1 "2018-06-11T09:21:22Z")
Hello, When I have reboot my graylog server, I have a problem with the web interface because it’s not available. When I see the status of Mongodb en elasticsearch, I have some problems : > ● mongod.service - High-performance, schema-free document-oriented database > Loaded: loaded (/usr/lib/systemd/system/mongod.service; enabled; vendor preset: disabled) > Active: failed (Result: exit-code) since lun. 2018-06-11 10:47:44 CEST; 22min ago > Docs: [https://docs.mongodb.org/manual](https://docs.mongodb.org/manual) > Process: 944 ExecStart=/usr/bin/mongod $OPTIONS (code=exited, status=1/FAILURE) > Process: 937 ExecStartPre=/usr/bin/chmod 0755 /var/run/mongodb (code=exited, status=0/SUCCESS) > Process: 931 ExecStartPre=/usr/bin/chown mongod:mongod /var/run/mongodb (code=exited, status=0/SUCCESS) > Process: 923 ExecStartPre=/usr/bin/mkdir -p /var/run/mongodb (code=exited, status=0/SUCCESS) > > juin 11 10:47:41 GRAYLOG-SERVER systemd[1]: Starting High-performance, schema-free document-oriented database… > juin 11 10:47:44 GRAYLOG-SERVER mongod[944]: about to fork child process, waiting until server is ready for connections. > juin 11 10:47:44 GRAYLOG-SERVER mongod[944]: forked process: 1640 > juin 11 10:47:44 GRAYLOG-SERVER systemd[1]: mongod.service: control process exited, code=exited status=1 > juin 11 10:47:44 GRAYLOG-SERVER systemd[1]: Failed to start High-performance, schema-free document-oriented database. > juin 11 10:47:44 GRAYLOG-SERVER systemd[1]: Unit mongod.service entered failed state. > juin 11 10:47:44 GRAYLOG-SERVER systemd[1]: mongod.service failed. > [admin@GRAYLOG-SERVER ~]$ systemctl status elasticsearch > > ● elasticsearch.service - Elasticsearch > Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled) > Active: failed (Result: exit-code) since lun. 2018-06-11 10:47:52 CEST; 22min ago > Docs: [http://www.elastic.co](http://www.elastic.co) > Process: 933 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID\_DIR}/elasticsearch.pid --quiet -Edefault.path.logs=${LOG\_DIR} -Edefault.path.data=${DATA\_DIR} -Edefault.path.conf=${CONF\_DIR} (code=exited, status=1/FAILURE) > Process: 926 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS) > Main PID: 933 (code=exited, status=1/FAILURE) > > juin 11 10:47:41 GRAYLOG-SERVER systemd[1]: Starting Elasticsearch… > juin 11 10:47:41 GRAYLOG-SERVER systemd[1]: Started Elasticsearch. > juin 11 10:47:46 GRAYLOG-SERVER elasticsearch[933]: OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure the number of parall…elGCThreads=N > juin 11 10:47:52 GRAYLOG-SERVER systemd[1]: elasticsearch.service: main process exited, code=exited, status=1/FAILURE > juin 11 10:47:52 GRAYLOG-SERVER systemd[1]: Unit elasticsearch.service entered failed state. > juin 11 10:47:52 GRAYLOG-SERVER systemd[1]: elasticsearch.service failed. Thanks to help me ---
**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\ **Post date:** [June 11, 2018, 9:39am UTC](https://community.graylog.org/t/web-interface-not-available/5539/2 "2018-06-11T09:39:06Z")
Check the logs of your MongoDB, Elasticsearch, and Graylog nodes. ➡ [http://docs.graylog.org/en/2.4/pages/configuration/file\_location.html](http://docs.graylog.org/en/2.4/pages/configuration/file_location.html) ---
**Author:** ![ale1](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@ale1](https://community.graylog.org/u/ale1)\ **Post date:** [June 11, 2018, 9:45am UTC](https://community.graylog.org/t/web-interface-not-available/5539/3 "2018-06-11T09:45:54Z")
Thanks I see that the file is used at 100% : > /dev/mapper/vg00-lv\_var 976M 912M 0 100% /var But I don’t know what is the role of this file ---
**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\ **Post date:** [June 11, 2018, 10:14am UTC](https://community.graylog.org/t/web-interface-not-available/5539/4 "2018-06-11T10:14:01Z")
`/var` is the directory in Linux systems, which is being used to store application data. This directory (or the underlying disk partition) being filled 100%, is the reason that none of your services are running anymore. ---
**Author:** ![ale1](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@ale1](https://community.graylog.org/u/ale1)\ **Post date:** [June 11, 2018, 10:17am UTC](https://community.graylog.org/t/web-interface-not-available/5539/5 "2018-06-11T10:17:15Z")
I have increase the size of the partition /dev/mapper/vg00-lv\_var. So I have no memory problem Now the service mongodb and elasticsearch works, but the web interface is again unavailable ---
**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\ **Post date:** [June 11, 2018, 10:39am UTC](https://community.graylog.org/t/web-interface-not-available/5539/6 "2018-06-11T10:39:58Z")
> [@ale1](#): > > Now the service mongodb and elasticsearch works, but the web interface is again unavailable Then again, check the logs of all relevant services. ---
**Author:** ![ale1](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@ale1](https://community.graylog.org/u/ale1)\ **Post date:** [June 11, 2018, 11:56am UTC](https://community.graylog.org/t/web-interface-not-available/5539/7 "2018-06-11T11:56:38Z")
I check the logs but I’ve non error message ---
**Author:** ![ale1](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@ale1](https://community.graylog.org/u/ale1)\ **Post date:** [June 11, 2018, 12:19pm UTC](https://community.graylog.org/t/web-interface-not-available/5539/8 "2018-06-11T12:19:03Z")
I see that on my graylog server : > – L’unité (unit) graylog-server.service a commencé à démarrer. > juin 11 14:12:02 GRAYLOG-SERVER polkitd[622]: Unregistered Authentication Agent for unix-process:5767:77895 (system bus name :1.32, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr\_FR.UTF- > juin 11 14:12:02 GRAYLOG-SERVER graylog-server[5773]: OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure the number of parallel GC threads ---
**Author:** ![ale1](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@ale1](https://community.graylog.org/u/ale1)\ **Post date:** [June 11, 2018, 1:03pm UTC](https://community.graylog.org/t/web-interface-not-available/5539/9 "2018-06-11T13:03:04Z")
In fact, I’ve a problem with iptables rules. Now it’s works ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\ **Post date:** [June 25, 2018, 1:03pm UTC](https://community.graylog.org/t/web-interface-not-available/5539/10 "2018-06-25T13:03:12Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.