blocks|key|3319810|text|我从版本点击中得到了安装postgresql93的相同错误。通过检查brew+services+list(~/Library/LaunchAgents/homebrew.mxcl.postgresql93.plist)输出中指示的brew+services+list文件，我发现了以下消息：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3319811|致命:数据目录"/usr/local/var/postgres“具有组或世界访问权限
详细信息:权限应该是u=rwx+(0700)。|blockquote|3319812|这让我找到了这样的答案：data+directory+"/usr/local/var/postgres"+has+wrong+ownership|3319813|在运行sudo+chmod+-R+700+/usr/local/var/postgres之后，我得到了另一个错误：|3319814|致命:无法打开目录"pg_tblspc"：没有这样的文件或目录|3319815|然后我发现：+missing+after+installation+of+latest+version+of+OS+X+(Yosemite+or+El+Capitan)|3319816|运行mkdir+/usr/local/var/postgres/pg_tblspc/后，集群成功启动。|3319817|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/35078217/data-directory-usr-local-var-postgres-has-wrong-ownership|1|https://stackoverflow.com/questions/25970132/pg-tblspc-missing-after-installation-of-latest-version-of-os-x-yosemite-or-el^0|Y|I|1H|1J|37|I|0|0|C|1O|0|0|3|15|0|0|6|26|1|0|2|14|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|19|8|@]|D|@]|E|$]]|$1|I|3|J|5|6|7|1A|8|@]|D|@$9|1B|A|1C|1|1D]]|E|$]]|$1|K|3|L|5|6|7|1E|8|@$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|1H|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|1I|8|@]|D|@$9|1J|A|1K|1|1L]]|E|$]]|$1|Q|3|R|5|6|7|1M|8|@$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1P|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]|10|$5|V|W|X|E|$Y|11]]]]

I got the same error installing postgresql93 from the versions tap.
Inspecting the .plist file indicated in the output of <code>brew services list</code>(<code>~/Library/LaunchAgents/homebrew.mxcl.postgresql93.plist</code>) I found the following message:

<blockquote>
 FATAL: data directory "/usr/local/var/postgres" has group or world access 
 DETAIL: Permissions should be u=rwx (0700).
</blockquote>

Which led me to this answer: <a href="https://stackoverflow.com/questions/35078217/data-directory-usr-local-var-postgres-has-wrong-ownership">data directory &quot;/usr/local/var/postgres&quot; has wrong ownership</a>

After running <code>sudo chmod -R 700 /usr/local/var/postgres</code> I got a different error:

<blockquote>
 FATAL: could not open directory "pg_tblspc": No such file or directory
</blockquote>

Which then led me to: <a href="https://stackoverflow.com/questions/25970132/pg-tblspc-missing-after-installation-of-latest-version-of-os-x-yosemite-or-el">`pg_tblspc` missing after installation of latest version of OS X (Yosemite or El Capitan)</a>

After running <code>mkdir /usr/local/var/postgres/pg_tblspc/</code> the cluster started successfully.

blocks|key|1717676|text|我也犯了同样的错误，我通过删除进程pid文件修复了它：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1717677|rm+-f+/usr/local/var/postgres/postmaster.pid|offset|length|style|CODE|1717678|entityMap^0|0|0|18|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I had the same error and I fixed it by removing the process pid file:
<code>rm -f /usr/local/var/postgres/postmaster.pid</code>

blocks|key|1719435|text|我会把威尔逊和蚱蜢的两个答案结合起来。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1719436|您可以使用brew+services+list检查postgres服务的plist文件，找到文件的位置，然后在您最喜欢的编辑器中打开它。|offset|length|style|CODE|1719437|您应该看到列出的StandardErrorPath值如下：|1719438|<key>StandardErrorPath</key>
<string>/usr/local/var/log/postgres.log</string>|code-block|syntax|javascript|1719439|然后，应该使用tail+-n+100+/usr/local/var/log/postgres.log跟踪日志文件的末尾。|1719440|在我的例子中，错误如下：|1719441|2017-12-06+11:51:16.078格林尼治时间85476致命:锁文件"postmaster.pid“已经存在了2017-12-06+11:51:16.078+GMT+85476提示:另一位邮政管理员(PID+601)是否运行在数据目录"/usr/local/var/postgres"？|blockquote|1719442|这是因为我不得不硬关机，我的Mac和postgres没有机会清理PID文件。只需删除PID文件rm+/usr/local/var/postgres/postmaster.pid并启动postgres+brew+services+start+postgresql即可。|1719443|警告：不要删除这个PID文件，除非您确信postgres没有运行。您可以通过运行brew+services+stop+postgresql，然后等待brew+services+list的结果显示posgres处于已停止状态来完成此操作。|BOLD|1719444|entityMap^0|0|5|I|0|8|H|0|0|7|17|0|0|0|1B|15|2S|U|0|3|T|14|T|22|I|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|19|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1A|8|@$D|1B|E|1C|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1D|8|@]|9|@]|A|$]]|$1|S|3|T|5|U|7|1E|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1F|8|@$D|1G|E|1H|F|G]|$D|1I|E|1J|F|G]]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1K|8|@$D|1L|E|1M|F|Z]|$D|1N|E|1O|F|G]|$D|1P|E|1Q|F|G]]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|11|$]]

I would combine the two answers from Wilson and Grasshopper here.

You can check the plist file for the postgres service using <code>brew services list</code> to find the location of the file and just opening it up in you favourite editor.

You should see the value of <code>StandardErrorPath</code> listed as: 

<pre><code>&lt;key&gt;StandardErrorPath&lt;/key&gt;
&lt;string&gt;/usr/local/var/log/postgres.log&lt;/string&gt;
</code></pre>

And then you should tail the end of the log file using <code>tail -n 100 /usr/local/var/log/postgres.log</code>

In my case the error was the following: 

<blockquote>
 2017-12-06 11:51:16.078 GMT [85476] FATAL: lock file "postmaster.pid" already exists
 2017-12-06 11:51:16.078 GMT [85476] HINT: Is another postmaster (PID 601) running in data directory "/usr/local/var/postgres"?
</blockquote>

This was because I had to hard shutdown my Mac and postgres didn't get a chance to cleanup the PID file. Just remove the PID file <code>rm /usr/local/var/postgres/postmaster.pid</code> and start postgres <code>brew services start postgresql</code>

A word of warning: do not delete this PID file unless you are sure that postgres is not running. You can do this by running <code>brew services stop postgresql</code> and then waiting for the result of <code>brew services list</code> to show posgres is in the stopped state.

blocks|key|3319904|text|我今天遇到了这个问题。postgres不再接受连接，尽管家酿公司认为它在运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3319905|为了修复它我跑了，|3319906|brew+services+restart+-vvv+postgresql|code-block|syntax|javascript|3319907|这个命令的输出，|3319908|==>+Successfully+stopped+`postgresql`+(label:+homebrew.mxcl.postgresql)
==>+Generated+plist+for+postgresql:
+++<?xml+version="1.0"+encoding="UTF-8"?>
+++<!DOCTYPE+plist+PUBLIC+"-//Apple//DTD+PLIST+1.0//EN"+"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+++<plist+version="1.0">
+++<dict>
+++++<key>KeepAlive</key>
+++++<true/>
+++++<key>Label</key>
+++++<string>homebrew.mxcl.postgresql</string>
+++++<key>ProgramArguments</key>
+++++<array>
+++++++<string>/usr/local/opt/postgresql/bin/postgres</string>
+++++++<string>-D</string>
+++++++<string>/usr/local/var/postgres</string>
+++++</array>
+++++<key>RunAtLoad</key>
+++++<true/>
+++++<key>WorkingDirectory</key>
+++++<string>/usr/local</string>
+++++<key>StandardErrorPath</key>
+++++<string>/usr/local/var/log/postgres.log</string>
+++</dict>
+++</plist>|3319909|然后我想，嗯，也许日志文件里有什么东西，|3319910|tail+-n+10+/usr/local/var/log/postgres.log|3319911|当然了，|3319912|[4826]+FATAL:++lock+file+"postmaster.pid"+already+exists
[4826]+HINT:++Is+another+postmaster+(PID+1489)+running+in+data+directory+"/usr/local/var/postgres"?|3319913|所以，我删除了那个文件|3319914|rm+/usr/local/var/postgres/postmaster.pid|3319915|一切又开始运作了。|3319916|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|16|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|18|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|1A|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|1B|8|@]|9|@]|A|$]]|$1|W|3|X|5|F|7|1C|8|@]|9|@]|A|$G|H]]|$1|Y|3|Z|5|6|7|1D|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|11|$]]

I ran into this problem today. postgres stopped accepting connections though homebrew thought it was running.
To fix it I ran,
<pre><code>brew services restart -vvv postgresql
</code></pre>
Output from this command,
<pre><code>==&gt; Successfully stopped `postgresql` (label: homebrew.mxcl.postgresql)
==&gt; Generated plist for postgresql:
 &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;!DOCTYPE plist PUBLIC &quot;-//Apple//DTD PLIST 1.0//EN&quot; &quot;http://www.apple.com/DTDs/PropertyList-1.0.dtd&quot;&gt;
 &lt;plist version=&quot;1.0&quot;&gt;
 &lt;dict&gt;
 &lt;key&gt;KeepAlive&lt;/key&gt;
 &lt;true/&gt;
 &lt;key&gt;Label&lt;/key&gt;
 &lt;string&gt;homebrew.mxcl.postgresql&lt;/string&gt;
 &lt;key&gt;ProgramArguments&lt;/key&gt;
 &lt;array&gt;
 &lt;string&gt;/usr/local/opt/postgresql/bin/postgres&lt;/string&gt;
 &lt;string&gt;-D&lt;/string&gt;
 &lt;string&gt;/usr/local/var/postgres&lt;/string&gt;
 &lt;/array&gt;
 &lt;key&gt;RunAtLoad&lt;/key&gt;
 &lt;true/&gt;
 &lt;key&gt;WorkingDirectory&lt;/key&gt;
 &lt;string&gt;/usr/local&lt;/string&gt;
 &lt;key&gt;StandardErrorPath&lt;/key&gt;
 &lt;string&gt;/usr/local/var/log/postgres.log&lt;/string&gt;
 &lt;/dict&gt;
 &lt;/plist&gt;
</code></pre>
Then I thought, hmm maybe there's something in that log file,
<pre><code>tail -n 10 /usr/local/var/log/postgres.log
</code></pre>
Sure enough,
<pre><code>[4826] FATAL: lock file &quot;postmaster.pid&quot; already exists
[4826] HINT: Is another postmaster (PID 1489) running in data directory &quot;/usr/local/var/postgres&quot;?
</code></pre>
So, I removed that file
<pre><code>rm /usr/local/var/postgres/postmaster.pid
</code></pre>
And everything started working again.

blocks|key|1717719|text|对我起作用的是删除/usr/local/var/postgres/文件夹，然后再卸载和安装postgres|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1717720|entityMap^0|9|O|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

What worked for me was removing the <code>/usr/local/var/postgres/</code> folder and then uninstalling and installing postgres again

blocks|key|1719489|text|在我的例子中，postmaster.pid文件甚至不存在。通过升级postgres就可以工作了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1719490|brew+update
brew+upgrade|code-block|syntax|javascript|1719491|然后，由于我将主要版本从10升级到11，所以我还必须运行以下命令：|1719492|brew+postgresql-upgrade-database|1719493|(源https://github.com/facebook/react-native/issues/18760#issuecomment-410533581)|1719494|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/facebook/react-native/issues/18760#issuecomment-410533581^0|7|E|0|0|0|0|2|24|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|14|8|@]|D|@$9|15|A|16|1|17]]|E|$]]|$1|Q|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

In my case the <code>postmaster.pid</code> file wasn't even there. Got it working by upgrading postgres.

<pre><code>brew update
brew upgrade
</code></pre>

Then, because I upgraded the major version from 10 to 11, I also had to run this:

<pre><code>brew postgresql-upgrade-database
</code></pre>

(source <a href="https://github.com/facebook/react-native/issues/18760#issuecomment-410533581" rel="noreferrer">https://github.com/facebook/react-native/issues/18760#issuecomment-410533581</a>)

blocks|key|2911515|text|使用命令更新它|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2911516|++brew+postgresql-upgrade-database|code-block|syntax|javascript|2911517|如果您有以下错误命令'brew‘未找到，则可以安装+，但可以安装:+sudo+apt安装linuxbrew包装器。|offset|length|style|BOLD|2911518|然后使用命令安装它。|2911519|+sudo+apt+install+linuxbrew-wrapper|2911520|entityMap^0|0|0|8|H|Q|U|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@$I|V|J|W|K|L]|$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

update it by using command 

<pre><code> brew postgresql-upgrade-database
</code></pre>

if you have following error 
Command 'brew' not found, but can be installed with:
sudo apt install linuxbrew-wrapper

then install it by using command 

<pre><code> sudo apt install linuxbrew-wrapper
</code></pre>

blocks|key|2911544|text|在我自己的例子中，postgres.log文件包含这个HINT:++Is+another+postmaster+already+running+on+port+5432?+If+not,+remove+socket+file+"/tmp/.s.PGSQL.5432"+and+retry.，在删除套接字文件并重新启动之后，一切正常。请注意，这是一个隐藏的文件，将无法通过窗口浏览器可见。移除应通过命令行进行。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2911545|entityMap^0|9|C|R|39|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

In my own case, the <code>postgres.log</code> file contains this <code>HINT: Is another postmaster already running on port 5432? If not, remove socket file "/tmp/.s.PGSQL.5432" and retry.</code> After removing the socket file and restarting, everything worked fine. Note that this is a hidden file and won't be visible through the window browser. Removal should be done via the command line.

blocks|key|3320082|text|万一安装了多个版本的postgresql。下面提到的命令将完成移除进程id(pid)并重新启动它的工作。只需确保选择正确的版本即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3320083|rm+-f+/usr/local/var/postgresql@9.6/postmaster.pid

brew+services+restart+postgresql@9.6+++|code-block|syntax|javascript|3320084|也请参考Eric的答案来确认这个问题是否与日志文件中的“锁文件postmaster.pid已经存在”有关。|3320085|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In case you have multiple versions of postgresql installed. Below mentioned commands will do the job of removing process id(pid) and restarting it. Just make sure you select the correct version.
<pre><code>rm -f /usr/local/var/postgresql@9.6/postmaster.pid

brew services restart postgresql@9.6 
</code></pre>
Please also refer to Eric Corner's answer to confirm if the issue is about &quot;lock file postmaster.pid already exists&quot; in log file.

blocks|key|2911588|text|您可能会看到libssl/libcrypto版本之间的冲突。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2911589|brew+services+start+postgres日志给了我nada，但手动启动pg_ctl+-D+/usr/local/var/postgres+start指出：|offset|length|style|CODE|2911590|缺少/./openssl/lib/libcryption.1.0.0.dylib中的定义_RAND_cleanup|2911591|试图：|2911592|brew+tap-new+$USER/old-openssl
brew+extract+--version=1.0.2t+openssl+$USER/old-openssl
brew+install+openssl@1.0.2t

#+and+then+either+brew+link+openssl@1.0.2t+or+symlink+the+required+files+to+current+openssl
ln+-s+/usr/local/Cellar/openssl/openssl@1.0.2t/lib/libcrypto.1.0.0.dylib+/usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib
ln+-s+/usr/local/Cellar/openssl/openssl@1.0.2t/lib/libssl.1.0.0.dylib+/usr/local/opt/openssl/lib/libssl.1.0.0.dylib|code-block|syntax|javascript|2911593|entityMap^0|0|0|S|17|13|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|10|8|@]|9|@]|A|$O|P]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

You might be seeing a conflict of libssl/libcrypto versions.
<code>brew services start postgres</code> logs gave me nada, but manually starting <code>pg_ctl -D /usr/local/var/postgres start</code> pointed at:
missing definition _RAND_cleanup in /.../openssl/lib/libcrypto.1.0.0.dylib
Have a shot at:
<pre><code>brew tap-new $USER/old-openssl
brew extract --version=1.0.2t openssl $USER/old-openssl
brew install openssl@1.0.2t

# and then either brew link openssl@1.0.2t or symlink the required files to current openssl
ln -s /usr/local/Cellar/openssl/openssl@1.0.2t/lib/libcrypto.1.0.0.dylib /usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib
ln -s /usr/local/Cellar/openssl/openssl@1.0.2t/lib/libssl.1.0.0.dylib /usr/local/opt/openssl/lib/libssl.1.0.0.dylib
</code></pre>

blocks|key|1719545|text|万一其他所有的答案都不管用..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1719546|我看到了同样的信息和被接受的答案，|1719547|rm+-f+/usr/local/var/postgres/postmaster.pid|offset|length|style|CODE|1719548|没起作用。也没有|1719549|rm+-f+/usr/local/var/postgres@9.6/postmaster.pid在我记得我安装了一个特定的版本之后。|1719550|我做了一个cat+/usr/local/var/log/postgresql@9.6.log，然后看到：|1719551|FATAL:++lock+file+"postmaster.pid"+already+exists
HINT:++Is+another+postmaster+(PID+1231)+running+in+data+directory+"/usr/local/var/postgresql@9.6"?|code-block|syntax|javascript|1719552|>+ps+aux%7Cgrep+1231
[...]+/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/usr/libexec/mobileassetd|1719553|**思考的脸**|1719554|关闭了iOS模拟器。Postgres自己重新启动.|BOLD|1719555|这是在桌面上，我们昨天断电了，所以基于其他答案，我怀疑根本原因是硬性关闭而没有给东西一个清理的机会。|1719556|entityMap^0|0|0|0|18|0|0|0|1C|0|5|15|0|0|0|0|0|P|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|17|8|@$F|18|G|19|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1A|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1B|8|@$F|1C|G|1D|H|I]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1E|8|@$F|1F|G|1G|H|I]]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1H|8|@]|9|@]|A|$S|T]]|$1|U|3|V|5|R|7|1I|8|@]|9|@]|A|$S|T]]|$1|W|3|X|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1K|8|@$F|1L|G|1M|H|10]]|9|@]|A|$]]|$1|11|3|12|5|6|7|1N|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|14|$]]

In case all the other answers don't work...
I was seeing this same message and the accepted answer, running
<code>rm -f /usr/local/var/postgres/postmaster.pid</code>
didn't work. Neither did
<code>rm -f /usr/local/var/postgres@9.6/postmaster.pid</code> after I remembered I had a specific version installed.
I did a <code>cat /usr/local/var/log/postgresql@9.6.log</code> and saw:
<pre><code>FATAL: lock file &quot;postmaster.pid&quot; already exists
HINT: Is another postmaster (PID 1231) running in data directory &quot;/usr/local/var/postgresql@9.6&quot;?
</code></pre>
<pre><code>&gt; ps aux|grep 1231
[...] /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/usr/libexec/mobileassetd
</code></pre>
**thinking face**
Closed the iOS Simulator. Postgres restarted on its own.
This is on a desktop and we had the power go out yesterday, so based on the other answers I suspect the root cause is the hard shutdown without giving things a chance to clean up.

blocks|key|2911660|text|问题-在macOS升级之后，Postgres无法工作|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2911661|我刚刚升级到最新的macOS+(大苏尔)。|2911662|使用postgresql作为数据库的本地实例的节点应用程序由于以下错误而无法启动：Error:+connect+ECONNREFUSED+127.0.0.1:5432|CODE|2911663|显然，postgresql在我的机器上已经不能正常运行了。|2911664|运行brew+services+list显示postgresql的错误|2911665|Name++++++++++Status++User++Plist++++
postgresql++++error+++*****+/Users/*****/Library/LaunchAgents/homebrew.mxcl.postgresql.plist|code-block|syntax|javascript|2911666|解决方案-升级Postgres|2911667|为了解决这个问题，我使用以下命令升级postgresql：|2911668|$+brew+services+stop+postgresql
$+brew+postgresql-upgrade-database+#+may+need+to+`rm-rf+/usr/local/var/postgres.old`+first
$+brew+services+start+postgresql|2911669|entityMap^0|0|B|0|0|15|16|0|0|2|I|0|0|0|F|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|14|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|15|8|@$9|16|A|17|B|J]]|D|@]|E|$]]|$1|K|3|L|5|6|7|18|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|19|8|@$9|1A|A|1B|B|J]]|D|@]|E|$]]|$1|O|3|P|5|Q|7|1C|8|@]|D|@]|E|$R|S]]|$1|T|3|U|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|V|3|W|5|6|7|1G|8|@]|D|@]|E|$]]|$1|X|3|Y|5|Q|7|1H|8|@]|D|@]|E|$R|S]]|$1|Z|3|-4|5|6|7|1I|8|@]|D|@]|E|$]]]|10|$]]

Problem - Postgres not working after macOS upgrade
I just upgraded to the latest macOS (Big Sur).
My node application that uses a local instance of postgresql as a database was unable to start due to this error: <code>Error: connect ECONNREFUSED 127.0.0.1:5432</code>
Clearly postgresql is no longer running properly on my machine.
Running <code>brew services list</code> shows an error for postgresql:
<pre><code>Name Status User Plist 
postgresql error ***** /Users/*****/Library/LaunchAgents/homebrew.mxcl.postgresql.plist
</code></pre>
Solution - Upgrade Postgres
To resolve the problem I upgraded postgresql with the following commands:
<pre><code>$ brew services stop postgresql
$ brew postgresql-upgrade-database # may need to `rm-rf /usr/local/var/postgres.old` first
$ brew services start postgresql
</code></pre>

blocks|key|3320203|text|如果您的postgres.log文件包含“图像未找到错误”，则可能需要重新安装postgresql：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3320204|brew+reinstall+postgresql|code-block|syntax|javascript|3320205|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If your postgres.log file contains &quot;image not found error&quot; then you may need to reinstall postgresql:
<pre><code>brew reinstall postgresql
</code></pre>

blocks|key|1717836|text|我的问题是与数据库的连接是开放的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1717837|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

My problem was an open connection to my database.

blocks|key|1719624|text|在我的例子中，在更新到MacOS蒙特利之后，它需要|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1719625|$+brew+postgresql-upgrade-database|code-block|syntax|javascript|1719626|也是。|1719627|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In my case after updating to MacOS Monterey it was need to make
<pre><code>$ brew postgresql-upgrade-database
</code></pre>
as well.

blocks|key|3320367|text|在我的例子中，问题在于我试图在Mac上的SSH会话中启动brew服务，在那里我的用户目前还没有登录。只要登录到Mac，通过MacOS登录GUI就可以解决这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3320368|更详细的错误消息包括提示问题是gui-related：|3320369|Error:+Failure+while+executing;+`/bin/launchctl+enable+gui/501/homebrew.mxcl.postgresql`+exited+with+64.|code-block|syntax|javascript|3320370|entityMap^0|S|4|0|F|3|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

In my case the problem was that I was attempting to start the <code>brew</code> service in an SSH session on a Mac, where my user was not currently logged in. Simply logging into the Mac, through the MacOS login GUI solved the issue.
A more detailed error message included the hint that the problem was <code>gui</code>-related:
<pre><code>Error: Failure while executing; `/bin/launchctl enable gui/501/homebrew.mxcl.postgresql` exited with 64.
</code></pre>

blocks|key|1719652|text|如果有人在尝试了所有的事情后都跌到了谷底，但它不起作用，这就是对我起作用的原因。我最终决定不使用brew。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1719653|我直接从这个链接https://postgresapp.com的网站安装了Postgres应用程序，初始化了一个新的服务器，并像往常一样创建了数据库和表。|offset|length|1719654|我也得到了端口占用相关的错误，这个答案https://stackoverflow.com/a/43825665对我有用。|1719655|entityMap|0|LINK|mutability|MUTABLE|url|https://postgresapp.com/|1|https://stackoverflow.com/a/43825665^0|0|8|N|0|0|J|10|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

If someone scrolls to the bottom after trying everything out and it's not working, this is what worked for me. I decided not to use brew for this eventually.
I installed Postgres app directly from the website following this link <a href="https://postgresapp.com" rel="nofollow noreferrer">https://postgresapp.com</a>, initialised a new server and created the databases and tables as usual.
I was also getting port occupied related errors and this answer
<a href="https://stackoverflow.com/a/43825665">https://stackoverflow.com/a/43825665</a> worked for me.

blocks|key|3320460|text|在我的例子中(postgres由自制)，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3320461|跟踪日志以查看错误是什么tail+-n+50+/usr/local/var/log/postgres.log
2022-04-28+16:38:10.509+PDT+84751致命:锁文件"postmaster.pid“已经存在2022-04-28+16:38:10.509+PDT+84751提示:另一个邮政管理员(PID+969)是否在数据目录"/usr/local/var/postgres”中运行？|unordered-list-item|offset|length|style|CODE|3320462|基于上面的pid杀死kill+-9+<pid>|3320463|通过自制brew+services+restart+postgresql+&&+brew+services+list重新启动服务|3320464|entityMap^0|0|C|16|0|5|3|A|D|0|4|1I|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@$E|Q|F|R|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|S|8|@$E|T|F|U|G|H]|$E|V|F|W|G|H]]|9|@]|A|$]]|$1|K|3|L|5|D|7|X|8|@$E|Y|F|Z|G|H]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$]]

In my case (postgres installed by homebrew),
<ul>
<li>tailing the log to see what the error was <code>tail -n 50 /usr/local/var/log/postgres.log</code>
2022-04-28 16:38:10.509 PDT [84751] FATAL: lock file &quot;postmaster.pid&quot; already exists
2022-04-28 16:38:10.509 PDT [84751] HINT: Is another postmaster (PID 969) running in data directory &quot;/usr/local/var/postgres&quot;?
</li>
<li>kill the <code>pid</code> based on above <code>kill -9 &lt;pid&gt;</code>
</li>
<li>restart the service via homebrew <code>brew services restart postgresql &amp;&amp; brew services list</code>
</li>
</ul>

blocks|key|1717909|text|当我强制重启我的mac时，我也犯了同样的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1717910|当我这么做的时候|1717911|brew+services+list|code-block|syntax|javascript|1717912|我发现了一个错误：|1717913|postgresql++++++++error++256+~/Library/LaunchAgents/homebrew.mxcl.postgresql.plist|1717914|为解决这一问题所采取的步骤：|1717915|打开终端并键入以下命令。|1717916|cd+/opt/homebrew/var/postgres
rm+postmaster.pid|1717917|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|11|8|@]|9|@]|A|$G|H]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

I had the same error when I forced the restart of my mac.
When I did:
<pre><code>brew services list
</code></pre>
I got this error:
<pre><code>postgresql error 256 ~/Library/LaunchAgents/homebrew.mxcl.postgresql.plist
</code></pre>
Steps followed to resolve this issue:
Open the terminal and type the following command.
<pre><code>cd /opt/homebrew/var/postgres
rm postmaster.pid
</code></pre>

I've been looking for a solution for this and could not find a working solution.

I've installed postgres using brew (<code>brew install postgres</code>) in my MacBook and I am currently running it using brew services (<code>brew services list</code> displays postgres as a running service). However, when I try to run <code>psql</code> I get following error.

<blockquote>
 psql: could not connect to server: No such file or directory Is the
 server running locally and accepting connections on Unix domain
 socket "/tmp/.s.PGSQL.5432"?
</blockquote>

Anyone has already solved similar problem?

Cannot connect to Postgres server running through brew services

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我一直在寻找解决这个问题的方法，却找不到一个可行的解决方案。我已经在我的MacBook中使用brew (brew install postgres)安装了postgres，并且我目前正在使用brew服务运行它(brew services list显示postgres是一个正在运行的服务)。但是，当我试图运行psql时，...

问无法连接到通过brew服务运行的Postgres服务器
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法连接到通过brew服务运行的Postgres服务器EN