Block #515,000 has hit and everything looks stable. MaWo will post his analysis about the hard fork after he has completed it, as it is currently ongoing.
I can confirm it looks good.
I only observed an issue with nodes which use highly shared resources. Some of them needed a long time for the calculation of the 515000 checksum.
Yeah something is strange
2015-12-06 10:09:59 INFO: Finished blockchain download
2015-12-06 10:10:17 INFO: Checksum calculated:
[52, -50, -25, 21, -64, 23, 123, -110, -74, 4, 91, -53, -91, 49, -117, -54, -119, -45, 112, -114, -85, 7, -123, -106, 65, -2, -97, 30, -36, 18, 49, 63]
And on most of my slower nodes
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.sql.SQLException: Login timeout
at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:209)
at nxt.db.BasicDb.getPooledConnection(BasicDb.java:170)
at nxt.db.BasicDb.getConnection(BasicDb.java:164)
at nxt.db.TransactionalDb.getConnection(TransactionalDb.java:62)
at nxt.db.EntityDbTable.getManyBy(EntityDbTable.java:175)
... 8 more
2015-12-06 11:20:49 INFO: Blockchain download in progress
2015-12-06 11:20:49 INFO: Downloaded 68 blocks in 59 s, 20 per s, 0 min left
2015-12-06 11:20:49 INFO: Finished blockchain download