I get two errors when I look to start a Chainlink node. Here they are:
[ERROR] unable to lock ORM: pq: password authentication failed for
user "root" logger/default.go:155
stacktrace=github.com/smartcontractkit/chainlink/core/logger.Errorf
[FATAL] Unable to initialize ORM: pq: password authentication failed
for user "root" unable to open postgresql://:#10.24.64.5:5432/ for
gorm DB
Then, I am also unable to connect to the GUI
Related
getting this error :-
SASL authentication error: SASL handshake failed (step): SASL(-1): generic failure: GSSAPI Error: An invalid name was supplied (Success) (after 25ms in state AUTH_REQ)
kinit command is working fine with the keytab file, need to know what might be the issue?
Looked over internet, tried changing file permission of krb5.conf file, nothing changed.
I am trying to start a chainlink node in rinkeby testnet.I have setup a postgres DB in AWS. The Database URL is already given. Below is the error while i am trying to start the node.
[ERROR] invalid database url %spostgresql://postgres:Bounty2000%#database-1.ciiecd8szsuh.us-west-1.rd
s.amazonaws.com:5432/db_sar_rinkeby orm/config.go:283
[ERROR] failed to initialize database, got error failed to connect to `host=/tmp user=root database=`
: dial error (dial unix /tmp/.s.PGSQL.5432: connect: no such file or directory) orm/orm.go:82
[ERROR] failed to initialize database, got error failed to connect to `host=/tmp user=root database=`
: dial error (dial unix /tmp/.s.PGSQL.5432: connect: no such file or directory) orm/orm.go:82
I tried changing few settings from AWS front but nothing helped.. If anyone have any clue pls help me up.
Based on the documentation it looks like there may be an "s" in front of your postgres URL, try removing that in your .env file. Also try replacing the database name with the IP address+Port. What should replace $DATABASE is "postgres". Finally try adding in ?sslmode=disable if you don't have ssl activated at the database (not recommended for a production node).
Example in .env:
DATABASE_URL=postgresql://me1234:password1234#10.10.100.100:3000/postgres?sslmode=disable
I have configured my local REST server to use GitHub auth and Mongo DB. I have followed the deployment steps and can authenticate my GiHub ID putting the default Wallet into the Mongo DB. I then create a participant and issue an identity for that participant. I add the identity to the wallet and set that identity as the default. I was able to do a system/ping to return the current participant and also was able to call REST APIs.
Now I would like to start REST server with single user mode with identity which I created in the deployment steps as follow.
composer-rest-server -i nomura -s twidKDZiYFGw -m false -a false
I assume Blockchain identity specified on the command line at startup is created when issuing an identity for the participant.
But it shows the following error.
Discovering types from business network definition ...
Connection fails: Error: Error trying to ping. Error: Error trying to query chaincode. Error: chaincode error (status: 500, message: Error: The current identity has not been registered:nomura)
It will be retried for the next request.
Exception: Error: Error trying to ping. Error: Error trying to query chaincode. Error: chaincode error (status: 500, message: Error: The current identity has not been registered:nomura)
Error: Error trying to ping. Error: Error trying to query chaincode. Error: chaincode error (status: 500, message: Error: The current identity has not been registered:nomura)
What else do I have to do to create valid blockchain id for starting REST server?
your identity is fine. The problem appears to be how you're trying to start the REST server. You need to specify the connection profile (to connect to the business network).
Example syntax (where 'hlfv1' below is my HL Fabric v1 connection profile name) is:
composer-rest-server -p hlfv1 -n my-network -i nomura -s twidKDZiYFGw -m false -a false
I am trying out Lagom from Lightbend, using the my-first-system template from the GettingStarted page.
I am on Windows 10, and behind a corporate proxy.
Activator fails to download some dependencies due to missing credentials for the proxy. I have set the HTTP_PROXY environment variable.
The following error is reported by activator:
[info] Updating {file:/E:/Projects/LagomHelloWorld/my-first-system/project/}my-first-system-build...
[info] Resolving com.lightbend.lagom#lagom-sbt-plugin;1.0.0 ...
[error] Server access Error: Connection timed out: connect url=https://repo.typesafe.com/typesafe/ivy-releases/com.lightbend.lagom/lagom-sbt-plugin/scala_2.10/sbt_0.13/1.0.0/ivys/ivy.xml
[error] Server access Error: Connection timed out: connect url=https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/com.lightbend.lagom/lagom-sbt-plugin/scala_2.10/sbt_0.13/1.0.0/ivys/ivy.xml
[error] Server access Error: Connection timed out: connect url=https://repo1.maven.org/maven2/com/lightbend/lagom/lagom-sbt-plugin_2.10_0.13/1.0.0/lagom-sbt-plugin-1.0.0.pom
[error] Unable to find credentials for [ # <proxy-ipv4-addr> ].
[warn] module not found: com.lightbend.lagom#lagom-sbt-plugin;1.0.0
Note: The error message contains the actual IPv4 address, not the substitute I show above.
Where should I specify the user id and password for the proxy?
How can I do that in a secure way?
Activator should check for system properties, in your case
#-Dhttp.proxyUser=PUT YOUR PROXY USER HERE
#-Dhttp.proxyPassword=PUT YOUR PROXY PASSWORD HERE
in a file ~/.activator/activatorconfig.txt.
This is described in detail in the FAQ section on https://www.lightbend.com/activator/docs
Scroll down to the section "Behind a Proxy".
I have Reset the DEV_OAM and DEV_OPSS Passwords
Using the command
alter user dev_oam identified by Xxxxxxx
alter user dev_opss identified by Xxxxxx
After the Password Reset i have tried to restart the Weblogic Admin Server and Oam managed server.When i am trying to restart the Admin Server, I encountered the below error.
Internal Exception: java.sql.SQLException: ORA-01017: invalid username/password; logon denied
Error Code: 1017
Feb 20, 2015 10:58:08 PM oracle.security.jps.internal.credstore.ldap.LdapCredentialStore init
WARNING: Could not create credential store instance. Reason oracle.security.jps.service.policystore.PolicyStoreConnectivityException: JPS-10000: There was an internal error in the policy store.
JPS-01055: Could not create credential store instance. Reason oracle.security.jps.service.policystore.PolicyStoreConnectivityException: JPS-10000: There was an internal error in the policy store.
Error: Diagnostics data was not saved to the credential store.
Error: Validate operation has failed.
[oracle#oamps2 bin]$
[oracle#oamps2 bin]$ tail -f AdminServer.out
[EL Severe]: 2015-02-20 22:46:27.246--ServerSession(899981417)--Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-01017: invalid username/password; logon denied
Error Code: 1017
Feb 20, 2015 10:46:27 PM oracle.security.jps.internal.credstore.ldap.LdapCredentialStore init
WARNING: Could not create credential store instance. Reason oracle.security.jps.service.policystore.PolicyStoreConnectivityException: JPS-10000: There was an internal error in the policy store.
JPS-01055: Could not create credential store instance. Reason oracle.security.jps.service.policystore.PolicyStoreConnectivityException: JPS-10000: There was an internal error in the policy store.
Error: Diagnostics data was not saved to the credential store.
Error: Validate operation has failed.
Need to do the security configuration first!
Can anyone suggest me what should i do to resolve this.
Have you altered all of your connection pool configuration passwords in weblogic to match the database password? This document may help you, particularly the referenced documents at the bottom (You need an oracle support account to view these).