pwAdmin stopped working :/

Hey peopple, i'm new to this community and in server creation in general.I finally managed to install hrace009's server on VBOX and i got it running all well, pwAdmin set up etc. I closed my computer then opened the server again etc etc and when i tried to access pwAdmin on my browser it just loaded endlessly, nothing more. And yes, i did use ./tomcat_start.sh. Second reason i'm making this thread is to ask for help if anyone is patient and helpful enough to guide me, because i have ENDLESS questions that can't fit in one thread ( that would be a big mess)If anyone wants to give me some help feel free to request my skype / msn!
Ty in advance!(is something blocking my 8080 port? how can i tell? because accesing 192.168.0.10/pw is possible yet :8080 is not. And even if i plainly try to acess the IP on that port instead of getting random error, i get that endless load)

type ifconfig and make sure eth0 is still reading as 192.168.0.10 if its not then you have to go into your interfaces.

nano /etc/network/interfaces and change the system to static and not dhcp

and change the ip to 192.168.0.10 and also make sure your resolv.conf is also reading your router ip which should be something like 192.168.0.1

if your rounter runs 192.168.1.254 then you need to change all the ip's of each file to a 192.168.1.10

i made a thread based on hrace009 vbox release check that out.

hope this helps.

Quote:

---

Originally Posted by 88supra86

type ifconfig and make sure eth0 is still reading as 192.168.0.10 if its not then you have to go into your interfaces.

nano /etc/network/interfaces and change the system to static and not dhcp

and change the ip to 192.168.0.10 and also make sure your resolv.conf is also reading your router ip which should be something like 192.168.0.1

if your rounter runs 192.168.1.254 then you need to change all the ip's of each file to a 192.168.1.10

i made a thread based on 343 vbox release check that out.

hope this helps.

---

Ty for the uber fast reply but i am kinda confused on what you said.Am gonna try the part of witch i understand XD uhm, i access my router from 192.168.1.1 if that matters?

Quote:

---

Originally Posted by 88supra86

type ifconfig and make sure eth0 is still reading as 192.168.0.10 if its not then you have to go into your interfaces.

nano /etc/network/interfaces and change the system to static and not dhcp

and change the ip to 192.168.0.10 and also make sure your resolv.conf is also reading your router ip which should be something like 192.168.0.1

if your rounter runs 192.168.1.254 then you need to change all the ip's of each file to a 192.168.1.10

i made a thread based on 343 vbox release check that out.

hope this helps.

---

Correction, my release is GENERAL -- not specifically VBox (or any VM for that matter)... It is actually 'intended' to be installed on a physical machine, but will work just fine in any VM (had to install in a VM for video, not like I was gonna sit there with a camcorder and record myself installing it to a physical machine LOL)

:thumbup:



But yes..., If you're having possible networking issues you may also try reading this:

http://forum.ragezone.com/f695/absol...tcp-ip-709746/

Quote:

---

Originally Posted by 343

Correction, my release is GENERAL -- not specifically VBox (or any VM for that matter)... It is actually 'intended' to be installed on a physical machine, but will work just fine in any VM (had to install in a VM for video, not like I was gonna sit there with a camcorder and record myself installing it to a physical machine LOL)

:thumbup:



But yes..., If you're having possible networking issues you may also try reading this:

http://forum.ragezone.com/f695/absol...tcp-ip-709746/

---

I have already read ur excelent guide yet i dont seem to be able to solve my problem XD i thought the 192.168.0.1 is the ip of the LAN the server uses to connect to my computer XD ( mi noob?)

I'm hoping maybe hrace (or someone else using his release) can chime in, because I don't and never have used his release (I have and made my own release, based off of a really old one)... It may be something specific to his release ???

Quote:

---

Originally Posted by 343

I'm hoping maybe hrace (or someone else using his release) can chime in, because I don't and never have used his release (I have and made my own release, based off of a really old one)... It may be something specific to his release ???

---

i really don't know, but i am kind of disapointed. I'm newb to this and i was so happy to make it work and now GRRRR it doesn't! Can you explain me what 192.168.0.1 stands for? i can find all these addresses but i dont even know what they mean.

When I used his release forever ago the networking was a bit weird simply because the DNS was set statically and other networking stuff all being static. To make it work correctly you'd need to fix all of that and by the time all that is done you could've done a clean install of 343's release (I quickly moved away from that after ronny posted his guide as before that there wasn't really one and I was still mostly newish to PW so I had no damn clue what I needed to do to get it to work. Now I basically can do it with my eyes closed)

Quote:

---

Originally Posted by das7002

When I used his release forever ago the networking was a bit weird simply because the DNS was set statically and other networking stuff all being static. To make it work correctly you'd need to fix all of that and by the time all that is done you could've done a clean install of 343's release (I quickly moved away from that after ronny posted his guide as before that there wasn't really one and I was still mostly newish to PW so I had no damn clue what I needed to do to get it to work. Now I basically can do it with my eyes closed)

---

So basically, vbox isn't the ideal place for setting up a server? i mean that way. And i initialy went for 343's package but (poor me) i thought it lacked guidance on installation and all that for complete newbies like me

from what i just saw you sait your router access is 192.168.1.1 you need to change your resolv.conf to that nano /etc/resolv.conf

then you need to go through each file and change the ip's to 192.168.1.10

change your VBOX Network Interface /etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
address YOUR VBOX IP
netmask YOUR NETMASK
network 192.168.0.0 <<< Always Fill This XXX.XXX.0.0
broadcast YOUR NEWORK BRODCAST
gateway YOUR GATEWAY IP TO INTERNET
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers YOUR DOMAIN IP, IF YOU USE DOMAIN
dns-search YOUR DOMAIN NAME, IF YOU USE DOMAIN

-----------------------------------------------------------------
and don't forget to Replace the IPs with your current addresses except the lines with 0.0.0.0

/PWServer/gacd/gamesys.conf - change ip from 192.168.0.10 to 192.168.1.10
/PWServer/gamed/gmserver.conf - change ip from 192.168.0.10 to 192.168.1.10
/PWServer/gamed/gs.conf - change ip from 192.168.0.10 to 192.168.1.10
/PWServer/gamed/gsrollback.conf - change ip from 192.168.0.10 to 192.168.1.10
/PWServer/gamedbd/cashstat.conf - change ip from 192.168.0.10 to 192.168.1.10
/PWServer/gamedbd/gamesys.conf - change ip from 192.168.0.10 to 192.168.1.10
/PWServer/gdeliveryd/gamesys.conf - change ip from 192.168.0.10 to 192.168.1.10
/PWServer/gfactiond/gamesys.conf - change ip from 192.168.0.10 to 192.168.1.10
/PWServer/glinkd/gamesys.conf - change ip from 192.168.0.10 to 192.168.1.10
/PWServer/logservice/logservice.conf - change ip from 192.168.0.10 to 192.168.1.10
/PWServer/uniquenamed/gamesys.conf - change ip from 192.168.0.10 to 192.168.1.10
/etc/authd.conf - change ip from 192.168.0.10 to 192.168.1.10
/etc/gmopgen.xml - change ip from 192.168.0.10 to 192.168.1.10
/etc/GMserver.conf - change ip from 192.168.0.10 to 192.168.1.10
/etc/hosts - change ip from 192.168.0.10 to 192.168.1.10
/etc/iweb.conf - change ip from 192.168.0.10 to 192.168.1.10

---------- Post added at 10:11 PM ---------- Previous post was at 10:06 PM ----------

Quote:

---

Originally Posted by partendo

So basically, vbox isn't the ideal place for setting up a server? i mean that way. And i initialy went for 343's package but (poor me) i thought it lacked guidance on installation and all that for complete newbies like me

---

his guidance to installation is perfect and strait forward and very easy

Quote:

---

Originally Posted by partendo

So basically, vbox isn't the ideal place for setting up a server? i mean that way. And i initialy went for 343's package but (poor me) i thought it lacked guidance on installation and all that for complete newbies like me

---

No I was saying hrace's release isn't exactly the easiest to use. There is nothing wrong using VirtualBox to run your actual server if you feel like it.

K ty both for your answers, as for the whole IP modification pwadmin worked for me the first 2 hours or so!i even reinstalled the server and it still doesnt work. i suspect sometihng is blocking my 8080 port! and on ipcofig the gateaway is the IP of my router?
Edit: on my resolv.conf i see : nameserver 192.168.0.1 When i change it and click save after i open the server again its set back to normal
btw. supra i added you on msn
And why is the 192.168.0.10 wrong? i can access 192.168.0.10/pw so it dont think the problem hides inside the IP

Ok, so i reinstalled VBOX and the sever a couple of times and i got it working, yet i still need help with the whole IP-network thing, The settings the the default provided by the guide but they have like completely no relation to my network whatsoever ( my gateaway is 192.168.1.1 yet server pwadmin runs fine on 192.168.0.10 -impossible accroding to tcip/ip stuff since they share the same mask- If anyone wants to help me configure it let me know! and supra i'm gonna w8 for you on msn if u still want to help!

for checking the jetty is up and running or not try command netstat -na | grep :8080 <-- if you see 1 or more line as a result then you can access your pwadmin from your desktop. i suggest you use ubuntu for the most compatible as my experience on pw server...