There were several for that IP address, all of which were supposed to be the IP of my local machine.
We changed network configs a few weeks ago and I had a new intranet IP address (192.168.1.131), but hadn't yet used any of the "fake" domains on the new network, so hadn't spotted it. If my localhost's name is 'asimov', I had, amongst others: 172.16.1.33 www.asimov 172.16.1.33 asimov 127.0.0.1 www.localhost 127.0.0.1 localhost Thanks, Stewart On Jul 21, 4:30 pm, Thomas Mueller <[email protected]> wrote: > Hi, > > Do you remember what the /etc/hosts config was? H2 should at least > print a better error message for this case, and I wonder how I can > reproduce the problem. > > Regards, > Thomas > > > > > > > > On Thu, Jul 21, 2011 at 5:24 PM, Stewart <[email protected]> wrote: > > Thomas! You da man! > > > I had already run the testNetwork script (output in 1st post above), > > but when you mentioned /etc/hosts, something clicked. > > > I checked the IP address in the h2 output (172.16.1.33) against my > > current network IP, and they are not the same. > > Then looking in /etc/hosts, there was a rogue config set to > > 172.16.1.33, which should have been my own IP address. > > > Changing /etc/hosts totally fixed it! > > > :-) > > > On Jul 21, 3:23 pm, Thomas Mueller <[email protected]> > > wrote: > >> Hi, > > >> I guess the error message is wrong... Could you check your /etc/hosts > >> file for strange entries, and run this script from the /h2 directory? > > >> ./build.sh testNetwork > > >> Regards, > >> Thomas > > >> On Thu, Jul 21, 2011 at 4:07 PM, Stewart <[email protected]> > >> wrote: > >> > Thanks for the suggestion. > > >> > A friend of mine on Fedora has just done this and it works fine. I'm > >> > on Ubuntu 10.04. > > >> > I don't have the ports blocked. I can bring up Tomcat on port 8082 > >> > just fine, and access it with http. > > >> > So it seems to work in other environments, and other things seem to > >> > work on those ports, leaving me completely baffled. > > >> > On Jul 21, 1:54 pm, Noel Grandin <[email protected]> wrote: > >> >> At the point in time you did a grep the H2 process had terminated, so > >> >> it > >> >> was no longer listening. > > >> >> You need to find out what is running on ports 8082, 9092, 5435 > > >> >> At I guess I would say that you probably have H2 still running in some > >> >> other session. > > >> >> Stewart wrote: > >> >> > I already did (Crtl+F for netstat in post above) > > >> >> > Nothing is running on the required ports. > > >> >> > On Jul 21, 12:27 pm, Noel Grandin <[email protected]> wrote: > >> >> >> Do a netstat to find out what else is running on those ports. > > >> >> >> Stewart wrote: > >> >> >>> Hi Guys, > >> >> >>> Hoping you can help me. > >> >> >>> I am pretty sure that ports 8082, 9092 and 5435 are not already in > >> >> >>> use, yet I can't start h2 on the command line. > >> >> >>> I'm investigating this as part of debugging a maven build, which > >> >> >>> boots > >> >> >>> h2 in order to run database tests, but which just hangs instead. > >> >> >>> Any clues? > >> >> >>> stewart@asimov:~/Downloads/h2/bin$ java -jar h2-1.3.158.jar > >> >> >>> The Web Console server could not be started. Possible cause: > >> >> >>> another > >> >> >>> server is already running athttp://172.16.1.33:8082 > >> >> >>> Root cause: Exception opening port "H2 Console Server > >> >> >>> (http://172.16.1.33:8082)" (port may be in use), cause: "timeout" > >> >> >>> [90061-158] > >> >> >>> The TCP server could not be started. Possible cause: another server > >> >> >>> is > >> >> >>> already running at tcp://172.16.1.33:9092 > >> >> >>> Root cause: Exception opening port "H2 TCP Server > >> >> >>> (tcp://172.16.1.33:9092)" (port may be in use), cause: "timeout" > >> >> >>> [90061-158] > >> >> >>> The PG server could not be started. Possible cause: another server > >> >> >>> is > >> >> >>> already running at pg://172.16.1.33:5435 > >> >> >>> Root cause: Exception opening port "H2 PG Server > >> >> >>> (pg://172.16.1.33:5435)" (port may be in use), cause: "timeout" > >> >> >>> [90061-158] > >> >> >>> Exception in thread "main" org.h2.jdbc.JdbcSQLException: Exception > >> >> >>> opening port "H2 Console Server (http://172.16.1.33:8082)" (port > >> >> >>> may > >> >> >>> be in use), cause: "timeout" [90061-158] > >> >> >>> at > > >> >> >>> org.h2.message.DbException.getJdbcSQLException(DbException.java:329) > >> >> >>> at org.h2.message.DbException.get(DbException.java:169) > >> >> >>> at org.h2.tools.Server.start(Server.java:377) > >> >> >>> at org.h2.tools.Console.runTool(Console.java:230) > >> >> >>> at org.h2.tools.Console.main(Console.java:100) > >> >> >>> ^Cstewart@asimov:~/Downloads/h2/bin$ netstat -an | grep 8082 > >> >> >>> stewart@asimov:~/Downloads/h2/bin$ netstat -an | grep 9092 > >> >> >>> stewart@asimov:~/Downloads/h2/bin$ netstat -an | grep 5435 > >> >> >>> stewart@asimov:~/Downloads/h2/bin$ > >> >> >>> stewart@asimov:~/Downloads/h2$ ./build.sh testNetwork > >> >> >>> Target: testNetwork > >> >> >>> localhost:localhost/127.0.0.1 > >> >> >>> localhost/127.0.0.1 > >> >> >>> localhost/0:0:0:0:0:0:0:1 > >> >> >>> getLocalHost:asimov/172.16.1.33 > >> >> >>> /172.16.1.33 > >> >> >>> byName:/172.16.1.33 > >> >> >>> ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=50146] > >> >> >>> server accepting > >> >> >>> client:/172.16.1.33:50146 > >> >> >>> java.net.SocketTimeoutException: connect timed out > >> >> >>> at java.net.PlainSocketImpl.socketConnect(Native Method) > >> >> >>> at > >> >> >>> java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) > >> >> >>> at > >> >> >>> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) > >> >> >>> at > >> >> >>> java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) > >> >> >>> at > >> >> >>> java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) > >> >> >>> at java.net.Socket.connect(Socket.java:529) > >> >> >>> at org.h2.build.Build.testNetwork(Build.java:701) > >> >> >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > >> >> >>> Method) > >> >> >>> at > > >> >> >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: > >> >> >>> 39) > >> >> >>> at > > >> >> >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp > >> >> >>> l.java: > >> >> >>> 25) > >> >> >>> at java.lang.reflect.Method.invoke(Method.java:597) > >> >> >>> at org.h2.build.BuildBase.invoke(BuildBase.java:241) > >> >> >>> at org.h2.build.BuildBase.runTarget(BuildBase.java:207) > >> >> >>> at org.h2.build.BuildBase.run(BuildBase.java:188) > >> >> >>> at org.h2.build.Build.main(Build.java:31) > >> >> >>> thread is still alive, interrupting > >> >> >>> done > >> >> >>> Done in 8120 ms > >> >> >>> ^C > >> >> >>> stewart@asimov:~/Downloads/h2$ > >> >> >>> stewart@asimov:~/Downloads/h2$ telnet localhost 50146 > >> >> >>> Trying ::1... > >> >> >>> Trying 127.0.0.1... > >> >> >>> telnet: Unable to connect to remote host: Connection refused > >> >> >>> stewart@asimov:~/Downloads/h2$ netstat -an | grep 50146 > >> >> >>> stewart@asimov:~/Downloads/h2$ > > >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups > >> > "H2 Database" group. > >> > To post to this group, send email to [email protected]. > >> > To unsubscribe from this group, send email to > >> > [email protected]. > >> > For more options, visit this group at > >> >http://groups.google.com/group/h2-database?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "H2 Database" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/h2-database?hl=en. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
