Opened 8 years ago

Closed 8 years ago

#632 closed defect (no response)

Jetty Error in the log

Reported by: DISABLED Owned by:
Priority: major Milestone: 0.9.2
Component: unspecified Version: 0.9
Keywords: Cc:
Parent Tickets: Sensitive: no


I was update i2p to 0.9, it shows a error in the log
[er (eepsite)] uter.startup.LoadClientAppsJob?: Error starting up the client class org.mortbay.jetty.Server

java.lang.NoSuchMethodException?: org.mortbay.jetty.Server.main([Ljava.lang.String;)
at java.lang.Class.getMethod(Unknown Source)
at net.i2p.router.startup.LoadClientAppsJob?$RunApp?.run(LoadClientAppsJob?.java:237)
at Source)


Change History (3)

comment:1 Changed 8 years ago by zzz

The automatic migration to Jetty 6 for your eepsite did not work for some reason.

If you don't have an eepsite, you can disable the startup on /configclients .

If you do, you'll have to migrate the files manually. Change org.mortbay.jetty.Server to org.mortbay.start.Main on /configclients (or manually in the clients.config file).

If the jetty.xml and associated config files were not copied over by the migration, you'll have to get them from the $I2P/eepsite-jetty6 directory.

For us to investigate why the migration failed, please look for messages in your wrapper log when you first restarted after the update, and copy them here.

comment:2 Changed 8 years ago by zzz

Also, sponge.i2p has a Jetty 6 migration program that may be helpful.

Also, please supply the system information from the top of /logs

comment:3 Changed 8 years ago by zzz

Resolution: no response
Status: newclosed
Note: See TracTickets for help on using tickets.