Ahh, thanks -- that's a bug with how the database is initialized for new installations. You can correct that by running this SQL query:UPDATE settings SET lastlogprocess=NOW();Fixed for the next build.
This bug is still in version 3.0.0b2