According to HyperLedger official Tutorial Document
1: http://hyperledger-fabric.readthedocs.io/en/release-1.0/build_network.html, I tried to run ./byfn.sh -m generate but the output consists of errors:
`
configtxgen -profile TwoOrgsOrdererGenesis -outputBlock ./channel-artifacts/genesis.block
2018-06-15 14:28:54.070 +07 [common/configtx/tool] main -> INFO 001 Loading configuration
2018-06-15 14:28:54.101 +07 [common/configtx/tool/localconfig] Load -> CRIT 002 Error unmarshaling config into struct: 4 error(s) decoding:
'' has invalid keys: capabilities
'Profiles[TwoOrgsChannel].Application' has invalid keys: Capabilities
'Profiles[TwoOrgsOrdererGenesis]' has invalid keys: Capabilities
'Profiles[TwoOrgsOrdererGenesis].Orderer' has invalid keys: Capabilities
res=1
set +x
`
I got some error message I feel like I missed some configuration but I had no idea.
Now the error is resolved thanks to suggestion from my senior suggesting that from the documents I should change version of bash
curl -sSL <link-to-file> | bash -s 1.1.0
Related
I am relatively new to Arch Linux.
So i have been dealing with this issue for quite a long time now. I got this new RTL8188FTV wireless USB network adapter and i have tried installing the drivers for it with Paru AUR helper. The installation seems to fail, as it throws this error at the end :
==> ERROR: Missing 5.15.70-1-lts kernel modules tree for module 8188fu/r112.89d7288.
I can confirm the wireless adapter is functional, since it works on Windows
Package Name: 8188fu-kelebek333-dkms-git
Is there a way to install this "kernel modules tree" so i could finish the installation?
Thanks!
Edit: back with more errors
Building module:
Cleaning build area...
'make' all KVER=6.0.5-arch1-1.............(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.0.5-arch1-1 (x86_64)
Consult /var/lib/dkms/8188fu/r113.f5df53d/build/make.log for more information.
error: command failed to execute correctly
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Install DKMS modules
==> dkms install --no-depmod 8188fu/r113.f5df53d -k 6.0.5-arch1-1
Error! Bad return status for module build on kernel: 6.0.5-arch1-1 (x86_64)
Consult /var/lib/dkms/8188fu/r113.f5df53d/build/make.log for more information.
==> WARNING: `dkms install --no-depmod 8188fu/r113.f5df53d -k 6.0.5-arch1-1' exited 10
==> ERROR: Missing 5.15.75-1-lts kernel modules tree for module 8188fu/r113.f5df53d.
(3/3) Performing snapper post snapshots for the following configurations...
The command
echo 'alias usb:v0BDApF179d*dc*dsc*dp*icFFiscFFipFFin* rtl8188fu' | sudo tee /etc/modprobe.d/r8188eu-blacklist.conf
doesn't seem to do much.
Installation still fails.
Your on kernel 5.15 so you have to backlist the rl8188eu driver. You can do that with this command
echo 'alias usb:v0BDApF179d*dc*dsc*dp*icFFiscFFipFFin* rtl8188fu' | sudo tee /etc/modprobe.d/r8188eu-blacklist.conf
The code was taken from the same repo the aur package was made from
https://github.com/kelebek333/rtl8188fu
I cloned https://github.com/plaid/plaid-link-ios plaid's IOS sample swift app and followed the instructions for Plaid node to get a Generated token. https://plaid.com/docs/quickstart/
I put my token in the swift app linkToken variable in the func presentPlaidLinkUsingLinkToken() but when I run the app and click on the plaid link I'm presented with this error:
2020-11-30 18:03:07.629202-0600 LinkDemo-Swift[1378:41715] [] nw_protocol_get_quic_image_block_invoke dlopen libquic failed
2020-11-30 18:03:08.771021-0600 LinkDemo-Swift[1378:41497] WF: === Starting WebFilter logging for process LinkDemo-Swift
2020-11-30 18:03:08.771106-0600 LinkDemo-Swift[1378:41497] WF: _userSettingsForUser : (null)
2020-11-30 18:03:08.771167-0600 LinkDemo-Swift[1378:41497] WF: _WebFilterIsActive returning: NO
2020-11-30 18:03:08.997682-0600 LinkDemo-Swift[1378:41497] Unbalanced calls to begin/end appearance transitions for <LinkKit.InProcessWebviewFallbackController: 0x13fe30a70>.
exit with ExitError(errorCode: LinkKit.ExitErrorCode.invalidRequest(INVALID_FIELD), errorMessage: "link_token must be properly formatted, non-empty string", displayMessage: Optional(""), errorJSON: nil)
ExitMetadata(status: Optional(requires_credentials), institution: Optional(LinkKit.Institution(id: "", name: "")), linkSessionID: Optional(""), requestID: Optional("FzibHWAqJqtTG3e"), metadataJSON: nil)
2020-11-30 18:03:40.762780-0600 LinkDemo-Swift[1378:41497] Could not signal service com.apple.WebKit.WebContent: 113: Could not find specified service
2020-11-30 18:03:40.768987-0600 LinkDemo-Swift[1378:41497] Could not signal service com.apple.WebKit.Networking: 113: Could not find specified service
My token is in the right format I'm sure, I'm not sure what I'm doing wrong.
Please help,
Thanks
Following the steps below I was able to build and run the LinkDemo-Swift app in iOS Simulator (iPhone 12 mini iOS 14.2) and link an account using the sandbox test credentials.
To ensure there are no mismatches in the environment the following commands show which setup I have used:
% sw_vers
ProductName: Mac OS X
ProductVersion: 10.15.7
BuildVersion: 19H15
% xcode-select -p
/Applications/Xcode.app/Contents/Developer
% xocdebuild -version
Xcode 12.2
Build version 12B45b
% swift -version
Apple Swift version 5.3.1 (swiftlang-1200.0.41 clang-1200.0.32.8)
Target: x86_64-apple-darwin19.6.0
% git -C $PATH_TO/quickstart log --format=oneline -1; true # replace $PATH_TO with the path to the directory containing the Plaid quickstart git clone
9ccc96567eaec7a77209676a1693387cc93a32d0 (HEAD -> master, upstream/master, upstream/HEAD) Merge pull r equest #167 from plaid/sb-quickstart-improvements
% git -C $PATH_TO/plaid-link-ios log --format=oneline -1; true # replace $PLAID_TO with the path to the directory containing the plaid-link-ios git clone
0a8b0c4a85d6042fafdb5deaa346d41364cafc1f (HEAD -> master, tag: ios/2.0.8, origin/master, origin/HEAD) Merge pull request #38 from plaid/add-changelog-2.0.8
Additionally I have the following Plaid quickstart related environment variables set (values redacted):
% env | grep -Ei '^plaid_(client_id|secret|public_key)' | tr 'a-z0-9' '•'
PLAID_CLIENT_ID=••••••••••••••••••••••••
PLAID_SECRET=••••••••••••••••••••••••••••••
PLAID_PUBLIC_KEY=••••••••••••••••••••••••••••••
To generate a link token I ran the node quickstart in Docker
% cd $PATH_TO/quickstart/node
% make QUICKSTART=node up
and also ran the node quickstart locally using nvm (not at the same time as both bind to localhost:8000):
% cd $PATH_TO/quickstart/node
% nvm use; node --version; npm --version
Now using node v14.15.0 (npm v6.14.8)
v14.15.0
6.14.8
% npm install
> nodemon#2.0.5 postinstall $HOME/src/quickstart/node/node_modules/nodemon
> node bin/postinstall || exit 0
added 179 packages from 133 contributors and audited 179 packages in 2.903s
10 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
% node index.js
plaid-quickstart server listening on port 8000
I used curl to generate a new link token from the node quickstart as follows:
% curl -sX POST localhost:8000/api/create_link_token \
| awk -F: 'BEGIN{RS=","} /link_token/{print $2}' \
| pbcopy
With the generated link token in the pasteboard I've replaced the <#GENERATED_LINK_TOKEN#> placeholder in the source code with the actual token:
% cd $PATH_TO/plaid-link-ios
% sed -i "" -e "s/\"<#GENERATED_LINK_TOKEN#>\"/$(pbpaste)/" LinkDemo-Swift/LinkDemo-Swift/ViewController+LinkToken.swift
% git diff -U1 | sed -e '/^\+.*linkToken/s/[0-9]/•/g'; true # link-token redacted
diff --git a/LinkDemo-Swift/LinkDemo-Swift/ViewController+LinkToken.swift b/LinkDemo-Swift/LinkDemo-Swift/ViewController+LinkToken.swift
index 9cce64f..361916a 100644
--- a/LinkDemo-Swift/LinkDemo-Swift/ViewController+LinkToken.swift
+++ b/LinkDemo-Swift/LinkDemo-Swift/ViewController+LinkToken.swift
## -20,3 +20,3 ## extension ViewController {
- let linkToken = "<#GENERATED_LINK_TOKEN#>"
+ let linkToken = "link-sandbox-f•••ebb•-•d•a-•aa•-adae-••a•••••••••"
I made sure that the sample app is properly configured to use the link token flow:
% grep -i 'let sampleFlow' LinkDemo-Swift/LinkDemo-Swift/ViewController.swift
let sampleFlow : PlaidLinkSampleFlow = .linkToken
With no further changes to the project and the LinkDemo Xcode workspace open
% open -a Xcode $PATH_TO/plaid-link-ios/LinkDemo.xcworkspace
I was able to "Build and Run (⌘ R)" the LinkDemo-Swift scheme in the iOS Simulator iPhone 12 mini (iOS 14.2 (18B79)) and successfully link an account using the sandbox test credentials user_good pass_good.
If the issue you are seeing persists I recommend to reach out to the official Plaid support (http://dashboard.plaid.com/support/new) providing detailed and exact steps on how the link token was created and which changes to the sample application were made.
This is my first post on Stackoverflow. Please bear with me...
I am new to basically everything around hyperledger-fabric.
While trying to follow the "Writing Your First Application Tutorial" i am unable to generate the genesis block.
I am running:
windows 10
Docker version 18.03.0-ce, build 0520e24302
docker-compose version 1.20.1, build 5d8c71b2
npm 6.1.2
node.js v12.1
python 2.7
I used the curl commands given in the instructions.
When i run
./startFabric.sh javascript
at first everything is going ok. I am getting some warnings but starting the Channel seems to work fine.
In the next few lines however i am getting an error.
Generate CCP files for Org1 and Org2
/c/Users/Jonathan/Hyperledger_Fabric/fabric-samples/bin/configtxgen
Generating Orderer Genesis block
CONSENSUS_TYPE=solo
+ '[' solo == solo ']'
+ configtxgen -profile TwoOrgsOrdererGenesis -channelID byfn-sys-channel -outputBlock ./channel-artifacts/genesis.block
2019-11-25 10:35:01.676 CET [common.tools.configtxgen] main -> INFO 001 Loading configuration
2019-11-25 10:35:01.677 CET [common.tools.configtxgen.localconfig] Load -> PANI 002 Error reading configuration: Unsupported Config Type ""
2019-11-25 10:35:01.679 CET [common.tools.configtxgen] func1 -> PANI 003 Error reading configuration: Unsupported Config Type ""
panic: Error reading configuration: Unsupported Config Type "" [recovered]
panic: Error reading configuration: Unsupported Config Type ""
It seems that the configuration is missing/not the right "type".
I googled my error and came up with people having similar/the same issue but i havent been able to solve my issue by following the advice they were given (hence why i am here).
Similar posts i found:
https://jira.hyperledger.org/browse/FAB-3467
Error cryptogen tool in Hyperledger Fabric
The people responding to the posts above generally seem to think its an issue regarding the path to the config file which apparently can be fixed with
FABRIC_CFG_PATH=$PWD
But that hasnt worked for me.
Full Console Output:
https://pastebin.com/CHxjZ1Uq
Look at the warning at the start: you are missing some prerequisites.
First, use the generate script to generate the crypto-config and artifacts folder.
Once you got your certificates you can start fabric.
You should have a generte.sh script or something like that.
Essentially it runs the certificate generation for your network using cryptogen.
The code is something like this:
which cryptogen
if [ "$?" -ne 0 ]; then
echo "cryptogen tool not found. exiting"
exit 1
fi
if [ -d "crypto-config" ]; then
rm -Rf crypto-config
fi
set -x
cryptogen generate --config=./crypto-config.yaml
Once you generated the certificates, you can now generate the genesis block with something like:
which configtxgen
if [ -d "config" ]; then
rm -Rf config
fi
mkdir config
configtxgen -profile OneOrgOrdererGenesis -outputBlock ./config/genesis.block
configtxgen -profile OneOrgChannel -outputCreateChannelTx ./config/channel.tx -channelID $CHANNEL_NAME
configtxgen -profile OneOrgChannel -outputAnchorPeersUpdate ./config/${MSP_NAME}anchors.tx -channelID $CHANNEL_NAME -asOrg $MSP_NAME
Obviously replacing with your names and variables.
I am trying to use for the first time the Yocto tool for my BeagleBoneBlack.
First I run this bash file to install Yocto:
#!/bin/bash
WKDIR=/work
mkdir -p $WKDIR/beaglebone-black/yocto/sources
mkdir -p $WKDIR/beaglebone-black/yocto/builds
cd $WKDIR/beaglebone-black/yocto/sources
git clone -b morty git://git.yoctoproject.org/poky.git poky-morty
cd $WKDIR/beaglebone-black/yocto/
source sources/poky-morty/oe-init-build-env builds/build-bbb-morty
Then I edited the file local.conf at "build-bbb-morty/conf" diretory:
MACHINE ?= "beaglebone"
and added
DL_DIR ?= "${TOPDIR}/../dl"
IMAGE_INSTALL_append = " kernel-modules kernel-devicetree"
Then I run bitbake:> bitbake core-image-minimal
After about 8 hours in my Core i7 five generation I got this result at my terminal output and I have no idea what I need to do to fix it:
bitbake core-image-minimal
Parsing recipes: 100% |########################################################################################################| Time: 0:02:55
Parsing of 864 .bb files complete (0 cached, 864 parsed). 1318 targets, 67 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-16.04"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "beaglebone"
DISTRO = "poky"
DISTRO_VERSION = "2.2.1"
TUNE_FEATURES = "arm armv7a vfp neon callconvention-hard cortexa8"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "morty:a3fa5ce87619e81d7acfa43340dd18d8f2b2d7dc"
NOTE: Fetching uninative binary shim from http ://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-nativesdk-libc.tar.bz2;sha256sum=101ff8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca
--2017-01-18 15:51:09-- http ://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-nativesdk-libc.tar.bz2
Resolving downloads.yoctoproject.org (downloads.yoctoproject.org)... 198.145.20.127
Connecting to downloads.yoctoproject.org (downloads.yoctoproject.org)|198.145.20.127|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2473216 (2.4M) [application/octet-stream]
Saving to: ‘/work/beaglebone-black/yocto/builds/build-bbb-morty/../dl/uninative/101ff8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca/x86_64-nativesdk-libc.tar.bz2’
2017-01-18 15:51:18 (297 KB/s) - ‘/work/beaglebone-black/yocto/builds/build-bbb-morty/../dl/uninative/101ff8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca/x86_64-nativesdk-libc.tar.bz2’ saved [2473216/2473216]
Initialising tasks: 100% |#####################################################################################################| Time: 0:00:14
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: attr-native-2.4.47-r0 do_fetch: Failed to fetch URL http ://download.savannah.gnu.org/releases/attr/attr-2.4.47.src.tar.gz, attempting MIRRORS if available
WARNING: libpng-native-1.6.24-r0 do_fetch: Failed to fetch URL http ://distfiles.gentoo.org/distfiles/libpng-1.6.24.tar.xz, attempting MIRRORS if available
ERROR: core-image-minimal-1.0-r0 do_image_wic: Function failed: do_image_wic (log file is located at /work/beaglebone-black/yocto/builds/build-bbb-morty/tmp/work/beaglebone-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_wic.23788)
ERROR: Logfile of failure stored in: /work/beaglebone-black/yocto/builds/build-bbb-morty/tmp/work/beaglebone-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_wic.23788
Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_wic
| Checking basic build environment...
| Done.
|
| Build artifacts not found, exiting.<br/>
| (Please check that the build artifacts for the machine
| selected in local.conf actually exist and that they
| are the correct artifacts for the image (.wks file))
|
| The artifact that couldn't be found was kernel-dir:
| /work/beaglebone-black/yocto/builds/build-bbb-morty/tmp/deploy/images/beaglebone
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_image_wic (log file is located at /work/beaglebone-black/yocto/builds/build-bbb-morty/tmp/work/beaglebone-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_wic.23788)
ERROR: Task (/work/beaglebone-black/yocto/sources/poky-morty/meta/recipes-core/images/core-image-minimal.bb:do_image_wic) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1771 tasks of which 6 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
/work/beaglebone-black/yocto/sources/poky-morty/meta/recipes-core/images/core-image-minimal.bb:do_image_wic
Summary: There were 2 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
While not sure this could be the reason of the problem, the prefered method to add packages to the image, in the local.conf context is using the CORE_IMAGE_EXTRA_INSTALL variable.
Therefore change:
IMAGE_INSTALL_append = " kernel-modules kernel-devicetree"
to
CORE_IMAGE_EXTRA_INSTALL += "kernel-modules kernel-devicetree"
I think there is no problem with your work method.
It seems to be a build environment problem, but the error log seems to confirm.
your log location at "/work/beaglebone-black/yocto/builds/build-bbb-morty/tmp/work/beaglebone-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_wic.23788"
Your error log indicates the the URL for fetching binaries failed.
You can try using tunnel through proxy. Or you can run the bitbake again because it can also fail sometimes due to network conditions.
I am running Sonarqube in a docker container using the default image from docker hub. Sonarqube is working fine. I am now working on using LDAPS for system login and can't seem to get it to work. I created a centos:latest container and have sonarqube running there. I did this so I could have ldapsearch, vim, telnet, update-ca, etc. I used openssl to add the server certificate. I tested with ldapsearch and the following is successful:
[root#bf9accb5647d linux-x86-64]# ldapsearch -x -LLL -H ldaps://dir.example.com -b "dc=example,dc=com" -D "uid=svcSonar,ou=SvcAccts,ou=People,dc=example,dc=com" -W '(uid=usernamehere)' cn
Enter LDAP Password: ******
dn: uid=usernamehere,ou=Users,ou=People,dc=example,dc=com
cn: User Name
Here is my relevant ldap configuration in sonar.properties:
sonar.security.realm=LDAP
ldap.url=ldaps://dir.example.com
ldap.bindDN=uid=svcSonar,ou=SvcAccts,ou=People,dc=example,dc=com
ldap.bindPassword=mypassword
ldap.user.baseDn=ou=Users,ou=People,dc=example,dc=com
ldap.user.request=(uid={login})
Here is the relevant sonar.log entries with TRACE and DEBUG on:
2016.04.15 16:32:35 INFO web[o.s.s.p.ServerPluginRepository] Deploy plugin LDAP / 1.5.1 / 8960e08512a3d3ec4d9cf16c4c2c95017b5b7ec5
2016.04.15 20:19:07 INFO web[org.sonar.INFO] Security realm: LDAP
2016.04.15 20:19:07 INFO web[o.s.p.l.LdapSettingsManager] User mapping: LdapUserMapping{baseDn=ou=Users,ou=People,dc=example,dc=com, request=(uid={0}), realNameAttribute=cn, emailAttribute=mail}
2016.04.15 20:19:07 DEBUG web[o.s.p.l.LdapContextFactory] Initializing LDAP context {java.naming.provider.url=ldaps://dir.example.com, java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, com.sun.jndi.ldap.connect.pool=true, java.naming.security.authentication=simple, java.naming.referral=follow}
2016.04.15 20:19:07 INFO web[o.s.p.l.LdapContextFactory] Test LDAP connection on ldaps://dir.example.com: OK
2016.04.15 20:19:07 INFO web[org.sonar.INFO] Security realm started
.
.
.
2016.04.15 20:26:55 DEBUG web[o.s.p.l.LdapUsersProvider] Requesting details for user usernamehere
2016.04.15 20:26:55 DEBUG web[o.s.p.l.LdapSearch] Search: LdapSearch{baseDn=ou=Users,ou=People,dc=example,dc=com, scope=s
ubtree, request=(uid={0}), parameters=[usernamehere], attributes=[mail, cn]}
2016.04.15 20:26:55 DEBUG web[o.s.p.l.LdapContextFactory] Initializing LDAP context {java.naming.provider.url=ldaps://di
r.example.com, java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, com.sun.jndi.ldap.connect.pool=true, java.na
ming.security.authentication=simple, java.naming.referral=follow}
2016.04.15 20:26:55 DEBUG web[o.s.p.l.LdapUsersProvider] User usernamehere not found in <default>
I did the following for the certificate:
echo "" | openssl s_client -connect server:port -prexit 2>/dev/null | sed -n -e '/BEGIN\ CERTIFICATE/,/END\ CERTIFICATE/ p' > ldap.pem
update-ca-trust force-enable
cp ldap.pem /etc/pki/ca-trust/source/anchors/
update-ca-trust extract
I also used the keytool to add the ldap.pem to the java cacerts for the jre being using by Sonarqube.
Any ideas?
I found the problem. I needed to change ldap.bindDN to ldap.bindDn. :)