gistfile1.txt

 >>  MySQLTuner 1.2.0 - Major Hayden <major@mhtx.net>
 >>  Bug reports, feature requests, and downloads at http://mysqltuner.com/
 >>  Run with '--help' for additional options and output filtering

-------- General Statistics --------------------------------------------------
[--] Skipped version check for MySQLTuner script
[!!] Your MySQL version 10.0.4-MariaDB-1~precise-log is EOL software!  Upgrade soon!
[OK] Operating on 64-bit architecture

-------- Storage Engine Statistics -------------------------------------------
[--] Status: +Archive -BDB +Federated +InnoDB -ISAM -NDBCluster 
[--] Data in MyISAM tables: 2K (Tables: 33)
[--] Data in CSV tables: 0B (Tables: 2)
[--] Data in InnoDB tables: 9K (Tables: 16)
[--] Data in PERFORMANCE_SCHEMA tables: 0B (Tables: 52)
[!!] Total fragmented tables: 34

-------- Security Recommendations  -------------------------------------------
[OK] All database users have passwords assigned
Use of uninitialized value in addition (+) at mysqltuner.pl line 582 (#1)
    (W uninitialized) An undefined value was used as if it were already
    defined.  It was interpreted as a "" or a 0, but maybe it was a mistake.
    To suppress this warning assign a defined value to your variables.
    
    To help you figure out what was undefined, perl will try to tell you the
    name of the variable (if any) that was undefined. In some cases it cannot
    do this, so it also tells you what operation you used the undefined value
    in.  Note, however, that perl optimizes your program and the operation
    displayed in the warning may not necessarily appear literally in your
    program.  For example, "that $foo" is usually optimized into "that "
    . $foo, and the warning will refer to the concatenation (.) operator,
    even though there is no . in your program.
    
Argument "xargs:" isn't numeric in addition (+) at mysqltuner.pl line 618 (#2)
    (W numeric) The indicated string was fed as an argument to an operator
    that expected a numeric value instead.  If you're fortunate the message
    will identify which operator was so unfortunate.
    
Argument "du:" isn't numeric in addition (+) at mysqltuner.pl line 618 (#2)

-------- Performance Metrics -------------------------------------------------
[--] Up for: 2h 21m 22s (18K q [2.122 qps], 365 conn, TX: 4M, RX: 1M)
[--] Reads / Writes: 55% / 45%
[--] Total buffers: 496.0M global + 416.0K per thread (350 max threads)
[OK] Maximum possible memory usage: 638.2M (1% of installed RAM)
[OK] Slow queries: 0% (0/18K)
[OK] Highest usage of available connections: 43% (153/350)
[!!] Cannot calculate MyISAM index size - re-run script as root user
[OK] Temporary tables created on disk: 1% (10 on disk / 715 total)
[OK] Thread cache hit rate: 58% (153 created / 365 connections)
[OK] Table cache hit rate: 68% (90 open / 131 opened)
[OK] Open file limit used: 4% (73/1K)
[OK] Table locks acquired immediately: 96% (11K immediate / 11K locks)
[OK] InnoDB data size / buffer pool: 9.4K/256.0M

-------- Recommendations -----------------------------------------------------
General recommendations:
    Run OPTIMIZE TABLE to defragment tables for better performance
    MySQL started within last 24 hours - recommendations may be inaccurate
    Upgrade MySQL to version 4+ to utilize query caching
    Upgrade to MySQL 4.1+ to use concurrent MyISAM inserts