Opened 8 years ago

Closed 8 years ago

#342 closed defect (fixed)

Wrapper double restart

Reported by: guest Owned by:
Priority: minor Milestone: 0.8.8
Component: router/wrapper Version: 0.8.1
Keywords: Cc:
Parent Tickets:

Description

I2P version: 0.8.1-13
Java version: Sun Microsystems Inc. 1.6.0_18 (OpenJDK Runtime Environment 1.6.0_18-b18)
Platform: Linux amd64 2.6.32-26-generic
Processor: uninitialized (athlon64)
Jbigi: Locally optimized native BigInteger? library loaded from the library path
Encoding: UTF-8

2010/11/29 15:17:45 | INFO: Started HttpContext?,/
2010/11/30 03:41:46 | 02:41:45.838 KRITISCH [hutdown hook] net.i2p.router.Router : Restarting after a brief delay
2010/11/30 03:41:48 | 30-nov-2010 2:41:48 org.mortbay.util.Container stop
2010/11/30 03:41:48 | INFO: Stopped org.mortbay.jetty.servlet.WebApplicationHandler?@16edbe39
2010/11/30 03:41:48 | 30-nov-2010 2:41:48 org.mortbay.util.Container stop
2010/11/30 03:41:48 | INFO: Stopped WebApplicationContext?i2pbote,i2pbote
2010/11/30 03:41:48 | NeoDatis? server stopping
2010/11/30 03:41:48 | NeoDatis? ODB Server (port 65534) shutdown [uptime=19Hours]
2010/11/30 03:41:48 | SeedlessCache? Exited.
2010/11/30 03:41:48 | SeedlessSeedFinder? Exited.
2010/11/30 03:41:48 | SeedlessSeedFinder? server context destroyed
2010/11/30 03:41:48 | 30-nov-2010 2:41:48 org.mortbay.util.Container stop
2010/11/30 03:41:48 | INFO: Stopped org.mortbay.jetty.servlet.WebApplicationHandler?@2d42c778
2010/11/30 03:41:48 | 30-nov-2010 2:41:48 org.mortbay.util.Container stop
2010/11/30 03:41:48 | INFO: Stopped WebApplicationContext?SeedlessConsole,/SeedlessConsole
2010/11/30 03:41:48 | 30-nov-2010 2:41:48 org.mortbay.util.Container stop
2010/11/30 03:41:48 | INFO: Stopped org.mortbay.jetty.servlet.WebApplicationHandler?@fc54796
2010/11/30 03:41:48 | 30-nov-2010 2:41:48 org.mortbay.util.Container stop
2010/11/30 03:41:48 | INFO: Stopped WebApplicationContext?snowman,snowman
2010/11/30 03:41:57 | 02:41:57.354 KRITISCH [hutdown hook] net.i2p.router.Router : Shutdown(4) complete
2010/11/30 03:41:59 | on_exit trigger matched. Restarting the JVM. (Exit code: 4)
2010/11/30 03:42:13 | Launching a JVM...
2010/11/30 03:42:14 | Wrapper (Version 3.1.1) http://wrapper.tanukisoftware.org
2010/11/30 03:42:14 |
2010/11/30 03:42:14 | Starting I2P 0.8.1-13
2010/11/30 03:42:15 | INFO: Locally optimized native BigInteger? library loaded from the library path
2010/11/30 03:43:16 | TERM trapped. Shutting down.
2010/11/30 03:43:17 | 02:43:17.178 CRIT [r 1 shutdown] net.i2p.router.Router : Shutting down the router...
2010/11/30 03:43:17 | 02:43:17.178 CRIT [r 1 shutdown] net.i2p.router.Router : Shutdown(3) complete
2010/11/30 03:43:18 | <-- Wrapper Stopped
2010/11/30 03:43:30 | --> Wrapper Started as Daemon
2010/11/30 03:43:30 | Launching a JVM...
2010/11/30 03:43:30 | Wrapper (Version 3.1.1) http://wrapper.tanukisoftware.org
2010/11/30 03:43:30 |
2010/11/30 03:43:30 | Starting I2P 0.8.1-13

Subtickets

Change History (3)

comment:1 Changed 8 years ago by zzz

  • Component changed from router/general to router/wrapper
  • Summary changed from double restart to Wrapper double restart

How did you stop the router in the first place? From the console? i2prouter stop?

2010/11/30 03:43:16 | TERM trapped. Shutting down.

What caused this? did you send a SIGTERM? C?

comment:2 Changed 8 years ago by guest

update was downloaded, I hit the "restart button" on router console. after a whil I tried to refresh the view and it still was not up.
after shutting down it srtarted -12 found update and started -13 but never came really up.
i2prouter status said it was running but no router console came up.
had to stop it with i2prouter stop, it hung a bit but then exited and then I start with i2prouter start. So I had to restart twice for one update (with the automatic restart three in total).

comment:3 Changed 8 years ago by zzz

  • Milestone set to 0.8.8
  • Resolution set to fixed
  • Status changed from new to closed

Shutdown and wrapper communication reworked significantly in 0.8.7-xxx (what will be 0.8.8), should be a lot more reliable now.

Note: See TracTickets for help on using tickets.