Named will not start with error "couldn't open pid file './named.pid': File exists"

Solution Verified - Updated -

Issue

  • After applying latest round of patches we noticed the named service would not start up.
Jul 22 12:57:20 server1 named[6475]: loading configuration from '/etc/named.conf'
Jul 22 12:57:20 server1 named[6475]: using default UDP/IPv4 port range: [1024, 65535]
Jul 22 12:57:20 server1 named[6475]: using default UDP/IPv6 port range: [1024, 65535]
Jul 22 12:57:20 server1 named[6475]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 22 12:57:20 server1 named[6475]: binding TCP socket: address in use
Jul 22 12:57:20 server1 named[6475]: listening on IPv4 interface eth0, 10.59.90.76#53
Jul 22 12:57:20 server1 named[6475]: binding TCP socket: address in use
Jul 22 12:57:20 server1 named[6475]: listening on IPv4 interface eth1, 172.16.1.183#53
Jul 22 12:57:20 server1 named[6475]: binding TCP socket: address in use
Jul 22 12:57:20 server1 named[6475]: command channel listening on 127.0.0.1#953
Jul 22 12:57:20 server1 named[6475]: command channel listening on ::1#953
Jul 22 12:57:20 server1 named[6475]: couldn't open pid file './named.pid': File exists
Jul 22 12:57:20 server1 named[6475]: exiting (due to early fatal error)
  • Trying to booting off of an old kernel did not help

Environment

  • Red Hat Enterprise Linux 5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In