I am using grunt to do a build and one plugin I am using is grunt-s3 to push files (if tests successful) to the cloud.
However, I am getting:
Running "s3" task
>> Error: Upload error: /header/dist/js/lib/json2.min.js.gz (Error: connect ECONNREFUSED)
>> Error: Upload error: /header/dist/js/lib/modernizr.custom.js.gz (Error: connect ECONNREFUSED)
>> Error: Upload error: /header/dist/js/master.menu.min.js.gz (Error: connect ECONNREFUSED)
Anyone have any idea what I can check/change? My Amazon credentials are ok as I can log in using my key/secret to my bucket via cloudberry explorer on the same machine/connection so must be something node/grunt related?
EDIT
Reading npm docs says this:
"I get ECONNREFUSED a lot. What's up?
... or node's DNS isn't able to reach out."
This sounds intriguing, but I have no idea what to check or how to resolve as I am new to node.js
Related
So I'm fairly new to Near protocol. I created a near app using
npx create-near-app#latest
hello-near was the default name of the near app and folder so i just pressed enter.
npm install -g near-cli
cd hello-near
npm run build:contract
So, everything above ran smoothly. But when I went to deploy it using the command
near dev-deploy build/hello-near.wasm
And gives this output.
Starting deployment. Account id: dev-1660902746796-39871857513719, node: https://rpc.testnet.near.org, helper: https://helper.testnet.near.org, file: contract/build/hello_near.wasm
Transaction Id F7FWUEbKFqoWs9yNvk156bdmzWhHfnJ9exhWNHPREMAb
To see the transaction in the transaction explorer, please open this url in your browser
https://explorer.testnet.near.org/transactions/F7FWUEbKFqoWs9yNvk156bdmzWhHfnJ9exhWNHPREMAb
Done deploying to dev-1660902746796-39871857513719
The transaction has succeeded. But right after this, it throws a long error :https://pastebin.com/5vZpN1HD
in short, it says ECONNREFUSED 0.0.0.0:443
The problem was with my DNS. segment.io was not getting connected because I had adguardDNS. I changed my DNS to 8.8.8.8 / 8.8.4.4 and that solved the Issue and authentication was successful.
While start the nodejs lambda function by serverless offline, i am getting the below error
command : serverless offline start
Error:
Error: EISDIR: illegal operation on a directory, symlink 'R:Projects<project>\node_modules' -> 'R:Projects<project>.build\node_modules'
Please help to resolve the issue, searching for the solution since two days.
I am trying to get the archive link from my node js application.This is working fine in my local machine but i am getting error in azure private app service.
octokit.repos.getArchiveLink({owner:owner,repo:sourceRepoName,archive_format:'zipball',ref:branch})
on executing this command in azure private app service I am getting the following error:
{ Error: Command failed: wmic os get Caption
Access is denied.
at makeError (D:\home\site\wwwroot\node_modules\execa\index.js:172:9)
at Function.module.exports.sync (D:\home\site\wwwroot\node_modules\execa\index.js:341:15)
at module.exports.release (D:\home\site\wwwroot\node_modules\windows-release\index.js:34:24)
at module.exports (D:\home\site\wwwroot\node_modules\os-name\index.js:39:18)
at getUserAgentNode (D:\home\site\wwwroot\node_modules\universal-user-agent\index.js:6:51)
at restEndpoint (D:\home\site\wwwroot\node_modules#octokit\rest\lib\endpoint\index.js:27:48)
at restRequest (D:\home\site\wwwroot\node_modules#octokit\rest\lib\request\index.js:7:26)
code: 1,
stdout: '',
stderr: 'Access is denied.\r\n',
failed: true,
signal: null,
cmd: 'wmic os get Caption',
timedOut: false }
According to your error information, the issue was caused by calling the command wmic os get Caption which be prevented by the Win32k.sys (User32/GDI32) Restrictions of Azure Web App sandbox. If try to call the command via Kudu console of your WebApp, the error Access is denied will be shown as same as I got as the figure below.
So if you have to use the current node package for Windows, the only way is using Azure Windows VM instead of Azure WebApps. if not, you can try to deploy your app on Azure WebApps for Linux.
Hope it helps. Any concern, please feel free to let me know.
I have setup a sails project from production to local machine ( window). We are using sails-cassandra. Now when i am running **node app.js*. I am getting following error
> error: A hook (`orm`) failed to load!
error: Error: There was an error
> attempting to load `sails-cassandra`. (Sails attempted to load this
> adapter because it is referenced by a datastore
> (`someCassandraServer`) in this app's configuration) Please ensure
> that `sails-cassandra` is a valid Sails/Waterline adapter, and that it
> is installed in this app.
Anybody have an idea what i am missing. My Cassandra database is setup on external server, i am able to ping that server.
Logstash 5.1.1 on Windows 7 32bit, trying without success to install logstash-filter-elapsed. Below the method I tried.
Before running plugin installer, I run:
set DEBUG=1
to show debug output.
Then I run:
logstash-plugin install logstash-filter-elapsed
This fails both when I'm in my corporate network (with proxy) and when using a network without proxy, with the following error:
Looking if package named: logstash-filter-elapsed exists at https://artifacts.elastic.co/downloads/logstash-plugins/logstash-filter-elapsed/logstash-filter-elapsed-5.1.1.zip
Errno::ECONNREFUSED: Connection refused - Connection refused
initialize at org/jruby/ext/socket/RubyTCPSocket.java:126
open at org/jruby/RubyIO.java:1197
connect at C:/tools/logstash-5.1.1/vendor/jruby/lib/ruby/1.9/net/http.rb:763
timeout at org/jruby/ext/timeout/Timeout.java:98
connect at C:/tools/logstash-5.1.1/vendor/jruby/lib/ruby/1.9/net/http.rb:763
do_start at C:/tools/logstash-5.1.1/vendor/jruby/lib/ruby/1.9/net/http.rb:756
start at C:/tools/logstash-5.1.1/vendor/jruby/lib/ruby/1.9/net/http.rb:745
start at C:/tools/logstash-5.1.1/vendor/jruby/lib/ruby/1.9/net/http.rb:557
start at C:/tools/logstash-5.1.1/lib/pluginmanager/utils/http_client.rb:13
remote_file_exist? at C:/tools/logstash-5.1.1/lib/pluginmanager/utils/http_client.rb:23
get_installer_for at C:/tools/logstash-5.1.1/lib/pluginmanager/pack_fetch_strategy/repository.rb:27
create at C:/tools/logstash-5.1.1/lib/pluginmanager/install_strategy_factory.rb:15
each at org/jruby/RubyArray.java:1613
create at C:/tools/logstash-5.1.1/lib/pluginmanager/install_strategy_factory.rb:14
execute at C:/tools/logstash-5.1.1/lib/pluginmanager/install.rb:27
run at C:/tools/logstash-5.1.1/vendor/bundle/jruby/1.9/gems/clamp-0.6.5/lib/clamp/command.rb:67
execute at C:/tools/logstash-5.1.1/vendor/bundle/jruby/1.9/gems/clamp-0.6.5/lib/clamp/subcommand/execution.rb:11
run at C:/tools/logstash-5.1.1/vendor/bundle/jruby/1.9/gems/clamp-0.6.5/lib/clamp/command.rb:67
run at C:/tools/logstash-5.1.1/vendor/bundle/jruby/1.9/gems/clamp-0.6.5/lib/clamp/command.rb:132
(root) at C:\tools\logstash-5.1.1\lib\pluginmanager\main.rb:46
It seems that there's a timeout in contacting the url "https://artifacts.elastic.co/downloads/logstash-plugins/logstash-filter-elapsed/logstash-filter-elapsed-5.1.1.zip".
Opening this url in a browser returns an xml with an error message (seems like the xml you when trying to access a not existing object from a AWS S3 bucket).
Adding the --no-verify flag yelds the same result.
EDIT
I tried to bypass this problematic "Looking if package named:..." step: I edited logstash-5.1.1\lib\pluginmanager\pack_fetch_strategy\repository.rb, adding a return nil at the beginning of the def get_installer_for(plugin_name).
Running the installation, I get another error:
Installing logstash-filter-elapsed
Error Bundler::HTTPError, retrying 1/10
Could not fetch specs from https://rubygems.org/
Error Bundler::HTTPError, retrying 2/10
Could not fetch specs from https://rubygems.org/
...