I believe I killed the process by entering Control-C, I'm accessing
this server via SSH and no other consoles popped open  (I confirmed my
DISPLAY setting points to my windows desktop where I'm working from).
I tried a couple of other ports, e.g. 550105, and had the same result.

Is there a debug mode I should engage?

Thanks.

On Sat, Oct 30, 2010 at 3:25 PM, Vega <[email protected]> wrote:
> Try to kill the console. If doesn't help - just change the port from
> 9898 to something else.
>
> On Oct 31, 12:21 am, Lennard de Rijk <[email protected]> wrote:
>> On Sat, Oct 30, 2010 at 3:19 PM, James Purser <[email protected]>wrote:
>>
>> > What distro are you using?
>>
>> Good point, can't reproduce on mac or ubuntu here.
>>
>> Greetings,
>> Lennard
>>
>>
>>
>> > Do you have anything like selinux running?
>>
>> > James
>>
>> > On Sun, Oct 31, 2010 at 9:09 AM, John Poole <[email protected]> wrote:
>>
>> >> run-server.sh has fatal error on startup  My results are at:
>>
>> >>    http://pastebin.com/diuHqEvp
>>
>> >> I terminated the process with Control-C.
>>
>> >> The gravamen of the problem appears to be:
>>
>> >>     .....
>> >>     SEVERE: Fatal error starting http server.
>> >>     java.net.BindException: Address already in use
>> >>     .....
>>
>> >> Both before and after attempting the run_server.sh command, I ran
>> >> netstat to determine if there was a port conflict and nothing came
>> >> back to suggest a conflict:
>> >>     hermes wave-protocol # netstat -an |grep 9898
>> >>     hermes wave-protocol #
>>
>> >> I also tried running netstat in another console while the
>> >> run-server.sh was running and before I terminated it with a Control-C.
>> >>  I had the same result: nothing on the grep for "9898".
>>
>> >> For reference:
>> >>     hermes wave-protocol # java -version
>> >>     java version "1.6.0_22"
>> >>     Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
>> >>     Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)
>> >>     hermes wave-protocol # netstat -an |grep 9898
>> >>     hermes wave-protocol #
>>
>> >> --
>> >> John L. Poole
>>
>> >> P.O. Box 6566
>> >> Napa, CA 94581-6566
>> >> 707-812-1323
>>
>> >> [email protected]
>>
>> >> --
>> >> You received this message because you are subscribed to the Google Groups
>> >> "Wave Protocol" group.
>> >> To post to this group, send email to [email protected].
>> >> To unsubscribe from this group, send email to
>> >> [email protected]<wave-protocol%2bunsubscr...@goog
>> >>  legroups.com>
>> >> .
>> >> For more options, visit this group at
>> >>http://groups.google.com/group/wave-protocol?hl=en.
>>
>> >  --
>> > You received this message because you are subscribed to the Google Groups
>> > "Wave Protocol" group.
>> > To post to this group, send email to [email protected].
>> > To unsubscribe from this group, send email to
>> > [email protected]<wave-protocol%2bunsubscr...@goog
>> >  legroups.com>
>> > .
>> > For more options, visit this group at
>> >http://groups.google.com/group/wave-protocol?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Wave Protocol" 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/wave-protocol?hl=en.
>
>



-- 
John L. Poole

P.O. Box 6566
Napa, CA 94581-6566
707-812-1323

[email protected]

-- 
You received this message because you are subscribed to the Google Groups "Wave 
Protocol" 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/wave-protocol?hl=en.

Reply via email to