1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

-bash: /usr/local/sbin/install-a2billing: /bin/sh^M: bad interpreter: No such file or

Discussion in 'Add-On Install Instructions' started by Netizen, Mar 12, 2009.

  1. Netizen

    Netizen
    Expand Collapse
    New Member

    Joined:
    Mar 10, 2009
    Messages:
    10
    Likes Received:
    0
    Hi people,

    Any ideas I am getting the following message when I'm trying to install a2billing?

    -bash: /usr/local/sbin/install-a2billing: /bin/sh^M: bad interpreter: No such file or directory

    I have already updated scripts.

    Any ideas?
    Thank you
    Netizen
     
  2. jroper

    jroper
    Expand Collapse
    Guru

    Joined:
    Oct 20, 2007
    Messages:
    3,818
    Likes Received:
    56
    Have you searched for anyone else with the same problem?

    Joe
     
  3. madoleh

    madoleh
    Expand Collapse
    New Member

    Joined:
    Mar 3, 2009
    Messages:
    2
    Likes Received:
    0
    That was good, Joe!!!
     
  4. Netizen

    Netizen
    Expand Collapse
    New Member

    Joined:
    Mar 10, 2009
    Messages:
    10
    Likes Received:
    0

    Yes I did
    Not everybody uses Google as first preference you see.
    N
     
  5. megazot

    megazot
    Expand Collapse
    New Member

    Joined:
    Mar 16, 2009
    Messages:
    4
    Likes Received:
    0
    i have solved this problem in this way:
    cd /usr/local/sbin
    dos2unix install-a2billing
    install-a2billing.


    the script was opened with winzozz editor!!!! :(
     
  6. synchronous

    synchronous
    Expand Collapse
    New Member

    Joined:
    Sep 29, 2009
    Messages:
    9
    Likes Received:
    0
    nice fix

    I had the same issue and this worked for me beautifully. Great work.
     
  7. blanchae

    blanchae
    Expand Collapse
    Guru

    Joined:
    Mar 12, 2008
    Messages:
    1,922
    Likes Received:
    4
    The ^M is the clue. This indicates that somehow the script or text file was created using an MSDOS editor and not a Unix editor. MSDOS terminates end of lines with the ASCII characters CR (carriage return) and LF (Line Feed) while Unix only uses LF. When a MSDOS created script runs, Unix chokes on the extra character and reports it as the keyboard shortcut ^M. You can use the "^" series of keyboard shortcuts to "type" in ASCII control characters. You can read the details on my online book Introduction to Data Communications
     
  8. kenn10

    kenn10
    Expand Collapse
    Guru-ish

    Joined:
    Dec 16, 2007
    Messages:
    710
    Likes Received:
    72
    Well, as much as I worry about Google becoming self aware and turning into SkyNet, it still is the best search engine for more technical searches.
     
  9. callingcard

    callingcard
    Expand Collapse
    New Member

    Joined:
    Feb 21, 2008
    Messages:
    2
    Likes Received:
    0
    Wonderful Solution which worked from the very first time.

    Thank you!


     

Share This Page