maybe try 'pkg install sqlite3' or possibly even py27-sqlite3? I'm not sure what method murmur uses to call sqlite, but I know there were some issues with this.
also i never mess with the vanilla or vimage setting, I just leave them alone.
Bingo! installing sqlite3 did the trick for me. I have to fix the permissions on the database but chmod 777 did the trick as a test so at least I know it will work now:
root@murmur:/ # pkg install sqlite3
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
The following 1 packages will be affected (of 0 checked):
Installed packages to be UPGRADED:
sqlite3: 3.8.2 -> 3.8.6
The process will require 55 kB more space.
556 kB to be downloaded.
Proceed with this action? [y/N]: y
[murmur] Fetching sqlite3-3.8.6.txz: 100% 556 kB 570.1k/s 00:01
Checking integrity... done (0 conflicting)
[murmur] [1/1] Upgrading sqlite3 from 3.8.2 to 3.8.6: 100%
root@murmur:/ # /usr/local/sbin/murmurd -ini /usr/local/etc/murmur.ini -supw ********
<W>2014-09-05 12:53:01.568 Initializing settings from /usr/local/etc/murmur.ini (basepath /usr/local/etc)
<W>2014-09-05 12:53:01.568 Binding to address 0.0.0.0
<W>2014-09-05 12:53:01.569 OpenSSL: OpenSSL 0.9.8y 5 Feb 2013
<C>2014-09-05 12:53:01.569 WARNING: You are running murmurd as root, without setting a uname in the ini file. This might be a security risk.
<W>2014-09-05 12:53:01.587 ServerDB: Opened SQLite database /var/db/murmur/murmur.sqlite
<W>2014-09-05 12:53:01.588 Generating new tables...
<F>2014-09-05 12:53:01.812 Superuser password set on server 1
root@murmur:/ # service murmur start
Starting murmur.
ServerDB: Database is not writable
root@murmur:/ # chmod 777 /var/db/murmur/murmur.sqlite
root@murmur:/ # service murmur start
Starting murmur.
Thanks Joshua!