Totally different tack:
If you look at how flowvisor is invoked in the ./scripts/flowvisor.sh
script, you need to set
-Dorg.flowvisor.config_dir=$config_dir -Dorg.flowvisor.install_dir=$install_dir"
as jvm options. The config dir and the install dir get set by default
in the ./scripts/envs.sh file, so take a look at where you want them
to point.
- Rob
.
On Wed, Mar 21, 2012 at 9:22 AM, Xuan-Nam Nguyen
<xuan-nam.ngu...@inria.fr> wrote:
> Hi Ali,
>
> Thanks for your suggestion. I'm using the source code version 0.8.1
> After running with your option and change the value of jettyPort = -1 to
> 8888 I got such error :
>
>
> Setting debugging mode: all logs to stderr
>
> --- Setting logging level to NOTE
> CRIT:2012-03-21T17:15:32.076:none:: log level enabled: CRIT
> ALERT:2012-03-21T17:15:32.079:none:: log level enabled: ALERT
> WARN:2012-03-21T17:15:32.079:none:: log level enabled: WARN
> INFO:2012-03-21T17:15:32.079:none:: log level enabled: INFO
> NOTE:2012-03-21T17:15:32.079:none:: log level enabled: NOTE
> INFO:2012-03-21T17:15:32.079:none:: initializing poll loop
> INFO:2012-03-21T17:15:32.292:none:: initializing FlowVisor UserAPI JSONRPC
> SSL WebServer on port 8888
> INFO:2012-03-21T17:15:32.417:none:: Logging to {} via
> {}org.flowvisor.log.jetty...@d12eeaorg.flowvisor.log.JettyLog
> CRIT:2012-03-21T17:15:32.423:none:: MAIN THREAD DIED!!!
> CRIT:2012-03-21T17:15:32.423:none:: ----------------------------
> CRIT:2012-03-21T17:15:32.424:none:: ----- exception in thread
> Thread[main,5,main]::java.lang.RuntimeException: Property
> javax.net.ssl.keyStore not defined; are you correctly using the flowvisor
> wrapper script?
> CRIT:2012-03-21T17:15:32.424:none::
> org.flowvisor.api.JettyServer.init(JettyServer.java:56)
> CRIT:2012-03-21T17:15:32.424:none::
> org.flowvisor.api.JettyServer.<init>(JettyServer.java:40)
> CRIT:2012-03-21T17:15:32.424:none::
> org.flowvisor.api.JettyServer.spawnJettyServer(JettyServer.java:168)
> CRIT:2012-03-21T17:15:32.424:none::
> org.flowvisor.FlowVisor.run(FlowVisor.java:144)
> CRIT:2012-03-21T17:15:32.424:none::
> org.flowvisor.FlowVisor.main(FlowVisor.java:225)
> CRIT:2012-03-21T17:15:32.424:none:: ----------------------------
>
> respawning too fast -- DYING
> CRIT:2012-03-21T17:15:32.425:none:: respawning too fast -- DYING
>
> It seems that is the problem with keyStore ?
>
> Regards
> Nam
>
>
>
>
>
>
>
> ________________________________
>
> From: "Ali Al-Shabibi" <ali.al-shab...@stanford.edu>
> To: "Xuan-Nam Nguyen" <xuan-nam.ngu...@inria.fr>
> Cc: "Aaron Rosen" <aro...@clemson.edu>, openflow-discuss@lists.stanford.edu
> Sent: Wednesday, March 21, 2012 4:58:56 PM
>
> Subject: Re: [openflow-discuss] Import FlowVisor Project into Eclipse ?
>
> Hi Nam,
>
> What version of FlowVisor are you trying to run? Also could you start
> flowvisor with the following options:
>
> flowvisor -l DEBUG <configfile>
>
> Try this from within eclipse.
>
> --
> Ali Al-Shabibi
>
> On 21 mars 2012, at 06:30, Xuan-Nam Nguyen <xuan-nam.ngu...@inria.fr> wrote:
>
> Thank you, but I used netstat -ltnup to check and I see nothing run on port
> 8080 and I still got that error.
> In Bug track :
> https://openflow.stanford.edu/bugs/browse/FLOWVISOR-30?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
> it said also that is a problem with port I think in my case, it is not the
> problem with port because I can start flowvisor from command line but can
> not start it from Eclipse.
>
> It seems that is the problem with lib or link directory but with such that
> log I do not know how to solve.
>
> Thanks
>
> Nam
>
> ________________________________
>
> From: "Aaron Rosen" <aro...@clemson.edu>
> To: "Xuan-Nam Nguyen" <xuan-nam.ngu...@inria.fr>
> Cc: openflow-discuss@lists.stanford.edu
> Sent: Wednesday, March 21, 2012 12:04:54 PM
> Subject: Re: [openflow-discuss] Import FlowVisor Project into Eclipse ?
>
> Do you have anything already binding on port 8080? Flowvisor also uses that
> port for an RPC service.
>
> Aaron
>
> On Wed, Mar 21, 2012 at 6:49 AM, Xuan-Nam Nguyen <xuan-nam.ngu...@inria.fr>
> wrote:
>>
>> Thanks Aaron,
>>
>> I changed to a different port (6633 -> 6635) but I still got the same
>> error.
>>
>> (I can build Flowvisor by 'make install' command and it runs well and I'm
>> trying to import the source to Eclipse to understand more and to modify a
>> bit)
>>
>> Nam
>>
>> ________________________________
>>
>> From: "Aaron Rosen" <aro...@clemson.edu>
>> To: "Xuan-Nam Nguyen" <xuan-nam.ngu...@inria.fr>
>> Cc: openflow-discuss@lists.stanford.edu
>> Sent: Wednesday, March 21, 2012 11:30:15 AM
>> Subject: Re: [openflow-discuss] Import FlowVisor Project into Eclipse ?
>>
>>
>> I've gotten that error if something is already binded on the same port
>> that flowvisor is trying to use (or maybe you already have flowvisor running
>> somewhere else on the machine using the same port).
>>
>> Aaron
>>
>> On Wed, Mar 21, 2012 at 6:11 AM, Xuan-Nam Nguyen
>> <xuan-nam.ngu...@inria.fr> wrote:
>>>
>>> Hi all,
>>>
>>> I have checked out the source code of FlowVisor from
>>> https://openflow.stanford.edu/display/DOCS/Flowvisor and imported it to
>>> Eclipse using the option "Java Project from Existing Ant buildfile".
>>>
>>> When I run or debug, I get the following error
>>> --- Setting logging level to NOTE
>>> respawning too fast -- DYING
>>>
>>> Thanks in advance.
>>>
>>> NGUYEN Xuan Nam
>>>
>>>
>>> _______________________________________________
>>> openflow-discuss mailing list
>>> openflow-discuss@lists.stanford.edu
>>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>>>
>>
>>
>>
>> --
>> Aaron O. Rosen
>> Masters Student - Network Communication
>> 306B Fluor Daniel
>>
>>
>>
>
>
>
> --
> Aaron O. Rosen
> Masters Student - Network Communication
> 306B Fluor Daniel
>
>
>
> _______________________________________________
> openflow-discuss mailing list
> openflow-discuss@lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>
>
>
> _______________________________________________
> openflow-discuss mailing list
> openflow-discuss@lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>
_______________________________________________
openflow-discuss mailing list
openflow-discuss@lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
