Opened 8 years ago

Last modified 4 years ago

#905 open enhancement

What a mess with log files in Windows :-(

Reported by: DISABLED Owned by:
Priority: minor Milestone:
Component: wrapper Version: 0.9.4
Keywords: windows install Cc: killyourtv
Parent Tickets: #1410 Sensitive: no


After some hours from start it seems that the path to log file for wrapper changes in "C:\Program Files (x86)\i2p\wrapper.log" that is not the path when i2p started.
Router Logs also, always display 'uninitialized' also if I have configured it many times.
Anyone could help me to understand this mess?
Thank U

Always ready to give more details about.


Change History (7)

comment:1 Changed 8 years ago by zzz

Windows version?

Running as service or not?

The router log stays 'uninitialized' until it's first written to, but that's probably bad UI and needs improvement. Also there was a bug #805 on setting the router log location, fixed in 0.9.5

comment:2 Changed 8 years ago by killyourtv

Cc: killyourtv added

I found that when I2P starts it tries to write wrapper.log to %appdata%\i2p, but that doesn't exist until I2P is run for the first time. Since it can't write to %appdata%\i2p wrapper.log goes to the CWD.

On subsequent runs, wrapper.log is written to %appdata%\i2p.

One possible solution would be to use the shipped but currently unused script "i2prouter.bat" to start I2P using the wrapper. If we do that we can create %appdata%\i2p ourselves.

--- installer/resources/i2prouter.bat   a1f0a332f42a1ac4e2dbe4401e8d8b3f388bcf65
+++ installer/resources/i2prouter.bat   0bdad331cb3add5e40a48862ec427588423048f4
@@ -85,8 +85,9 @@ rem
 rem Start the Wrapper
+if not exist "%APPDATA%\I2P" mkdir "%APPDATA%\I2P"
 if not errorlevel 1 goto :eof
+rem pause
--- installer/resources/shortcutSpec.xml        adbea3965cdc4e4da8a0f8976bd8946d4388213e
+++ installer/resources/shortcutSpec.xml        9fd44536d245831eda7c18955b24ebfa8b5fdcaa
@@ -22,8 +22,7 @@
            startup="no" />
  <shortcut name="Start I2P (restartable)"
-           target="$INSTALL_PATH\I2Psvc.exe"
-           commandLine="-c wrapper.config"
+           target="$INSTALL_PATH\i2prouter.bat"

comment:3 Changed 8 years ago by zzz

Milestone: 0.9.6

Router log file name shown even if not yet written to, in 0.9.5-16 rev d9802bced393452a43755b7fa48f1d4eab8dd229 .

comment:4 Changed 8 years ago by zzz

re: i2prouter.bat

Yeah, I see that i2prouter does a mkdir of PIDDIR and LOGDIR for linux.

Is the wrapper log location wrong on /logs on the first run, or is it correct?

If it's correct, maybe this isn't a problem at all?
Do we want to add an i2prouter.bat right now, since we already have Windows startup stuff changes in the works with #912?

We could also make the dir in install.xml but I guess the permissions could be wrong, or in the wrong place if a different user installed it.

I see comments in wrapper.config that the PIDDIR must exist or the wrapper will fail to start. So that's disabled by default in wrapper.config (overridden for linux users in i2prouter).

comment:5 Changed 8 years ago by zzz

correction I meant #741 not #912 in the comment above

comment:6 Changed 6 years ago by str4d

Keywords: windows install added
Milestone: 0.9.6

comment:7 Changed 4 years ago by zzz

Parent Tickets: 1410
Status: newopen

#1410 and #1736 are dups

Note: See TracTickets for help on using tickets.