sixhop / AutoMySQLBackup

A fork and further development of AutoMySQLBackup from sourceforge. http://sourceforge.net/projects/automysqlbackup/
GNU General Public License v2.0
341 stars 103 forks source link

line 873: 6: Bad file descriptor #28

Closed modir closed 5 years ago

modir commented 6 years ago

I just downloaded the newest version and I got these error messages:

/usr/local/bin/automysqlbackup: line 873: 6: Bad file descriptor
/usr/local/bin/automysqlbackup: line 874: 7: Bad file descriptor
BigAndini commented 6 years ago

Can you please tell me which OS you're using for automysqlbackup?

modir commented 6 years ago

CentOS 7

BigAndini commented 6 years ago

Are you executing automysqlbackup as root and can you please check if SELinux is active? Maybe this will prohibit the file descriptor handling. Is this the only error or are there errors before? Could you please execute automysqlbackup using bash -x and send the log?

BigAndini commented 5 years ago

Nothing heard for a longer time. I will close this issue. Feel free to reopen it if the issue still exists for you.

shanerbaner82 commented 3 years ago

I am installing this inside of Docker (Ubuntu 18.04) like so:

RUN sudo mkdir /usr/local/src/automysqlbackup &&\
    cd /usr/local/src/automysqlbackup &&\
    sudo wget https://github.com/sixhop/AutoMySQLBackup/archive/3.0.7.tar.gz &&\
    sudo tar xvzf 3.0.7.tar.gz &&\
    cd AutoMySQLBackup-3.0.7 &&\
    sudo chmod a+x install.sh &&\
    sudo sh install.sh

When I ssh into the box and run automysqlbackup as root I get this same issue:

root@6d533a04eff1:~# automysqlbackup 
does not exist. Exiting.
Note: Supplied more than one argument, ignoring ALL arguments - using default and global config file only.
Error: No basedir found, i.e.
/usr/local/bin/automysqlbackup: line 873: 6: Bad file descriptor
/usr/local/bin/automysqlbackup: line 874: 7: Bad file descriptor
Skipping normal output methods, since the program exited before any log files could be created.

I feel like I am missing some big step.... any help here is appreciated.

andyrue commented 3 years ago

I got this error when my CONFIG_backup_dir was pointing to a folder that didn't exist.