Author |
Message |
432hz

Joined: Dec 13, 2007 Posts: 12 Location: the Netherlands - Enschede / Hengelo
|
Posted: Fri Jan 29, 2010 8:12 am Post subject:
[chuck]: cannot bind to tcp port 8888... Subject description: [chuck]: cannot bind to tcp port 8888... |
 |
|
hendrikus@pardus chuck $ ./chuck birdies.ck
[chuck]: cannot bind to tcp port 8888...
Can someone explane me what this message means - i know that there is a http://localhost 8080 port? _________________ http://sites.google.com/site/432hz440hz/ |
|
Back to top
|
|
 |
kurtk
Joined: Jan 27, 2010 Posts: 8 Location: usa
|
Posted: Fri Jan 29, 2010 8:52 am Post subject:
|
 |
|
is another chuck already running? perhaps in another shell?
if i enter:
%>chuck test.ck
in one shell and then in another shell do it again...
%>chuck test.ck
the second chuck gives that same complaint.
you want to enter:
%> chuck --loop
in one shell
and then:
%> chuck test.ck
in another to add the shred to the vm.
or if you are hardcore:
%> chuck --loop &
in one giving you back the prompt and then
%>chuck test.ck
in the same shell.
hope that helps. _________________ .............................................
http://kurtkotheimer.com
............................................. |
|
Back to top
|
|
 |
Kassen
Janitor


Joined: Jul 06, 2004 Posts: 7678 Location: The Hague, NL
G2 patch files: 3
|
Posted: Fri Jan 29, 2010 7:44 pm Post subject:
|
 |
|
Yes, exactly as Kurt says. Dan Trueman was asking on the mailing list about the same thing, a while ago. His problem definitely had to do with a second instance.
This port is the default one that ChucK uses to communicate between the VM and other terminal windows for the commands to add, replace, remove, etc, shreds. if the issue isn't a second instance of ChucK it might be a overly active firewall.
Also note that "chuck --loop &" will only work on Unix-based OS's so not on Windows.
Welcome on board, Kurt. _________________ Kassen |
|
Back to top
|
|
 |
432hz

Joined: Dec 13, 2007 Posts: 12 Location: the Netherlands - Enschede / Hengelo
|
Posted: Sat Jan 30, 2010 3:38 am Post subject:
[chuck]: cannot bind to tcp port 8888... Subject description: [chuck]: cannot bind to tcp port 8888... |
 |
|
Kassen wrote: |
This port is the default one that ChucK uses to communicate between the VM and other terminal windows for the commands to add, replace, remove, etc, shreds.
|
Is it posible to changes this to another port - while this happands to many time in my situation that i don't can work around with Chuck. Because there is not any other program running than Chuck at that moment, that clamed the sound card.
It will happend that when i changes form only one Chuck example otf_01 to hanoi.ck Chuck will give me that message cannot bind to tcp port 8888
I am also working with Sox a lot. With Sox you can have many terminals open with Sox as much as you like and in the same time other music programs.
Kassen wrote: |
Also note that "chuck --loop &" will only work on Unix-based OS's so not on Windows.
|
I am on Linux Pardus._Unix. _________________ http://sites.google.com/site/432hz440hz/ |
|
Back to top
|
|
 |
432hz

Joined: Dec 13, 2007 Posts: 12 Location: the Netherlands - Enschede / Hengelo
|
Posted: Sat Jan 30, 2010 3:43 am Post subject:
|
 |
|
kurtk wrote: | is another chuck already running? perhaps in another shell?
if i enter:
%>chuck test.ck
in one shell and then in another shell do it again...
%>chuck test.ck
the second chuck gives that same complaint.
you want to enter:
%> chuck --loop
in one shell
and then:
%> chuck test.ck
in another to add the shred to the vm.
or if you are hardcore:
%> chuck --loop &
in one giving you back the prompt and then
%>chuck test.ck
in the same shell.
hope that helps. |
Kurk also thanks to help me on my way with Chuck _ i answer to Kassen. _________________ http://sites.google.com/site/432hz440hz/ |
|
Back to top
|
|
 |
Kassen
Janitor


Joined: Jul 06, 2004 Posts: 7678 Location: The Hague, NL
G2 patch files: 3
|
Posted: Tue Feb 02, 2010 8:03 am Post subject:
Re: [chuck]: cannot bind to tcp port 8888... Subject description: [chuck]: cannot bind to tcp port 8888... |
 |
|
432hz wrote: |
Is it posible to changes this to another port - while this happands to many time in my situation that i don't can work around with Chuck. Because there is not any other program running than Chuck at that moment, that clamed the sound card. |
Yes, it is. See the "--port" command here;
http://chuck.cs.princeton.edu/doc/program/vm.html
Quote: |
It will happend that when i changes form only one Chuck example otf_01 to hanoi.ck Chuck will give me that message cannot bind to tcp port 8888
|
Ah, ok... but in that case I'd simply run both on the same VM, using the "add" or "replace" commands. The only reason I can think of to want to use two VM's would be to make use of a multi-core cpu. Is there a reason that strategy doesn't suit your needs?
Quote: |
I am also working with Sox a lot. With Sox you can have many terminals open with Sox as much as you like and in the same time other music programs. |
I'm not familiar with that. Does that have a advantage over regular terminal windows like on my Ubuntu install?
Quote: |
I am on Linux Pardus._Unix. |
I looked that up. Looks quite interesting. Good to see Turkey take a lead in adopting open systems for governmental usage. Here in NL they demand that you have a closed source OS (and it better be a new one) to file your taxes digitally.... and NL is supposed to be a relatively "free" country! _________________ Kassen |
|
Back to top
|
|
 |
|