Clean install of 3.7 fails with tomcat 5.5.27 on archlinux

Hay guyse,
It appears that after moving subsonic.war to /opt/tomcat/webapps/, clearing /var/subsonic and /opt/tomcat/work and (re)starting tomcat I get the classic 404 "requested resource () is not available" message no matter what.
3.7b1 and 3.7 both fail to deliver. Catalina and subsonic logs are all dead quiet, here's the last relevant line from subsonic.log:
INFO DaoHelper - Done checking database schema.
3.6 would continue with the SearchService announcements, however there are no entries regardless of how long the server has been up.
I fixed the problem with 3.7 by rolling back to a clean install of 3.6 for now, also unchecking "Notify me about new versions."
-Bebe
It appears that after moving subsonic.war to /opt/tomcat/webapps/, clearing /var/subsonic and /opt/tomcat/work and (re)starting tomcat I get the classic 404 "requested resource () is not available" message no matter what.
3.7b1 and 3.7 both fail to deliver. Catalina and subsonic logs are all dead quiet, here's the last relevant line from subsonic.log:
INFO DaoHelper - Done checking database schema.
3.6 would continue with the SearchService announcements, however there are no entries regardless of how long the server has been up.
I fixed the problem with 3.7 by rolling back to a clean install of 3.6 for now, also unchecking "Notify me about new versions."
-Bebe