root#00-00-00-00:~# ss-server -c /etc/shadowsocks-libev/config.json -v
2021-11-02 19:54:26 INFO: initializing ciphers? aes-256-gcm
2021-11-02 19:54:26 INFO: tcp server listening at xx.xx.xx.xx:xx00
2021-11-02 19:54:26 ERROR: bind: Address already in use
2021-11-02 19:54:26 ERROR: failed to bind address
This is a brand new deployment from the marketplace.
How do I clear this error?
Thanks!
It was brand new deployment so I did understand the error.
It appears that it was already running, thus trying to run it again resulted in that error message.
ss -plunt | grep "ss-server"
That is a good command to run to see if it is working.
Related
The situation is, I wanna establish a QUIC connection based on quic-go from local to ECS server. The related tests using localhost are done both on local and remote device. That is:
#local: .$QUIC-GO-PATH/example/client/main -insecure -keylog ssl.log -qlog trial.log -v https://127.0.0.1:6121/demo/tile
#local: .$QUIC-GO-PATH/example/main -qlog -tcp -v
These tests are completed.
Now is the problem,when I start local-remote connection an error occurred:
#remote: .$QUIC-GO-PATH/example/main -qlog -tcp -v
#local: .$QUIC-GO-PATH/example/client/main -insecure -keylog ssl.log -qlog trial.log -v https://$REMOTE_IPADDR:6121/demo/tile
timeout: no recent network activity
When I go through a wireshark examination, it seems like the CRYPTO handshake never finishes:
Wireshark
Also client Qlog file atteched here:
Qlog file
Codes are all the same with https://github.com/lucas-clemente/quic-go
Help!
This problem has been solved.
Code $QUIC-GO-PATH/example/main.go has binded the port as a default onto 127.0.0.1:6121, which led to the problem that the server cannot get reached by client outside, just get this on server running:
-bind 0.0.0.0:6121
I am trying to get started with Hyperledger Fabric. I managed to run the "build your first network"-tutorial from the samples, and I followed the "write your first application"-tutorial as well, which also worked.
As a next step, I wanted to create my own network more or less from scratch, by adjusting the .yaml files from the samples and running cryptogen and configtxgen manually. I managed to build a network with three organisations, two peers per org and a solo ordering service. I now want to install some basic chaincode on one of the peers, but I'm stuck, as I get a couple of weird errors:
2018-03-01 22:27:30.525 UTC [grpc] Printf -> DEBU 003 transport: http2Client.notifyError got notified that the client transport was broken read tcp 172.20.0.9:45178->172.20.0.3:7050: read: connection reset by peer.
Error: Error getting broadcast client: Error connecting to orderer.rle.de:7050 due to rpc error: code = Internal desc = transport: write tcp 172.20.0.9:45178->172.20.0.3:7050: write: broken pipe
2018-03-01 22:27:30.525 UTC [grpc] Printf -> DEBU 004 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: Error while dialing dial tcp: lookup orderer.rle.de on 127.0.0.11:53: dial udp 127.0.0.11:53: operation was canceled"; Reconnecting to {orderer.rle.de:7050 <nil>}
2018-03-01 22:27:30.525 UTC [grpc] Printf -> DEBU 005 grpc: addrConn.transportMonitor exits due to: grpc: the connection is closing
After that, I get the usage information for peer chaincode instantiate
If you could provide any insight into what might be causing this error, I would be super grateful. I don't even know if it is caused by the network config or by the chaincode itself (I don't think so, since I tried two different chaincodes, one of which was "sacc" from the samples) but the installation of the chaincode seems to be working. My problem is that I have no idea what I'm doing, so after googling and fooling around with the arguments for peer chaincode instantiate, I'm all out of ideas.
My command (I run it from a .sh file) is:
peer chaincode instantiate -o orderer.rle.de:7050 -C driverlogschannel -n test -v 1.0 -c '{"Args":["John","0"]}' -P "OR ('rleMSP.member')"
The chaincode is taken from the sacc example installed via
peer chaincode install -n test -v 1.0 -p sacc
Thanks a lot! If you need more logs or other info, I can provide them.
Solved it. The problem had to do with the fact that I was not submitting a cafile. Basically, what I did is going back to this tutorial and trying it with their chaincode again:
peer chaincode install -n mycc -v 1.0 -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02
but I adjusted it to
peer chaincode install -n mycc -v 1.0 -p chaincode_example02
(I put the chaincode_example02.go file from fabric-samples/chaincode/ into my $GOPATH/src/chaincode_example02 folder and adjusted my docker-compose-cli.yaml by adding this line to cli -->volumes)
- $GOPATH/src/chaincode_example02:/opt/gopath/src/chaincode_example02
Then, the crucial point:
peer chaincode instantiate -o orderer.example.com:7050 --tls $CORE_PEER_TLS_ENABLED --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C $CHANNEL_NAME -n mycc -v 1.0 -c '{"Args":["init","a", "100", "b","200"]}' -P "OR ('Org1MSP.member','Org2MSP.member')"
although I adjusted this line again so that it matched my folder structure (exchanging example.com for my domain and so on.)
That solved the issue.
I am having problems trying to deploy the rest server with persistence storage (mongo db) I ge this message when deploying the rest server:
docker logs -f rest
[2018-03-12 00:01:13] PM2 log: Launching in no daemon mode
[2018-03-12 00:01:14] PM2 log: Starting execution sequence in -fork mode- for app name:composer-rest-server id:0
[2018-03-12 00:01:14] PM2 log: App name:composer-rest-server id:0 online
WARNING: NODE_APP_INSTANCE value of '0' did not match any instance config file names.
WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
Discovering types from business network definition ...
Connection fails: Error: Error trying to ping. Error: Error trying to query business network. Error: REQUEST_TIMEOUT
It will be retried for the next request.
Exception: Error: Error trying to ping. Error: Error trying to query business network. Error: REQUEST_TIMEOUT
Error: Error trying to ping. Error: Error trying to query business network. Error: REQUEST_TIMEOUT
at _checkRuntimeVersions.then.catch (/home/composer/.npm-global/lib/node_modules/composer-rest-server/node_modules/composer-connector-hlfv1/lib/hlfconnection.js:699:34)
at
at process._tickDomainCallback (internal/process/next_tick.js:228:7)
[2018-03-12 00:07:03] PM2 log: App [composer-rest-server] with id [0] and pid [14], exited with code [1] via signal [SIGINT]
I am using composer v.18
is there any work around to fix this error. when I run the composer-rest- server alone it work. but if I try to add the mongodb it does not work
I just a new beginner of Hyperledger Composer.So I try to deploy REST server using Docker by following this guide
Deploying the REST server for a business network
Then when i run docker, it show this error on docker logs
docker logs rest
0|composer | WARNING: NODE_APP_INSTANCE value of '0' did not match any instance config file names.
0|composer | WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
0|composer | Discovering types from business network definition ...
0|composer | D0831 07:04:36.180952003 24 env_linux.c:66] Warning: insecure environment read function 'getenv' used
0|composer | D0831 07:04:37.574385287 24 env_linux.c:66] Warning: insecure environment read function 'getenv' used
0|composer | Connection fails: Error: Error trying to ping. Error: Composer runtime (0.11.3) is not compatible with client (0.11.2)
0|composer | It will be retried for the next request.
0|composer | Exception: Error: Error trying to ping. Error: Composer runtime (0.11.3) is not compatible with client (0.11.2)
0|composer | Error: Error trying to ping. Error: Composer runtime (0.11.3) is not compatible with client (0.11.2)
0|composer | at _checkRuntimeVersions.then.catch (/usr/local/lib/node_modules/composer-rest-server/node_modules/composer-connector-hlfv1/lib/hlfconnection.js:696:34)
PM2 | App [composer-rest-server] with id [0] and pid [24], exited with code [1] via signal [SIGINT]
PM2 | Starting execution sequence in -fork mode- for app name:composer-rest-server id:0
PM2 | App name:composer-rest-server id:0 online
So i try to update the version by following on this guide on the same doc
Updating Hyperledger Composer
But after I stop/reboot fabric, redeploy the chaincode again and run the docker, the error still exist.
Can anyone please tell me what i've missing?
Note: I try this solution too but still have the same problem.
Ok i've solve the problem. I remove all docker image and start new fabric to download image again,and it works!!
docker rmi $(docker images -q)
I am new to Logstash.I am trying to load data from Sql server to Elasticsearch using Logstash,while doing so I get the below error:
C:\logstash-5.0.2>bin\logstash -f C:\logstash-5.0.2\bin\Crash_Data.conf
Using JAVA_HOME=C:\Program Files\Java\jre8 retrieved from C:\ProgramData\Oracle\
java\javapath\java.exe
Picked up _JAVA_OPTIONS: -Djava.net.preferIPv4Stack=true
Could not find log4j2 configuration at path /logstash-5.0.2/config/log4j2.proper
ties. Using default config which logs to console
15:33:47.206 [[main]-pipeline-manager] ERROR logstash.agent - Pipeline aborted d
ue to error {:exception=>#<Sequel::DatabaseConnectionError: Java::ComMicrosoftSq
lserverJdbc::SQLServerException: The TCP/IP connection to the host Device_Crash_Reporting, port 1433 has failed. . Verify the connection properties. Make sure
that an instance of SQL Server is running on the host and accepting TCP/IP conn
ections at the port. Make sure that TCP connections to the port are not blocked
by a firewall.".>, :backtrace=>["com.microsoft.sqlserver.jdbc.SQLServerException
.makeFromDriverError(com/microsoft/sqlserver/jdbc/SQLServerException.java:191)",
"com.microsoft.sqlserver.jdbc.SQLServerException.ConvertConnectExceptionToSQLSe
rverException(com/microsoft/sqlserver/jdbc/SQLServerException.java:242)", "com.m
icrosoft.sqlserver.jdbc.SocketFinder.findSocket(com/microsoft/sqlserver/jdbc/IOB
uffer.java:2369)", "com.microsoft.sqlserver.jdbc.TDSChannel.open(com/microsoft/s
qlserver/jdbc/IOBuffer.java:551)", "com.microsoft.sqlserver.jdbc.SQLServerConnec
tion.connectHelper(com/microsoft/sqlserver/jdbc/SQLServerConnection.java:1962)",
"com.microsoft.sqlserver.jdbc.SQLServerConnection.login(com/microsoft/sqlserver
/jdbc/SQLServerConnection.java:1627)", "com.microsoft.sqlserver.jdbc.SQLServerCo
nnection.connectInternal(com/microsoft/sqlserver/jdbc/SQLServerConnection.java:1
458)", "com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(com/microsoft/s
qlserver/jdbc/SQLServerConnection.java:772)", "com.microsoft.sqlserver.jdbc.SQLS
erverDriver.connect(com/microsoft/sqlserver/jdbc/SQLServerDriver.java:1168)", "R
UBY.connect(C:/logstash-5.0.2/vendor/bundle/jruby/1.9/gems/sequel-4.40.0/lib/seq
uel/adapters/jdbc.rb:222)", "RUBY.make_new(C:/logstash-5.0.2/vendor/bundle/jruby
/1.9/gems/sequel-4.40.0/lib/sequel/connection_pool.rb:116)", "RUBY.make_new(C:/l
ogstash-5.0.2/vendor/bundle/jruby/1.9/gems/sequel-4.40.0/lib/sequel/connection_p
ool/threaded.rb:228)", "RUBY.available(C:/logstash-5.0.2/vendor/bundle/jruby/1.9
/gems/sequel-4.40.0/lib/sequel/connection_pool/threaded.rb:201)", "RUBY._acquire
(C:/logstash-5.0.2/vendor/bundle/jruby/1.9/gems/sequel-4.40.0/lib/sequel/connect
ion_pool/threaded.rb:137)", "RUBY.acquire(C:/logstash-5.0.2/vendor/bundle/jruby/
1.9/gems/sequel-4.40.0/lib/sequel/connection_pool/threaded.rb:151)", "RUBY.sync(
C:/logstash-5.0.2/vendor/bundle/jruby/1.9/gems/sequel-4.40.0/lib/sequel/connecti
on_pool/threaded.rb:282)", "org.jruby.ext.thread.Mutex.synchronize(org/jruby/ext
/thread/Mutex.java:149)", "RUBY.sync(C:/logstash-5.0.2/vendor/bundle/jruby/1.9/g
ems/sequel-4.40.0/lib/sequel/connection_pool/threaded.rb:282)", "RUBY.acquire(C:
/logstash-5.0.2/vendor/bundle/jruby/1.9/gems/sequel-4.40.0/lib/sequel/connection
_pool/threaded.rb:150)", "RUBY.hold(C:/logstash-5.0.2/vendor/bundle/jruby/1.9/ge
ms/sequel-4.40.0/lib/sequel/connection_pool/threaded.rb:106)", "RUBY.synchronize
(C:/logstash-5.0.2/vendor/bundle/jruby/1.9/gems/sequel-4.40.0/lib/sequel/databas
e/connecting.rb:285)", "RUBY.test_connection(C:/logstash-5.0.2/vendor/bundle/jru
by/1.9/gems/sequel-4.40.0/lib/sequel/database/connecting.rb:295)", "RUBY.prepare
_jdbc_connection(C:/logstash-5.0.2/vendor/bundle/jruby/1.9/gems/logstash-input-j
dbc-4.1.3/lib/logstash/plugin_mixins/jdbc.rb:171)", "RUBY.register(C:/logstash-5
.0.2/vendor/bundle/jruby/1.9/gems/logstash-input-jdbc-4.1.3/lib/logstash/inputs/
jdbc.rb:191)", "RUBY.start_inputs(C:/logstash-5.0.2/logstash-core/lib/logstash/p
ipeline.rb:319)", "org.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)", "RU
BY.start_inputs(C:/logstash-5.0.2/logstash-core/lib/logstash/pipeline.rb:318)",
"RUBY.start_workers(C:/logstash-5.0.2/logstash-core/lib/logstash/pipeline.rb:195
)", "RUBY.run(C:/logstash-5.0.2/logstash-core/lib/logstash/pipeline.rb:153)", "R
UBY.start_pipeline(C:/logstash-5.0.2/logstash-core/lib/logstash/agent.rb:250)"]}
15:33:47.721 [Api Webserver] INFO logstash.agent - Successfully started Logstas
h API endpoint {:port=>9600}
15:33:50.261 [LogStash::Runner] WARN logstash.agent - stopping pipeline {:id=>"
main"}
C:\logstash-5.0.2>
I have checked the port to sql server and everything but still no luck.Can someone please help me with this problem.