After installing postgresql(13) on GCP, I tried installing citus using this command:
curl https://install.citusdata.com/community/rpm.sh | sudo bash
However I run into the following error. Any guidance/suggestions would be helpful.
[tony_stark#host]$ curl https://install.citusdata.com/community/rpm.sh | sudo bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 8667 100 8667 0 0 21791 0 --:--:-- --:--:-- --:--:-- 21831
Detected operating system as centos/7.
Checking for curl...
Detected curl...
Checking for postgresql13-server...
Detected postgresql13-server...
Checking for EPEL repositories...
Detected EPEL repoitories
Downloading repository file: https://repos.citusdata.com/community/config_file.repo?os=centos&dist=7&source=script...
curl: (7) Failed to connect to
Network is unreachable
Unable to run:
curl https://repos.citusdata.com/community/config_file.repo?os=centos&dist=7&source=script
The link curl https://repos.citusdata.com/community/config_file.repo?os=centos&dist=7&source=script works on my browser though.
Looks like a temporary issue on repository side. I just tried it and it works:
[sergiusz#host ~]$ curl https://install.citusdata.com/community/rpm.sh | sudo bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 8667 100 8667 0 0 25686 0 --:--:-- --:--:-- --:--:-- 25718
Detected operating system as centos/7.
Checking for curl...
Detected curl...
Checking for postgresql13-server...
Installing pgdg13 repo... done.
Checking for EPEL repositories...
Detected EPEL repoitories
Downloading repository file: https://repos.citusdata.com/community/config_file.repo?os=centos&dist=7&source=script.
.. done.
Installing pygpgme to verify GPG signatures... done.
Installing yum-utils... done.
Generating yum cache for citusdata_community... done.
The repository is set up! You can now install packages.
EDIT:
This file can be also downloaded manually:
curl "https://repos.citusdata.com/community/config_file.repo?os=centos&dist=7&source=script" -o /etc/yum.repos.d/citusdata_community.repo
I followed strap's guide to an google app engine deployment however when I pushed it to gcloud I get an error 500. It's on postgresql, Standard Environment. I don't know what other informations to include. Here's the error from gcloud.
2020-07-11T21:37:04.742759Z at DatabaseManager.initialize (/srv/node_modules/strapi-database/lib/database-manager.js:36:27) A
2020-07-11T21:37:04.742769Z at Strapi.load (/srv/node_modules/strapi/lib/Strapi.js:274:19) A
2020-07-11T21:55:09.103534Z GET 500 0 B 11.3 s Chrome 83 / I GET 500 0 B 11.3 s Chrome 83 5f0a353d00ff01946e3ca1b9ce0001737e736b756c70740001323032303037313174313635323139000100
2020-07-11T21:55:19.559829Z [2020-07-11T21:55:19.558Z] debug ⛔️ Server wasn't able to start properly. A
2020-07-11T21:55:19.562896Z [2020-07-11T21:55:19.562Z] error Error: EROFS: read-only file system, mkdir '/srv/.tmp' A
2020-07-11T21:55:19.562935Z at Object.mkdirSync (fs.js:757:3) A
2020-07-11T21:55:19.562956Z at _.forEach (/srv/node_modules/strapi-connector-bookshelf/lib/knex.js:152:16) A
2020-07-11T21:55:19.562972Z at /srv/node_modules/lodash/lodash.js:4925:15 A
2020-07-11T21:55:19.562987Z at baseForOwn (/srv/node_modules/lodash/lodash.js:2990:24) A
2020-07-11T21:55:19.563012Z at /srv/node_modules/lodash/lodash.js:4894:18 A
2020-07-11T21:55:19.563025Z at Function.forEach (/srv/node_modules/lodash/lodash.js:9368:14) A
2020-07-11T21:55:19.563034Z at module.exports.strapi (/srv/node_modules/strapi-connector-bookshelf/lib/knex.js:37:5) A
2020-07-11T21:55:19.563043Z at Object.initialize (/srv/node_modules/strapi-connector-bookshelf/lib/index.js:39:5) A
2020-07-11T21:55:19.563058Z at Object.initialize (/srv/node_modules/strapi-database/lib/connector-registry.js:30:25) A
2020-07-11T21:55:19.563071Z at DatabaseManager.initialize (/srv/node_modules/strapi-database/lib/database-manager.js:36:27) A
2020-07-11T21:55:19.563080Z at Strapi.load (/srv/node_modules/strapi/lib/Strapi.js:274:19) A
2020-07-11T21:55:20.688345Z GET 500 0 B 4.5 s Chrome 83 /favicon.ico I GET 500 0 B 4.5 s Chrome 83 5f0a354800ff0a80d9edd664c60001737e736b756c70740001323032303037313174313635323139000100
I tried launching it multiple times but same error. All of the postgresql information are correct as well. What is causing this?
Edit:
this is the instructions that I followed. https://strapi.io/documentation/v3.x/deployment/google-app-engine.html
I got up to deploy the project with gcloud app deploy
Due to some Android Studio problem, I invalidated flutter cache.
When I try flutter upgrade, I'm stuck with the "Building flutter tool ..." phase
$ flutter upgrade
Downloading Dart SDK from Flutter engine beb8a7ec48f6b980a778d19eeda613635c3897c9...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 16 100 16 0 0 25 0 --:--:-- --:--:-- --:--:-- 25
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries
Warning: left.
Throwing away 16 bytes
100 219M 100 219M 0 0 6082k 0 0:00:37 0:00:37 --:--:-- 6324k
Building flutter tool...
There is no verbose log either, after I tried -v.
Now flutter doctor is stuck at the same place.
What should I do?
Solved. Seems a network issue. I'm located in China. Had to use StealthVPN with https://pub.flutter-io.cn as the host URL to finish the building. None of the other local mirrors work, which require no StealthVPN.
It's super weird that I can download the Dart SDK from ALL the mirrors but only one of them can complete the "building".
There really should be a clear warning and detailed progress report. It's hard to imagine "building ..." involving internet access.
I have been working with HFC SDK for Node.js and it used to work, but since last night I am having some problems.
When running helloblockchain.js only few times works, most time I get this error when it tries to enroll a new user:
E0113 11:56:05.983919636 5288 handshake.c:128] Security handshake failed: {"created":"#1484304965.983872199","description":"Handshake read failed","file":"../src/core/lib/security/transport/handshake.c","file_line":237,"referenced_errors":[{"created":"#1484304965.983866102","description":"FD shutdown","file":"../src/core/lib/iomgr/ev_epoll_linux.c","file_line":948}]}
Error: Failed to register and enroll JohnDoe: Error
Other times, the enroll works and the failure appears deploying the chaincode:
Enrolled and registered JohnDoe successfully
Deploying chaincode ...
E0113 12:14:27.341527043 5455 handshake.c:128] Security handshake failed: {"created":"#1484306067.341430168","description":"Handshake read failed","file":"../src/core/lib/security/transport/handshake.c","file_line":237,"referenced_errors":[{"created":"#1484306067.341421859","description":"FD shutdown","file":"../src/core/lib/iomgr/ev_epoll_linux.c","file_line":948}]}
Failed to deploy chaincode: request={"fcn":"init","args":["a","100","b","200"],"chaincodePath":"chaincode","certificatePath":"/certs/peer/cert.pem"}, error={"error":{"code":14,"metadata":{"_internal_repr":{}}},"msg":"Error"}
Or:
Enrolled and registered JohnDoe successfully
Deploying chaincode ...
E0113 12:15:27.448867739 5483 handshake.c:128] Security handshake failed: {"created":"#1484306127.448692244","description":"Handshake read failed","file":"../src/core/lib/security/transport/handshake.c","file_line":237,"referenced_errors":[{"created":"#1484306127.448668047","description":"FD shutdown","file":"../src/core/lib/iomgr/ev_epoll_linux.c","file_line":948}]}
events.js:160
throw er; // Unhandled 'error' event
^
Error
at ClientDuplexStream._emitStatusIfDone (/usr/lib/node_modules/hfc/node_modules/grpc/src/node/src/client.js:189:19)
at ClientDuplexStream._readsDone (/usr/lib/node_modules/hfc/node_modules/grpc/src/node/src/client.js:158:8)
at readCallback (/usr/lib/node_modules/hfc/node_modules/grpc/src/node/src/client.js:217:12)
E0113 12:15:27.563487641 5483 handshake.c:128] Security handshake failed: {"created":"#1484306127.563437122","description":"Handshake read failed","file":"../src/core/lib/security/transport/handshake.c","file_line":237,"referenced_errors":[{"created":"#1484306127.563429661","description":"FD shutdown","file":"../src/core/lib/iomgr/ev_epoll_linux.c","file_line":948}]}
This code worked yesterday, so I don't know what could be happening.
Does anybody know how can I fix it?
Thanks,
Javier.
ibm-bluemix
blockchain
These types of intermittent issues are usually related to GRPC. An initial suggestion is to ensure that you are using at least GRPC version 1.0.0.
If you are using a Mac, then the maximum number of open file descriptors should be checked (using ulimit -n). Sometimes this is initially set to a low value such as 256, so increasing the value could help.
There are a couple of GRPC issues with similar symptoms.
https://github.com/grpc/grpc/issues/8732
https://github.com/grpc/grpc/issues/8839
https://github.com/grpc/grpc/issues/8382
There is a grpc.initial_reconnect_backoff_ms property that is mentioned in some of these issues. Increasing the value past the 1000 ms level might help reduce the frequency of issues. Below are instructions for how the helloblockchain.js file can be modified to set this property to a higher value.
Open the helloblockchain.js file in the Hyperledger Fabric Client example and find the enrollAndRegisterUsers function.
Add “grpc.initial_reconnect_backoff_ms": 5000 to the setMemberServicesUrl call.
chain.setMemberServicesUrl(ca_url, {
pem: cert, "grpc.initial_reconnect_backoff_ms": 5000
});
Add “grpc.initial_reconnect_backoff_ms": 5000 to the addPeer call.
chain.addPeer("grpcs://" + peers[i].discovery_host + ":" + peers[i].discovery_port,
{pem: cert, "grpc.initial_reconnect_backoff_ms": 5000
});
Note that setting the grpc.initial_reconnect_backoff_ms property may reduce the frequency of issues, but it will not necessarily eliminate all issues.
The connection to the eventhub that is made in the helloblockchain.js file can also be a factor. There is an earlier version of the Hyperledger Fabric Client that does not utilize the eventhub. This earlier version could be tried to determine if this makes a difference. After running git clone https://github.com/IBM-Blockchain/SDK-Demo.git, run git checkout b7d5195 to use this prior level. Before running node helloblockchain.js from a Node.js command window, the git status command can be used to check the code level that is being used.
I am trying to install solaris studio 12.3 on a Solaris 11 x86 machine.
I have downloaded oracle cert and key from mentioned link, but while publishing am getting following error.
pkg set-publisher -k Oracle_Solaris_Studio.key.pem -c Oracle_Solaris_Studio.certificate.pem -g **PORTAL** solarisstudio
pkg set-publisher: The origin URIs for 'solarisstudio' do not appear to point to a valid pkg repository.
Please verify the repository's location and the client's network configuration.
Additional details:
Unable to contact valid package repository
Encountered the following error(s):
Unable to contact any configured publishers.
This is likely a network configuration problem.
1: Framework error: code: 7 reason: Failed connect to pkg.oracle.com:443; Connection refused
URL: '**PORTAL**' (happened 4 times)
2: Framework error: code: 28 reason: Connection timed out after 60000 milliseconds
URL: '**PORTAL**' (happened 4 times)
Please let me know if further information is required.
NOTE PORTAL - https://pkg.oracle.com/solarisstudio/release
Configuring correct proxy settings as pointed out by alanc, resolved the issue.