those who want new versions might not have as perfect a conversion experience. If it ends up with people losing worlds and other complications
mostly unrelated, but made me think of a feature idea for the webUI: upload/download the word folder (zipped probably i think) via the web UI. So you could from a browser, download the current world, and upload a zipped world folder to load to the server. especially valuable for migrating servers/machines/mineOS versions. less ftp the better in my opinion.
those who want new versions might not have as perfect a conversion experience. If it ends up with people losing worlds and other complications
mostly unrelated, but made me think of a feature idea for the webUI: upload/download the word folder (zipped probably i think) via the web UI. So you could from a browser, download the current world, and upload a zipped world folder to load to the server. especially valuable for migrating servers/machines/mineOS versions. less ftp the better in my opinion.
in ways, I'm a fan of FTP. Firstly, its just downright designed better for file transfers. So especially with world zip/tars about 30+MB, doing that through a HTML form is really not ideal. I think for convention and for safety, FTP is the best option
I have created a new page--the MineOS tutorials page, which will get filled in as I change my endless supply of screenshots into well worded works of art.
For those of you eagerly awaiting, the hey0 tutorial is up and running--alas, you must download the new ISO in order to take advantage of the tutorial I have created. I have also created a "Updating your files from a new MineOS release". This is an informational and essential guide you'll need to use once your servers become full-production servers and not just for tinkering around. I highly advise you to read this, even if you're starting a brand new (virtual) server.
This is the thing i get when i install it i think this is why it wouldn't work please help me
The error reports you're out of disk space. The most likely cause of this is not that you're actually out of space, but that you might have mistyped the size of your partition in this step.
Make sure it follows the format: +xxxxM (e.g., '+4000M' ) including the plus sign AND the upper case M. Otherwise, fdisk (the partition creator) will mis-allocate the partitions. Your partition size must be at least 60M, plus the space for the worlds and the backups, so be generous, like '+5120M' for 5GB or etc.
Hey, what do I do if I forgot my ssh password? =D
Do I have to setup the server all over again?
Hmm. Well, you don't *have* to, if you skip boot straight from the disk using no boot code (no 'tce=xda1). Then you can mount the hard drive and reset the password like this:
Server files must be downloaded before worlds can be created.
Run 'Update' to download most recent minecraft_server.jar
I have no idea what's going wrong. I've reinstalled multiple times. I've increased the memory of the partition, as well as the ram accessible. I even manually placed the minecraft-server.jar into the partition, but so far nothing's working. The .jar file created a completely different error message.
I'm stuck, and I have no idea what to do next.
Thanks for any help.
I don't know what the problem is but whenever, I shutdown my computer and the virtual OS and I login the next day I lose my player data, I have to keep reverting to a backup. I thought it was a mistake at first, but this has happened twice already.
Server files must be downloaded before worlds can be created.
Run 'Update' to download most recent minecraft_server.jar
--Joe
That's definitely an issue I haven't seen before, but luckily theres a number of things we can do to verify whats going on.
The first test we can try is: once you click 'update' and it verifies the files are downloaded, connect via FTP. Does the minecraft_server.jar exist there? If not, it means the MC_PATH in /usr/games/minecraft/admin.sh might not be setting properly.
To find out, reboot your server and boot without a boot code (no tce=sda1 or tce=hda1). This will load the whole OS into RAMDISK (which means the MC_PATH is /usr/games/minecraft/ram-worlds). Try the update and check the FTP thing here again. If the file properly shows up, we know the problem was HD-related, likely during the ./setup_server.sh script. That means somewhere in step 2 is where the problem is occurring for you.
Also, if you want to try too, while youre actually using a bootcode (tce=xda1), type in 'cat /usr/games/minecraft/admin.sh | grep "^MC_PATH"
if used with the bootcode, it should return MC_PATH=/mnt/sda1/minecraft
try these out and we should be able to root out the prob!
I don't know what the problem is but whenever, I shutdown my computer and the virtual OS and I login the next day I lose my player data, I have to keep reverting to a backup. I thought it was a mistake at first, but this has happened twice already.
You lose your player data? or you lose your world data?
If youre ONLY losing player data, it means that you are either a) not stopping the world 'gracefully', with the stop button or :cool.gif: it means youre doing your backups while your player is logged in.
Minecraft saves worldchunks to disk pretty regularly, but it ONLY saves player data when the player disconnects (and this seems to be the case even with "save-all"). If your world data persists, but your player inventory doesnt, this is the issue.
If you're losing world changes too, it means either you're a) not stopping the world gracefully or :cool.gif: i cant think of another thing. Are you hitting 'backup' and then just shutting it down? (thats a perfectly sensible assumption--i dont know why notch designed it this way)
Nice distro! Perhaps you can add a simple way to setup ssl with authentic certs in the web gui?
I'm fairly certain I can find a way to make https:// work with an ssl cert, I'll have to look into it. However, theres a few things im concerned about before I think about adding this functionality (even if non compulsory).
When signing in with a self-signed cert, many browsers like chrome and FF get all red and warny. This would probably make most most users drop :brick:. ON the other hand, if youre talking about a real-live authentic cert....hmm. Well, i'll have to see about how easy that is to setup as a post-installation tutorial.
The first test we can try is: once you click 'update' and it verifies the files are downloaded, connect via FTP. Does the minecraft_server.jar exist there? If not, it means the MC_PATH in /usr/games/minecraft/admin.sh might not be setting properly.
Test one: It doesn't. the FTP directory remains empty.
Quote from hexparrot »
To find out, reboot your server and boot without a boot code (no tce=sda1 or tce=hda1). This will load the whole OS into RAMDISK (which means the MC_PATH is /usr/games/minecraft/ram-worlds). Try the update and check the FTP thing here again. If the file properly shows up, we know the problem was HD-related, likely during the ./setup_server.sh script. That means somewhere in step 2 is where the problem is occurring for you.
Test two: The FTP directory remains empty.
Quote from hexparrot »
Also, if you want to try too, while youre actually using a bootcode (tce=xda1), type in 'cat /usr/games/minecraft/admin.sh | grep "^MC_PATH"
if used with the bootcode, it should return MC_PATH=/mnt/sda1/minecraft
try these out and we should be able to root out the prob!
Test three: This does in fact work. I get the result you have above.
Another odd (but possibly unrelated) bit - My passwords reset to the default at some point. I know I had them set as something different.
Backing up while players are on seemed to be the issue. Does that mean that I cannot back up the server while players are on? Even if it is like an automatic scheduled back up?
Backing up while players are on seemed to be the issue. Does that mean that I cannot back up the server while players are on? Even if it is like an automatic scheduled back up?
Player data isn't saved (to disk) until the player disconnects/is disconnected. This is the design of the official Minecraft server jar itself, which I cannot override. Sensibly, 'save-all' (the minecraft server command) would do this: save presently-logged-on players data to disk so it may be backed up. However, this just is not the case and I may even tweet it to Notch or something to see if this is a deliberate design he intends to keep.
From some informal testing I did, I found that nearly nothing can force the Minecraft server to update the player data--the literal data committed to disk: not hitting escape (a la 'saving world..'), not dying, not save-all, nothing. Just kicking the player or the player disconnecting. Once one of those two things happen, then the player's file gets modified (timestamp).
The ramifications of this design (flaw?) shouldn't be THAT severe, however. But if your server isn't running 24/7, it means you need to do just one thing: hit stop & backup before you shut down your Virtual Machine.
edit: to reiterate--using the 'backup' button will ALWAYS properly back up the world, in ALL cases. It's only player inventory that is volatile due to this design.
mostly unrelated, but made me think of a feature idea for the webUI: upload/download the word folder (zipped probably i think) via the web UI. So you could from a browser, download the current world, and upload a zipped world folder to load to the server. especially valuable for migrating servers/machines/mineOS versions. less ftp the better in my opinion.
in ways, I'm a fan of FTP. Firstly, its just downright designed better for file transfers. So especially with world zip/tars about 30+MB, doing that through a HTML form is really not ideal. I think for convention and for safety, FTP is the best option
I'm definitely going to use this for my personal server and recommend it to my friends who host out of their homes.
Well done :smile.gif:
Trusted and Established Minecraft Server Hosting since Alpha in 2010. Minecraft Server Host: www.minecraftserverhost.net
Test Servers: test.minecraft.ms | east.minecraft.ms | central.minecraft.ms | west.minecraft.ms
I am a representative of Minecraftserverhost.net
http://minecraft.codeemo.com/tutorials.html
For those of you eagerly awaiting, the hey0 tutorial is up and running--alas, you must download the new ISO in order to take advantage of the tutorial I have created. I have also created a "Updating your files from a new MineOS release". This is an informational and essential guide you'll need to use once your servers become full-production servers and not just for tinkering around. I highly advise you to read this, even if you're starting a brand new (virtual) server.
Any other comments or questions, I'll be here.
EnviousHost MINECRAFT SERVERS - CHEAP - [FREE MUMBLE] [FREE WEBHOSTING] [ONE CLICK PLUGINS]
The error reports you're out of disk space. The most likely cause of this is not that you're actually out of space, but that you might have mistyped the size of your partition in this step.
http://minecraft.codeemo.com/images/ss/mc-3.png
Make sure it follows the format: +xxxxM (e.g., '+4000M' ) including the plus sign AND the upper case M. Otherwise, fdisk (the partition creator) will mis-allocate the partitions. Your partition size must be at least 60M, plus the space for the worlds and the backups, so be generous, like '+5120M' for 5GB or etc.
I uploaded the tutorial for setting up hey0 here: http://minecraft.codeemo.com/config_hey0.html
heres the tut: http://minecraft.codeemo.com/config_restore.html
Do I have to setup the server all over again?
Hmm. Well, you don't *have* to, if you skip boot straight from the disk using no boot code (no 'tce=xda1). Then you can mount the hard drive and reset the password like this:
((mounting the hard drive))
I think that should do the trick.
I've been having trouble getting this working!
I'm installing using VirtualBox on Ubuntu, following the tutorial exactly.
The install seems to work just fine, no errors, no hang-ups.
But when I get to the webadmin page, I can't get it to update the server files.
I click update server file, and it reads:
Then I click create, and it reads:
I have no idea what's going wrong. I've reinstalled multiple times. I've increased the memory of the partition, as well as the ram accessible. I even manually placed the minecraft-server.jar into the partition, but so far nothing's working. The .jar file created a completely different error message.
I'm stuck, and I have no idea what to do next.
Thanks for any help.
--Joe
That's definitely an issue I haven't seen before, but luckily theres a number of things we can do to verify whats going on.
The first test we can try is: once you click 'update' and it verifies the files are downloaded, connect via FTP. Does the minecraft_server.jar exist there? If not, it means the MC_PATH in /usr/games/minecraft/admin.sh might not be setting properly.
To find out, reboot your server and boot without a boot code (no tce=sda1 or tce=hda1). This will load the whole OS into RAMDISK (which means the MC_PATH is /usr/games/minecraft/ram-worlds). Try the update and check the FTP thing here again. If the file properly shows up, we know the problem was HD-related, likely during the ./setup_server.sh script. That means somewhere in step 2 is where the problem is occurring for you.
Also, if you want to try too, while youre actually using a bootcode (tce=xda1), type in 'cat /usr/games/minecraft/admin.sh | grep "^MC_PATH"
if used with the bootcode, it should return MC_PATH=/mnt/sda1/minecraft
try these out and we should be able to root out the prob!
You lose your player data? or you lose your world data?
If youre ONLY losing player data, it means that you are either a) not stopping the world 'gracefully', with the stop button or :cool.gif: it means youre doing your backups while your player is logged in.
Minecraft saves worldchunks to disk pretty regularly, but it ONLY saves player data when the player disconnects (and this seems to be the case even with "save-all"). If your world data persists, but your player inventory doesnt, this is the issue.
If you're losing world changes too, it means either you're a) not stopping the world gracefully or :cool.gif: i cant think of another thing. Are you hitting 'backup' and then just shutting it down? (thats a perfectly sensible assumption--i dont know why notch designed it this way)
I'm fairly certain I can find a way to make https:// work with an ssl cert, I'll have to look into it. However, theres a few things im concerned about before I think about adding this functionality (even if non compulsory).
When signing in with a self-signed cert, many browsers like chrome and FF get all red and warny. This would probably make most most users drop :brick:. ON the other hand, if youre talking about a real-live authentic cert....hmm. Well, i'll have to see about how easy that is to setup as a post-installation tutorial.
Thanks for the idea, i'll look right into it
Test one: It doesn't. the FTP directory remains empty.
Test two: The FTP directory remains empty.
Test three: This does in fact work. I get the result you have above.
Another odd (but possibly unrelated) bit - My passwords reset to the default at some point. I know I had them set as something different.
Thanks for the help so far!
--Joe
Player data isn't saved (to disk) until the player disconnects/is disconnected. This is the design of the official Minecraft server jar itself, which I cannot override. Sensibly, 'save-all' (the minecraft server command) would do this: save presently-logged-on players data to disk so it may be backed up. However, this just is not the case and I may even tweet it to Notch or something to see if this is a deliberate design he intends to keep.
From some informal testing I did, I found that nearly nothing can force the Minecraft server to update the player data--the literal data committed to disk: not hitting escape (a la 'saving world..'), not dying, not save-all, nothing. Just kicking the player or the player disconnecting. Once one of those two things happen, then the player's file gets modified (timestamp).
The ramifications of this design (flaw?) shouldn't be THAT severe, however. But if your server isn't running 24/7, it means you need to do just one thing: hit stop & backup before you shut down your Virtual Machine.
edit: to reiterate--using the 'backup' button will ALWAYS properly back up the world, in ALL cases. It's only player inventory that is volatile due to this design.