I have also deployed two instances; but both show this problem. It intrigues me; all static files are present in the lib/graylog.jar and the main.css looks fine there. I don't understand why multiple instances would have the same problem with the exact same file....
the log shows nothing special and lsof shows no caches on disk. Stracing doesn't help either On Monday, February 24, 2014 3:00:52 PM UTC+1, Micoto Szillat wrote: > > I also have problems with the main.css being empty. Today, I installed two > instances of Graylog2 and this only occurs on one of them. Maybe the assets > are compiled and cached on the server somewhere? > > On Monday, February 24, 2014 10:18:04 AM UTC+1, sjon wrote: >> >> Okay I moved both the elasticsearch and mongodb data and reconfigured a >> GELF input; but I partially experience the same problem: although /streams >> now works; my main.css is still empty and the interface looks like crap. >> All other css files work fine. Since this is all contained in the custom >> java web-server there is little I can do to debug this, right? Is there >> anything special about the main.css that causes this to break; or is the >> problem caused by something else? >> >> I have attached a screenshot of the home-page after logging in (the >> login-page works fine), not sure if it helps >> >> On Saturday, February 22, 2014 9:35:57 PM UTC+1, lennart wrote: >>> >>> Yes! Your old data unfortunately is not compatible with the new >>> version. We did so many changes from 0.12 to 0.20 that we decided to >>> make a hard break and not build in any migrations or similar. >>> >>> Future versions will of course ship with a proper migration path. >>> >>> Starting with a clean ElasticSearch and MongoDB setup should fix your >>> problems. >>> >>> Thanks, >>> Lennart >>> >>> On Fri, Feb 21, 2014 at 12:50 PM, sjon <[email protected]> wrote: >>> > I just installed graylog-web-interface-0.20 and some things don't seem >>> to >>> > work right. The interface looks a bit strange because >>> > /assets/stylesheets/main.css is empty (although the response-code is >>> 200). >>> > Also; the /streams page is empty (with a 500 response-code). I cannot >>> find >>> > any messages in the logfiles that help me any further. Can anyone help >>> me >>> > debug this? >>> > >>> > This installation runs with a pre-0.20 elasticsearch & mongo database >>> and I >>> > haven't taken any explicit migration steps; might that be the problem? >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups >>> > "graylog2" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> an >>> > email to [email protected]. >>> > For more options, visit https://groups.google.com/groups/opt_out. >>> >> -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
