Admittedly I am not a sophisticated mysql/apache/linux user but usually able to hold my own.  I have been running Tracks off a local server using a mysql backend based on the instructions from the Tracks website.  For a week everything ran perfectly (ubuntu 8.10, tracks 1.7, latest ruby, etc.) with absolutely no issues whatsoever.  I was able to access tracks from anywhere on my local network. 

Then I had to go out of town a few days and powered off the server.  When I returned I was unable to connect to the Tracks homepage.  The database is there and seems to be fine whether accessed locally or over the network.  I can browse the tracks folders through the web, logs etc. but can’t connect to the home page or login page and xxx.xxx.xx.xxx:3000/login and browsing the tracks folders I don’t see any index pages or login pages in the folder. 

I really can’t find anything on google or reading any of the posts here that would explain what happened or what to do.  If anyone has any suggestions I would appreciate it.  My theory would be that either something is not starting or that I need to re-install something but really don’t want to lose all my work so far by wiping the database and starting over.

Hope I am being clear and if I need to add something let me know.

I guess this was just to remind myself of two things.  1) I am an idiot,  2)If you haven’t slept for 3 days it is probably best to wait before attempting anything remotely mental. 

Bottom line is that I had forgotten to run the server script.  I guess it is hard for Tracks to run if you don’t start it.  Sorry for wasting the time of anyone who bothered to read this.  I will now slink away.