I trying setup LDAP(Active Directory) authetication ceph rgw.
My ceph version 12.2.2.
My config file ceph.conf
[cephrgwhost]
rgw_frontends = civetweb port=443
rgw_ldap_uri = "ldap://adceph.ceph.int:389"
rgw_ldap_binddn = "CN=cephldap,CN=Users,DC=ceph,DC=int"
rgw_ldap_secret = "Password"
rgw_ldap_searchdn = "cn=users,dc=ceph,dc=int"
rgw_ldap_dnattr = "cn"
rgw_s3_auth_use_ldap = true
debug rgw = 20
At rgw host i make three commands
# export RGW_ACCESS_KEY_ID="<username>"
# export RGW_SECRET_ACCESS_KEY="<password>"
# radosgw-token --encode --ttype=ad
the result of these commands is the base64 string:
ewogICAgIlJHV19UT0tFTiI6IHsKICAgICAgICAidmVyc2lvbiI6IDEsCiAgICAgICAgInR5cGUiOiAiYWQiLAogICAgICAgICJpZCI6ICJjZXBobGRhcCIsCiAgICAgICAgImtleSI6ICJwYXNzd29yZCIKICAgIH0KfQo=
in the decoded state the string looks like this. Login and password are in this line
{
"RGW_TOKEN": {
"version": 1,
"type": "ad",
"id": "cephldap",
"key": "password"
}
}
for connection to rgw i use python boto. I not understund what use need value for variable aws_secret_access_key
import boto
import boto.s3.connection
access_key = 'base64'
secret_key = ''
conn = boto.connect_s3(
aws_access_key_id = access_key,
aws_secret_access_key = secret_key,
host = 'cephrgwhost',
port = 7480,
is_secure=False, # uncomment if you are not using ssl
calling_format = boto.s3.connection.OrdinaryCallingFormat(),
)
for bucket in conn.get_all_buckets():
print bucket
print "{name}\t{created}".format(
name = bucket.name,
created = bucket.creation_date,
)
execution of the script gives this result:
Traceback (most recent call last):
File "s3python.py", line 18, in <module>
for bucket in conn.get_all_buckets():
File "c:\Python27\lib\site-packages\boto\s3\connection.py", line 447, in get_a
ll_buckets
response.status, response.reason, body)
boto.exception.S3ResponseError: S3ResponseError: 403 Forbidden
<?xml version="1.0" encoding="UTF-8"?><Error><Code>AccessDenied</Code><RequestId
>tx000000000000000000004-005b7e7f94-1ebb3-default</RequestId><HostId>1ebb3-defau
lt-default</HostId></Error>
the contents of the cephrgwhost log (log file /var/log/ceph/ceph-client.rgw.cephrgwhost.log). I'm looking at the traffic between cephrgwhost and adceph.ceph.int, no ldap traffic is present
2018-08-23 15:20:26.424061 7fa4d427c700 20 CONTENT_LENGTH=0
2018-08-23 15:20:26.424099 7fa4d427c700 20 HTTP_ACCEPT_ENCODING=identity
2018-08-23 15:20:26.424104 7fa4d427c700 20 HTTP_AUTHORIZATION=AWS ewogICAgIlJHV19UT0tFTiI6IHsKICAgICAgICAidmVyc2lvbiI6IDEsCiAgICAgICAgInR5cGUiOiAiYWQiLAogICAgICAgICJpZCI6ICJjZXBobGRhcCIsCiAgICAgICAgImtleSI6ICJwYXNzd29yZCIKICAgIH0KfQo=:CRW41WihDir6Xj6cJihdMKj95/M=
2018-08-23 15:20:26.424109 7fa4d427c700 20 HTTP_DATE=Thu, 23 Aug 2018 12:20:20 GMT
2018-08-23 15:20:26.424111 7fa4d427c700 20 HTTP_HOST=ceph132v12.ceph.int:7480
2018-08-23 15:20:26.424123 7fa4d427c700 20 HTTP_USER_AGENT=Boto/2.49.0 Python/2.7.10 Windows/7
2018-08-23 15:20:26.424131 7fa4d427c700 20 REQUEST_METHOD=GET
2018-08-23 15:20:26.424133 7fa4d427c700 20 REQUEST_URI=/
2018-08-23 15:20:26.424134 7fa4d427c700 20 SCRIPT_URI=/
2018-08-23 15:20:26.424136 7fa4d427c700 20 SERVER_PORT=7480
2018-08-23 15:20:26.424139 7fa4d427c700 1 ====== starting new request req=0x7fa4d42761f0 =====
2018-08-23 15:20:26.424190 7fa4d427c700 2 req 9:0.000041::GET /::initializing for trans_id = tx000000000000000000009-005b7ea68a-1ebb3-default
2018-08-23 15:20:26.424202 7fa4d427c700 10 rgw api priority: s3=5 s3website=4
2018-08-23 15:20:26.424204 7fa4d427c700 10 host=ceph132v12.ceph.int
2018-08-23 15:20:26.424211 7fa4d427c700 20 subdomain= domain= in_hosted_domain=0 in_hosted_domain_s3website=0
2018-08-23 15:20:26.424215 7fa4d427c700 20 final domain/bucket subdomain= domain= in_hosted_domain=0 in_hosted_domain_s3website=0 s->info.domain= s->info.request_uri=/
2018-08-23 15:20:26.424264 7fa4d427c700 20 get_handler handler=26RGWHandler_REST_Service_S3
2018-08-23 15:20:26.424270 7fa4d427c700 10 handler=26RGWHandler_REST_Service_S3
2018-08-23 15:20:26.424272 7fa4d427c700 2 req 9:0.000134:s3:GET /::getting op 0
2018-08-23 15:20:26.424280 7fa4d427c700 10 op=26RGWListBuckets_ObjStore_S3
2018-08-23 15:20:26.424282 7fa4d427c700 2 req 9:0.000144:s3:GET /:list_buckets:verifying requester
2018-08-23 15:20:26.424289 7fa4d427c700 20 rgw::auth::StrategyRegistry::s3_main_strategy_t: trying rgw::auth::s3::AWSAuthStrategy
2018-08-23 15:20:26.424292 7fa4d427c700 20 rgw::auth::s3::AWSAuthStrategy: trying rgw::auth::s3::S3AnonymousEngine
2018-08-23 15:20:26.424296 7fa4d427c700 20 rgw::auth::s3::S3AnonymousEngine denied with reason=-1
2018-08-23 15:20:26.424304 7fa4d427c700 20 rgw::auth::s3::AWSAuthStrategy: trying rgw::auth::s3::AWSv2ExternalAuthStrategy
2018-08-23 15:20:26.424306 7fa4d427c700 20 rgw::auth::s3::AWSv2ExternalAuthStrategy: trying rgw::auth::s3::LDAPEngine
2018-08-23 15:20:26.424332 7fa4d427c700 10 get_canon_resource(): dest=/
2018-08-23 15:20:26.424335 7fa4d427c700 10 string_to_sign:
GET
Thu, 23 Aug 2018 12:20:20 GMT
/
2018-08-23 15:20:26.425295 7fa4d427c700 12 auth search filter: (cn=cephldap)
2018-08-23 15:20:26.426999 7fa4d427c700 5 auth ldap_search_s error uid=cephldap ldap err=1
2018-08-23 15:20:26.442038 7fa4d427c700 5 auth ldap_search_s error uid=cephldap ldap err=1
2018-08-23 15:20:26.442066 7fa4d427c700 20 rgw::auth::s3::LDAPEngine denied with reason=-13
2018-08-23 15:20:26.442071 7fa4d427c700 20 rgw::auth::s3::AWSv2ExternalAuthStrategy denied with reason=-13
2018-08-23 15:20:26.442073 7fa4d427c700 20 rgw::auth::s3::AWSAuthStrategy: trying rgw::auth::s3::LocalEngine
2018-08-23 15:20:26.442100 7fa4d427c700 10 get_canon_resource(): dest=/
2018-08-23 15:20:26.442103 7fa4d427c700 10 string_to_sign:
GET
Thu, 23 Aug 2018 12:20:20 GMT
/
2018-08-23 15:20:26.442164 7fa4d427c700 20 get_system_obj_state: rctx=0x7fa4d4273ac0 obj=default.rgw.meta:users.keys:ewogICAgIlJHV19UT0tFTiI6IHsKICAgICAgICAidmVyc2lvbiI6IDEsCiAgICAgICAgInR5cGUiOiAiYWQiLAogICAgICAgICJpZCI6ICJjZXBobGRhcCIsCiAgICAgICAgImtleSI6ICJwYXNzd29yZCIKICAgIH0KfQo= state=0x5563c351ef60 s->prefetch_data=0
2018-08-23 15:20:26.442182 7fa4d427c700 10 cache get: name=default.rgw.meta+users.keys+ewogICAgIlJHV19UT0tFTiI6IHsKICAgICAgICAidmVyc2lvbiI6IDEsCiAgICAgICAgInR5cGUiOiAiYWQiLAogICAgICAgICJpZCI6ICJjZXBobGRhcCIsCiAgICAgICAgImtleSI6ICJwYXNzd29yZCIKICAgIH0KfQo= : type miss (requested=0x6, cached=0x0)
2018-08-23 15:20:26.444163 7fa4d427c700 10 moving default.rgw.meta+users.keys+ewogICAgIlJHV19UT0tFTiI6IHsKICAgICAgICAidmVyc2lvbiI6IDEsCiAgICAgICAgInR5cGUiOiAiYWQiLAogICAgICAgICJpZCI6ICJjZXBobGRhcCIsCiAgICAgICAgImtleSI6ICJwYXNzd29yZCIKICAgIH0KfQo= to cache LRU end
2018-08-23 15:20:26.444182 7fa4d427c700 5 error reading user info, uid=ewogICAgIlJHV19UT0tFTiI6IHsKICAgICAgICAidmVyc2lvbiI6IDEsCiAgICAgICAgInR5cGUiOiAiYWQiLAogICAgICAgICJpZCI6ICJjZXBobGRhcCIsCiAgICAgICAgImtleSI6ICJwYXNzd29yZCIKICAgIH0KfQo= can't authenticate
2018-08-23 15:20:26.444186 7fa4d427c700 20 rgw::auth::s3::LocalEngine denied with reason=-2028
2018-08-23 15:20:26.444189 7fa4d427c700 20 rgw::auth::s3::AWSAuthStrategy denied with reason=-13
2018-08-23 15:20:26.444191 7fa4d427c700 20 rgw::auth::StrategyRegistry::s3_main_strategy_t: trying rgw::auth::s3::AWSAuthStrategy
2018-08-23 15:20:26.444194 7fa4d427c700 20 rgw::auth::s3::AWSAuthStrategy: trying rgw::auth::s3::S3AnonymousEngine
2018-08-23 15:20:26.444198 7fa4d427c700 20 rgw::auth::s3::S3AnonymousEngine denied with reason=-1
2018-08-23 15:20:26.444200 7fa4d427c700 20 rgw::auth::s3::AWSAuthStrategy: trying rgw::auth::s3::AWSv2ExternalAuthStrategy
2018-08-23 15:20:26.444202 7fa4d427c700 20 rgw::auth::s3::AWSv2ExternalAuthStrategy: trying rgw::auth::s3::LDAPEngine
2018-08-23 15:20:26.444223 7fa4d427c700 10 get_canon_resource(): dest=/
2018-08-23 15:20:26.444225 7fa4d427c700 10 string_to_sign:
GET
Thu, 23 Aug 2018 12:20:20 GMT
/
2018-08-23 15:20:26.444630 7fa4d427c700 12 auth search filter: (cn=cephldap)
2018-08-23 15:20:26.445286 7fa4d427c700 5 auth ldap_search_s error uid=cephldap ldap err=1
2018-08-23 15:20:26.455836 7fa4d427c700 5 auth ldap_search_s error uid=cephldap ldap err=1
2018-08-23 15:20:26.455864 7fa4d427c700 20 rgw::auth::s3::LDAPEngine denied with reason=-13
2018-08-23 15:20:26.455869 7fa4d427c700 20 rgw::auth::s3::AWSv2ExternalAuthStrategy denied with reason=-13
2018-08-23 15:20:26.455871 7fa4d427c700 20 rgw::auth::s3::AWSAuthStrategy: trying rgw::auth::s3::LocalEngine
2018-08-23 15:20:26.455894 7fa4d427c700 10 get_canon_resource(): dest=/
2018-08-23 15:20:26.455898 7fa4d427c700 10 string_to_sign:
GET
Thu, 23 Aug 2018 12:20:20 GMT
/
2018-08-23 15:20:26.455909 7fa4d427c700 20 get_system_obj_state: rctx=0x7fa4d4273ac0 obj=default.rgw.meta:users.keys:ewogICAgIlJHV19UT0tFTiI6IHsKICAgICAgICAidmVyc2lvbiI6IDEsCiAgICAgICAgInR5cGUiOiAiYWQiLAogICAgICAgICJpZCI6ICJjZXBobGRhcCIsCiAgICAgICAgImtleSI6ICJwYXNzd29yZCIKICAgIH0KfQo= state=0x5563c351ef60 s->prefetch_data=0
2018-08-23 15:20:26.455918 7fa4d427c700 10 cache get: name=default.rgw.meta+users.keys+ewogICAgIlJHV19UT0tFTiI6IHsKICAgICAgICAidmVyc2lvbiI6IDEsCiAgICAgICAgInR5cGUiOiAiYWQiLAogICAgICAgICJpZCI6ICJjZXBobGRhcCIsCiAgICAgICAgImtleSI6ICJwYXNzd29yZCIKICAgIH0KfQo= : type miss (requested=0x6, cached=0x0)
2018-08-23 15:20:26.457111 7fa4d427c700 10 cache put: name=default.rgw.meta+users.keys+ewogICAgIlJHV19UT0tFTiI6IHsKICAgICAgICAidmVyc2lvbiI6IDEsCiAgICAgICAgInR5cGUiOiAiYWQiLAogICAgICAgICJpZCI6ICJjZXBobGRhcCIsCiAgICAgICAgImtleSI6ICJwYXNzd29yZCIKICAgIH0KfQo= info.flags=0x0
2018-08-23 15:20:26.457120 7fa4d427c700 10 moving default.rgw.meta+users.keys+ewogICAgIlJHV19UT0tFTiI6IHsKICAgICAgICAidmVyc2lvbiI6IDEsCiAgICAgICAgInR5cGUiOiAiYWQiLAogICAgICAgICJpZCI6ICJjZXBobGRhcCIsCiAgICAgICAgImtleSI6ICJwYXNzd29yZCIKICAgIH0KfQo= to cache LRU end
2018-08-23 15:20:26.457138 7fa4d427c700 5 error reading user info, uid=ewogICAgIlJHV19UT0tFTiI6IHsKICAgICAgICAidmVyc2lvbiI6IDEsCiAgICAgICAgInR5cGUiOiAiYWQiLAogICAgICAgICJpZCI6ICJjZXBobGRhcCIsCiAgICAgICAgImtleSI6ICJwYXNzd29yZCIKICAgIH0KfQo= can't authenticate
2018-08-23 15:20:26.457154 7fa4d427c700 20 rgw::auth::s3::LocalEngine denied with reason=-2028
2018-08-23 15:20:26.457159 7fa4d427c700 20 rgw::auth::s3::AWSAuthStrategy denied with reason=-13
2018-08-23 15:20:26.457161 7fa4d427c700 5 Failed the auth strategy, reason=-13
2018-08-23 15:20:26.457163 7fa4d427c700 10 failed to authorize request
2018-08-23 15:20:26.457165 7fa4d427c700 20 handler->ERRORHANDLER: err_no=-13 new_err_no=-13
2018-08-23 15:20:26.457300 7fa4d427c700 2 req 9:0.033161:s3:GET /:list_buckets:op status=0
2018-08-23 15:20:26.457307 7fa4d427c700 2 req 9:0.033169:s3:GET /:list_buckets:http status=403
2018-08-23 15:20:26.457312 7fa4d427c700 1 ====== req done req=0x7fa4d42761f0 op status=0 http_status=403 ======
2018-08-23 15:20:26.457326 7fa4d427c700 20 process_request() returned -13
2018-08-23 15:20:26.457411 7fa4d427c700 1 civetweb: 0x5563c3739000: 10.201.0.131 - - [23/Aug/2018:15:20:26 +0300] "GET / HTTP/1.1" 1 0 - Boto/2.49.0 Python/2.7.10 Windows/7
2018-08-23 15:20:30.973550 7fa4f48d7700 2 RGWDataChangesLog::ChangesRenewThread: start
In the logs the following line indicates
5 auth ldap_search_s error uid=cephldap ldap err=1
That it tried to contact ldap and returned that error, are you sure the ldap config settings in ceph.conf ie. binddn and searchdn are correct?
Yes i sure the ldap config correct. I moved rgw_ldap_(settings) to [global] section in config file ceph.conf and remov in string rgw_ldap_uri = "ldap://adceph.ceph.int:389" port ":389" and change rgw_ldap_secret = "Password" on rgw_ldap_secret = /path/to/pass and authentication began to work.
Related
I think this question can be rewritten to "Using Spring Boot and keycloak-spring-boot-starter, what happens after KeycloakSpringBootConfigResolver.resolve()?"
I have a custom keycloak config resolver:
public class CustomKeycloakConfigResolver
extends KeycloakSpringBootConfigResolver {
...
#Override
public KeycloakDeployment resolve(final HttpFacade.Request request) {
LOGGER.debug("-----------------------------------------------");
LOGGER.debug("Resolving Deployment for {}", request.getURI());
...
LOGGER.trace("---------- CREATING KEYCLOAK DEPLOYMENT ---------");
KeycloakDeployment keycloakDeployment =
KeycloakDeploymentBuilder.build(adapterConfig);
LOGGER.trace("---------- /CREATED KEYCLOAK DEPLOYMENT ---------");
return keycloakDeployment;
This pulls the KeycloakDeployment configuration from our database instead of from application.properties. Testing on a local docker swarm cluster, it works like a charm (but this is only on one machine, without SSL enabled, etc).
Pushing out to our QA environment (nginx on one machine with TLS termination, REST service on another, Keycloak on another, database provided by RDS), the generation of a KeycloakDeployment goes off without a hitch. This includes reaching out to .well-known/openid-configuration and resolving all of the Keycloak URLs, and printing both of the final trace() statements.
Almost immediately after (within 10-30ms) creating the KeycloakDeployment and returning it to the keycloak-spring-boot-starter framework, I receive a SocketTimeoutException exception. I can't tell from the exception what the system is trying to do when throws this exception, and I haven't been able to tell from https://github.com/keycloak/keycloak what the workflow is after the deployment is "resolved()".
So - what happens next?
A secured method is accessed
Spring Boot auth hands off to Keycloak auth
Keycloak auth generates a custom KeycloakDeployment
KeycloakDeployment is resolved - reaches out to Keycloak service and obtains the OIDC configuration
KeycloakDeployment is passed back to Keycloak auth framework
... Something happens that throws an immediate socket timeout exception...
Method is never invoked
How do I figure out what's happening in step 6? I find it hard to believe it's an actual socket timeout after only 20ms, and everything I think it should be accessing is up and responsive. But I'm willing to be wrong...
---- Original Question ----
I'm trying to get Keycloak working with a Spring Boot REST service behind an nginx proxy. TLS is terminated at the nginx server. Everything is in docker containers, but on separate machines (no kube, no swarm, etc).
Everything seems good. I can login to the master realm, create a new realm, add users, etc. However when the REST service tries to contact the Keycloak server (through the nginx proxy), I'm getting an SSL timeout error:
2022-03-22 18:59:13.384 INFO 26 --- [nio-8080-exec-3] o.keycloak.adapters.KeycloakDeployment : Loaded URLs from https://hostname/auth/realms/myrealm/.well-known/openid-configuration
javax.net.ssl|WARNING|18|http-nio-8080-exec-3|2022-03-22 18:59:13.409 UTC|SSLSocketImpl.java:1672|handling exception (
"throwable" : {
java.net.SocketTimeoutException: Read timed out
at java.base/sun.nio.ch.NioSocketImpl.timedRead(NioSocketImpl.java:283)
...
Thing is, this "timeout" happens almost instantaneously after the .well-known/openid-configuration response, so I'm skeptical it's even actually a timeout, unless the threshold is set to like 10ms by default or something.
I cranked up javax.net logging with System.setProperty("javax.net.debug", "ssl:all");, and I can't see anything obvious:
2022-03-22 18:59:13.384 INFO 26 --- [nio-8080-exec-3] o.keycloak.adapters.KeycloakDeployment : Loaded URLs from https://hostname/auth/realms/myrealm/.well-known/openid-configuration
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.385 UTC|SSLSocketOutputRecord.java:331|WRITE: TLSv1.2 application_data, length = 11
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.385 UTC|SSLCipher.java:1770|Plaintext before ENCRYPTION (
0000: 07 00 00 00 03 63 6F 6D 6D 69 74 .....commit
)
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.388 UTC|SSLSocketOutputRecord.java:346|Raw write (
0000: 17 03 03 00 23 00 00 00 00 00 00 00 80 9C 76 46 ....#.........vF
0010: 44 FA F9 3A A4 9B A1 B2 D8 9B 6A 69 76 C7 1A 3D D..:......jiv..=
0020: 94 C4 40 D2 D8 F2 E4 7E ..#.....
)
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.388 UTC|SSLSocketInputRecord.java:488|Raw read (
0000: 17 03 03 00 23 ....#
)
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.388 UTC|SSLSocketInputRecord.java:214|READ: TLSv1.2 application_data, length = 35
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.388 UTC|SSLSocketInputRecord.java:488|Raw read (
0000: 15 13 12 41 88 AD 18 6F B8 5E 25 90 9D BA 23 BF ...A...o.^%...#.
0010: B3 A5 A9 5E 61 FA 77 BD AE A4 C0 57 B2 1D 5B 18 ...^a.w....W..[.
0020: E8 C7 77 ..w
)
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.388 UTC|SSLSocketInputRecord.java:247|READ: TLSv1.2 application_data, length = 35
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.388 UTC|SSLCipher.java:1672|Plaintext after DECRYPTION (
0000: 07 00 00 01 00 00 00 00 00 00 00 ...........
)
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.388 UTC|SSLSocketOutputRecord.java:331|WRITE: TLSv1.2 application_data, length = 21
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.389 UTC|SSLCipher.java:1770|Plaintext before ENCRYPTION (
0000: 11 00 00 00 03 53 45 54 20 61 75 74 6F 63 6F 6D .....SET autocom
0010: 6D 69 74 3D 31 mit=1
)
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.390 UTC|SSLSocketOutputRecord.java:346|Raw write (
0000: 17 03 03 00 2D 00 00 00 00 00 00 00 81 6B 87 27 ....-........k.'
0010: 9C 91 53 E2 F8 70 1C D4 FA F3 4A 79 1B B0 11 05 ..S..p....Jy....
0020: 13 3E 4F 10 A8 E8 43 B3 BB FA 1E 48 82 DF 59 25 .>O...C....H..Y%
0030: CF 9D ..
)
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.392 UTC|SSLSocketInputRecord.java:488|Raw read (
0000: 17 03 03 00 23 ....#
)
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.392 UTC|SSLSocketInputRecord.java:214|READ: TLSv1.2 application_data, length = 35
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.392 UTC|SSLSocketInputRecord.java:488|Raw read (
0000: 15 13 12 41 88 AD 18 70 E3 20 7E 21 DA B0 24 28 ...A...p. .!..$(
0010: EF 6D EB BC 5C CE 5D 94 1D BC 04 BB F9 D1 3D 72 .m..\.].......=r
0020: 0C 71 83 .q.
)
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.392 UTC|SSLSocketInputRecord.java:247|READ: TLSv1.2 application_data, length = 35
javax.net.ssl|DEBUG|18|http-nio-8080-exec-3|2022-03-22 18:59:13.393 UTC|SSLCipher.java:1672|Plaintext after DECRYPTION (
0000: 07 00 00 01 00 00 00 02 00 00 00 ...........
)
javax.net.ssl|WARNING|18|http-nio-8080-exec-3|2022-03-22 18:59:13.409 UTC|SSLSocketImpl.java:1672|handling exception (
"throwable" : {
java.net.SocketTimeoutException: Read timed out
at java.base/sun.nio.ch.NioSocketImpl.timedRead(NioSocketImpl.java:283)
...
So between the well-known configuration call and the final timeout exception:
18:59:13.384
18:59:13.409
all of 25ms passes by - seems hard to believe there would be a legitimate timeout exception thrown, but I can't seem to get any more clue as to what is causing the timeout. The keycloak service definitely IS reachable, and responds quite quickly.
Nothing at all in the Keycloak logs, and not terribly much in the nginx logs:
[--- AUTH ---] [22/Mar/2022:19:19:56 +0000] [200] "POST /auth/realms/myrealm/protocol/openid-connect/token HTTP/1.1" "https://web.mycompany.com/"
[--- AUTH ---] [22/Mar/2022:19:19:57 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:19:57 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
2022/03/22 19:19:57 [info] 73#73: *659 client #.#.#.# closed keepalive connection
[--- AUTH ---] [22/Mar/2022:19:19:57 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:19:57 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:19:58 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:19:58 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
2022/03/22 19:19:58 [info] 73#73: *670 client #.#.#.# closed keepalive connection
2022/03/22 19:19:58 [info] 73#73: *668 client #.#.#.# closed keepalive connection
[--- AUTH ---] [22/Mar/2022:19:19:58 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:19:58 +0000] [200] "GET /auth/realms/myrealm/protocol/openid-connect/certs HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:19:58 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:19:58 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:19:59 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:19:59 +0000] [200] "GET /auth/realms/myrealm/protocol/openid-connect/certs HTTP/1.1" "-"
2022/03/22 19:19:59 [info] 73#73: *677 client #.#.#.# closed keepalive connection
2022/03/22 19:19:59 [info] 73#73: *675 client #.#.#.# closed keepalive connection
[--- AUTH ---] [22/Mar/2022:19:19:59 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:19:59 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:19:59 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:20:00 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
2022/03/22 19:20:00 [info] 73#73: *664 client #.#.#.# closed keepalive connection
2022/03/22 19:20:00 [info] 73#73: *666 client #.#.#.# closed keepalive connection
2022/03/22 19:20:00 [info] 73#73: *672 client #.#.#.# closed keepalive connection
2022/03/22 19:20:00 [info] 73#73: *682 client #.#.#.# closed keepalive connection
2022/03/22 19:20:00 [info] 73#73: *684 client #.#.#.# closed keepalive connection
2022/03/22 19:20:00 [info] 74#74: *686 client #.#.#.# closed keepalive connection
[--- AUTH ---] [22/Mar/2022:19:20:00 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:20:00 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:20:01 +0000] [200] "GET /auth/realms/myrealm/.well-known/openid-configuration HTTP/1.1" "-"
[--- AUTH ---] [22/Mar/2022:19:20:01 +0000] [200] "GET /auth/realms/myrealm/protocol/openid-connect/certs HTTP/1.1" "-"
[--- REST ---] [22/Mar/2022:19:20:01 +0000] [401] "GET /api/v1/stuff HTTP/1.1" "https://web.mycompany.com/"
Any help as to what's going on?
Other notes:
I've gone through the Setting Up a load balancer or proxy instructions from Keycloak. Specifically, the nginx server has the following:
upstream AUTH {
server #.#.#.#:8080;
server #.#.#.#:8080;
}
...
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $http_host;
proxy_pass http://AUTH;
I think that covers bullet points 1 and 2.
Bullet point 3 is covered by the keycloak server. The standalone-ha.xml file has:
<subsystem xmlns="urn:jboss:domain:undertow:12.0" default-server="default-server" default-virtual-host="default-host" default-servlet-container="default" default-security-domain="other" statistics-enabled="true">
<buffer-cache name="default"/>
<server name="default-server">
<ajp-listener name="ajp" socket-binding="ajp"/>
<http-listener name="default" socket-binding="http" redirect-socket="https" proxy-address-forwarding="${env.PROXY_ADDRESS_FORWARDING:false}" enable-http2="true"/>
<https-listener name="https" socket-binding="https" ssl-context="applicationSSC" proxy-address-forwarding="${env.PROXY_ADDRESS_FORWARDING:false}" enable-http2="true"/>
<host name="default-host" alias="localhost">
<location name="/" handler="welcome-content"/>
<http-invoker http-authentication-factory="application-http-authentication"/>
</host>
</server>
and the container is launched with the environment variable
PROXY_ADDRESS_FORWARDING=true
I've verified with a false login that Keycloak is seeing the end user's IP address rather than the nginx server:
15:17:07,304 WARN [org.keycloak.events] (default task-14) type=LOGIN_ERROR, realmId=master, clientId=security-admin-console, userId=null, ipAddress=#.#.#.#, error=user_not_found, auth_method=openid-connect, auth_type=code, redirect_uri=https://host.name/auth/admin/master/console/#/realms/MyRealm/login-settings, code_id=..., username=foo, authSessionParentId=..., authSessionTabId=...
Where #.#.#.# is my IP address.
I am having a problem with Google's SMTP servers. They reject my SMTP server's IP for no valid reason. My server complies with all the necessary rules to deliver the message but Google rejects it by IP without giving me details and I cannot find support either. I have written to postmaster#gmail.com but got no response. My server sends notifications to the users of the system, it does not do SPAM and apparently everything is correct. I don't see a valid reason for this crash, and I can't find a way to fix it. I would like to know if the same thing happened to someone and how they could solve it. Next I copy the console with the delivery attempt and additionally some DNS checks that show that apparently there is no problem on my server:
root#venabili:~# hostname -f
venabili.tecnologica.com.ar
root#venabili:~# id
uid=0(root) gid=0(root) grupos=0(root)
root#venabili:~# ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 200.69.236.179 netmask 255.255.255.0 broadcast 200.69.236.255
inet6 fe80::f816:3eff:fe27:b8e1 prefixlen 64 scopeid 0x20<link>
ether fa:16:3e:27:b8:e1 txqueuelen 1000 (Ethernet)
RX packets 302342269 bytes 32703331063 (30.4 GiB)
RX errors 0 dropped 17 overruns 0 frame 0
TX packets 75025298 bytes 12670842456 (11.8 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root#venabili:~# nslookup
> server 8.8.8.8
Default server: 8.8.8.8
Address: 8.8.8.8#53
> set type=mx
> tecnologica.com.ar
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
tecnologica.com.ar mail exchanger = 10 venabili.tecnologica.com.ar.
Authoritative answers can be found from:
> set type=a
> venabili.tecnologica.com.ar
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: venabili.tecnologica.com.ar
Address: 200.69.236.179
> set type=aaaa
> venabili.tecnologica.com.ar
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: venabili.tecnologica.com.ar
Address: fe80::f816:3eff:fe27:b8e1
> set type=ptr
> 200.69.236.179
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
179.236.69.200.in-addr.arpa name = venabili.tecnologica.com.ar.
Authoritative answers can be found from:
> set type=txt
> tecnologica.com.ar
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
tecnologica.com.ar text = "v=spf1 a mx ip4:200.69.236.179 ip6:fe80::f816:3eff:fe27:b8e1 ~all"
Authoritative answers can be found from:
> set type=txt
> default._domainkey.tecnologica.com.ar
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
default._domainkey.tecnologica.com.ar text = "v=DKIM1; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAz+GrX8vxp9W51ehJuixhL5AbjmCgcN2h7KqMiLI8LMUfmpWPP1GIhxlWCieFUVMOAQGlQrImuFE3kk/qLOgyumzUTRBwxlNX+7tix7dlBclXAWq8SjB9SbbAcPKkTBAq0pvXvp4l4qTCFnfVXAs1g/lCywlJrbfAFVVXWdN44ElFz+bD4YRYsXSmz//L1uFU7YE" "zkFUvbMtwBOL1xRvjAFXH4xQ7/vkHX6+OIxnm47vO/a2CqFVXok0FhAj44BmlBT+Py0x0SP8jsm+xhnLc238ZIsGylTwCb0Zbl3DR9bKGBy9FqXoUyRIzWKEkAtwaKq7qeBO3oRT4kQOKEOog2QIDAQAB"
Authoritative answers can be found from:
> _dmarc.tecnologica.com.ar
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
_dmarc.tecnologica.com.ar text = "v=DMARC1; p=reject; rua=mailto:postmaster#tecnologica.com.ar; ruf=mailto:postmaster#tecnologica.com.ar"
Authoritative answers can be found from:
> _smtp._tls.tecnologica.com.ar
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
_smtp._tls.tecnologica.com.ar text = "v=TLSRPTv1; rua=mailto:postmaster#tecnologica.com.ar"
Authoritative answers can be found from:
> _mta-sts.tecnologica.com.ar
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
_mta-sts.tecnologica.com.ar text = "v=STSv1; id=20200918192500"
Authoritative answers can be found from:
> set type=cname
> mta-sts.tecnologica.com.ar
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
mta-sts.tecnologica.com.ar canonical name = venabili.tecnologica.com.ar.
Authoritative answers can be found from:
> exit
root#venabili:~# openssl s_client -connect mta-sts.tecnologica.com.ar:443
CONNECTED(00000004)
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
verify return:1
depth=0 CN = mta-sts.tecnologica.com.ar
verify return:1
---
Certificate chain
0 s:CN = mta-sts.tecnologica.com.ar
i:C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
1 s:C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
i:O = Digital Signature Trust Co., CN = DST Root CA X3
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIFbTCCBFWgAwIBAgISBC7Vr1sblDEJHYgxBtfro6xcMA0GCSqGSIb3DQEBCwUA
MEoxCzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeXB0MSMwIQYDVQQD
ExpMZXQncyBFbmNyeXB0IEF1dGhvcml0eSBYMzAeFw0yMDA5MTgyMzM4MjdaFw0y
MDEyMTcyMzM4MjdaMCUxIzAhBgNVBAMTGm10YS1zdHMudGVjbm9sb2dpY2EuY29t
LmFyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5glA7vEmuS0EzKhn
w9IfLPHHertYYOYx54t/2zr8G1pSmkCjrOlfV+YHwIuWeehxDUz/ezy1JXyK11kd
raDd71MoBd9mV12fjITO99oDpkYu9g09TxJ9rpIEkU8LRGkgjfDGBBtf5X5Za+Ah
gWbJ4JudVoykVZ00riQsZzbfJ8FNZcwEgErWCZCBL45tR7tfeFlXTJGFhyszqQN+
r4gS3C/JpsObIMaoqmkJrO5YUGcfGvqDOG3INthp2L9/t743OfYUGTqRFu09Rq5S
xwEYxR8GksaLwzMWOIRelMP4W5F9ce7hhdxU68cK4j9rHXaaeNXLySeMs7K9C2vt
p1nnowIDAQABo4ICcDCCAmwwDgYDVR0PAQH/BAQDAgWgMB0GA1UdJQQWMBQGCCsG
AQUFBwMBBggrBgEFBQcDAjAMBgNVHRMBAf8EAjAAMB0GA1UdDgQWBBQ1A7mXXvtb
eS6ZYRtw4EA7WhJ3/zAfBgNVHSMEGDAWgBSoSmpjBH3duubRObemRWXv86jsoTBv
BggrBgEFBQcBAQRjMGEwLgYIKwYBBQUHMAGGImh0dHA6Ly9vY3NwLmludC14My5s
ZXRzZW5jcnlwdC5vcmcwLwYIKwYBBQUHMAKGI2h0dHA6Ly9jZXJ0LmludC14My5s
ZXRzZW5jcnlwdC5vcmcvMCUGA1UdEQQeMByCGm10YS1zdHMudGVjbm9sb2dpY2Eu
Y29tLmFyMEwGA1UdIARFMEMwCAYGZ4EMAQIBMDcGCysGAQQBgt8TAQEBMCgwJgYI
KwYBBQUHAgEWGmh0dHA6Ly9jcHMubGV0c2VuY3J5cHQub3JnMIIBBQYKKwYBBAHW
eQIEAgSB9gSB8wDxAHcA5xLysDd+GmL7jskMYYTx6ns3y1YdESZb8+DzS/JBVG4A
AAF0o8xFcQAABAMASDBGAiEAlc3Q8FEkd5ZUayxVfeorQv9+Jt1OSgOOP+jqVw5K
sskCIQCE0Hx7YDWcJ9o4Cck50WP7UtA/qRgmfn1fVIHyEZMftwB2AAe3XBvlfWj/
8bDGHSMVx7rmV3xXlLdq7rxhOhpp06IcAAABdKPMRZcAAAQDAEcwRQIgBVUd9xxC
DVX/kr0+308ra9YOqJC/yvBJnktxWg6YUVMCIQCR14/ouxc+Ydm4tePVBjBnmpRq
QzQEDYrd+4R7JjpiCjANBgkqhkiG9w0BAQsFAAOCAQEAlCnRwvP7wNRHTzB5N9/N
2cBPuVxKbvf1rHwusXYzQBVlyM6grEvjTgd5V/C+we1ueDUp991tP3z5AAksIGWM
/ssDlK0VSxv9PIzC1LxDK39Sl+P8xkuGj0zSDYg321sFjFyZLashP+xFYyzx3QdD
9h65J0uB/BigWOIN9sK1vLVhIB4yqV190vucyMamJBZ1dvSaYCi52dCgEEsAxM3v
LksETYgpSqB4+6zB2ae3/FN2/m3vyWCdFv1fL19hIidKjwIYhIKVOLKTQCYvCd+p
srhlTtnRf8i+P8Dni9xKmKSFwSGc8L+AS0AfTh6M/+IEPOO2zJsp1R/PBWgiy42v
fw==
-----END CERTIFICATE-----
subject=CN = mta-sts.tecnologica.com.ar
issuer=C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: RSA-PSS
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 3203 bytes and written 403 bytes
Verification: OK
---
New, TLSv1.2, Cipher is ECDHE-RSA-CHACHA20-POLY1305
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol : TLSv1.2
Cipher : ECDHE-RSA-CHACHA20-POLY1305
Session-ID: 38FDD25BCB4C28F5364CA3418C05D13F279E62882E594190276850599BB67EAB
Session-ID-ctx:
Master-Key: 41AEF29EC1545AAE8C53958032EFF464E237232D8AA9D22CF9513297DFFBA40645226685FE58FEC782DA20CDFFEB5EDB
PSK identity: None
PSK identity hint: None
SRP username: None
TLS session ticket lifetime hint: 300 (seconds)
TLS session ticket:
0000 - 5f 78 fa 6f 3a 54 9c c2-f0 8e b2 b7 70 13 05 d4 _x.o:T......p...
0010 - 4b 39 84 62 c7 cb 96 f8-89 5c 27 09 6c 2b aa ad K9.b.....\'.l+..
0020 - 52 22 36 d6 a3 0b 8b 5e-ed 4b 78 f5 49 61 47 69 R"6....^.Kx.IaGi
0030 - c9 e7 41 88 c2 e6 29 86-b5 52 a9 8f 56 3f 79 3e ..A...)..R..V?y>
0040 - 14 bd b5 24 ca c5 f7 a4-ab b9 f9 26 dc 1c 71 7a ...$.......&..qz
0050 - ab 5a a2 a9 76 df 61 70-a5 91 5f 69 36 bc 64 69 .Z..v.ap.._i6.di
0060 - 02 b5 4b ba 79 e0 c9 a7-3b e2 a6 30 9b 2b 34 33 ..K.y...;..0.+43
0070 - 02 af 1e 3c 82 90 bc ca-32 b3 57 5b e0 b6 33 b0 ...<....2.W[..3.
0080 - a6 4c dc a8 c9 01 29 cf-98 ba 7c 40 3a ae 4b 04 .L....)...|#:.K.
0090 - 95 66 2f 96 b2 b9 5b f1-b0 f2 b0 6c e4 61 6f d0 .f/...[....l.ao.
00a0 - 98 a2 67 06 c9 22 ef a3-f5 ec 24 ac a2 b1 5f 4e ..g.."....$..._N
Start Time: 1600571394
Timeout : 7200 (sec)
Verify return code: 0 (ok)
Extended master secret: yes
---
GET /.well-known/mta-sts.txt HTTP/1.1
Host: venabili.tecnologica.com.ar
HTTP/1.1 200 OK
Server: nginx/1.14.2
Date: Sun, 20 Sep 2020 03:10:22 GMT
Content-Type: text/plain
Content-Length: 77
Last-Modified: Sat, 19 Sep 2020 14:07:46 GMT
Connection: keep-alive
ETag: "5f6610b2-4d"
Accept-Ranges: bytes
version: STSv1
mode: testing
mx: venabili.tecnologica.com.ar
max_age: 604800
^C
root#venabili:~# openssl s_client -starttls smtp -connect venabili.tecnologica.com.ar:587 -crlf -ign_eof
CONNECTED(00000004)
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
verify return:1
depth=0 CN = venabili.tecnologica.com.ar
verify return:1
---
Certificate chain
0 s:CN = venabili.tecnologica.com.ar
i:C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
1 s:C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
i:O = Digital Signature Trust Co., CN = DST Root CA X3
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIFbzCCBFegAwIBAgISBAyLUnN1zyR0tAMF7k1G3023MA0GCSqGSIb3DQEBCwUA
MEoxCzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeXB0MSMwIQYDVQQD
ExpMZXQncyBFbmNyeXB0IEF1dGhvcml0eSBYMzAeFw0yMDA5MTgyMjMxMjZaFw0y
MDEyMTcyMjMxMjZaMCYxJDAiBgNVBAMTG3ZlbmFiaWxpLnRlY25vbG9naWNhLmNv
bS5hcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL/svQH9FsoQZyGh
krGZLrN3GAzwuAV2IEsYdAixVrVXGPPjA4oTxQDWncBPVh8x6nMstJqq4xP19aBr
pw5P2rcsMvLT9RJ14wGuNzzDcx9uOmR709ZrPpPzZJ4JJnZxQP5dE2jJMrPQ7tnI
3AudscEaAMW8qBLj91jPDiv4LbRHL4xU+w46yZbB6szgb4u567SSKFaVlRQ8tmCt
msIkYdA5mP5/1Z0QN6PgtAzCWECEkn/eRpuTUHliMjgCocwQ3RYkofGrNQ1a4H7F
RgdaQzjCjQ7JdT/pZTYWrejr3alMsFAukRfIH/FMI5v8ojaxzlQOhz46WJiw3qNH
rmjb+G0CAwEAAaOCAnEwggJtMA4GA1UdDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggr
BgEFBQcDAQYIKwYBBQUHAwIwDAYDVR0TAQH/BAIwADAdBgNVHQ4EFgQU91GfsO41
iPZN1SROqwqnCPSN9yIwHwYDVR0jBBgwFoAUqEpqYwR93brm0Tm3pkVl7/Oo7KEw
bwYIKwYBBQUHAQEEYzBhMC4GCCsGAQUFBzABhiJodHRwOi8vb2NzcC5pbnQteDMu
bGV0c2VuY3J5cHQub3JnMC8GCCsGAQUFBzAChiNodHRwOi8vY2VydC5pbnQteDMu
bGV0c2VuY3J5cHQub3JnLzAmBgNVHREEHzAdght2ZW5hYmlsaS50ZWNub2xvZ2lj
YS5jb20uYXIwTAYDVR0gBEUwQzAIBgZngQwBAgEwNwYLKwYBBAGC3xMBAQEwKDAm
BggrBgEFBQcCARYaaHR0cDovL2Nwcy5sZXRzZW5jcnlwdC5vcmcwggEFBgorBgEE
AdZ5AgQCBIH2BIHzAPEAdwDnEvKwN34aYvuOyQxhhPHqezfLVh0RJlvz4PNL8kFU
bgAAAXSjjusOAAAEAwBIMEYCIQDOwhtVW/tkJzexdCpcX2gLXX7axA8Fw4bDURrr
tu/ecQIhAKpdzqz+iWGw9I7pkKfYNjyyLdWojRlT+IYQfR7qxQc4AHYAB7dcG+V9
aP/xsMYdIxXHuuZXfFeUt2ruvGE6GmnTohwAAAF0o47rMwAABAMARzBFAiBUUOSO
S+8ueu2ACk+862qxbAsXylwZAfHhg/7HmEeEQQIhAKq3jqMMSIjTo47t2JXrU58d
PP6E3NwNHOgGCNje4R/nMA0GCSqGSIb3DQEBCwUAA4IBAQAua/T4drS/7xpNmGDV
Xp2iFhSaVsbWeHh5+40POEAy9NvaZ8O4CeNjV3NeV84QI2Jh1PjehebM72K85rCT
7jEOqaJY5vmKrLBVji6MsgryyGLm4Y368nMR3JrXDLUkATgart+jLdsxLbaRsI1t
Gf+BLc6TYb4roGiI7TTjEQDAy2SOGqfOWbAEdVKIEr9P3IBrlOSOl2o8gd97PXQ/
vEmklVM/5zr5l5paInHOidBL8y8qVk2s9AkaQNAS2QTX5+iFl9D1u8z5mz49eKPb
sb9GSFVTm/qe0KHl02qga4/1ANRoNCuKoaE5xxhqyboJwy58qp7opbzipqxbQI0T
N8e/
-----END CERTIFICATE-----
subject=CN = venabili.tecnologica.com.ar
issuer=C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: RSA-PSS
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 3389 bytes and written 432 bytes
Verification: OK
---
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 2048 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---
250 CHUNKING
---
Post-Handshake New Session Ticket arrived:
SSL-Session:
Protocol : TLSv1.3
Cipher : TLS_AES_256_GCM_SHA384
Session-ID: D8A0F5C48FBFE47FAEF6482AC696CBCAB01EB030F683053A41539DCD5B91E593
Session-ID-ctx:
Resumption PSK: 3CACF3832764ACCF8A00FFDAFA9A8771E62C04FCDF1429A85EB2A3AC0F39733F642045E4602CE73F62AEC75745B51392
PSK identity: None
PSK identity hint: None
SRP username: None
TLS session ticket lifetime hint: 7200 (seconds)
TLS session ticket:
0000 - 30 00 51 89 4c df 15 62-da 50 55 37 92 60 65 f2 0.Q.L..b.PU7.`e.
0010 - 05 72 39 3d fb 1e 8a 05-2f 95 6b f0 cd 33 29 b0 .r9=..../.k..3).
0020 - b7 38 89 4f 2f 32 91 66-f7 59 2f 80 43 fc 81 f7 .8.O/2.f.Y/.C...
0030 - c6 53 68 3d d8 69 0d 10-6c 4c 62 9c 81 d9 ec 60 .Sh=.i..lLb....`
0040 - 9f ef a0 95 46 d3 e0 10-29 09 20 ab 48 3b 07 34 ....F...). .H;.4
0050 - 82 d3 0e 39 3d 11 18 e8-9e 44 b7 69 b9 d0 45 2e ...9=....D.i..E.
0060 - 97 4f da 69 aa 89 27 2c-e5 9c 63 39 4b f8 3f 54 .O.i..',..c9K.?T
0070 - 23 1a db 73 ac 7e 78 20-76 f5 67 b9 8f e1 c3 34 #..s.~x v.g....4
0080 - d7 f0 b5 0b 0d c7 dc 80-f6 40 0c 20 3f 8d 16 b7 .........#. ?...
0090 - 3a c2 e2 a9 c1 b6 fd 84-65 7f a5 1c 16 81 60 5a :.......e.....`Z
00a0 - 53 12 3a bf d0 4a 0c 0e-a2 3b 57 ce ad 63 89 e6 S.:..J...;W..c..
00b0 - a7 58 ea 21 f9 2e 04 00-ff 6f a7 40 9d 2c bf 39 .X.!.....o.#.,.9
00c0 - 8d d9 19 c9 e1 05 a6 19-a4 60 06 75 8d 3e 95 89 .........`.u.>..
Start Time: 1600567929
Timeout : 7200 (sec)
Verify return code: 0 (ok)
Extended master secret: no
Max Early Data: 0
---
read R BLOCK
ehlo venabili.tecnologica.com.ar
250-venabili.tecnologica.com.ar
250-PIPELINING
250-SIZE
250-VRFY
250-ETRN
250-AUTH PLAIN LOGIN
250-AUTH=PLAIN LOGIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250-SMTPUTF8
250 CHUNKING
auth login
334 VXNlcm5hbWU6
bm8tcmVzcG9uZGVyQHRlY25vbG9naWNhLmNvbS5hcg==
334 UGFzc3dvcmQ6
!!!
235 2.7.0 Authentication successful
mail from: no-responder#tecnologica.com.ar
250 2.1.0 Ok
rcpt to: jmouriz#gmail.com
250 2.1.5 Ok
data
354 End data with <CR><LF>.<CR><LF>
from: root <no-responder#tecnologica.com.ar>
to: Juan Manuel Mouriz <jmouriz#gmail.com>
subject: Mensaje de prueba
Hola, este es un mensaje de prueba
.
250 2.0.0 Ok: queued as 5E50844853
quit
221 2.0.0 Bye
closed
root#venabili:~# grep 5E50844853 /var/log/mail.log
Sep 19 23:18:54 venabili postfix/submission/smtpd[7994]: 5E50844853: client=venabili.tecnologica.com.ar[200.69.236.179], sasl_method=login, sasl_username=no-responder#tecnologica.com.ar
Sep 19 23:20:35 venabili postfix/cleanup[8543]: 5E50844853: message-id=<20200920021854.5E50844853#venabili.tecnologica.com.ar>
Sep 19 23:20:35 venabili postfix/qmgr[5677]: 5E50844853: from=<no-responder#tecnologica.com.ar>, size=554, nrcpt=1 (queue active)
Sep 19 23:20:35 venabili postfix/cleanup[8543]: 6F3BE4485D: message-id=<20200920021854.5E50844853#venabili.tecnologica.com.ar>
Sep 19 23:20:35 venabili amavis[26666]: (26666-19) Passed CLEAN {RelayedOutbound}, ORIGINATING LOCAL [200.69.236.179]:55833 [200.69.236.179] <no-responder#tecnologica.com.ar> -> <jmouriz#gmail.com>, Queue-ID: 5E50844853, Message-ID: <20200920021854.5E50844853#venabili.tecnologica.com.ar>, mail_id: bcEyyqxUQvNK, Hits: -1, size: 554, queued_as: 6F3BE4485D, dkim_new=default:tecnologica.com.ar, 329 ms
Sep 19 23:20:35 venabili postfix/smtp[8676]: 5E50844853: to=<jmouriz#gmail.com>, relay=127.0.0.1[127.0.0.1]:10026, delay=115, delays=115/0.02/0.01/0.32, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10027): 250 2.0.0 Ok: queued as 6F3BE4485D)
Sep 19 23:20:35 venabili postfix/qmgr[5677]: 5E50844853: removed
root#venabili:~# grep 6F3BE4485D /var/log/mail.log
Sep 19 23:20:35 venabili postfix/smtpd[8679]: 6F3BE4485D: client=localhost[127.0.0.1]
Sep 19 23:20:35 venabili postfix/cleanup[8543]: 6F3BE4485D: message-id=<20200920021854.5E50844853#venabili.tecnologica.com.ar>
Sep 19 23:20:35 venabili postfix/qmgr[5677]: 6F3BE4485D: from=<no-responder#tecnologica.com.ar>, size=1625, nrcpt=1 (queue active)
Sep 19 23:20:35 venabili amavis[26666]: (26666-19) Passed CLEAN {RelayedOutbound}, ORIGINATING LOCAL [200.69.236.179]:55833 [200.69.236.179] <no-responder#tecnologica.com.ar> -> <jmouriz#gmail.com>, Queue-ID: 5E50844853, Message-ID: <20200920021854.5E50844853#venabili.tecnologica.com.ar>, mail_id: bcEyyqxUQvNK, Hits: -1, size: 554, queued_as: 6F3BE4485D, dkim_new=default:tecnologica.com.ar, 329 ms
Sep 19 23:20:35 venabili postfix/smtp[8676]: 5E50844853: to=<jmouriz#gmail.com>, relay=127.0.0.1[127.0.0.1]:10026, delay=115, delays=115/0.02/0.01/0.32, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10027): 250 2.0.0 Ok: queued as 6F3BE4485D)
Sep 19 23:20:37 venabili postfix/smtp[8680]: 6F3BE4485D: to=<jmouriz#gmail.com>, relay=gmail-smtp-in.l.google.com[172.217.192.26]:25, delay=1.7, delays=0.02/0.02/0.88/0.8, dsn=5.7.1, status=bounced (host gmail-smtp-in.l.google.com[172.217.192.26] said: 550-5.7.1 [200.69.236.179] The IP you're using to send mail is not authorized to 550-5.7.1 send email directly to our servers. Please use the SMTP relay at your 550-5.7.1 service provider instead. Learn more at 550 5.7.1 https://support.google.com/mail/?p=NotAuthorizedError a44si4686321qtk.87 - gsmtp (in reply to end of DATA command))
Sep 19 23:20:37 venabili postfix/bounce[8681]: 6F3BE4485D: sender non-delivery notification: 32EF64485E
Sep 19 23:20:37 venabili postfix/qmgr[5677]: 6F3BE4485D: removed
root#venabili:~#
The domain in question is tecnologica.com.ar and I leave a link to some verifications where it is seen that the RR SPF, DKIM, DMARC, _SMTP._TLS, _MTA-STS, MTA-STS, CAA and PTR are correct and it is not a open relay:
https://mxtoolbox.com/domain/tecnologica.com.ar
The certificates are signed by Let's Encrypt. The host name matches the certificate. The classes are correct. And finally, I do not SPAM. I would greatly appreciate a help because at this point I am completely disoriented and can't find what else to do.
I am not looking for a solution but rather where I can find it.
Thank you very much for your help
Additional info
This is a report domain for DMARC:
<?xml version="1.0" encoding="UTF-8" ?>
<feedback>
<report_metadata>
<org_name>google.com</org_name>
<email>noreply-dmarc-support#google.com</email>
<extra_contact_info>https://support.google.com/a/answer/2466580</extra_contact_info>
<report_id>7762784093316082866</report_id>
<date_range>
<begin>1603756800</begin>
<end>1603843199</end>
</date_range>
</report_metadata>
<policy_published>
<domain>tecnologica.com.ar</domain>
<adkim>r</adkim>
<aspf>r</aspf>
<p>reject</p>
<sp>reject</sp>
<pct>100</pct>
</policy_published>
<record>
<row>
<source_ip>200.69.236.179</source_ip>
<count>2</count>
<policy_evaluated>
<disposition>none</disposition>
<dkim>pass</dkim>
<spf>pass</spf>
</policy_evaluated>
</row>
<identifiers>
<header_from>tecnologica.com.ar</header_from>
</identifiers>
<auth_results>
<dkim>
<domain>tecnologica.com.ar</domain>
<result>pass</result>
<selector>default</selector>
</dkim>
<spf>
<domain>tecnologica.com.ar</domain>
<result>pass</result>
</spf>
</auth_results>
</record>
</feedback>
And this is a report domain for TLS:
{"organization-name":"Google Inc.","date-range":{"start-datetime":"2020-10-26T00:00:00Z","end-datetime":"2020-10-26T23:59:59Z"},"contact-info":"smtp-tls-reporting#google.com","report-id":"2020-10-26T00:00:00Z_tecnologica.com.ar","policies":[{"policy":{"policy-type":"sts","policy-string":["version: STSv1\r","mode: testing\r","mx: venabili.tecnologica.com.ar\r","max_age: 604800\r","\r"],"policy-domain":"tecnologica.com.ar"},"summary":{"total-successful-session-count":1,"total-failure-session-count":0}}]}
I am trying to check if a file exists on the internal flash:/ disk of a Cisco switch.
switch-2950#dir flash:/
Directory of flash:/
2 -rwx 3721946 Jul 24 2009 16:17:10 +00:00 c2950-i6k2l2q4-mz.121-22.EA13.bin
3 -rwx 2035 Mar 01 1993 00:25:01 +00:00 config.text
5 drwx 4416 Jul 24 2009 16:19:50 +00:00 html
6 -rwx 556 Mar 01 1993 00:49:35 +00:00 vlan.dat
335 -rwx 315 Jul 24 2009 17:43:37 +00:00 env_vars
21 -rwx 112 Jul 24 2009 16:10:20 +00:00 info
22 -rwx 112 Jul 24 2009 16:20:56 +00:00 info.ver
23 drwx 64 Mar 01 1993 00:00:11 +00:00 crashinfo
25 -rwx 13495 May 18 2011 19:57:30 +00:00 config.old
336 -rwx 3832 Mar 01 1993 00:25:01 +00:00 private-config.text
7741440 bytes total (2124800 bytes free)
vlan.dat clearly exists. I can perform operations against it (such as copy).
However, I want to test if that particular file exists before performing
operations against it.
I am trying:
if os.path.isfile("flash:/vlan.dat"):
But it always returns False and the commands inside the 'if' statement are skipped over.
I have looked over numerous posts but they all cover Linux or Windows. I can't find anything regarding a Cisco file system.
I solved it another way. I do a 'dir flash:/', then I check for the existence
of the 'vlan.dat' file.
today = time.strftime("%x")
timenow = time.strftime("%X")
filename = (hostname + '-' + '%s' + '_' + '%s') % (today, timenow)
filename = filename.replace("/", "-")
filename = filename.replace(":", "-")
ssh_channel.send("dir flash:/" + "\n")
time.sleep(0.3)
outp = ssh_channel.recv(2000)
output = outp.decode("utf-8")
if 'vlan.dat' in output:
ssh_channel.send("copy flash:/vlan.dat tftp://192.168.1.106/" + filename + ".dat" + "\n")
time.sleep(0.3)
Ubuntu 16.04
System Environment
Node v6.9.5
NPM v4.4.4
Docker v17.03.1-ce
Docker-compose v1.11.2
Deleted sample-applications, uninstalled composer-cli, reinstalled composer-cli, cleared all docker images, updated pip, updated rest of dependencies, cloned sample-applications cd into directory and ran nmp install
This is the error I get:
npm ERR! Tell the author that this fails on your system:
npm ERR! composer archive create --sourceName digitalproperty-network --sourceType module --archiveFile digitalPropertyNetwork.bna && composer network deploy --archiveFile digitalPropertyNetwork.bna -p defaultProfile -i admin -s adminpw && composer network list -n digitalproperty-network -i admin -s adminpw
Here is the Log
0 info it worked if it ends with ok
1 verbose cli [ '/home/goodfaith/.nvm/versions/node/v6.9.5/bin/node',
1 verbose cli '/home/goodfaith/.nvm/versions/node/v6.9.5/bin/npm',
1 verbose cli 'run',
1 verbose cli 'deployNetwork' ]
2 info using npm#4.4.4
3 info using node#v6.9.5
4 verbose run-script [ 'predeployNetwork', 'deployNetwork', 'postdeployNetwork' ]
5 info lifecycle getting-started#1.0.0~predeployNetwork: getting-started#1.0.0
6 silly lifecycle getting-started#1.0.0~predeployNetwork: no script for predeployNetwork, continuing
7 info lifecycle getting-started#1.0.0~deployNetwork: getting-started#1.0.0
8 verbose lifecycle getting-started#1.0.0~deployNetwork: unsafe-perm in lifecycle true
9 verbose lifecycle getting-started#1.0.0~deployNetwork: PATH: /home/goodfaith/.nvm/versions/node/v6.9.5/lib/node_modules/npm/bin/node-gyp-bin:/home/goodfaith/sample-applications/packages/getting-started/node_modules/.bin:/home/goodfaith/.nvm/versions/node/v6.9.5/lib/node_modules/npm/bin/node-gyp-bin:/home/goodfaith/sample-applications/packages/getting-started/node_modules/.bin:/home/goodfaith/.nvm/versions/node/v6.9.5/bin:/home/goodfaith/bin:/home/goodfaith/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
10 verbose lifecycle getting-started#1.0.0~deployNetwork: CWD: /home/goodfaith/sample-applications/packages/getting-started
11 silly lifecycle getting-started#1.0.0~deployNetwork: Args: [ '-c',
11 silly lifecycle 'composer archive create --sourceName digitalproperty-network --sourceType module --archiveFile digitalPropertyNetwork.bna && composer network deploy --archiveFile digitalPropertyNetwork.bna -p defaultProfile -i admin -s adminpw && composer network list -n digitalproperty-network -i admin -s adminpw' ]
12 silly lifecycle getting-started#1.0.0~deployNetwork: Returned: code: 1 signal: null
13 info lifecycle getting-started#1.0.0~deployNetwork: Failed to exec deployNetwork script
14 verbose stack Error: getting-started#1.0.0 deployNetwork: `composer archive create --sourceName digitalproperty-network --sourceType module --archiveFile digitalPropertyNetwork.bna && composer network deploy --archiveFile digitalPropertyNetwork.bna -p defaultProfile -i admin -s adminpw && composer network list -n digitalproperty-network -i admin -s adminpw`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/home/goodfaith/.nvm/versions/node/v6.9.5/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess.<anonymous> (/home/goodfaith/.nvm/versions/node/v6.9.5/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:877:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid getting-started#1.0.0
16 verbose cwd /home/goodfaith/sample-applications/packages/getting-started
17 verbose Linux 4.4.0-31-generic
18 verbose argv "/home/goodfaith/.nvm/versions/node/v6.9.5/bin/node" "/home/goodfaith/.nvm/versions/node/v6.9.5/bin/npm" "run" "deployNetwork"
19 verbose node v6.9.5
20 verbose npm v4.4.4
21 error code ELIFECYCLE
22 error errno 1
23 error getting-started#1.0.0 deployNetwork: `composer archive create --sourceName digitalproperty-network --sourceType module --archiveFile digitalPropertyNetwork.bna && composer network deploy --archiveFile digitalPropertyNetwork.bna -p defaultProfile -i admin -s adminpw && composer network list -n digitalproperty-network -i admin -s adminpw`
23 error Exit status 1
24 error Failed at the getting-started#1.0.0 deployNetwork script 'composer archive create --sourceName digitalproperty-network --sourceType module --archiveFile digitalPropertyNetwork.bna && composer network deploy --archiveFile digitalPropertyNetwork.bna -p defaultProfile -i admin -s adminpw && composer network list -n digitalproperty-network -i admin -s adminpw'.
24 error Make sure you have the latest version of node.js and npm installed.
24 error If you do, this is most likely a problem with the getting-started package,
24 error not with npm itself.
24 error Tell the author that this fails on your system:
24 error composer archive create --sourceName digitalproperty-network --sourceType module --archiveFile digitalPropertyNetwork.bna && composer network deploy --archiveFile digitalPropertyNetwork.bna -p defaultProfile -i admin -s adminpw && composer network list -n digitalproperty-network -i admin -s adminpw
24 error You can get information on how to open an issue for this project with:
24 error npm bugs getting-started
24 error Or if that isn't available, you can get their info via:
24 error npm owner ls getting-started
24 error There is likely additional logging output above.
25 verbose exit [ 1, true ]
When running composer archive create --sourceName digitalproperty-network --sourceType module --archiveFile digitalPropertyNetwork.bna && composer network deploy --archiveFile digitalPropertyNetwork.bna -p defaultProfile -i admin -s adminpw && composer network list -n digitalproperty-network -i admin -s adminpw
I get:
Creating Business Network Archive
Node module search path :
undefined
Not found in main node_module search path, trying current directory :/home/goodfaith/sample-applications/packages/getting-started/node_modules/digitalproperty-network
Looking for package.json of Business Network Definition in /home/goodfaith/sample-applications/packages/getting-started/node_modules/digitalproperty-network
Found:
Description:Digital Property Network
Name:digitalproperty-network
Identifier:digitalproperty-network#0.0.6
Written Business Network Definition Archive file to digitalPropertyNetwork.bna
Command completed successfully.
Command succeeded
Deploying business network from archive: digitalPropertyNetwork.bna
Business network definition:
Identifier: digitalproperty-network#0.0.6
Description: Digital Property Network
TypeError: Cannot read property 'fail' of undefined
Command failed
This is all of the node logs, not sure which one .bna file gets deployed to.
goodfaith#goodfaith:~/sample-applications/packages/getting-started$ docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5c9ea989790d hyperledger/fabric-peer:x86_64-1.0.0-alpha "peer node start -..." 6 minutes ago Up 6 minutes 0.0.0.0:7056->7051/tcp, 0.0.0.0:7058->7053/tcp peer1
42a7ea675cd8 hyperledger/fabric-peer:x86_64-1.0.0-alpha "peer node start -..." 6 minutes ago Up 6 minutes 0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp peer0
afaf2bbdb46c hyperledger/fabric-orderer:x86_64-1.0.0-alpha "orderer" 6 minutes ago Up 6 minutes 0.0.0.0:7050->7050/tcp orderer0
817b10f94193 hyperledger/fabric-ca:x86_64-1.0.0-alpha "sh -c 'fabric-ca-..." 6 minutes ago Up 6 minutes 0.0.0.0:7054->7054/tcp ca_peerOrg1
goodfaith#goodfaith:~/sample-applications/packages/getting-started$
2017-04-15 21:52:33.956 UTC [ledgermgmt] initialize -> INFO 001 Initializing ledger mgmt
2017-04-15 21:52:33.956 UTC [kvledger] NewProvider -> INFO 002 Initializing ledger provider
2017-04-15 21:52:34.692 UTC [kvledger] NewProvider -> INFO 003 ledger provider Initialized
2017-04-15 21:52:34.692 UTC [ledgermgmt] initialize -> INFO 004 ledger mgmt initialized
2017-04-15 21:52:34.693 UTC [eventhub_producer] start -> INFO 005 event processor started
2017-04-15 21:52:34.694 UTC [chaincode] NewChaincodeSupport -> INFO 006 Chaincode support using peerAddress: peer1:7051
2017-04-15 21:52:34.694 UTC [sysccapi] RegisterSysCC -> INFO 007 system chaincode cscc(github.com/hyperledger/fabric/core/scc/cscc) registered
2017-04-15 21:52:34.694 UTC [sysccapi] RegisterSysCC -> INFO 008 system chaincode lccc(github.com/hyperledger/fabric/core/scc/lccc) registered
2017-04-15 21:52:34.694 UTC [sysccapi] RegisterSysCC -> INFO 009 system chaincode escc(github.com/hyperledger/fabric/core/scc/escc) registered
2017-04-15 21:52:34.694 UTC [sysccapi] RegisterSysCC -> INFO 00a system chaincode vscc(github.com/hyperledger/fabric/core/scc/vscc) registered
2017-04-15 21:52:34.694 UTC [sysccapi] RegisterSysCC -> INFO 00b system chaincode qscc(github.com/hyperledger/fabric/core/chaincode/qscc) registered
2017-04-15 21:52:34.695 UTC [gossip/service] func1 -> INFO 00c Initialize gossip with endpoint peer1:7051 and bootstrap set [127.0.0.1:7051]
2017-04-15 21:52:34.695 UTC [msp] DeserializeIdentity -> INFO 00d Obtaining identity
2017-04-15 21:52:34.695 UTC [msp] Validate -> INFO 00e MSP Org1MSP validating identity
2017-04-15 21:52:34.697 UTC [msp] DeserializeIdentity -> INFO 00f Obtaining identity
2017-04-15 21:52:34.698 UTC [msp] Validate -> INFO 010 MSP Org1MSP validating identity
2017-04-15 21:52:34.698 UTC [msp] DeserializeIdentity -> INFO 011 Obtaining identity
2017-04-15 21:52:34.698 UTC [gossip/discovery#peer1:7051] NewDiscoveryService -> INFO 012 Started {peer1:7051 [] [125 58 68 210 143 225 187 103 137 152 206 221 191 200 16 240 149 119 163 246 238 16 27 103 91 198 163 125 200 174 34 56] peer1:7051} incTime is 1492293154698594806
2017-04-15 21:52:34.698 UTC [gossip/gossip#peer1:7051] NewGossipService -> INFO 013 Creating gossip service with self membership of {peer1:7051 [] [125 58 68 210 143 225 187 103 137 152 206 221 191 200 16 240 149 119 163 246 238 16 27 103 91 198 163 125 200 174 34 56] peer1:7051}
2017-04-15 21:52:34.698 UTC [msp] DeserializeIdentity -> INFO 014 Obtaining identity
2017-04-15 21:52:34.698 UTC [msp] Validate -> INFO 015 MSP Org1MSP validating identity
2017-04-15 21:52:34.701 UTC [gossip/discovery#peer1:7051] connect2BootstrapPeers -> INFO 017 Entering: [127.0.0.1:7051]
2017-04-15 21:52:34.701 UTC [gossip/discovery#peer1:7051] connect2BootstrapPeers -> INFO 018 Exiting
2017-04-15 21:52:34.699 UTC [msp] DeserializeIdentity -> INFO 016 Obtaining identity
2017-04-15 21:52:34.701 UTC [msp] Validate -> INFO 019 MSP Org1MSP validating identity
2017-04-15 21:52:34.702 UTC [gossip/gossip#peer1:7051] start -> INFO 01a Gossip instance peer1:7051 started
2017-04-15 21:52:34.704 UTC [chaincode] Init -> INFO 01b Init CSCC
2017-04-15 21:52:34.704 UTC [sysccapi] deploySysCC -> INFO 01c system chaincode cscc/(github.com/hyperledger/fabric/core/scc/cscc) deployed
2017-04-15 21:52:34.705 UTC [sysccapi] deploySysCC -> INFO 01d system chaincode lccc/(github.com/hyperledger/fabric/core/scc/lccc) deployed
2017-04-15 21:52:34.705 UTC [escc] Init -> INFO 01e Successfully initialized ESCC
2017-04-15 21:52:34.705 UTC [sysccapi] deploySysCC -> INFO 01f system chaincode escc/(github.com/hyperledger/fabric/core/scc/escc) deployed
2017-04-15 21:52:34.706 UTC [sysccapi] deploySysCC -> INFO 020 system chaincode vscc/(github.com/hyperledger/fabric/core/scc/vscc) deployed
2017-04-15 21:52:34.706 UTC [qscc] Init -> INFO 021 Init QSCC
2017-04-15 21:52:34.706 UTC [sysccapi] deploySysCC -> INFO 022 system chaincode qscc/(github.com/hyperledger/fabric/core/chaincode/qscc) deployed
2017-04-15 21:52:34.706 UTC [nodeCmd] initSysCCs -> INFO 023 Deployed system chaincodess
2017-04-15 21:52:34.707 UTC [nodeCmd] serve -> INFO 024 Starting peer with ID=[name:"peer1" ], network ID=[dev], address=[peer1:7051]
2017-04-15 21:52:34.815 UTC [nodeCmd] serve -> INFO 025 Started peer with ID=[name:"peer1" ], network ID=[dev], address=[peer1:7051]
2017-04-15 21:52:41.746 UTC [ledgermgmt] CreateLedger -> INFO 026 Creating ledger with id = mychannel
2017-04-15 21:52:41.861 UTC [ledgermgmt] CreateLedger -> INFO 027 Created ledger with id = mychannel
2017-04-15 21:52:41.917 UTC [kvledger] Commit -> INFO 028 Channel [mychannel]: Created block [0] with 1 transaction(s)
2017-04-15 21:52:41.928 UTC [gossip/state] NewGossipStateProvider -> INFO 029 Updating node metadata information, current ledger sequence is at = 0, next expected block is = 1
2017-04-15 21:52:41.931 UTC [deliveryClient] NewDeliverService -> INFO 02a Creating delivery service to get blocks from the ordering service, orderer0:7050
2017-04-15 21:52:41.962 UTC [chaincode] Init -> INFO 02b Init CSCC
2017-04-15 21:52:41.962 UTC [sysccapi] deploySysCC -> INFO 02c system chaincode cscc/mychannel(github.com/hyperledger/fabric/core/scc/cscc) deployed
2017-04-15 21:52:41.963 UTC [sysccapi] deploySysCC -> INFO 02d system chaincode lccc/mychannel(github.com/hyperledger/fabric/core/scc/lccc) deployed
2017-04-15 21:52:41.963 UTC [escc] Init -> INFO 02e Successfully initialized ESCC
2017-04-15 21:52:41.963 UTC [sysccapi] deploySysCC -> INFO 02f system chaincode escc/mychannel(github.com/hyperledger/fabric/core/scc/escc) deployed
2017-04-15 21:52:41.964 UTC [sysccapi] deploySysCC -> INFO 030 system chaincode vscc/mychannel(github.com/hyperledger/fabric/core/scc/vscc) deployed
2017-04-15 21:52:41.964 UTC [qscc] Init -> INFO 031 Init QSCC
2017-04-15 21:52:41.964 UTC [sysccapi] deploySysCC -> INFO 032 system chaincode qscc/mychannel(github.com/hyperledger/fabric/core/chaincode/qscc) deployed
2017-04-15 21:52:43.705 UTC [gossip/gossip#peer1:7051] func2 -> INFO 033 Learned of a new certificate: [10 7 79 114 103 49 77 83 80 18 244 5 45 45 45 45 45 66 69 71 73 78 32 45 45 45 45 45 10 77 73 73 67 69 106 67 67 65 98 105 103 65 119 73 66 65 103 73 81 80 106 98 54 51 109 68 76 52 101 48 54 50 77 80 106 116 99 65 49 67 68 65 75 66 103 103 113 104 107 106 79 80 81 81 68 65 106 66 103 77 81 115 119 10 67 81 89 68 86 81 81 71 69 119 74 86 85 122 69 84 77 66 69 71 65 49 85 69 67 66 77 75 81 50 70 115 97 87 90 118 99 109 53 112 89 84 69 87 77 66 81 71 65 49 85 69 66 120 77 78 85 50 70 117 73 69 90 121 10 89 87 53 106 97 88 78 106 98 122 69 82 77 65 56 71 65 49 85 69 67 104 77 73 99 71 86 108 99 107 57 121 90 122 69 120 69 84 65 80 66 103 78 86 66 65 77 84 67 72 66 108 90 88 74 80 99 109 99 120 77 66 52 88 10 68 84 69 51 77 68 77 119 77 84 69 51 77 122 89 48 77 86 111 88 68 84 73 51 77 68 73 121 78 122 69 51 77 122 89 48 77 86 111 119 85 106 69 76 77 65 107 71 65 49 85 69 66 104 77 67 86 86 77 120 69 122 65 82 10 66 103 78 86 66 65 103 84 67 107 78 104 98 71 108 109 98 51 74 117 97 87 69 120 70 106 65 85 66 103 78 86 66 65 99 84 68 86 78 104 98 105 66 71 99 109 70 117 89 50 108 122 89 50 56 120 70 106 65 85 66 103 78 86 10 66 65 77 84 68 88 66 108 90 88 74 80 99 109 99 120 85 71 86 108 99 106 69 119 87 84 65 84 66 103 99 113 104 107 106 79 80 81 73 66 66 103 103 113 104 107 106 79 80 81 77 66 66 119 78 67 65 65 83 48 104 79 56 67 10 56 112 104 43 80 105 70 107 89 105 107 100 86 65 75 47 122 67 100 50 99 107 120 98 54 109 53 98 84 79 113 53 52 86 116 87 82 55 119 98 100 80 117 117 57 100 106 73 67 84 97 82 79 84 85 109 102 101 111 65 72 70 54 48 10 111 108 47 90 47 112 101 110 82 47 71 54 99 104 113 75 111 50 73 119 89 68 65 79 66 103 78 86 72 81 56 66 65 102 56 69 66 65 77 67 66 97 65 119 69 119 89 68 86 82 48 108 66 65 119 119 67 103 89 73 75 119 89 66 10 66 81 85 72 65 119 69 119 68 65 89 68 86 82 48 84 65 81 72 47 66 65 73 119 65 68 65 114 66 103 78 86 72 83 77 69 74 68 65 105 103 67 68 89 112 98 80 75 119 98 103 104 57 117 83 48 104 56 54 118 72 57 73 53 10 122 99 47 68 69 73 108 66 85 74 67 76 107 80 66 101 107 88 108 86 97 106 65 75 66 103 103 113 104 107 106 79 80 81 81 68 65 103 78 73 65 68 66 70 65 105 69 65 109 71 83 51 76 84 97 113 67 107 87 86 43 109 121 108 10 108 104 103 57 111 118 116 76 74 65 66 117 120 81 76 110 97 106 77 74 89 81 79 88 85 82 103 67 73 72 76 86 78 114 68 98 69 70 48 75 112 69 109 70 119 88 73 66 89 77 70 100 115 75 71 82 65 70 48 107 67 52 51 77 10 98 112 113 56 55 85 74 113 10 45 45 45 45 45 69 78 68 32 45 45 45 45 45 10]
^C
goodfaith#goodfaith:~/sample-applications/packages/getting-started$
2017-04-15 21:52:32.342 UTC [ledgermgmt] initialize -> INFO 001 Initializing ledger mgmt
2017-04-15 21:52:32.342 UTC [kvledger] NewProvider -> INFO 002 Initializing ledger provider
2017-04-15 21:52:32.694 UTC [kvledger] NewProvider -> INFO 003 ledger provider Initialized
2017-04-15 21:52:32.695 UTC [ledgermgmt] initialize -> INFO 004 ledger mgmt initialized
2017-04-15 21:52:32.696 UTC [eventhub_producer] start -> INFO 005 event processor started
2017-04-15 21:52:32.697 UTC [chaincode] NewChaincodeSupport -> INFO 006 Chaincode support using peerAddress: peer0:7051
2017-04-15 21:52:32.697 UTC [sysccapi] RegisterSysCC -> INFO 007 system chaincode cscc(github.com/hyperledger/fabric/core/scc/cscc) registered
2017-04-15 21:52:32.697 UTC [sysccapi] RegisterSysCC -> INFO 008 system chaincode lccc(github.com/hyperledger/fabric/core/scc/lccc) registered
2017-04-15 21:52:32.697 UTC [sysccapi] RegisterSysCC -> INFO 009 system chaincode escc(github.com/hyperledger/fabric/core/scc/escc) registered
2017-04-15 21:52:32.698 UTC [sysccapi] RegisterSysCC -> INFO 00a system chaincode vscc(github.com/hyperledger/fabric/core/scc/vscc) registered
2017-04-15 21:52:32.698 UTC [sysccapi] RegisterSysCC -> INFO 00b system chaincode qscc(github.com/hyperledger/fabric/core/chaincode/qscc) registered
2017-04-15 21:52:32.698 UTC [gossip/service] func1 -> INFO 00c Initialize gossip with endpoint peer0:7051 and bootstrap set [127.0.0.1:7051]
2017-04-15 21:52:32.698 UTC [msp] DeserializeIdentity -> INFO 00d Obtaining identity
2017-04-15 21:52:32.699 UTC [msp] Validate -> INFO 00e MSP Org1MSP validating identity
2017-04-15 21:52:32.701 UTC [msp] DeserializeIdentity -> INFO 00f Obtaining identity
2017-04-15 21:52:32.701 UTC [msp] Validate -> INFO 010 MSP Org1MSP validating identity
2017-04-15 21:52:32.701 UTC [msp] DeserializeIdentity -> INFO 011 Obtaining identity
2017-04-15 21:52:32.702 UTC [gossip/discovery#peer0:7051] NewDiscoveryService -> INFO 012 Started {peer0:7051 [] [156 43 33 171 114 249 57 151 235 35 197 207 85 206 60 90 178 209 11 90 101 229 107 30 108 214 245 107 90 240 230 193] peer0:7051} incTime is 1492293152702183828
2017-04-15 21:52:32.703 UTC [gossip/gossip#peer0:7051] NewGossipService -> INFO 013 Creating gossip service with self membership of {peer0:7051 [] [156 43 33 171 114 249 57 151 235 35 197 207 85 206 60 90 178 209 11 90 101 229 107 30 108 214 245 107 90 240 230 193] peer0:7051}
2017-04-15 21:52:32.703 UTC [msp] DeserializeIdentity -> INFO 014 Obtaining identity
2017-04-15 21:52:32.704 UTC [msp] Validate -> INFO 015 MSP Org1MSP validating identity
2017-04-15 21:52:32.704 UTC [msp] DeserializeIdentity -> INFO 016 Obtaining identity
2017-04-15 21:52:32.704 UTC [msp] Validate -> INFO 017 MSP Org1MSP validating identity
2017-04-15 21:52:32.705 UTC [gossip/discovery#peer0:7051] connect2BootstrapPeers -> INFO 018 Entering: [127.0.0.1:7051]
2017-04-15 21:52:32.705 UTC [gossip/discovery#peer0:7051] connect2BootstrapPeers -> INFO 019 Exiting
2017-04-15 21:52:32.705 UTC [gossip/gossip#peer0:7051] start -> INFO 01a Gossip instance peer0:7051 started
2017-04-15 21:52:32.706 UTC [chaincode] Init -> INFO 01b Init CSCC
2017-04-15 21:52:32.706 UTC [sysccapi] deploySysCC -> INFO 01c system chaincode cscc/(github.com/hyperledger/fabric/core/scc/cscc) deployed
2017-04-15 21:52:32.706 UTC [sysccapi] deploySysCC -> INFO 01d system chaincode lccc/(github.com/hyperledger/fabric/core/scc/lccc) deployed
2017-04-15 21:52:32.707 UTC [escc] Init -> INFO 01e Successfully initialized ESCC
2017-04-15 21:52:32.707 UTC [sysccapi] deploySysCC -> INFO 01f system chaincode escc/(github.com/hyperledger/fabric/core/scc/escc) deployed
2017-04-15 21:52:32.707 UTC [sysccapi] deploySysCC -> INFO 020 system chaincode vscc/(github.com/hyperledger/fabric/core/scc/vscc) deployed
2017-04-15 21:52:32.707 UTC [qscc] Init -> INFO 021 Init QSCC
2017-04-15 21:52:32.707 UTC [sysccapi] deploySysCC -> INFO 022 system chaincode qscc/(github.com/hyperledger/fabric/core/chaincode/qscc) deployed
2017-04-15 21:52:32.707 UTC [nodeCmd] initSysCCs -> INFO 023 Deployed system chaincodess
2017-04-15 21:52:32.708 UTC [nodeCmd] serve -> INFO 024 Starting peer with ID=[name:"peer0" ], network ID=[dev], address=[peer0:7051]
2017-04-15 21:52:32.774 UTC [nodeCmd] serve -> INFO 025 Started peer with ID=[name:"peer0" ], network ID=[dev], address=[peer0:7051]
2017-04-15 21:52:41.746 UTC [ledgermgmt] CreateLedger -> INFO 026 Creating ledger with id = mychannel
2017-04-15 21:52:41.861 UTC [ledgermgmt] CreateLedger -> INFO 027 Created ledger with id = mychannel
2017-04-15 21:52:41.917 UTC [kvledger] Commit -> INFO 028 Channel [mychannel]: Created block [0] with 1 transaction(s)
2017-04-15 21:52:41.934 UTC [gossip/gossip#peer0:7051] JoinChan -> INFO 029 Anchor peer with same endpoint, skipping connecting to myself
2017-04-15 21:52:41.934 UTC [gossip/state] NewGossipStateProvider -> INFO 02a Updating node metadata information, current ledger sequence is at = 0, next expected block is = 1
2017-04-15 21:52:41.934 UTC [deliveryClient] NewDeliverService -> INFO 02b Creating delivery service to get blocks from the ordering service, orderer0:7050
2017-04-15 21:52:41.967 UTC [chaincode] Init -> INFO 02c Init CSCC
2017-04-15 21:52:41.967 UTC [sysccapi] deploySysCC -> INFO 02d system chaincode cscc/mychannel(github.com/hyperledger/fabric/core/scc/cscc) deployed
2017-04-15 21:52:41.967 UTC [sysccapi] deploySysCC -> INFO 02e system chaincode lccc/mychannel(github.com/hyperledger/fabric/core/scc/lccc) deployed
2017-04-15 21:52:41.968 UTC [escc] Init -> INFO 02f Successfully initialized ESCC
2017-04-15 21:52:41.969 UTC [sysccapi] deploySysCC -> INFO 030 system chaincode escc/mychannel(github.com/hyperledger/fabric/core/scc/escc) deployed
2017-04-15 21:52:41.969 UTC [sysccapi] deploySysCC -> INFO 031 system chaincode vscc/mychannel(github.com/hyperledger/fabric/core/scc/vscc) deployed
2017-04-15 21:52:41.969 UTC [qscc] Init -> INFO 032 Init QSCC
2017-04-15 21:52:41.969 UTC [sysccapi] deploySysCC -> INFO 033 system chaincode qscc/mychannel(github.com/hyperledger/fabric/core/chaincode/qscc) deployed
2017-04-15 21:52:45.168 UTC [eventhub_producer] Chat -> ERRO 034 Error during Chat, stopping handler: stream error: code = 1 desc = "context canceled"
2017-04-15 21:52:53.714 UTC [gossip/gossip#peer0:7051] func2 -> INFO 035 Learned of a new certificate: [10 7 79 114 103 49 77 83 80 18 244 5 45 45 45 45 45 66 69 71 73 78 32 45 45 45 45 45 10 77 73 73 67 69 106 67 67 65 98 109 103 65 119 73 66 65 103 73 82 65 78 103 100 53 103 119 72 75 120 78 121 113 120 112 116 118 52 48 111 80 69 107 119 67 103 89 73 75 111 90 73 122 106 48 69 65 119 73 119 89 68 69 76 10 77 65 107 71 65 49 85 69 66 104 77 67 86 86 77 120 69 122 65 82 66 103 78 86 66 65 103 84 67 107 78 104 98 71 108 109 98 51 74 117 97 87 69 120 70 106 65 85 66 103 78 86 66 65 99 84 68 86 78 104 98 105 66 71 10 99 109 70 117 89 50 108 122 89 50 56 120 69 84 65 80 66 103 78 86 66 65 111 84 67 72 66 108 90 88 74 80 99 109 99 120 77 82 69 119 68 119 89 68 86 81 81 68 69 119 104 119 90 87 86 121 84 51 74 110 77 84 65 101 10 70 119 48 120 78 122 65 122 77 68 69 120 78 122 77 50 78 68 70 97 70 119 48 121 78 122 65 121 77 106 99 120 78 122 77 50 78 68 70 97 77 70 73 120 67 122 65 74 66 103 78 86 66 65 89 84 65 108 86 84 77 82 77 119 10 69 81 89 68 86 81 81 73 69 119 112 68 89 87 120 112 90 109 57 121 98 109 108 104 77 82 89 119 70 65 89 68 86 81 81 72 69 119 49 84 89 87 52 103 82 110 74 104 98 109 78 112 99 50 78 118 77 82 89 119 70 65 89 68 10 86 81 81 68 69 119 49 119 90 87 86 121 84 51 74 110 77 86 66 108 90 88 73 121 77 70 107 119 69 119 89 72 75 111 90 73 122 106 48 67 65 81 89 73 75 111 90 73 122 106 48 68 65 81 99 68 81 103 65 69 90 105 98 89 10 112 84 117 114 55 104 47 76 73 107 90 107 86 49 121 114 49 49 109 80 48 77 52 72 116 115 43 65 82 114 107 121 51 114 57 55 87 105 104 118 70 48 43 84 103 120 85 73 85 114 70 106 69 101 52 89 118 43 83 73 108 122 53 43 10 73 69 54 66 108 78 101 109 97 70 54 55 110 85 101 68 43 97 78 105 77 71 65 119 68 103 89 68 86 82 48 80 65 81 72 47 66 65 81 68 65 103 87 103 77 66 77 71 65 49 85 100 74 81 81 77 77 65 111 71 67 67 115 71 10 65 81 85 70 66 119 77 66 77 65 119 71 65 49 85 100 69 119 69 66 47 119 81 67 77 65 65 119 75 119 89 68 86 82 48 106 66 67 81 119 73 111 65 103 50 75 87 122 121 115 71 52 73 102 98 107 116 73 102 79 114 120 47 83 10 79 99 51 80 119 120 67 74 81 86 67 81 105 53 68 119 88 112 70 53 86 87 111 119 67 103 89 73 75 111 90 73 122 106 48 69 65 119 73 68 82 119 65 119 82 65 73 103 74 54 122 109 71 84 89 87 101 65 106 97 97 56 122 86 10 73 55 51 116 51 90 111 112 47 109 70 55 57 48 78 119 107 72 50 83 83 108 116 52 83 65 77 67 73 71 57 121 101 72 55 75 56 89 100 68 56 65 111 51 107 66 105 65 82 121 106 73 43 81 112 105 87 113 105 49 75 56 113 83 10 98 54 69 87 112 116 103 50 10 45 45 45 45 45 69 78 68 32 45 45 45 45 45 10]
^C
goodfaith#goodfaith:~/sample-applications/packages/getting-started$ \
2017-04-15 21:52:30.473 UTC [orderer/multichain] NewManagerImpl -> INFO 001 Starting with system channel: testchainid and orderer type solo
2017-04-15 21:52:30.473 UTC [orderer/main] NewServer -> INFO 002 Starting orderer
2017-04-15 21:52:30.473 UTC [orderer/main] main -> INFO 003 Beginning to serve requests
2017-04-15 21:52:35.456 UTC [msp] Validate -> INFO 004 MSP OrdererMSP validating identity
2017-04-15 21:52:35.464 UTC [msp] Validate -> INFO 005 MSP OrdererMSP validating identity
2017-04-15 21:52:35.507 UTC [orderer/multichain] newChain -> INFO 006 Created and starting new chain mychannel
2017-04-15 21:52:41.708 UTC [msp] Validate -> INFO 007 MSP Org1MSP validating identity
2017-04-15 21:52:41.717 UTC [orderer/common/deliver] Handle -> WARN 008 Error reading from stream: EOF
2017-04-15 21:52:41.965 UTC [msp] Validate -> INFO 009 MSP Org1MSP validating identity
^C
goodfaith#goodfaith:~/sample-applications/packages/getting-started$
2017/04/15 21:52:29 [INFO] Created default configuration file at /etc/hyperledger/fabric-ca-server/fabric-ca-server-config.yaml
2017/04/15 21:52:29 Initialize BCCSP [SW]
2017/04/15 21:52:29 [INFO] The CA key and certificate files already exist
2017/04/15 21:52:29 [INFO] Key file location: /etc/hyperledger/fabric-ca-server-config/d8a5b3cac1b821f6e4b487ceaf1fd239cdcfc310894150908b90f05e9179556a_sk
2017/04/15 21:52:29 [INFO] Certificate file location: /etc/hyperledger/fabric-ca-server-config/peerOrg1-cert.pem
2017/04/15 21:52:31 [INFO] Initialized sqlite3 data base at /etc/hyperledger/fabric-ca-server/fabric-ca-server.db
2017/04/15 21:52:31 [INFO] Listening at http://0.0.0.0:7054
Apologies - the sample-applications repository was incorrectly updated to use Hyperledger Fabric v1.0 when it is not yet ready for prime-time. I've reverted the changes to sample-applications.
Please can you pull down the latest version of the sample-applications repository and try again? You may need to manually remove the Hyperledger Fabric v1.0 containers using the command: docker ps -aq | xargs docker rm -f
If you are using v1.0, copyng hlfv1/connection.json to ~/.composer-connection-profiles/defaultProfile/connection.json manually may work.
You may need to update path inside hlfv1/connection.json too.
Looks like the format of connection.json has changed.
There is a instruction here.
I want to copy specific file done last changes in Oct 16-17,file type is java.
shia#ubuntu:~/code$ ls -alxo
total 96
drwx------ 2 shia 4096 Oct 20 18:54 .
drwxr-xr-x 61 shia 12288 Oct 20 19:24 ..
-rw------- 1 shia 12288 Oct 16 21:52 .Reuse.java.swp
-rw-rw-r-- 1 shia 746 Oct 20 11:16 Argus.class
-rw-rw-r-- 1 shia 302 Oct 20 11:16 Argus.java
-rw------- 1 shia 310 Oct 16 21:30 Call.java
-rw-rw-r-- 1 shia 417 Oct 17 15:20 Ordinary.class
-rw-rw-r-- 1 shia 298 Oct 17 14:57 Overriding.java
-rw-rw-r-- 1 shia 562 Oct 19 21:27 Package.class
-rw-rw-r-- 1 shia 430 Oct 19 21:27 Package.java
-rw------- 1 shia 729 Oct 17 13:50 Reuse.java
-rw------- 1 shia 424 Oct 17 13:47 Room.java
-rw------- 1 shia 321 Oct 16 21:22 Simpleobject.java
-rw-rw-r-- 1 shia 1187 Oct 17 00:04 Static.java
-rw-rw-r-- 1 shia 686 Oct 17 15:20 Super.class
-rw-rw-r-- 1 shia 1010 Oct 17 15:20 Super.java
-rw------- 1 shia 843 Oct 17 14:20 This.java
-rw-rw-r-- 1 shia 521 Oct 17 14:51 b.java
-rw-rw-r-- 1 shia 90 Oct 20 18:54 cp.awk
-rw-rw-r-- 1 shia 105 Oct 20 17:19 file.txt
I try to specific them but i don't know how to copy them.
shia#ubuntu:~/code$ ls -alxo|grep 'Oct 1[67].*java$'|awk '{print $8}'
Call.java
Overriding.java
Reuse.java
Room.java
Simpleobject.java
Static.java
Super.java
This.java
b.java
Any help,thanks a lot!
One way using find:
find . -maxdepth 1 -type f -name "*.java" -newermt 2012-10-16 ! -newermt 2012-10-18 -exec cp '{}' /home/user/dstFolder/ \;
You can use xargs to copy the files found:
...| xargs -i cp '{}' /home/user/dstFolder/
This will copy all the files found to the folder /home/user/dstFolder/.