Problem with ISPConfig (only 2 sites configured)

Discussion in 'General' started by ggarcia24, Nov 17, 2008.

  1. ggarcia24

    ggarcia24 New Member

    Hi everyone :) how are you, first I'll like to Thank everyone for this amazing place, second I wan to ask if some one have some information on an issue that i'm having with ISPConfig.

    I have a VPS on Virtual Host ( 256Mb RAM, 15Gb space, 2 CPU, Debian Etch.

    I've tryed to adapt the default instalation that Virtual Host (VH) make on the server to the Debian Etch prefect install, then I've installed without any issue ISPConfig, and added my domain as a site that I've bought with Godaddy (, I've installed Chrooted BIND, and followed the tutorial to make my own domain server.

    So far everything was going smooth :D, up untill I've tryed to add an other domain to ISPConfig ( I've added the domain in ISPConfig and BIND resolved the domain without a problem, but I'm having some rare issue, in the first week the both websites ( and worked fantastic, but in the last few weeks just works perfect,,ar gets resolved but it doesn't load the page...

    Can some body please help me, I've tryed to see if the problem was BIND but it returns me an IP, I've try to see if the problem was the server, but it doesn't show any CPU / Memory usage problems (load in the server is very low), and a friend told me to make a telnet 80, to see if the web server was listening and it show some reply after I write can some body gide me???? I want to lear, so links to read are ok, I read / write in english and spanish (my default language is spanish).

    Thanks in advance.
  2. ggarcia24

    ggarcia24 New Member

    I've found the problem ^_^!!! MySQL is the problem... :(... al thought I've tryed to do a little optimizations to mysql seems to me that i've screwed up big time!!!... does anyone here could offerme a manual to optimize MySQL Server????

    Just in case anyone ask here's my.cnf:

    # The MySQL database server configuration file.
    # You can copy this to one of:
    # - "/etc/mysql/my.cnf" to set global options,
    # - "~/.my.cnf" to set user-specific options.
    # One can use all long options that the program supports.
    # Run program with --help to get a list of available options and with
    # --print-defaults to see which it would actually understand and use.
    # For explanations see
    # This will be passed to all mysql clients
    # It has been reported that passwords should be enclosed with ticks/quotes
    # escpecially if they contain "#" chars...
    # Remember to edit /etc/mysql/debian.cnf when changing the socket location.
    port            = 3306
    socket          = /var/run/mysqld/mysqld.sock
    # Here is entries for some specific programs
    # The following values assume you have at least 32M ram
    # This was formally known as [safe_mysqld]. Both versions are currently parsed.
    socket          = /var/run/mysqld/mysqld.sock
    nice            = 0
    # * Basic Settings
    user            = mysql
    pid-file        = /var/run/mysqld/
    socket          = /var/run/mysqld/mysqld.sock
    port            = 3306
    basedir         = /usr
    datadir         = /var/lib/mysql
    tmpdir          = /tmp
    language        = /usr/share/mysql/english
    # localhost which is more compatible and is not less secure.
    bind-address            =
    # * Fine Tuning
    key_buffer              = 512K
    max_allowed_packet      = 16M
    thread_stack            = 128K
    thread_cache_size       = 8
    table_cache = 1024
    max_connections = 100
    max_user_connections = 30
    max_connect_errors = 100
    wait_timeout = 10
    interactive_timeout = 10
    # * Query Cache Configuration
    query_cache_type = 1
    query_cache_limit       = 1M
    query_cache_size        = 4M
    # * Logging and Replication
    # Both location gets rotated by the cronjob.
    # Be aware that this log type is a performance killer.
    log             = /var/log/mysql/mysql.log
    # Error logging goes to syslog. This is a Debian improvement :)
    # Here you can see queries with especially long duration
    log_slow_queries        = /var/log/mysql/mysql-slow.log
    long_query_time = 5
    # The following can be used as easy to replay backup logs or for replication.
    #server-id              = 1
    log_bin                 = /var/log/mysql/mysql-bin.log
    # WARNING: Using expire_logs_days without bin_log crashes the server! See README.Debian!
    expire_logs_days        = 10
    max_binlog_size         = 100M
    #binlog_do_db           = include_database_name
    #binlog_ignore_db       = include_database_name
    # * BerkeleyDB
    # Using BerkeleyDB is now discouraged as its support will cease in 5.1.12.
    # * InnoDB
    # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
    # Read the manual for more InnoDB related options. There are many!
    # You might want to disable InnoDB to shrink the mysqld process by circa 100MB.
    # * Security Features
    # Read the manual, too, if you want chroot!
    # chroot = /var/lib/mysql/
    # For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
    # ssl-ca=/etc/mysql/cacert.pem
    # ssl-cert=/etc/mysql/server-cert.pem
    # ssl-key=/etc/mysql/server-key.pem
    max_allowed_packet      = 16M
    #no-auto-rehash # faster start of mysql but no tab completition
    key_buffer              = 16M
    # * NDB Cluster
    # See /usr/share/doc/mysql-server-*/README.Debian for more information.
    # The following configuration is read by the NDB Data Nodes (ndbd processes)
    # not from the NDB Management Nodes (ndb_mgmd processes).
    # ndb-connectstring=
    # * IMPORTANT: Additional settings that can override those from this file!
    !includedir /etc/mysql/conf.d/
  3. falko

    falko Super Moderator Howtoforge Staff

  4. ggarcia24

    ggarcia24 New Member

    Well thank you falko for the quick answer!!

    I've run both script mentioned on this site (mysqltuner and tuning-primer) and both script "guideme" into the current confiuration, althoug I think that the problem is that I didn't wait the 48hs expected by both scripts... I think I'll wait to tomorrow to run the scripts... do you think that this is a problem?
  5. falko

    falko Super Moderator Howtoforge Staff

  6. ggarcia24

    ggarcia24 New Member

    Sorry, for the delay but I decided to quit on the Debian Etch installation and go for the Ubuntu, since Ubuntu haves the php 5.2.6, and is debian based...

    So i've reinstalled the O.S. and well oviously MySQL start working (aparently perfect)...

    Thanks falko for all the help and advises

Share This Page