Redhawksdr Failed to connect to local domain - dns

I'm getting the following error while trying to connect
Failed to connect to domain: REDHAWK_DEV
org.eclipse.core.runtime.CoreException: Error while executing callable. Caused by
org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
I tried
$ nodeBooter -D
Segmentation fault (core dumped)
and also
$ cleanomni
sh: 1: /etc/init.d/omniNames: not found
I'm on Ubuntu 14.04.5 64bit with redhawk-src-2.0.3
Is there any solution?

Based on the dialog, this was a network issue, not a REDHAWK configuration issue. We will consider adding the text mentioned in the manual for clarification.

Related

Facing Appium error: Error getting device API level

These are the errors I got, as a test is done on cucumber, appium for mobile testing. I used windows and eclipse (cucumber) and I got these errors, before it was running
Failed to Create Session. The session identified by fca400..... is not known
and when I ran
adb uninstall io.appium.uiautomator2.server; adb uninstall io.appium.uiautomator2.server.test; adb uninstall io.appium.unlock (was throwing error); adb uninstall io.appium.settings
I got the following error
Failed to create session. An unknown server-side error occurred while processing the command. Original error: Error getting device API level. Original error: Error executing adbExec. Original error: 'Command 'C:\Users\Diego\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 1115fbab02003004 shell getprop ro.build.version.sdk' timed out after 20000ms'. Try to increase the 20000ms adb execution timeout represented by 'adbExecTimeout' capability

Hyperledger Fabric and Node.js creation of environment successfully and getting some error in execution

I am creating network but after that when I'm running the query.js and I am getting this errors:
Fatal error in ../deps/v8/src/api.cc, line 1200
Check failed: !value_obj->IsJSReceiver() || value_obj->IsTemplateInfo().
==== C stack trace ===============================
node(v8::base::debug::StackTrace::StackTrace()+0x16) [0x1598936]
node(V8_Fatal+0xd6) [0x15935c6]
node(v8::Template::Set(v8::Local, v8::Local, v8::PropertyAttribute)+0xf7) [0xa9a447]
/home/ubramanyam/fabric-samples/fabcar/node_modules/grpc/src/node/extension_binary
#Subramanyam , What OS and Node version are you using ?
Can you also confirm if you followed instructions given here
http://hyperledger-fabric.readthedocs.io/en/latest/prereqs.html#node-js-runtime-and-npm

Chef-server-ctl reconfigure/ Creating Admin User on chef server

I am fairly new to Linux (and brand new to chef) and I have ran into an issue when setting up my chef server. I am trying to create an admin user with the command
sudo chef-server-ctl user-create admin Admin Ladmin admin#example.com
examplepass -f admin.pem
but after I keep getting this error:
ERROR: Connection refused connecting...
ERROR: Connection refused connecting to https://127.0.0.1/users/, retry 5/5
ERROR: Network Error: Connection refused - Connection refused
connecting to https://..., giving up
Check your knife configuration and network settings
I also noticed that when I ran chef-server-ctl I got this output:
[2016-12-21T13:24:59-05:00] ERROR: Running exception handlers Running
handlers complete
[2016-12-21T13:24:59-05:00] ERROR: Exception
handlers complete Chef Client failed. 0 resources updated in 01 seconds
[2016-12-21T13:24:59-05:00] FATAL: Stacktrace dumped to
/var/opt/opscode/local-mode-cache/chef-stacktrace.out
[2016-12-21T13:24:59-05:00] FATAL: Please provide the contents of the
stacktrace.out file if you file a bug report
[2016-12-21T13:24:59-05:00] FATAL:
Chef::Exceptions::CannotDetermineNodeName: Unable to determine node
name: configure node_name or configure the system's hostname and fqdn
I read that this error is due to a prerequisite mistake but I'm uncertain as to what it means or how to fix it. So any input would be greatly appreciated.
Your server does not have a valid FQDN (aka full host name). You'll have to fix this before installing Chef server.

ejabberd 16.01 postinstall.sh fails on centos 7

I've just installed ejabberd 16.01 on my CentOS 7.1.1503, I have used the rpm installer downloaded from ProcessOne's web site using:
sudo rpm -Uvh ejabberd-16.01-0.x86_64.rpm
The installation went well up until the end, but finally I got an error message (without any description). I took a look into /opt/ejabberd-16.01 and saw everything was in it's place so I've tried running /bin/postinstall.sh manually to see what might go wrong.
When I run the script I get the following output:
-=- ejabberd post installation script -=-
(c) 2005-2015 ProcessOne
* Checking ejabberd installation
usermod: no changes
* Starting ejabberd instance
Failed to create main carrier for ll_alloc
Aborted (core dumped)
Failed to create main carrier for ll_alloc
Aborted (core dumped)
Failed to create main carrier for ll_alloc
Aborted (core dumped)
Failed to create main carrier for ll_alloc
Aborted (core dumped)
Failed to create main carrier for ll_alloc
Aborted (core dumped)
Failed to create main carrier for ll_alloc
Aborted (core dumped)
Failed to create main carrier for ll_alloc
Aborted (core dumped)
Failed to create main carrier for ll_alloc
Aborted (core dumped)
I get a familiar experience when I start the ejabbered server using:
ejabberdctl start
and then when I try to use ejabberdctl again (to stop/register a user) I get the same result:
1
From searching around I've found some connection to memory issues (erl with centos Failed to create main carrier for ll_alloc)
but this doesn't seem to be the case since I have 1GB of RAM and this is the output of top command: 3
so as you can see I have 573MB of free RAM (shouldn't it be enough??)
any help would be very much appreciated,
Thank you.

Error while bootstrapping ec2 instance on hosted chef server on azure

I am trying to bootstrap ec2 instance using knife on chef server hosted on azure marketplace. the chef client run fails throwing the following error.
PS C:\Users\xyz\chef-repo> knife ec2 server create -I ami-25c00c46 -f t2.micro
--region ap-southeast-1 -N ec2module
-x ubuntu -i abc.pem -r "role[ec2], role[jenkinserver]" -g sg-9f1b31fa sudo
.ap-southeast-1.compute.amazonaws.com Chef encountered an error attempting to create the client "ec2module"
.ap-southeast-1.compute.amazonaws.com Running handlers:
.ap-southeast-1.compute.amazonaws.com [2016-01-20T11:39:26+00:00] ERROR: Running exception handlers
.ap-southeast-1.compute.amazonaws.com Running handlers complete
.ap-southeast-1.compute.amazonaws.com [2016-01-20T11:39:26+00:00] ERROR: Exception handlers complete
.ap-southeast-1.compute.amazonaws.com Chef Client failed. 0 resources updated in 03 seconds
.ap-southeast-1.compute.amazonaws.com [2016-01-20T11:39:26+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
.ap-southeast-1.compute.amazonaws.com [2016-01-20T11:39:26+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
.ap-southeast-1.compute.amazonaws.com [2016-01-20T11:39:26+00:00] ERROR: undefined method `length' for nil:NilClass
.ap-southeast-1.compute.amazonaws.com [2016-01-20T11:39:26+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
There seems to be a problem with the server SSL certificate and perhaps it is related to Chef issue #4301 (read it).
Try downloading the SSL certificate from the Chef Server:
> knife ssl fetch
Then, you can check it with:
> knife ssl check
I hope this helps.

Resources