Killing MailCatcher: Something's using port 1025

ruby-on-rails foreman mailcatcher
CJ -S picture CJ -S · Jul 18, 2014 · Viewed 21.9k times · Source

I'm trying to run "foreman start" for a rails app however this error message is preventing me from running the foreman properly:

~~> ERROR: Something's using port 1025. Are you already running MailCatcher?

I've tried killing the PID, going to the web interface to quit the program and also...restarting the comp. Does anybody know how to remedy this?

Thanks

Answer

Joseph Combs picture Joseph Combs · Jan 13, 2015

In OSX, run the following in a shell:

sudo lsof -nP -iTCP:1025 -sTCP:LISTEN

The expected output of this command is a process, which is listening on port 1025:

ruby    43841 youruserid    9u  IPv4 0x6a1610da80bb9b4f      0t0  TCP 127.0.0.1:1025 (LISTEN)

In the output above, the 2nd value is the process ID. Then, to kill the offending process (substitute in the correct PID):

sudo kill 43841

Related questions

foreman only shows line with “started with pid #” and nothing else

When I run foreman I get the following: > foreman start 16:47:56 web.1 | started with pid 27122 Only if I stop it (via ctrl-c) it shows me what is missing: ^CSIGINT received 16:49:26 system | sending SIGTERM to all processes 16:49:26 web.1 | => Booting Thin 16:49:26 …

Read More
How to simply stop or restart foreman processes

We have rails app that is running some foreman processes with bundle exec foreman start, and have googled a lot of different things, and found that the common suggestion is to set up another background process handler, and export the …

Read More
Getting error: Peer authentication failed for user "postgres", when trying to get pgsql working with rails

I'm getting the error: FATAL: Peer authentication failed for user "postgres" when I try to make postgres work with Rails. Here's my pg_hba.conf, my database.yml, and a dump of the full trace. I changed authentication to md5 …

Read More