I tried to run expo start or yarn start and the console threw an error. On wsl1 it is working fine, it shows the QR code. However, I have to switch to wsl2 to set up mysql for my local server and now expo is not starting.
Also sometimes the QR code shows up but when I try to open the app in my device, the same error shows up.
Developer tools running on http://localhost:19002
Could not get status from Metro bundler. connect ECONNREFUSED 127.0.0.1:19001
Connecting to Metro bundler failed.
Error: Connecting to Metro bundler failed.
at _waitForRunningAsync (/home/kevsmercs/.nvm/versions/node/v12.13.0/lib/node_modules/expo-cli/node_modules/xdl/src/start/startLegacyReactNativeServerAsync.ts:344:11)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
I think the problem here is expo itself. I tried to I check the developer tools url, the site cant be reached. I also tried to check my account using expo login and this error shows up
Fetching the user profile failed
connect ECONNREFUSED 127.0.0.1:8888
connect ECONNREFUSED 127.0.0.1:8888
Error: connect ECONNREFUSED 127.0.0.1:8888
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1128:14)
jest-haste-map: Watchman crawl failed. Retrying once with node crawler. Usually this happens when watchman isn't running. Create an empty .watchmanconfig file in your project's root folder or initialize a git or hg repository in your project. Error: Watchman error: query failed: synchronization failed: Connection timed out. Make sure watchman is running for this project. See https://facebook.github.io/watchman/docs/troubleshooting.html.
I tried multiple fixes but no luck.
1. set `REACT_NATIVE_PACKAGER_HOSTNAME` to my ip using `export`
2. delete `.expo` from root of project and run `expo start -c`
3. turn off windows defender and firewall
4. update `expo-cli` to latest (4.4.1)
5. restart laptop
Maybe this GitHub issue describes your problem and the workaround?
This can usually happen when publishing without ever having run expo start, also it's a good idea to run rm -rf .expo to clear your local state
it's listed in our common development errors
Your latest edit shows this error message and suggested fix: Usually this happens when watchman isn't running. Create an empty .watchmanconfig file in your project's root folder or initialize a git or hg repository in your project. Did you try that?
Related
I have setup Sonarqube in my Ec2 earlier using java version 1.8 and it was running fine. Now also I am using java 1.8 for this. I have configured sonarqube by making a user in root in ec2 and inside opt folder I have configured everything for it. Now its not working. I am using ./sonar.sh start for starting the sonarqube in it.After sometime when I check the status of sonar it shows its not running.
Attaching the screenshot for the same.
enter image description here
Sonar Sever will not work with root account as it uses elastic search. Therefore, the service will stop as you as you run the start command. You can go to logs and see the error.
Log files shows the root cause for the error
Create a normal user to start sonar server. If you are using ubuntu, you can use ubuntu user or create a new one.
Once user is created, sonar.sh file and search for RUN_AS_USER parameter.
set your non root user in sonar.sh file
check the ownership of sonar directory as follows:
check sonar directory ownership
If package is not installed, ru below command to install ACL.
access control list installation on ubuntu
Change the ownership of directory/ sub dir as follows:
change ownership of directory
Restart sonar server as follows:
start sonar server
Get the status after start
check the status
Finally, Go to your network settings in EC# and open port 9000.
My current set up has a Django project running on Windows 2016 IIS.
The project is hosted on GitHub for collaboration and I would like to set up a GitHub webhook so whenever there's a push to master branch from any of the collaborators, the IIS Server will run a "git pull" to update the project on the server.
What is normally the setup for this?
What I have tried so far is to create an endpoint in the Django project, this endpoint whenever called will run Python subprocess to run "git pull" command in the project itself. However, whenever I run it, it get a 500 response from IIS.
Thanks #VonC for helping.
I have looked to the log (which was the one in XML) but it wasn't much help.
What I'm posting here was my workaround, not exactly to the answer for the question above.
I used django-background-tasks to add the command subprocess.run(['git', 'pull']) as a task to run later (after a few seconds after that by the #background decorator).
Error 500 means the IIS server throws an error.
You need to check said IIS server logs in order to check at what point in the execution of the webhook endpoint script the error occurs.
I'm setting active host and having Docker client point at it:
docker-machine env [instance name]
That gives me output:
Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host. You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'
when I try to regenerate the certs I get this from the debug log: fork/exec /usr/bin/ssh: permission denied
Changing permission settings for the directory didn't help. How can I troubleshoot it ?
Solution found here https://www.digitalocean.com/community/questions/ssh-not-available-when-creating-docker-machine-through-digitalocean
Problem was running Docker as a snap (Ubuntu's repo) instead of official build from Docker. As soon as I uninstalled the Docker snap and installed official build SSH problem has gone away.
I'm working with a website running on laravel. The site works fine on my local through Homestead, no problems.
Recently, I pushed the git repo up to a server that never had this site running on it before. I set everything up right (had some nginx config issues for a while, but got those all sorted out). Nginx has the public folder set as the site root, so it hits the proper index page when you load the page.
What I'm getting is a 500 error. My error logs reveal the following is the reason:
site_root/public/../bootstrap/autoload.php - Failed to open stream: permission denied
in
site_root/public/index.php on line 22
I can confirm that the bootstrap folder and the autoload.php file are both accessible by the web user, and have permissions that should allow access.
I've read a few cases online of people solving this issue with a 'composer install'. I tried updating composer, doing an install, and dumping its cache. I also tried removing the vendor folder (which had been a part of the git repo), and running composer install to regenerate it. None of these have worked. Happy to supply any info that will help. This is Laravel 5.2 running on Ubuntu Server 14.04 with nginx, all on an AWS box.
Solved it. This was actually an issue with site-wide permissions. They were set to 770 instead of 775. I suspect that I can and should restrict them more. For now, I'm just happy to have it loading again.
Moral of the story is to check your permissions site-wide, not necessarily just on the file which gives you the fatal error. You may continue to get the same fatal error, despite permissions being wide-open on the mentioned file. If so, look for permissions issues elsewhere.
We have upgraded the Bitnami Redmine from 2.4.2-0 to 2.6.0-0 on a Windows server.
When we try to access (localhost/redmine) but after upgrading Redmine, it shows the following error:
Internal error
An error occurred on the page you were trying to access.
If you continue to experience problems please contact your Redmine administrator for assistance.
If you are the Redmine administrator, check your log files for details about the error.
Below is the error found in log file,
GET "/redmine/" for 127.0.0.1 at 2014-11-18 14:19:53 +0530
Processing by WelcomeController#index as HTML Current user: anonymous Completed 500 Internal Server Error in 65.0ms
NoMethodError (undefined method passwd_changed_on' for #<AnonymousUser:0x67c50d8>): app/controllers/application_controller.rb:149:in force_logout_if_password_changed'
You should run this command:
% ruby bin/rake db:migrate RAILS_ENV=production
In the root directory of your redmine install.