After doing a git pull and starting the server this error keeps poping up

gistfile1.txt

=> Booting Puma
=> Rails 5.0.1 application starting in development on http://localhost:3000
=> Run `rails server -h` for more startup options
Puma starting in single mode...
* Version 3.4.0 (ruby 2.3.3-p222), codename: Owl Bowl Brawl
* Min threads: 5, max threads: 5
* Environment: development
* Listening on tcp://localhost:3000
Exiting
/home/anonymous/.rvm/gems/ruby-2.3.3/gems/puma-3.4.0/lib/puma/binder.rb:255:in `initialize': Address already in use - bind(2) for "localhost" port 3000 (Errno::EADDRINUSE)
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/puma-3.4.0/lib/puma/binder.rb:255:in `new'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/puma-3.4.0/lib/puma/binder.rb:255:in `add_tcp_listener'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/puma-3.4.0/lib/puma/binder.rb:102:in `block in parse'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/puma-3.4.0/lib/puma/binder.rb:85:in `each'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/puma-3.4.0/lib/puma/binder.rb:85:in `parse'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/puma-3.4.0/lib/puma/runner.rb:129:in `load_and_bind'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/puma-3.4.0/lib/puma/single.rb:84:in `run'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/puma-3.4.0/lib/puma/launcher.rb:172:in `run'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/puma-3.4.0/lib/rack/handler/puma.rb:51:in `run'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/rack-2.0.1/lib/rack/server.rb:296:in `start'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/railties-5.0.1/lib/rails/commands/server.rb:79:in `start'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/railties-5.0.1/lib/rails/commands/commands_tasks.rb:90:in `block in server'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/railties-5.0.1/lib/rails/commands/commands_tasks.rb:85:in `tap'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/railties-5.0.1/lib/rails/commands/commands_tasks.rb:85:in `server'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/railties-5.0.1/lib/rails/commands/commands_tasks.rb:49:in `run_command!'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/railties-5.0.1/lib/rails/commands.rb:18:in `<top (required)>'
	from /home/anonymous/anti_plag/bin/rails:9:in `require'
	from /home/anonymous/anti_plag/bin/rails:9:in `<top (required)>'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/spring-1.7.2/lib/spring/client/rails.rb:28:in `load'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/spring-1.7.2/lib/spring/client/rails.rb:28:in `call'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/spring-1.7.2/lib/spring/client/command.rb:7:in `call'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/spring-1.7.2/lib/spring/client.rb:30:in `run'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/spring-1.7.2/bin/spring:49:in `<top (required)>'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/spring-1.7.2/lib/spring/binstub.rb:11:in `load'
	from /home/anonymous/.rvm/gems/ruby-2.3.3/gems/spring-1.7.2/lib/spring/binstub.rb:11:in `<top (required)>'
	from /home/anonymous/anti_plag/bin/spring:15:in `require'
	from /home/anonymous/anti_plag/bin/spring:15:in `<top (required)>'
	from bin/rails:3:in `load'
	from bin/rails:3:in `<main>'

kill -9 $(lsof -i tcp:3000 -t)

Or just

rm tmp/pids/server.pid