Hi Mark, Please check your Graylog server and web interface logs for more information. If you need help with it, we will need to know the error that is logged there when you access the nodes page, and please open a new thread for it :).
Regards, Edmundo -- Developer Tel.: +49 (0)40 609 452 077 Fax.: +49 (0)40 609 452 078 TORCH GmbH - A Graylog company Steckelhörn 11 20457 Hamburg Germany Commercial Reg. (Registergericht): Amtsgericht Hamburg, HRB 125175 Geschäftsführer: Lennart Koopmann (CEO) > On 26 Mar 2015, at 01:28, Mark Moorcroft <plak...@gmail.com> wrote: > > > Nice... > > BTW, I have been getting "This exception has been logged with id 6libgij97." > quite a bit today when I click on the "nodes" link. This is happening on both > of my graylog servers. > > On Monday, March 16, 2015 at 8:00:44 AM UTC-7, Jochen Schalanda wrote: > Hi, > > I'm delighted to announce the release of Graylog 1.0.1 into the wild. This is > purely a bug-fix release and doesn't bring any new features. > > The changes since Graylog 1.0.0 are: > > • Properly log stack traces (#970) > • Update REST API browser to new Graylog logo > • Avoid spamming the logs if the original input of a message in the > disk journal can't be loaded (#1005) > • Allows reader users to see the journal status (#1009) > • Compatibility with MongoDB 3.0 and Wired Tiger storage engine (#1024) > • Respect rest_transport_uri when generating entity URLs in REST API > (#1020) > • Properly map NodeNotFoundException (#1137) > • Allow replacing all existing Grok patterns on bulk import (#1150) > • Configuration option for discarding messages on error in AMQP inputs > (#1018) > • Configuration option of maximum HTTP chunk size for HTTP-based inputs > (#1011) > • Clone alarm callbacks when cloning a stream (#990) > • Add hasField() and getField() methods to MessageSummary class (#923) > • Add per input parse time metrics (#1106) > • Allow the use of log4j-extras classes in log4j configuration (#1042) > • Fix updating of input statistics for Radio nodes (#1022) > • Emit proper error message when a regular expression in an Extractor > doesn't match example message (#1157) > • Add additional information to system jobs (#920) > • Fix false positive message on LDAP login test (#1138) > • Calculate saved search resolution dynamically (#943) > • Only enable LDAP test buttons when data is present (#1097) > • Load more than 1 message on Extractor form (#1105) > • Fix NPE when listing alarm callback using non-existent plugin (#1152) > • Redirect to nodes overview when node is not found (#1137) > • Fix documentation links to integrations and data sources (#1136) > • Prevent accidental indexing of web interface by web crawlers (#1151) > • Validate grok pattern name on the client to avoid duplicate names > (#937) > • Add message journal usage to nodes overview page (#1083) > • Properly format numbers according to locale (#1128, #1129) > Thanks to everyone who helped creating this release by using Graylog and > reporting bugs and regressions to the mailing list and on GitHub. > > The official RPM and DEB packages, as well as the virtual machine images have > been updated with the new version. > > As always, if you find any bugs in this release, please open an issue on > GitHub at https://github.com/Graylog2/graylog2-server/issues. > > > Best regards, > Jochen (in the name of the Graylog team) > > -- > 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 graylog2+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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 graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
