Testnet question

How long does it take to sync testnet? I am not able to hit this url after 10 mins
http://127.0.0.1:8989/ncc/web/index.html

logs:
2016-08-24 22:11:55.579 INFO chain update of 400 blocks (7 transactions) needed 249 ms (35571 μs/tx) (org.nem.nis.sync.BlockChainUpdateContext fu)
transactions257
transactions257
transactions257
transactions257
transactions257
transactions257
transactions257
2016-08-24 22:11:55.596 INFO synchronizing with Node [Testnet1 ] @ [50.3.87.123] finished (org.nem.peer.services.NodeSynchronizer a)
2016-08-24 22:11:58.596 INFO synchronizing with Node [Hi, I am BigAlice2 ] @ [104.128.226.60] (org.nem.peer.services.NodeSynchronizer a)
2016-08-24 22:11:59.209 INFO received 400 blocks (2 transactions) in 334 ms from remote (167000 μs/tx) (org.nem.nis.sync.BlockChainUpdater c)
2016-08-24 22:11:59.406 INFO clustering completed: { clusters: 1 (average size: 5.00), hubs: 0, outliers: 271 } (org.nem.nis.pox.poi.PoiContext$AccountProcessor dd)
2016-08-24 22:11:59.408 INFO Iterations required: 5; converged?: true (org.nem.nis.cx.na.xgf run)
2016-08-24 22:11:59.408 INFO POI iterator needed 1ms. (org.nem.nis.pox.poi.PoiImportanceCalculator c)
2016-08-24 22:11:59.624 INFO validated 400 blocks (2 transactions) in 412 ms (206000 μs/tx) (org.nem.nis.sync.BlockChainUpdateContext fu)
2016-08-24 22:11:59.624 INFO new block’s score: 4827389370417792 (org.nem.nis.sync.BlockChainUpdateContext a)
2016-08-24 22:11:59.911 INFO chain update of 400 blocks (2 transactions) needed 287 ms (143500 μs/tx) (org.nem.nis.sync.BlockChainUpdateContext fu)
transactions257
transactions257

thank you

The log is a nis log and looks ok.
If you don’t get a response from the above url it means that ncc doesn’t run.
Did you start ncc? If yes can you supply the logs?

ah…got it. So I need to run nis and ncc for the client to come up(the client is up now). If I just run ncc, does it use the remote nodes?

If i say ‘already a member’ it shows the mainnet wallet as available.

Also, I have a mainnet account on the same machine. Would a testnet account interfere with the wallet creation?

thank you

You can change the ncc settings to use a remote nis instead of a local nis.
mainnet and testnet account have to be in different wallets. Aside from that there is no restriction, you can have both mainnet wallets and testnet wallets on the same computer.

thank you.

Getting this error now…both nis and ncc is running on testnet. What certificate is it complaining about?

Getting error when creating wallets and when opening them. I have the latest release

2016-08-25 23:29:36.278 WARNING no certificate found for (file:/home/USERNAME/crypto/nem_test/package/ncc/nem-core-0.6.79-BETA.jar ) (org.nem.core.metadata.CodeSourceFacade )
2016-08-25 23:29:36.280 INFO Analyzing meta data in <nem-core-0.6.79-BETA.jar> (org.nem.core.metadata.JarFacade )
2016-08-25 23:29:36.289 INFO Meta data title , version <0.6.79-BETA> (org.nem.core.metadata.JarFacade )
2016-08-25 23:29:36.585 INFO exiting /ncc/api/version [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor afterCompletion)
2016-08-25 23:29:36.974 INFO entering /ncc/api/wallet/create [127.0.0.1] (org.nem.ncc.controller.interceptors.AuditInterceptor preHandle)
2016-08-25 23:29:37.067 INFO Opening storable entity for writing located at </home/USERNAME/nem/ncc/TESTWALLET.wlt> (org.nem.ncc.storable.entity.storage.StorableEntityFileDescriptor openWrite)
2016-08-25 23:29:37.070 INFO Opening storable entity for writing located at </home/USERNAME/nem/ncc/TESTWALLET.adb> (org.nem.ncc.storable.entity.storage.StorableEntityFileDescriptor openWrite)
2016-08-25 23:29:37.071 INFO Opening storable entity for writing located at </home/USERNAME/nem/ncc/TESTWALLET.adb> (org.nem.ncc.storable.entity.storage.StorableEntityFileDescriptor openWrite)

Don’t worry about that message it only means that the jars are not signed via an official certificate.
This does not influence the behavior of the software in any way.