Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#621 closed defect (fixed)

ALL ISSUES RESOLVED!!!! Unable to Access i2p after upgrade to 0,8.13-20

Reported by: DISABLED Owned by: zzz
Priority: minor Milestone: 0.9
Component: apps/console Version: 0.8.13
Keywords: Unable to Access i2p following upgrade to 0.8.13.20 Cc: hotlady@…
Parent Tickets: Sensitive: no

Description (last modified by zzz)

Hi Folks,

I upgraded from 0.8.13.0 to 0.8.13.20. This upgrade was performed through my i2p router console. After the download completed, I attempted to restart the router. However, even after waiting 10 minutes, I was unable to access i2p. Then I completely restarted my laptop. After this reboot, I opened the i2p (restatable) link, and copied all of the information from this window, so hopefully you can tell me what is going on…and better yet, what I need to change.

Just so you know, I was never unable to access i2p following this upgrade. I tried to unstall 0.8.13.20 using the Izpack uninstaller, but the uninstaller completely hung. I do not know if this is another bug, because my Izpack uninstaller works just fine for 0.8.13.0!!

So I physically deleted the i2p directory, and reinstalled the SHA 256 verified 0.8.13.0. I can now access i2p, but I still cannot access my webserver. I have documented my log files concerning this specific issue at http://pastethis.i2p/show/948/ and http://pastethis.i2p/show/951/.

BTW - I previously had this same issue of not being able to access i2p after attempting to upgrade from 0.8.13.0 to 0.8.13.4. That i2p date I downloaded (and verified) from Echelon website. Followed the same steps I outlined above.

Please take a look at the attached *.pdf file of the i2p start window output.

If anyone cares to e-mail me I am at:

1hK3-hMMGVzLALCVst2sLxDxQQr6gCOrpu1Dw0xjz2nqKQbSBTZIuHnAvE93Meh1kX-e3a4C8nZ1PWgvUbjpwl on 12p-Bote,

or hotlady@… on Susimail.

Best regards,

PrivacyHawk?

Subtickets

Attachments (1)

i2p - 0.8.13.20 - Startup Errors.pdf (118.7 KB) - added by DISABLED 7 years ago.
i2p Start-up Window Output and Errors

Download all attachments as: .zip

Change History (10)

Changed 7 years ago by DISABLED

i2p Start-up Window Output and Errors

comment:1 Changed 7 years ago by zzz

Description: modified (diff)

To get your eepsite working on jetty 5 with 0.8.13-0 again, restore clients.config and eepsite/jetty.xml from the backups clients.config.jetty5 and eepsite/jetty5.xml, and restart I2P.

On 0.8.13-20, did you follow the instructions (shown at the top of the pdf) to resolve the error? did it fix the problem?

comment:2 Changed 7 years ago by zzz

Component: unspecifiedapps/console
Milestone: 0.8.130.9
Owner: set to zzz
Status: newassigned

I've tried twice to fix this on Windows, maybe third time will do it. I have an idea.

comment:3 Changed 7 years ago by zzz

3rd attempt to fix checked in as 0.8.13-22. Please test and report.

comment:4 Changed 7 years ago by zzz

Cc: hotlady@… added

comment:5 in reply to:  1 Changed 7 years ago by DISABLED

Replying to zzz:

To get your eepsite working on jetty 5 with 0.8.13-0 again, restore clients.config and eepsite/jetty.xml from the backups clients.config.jetty5 and eepsite/jetty5.xml, and restart I2P.

On 0.8.13-20, did you follow the instructions (shown at the top of the pdf) to resolve the error? did it fix the problem?

Hi ZZZ,

I have sent you a Susimail with updated information concerning the issues I am continuing to experience. Yes - I did try the change suggested in the .pdf…and it did not fix the problem.

Please let me know how to restore the files you have referenced above. Windows tells me there are no previous versions of my i2p Clients configuration file.

Please let me know what you think after you have had a chance to read my email.

Thanks ZZZ…and best regards,

PrivacyHawk?

comment:6 in reply to:  3 Changed 7 years ago by DISABLED

Replying to zzz:

3rd attempt to fix checked in as 0.8.13-22. Please test and report.

Hi ZZZ,

Very much appreciate your efforts to fix this issue. However, it appears 3rd attempt is not successful. Downloaded and installed 0.8.13-24 today. Same inability to access i2p after restart and laptop reboot. Please check my susimail to you, and the attached files.

Best regards,

PrivacyHawk?

comment:7 Changed 7 years ago by DISABLED

Summary: Unable to Access i2p after upgrade to 0,8.13-20ALL ISSUES RESOLVED!!!! Unable to Access i2p after upgrade to 0,8.13-20

Hi ZZZ,

I am very pleased to report that through KYTV's diligence and intelligence yesterday with me via chatzilla, KYTV provided the necessary changes to resolve EVERY i2p problem I had been experiencing. My inability to access i2p after previous upgrade attempts have been resolved, and eepsite webserver access issue no longer exists. Happy to report I am writing to you from within 0.8.13-25!!

Lessons Learned:

  1. Users experienced similar issues must rename the i2p profile folder, which file location is pointed to under the Clients Tab. On my system, the relevant profile is located at:

"To change other client options, edit the file C:\Users\AppData?\Roaming\I2P\clients.config. All changes require restart to take effect."

  1. Per KYTV's suggestion, I renamed the i2p folder to i2p.old.
  1. Windows users MUST have i2p completely shutdown PRIOR to this renaming attempt, otherwise Windows will display "Access Denied" with no further explanation.
  1. Don't know if this was necessary, but I then uninstalled i2p, re-booted my laptop, installed a clean copy of 0.8.13-0, and hurrah…EVERYTHING worked.
  1. I then downloaded KYTV's update zip file, copied it into my i2p directory…restarted i2p…and everything works on 0.8.13-25!!

Thanks for your help ZZZ…and please pass on my sincere thanks to KYTV…who simply ROCKS!!!

Best regards,

PrivacyHawk?

comment:8 in reply to:  7 Changed 7 years ago by killyourtv

Resolution: fixed
Status: assignedclosed

Replying to guest:

  1. Per KYTV's suggestion, I renamed the i2p folder to i2p.old.
  1. Windows users MUST have i2p completely shutdown PRIOR to this renaming attempt, otherwise Windows will display "Access Denied" with no further explanation.

Part of our exchange last night:
<privacyhawk> What would you like me to change?
<killyourtv> I'd like you to do what I've suggested a few times. 1) Stop I2P; 2) rename the old profile directory; 3) start I2P

So you see, there's a reason I said to do it that way… ;)

Anyhow, I'm glad it works now (but zzz's instructions at 1 would have fixed your problems). I'd still like to know what went wrong during the migration from 0.8.13 to the dev build) because clearly the log at http://pastethis.i2p/show/951/ was from /after/ you reverted back to 0.8.13 (because as I mentioned last night, the class referenced in your log (org.mortbay.start.Main) does not exist in 0.8.13).

According to the paste (#951), you (may have) upgraded to 0.8.13-4 when the problems started so I think that maybe you got 'bitten' by early jetty6 'issues' that went away around -9. If you were able to go from a clean 0.8.13 to 0.8.13-25 without problems, I think this bug can be closed.

comment:9 Changed 7 years ago by zzz

Thanks guys. I was really confused with the original issue, because you had Jetty 6 errors on what you said was a 0.8.13-0 install. I had no idea you had previously tried an update and then attempted to undo it.

It's been a bumpy ride the last few weeks but it seems like things are shaking out. Thoroughly resolving tickets like these is important to give us the confidence to move forward with a release.

Note: See TracTickets for help on using tickets.