nathan,
t
his error means some process is already using the port jdwp is
trying to use. The likely cause is that you're running a second instance
of matterhorn (or something that runs jdwp).  "ps -aux | grep java"
should show you other java instances that are running.

Chris

On Sat, 03 Sep 2011 20:05:59 -0500
Nathan Cameron <[email protected]> wrote:

> Alright...I turned off all of the capture agents running 1.1 and
> attempted to start the core only to get the following error:
> 
> ERROR: transport error 202: bind failed: Address already in use
> ERROR: JDWP Transport dt_socket failed to initialize,
> TRANSPORT_INIT(510) JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197):
> No transports initialized [../../../src/share/back/debugInit.c:690]
> FATAL ERROR in native method: JDWP No transports initialized,
> jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197) Aborted
> 
> I never had these problems with 1.1.  How can I fix this.
> 
> Thank you for any assistance you can give as always.
> 
> On Sep 3, 2011, at 10:34 AM, Wunden Tobias wrote:
> 
> > Hi Nathan,
> > 
> >> WARN (OrganizationFilter:96) - No organization is mapped to handle
> >> http://192.168.1.40:8080/capture-admin/recordings/2537
> > 
> > please take a look at the mailing list archives from this week,
> > conversation between Hank Magnuski and Josh holtzman on the exact
> > same topic.
> > 
> >> I think this could possibly be because I have capture agents on
> >> 1.1 pointing to the same address as this core 1.2 machine?  Are
> >> Matterhorn versions backward compatible like that or do I have to
> >> update all capture agents to 1.2?
> > 
> > Same here: Chris Brooks answered a similar question yesterday:
> > there are REST api changes, so capture agents are not compatible
> > with different cores.
> > 
> >> If I need to do that is there a way to preserve the raw capture
> >> data stored in the cache folder of the capture agents?
> > 
> > You can take the media packages that the agents created and ingest
> > them manually if you like. Even keeping the cache around and just
> > updating the software might work (Chris, please chime in if that's
> > not the case).
> > 
> > Tobias
> > _______________________________________________
> > Community mailing list
> > [email protected]
> > http://lists.opencastproject.org/mailman/listinfo/community
> > 
> > 
> > To unsubscribe please email
> > [email protected]
> > _______________________________________________
> 
> _______________________________________________
> Community mailing list
> [email protected]
> http://lists.opencastproject.org/mailman/listinfo/community
> 
> 
> To unsubscribe please email
> [email protected]
> _______________________________________________

_______________________________________________
Community mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/community


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to