fabric:create -g localip is ignored

[Isszul]

using

fabric:create -g localip 

throws no error and still creates the fabric with local hostname resolution.

[jstrachan]

which version are you using and which shell script are you using to create the fabric? You know the bin/fabric8 and bin/fabric8-start commands create a fabric by default and use env vars to specify the global resolver etc? http://fabric8.io/gitbook/environmentVariables.html

[Isszul]

Fabric8 version CR5

From a fresh installation, just running bin/fabric doesnt seem to create a fabric ensemble and prompts to create one in the shell display

Please wait while Fabric8 is loading...
100% [========================================================================]

______    _          _      _____
|  ___|  | |        (_)    |  _  |
| |_ __ _| |__  _ __ _  ___ \ V /
|  _/ _` | '_ \| '__| |/ __|/ _ \
| || (_| | |_) | |  | | (__| |_| |
\_| \__,_|_.__/|_|  |_|\___\_____/
  Fabric8 Container (1.1.0.CR5)
  http://fabric8.io/

Type 'help' to get started
and 'help [cmd]' for help on a specific command.
Hit '<ctrl-d>' or 'osgi:shutdown' to shutdown this container.

Open a browser to http://localhost:8181 to access the management console

Create a new Fabric via 'fabric:create'
or join an existing Fabric via 'fabric:join [someUrls]'

Fabric8:karaf@root>

Happy to take a look at working around this with an env var, should it defined in bin/setenv? or are you talking about a etc/ configuration?

[davsclaus]

Yeah the welcome screen hasn't been updated yet. We are in the middle of a needed karaf 2.4 upgrade. And after that it allows us to make that welcome screen more intelligent.

Also it outputs 2 time the 1st time you start fabric as said http://fabric8.io/faq/

So you should wait until that 2nd screen is printed before fabric is ready. Or use fabric:status

If you want to manually create fabric, then start in standalone mode with bin/standalone

[Isszul]

That would explain a few funny things I have seen.

Any idea how long the 2nd time takes?

I still have that shell open and its not happened yet.

Also fabric:status doesn't seem to be available until I run fabric:create manually.

Fabric8:karaf@root> fabric:status
Command not found: fabric:status

I am running this under windows, if you think that might make a difference?

[jstrachan]

@Isszul BTW sorry about the messy startup; as soon as karaf 2.4.x gets merged in things should be much more slick.

I tend to wait until the container-list command is available via tab completion & returns success. Or you can watch the log. It takes about a minute to properly startup and create the fabric usually.

Currently you get the startup screen twice as well; the 2nd time it appears is usually around the time the fabric is properly created and ready for use.

This should be fixed for good in a week or so I hope!

[jstrachan]

once fabric's started; its much slicker ;)

[Isszul]

Thanks for the info!

I'll hold off until CR6 then.

[Isszul]

Setting the ENV VAR worked around this for me so I will close this.