nodester/nodester — Issue #316: Can't start apps
Author: pateras
Created: 2012-02-25 22:19:51+00:00
State: open

None of my apps seem to start, even when they're just initialized. Just now, I did the following:

>nodester app create blanktest
nodester app init blanktest

After entering my password, I saw this:

> nodester info clone complete
nodester info Writing app data to config in blanktest\.nodester.appconfig
nodester info writing app files
nodester info processing the initial commit
nodester info blanktest started.
nodester info Some helpful app commands:

cd ./blanktest
curl http://blanktest.nodester.com/
nodester app info
nodester app logs
nodester app stop|start|restart

I then went to blanktest.nodester.com, which just said "Application offline".

Here are a few diagnostic attempts:

>$ nodester app info
nodester info Gathering information about: blanktest
nodester warn blanktest on port 14920 running: false (pid: unknown)
nodester info gitrepo: git@nodester.com:/node/git/REMOVED.git
nodester info appfile: server.js

I edited the repo url for this post (it doesn't actually say REMOVED). Not sure if that's something you'd want to make public. Anyway, notice the (pid: unknown). That doesn't look good.

>$ nodester app logs
nodester ERROR Fatal Error! API Response: {"status":"failure","message":"No logs available."}
Reason: No logs available.

>$ nodester app start
nodester info Attemping to start app: blanktest
nodester warn false

For a little more complete history, shortly after I created my first nodester app (Kittenpick), I copied some source code to its directory, did an add, a commit, and a push, and it stopped working (Application offline). Every app I've made since has gotten "Application offline", so I'm guessing my commit/push broke something?

The Kittenpick diagnostics are a little different from blanktest:

>$ nodester app logs
nodester info Showing logs for: kittenpick
New PID: 16361
chroot_runner
chroot_runner
Process exited cleanly. Dieing.

Not sure what the chroot_runner is telling me there, or if this is even valid output when querying logs.

>$ nodester app info
nodester info Gathering information about: kittenpick
nodester info kittenpick on port 14917 running: true (pid: 16361)
nodester info gitrepo: git@nodester.com:/node/git/REMOVED.git
nodester info appfile: server.js

Notice how this one has a pid.

>$ nodester app start
nodester info Attemping to start app: kittenpick
nodester ERROR Fatal Error! API Response: {"status":"failure - application already running."}
Reason: HTTP Error 408 returned.

Despite its claim that the app is running, kittenpick.nodester.com comes back with "Application offline".

So that's where I'm at (pretty much dead in the water). It's clear that I've broken something, but I'm not sure what to do to fix or even further diagnose the problem. I'll provide any further info as needed.

Thank you.