Hi Michael
Seems to me that the problem is that the IceStorm Freeze database directory does not exists, or the user has not permission to read/write it. When IceStorm try to create the lock file it report the problem. Note that if you are using relative paths that is relative to the directory from where you start IceStorm.
I can easy reproduce that behavior by starting IceStorm with a non existent database directory.
Code:
clock $ /opt/Ice-3.4.2/bin/icebox --Ice.Config=config.icebox
!! 01/11/12 21:53:26.272 /opt/Ice-3.4.2/bin/icebox: error: ServiceManager: exception while starting service IceStorm:
FileUtil.cpp:461: IceUtil::FileLockedException:
could not lock file: `db/__Freeze/lock'
syscall exception: No such file or directory
If i create the database directory everything works as expected