brew services start nginx - nginx

sudo brew services start nginx
Bootstrap failed: 37: Operation already in progress
Error: Failure while executing; /bin/launchctl bootstrap system /Library/LaunchDaemons/homebrew.mxcl.nginx.plist exited with 37.

Related

Upgrading R gives error - Failed to connect to Mir: Failed to connect to server socket: No such file or directory

I'm currently using R version 3.6.1 and I'm trying to update it to R/4.2. I tried following instructions here and here. But everytime i try sudo add-apt-repository 'deb https://cloud.r-project.org/bin/linux/ubuntu focal-cran40/, I'm getting this error
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
How do I resolve this ?

Nginx upgrade from 1.16 to 1.18 failed due to module discrepancy on Ubuntu 16.04

I installed Nginx 1.18.0 using this guide, however, the install failed with the following error:
nginx: [emerg] module "/etc/nginx/modules/ngx_http_dav_ext_module.so" version 1016001 instead of 1018000 in /etc/nginx/modules-enabled/50-mod-http-dav-ext.conf:1 nginx: configuration file /etc/nginx/nginx.conf test failed
I tried to install with
apt install libnginx-mod-http-dav-ext, but received the following:
libnginx-mod-http-dav-ext is already the newest version (1.16.1-0+xenial1).
I currently have the line include /etc/nginx/modules-enabled/*.conf; in /etc/nginx/nginx.conf commented out, but this cannot stay, since it is a production server. Why is the error showing 1.16.1-0+xenial1 when I installed 1.18.0?

I cannot install any node package with npm

I upgraded my npm to the latest version and now I can't run any npm command again, I uninstalled the node js and downloaded it again,
when I ran npm install -g ionic#latest I got this error in my command prompt:
npm WARN deprecated ionic#5.4.16: The Ionic CLI now uses ✨ #ionic/cli ✨ for its package name! 👉 https://twitter.com/ionicframework/status/1223268498362851330
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! network request to https://registry.npmjs.org/env-paths failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\De Stone Of David\AppData\Roaming\npm-cache\_logs\2020-03-23T11_48_48_277Z-debug.log
I don't know what to do now, I also ran npm cache clean --force in powershell as admin and got the same error.
This is a case where reading the error message carefully can help. The key line is
npm ERR! network request to https://registry.npmjs.org/env-paths failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org
ENOTFOUND is a message delivered by your OS to npm. It means npm's attempt to use the Domain Name Service (DNS) to look up that registry machine's hostname failed.
So, you have a networking-connectivity problem, or, less likely, a firewall problem. Try this on a command line on your machine.
curl https://registry.npmjs.org
If it, too, doesn't work, try rebooting your machine. If that doesn't work, ask a network engineer for help and mention the curl command as evidence of the problem.
Some home ISPs (I'm looking at you, Comcast) sometimes have connectivity trouble that shows up as DNS failures. Power-cycle your cable modem and router. If that doesn't help, call tech support and ask them to reset your modem remotely.
If you have a VPN in use try disconnecting from it, then try your npm operation again. If it works without the VPN, then ask the person who maintains the VPN for help.
I have no trouble getting to that hostname from my location.

Xdebug via SSH in PhpStorm - doesn't stop at breakpoint

I have project via SSH in PhpStorm.
I'm trying run PHPUnit script with debugger and I see this message:
Connection with 'Xdebug 2.6.0' was not established
In xdebug.log I see:
Log opened at 2018-07-11 08:52:42
I: Connecting to configured address/port: 46.170.254.34:9001.
W: Creating socket for '46.170.254.34:9001', poll success, but error: Operation now in progress (29).
E: Could not connect to client. :-(
Log closed at 2018-07-11 08:52:42
In console I see:
ssh://xxxx#xxxx.pl:22/usr/bin/php -dxdebug.remote_enable=1 -dxdebug.remote_mode=req -dxdebug.remote_port=9001 -dxdebug.remote_host=11.11.11.11 /home/path/vendor/phpunit/phpunit/phpunit --bootstrap /home/path/vendor/autoload.php --configuration /home/path/phpunit.xml --filter "/(::testGettingMe)( .*)?$/" App\Tests\Functional\Context\Api\MeControllerTest /home/path/tests/Functional/Context/Api/MeControllerTest.php --teamcity
Any suggestion?

Meteor deploy Bcrypt error Invoking deployment process

I want to deploy a meteor app (v1.2) to digital ocean. I am using MUP with this tutorial.
When I run mup deploy verbose I get this error (see below). I tried this as well being how i am on linux. meteor build myAppHere --architecture os.linux.x86_64 . But I still get the error.
Any ideas?
Started TaskList: Deploy app 'myAppHere' (linux)
[162.243.58.84] - Uploading bundle
[162.243.58.84] - Uploading bundle: SUCCESS
[162.243.58.84] - Setting up Environment Variables
[162.243.58.84] - Setting up Environment Variables: SUCCESS
[162.243.58.84] - Invoking deployment process
[162.243.58.84] x Invoking deployment process: FAILED
-----------------------------------STDERR-----------------------------------
ile=node.lib',
gyp info spawn args '-Dmodule_root_dir=/opt/myAppHere/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt',
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args 'build',
gyp info spawn args '-Goutput_dir=.' ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
gyp info ok
npm WARN package.json meteor-dev-bundle#0.0.0 No description
npm WARN package.json meteor-dev-bundle#0.0.0 No repository field.
npm WARN package.json meteor-dev-bundle#0.0.0 No README data
stop: Unknown instance:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to localhost port 81: Connection refused
Latest deployment failed! Reverted back to the previous version.
What is your node version? Most probably installed nodejs version is old. You can try with "nodeVersion": "0.10.40" in your mup.json

Resources