Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Never completes first startup/install on windows 10 #95

Open
Krytical13 opened this issue Oct 26, 2017 · 2 comments
Open

Never completes first startup/install on windows 10 #95

Krytical13 opened this issue Oct 26, 2017 · 2 comments
Labels

Comments

@Krytical13
Copy link

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:

heritrix is not up starting
INFO: No tasks are running which match the specified criteria.

result of trying to find the hertrix pid windows { found: false }

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

C:\WAIL>
app ready
we do not have persisted pids
windowman init is done
init wail
first load
loadingWindow is ready to show
creating wail window
mainWindow is ready to show
creating creating archive manager
archiveManWindow is ready to show
creating crawl manager
archive man intial load
window manager send loadingWindow initial-load 'Archives have loaded'
mainWindow has loaded sending got-all-collections
window manager send mainWindow got-all-collections { cols: [ [Object] ], wasError: false }
crawlManWindow is ready to show
creating request daemon
got crawlMan-initial-load
window manager send loadingWindow initial-load 'Crawls have been loaded'
we have both load states, load is complete
window manager send mainWindow got-all-runs []
wail has both loading states
reqDaemonWindow is ready to show
all windows loaded
loading done
service man starting heritrix loading
checking serivce heritrix has not been started
heritrix is not up starting
INFO: No tasks are running which match the specified criteria.

result of trying to find the hertrix pid windows { found: false }

Oracle Corporation OpenJDK Runtime Environment 1.7.0-u80-unofficial-b32
Using ad-hoc HTTPS certificate with fingerprint...
SHA1:C9:A1:E7:28:43:39:AB:27:D3:43:DE:6C:C2:EE:8D:05:EC:E0:D3:AF
Verify in browser before accepting exception.
2017-10-26 18:39:45.442:INFO::Logging to STDERR via org.mortbay.log.StdErrLog
2017-10-26 18:39:45.442:INFO::jetty-6.1.26
2017-10-26 18:39:45.709:INFO::Started SslSocketConnector@localhost:8443
engine listening at port 8443
operator login set per command-line
NOTE: We recommend a longer, stronger password, especially if your web
interface will be internet-accessible.
Heritrix version: 3.2.0

@N0taN3rd N0taN3rd added the bug label Oct 26, 2017
@N0taN3rd
Copy link
Owner

@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?

@Krytical13
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants