Zap will not start

[N Anderton]

I have ZAP installed on a build server Windows 2008 R2 and on my Windows 7 desktop, and Zap only occasionally starts. I click on the program and my cursor shows it is waiting for a second or 2 and then nothing. The command interface will also not show any signs of running. Then just out of the blue it might launch the program.

 

any help is appreciated.

 

thanks Noel

 

 

[Simon Bennetts]

Can you have a look at the zap.log file in the 'standard directory' : https://code.google.com/p/zaproxy/wiki/FAQconfig and see if there are any errors logged.
How much memory does the box have?

ZAP should start consistently on all platforms, although it can take a little while to start up if you dont have much memory.

Cheers,

Simon

[N Anderton]

Thanks, there is a Log directory in the install directory, I was looking for the log files in there.

Here is the exceptions

2014-08-20 11:06:34,356 INFO  ZAP - OWASP ZAP 2.3.1 started.

2014-08-20 11:06:34,467 ERROR Model - Failed to delete file C:\Users\nanderton\OWASP ZAP\session\untitled1.data

2014-08-20 11:06:34,468 ERROR Model - Failed to delete file C:\Users\nanderton\OWASP ZAP\session\untitled1.lck

2014-08-20 11:06:34,468 ERROR Model - Failed to delete file C:\Users\nanderton\OWASP ZAP\session\untitled1.log

2014-08-20 11:06:44,931 FATAL ZAP - invalid database address: jdbc:hsqldb:file:C:/Users/nanderton/OWASP ZAP/session/untitled1

java.sql.SQLException: invalid database address: jdbc:hsqldb:file:C:/Users/nanderton/OWASP ZAP/session/untitled1

at org.sqlite.JDBC.createConnection(JDBC.java:110)

at org.sqlite.JDBC.connect(JDBC.java:87)

at java.sql.DriverManager.getConnection(Unknown Source)

at java.sql.DriverManager.getConnection(Unknown Source)

at org.parosproxy.paros.db.DatabaseServer.start(Unknown Source)

at org.parosproxy.paros.db.DatabaseServer.<init>(Unknown Source)

at org.parosproxy.paros.db.Database.open(Unknown Source)

at org.parosproxy.paros.model.Model.createAndOpenUntitledDb(Unknown Source)

at org.parosproxy.paros.model.Model.init(Unknown Source)

at org.zaproxy.zap.ZAP.run(Unknown Source)

at org.zaproxy.zap.ZAP.main(Unknown Source)

It was the java process that still had a lock on the files. I killed that process and i was able to get ZAP to start. It takes about 4 - 5 minutes to start, I have another question on the forum asking about how long it takes.

It looks like my attempts to start it Headless are failing some how, and they leave the process locking the files. 

My machine has 20GB of RAM, the Build server only has 4GB Ram. Is 20GB not sufficient?

[Visser, Dale]

I run ZAP scans on a Linux VM which has only 5.2 GB RAM allocated to it. On top of that, I watch my memory usage, and it never hits the swap partition.

--
You received this message because you are subscribed to the Google Groups "OWASP ZAP User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Simon Bennetts]

Yeah, 20Gb is _loads_ of memory.
I suspect the problem might be that you're trying to start ZAP multiple times, due to the huge start up time.
Lets focus on that (in the other thread?) and once we get that sorted hopefully you wont get the locking problem.

To unsubscribe from this group and stop receiving emails from it, send an email to zaproxy-users+unsubscribe@googlegroups.com.

[Gladwin Dsouza]

I was facing a similar issue, the ZAP tool was working fine on my local machine but was displaying erratic behavior on the Virtual Machine. I tried all the previously mentioned suggestions but none of them could mitigate the issue. Upon checking the log files i found out that the HSQLDB files were being locked even after closing the tool or even if the tool did not start. I eventually figured out that the difference between the 2 environments was just the operating system. My local had Windows 10 pro while the VM had Windows 10 enterprise. So in case if any one else is facing similar, kindly check the operating system.