Hey Hexparrot, would you be interested in letting me test your newest ISO(s)? I can run multiple VM's and run different tests with different setups etc and I really enjoy MineOS. So trying out the newest setup would be awesome.
Hey Hexparrot, would you be interested in letting me test your newest ISO(s)? I can run multiple VM's and run different tests with different setups etc and I really enjoy MineOS. So trying out the newest setup would be awesome.
Psst... it's a secret, but the newest version is on the homepage of the MineOS website: http://minecraft.codeemo.com/
okay so, it seems like ive downloaded the server files just fine and updated everything through the admin page but whenever i try to start the server the status doesn't stop showing 'down' and am unable to connect to my servers, am i just needing to wait for you to update mineos itself or is there a fix for this?
I dont mean to go on but looking at all the steps you are saying need to be taken have I done something wrong?
The world was created as 1.2. Tried to use admin to update which failed. I FTP'd over the 1.3 minecraft_server.jar. Logged in with 1.3 Minecraft and am playing happily.
Have I messed anything else up in the mineos admin page (backup etc?) or am I just lucky it all seemingly works?
My steps are certainly not required for all this (in fact, an existing world with update server files will work just fine)
My steps provided are for educational/functional use, to see how command line can be used to do--everything. The natural steps would be to just 'create' a bukkit server, etc . But the steps I outlined show how one need not be tied to it, and can use CLI to adjust the settings of their server.
i belive it sets a limit on how much memory the server can use
More specifically, it sets the initial (xms) and maximum (xmx) heap size of the java instance, which is precisely how much memory the server can use (Minecraft server)
okay so, it seems like ive downloaded the server files just fine and updated everything through the admin page but whenever i try to start the server the status doesn't stop showing 'down' and am unable to connect to my servers, am i just needing to wait for you to update mineos itself or is there a fix for this?
Try 'force stop servers' from the server page. Minecraft doesnt handle multiple java instances well, and this might have happened. Force stop servers will close all instances so you can start one up properly with the start button.
okay so, it seems like ive downloaded the server files just fine and updated everything through the admin page but whenever i try to start the server the status doesn't stop showing 'down' and am unable to connect to my servers, am i just needing to wait for you to update mineos itself or is there a fix for this?
No update to MineOS should be necessary for the new 1.3 MC or Bukkit servers to work. I'd recommend taking a look at the server log to see if there are clues there. The problem may be self-evident.
updated to recent mineos,
updated the downloads paths...
updated the minecraft_server.jar etc
created a fresh 1.3 world through webUI,
copied my 1.2 world into it, and when i try to start the world again,
it shows me a different world. its another spawn and i guess another world.
do i need to use the import/restore progress to get it working?
edit: i tried the "copy the old world to SP mode"-trick, but i cant select my world to convert it over there. my main issue seem to be, that i dont have a converted 1.3 map, to use in my server?
Users and admins dont need to be concerned with converting maps, it will be done automagically. But here are the steps you can do:
a) if you create a fresh world to overwrite, make sure to delete the new '1.3' world /world directory.
:cool.gif: if you decide to use import, be sure to delete the entire /one directory.
To clarify, the new updated ISOs and the new mineos.tcz update files are not essential to getting an existing world to work with Pure 1.3/Bukkit 1.3
There are many features I have created in the past few weeks, and there are a few problems that have been introduce by rewrite, but the 1.28.11 ISO is 100% ready and capable of playing Beta 1.3 worlds.
Many changes have occurred recently (along with my update) so it seems like my updates are 'resolving' these issues, and people 1.28.11 are left in the dust--this is not the case.
The biggest, most significant changes to the Minecraft hosting world (regarding MineOS) is the updating of the 'uservars' file. With updated URLS in uservars, you can see how a completely configured 1.2 world will work with 1.3 with no additional steps.http://www.minecraftforum.net/viewtopic.php?f=10&t=115788&view=unread#p2766206
True, some of the instructions I've been posting recently will not be relevant--but a working server is a working server--"if it ain't broke, dont break it"
That said, I think the latest updates are making my troubleshooting process much easier, and I look forward to being able to guilt-free consciously encourage you all to update.
Side note: things like chunk repair are now broken with beta 1.3 until the checkworld.py by sk89 is updated (if it is updated). Backup and restore and backtrack STILL WORK, but in this case, you do not want to backup to 1.2 restore points for obvious reasons.
Try 'force stop servers' from the server page. Minecraft doesnt handle multiple java instances well, and this might have happened. Force stop servers will close all instances so you can start one up properly with the start button.
tried that, didnt work :sad.gif:
executing command: cgi-bin/server.cgi?command=start&world=two&argument=
{'world': 'two', 'command': 'start'} starting up world...
using port: 25565
world two: down
Is that 64-bit version going to be ready soon? I only ask because in the next day or two, I'll have the opportunity to actually be in physical proximity with my server, which makes it an opportune time to change things.
If you're looking for someone to help on the design of the web admin page, you can contact me :smile.gif: you can view my work at www.therevtastic.com.
Rollback Post to RevisionRollBack
"We have a dream that one day people will be judged not by the content of their character but by how many evil planets they have exploded."
http://192.168.1.xxx:8080? or .8080
:8080 is the correct one.
Also, the web-ui doesnt work if you didnt do ./20_passwords.sh---set the HTTP password (second one), and follow it up with a ./90_reboot_sudo.sh
Psst... it's a secret, but the newest version is on the homepage of the MineOS website: http://minecraft.codeemo.com/
:biggrin.gif: <3
Or, if you must cheat: http://minecraft.codeemo.com/mineos.iso
My steps are certainly not required for all this (in fact, an existing world with update server files will work just fine)
My steps provided are for educational/functional use, to see how command line can be used to do--everything. The natural steps would be to just 'create' a bukkit server, etc . But the steps I outlined show how one need not be tied to it, and can use CLI to adjust the settings of their server.
More specifically, it sets the initial (xms) and maximum (xmx) heap size of the java instance, which is precisely how much memory the server can use (Minecraft server)
Try 'force stop servers' from the server page. Minecraft doesnt handle multiple java instances well, and this might have happened. Force stop servers will close all instances so you can start one up properly with the start button.
Import I think is the easiest, but thats just me. http://codeemo.com/mantis/view.php?id=15
Users and admins dont need to be concerned with converting maps, it will be done automagically. But here are the steps you can do:
a) if you create a fresh world to overwrite, make sure to delete the new '1.3' world /world directory.
:cool.gif: if you decide to use import, be sure to delete the entire /one directory.
There are many features I have created in the past few weeks, and there are a few problems that have been introduce by rewrite, but the 1.28.11 ISO is 100% ready and capable of playing Beta 1.3 worlds.
Many changes have occurred recently (along with my update) so it seems like my updates are 'resolving' these issues, and people 1.28.11 are left in the dust--this is not the case.
The biggest, most significant changes to the Minecraft hosting world (regarding MineOS) is the updating of the 'uservars' file. With updated URLS in uservars, you can see how a completely configured 1.2 world will work with 1.3 with no additional steps. http://www.minecraftforum.net/viewtopic.php?f=10&t=115788&view=unread#p2766206
True, some of the instructions I've been posting recently will not be relevant--but a working server is a working server--"if it ain't broke, dont break it"
That said, I think the latest updates are making my troubleshooting process much easier, and I look forward to being able to guilt-free consciously encourage you all to update.
Side note: things like chunk repair are now broken with beta 1.3 until the checkworld.py by sk89 is updated (if it is updated). Backup and restore and backtrack STILL WORK, but in this case, you do not want to backup to 1.2 restore points for obvious reasons.
using an older, non virtualbox 4.0 version?
http://minecraft.codeemo.com/config_adminpy.html
Though it is discussing how to use admin_console.py, the functions are exactly those of the web-ui
tried that, didnt work :sad.gif: