The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Keep getting this cron error: /bin/sh: /usr/local/bandmin/bandmin: is a directory

Discussion in 'General Discussion' started by DWHS.net, Feb 9, 2010.

  1. DWHS.net

    DWHS.net Well-Known Member
    PartnerNOC

    Joined:
    Jul 28, 2002
    Messages:
    1,569
    Likes Received:
    6
    Trophy Points:
    38
    Location:
    LA, Costa RIca
    cPanel Access Level:
    Root Administrator
    /bin/sh: /usr/local/bandmin/bandmin: is a directory

    Maybe 50 times a day, any idea how to get something where it's looking or how to fix the error?
     
  2. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    The specified path should be an executable script and not a directory.

    It will help to know, is the system a new installation, or an existing install that just started to experience the issue?

    Does the symptom reoccur frequently (after applying corrections)?

    What is the output of the following two commands?
    Code:
    # stat /usr/local/bandmin/bandmin
    # ls -ahl /usr/local/bandmin
    If the bandmin directory simply contains another bandmin directory instead of an executable script of the same name, try moving it out of the way and then forcing a bandmin update or re-install using the following command:
    Code:
    # /scripts/bandminup --force
     
  3. DWHS.net

    DWHS.net Well-Known Member
    PartnerNOC

    Joined:
    Jul 28, 2002
    Messages:
    1,569
    Likes Received:
    6
    Trophy Points:
    38
    Location:
    LA, Costa RIca
    cPanel Access Level:
    Root Administrator
    I ran this /scripts/bandminup --force

    and it installed bandmin where the cron was trying to run.

    All is fixed, thanks!
     
Loading...

Share This Page