tosswald
|
Posted: December 04, 2009 12:45 by tosswald
|
|
Hello, I am trying now to set up the NLG system on a remote server for the challenge time. I made my tests by running the server on the remote computer, and the matchmaker and the client being on my local computer. The tutorial works perfectly, but the server always crashes afterwards. I tried several configurations (sgplan, lazyff, with the example servers and the one we are developing) and I always get the same problem. I am using the 2.2 give tools locally. The logs are not saved either. The most espressive error message is the one I got by using the latest release of the example-nlg-server, with lazyff planner (actually without, as it crashes before). In other cases, I did not always get the java exception. Here is the ouput I get from the server : osswald@labotalc2:~/give2-demo-nlgservers-1.0.3/give2-example-nlgserver$ ./scripts/start-example-nlgserver GIVE NLG server, version null Reading configuration from example-nlgsystem-config.xml... NLG system class: class edu.union.give2.simplenlgservernolandmarks.ExampleNlgSystem [Server 17:45:11.325] Listening on port 3001 [Server 17:45:21.353] Accepted connection for game ID 26, client gets instance on port 3002 [NlgServerInstance 17:45:21.398] Warning: Thread CPU measuring is not supported on this JVM. [NlgServerInstance 17:45:21.398] Server instance running on port 3002 for gameId 26 at Thu Dec 03 17:45:21 GMT+01:00 2009 [NlgServerInstance 17:45:21.398] Accepting connections from matchmaker on port 3002 [Server 17:45:21.501] Listening on port 3001 [NlgServerInstance 17:45:21.503] Accepted connection from matchmaker. [NlgServerInstance 17:45:21.861] Accepting connection from client on port 3002 ... [NlgServerInstance 17:45:21.861] Accepted connection from client. State changed to: WAITING_FOR_CURSOR_UP ok State changed to: JUST_TALKING State changed to: WAITING_FOR_CURSOR_RIGHT State changed to: JUST_TALKING State changed to: WAITING_FOR_CURSOR_LEFT State changed to: JUST_TALKING State changed to: WAITING_FOR_PICTURE_CLICK State changed to: JUST_TALKING State changed to: WAITING_FOR_DOOR_CLICK State changed to: JUST_TALKING ****** TUTORIAL ENDING ****** [NlgServerInstance 17:46:16.855] Server instance was interrupted by the server (InterruptedIO). [Server 17:46:16.856] Port 3002 released, free ports are now: [3002] Exception in thread "Thread-2" java.lang.NullPointerException at edu.union.give2.simplenlgservernolandmarks.ExampleNlgSystem.connectionDisconnected(ExampleNlgSystem.java:92) at give.nlgserver.NlgServerInstance.run(NlgServerInstance.java:272) State changed to: WAITING_FOR_END Does somebody know where it can come from ? Thanks, Tarik |
Error on remote server: server crashes after the tutorial ends
9 posts
Replies: 8 - Last Post: February 05, 2010 13:14
by: Alexander Koller
by: Alexander Koller
showing 1 - 9 of 9
|
Alexander Koller
|
Posted: January 11, 2010 13:33 by Alexander Koller
|
|
Hi, I've just looked at this problem more closely (sorry it took so long), and I'm afraid I can't manage to reproduce it. I have an idea what might be causing it, and have changed the NLG server code to fix the possible bug, but can't test whether it does the job. I'm going to release GIVE 2.2.1, containing the bugfix, this week. Once I've done that, could you please check whether your original setup now works? Cheers, Alexander. |
|
Alexander Koller
|
Posted: February 05, 2010 13:14 by Alexander Koller
|
|
Hi Tarik, I believe I found the source of your bug, and fixed it. The transition from tutorial to main task should be more robust in 2.2.2. Cheers, Alexander. |
|
johannes.braunias
|
Posted: December 04, 2009 18:08 by johannes.braunias
|
|
Can you post your configuration files (matchmaker-config.xml)? I experienced a similar issue where I had "localhost" in the matchmaker config file, because the nlg-server was running on the same machine as the matchmaker. But the client was running on a different machine and was told from the matchmaker the "localhost" address (for the nlg-server). – Which the client could only resolve to its own address. |
|
tosswald
|
Posted: December 07, 2009 14:26 by tosswald
|
|
Hi, As for me, it is obvious that the client is well connected to the nlg-server, as you can see in the output (state messages from the tutorial). Anyway, here is my matchmaker-config file : <?xml version="1.0"?> <matchmaker port="3000" reporting-port="2999" web-port="8080"> <!-- <skip-questionnaire /> --> <!-- <skip-tutorial /> --> <worlds> <world file="examples/development-world.giveworld" /> </worlds> <nlgservers> <nlgserver name="Example NLG Server (remote)" hostname="labotalc2.loria.fr" port="3001" /> </nlgservers> <database jdbc-url="jdbc:mysql://localhost:8889/give" username="root" password="root" /> <web-reporter port="8079" hostname="localhost" /> <!-- (disabled for participants' packages) <geolocation filename="data/GeoLiteCity.dat" /> --> </matchmaker> |
|
fersingb
|
Posted: December 13, 2009 11:21 by fersingb
|
|
Hi tosswald, I had the same problem you're experiencing. The server crashed after I entered the 1st room when the tutorial wasn't skipped. The problem seemed to be a method I called in the connectionEstablished method. After I commented out this part of code I had no crash any more. Do you do some computations in the connectionEstablished method? Try to comment out the code and check if it stills crash. That's not a fix but it might help to identify the bug. regards, Boris PS : Il fait beau dans le 54 ? |
|
tosswald
|
Posted: December 16, 2009 12:17 by tosswald
|
|
Hi Boris, Actually, I also have the same problem when using the example-nlg-server provided by Alexander Koller. And in this server, I haven't changed any letter in the code. Exactly the same application works perfectly when executed locally but crashes on the server. And as you said, it works if we skip the tutorial. It really seems to be the transition phase which makes it crash... PS : Arf, démasqué... Il fait pas mal en ce moment, mais avant il a plu pendant un mois... |
showing 1 - 9 of 9
Replies: 8 - Last Post: February 05, 2010 13:14
by: Alexander Koller
by: Alexander Koller
