Yes, in macOS the purpose of document quarantine is to get in your way and ruin your day.įind a document, any document, so long as it has a quarantine flag attached to it.
Brew start copyq free#
I think I’ve found it: they can stop you from opening documents, even those which are known to be free of malware and have never been near the Internet.
Brew start copyq how to#
Now the problem is: how to revert to previous version or upgrade old data to new version of postgres DB, but this is for another topic.Last week, I looked at quarantine flags on documents, and wondered what their true purpose was. 14:19:26.166 CEST DETAIL: The data directory was initialized by PostgreSQL version 13, which is not compatible with this version 14.3. 14:19:26.166 CEST FATAL: database files are incompatible with server 14:19:16.128 CEST DETAIL: The data directory was initialized by PostgreSQL version 13, which is not compatible with this version 14.3. 14:19:16.128 CEST FATAL: database files are incompatible with server
14:19:06.111 CEST DETAIL: The data directory was initialized by PostgreSQL version 13, which is not compatible with this version 14.3. 14:19:06.111 CEST FATAL: database files are incompatible with server 14:18:56.071 CEST DETAIL: The data directory was initialized by PostgreSQL version 13, which is not compatible with this version 14.3. 14:18:56.071 CEST FATAL: database files are incompatible with server
14:18:46.029 CEST DETAIL: The data directory was initialized by PostgreSQL version 13, which is not compatible with this version 14.3. 14:18:46.029 CEST FATAL: database files are incompatible with server Is the server running locally and accepting connections on that socket?Ĭhecking postgres log as mentioned by helped, in my case it was:Īnd the issue was clear: $ tail /usr/local/var/log/postgres.log Psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: No such file or directory => Successfully started `postgresql` (label: )īut there still was a problem when trying to connect: $ psql -d postgres -U apiuser => Successfully stopped `postgresql` (label: ) I've tried restart and it looked promising: $ brew services restart postgres $ brew services start postgresqlĮrror: Failure while executing `/bin/launchctl bootstrap gui/501 /Users/yrk/Library/LaunchAgents/` exited with 5. I had similar error in regard to postgres. I quickly fixed this and apache started up. It turned out that after the php upgrade, the php version had changed and I forgot to write the new php version in the apache configuration file. Then it was finally clear what was the reason why httpd service was not starting. Httpd: Syntax error on line 66 of /opt/homebrew/etc/httpd/nf: Cannot load into server: 0x000A): tried: (no such file), '/usr/local/lib/libphp5.so' (no such file), '/usr/lib/libphp5.so' (no such file) To do this I ran apache without brew: $ /opt/homebrew/Cellar/httpd/2.4.51/bin/apachectl start At first I tried to use the tips from the answers in this thread, but neither reinstalling apache nor unload -w/load -w helped. Unfortunately brew doesn't show the user what causes this error. Users/john/Library/LaunchAgents/` exited with Try re-running the command as root for richer errors.Įrror: Failure while executing `/bin/launchctl bootstrap gui/501 I had a similar problem, but instead of mongodb, I could not start apache(httpd). To see the real errors, you need to run the service without brew
0 kommentar(er)
