rogue postgres process running after boot

Question

I have had problems with postgres after I replaced my original postgres installation with a homebrew installation.

After boot, if I issue the psql command, I get:

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"?

If I run:

ps auxwww | grep postgres

I get this weird output:

paulcowan 2829 0.0 0.0 2432784 540 s000 R+ 9:17am 0:00.00 grep postgres

And if I run:

ps -ef | grep postgres

I get:

501 2842 1040 0 9:19am ttys000 0:00.00 grep postgres

If I then run:

pg_ctl -D /usr/local/var/postgres -l /usr/local/var/postgres/server.log start

Everything starts.

I have tried to get postgres to start on login and I enter this command:

 ln -sfv /usr/local/opt/postgresql/*.plist ~/Library/LaunchAgents

Followed by this:

launchctl load ~/Library/LaunchAgents/homebrew.mxcl.postgresql.plist

I get this error:

launchctl: Couldn't stat("/Users/paulcowan/Library/LaunchAgents/homebrew.mxcl.postgresql.plist"): No such file or directory nothing found to load

Which operating system are you using?

user330315
– user330315

2014-05-26 19:37:07 +00:00
Commented May 26, 2014 at 19:37 — user330315
– user330315, Commented May 26, 2014 at 19:37
@a_horse_with_no_name Mac OS X - only thing with launchd

Craig Ringer
– Craig Ringer

2014-05-27 05:45:55 +00:00
Commented May 27, 2014 at 5:45 — Craig Ringer
– Craig Ringer, Commented May 27, 2014 at 5:45

jjanes · Accepted Answer · 2014-05-26 19:37:14Z

3

You are piping the output of ps through grep, and grep is finding itself, because grep's visible command line contains the string being searched for. Not weird at all.

There is no rogue PostgreSQL process.

answered May 26, 2014 at 19:37

jjanes

44.9k5 gold badges39 silver badges48 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

ChristopheD Over a year ago

+1, this is what is happening here according to me too.

double_word_disruptor · Accepted Answer · 2014-05-26 17:05:08Z

0

Seams that this is not a postgresql problem. It is linux related especially to your platform.

However, take a look at the default postgresql installation. Depending on linux flavour there are different start scripts in /etc/init.d or /lib/systemd

answered May 26, 2014 at 17:05

double_word_disruptor

1894 bronze badges

Collectives™ on Stack Overflow

rogue postgres process running after boot

2 Answers 2

1 Comment

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Related