Your config line also looks good. So the final question would be: did you restart Graylog after making the change?
Also, do you get any specific error messages on the login screen? And what does the Graylog logfile tell you? Refer to /var/log/graylog-server/server.log
java Exception: java.net.BindException: Address already in use
Error that shutsdowns Graylog:
org.graylog2.bootstrap.ServerBootstrap - Graylog startup failed. Exiting. Exception was:
java.lang.IllegalStateException: Expected to be healthy after starting. The following services are not running: {FAILED=[JerseyService [FAILED]]}
at com.google.common.util.concurrent.ServiceManager$ServiceManagerState.checkHealthy(ServiceManager.java:740) ~[graylog.jar:?]
at com.google.common.util.concurrent.ServiceManager$ServiceManagerState.awaitHealthy(ServiceManager.java:553) ~[graylog.jar:?]
at com.google.common.util.concurrent.ServiceManager.awaitHealthy(ServiceManager.java:312) ~[graylog.jar:?]
at org.graylog2.bootstrap.ServerBootstrap.startCommand(ServerBootstrap.java:149) [graylog.jar:?]
at org.graylog2.bootstrap.CmdLineTool.run(CmdLineTool.java:209) [graylog.jar:?]
at org.graylog2.bootstrap.Main.main(Main.java:44) [graylog.jar:?]
But after that error, if I run ./graylogctl status I get graylog-server not running, but still I can go to the login-page in Chrome and try to login
Ahhh, then I guess that graylogctl is not part of the standard RPM and DEB packages, but is included with the TGZ. Makes sense, because the RPM and DEB would rely on systemctl or service, whereas the TGZ is a generic installer to be used on Whatever Linux™.
So back to basics… Why did you originally ask about the username and password in the config file? Right now your question seems more focused on having conflicting Graylog instances on one box. Now’s the time for Linux-101 and troubleshooting; I hope you have some experience with that Graylog is not different from any other Linux-stack application when it comes to troubleshooting processes, ports and listeners.
Makes sense… In that case you’ll still need to do the Linux-101 troubleshooting to determine what’s going wrong Keep track of your processes and ports…