I am trying to build the module l2fwd in DPDK and I keep getting this error. I am using an Oracle Virtual Box with Ubuntu 16.04 OS.
l2fwd example application fails with the following message:
WARNING: Master core has no memory on local socket!
error allocating rte services array
Looks like you missed the step with huge page setup. Basically, you need to allocate huge pages for the application with the following command:
# echo 512 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
Please find more details in DPDK Getting Started Guide.
Related
I am new to Docker and I am trying my hands at it.
I have an image that is on ubuntu 18.04 running an interactive container with it.
I want to install .net3.1 core on it and commit it to my image.
referring to this linklink to install the .net core.
I have installed .net core in one of my EC2, machines similar way.
Here is a commend that I am running
wget https://packages.microsoft.com/config/ubuntu/18.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
I am getting an error below:
--2021-01-08 11:38:46-- https://packages.microsoft.com/config/ubuntu/18.04/packages-microsoft-prod.deb
Resolving packages.microsoft.com (packages.microsoft.com)... failed: Temporary failure in name resolution.
wget: unable to resolve host address 'packages.microsoft.com'
Could some one help me out with this and make me install .net core in this container?
This is relatively minor, and I wasn't able to find any other record of this issue, but it cost me several stressful hours. I'm considering opening an Appcelerator Jira ticket about this bug, so any feed back is welcome before I do so. Questions: Are there any other workarounds besides what I wrote below? What are some better ways to log the actual error?
Environment
Titanium SDK: 7.0.2.GA
Javascript Engine: V8
Platform & version: iOS 11.2
Device Details: iOS simulator (iPhone 7+)
Host Operating System: OS X 10.13 64 bit
Node Version: 7.10.0
Titanium CLI: 5.0.14
Npm Version: 4.2.0
Description
When building an iOS app and there is an issue connecting to the iOS log-server, it always output "Another process is currently bound to port xxxxx" even if there is another server connection issue such as the port not existing.
Workaround
Figure out the real issue by logging the actual error within the sdk itself (at ~/Library/Application Support/Titanium/mobilesdk/osx/7.0.2.GA/iphone/cli/commands/_build.js in the determineLogServerPort function).
Steps to Reproduce
Create a different type of error with the server. For example, my /etc/hosts file did not have an entry for 127.0.0.1 localhost, so the actual node error was 'ENOTFOUND'.
Create a new titanium app with appc ti new.
Build with appc ti build -p ios
Actual Result
Build errors out with following text:
[ERROR] Another process is currently bound to port 27973
[ERROR] Set a unique <log-server-port> between 1024 and 65535 in the <ios> section of the tiapp.xml
Expected Result
More detailed error. I.E. Something like:
Failed to create/connect to log server port with error "[error given by node net package]".
Followed by suggested solution. For example if the node error was EADDRINUSE, then you could still use the existing error message. But if it's another error, log accordingly so the user has the best information for solving the issue.
Close current emulator running and try again
when emulator was opened by xcode, I got such issue
Please make sure you are executing the app with same App name and ID.
If there is a change, please delete the app from device and retake the build.
I opened the ticket with appcelerator here: https://jira.appcelerator.org/browse/TIMOB-25872
They have just marked it as closed so it will hopefully be included in the next sdk version.
The solution for me was what was mentioned as a solution in the JIRA ticket on appcelerator https://jira.appcelerator.org/browse/TIMOB-25872.
I had recently moved to a new Mac and migrated everything, it created a copy of my host file renaming it but didn't update main one so it had no reference to the localhost in there. Once this was fixed it was building no problem again.
Below is what is in the host file.
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
Hope that helps someone, didn't see the answer on JIRA at first glance.
I'm trying to run the following blockchain tutorial on Windows 10
https://hyperledger.github.io/composer/tutorials/developer-guide.html
Everything went fine (all npm installs, fabric tools, download fabric, start fabric, create the project archive, composer runtime install) untill I ran the following command:
composer network start --card PeerAdmin#hlfv1 --networkAdmin admin --networkAdminEnrollSecret adminpw --archiveFile tutorial-network#0.0.1.bna --file networkadmin.card
And
had this error:
Starting business network from archive: tutorial-network#0.0.1.bna
Business network definition:
Identifier: tutorial-network#0.0.1
Description: Tuto DevWorks
× Starting business network definition. This may take a minute...
Error: Error trying to instantiate composer runtime. Error: Error: Invalid results returned ::NOT_FOUND
Command failed
Previous successful command was:
composer runtime install --card PeerAdmin#hlfv1 --businessNetworkName
tutorial-network √ Installing runtime for business network
tutorial-network. This may take a minute... Command succeeded
My configuration is:
WIN 10
Node v8.9.1
npm 5.5.1
Docker version 17.09.0-ce, build afdb6d4
git version 2.14.1.windows.1
I also tried with another bna archive and had the same issue.
Thanks for your help!
If this message occurs on the stage of instantiating the composer chaincode, one must check that there's a fabric channel defined and peers have joined it.
we don't, at present, support Windows 10. We support the platforms shown here:
https://hyperledger.github.io/composer/unstable/installing/development-tools.html
I was facing the issue in MacOS environment. I found that I haven't created the channel and joined the peers. Once I did that, I could start business network and ping.
I followed the steps below, but I'm getting an error.
Install Virtual Box (version 5.0.0) running on Windows 7 host machine.
Install Ubuntu server version 14.04.02 on it.
git clone https://github.com/openstack-dev/devstack.git
cd devstack; cp samples/local.conf .
After that i ran ./stack.sh but came with this error after running for approx 30 minutes:
2015-07-21 20:04:18.841 | ERROR (ConnectionRefused): Unable to establish connection to 10.0.2.15:8774/v2/c199aa06389a4c8c85dffddad18fce1b/flavors/… 2015-07-21 20:04:20.433 | + exit 1 deb#Devstack:~/devstack$
Please help me in resolving the issue
Try re-running the stack. Thats the best hack i found for DevStack debugging.
You need to do some specific network settings in virtual box to overcome this error.
From the Network section, change Attached to to Bridged Adapter, Adapter Type to Paravirtualized Network (virtio-net) and Promiscuous Mode to Allow All.
Check Enable Nested VT-x/AMD-v from System > Processor .
Select USB Tablet as the Pointing Device from System > Motherboard.
Then restart the virtual machine and check ifconfig for a new IP, add it in local.conf and then try install script again.
It should work this time :-)
I'm running virtualbox 4.1 on Debian. If I try to start a VM with a bridged NIC I get this error:
error: Failed to open/create
the internal network 'HostInterfaceNetworking-eth0' (you might need to
modprobe vboxnetflt to make it accessible) (VERR_PERMISSION_DENIED).
VBoxManage: error: Failed to attach the network LUN
(VERR_PERMISSION_DENIED) VBoxManage: error: Details: code
NS_ERROR_FAILURE (0x80004005), component Console, interface IConsole,
callee
System: Linux localhost.localdomain 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux
Virtual Box Version: 4.1.18_Debianr78361
The VM starts with a NAT NIC config.
The weirdest thing is if I export this VM and import it to another user, it works. The other user I tested with was the user I usually use for running auto started virtual machines. But I cant remember doing anything special setting this user up. It is only in its own group and no others. I tried to create a new user and import the VM, but I get the same error as above. I've tried purging virtual box, and completely deleting my conf but it does not work. I just cant figure out what the diff is.
Any help appreciated.
The solution for me was to install virtualbox-4.0 from linux mint. I believe that is actually a downgrade from what in debians repos. Probably packaged different too. Still don't know how the heck I was getting the error I was getting...
sudo apt-get install -f virtualbox-4.0
sudo /etc/init.d/vboxdrv setup