I have a problem with my fastapi/uvicorn logs in terminal.There are a lot of incomprehensible qusetion marks in log. Os: win10, version of fastapi: latest
Related
For work, the development stack we use is nginx + php + apache + mariadb, and using mac (with m1 chip).
I set up the development environment using brew.
The installation of the services was successful and even running the brew doctor command I am not shown any errors.
However, I have a problem with starting mariadb, that is when I launch brew services start mariadb with mariadb latest, that is 10.6, I get the message of service started successfully, but when I do brew services under mariadb it service status is stopped.
I am new to mac os, I have tried to search online but everything I have tried so far has not worked.
Do you have any suggestions or advice?
EDIT:
if i try to start service with mysql.server startcommand, i've this error:
Starting MariaDB
.211209 11:55:38 mysqld_safe Logging to '/opt/homebrew/var/mysql/Mac-mini-di-Ezio.local.err'.
211209 11:55:38 mysqld_safe Starting mariadbd daemon with databases from /opt/homebrew/var/mysql
/opt/homebrew/bin/mysql.server: line 264: kill: (73339) - No such process
ERROR!
I have a ddev installation on macOS which I used for a while.
ddev 1.16.2
docker 20.10.0
macOS 11.0.1 - Intel
Today I upgraded to docker 20.10.0 and in the process to ddev 1.16.2.
When I start an existing site, that worked all the time I get
Creating ddev-mysite-db ... error
ERROR: for ddev-mysite-db Cannot create container for service db: invalid mount config for type "bind": bind source path does not exist: /host_mnt/Users/me/Documents/Development/WebSite/mysite/.ddev
This started to happen after I upgraded docker from the previous version. Upgrading ddev did not change too much.
Even when I create a new site, the same error message pops up so I am pretty much stuck.
At least for me it looks like the docker 20.10.0 breaks ddev. Any ideas how to deal with that are very much appreciated.
Docker/macOS are not allowing access to the directory ~/Documents.
Starting with macOS Catalina, ~/Documents is a "protected directory", so you have to allow docker access to it, and docker should prompt.
However, Docker Desktop for Mac's 3.0.0 release (which I imagine you're referring to) had a bug where it did not do this properly. I imagine you need to upgrade to version 3.0.1 which was released today. Just "Check for updates"
In Docker > Preferences > Experimental features you can try disabling gRPC, and make Docker use osxfs file sharing system.
Reference: https://github.com/docker/for-mac/issues/4859#issuecomment-689012097
I'm very new to Gatsby and have just started reading up on the website's tutorial here. However, I'm having some trouble running the gatsby develop command as it throws an error and displays only this message and nothing else:
Looks like develop for this site is already running, can you visit http://://localhost:8000 ? If it is not, try again in five seconds!
When I click on http://://localhost:8000, the page just says localhost refused to connect.
Below is the output of gatsby info -C:
System:
OS: macOS High Sierra 10.13.6
CPU: (4) x64 Intel(R) Core(TM) i5-2415M CPU # 2.30GHz
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 14.4.0 - ~/.nvm/versions/node/v14.4.0/bin/node
npm: 6.14.5 - ~/.nvm/versions/node/v14.4.0/bin/npm
Languages:
Python: 2.7.14 - /usr/local/bin/python
Browsers:
Chrome: 85.0.4183.102
Safari: 11.1.2
npmPackages:
gatsby: ^2.24.54 => 2.24.54
npmGlobalPackages:
gatsby-cli: 2.12.94
I've also tried uninstalling and installing the gatsby-cli, but the issue persists. Also checked if anything's running on port 8000 using lsof -i TCP:8000, but nothing came up.
If someone could shed some light as to where the issue's coming from, I'd greatly appreciate it!
PS: I tried running gatsby build and gatsby serve, and encountered no problems.
This is because of the port of the OS firewall. You can easily fix it by adding a port to the default Gatsby running command (in your package.json):
gatsby develop -p 8001
Note the -p flag, as you can see in the documentation it change Gatsby's running port. Of course, you can change the 8001 for any desired (and unused) port. Changing it won't affect the Gatsby project because it will readapt the GraphQL playground to it.
Most likely you'd have to open port 8000 on the firewall.
On OSX this should be pfctl & /etc/pf.conf.
Trying to start elasticsearch 2.4.6 with ./elasticsearch in the bin direcytory. It just closes and nothing happens. See the below screenshot
Stepping through the starter scripts, I can see that it comes until exec "$JAVA" $JAVA_OPTS $ES_JAVA_OPTS -Des.path.home="$ES_HOME" -cp "$ES_CLASSPATH" org.elasticsearch.bootstrap.Elasticsearch start "$#" line and then closes.
However, please note that elasticsearch 5.* does not have this problem and starts normally without error
Can anyone tell me what could possibly be causing this? Or at least where can I find any error log. No error is logged in logs file of elasticsearch.
The problem was due to a kernel bug due to a fix for meltdown vulnerability. It is fixed by downgrading the kernel. (Or upgrading elasticsearch or the kernel as for now.)
Started STS using terminal in ubuntu 14.04 (./STS) and it turns white blank and didn't get started. And at terminal gets this info -
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
I am using Open JDK7 (1.7.0_65), STS - 3.6.1 and Ubuntu - 14.04 all 64 bit. Didn't get any log too.
Please tell what to do?
Set mozilla as your browser in STS. To do that add
-Dorg.eclipse.swt.browser.DefaultType=mozilla
at the end of STS.ini.