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.

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

Servers disappearing hours after creation and use #243

Closed
Jhereg10 opened this Issue Jun 6, 2017 · 9 comments

Comments

Projects
None yet
2 participants
@Jhereg10

Jhereg10 commented Jun 6, 2017

Please excuse if I'm posting this in the wrong spot. Also advise if there are log files I should post.

Upgraded unRAID to 6.3.5. Before reboot but after update, I found that my MineOS Node docker's servers had all disappeared from the GUI after about a month of uninterrupted use.

Verified file structure was still there, files themselves are still there, but GUI refuses to "see" any servers.

Created two test servers, which worked. Copied files from the previously working server to the new folders, and it worked fine yesterday. Logged in today to GUI and again, all servers have disappeared.

Any thoughts or guidance appreciated. Should I attempt uninstalling and reinstalling the docker? Please advise which file would be helpful for diagnosis.

@clowrym

This comment has been minimized.

clowrym commented Jun 6, 2017

This sounds to me like a permission problem in unraid, or a file mapping issue in docker. Can you confirm your unraid folder mappings / File permissions?

@Jhereg10

This comment has been minimized.

Jhereg10 commented Jun 6, 2017

Thanks clowrym.

My games data /var/games/minecraft is mapped to /mnt/user/appdata/minecraft (which lives on cache drive only) with read/write permission.

I'm seeing here is my most recent MineOS log:

USER_NAME not provided; defaulting to "mc"
mc already exists.
2017-06-04 18:44:02,365 CRIT Supervisor running as root (no user in config file)
2017-06-04 18:44:02,365 WARN Included extra file "/etc/supervisor/conf.d/mineos.conf" during parsing
2017-06-04 18:44:03,307 INFO RPC interface 'supervisor' initialized
2017-06-04 18:44:03,308 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2017-06-04 18:44:03,308 INFO supervisord started with pid 1
2017-06-04 18:44:04,329 INFO spawned: 'mineos' with pid 10
2017-06-04 18:44:05,331 INFO success: mineos entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-06-04 20:51:52,660 CRIT reaped unknown pid 96)
2017-06-04 20:51:53,661 CRIT reaped unknown pid 97)
2017-06-04 20:58:52,407 CRIT reaped unknown pid 187)
2017-06-04 20:58:52,407 CRIT reaped unknown pid 188)
2017-06-04 21:05:09,603 CRIT reaped unknown pid 36)
2017-06-04 21:05:09,603 CRIT reaped unknown pid 37)
2017-06-04 21:07:25,718 CRIT reaped unknown pid 320)
2017-06-04 21:07:25,718 CRIT reaped unknown pid 321)
2017-06-04 21:17:18,534 CRIT reaped unknown pid 445)
2017-06-04 21:17:18,534 CRIT reaped unknown pid 446)

@Jhereg10

This comment has been minimized.

Jhereg10 commented Jun 6, 2017

After some further review, I think you are right that it has to do with my cache drive / appdata folder mapping. Going to tweak this further by moving the folder and folder mapping somewhere else temporarily.

@Jhereg10

This comment has been minimized.

Jhereg10 commented Jun 6, 2017

Looks like the minecraft folders have the following permissions:

For archive, backup, profiles, and servers
drwxrwxr-x 1 nobody users

For import
drwxrwxrwx 1 nobody users

@clowrym

This comment has been minimized.

clowrym commented Jun 6, 2017

I've had to Change ownership to 1000:1000 on all my Minecraft folder's in order to have everything work. I'm not sure why this is, but neither nobody:users, or root:root worked with my set up.

I currently have everything from the /mnt/cache/appdata/Minecraft foolder down as 👍
drwxrwxr-x 1 1000 1000
The log looks identical to mine.

@Jhereg10

This comment has been minimized.

Jhereg10 commented Jun 6, 2017

Thanks, I'll give that a shot.

@Jhereg10

This comment has been minimized.

Jhereg10 commented Jun 6, 2017

That appears to have worked. Let me play around a bit and see if it stays working. 👍

@clowrym

This comment has been minimized.

clowrym commented Jun 6, 2017

Keep in mind that everytime you create, or add a new server, you will have to change ownership again!

@Jhereg10

This comment has been minimized.

Jhereg10 commented Jun 8, 2017

Thank you. Looks like this has indeed resolved the issue. Much obliged.

@Jhereg10 Jhereg10 closed this Jun 8, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment