Hallo,
ich habe das Programm auf meinem Raspberry Pi installiert.
Per Android App, kann ich Kategorien und Rezepte anlegen und editieren, aber wenn ich mich per PC aufschalte, sehe ich die Dinge zwar kann Sie aber nicht bearbeiten.
Ich denke, das könnte daran liegen, dass das Startscript nicht durchläuft. Es hängt an der folgenden Stelle seid 10 min
pi@raspberrypi:~ $ /etc/init.d/rezepte
18:36:54,107 |-INFO in ch.qos.logback.classic.c.a.a - Setting ReconfigureOnChang eFilter scanning period to 15 seconds
18:36:54,280 |-INFO in ReconfigureOnChangeFilter{invocationCounter=0} - Will sca n for changes in [] every 15 seconds.
18:36:54,281 |-INFO in ch.qos.logback.classic.c.a.a - Adding ReconfigureOnChange Filter as a turbo filter
18:36:54,316 |-INFO in ch.qos.logback.core.a.a.f - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
18:36:54,328 |-INFO in ch.qos.logback.core.a.a.f - Naming appender as [CONSOLE]
18:36:54,486 |-INFO in ch.qos.logback.core.a.a.r - Assuming default type [ch.qos .logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
18:36:54,634 |-INFO in ch.qos.logback.core.a.a.f - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
18:36:54,643 |-INFO in ch.qos.logback.core.a.a.f - Naming appender as [FILE]
18:36:54,704 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No compressio n will be used
18:36:54,710 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern rezeptSuite.%d{yyyy-MM-dd}.log for the active file
18:36:54,724 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggerin gPolicy - The date pattern is ‘yyyy-MM-dd’ from file name pattern ‘rezeptSuite.% d{yyyy-MM-dd}.log’.
18:36:54,724 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggerin gPolicy - Roll-over at midnight.
18:36:54,746 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggerin gPolicy - Setting initial period to Wed Nov 09 18:13:12 CET 2016
18:36:54,750 |-INFO in ch.qos.logback.core.a.a.r - Assuming default type [ch.qos .logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
18:36:54,759 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - A ctive log file name: log.dir_IS_UNDEFINED/rezeptSuite.log
18:36:54,760 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - F ile property is set to [log.dir_IS_UNDEFINED/rezeptSuite.log]
18:36:54,765 |-INFO in ch.qos.logback.classic.c.a.k - Setting level of ROOT logg er to INFO
18:36:54,766 |-INFO in ch.qos.logback.core.a.a.g - Attaching appender named [FIL E] to Logger[ROOT]
18:36:54,768 |-INFO in ch.qos.logback.core.a.a.g - Attaching appender named [CON SOLE] to Logger[ROOT]
18:36:54,770 |-INFO in ch.qos.logback.classic.c.a.h - Setting level of logger [o rg.apache.cayenne] to WARN
18:36:54,771 |-INFO in ch.qos.logback.core.a.a.g - Attaching appender named [FIL E] to Logger[org.apache.cayenne]
18:36:54,772 |-INFO in ch.qos.logback.core.a.a.g - Attaching appender named [CON SOLE] to Logger[org.apache.cayenne]
18:36:54,772 |-INFO in ch.qos.logback.classic.c.a.a - End of configuration.
18:36:54,774 |-INFO in ch.qos.logback.classic.c.a@1474c6c - Registering current configuration as safe fallback point
2016-11-09 18:36:54,784 1310 [main] INFO rezeptSuite.fx.RezeptSuite - start app lication
2016-11-09 18:36:54,806 1332 [main] INFO rezeptSuite.fx.RezeptSuite - workDirec tory: /home/pi/RezeptSuite/app
2016-11-09 18:36:54,807 1333 [main] INFO rezeptSuite.fx.RezeptSuite - installDi rectory: /home/pi/RezeptSuite/app
2016-11-09 18:36:54,935 1461 [main] INFO rezeptSuite.fx.RezeptSuite - creating DI injector
2016-11-09 18:36:56,044 2570 [main] INFO rezeptSuite.fx.RezeptSuite - created D I injector
2016-11-09 18:36:56,045 2571 [main] INFO rezeptSuite.fx.RezeptSuite - init data base
2016-11-09 18:36:56,763 3289 [main] INFO rezeptSuite.service.db.o - removing ob ject context
2016-11-09 18:36:56,765 3291 [main] INFO rezeptSuite.service.db.n - stopping da tabase server
2016-11-09 18:36:56,765 3291 [main] INFO rezeptSuite.service.db.n - starting da tabase server: /home/pi/RezeptSuite/app/rezepteDB
2016-11-09 18:36:59,257 5783 [main] INFO rezeptSuite.service.db.o - creating object context
2016-11-09 18:36:59,743 6269 [main] INFO rezeptSuite.service.db.o - reload recipe data
2016-11-09 18:37:01,329 7855 [main] INFO rezeptSuite.fx.RezeptSuite - database initialized
2016-11-09 18:37:01,331 7857 [main] INFO rezeptSuite.fx.RezeptSuite - init jetty server
2016-11-09 18:37:01,405 7931 [main] INFO org.eclipse.jetty.util.log - Logging initialized @9365ms
2016-11-09 18:37:02,531 9057 [main] INFO org.eclipse.jetty.server.Server - jetty-9.3.z-SNAPSHOT
2016-11-09 18:37:02,953 9479 [main] INFO o.j.r.plugins.guice.ModuleProcessor - registering factory for rezeptSuite.rest.v1.CategoriesResource
2016-11-09 18:37:03,075 9601 [main] INFO o.j.r.plugins.guice.ModuleProcessor - registering factory for rezeptSuite.rest.v1.RecipesResource
2016-11-09 18:37:03,103 9629 [main] INFO o.j.r.plugins.guice.ModuleProcessor - registering factory for rezeptSuite.rest.v1.RecipesSearchResource
2016-11-09 18:37:03,111 9637 [main] INFO o.j.r.plugins.guice.ModuleProcessor - registering factory for rezeptSuite.rest.v1.ConfigResource
2016-11-09 18:37:03,117 9643 [main] INFO o.j.r.plugins.guice.ModuleProcessor - registering factory for rezeptSuite.rest.v1.SyncResource
2016-11-09 18:37:03,131 9657 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@d39a69{/ws,null,AVAILABLE}
2016-11-09 18:37:03,254 9780 [main] INFO o.e.j.w.StandardDescriptorProcessor - NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
2016-11-09 18:37:04,029 10555 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.w.WebAppContext@818ac4{/,jar:file:/home/pi/RezeptSuite/app/rezeptsuite.client.fx.jar!/www,AVAILABLE}
2016-11-09 18:37:04,101 10627 [main] INFO o.e.jetty.server.AbstractConnector - Started ServerConnector@6c097d{HTTP/1.1,[http/1.1]}{0.0.0.0:8000}
2016-11-09 18:37:04,103 10629 [main] INFO org.eclipse.jetty.server.Server - Started @12077ms
2016-11-09 18:37:04,104 10630 [main] INFO rezeptSuite.fx.RezeptSuite - Jetty started
Jetzt ist doch noch was passiert:
2016-11-09 18:51:54,871 901397 [Scheduler-16953777] ERROR r.socketio.SocketIOServlet - Timeout on Read
java.net.SocketTimeoutException: Timeout on Read
at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.f(SourceFile) ~[rezeptsuite.client.fx.jar:na]
at org.eclipse.jetty.io.AbstractConnection.a(SourceFile) ~[rezeptsuite.client.fx.jar:na]
at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.a(SourceFile) ~[rezeptsuite.client.fx.jar:na]
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.a(SourceFile) ~[rezeptsuite.client.fx.jar:na]
at org.eclipse.jetty.io.FillInterest.a(SourceFile) [rezeptsuite.client.fx.jar:na]
at org.eclipse.jetty.io.AbstractEndPoint.a(SourceFile) [rezeptsuite.client.fx.jar:na]
at org.eclipse.jetty.io.IdleTimeout.v(SourceFile) [rezeptsuite.client.fx.jar:na]
at org.eclipse.jetty.io.IdleTimeout$1.run(SourceFile) [rezeptsuite.client.fx.jar:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_65]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_65]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]
Kann mir jemand sagen was ich falsch mache…
Vielen Dank