im encountering some new sort of errors since i updated to the recent 1/22 version.
maybe its not important for the main stability, but as they seem new to me, i just report them:
this comes right before the boot has succeeded:
2011-01-23 11:37:47: (configfile.c.1214) base-docroot doesn´t exist: /var/www/httpdocs
2011-01-23 11:37:47: (server.c.620) setting default values failed
httpd: chdir(/var/www/httpsdocs): No such file or directory
edit: this seems to affect my webUI. cant connect to it, which means i cant start any worlds, which means server doenst run
btw. is there any service running which makes it possible to SSH to my machine? on pre 1/17 version this was possible through ip:4200.
did you switch this port to another?
Yes, please definitely report any issues you run into. Though its really weird this would pop up after any update. Ever since 1/18, the only changes that have been made were to the admin.py script, often less than 20 bytes per update (thats all bukkit needs, sometimes).
Ill look into this, but strangely, its just telling me that theres no directory /var/www/httpsdocs....ill look into this.
on a sidenote, never really occurred to me till just now, i think ill add an 'update' button to MineOS for MineOS like i do for server files....strange i never thought of it.
Hey agian, is there any way I can modify the ram usage from 1gig to 3gig without needing to wipe the server, have people on it and don't want some sad folks I know i can start server via putty with more but would be great if i can make by default turn on that way.
Hey agian, is there any way I can modify the ram usage from 1gig to 3gig without needing to wipe the server, have people on it and don't want some sad folks I know i can start server via putty with more but would be great if i can make by default turn on that way.
If you mean starting the minecraft server itself, yeah. Just modify...
/usr/games/minecraft/uservars
The MEM entry in the [defaults] section.
Per server would be nice but it seems to be a shared setting for all servers right now.
I am trying to install No-ip DUC from http://www.no-ip.com, just in case I ever need to reset my modem and the ip changes.
When trying to install it, I found out that the "make" command does not work. It is not installed?
So I tried finding out how to install it and I found out how to install this package using "sudo apt-get install make"
but the apt-get is not installed either.
I am trying to install No-ip DUC from http://www.no-ip.com, just in case I ever need to reset my modem and the ip changes.
When trying to install it, I found out that the "make" command does not work. It is not installed?
So I tried finding out how to install it and I found out how to install this package using "sudo apt-get install make"
but the apt-get is not installed either.
The build environment is not necessary for most peoples needs, thus I have not included it. Of course, one can be easily downloaded.
Tinycorelinux doesnt use apt-get (debian) or yum or zypper or etc. it uses a package manager specifically for tinycore, which (by convention) removes parts like documentation, to provide functional but slim packages.
You can use 'ab' -- the package manager to download 'compiletc.tcz---so type
ab compiletc
and you can download all necessary packages for 'make'ing
I'm not using this myself, though I am running the server under linux, so I thought I'd mention it - I've found increased performance using the -noatime mount option in fstab. It stops the OS writing "last access time" metadata to the disk for each file. Given how many files there are in the world, it speeds up some things, especially world copy/backup, by a helluva lot, and it may be subliminal but I'm noticed a lot less "can't keep up" messages now.
Nice suggestion, havent really thought much about atime much. Though over 'noatime', I'm considering 'relatime' which should at least give me the advantages of reduced atime updates, though a chunk should now never lag behind the modified and created times. 'relatime' i think will be a great compromise, since now atimes will only be changed on chunk changes--which wont even occur that often, due to the delayed save-all nature of the minecraft server.
thus relatime will keep all the atimes current on modified chunks and still avoid the overhead of updating atimes on the hundreds of chunks that are only read!
Ok I might have miss this question and answer, but 29 pages is alot to read threw and might have missed it.
So If I want to run this slick and cool interface on my ubuntu box already going I just need to copy over these files..
/var/www/httpsdocs
/var/www/httpdocs (blank for me)
/usr/games/minecraft
/home/tc
/usr/games/minecraft/
/mnt/(drive)/tce/
Any other I need?
And any certain mods I need installed? Except the standards like ssh and apache(I think you use lighttpd).
PS. I like the minycore setup but not having some of the things I'm used to in ubuntu is killing me.
Ok I might have miss this question and answer, but 29 pages is alot to read threw and might have missed it.
So If I want to run this slick and cool interface on my ubuntu box already going I just need to copy over these files..
/var/www/httpsdocs
/var/www/httpdocs (blank for me)
/usr/games/minecraft
/home/tc
/usr/games/minecraft/
/mnt/(drive)/tce/
Any other I need?
And any certain mods I need installed? Except the standards like ssh and apache(I think you use lighttpd).
PS. I like the minycore setup but not having some of the things I'm used to in ubuntu is killing me.
/usr/games/minecraft
and
/var/www/httpsdocs
would pretty much be all you really need-- /usr/games/minecraft is 100% enough to run these scripts from console, so long as your uservars is also updated for your system.
and then the html files you just have to figure out with your current webserver setup. as i have it, its symlinked, which you can replicate. and make sure you have mod_cgi enabled on your webserver properties and +x on all the py and cgi files.
My PC is not getting an IP remotely similar to that at all and I still can't connect to the vm at all. I'm really tempted to buy a small box to host this on but i'm not really made out of money.
My PC is not getting an IP remotely similar to that at all and I still can't connect to the vm at all. I'm really tempted to buy a small box to host this on but i'm not really made out of money.
What kind of IP address are you getting for your PC then? (i dont need the exact value, even though it wouldnt matter, since youre behind NAT).
I'm getting 67.129.121.xx and the vm is some like 10.200.8.88.
If thats the case, you might end up having to use NAT. Nat isnt nearly as friendly to set up, but probably should still work out ok. Seems that your school network only is willing you/your room one IP (is your computer the only one using your wall-ethernet connection, or is it a router?)
I'm assuming you're plugged right into the wall, and thus the ip 67.129.121 is hard-allocated to that physical room. Thus, youd either a) use a router -- which would put your COMPUTER at a 192.x.x.x and your VMs at 192.x.x.x
or :cool.gif: use NAT in virtualbox, which, from googling--seems like its a hell of a lot of work. a lot lot of work.
On the other hand, while its set up the way it is....are you able to connect to your MC server with the 10.200.8.88 ip?
Check if you can...and maybe then, even all the other people on your network could also too (though those OUTSIDE your network wouldnt be able to).
I can not connect to my VM from my computer and each port gets it's own ip, my roommate's ip is one off from mine or something. So my best bet is to buy a router, seems way easier than nat. Any cheap one should work seeing how I don't even need wireless?
I can not connect to my VM from my computer and each port gets it's own ip, my roommate's ip is one off from mine or something. So my best bet is to buy a router, seems way easier than nat. Any cheap one should work seeing how I don't even need wireless?
correct, a cheap router will be the absolute easiest. Then you can just follow the normal port forwarding tutorial and youre set.
I've got a slight problem with people outside our network connecting.
So I've forwarded port 25565 to my computer's ip address which is static at 192.168.1.150. The ip of the VM however is 192.168.1.7, and while this allows anyone on our network to join the server by using that ip it of course won't allow anyone outside the network to join. So here I used whatismyip.com to find my computer's external ip and gave that to a friend to try, but all he could get was "connecting to server" and it would eventually time out.
Does the port instead need to be forwarded to the VM instead of my computer? If so would it need to be static, and how would I go about doing that?
Ok, so how do I set up a static IP within the OS? I've searched everywhere for how to set up a static IP within tinycorelinux but either everyone knows or no one does it.
Yes, please definitely report any issues you run into. Though its really weird this would pop up after any update. Ever since 1/18, the only changes that have been made were to the admin.py script, often less than 20 bytes per update (thats all bukkit needs, sometimes).
Ill look into this, but strangely, its just telling me that theres no directory /var/www/httpsdocs....ill look into this.
on a sidenote, never really occurred to me till just now, i think ill add an 'update' button to MineOS for MineOS like i do for server files....strange i never thought of it.
If you mean starting the minecraft server itself, yeah. Just modify...
/usr/games/minecraft/uservars
The MEM entry in the [defaults] section.
Per server would be nice but it seems to be a shared setting for all servers right now.
I am trying to install No-ip DUC from http://www.no-ip.com, just in case I ever need to reset my modem and the ip changes.
When trying to install it, I found out that the "make" command does not work. It is not installed?
So I tried finding out how to install it and I found out how to install this package using "sudo apt-get install make"
but the apt-get is not installed either.
I am not sure how to get no-ip duc installed, but it would be nice to know.
This is how they show you to install it.
http://www.no-ip.com/support/guides/upd ... lient.html
The build environment is not necessary for most peoples needs, thus I have not included it. Of course, one can be easily downloaded.
Tinycorelinux doesnt use apt-get (debian) or yum or zypper or etc. it uses a package manager specifically for tinycore, which (by convention) removes parts like documentation, to provide functional but slim packages.
You can use 'ab' -- the package manager to download 'compiletc.tcz---so type
ab compiletc
and you can download all necessary packages for 'make'ing
Nice suggestion, havent really thought much about atime much. Though over 'noatime', I'm considering 'relatime' which should at least give me the advantages of reduced atime updates, though a chunk should now never lag behind the modified and created times. 'relatime' i think will be a great compromise, since now atimes will only be changed on chunk changes--which wont even occur that often, due to the delayed save-all nature of the minecraft server.
thus relatime will keep all the atimes current on modified chunks and still avoid the overhead of updating atimes on the hundreds of chunks that are only read!
So If I want to run this slick and cool interface on my ubuntu box already going I just need to copy over these files..
/var/www/httpsdocs
/var/www/httpdocs (blank for me)
/usr/games/minecraft
/home/tc
/usr/games/minecraft/
/mnt/(drive)/tce/
Any other I need?
And any certain mods I need installed? Except the standards like ssh and apache(I think you use lighttpd).
PS. I like the minycore setup but not having some of the things I'm used to in ubuntu is killing me.
HACKED BY TEAMDOMI!
/usr/games/minecraft
and
/var/www/httpsdocs
would pretty much be all you really need-- /usr/games/minecraft is 100% enough to run these scripts from console, so long as your uservars is also updated for your system.
and then the html files you just have to figure out with your current webserver setup. as i have it, its symlinked, which you can replicate. and make sure you have mod_cgi enabled on your webserver properties and +x on all the py and cgi files.
That would definitely explain it--if your regular PC is getting a 10.x.x.x IP, its def cause your network is rocking NAT.
Thus, it shouldnt matter the IP is 10.x.x.x--as long as its bridged, then that IP should work out just fine.
What kind of IP address are you getting for your PC then? (i dont need the exact value, even though it wouldnt matter, since youre behind NAT).
and what kind of IP is your VM getting?
If thats the case, you might end up having to use NAT. Nat isnt nearly as friendly to set up, but probably should still work out ok. Seems that your school network only is willing you/your room one IP (is your computer the only one using your wall-ethernet connection, or is it a router?)
I'm assuming you're plugged right into the wall, and thus the ip 67.129.121 is hard-allocated to that physical room. Thus, youd either a) use a router -- which would put your COMPUTER at a 192.x.x.x and your VMs at 192.x.x.x
or :cool.gif: use NAT in virtualbox, which, from googling--seems like its a hell of a lot of work. a lot lot of work.
On the other hand, while its set up the way it is....are you able to connect to your MC server with the 10.200.8.88 ip?
Check if you can...and maybe then, even all the other people on your network could also too (though those OUTSIDE your network wouldnt be able to).
correct, a cheap router will be the absolute easiest. Then you can just follow the normal port forwarding tutorial and youre set.
Sorry it was a stupid mistake on my side, didn't press the 'start' button...
Now, I just need to access the 'server.properties'.
I SSH'ed into 'tc@box' but I couldn't find it?
Most likely looking in the wrong place?
Cheers,
Colby
So I've forwarded port 25565 to my computer's ip address which is static at 192.168.1.150. The ip of the VM however is 192.168.1.7, and while this allows anyone on our network to join the server by using that ip it of course won't allow anyone outside the network to join. So here I used whatismyip.com to find my computer's external ip and gave that to a friend to try, but all he could get was "connecting to server" and it would eventually time out.
Does the port instead need to be forwarded to the VM instead of my computer? If so would it need to be static, and how would I go about doing that?