Open Krytical13 opened 7 years ago
@Krytical13 have you been able to launch WAIL when not using powershell?
I am not familiar if there exists any differences from the normal windows shell and powershell.
WAIL relies on the commands Tasklist /fi "Windowtitle eq Heritrix" /fo csv
and Tasklist /fi "ImageName eq wayback.exe" /fo csv
to ensure they were started.
Was there additional command windows spawned when launching Heritrix?
ahh, I apologize. I guess I forgot to try running normally again after I un-blocked the files. So this does in fact run properly after un-blocking, running normally without admin. If you select "Run As Admin" it continues to fail starting the services.
I started by running the .exe normally, and it failed the same way as originally stated. I then ran the .exe as administrator and it failed the same way as originally stated. I then tried through CMD/Powershell, and it failed, but I realized I needed to un-block the files in windows. Once I un-blocked the files, I kept trying through powershell/CMD, instead of running normally.
Are you submitting a bug report or a feature request?
Bug Report
What is the current behavior?
Download release 1.1.0 for windows (newest release I could find with included .exe) Extract to c:\wail unblock all files (powershell>get-childitem | unblock-file) execute wail.exe
WAIL windows appears on screen, Attempts to start services, but has red ! message in WAIL window states "Wayback is waiting to be started" However when I start using cmd or powershell, I can see this message in the command line window:
However hertix appears to be started... not sure if it finished started, but there is a heritrix window open, and I can connect to the heritrix web interface.
What is the expected behavior?
everything should start up fully I'm guessing?
What's your environment?
WAIL version 1.1.0 for windows Windows 10 x64 1709
Other information