Custom init script is failing to start with "/bin/bash^M: bad interpreter: no such file or directory" error

Solution Verified - Updated -

Issue

  • Custom init script is failing to start with "/bin/bash^M: bad interpreter: no such file or directory" error
  • If we remove #!/bin/bash from the script, getting below error:
No such file or directory line : /etc/init.d/functions. 

Environment

  • Red Hat Enterprise Linux 6
  • bash
  • initscripts

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