OpenNethome - an open home automation project

After about a day after rebooting NetHome Raspary PI i get this when try to check the log. IF i reboot it works againg for a day or so.

-------------------------------------------------------------------------------------------
HTTP ERROR: 500

INTERNAL_SERVER_ERROR
RequestURI=/home

Caused by:

java.lang.NullPointerException
at nu.nethome.home.items.web.servergui.LogPage.printLog(LogPage.java:88)
at nu.nethome.home.items.web.servergui.LogPage.printPage(LogPage.java:74)
at nu.nethome.home.items.web.servergui.SettingsBasePage.printPage(SettingsBasePage.java:78)
at nu.nethome.home.items.web.servergui.HomeGUI.service(HomeGUI.java:232)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
Powered by Jetty://
------------------------------------------------------------------------------------------------------------------------------------------

Hmm, must be some odd log row without source class name. I fixed the logg-printer so it should be able to handle that situation, the fix is in the nightly build now. Test it and see if it helps.

Thank you for realy quick respons, ill try it out...

Regards