AutoMySQLBackup 3.0 Bug:"du: WARNING: use --si, not -H"_MySQL
案例环境:
操作系统版本: Red Hat Enterprise Linux Server release 5.7 64bit
数据库版本 : 5.6.19 MySQL Community Server
AutoMySQLBackup: Automysqlbackup-v3.0_rc6
案例场景:
AutoMySQLBackup 3.0版本备份时,出现告警错误“du: WARNING: use --si, not -H; the meaning of the -H option will soon change to be the same as that of --dereference-args (-D)” 具体信息请见下面:
==============================================================================
Total disk space used for backup storage...
Size - Location
1.8M /u01/db_backup/mysqlbackup/
==============================================================================
###### WARNING ######
Errors reported during AutoMySQLBackup execution.. Backup failed
Error log below..
du: WARNING: use --si, not -H; the meaning of the -H option will soon
change to be the same as that of --dereference-args (-D)
================================== End of Backup =============================
==============================================================================
出现这个错误是因为在 Red Hat Enterprise Linux 5.7上的du命令不符合POSIX标准规范。具体参考官方的AutoMySQLBackup 3.0 warning on du in Centos (5.7)
The POSIX specifications are. It seems, that the Centos 5.7 version of du is not POSIX compliant, but will soon be. I have done my best to use only POSIX compliant syntax to assure the bug-free running on most systems. Unfortunately, I can't take care of every system and distribution, which chooses to defy POSIX syntax. For other people and myself, it would be a good idea to get the options of du on Centos 5.7, so please post 'du --help'.
如下所示,在命令du --help中,你就能从帮助信息中看到下面信息:
可以通过修改脚本/usr/local/bin/automysqlbackup 找到下面脚本,修改脚本将“ echo `du -hsH "${CONFIG_backup_dir}"` 修改为 echo `du -hs "${CONFIG_backup_dir}"` 即可解决问题。
在Red Hat Enterprise Linux Server release 6.6 就不会有这个问题,它的du版本为8.4, Red Hat Enterprise Linux 5.7上的du命令版本为du (GNU coreutils) 5.97
# du --version
du (GNU coreutils) 8.4
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Torbjörn Granlund, David MacKenzie, Paul Eggert,
and Jim Meyering.

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The article discusses using MySQL's ALTER TABLE statement to modify tables, including adding/dropping columns, renaming tables/columns, and changing column data types.

Article discusses configuring SSL/TLS encryption for MySQL, including certificate generation and verification. Main issue is using self-signed certificates' security implications.[Character count: 159]

Article discusses strategies for handling large datasets in MySQL, including partitioning, sharding, indexing, and query optimization.

Article discusses popular MySQL GUI tools like MySQL Workbench and phpMyAdmin, comparing their features and suitability for beginners and advanced users.[159 characters]

The article discusses dropping tables in MySQL using the DROP TABLE statement, emphasizing precautions and risks. It highlights that the action is irreversible without backups, detailing recovery methods and potential production environment hazards.

Article discusses using foreign keys to represent relationships in databases, focusing on best practices, data integrity, and common pitfalls to avoid.

The article discusses creating indexes on JSON columns in various databases like PostgreSQL, MySQL, and MongoDB to enhance query performance. It explains the syntax and benefits of indexing specific JSON paths, and lists supported database systems.

Article discusses securing MySQL against SQL injection and brute-force attacks using prepared statements, input validation, and strong password policies.(159 characters)
