Unable to start app on locally hosted nodester - issues related to unmounting during the tearDown and setupUnionFS

40 views
Skip to first unread message

JimiB

unread,
Jun 3, 2012, 4:24:57 AM6/3/12
to node...@googlegroups.com
I've managed to set up nodester running on my own host at Amazon EC2.

I can:

1) Create a new app (warns that I seem to have cloned an empty git repo)
2) Init an app (but the .git folder doesn't get created for some reason and I have to do that bit manually - not a real problem right now)

The above aren't a problem, but thought worth mentioning in case it had an impact on the main problem I'm having.

Having sorted out my local git repo I'm then able to push the changes to Nodester, this appears to work correctly and I see a message through my terminal about syncing repo with chroot.
The status returned is 'Unable to restart' (Maybe this is a clue, shouldn't it be 'Unable to start')

Logging into the server to investigate I find error messages related to being unable to umount a set of directories: (apologies for posting so much code!)

Writing config data: /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_rw/.nodester/config.json
lib.exec_array exit: 1 - Error: Command failed: umount: /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_chroot/dev: not found
sudo umount /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_chroot/dev stderr: umount: /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_chroot/dev: not found
lib.exec_array exit: 1 - Error: Command failed: umount: /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_chroot/proc: not found
sudo umount /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_chroot/proc stderr: umount: /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_chroot/proc: not found
tear_down done
lib.exec_array exit: 1 - Error: Command failed: umount: /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_chroot: not mounted
sudo umount /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_chroot stderr: umount: /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_chroot: not mounted
lib.exec_array exit: 1 - Error: Command failed: umount: /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_pre_chroot/rw: not mounted
sudo umount /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_pre_chroot/rw stderr: umount: /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_pre_chroot/rw: not mounted
lib.exec_array exit: 1 - Error: Command failed: umount: /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_pre_chroot/app/app: not mounted
sudo umount /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_pre_chroot/app/app stderr: umount: /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_pre_chroot/app/app: not mounted
lib.exec_array exit: 1 - Error: Command failed: umount: /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_pre_chroot/os: not mounted
sudo umount /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_pre_chroot/os stderr: umount: /app/jimib/8-e0637cb80f0e660fe133a308f86eb9ad_pre_chroot/os: not mounted
Error setting up unionfs mounts

It appears that Nodester expects a certain set of directories to exist but they don't:
{repo_id}_chroot/dev
{repo_id}_chroot/proc

But I do see:
{repo_id}_chroot/app
{repo_id}_chroot/os
{repo_id}_chroot/rw

Also, it seems to suggest that Nodester expects these directories to have already been mounted, but as they don't exist I would have expected similar warnings when Nodester attempted to mount these directories, but it didn't. The rest of the log (except for the warning of the empty git repo) was clean.

Any pointers would be appreciated, I've got so far getting this thing running and seem to be falling down now at the last hurdle.

J



Chris Matthieu

unread,
Jun 4, 2012, 9:59:29 AM6/4/12
to node...@googlegroups.com
Jimi,

There is a set of sandbox files not in the repo.  I'll get them compressed for download tonight.

Regards,
Chris

James Bailey

unread,
Jun 4, 2012, 12:02:37 PM6/4/12
to node...@googlegroups.com
Thank you Chris.

Chris Matthieu

unread,
Jun 6, 2012, 1:29:37 AM6/6/12
to node...@googlegroups.com
Hi Jimi,

We have zipped up our sandbox directory to distribute.  You can download it from http://nodester.com/sandbox.tar.gz or find it in the repo under the public directory.  You will need to unzip this directory and update your config.js node_base_folder: '', to reference this unzipped directory.  New apps start with this sandbox as the base chroot directory.

Let us know if you have any questions.

Regards,
Chris

Jimi Bailey

unread,
Jun 6, 2012, 2:35:01 AM6/6/12
to node...@googlegroups.com
Great!

I'll have a play this morning.

Thank you

J

Chris Matthieu

unread,
Jun 6, 2012, 8:37:10 AM6/6/12
to node...@googlegroups.com
BTW, There is a great installation discussion occurring at https://github.com/nodester/nodester-installer/issues/8. You may want to join in there too.

-Chris 

Sent from my iPad
Reply all
Reply to author
Forward
0 new messages