Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

There is already a configuration directory for 'C**'. error on dirty shutdown #39

Open
micpalmia opened this issue Sep 17, 2013 · 1 comment
Open

There is already a configuration directory for 'C**'. error on dirty shutdown #39

micpalmia opened this issue Sep 17, 2013 · 1 comment

Comments

@micpalmia
Copy link
Contributor

From this discussion I discovered that this issue is related to not shutting down correctly the container.

This is what I try to do (following the tutorial):

  • add the path to test in the config file
  • sudo rce-make + rosmake Test
  • rce-master
  • sudo rce-container localhost
  • rce-robot localhost
  • rce-ros debug.cfg

At this point I get various There is already a configuration directory for 'C100'.. After this error, trying to shut everything down and restarting again gives a OSError: [Errno 17] File exists: '/opt/rce/container/rootfs/opt/rce/packages/test' Could not setup the rce environment.
@micpalmia
Copy link
Contributor Author

In order to solve the first error, the configuration and data files previously created have to be manually removed. These files can be found under /opt/rce/container/data and /opt/rce/container/config. A more useful error message could be served (at least saying where these files are).

The second problem can be solved deleting the test folder from inside /opt/rce/packages in the rce filesystem (i.e. in the /opt/rce/container/rootfs or wherever you installed it)

micpalmia added a commit to micpalmia/rce that referenced this issue Sep 17, 2013
@micpalmia
Improves container error message for easier debugging
9c3584f 
In case the engine is not shut down correctly, config and data
container folders are left in their directories, making it impossible to
execute the same code again after a problematic exit. The new error
message containes the path to the folder where the container
directories reside.

In order to prevent people deleting directories that are still in use,
 a short informative message is also provided.

This addresses but does not solve issue rapyuta-robotics#39
@micpalmia micpalmia mentioned this issue Sep 17, 2013
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@micpalmia