Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Server Replication
#1
Hello,

I have a Pandora FMS v4.1 Server - Build PC130925 in a datacenter.

I use a virtual machine as server and another as console.

For various reasons, I will change datacenter. But I can not even dream about losing my database.

A migration of images will not be possible because the current uses Citrix Xen and the new datacenter uses VMWare ESXI.

In the manual there is a chapter on disaster recovery (39.4), but recovery described in the manual occurs in the same environment (same ips) do not explore the possibilities if there is a need to change the ips input/environment.

Maybe my need is unusual.  Sad

I'm not comfortable in performing this change using only the information contained in the manual, there is some more specific document to that need?
In addition to providing an identical hardware in the new datacenter, and follow the steps described in chapter 39.4. What else should I change/pay attention?

Thank you
 Reply
#2
Something similar ocurred to me as well.
I solved such situation :
  1. install the same version of Pandora on the new server
  2. create a Dump of the "old Pandora database" [mysqldump --opt -u root -p > pandora.dump
]
  3. restore the dump on the new server
  4. edit the new server "Pandora_server.conf" and check the password for the pandora user.
  4. recreate the server agents (scripts).

once everything is working, do an upgrade.

The positive aspect of your problem is that you are free to try before shutting down the old server...
 Reply
#3
Hi rischfre,

Thanks you for your answer,

I will do it and post here the results.

About the "dump", its not better execute the pandora backup script ?

Regards
 Reply
#4
Hi,

I´m out of bullets ... i already try every tip from optimize doc ( http://wiki.pandorafms.com/index.php?tit...oncurrency )

My pandora is consuming all xml from data_in but its still with more than 8k unknow_agents.

I´m want to make it full work at v4.1.1 and when its ok i want to migrate to v5.x.

mysql conf is like this right now:

Quote:/var/spool/pandora/data_in# cat /etc/mysql/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
# http://dev.mysql.com/doc/mysql/en/server...ables.html

# 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.
[client]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock
[mysqld_safe]
socket          = /var/run/mysqld/mysqld.sock
nice            = 0
log-error      = /var/log/mysqld.log
[mysqld]
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir        = /usr
datadir        = /var/lib/mysql
tmpdir          = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
key_buffer              = 512M
max_allowed_packet      = 512M
thread_stack            = 256K
thread_cache_size      = 8
myisam-recover        = BACKUP
max_connections        = 1024
max_heap_table_size    = 1024M
read_buffer_size        = 64M
read_rnd_buffer_size    = 128M
#record_buffer          = 8M
table_cache            = 256
sort_buffer_size        = 8M
max_delayed_threads    = 50
#thread_concurrency    = 10
query_cache_min_res_unit = 1K
query_cache_limit      = 2M
query_cache_size        = 128M
join_buffer_size        = 16M
#server-id              = 1
#log_bin                        = /var/log/mysql/mysql-bin.log

expire_logs_days        = 10
max_binlog_size        = 100M
#binlog_do_db          = include_database_name
#binlog_ignore_db      = include_database_name
# * InnoDB

innodb_flush_log_at_trx_commit      = 0
innodb_buffer_pool_size              = 2G
innodb_additional_mem_pool_size      = 4M
innodb_flush_method                  = O_DIRECT
innodb_open_files                    = 700
innodb_thread_sleep_delay            = 1000
innodb_concurrency_tickets            = 250
innodb_lock_wait_timeout        = 180
innodb_thread_concurrency      = 20

[mysqldump]
quick
quote-names
max_allowed_packet      =      512M

[isamchk]
key_buffer              = 512M

max_connections = 500

back_log        = 100
log_warnings

!includedir /etc/mysql/conf.d/


My server have 2xvcpu 2,4Ghz 8GB ram and a storage with 7200k rpm disks.

Any tip ?

My "feeling" is pointing to database settings but i do not have any new ideas..

Regards
 Reply
#5
Ohh another note... when i run the pandora_db.pl i got this erro when its almost finish:

Quote:/var/spool/pandora/data_in# /usr/share/pandora_server/util/pandora_db.pl /etc/pandora/pandora_server.conf

Pandora FMS DB Tool 4.0.2 PS120626 Copyright © 2004-2009 Artica ST
This program is Free Software, licensed under the terms of GPL License v2
You can download latest versions and documentation at http://www.pandorafms.org

Pandora DB now initialized and running (PURGE=60 days, COMPACT=15 days, STEP=1) ...

[*] Pandora FMS Enterprise module not available.

Starting at 2014-08-23 00:11:50
[PURGE] Deleting old data...
[PURGE] Data deletion Progress %100 ..
[PURGE] No data in tagente_datos_log4x
[PURGE] Deleting old string data...
[PURGE] String deletion Progress %100 ..
[PURGE] Deleting old event data (More than 15 days)...
[PURGE] Deleting old audit data (More than 15 days)...
[PURGE] Delete pending deleted modules (data table)...
[PURGE] Delete pending deleted modules (status, module table)...
[PURGE] Deleting old access data (More than 24hr)
[PURGE] Agent access deletion progress %100 ..
[PURGE] Delete contents in report that have some deleted modules...
[PURGE] Delete contents in report that have some deleted agents...
[PURGE] Delete empty contents in report (like SLA or Exception)...
[CHECKDB] Deleting non-init data...
[CHECKDB] Deleting unknown data (More than 0 days)...
[CHECKDB] Checking database consistency (Missing status)...
[CHECKDB] Checking database consistency (Missing module)...
[CHECKDB] Deleting non-existing module 63756 in state table
[CHECKDB] Deleting non-existing module 63757 in state table
[CHECKDB] Deleting non-existing module 63758 in state table
[CHECKDB] Deleting non-existing module 63759 in state table
[CHECKDB] Deleting non-existing module 63760 in state table
[CHECKDB] Deleting non-existing module 63761 in state table
[CHECKDB] Deleting non-existing module 63762 in state table
[CHECKDB] Deleting non-existing module 63763 in state table
[CHECKDB] Deleting non-existing module 63764 in state table
[CHECKDB] Deleting non-existing module 63765 in state table
[CHECKDB] Deleting non-existing module 63766 in state table
[CHECKDB] Deleting non-existing module 63767 in state table
[CHECKDB] Deleting non-existing module 63768 in state table
[CHECKDB] Deleting non-existing module 63769 in state table
[CHECKDB] Deleting non-existing module 63770 in state table
[CHECKDB] Deleting non-existing module 63771 in state table
[CHECKDB] Deleting non-existing module 63772 in state table
[CHECKDB] Deleting non-existing module 63773 in state table
[CHECKDB] Deleting non-existing module 63774 in state table
[CHECKDB] Deleting non-existing module 63775 in state table
[CHECKDB] Deleting non-existing module 63776 in state table
[CHECKDB] Deleting non-existing module 63777 in state table
[CHECKDB] Deleting non-existing module 63778 in state table
[CHECKDB] Deleting non-existing module 63779 in state table
[CHECKDB] Deleting non-existing module 63780 in state table
[CHECKDB] Deleting non-existing module 63781 in state table
[CHECKDB] Deleting non-existing module 63782 in state table
[CHECKDB] Deleting non-existing module 63783 in state table
[CHECKDB] Deleting non-existing module 63784 in state table
[CHECKDB] Deleting non-existing module 63785 in state table
[INTEGRITY] Cleaning up group stats
[INTEGRITY] Deleting non-used IP addresses
DBD::mysql::db do failed: Lock wait timeout exceeded; try restarting transaction at /usr/lib/perl5/PandoraFMS/DB.pm line 579.
DBD::mysql::db do failed: Lock wait timeout exceeded; try restarting transaction at /usr/lib/perl5/PandoraFMS/DB.pm line 579.

Regards
 Reply
#6
Hi guys,

Let me share with you my experience.

First of all i need to change my server from DC_old to DC_new.

So i prepare the new machine with the same version of pandora and execute a dump at DC_old then i execute a source at DC_new.

I got many dificults, because my new storage was using a firmware out of date and i don´t have checked it out.

So when it was fixed my new (old) pandora v4.1.1 was ready.

But i decide to update it to v5.x

So i run the scripts to update from 4.1_ to_5.0, migrate_plugins, 5.0_to_5.1, alter tables that have the pandora server name, optimize tables, set at my.cnf special tokens with innodb.

Now i got no errors at logs, i have some queue at my data_in but its working!

My pandora_server.conf:
Quote:#############################################################################
# Pandora FMS Server Parameters
# Pandora FMS, the Flexible Monitoring System.
# Version 5.1
# Licensed under GPL license v2,
# © 2003-2014 Artica Soluciones Tecnologicas
# http://www.pandorafms.com
# Please change it for your setup needs
#############################################################################

# Servername: Name of this server
# if not given, it takes hostname. It's preferable to setup one
# because machine name could change by some reason.

#servername greystone

# incomingdir:  Defines directory where incoming data packets are stored
# You could set directory relative to base path or absolute, starting with /

incomingdir /var/spool/pandora/data_in

# log_file: Main logfile for pandora_server
# You could set file relative to base path or absolute, starting with /

log_file /var/log/pandora/pandora_server.log

# Log file for Pandora FMS SNMP console. Its generated by NetSNMP Trap daemon

snmp_logfile /var/log/pandora/pandora_snmptrap.log

# Error logfile: aux logfile for pandora_server errors (in Daemon mode)
# You could set file relative to base path or absolute, starting with /

errorlog_file /var/log/pandora/pandora_server.error

# daemon: Runs in daemon mode (background) if 1, if 0 runs in foreground
# this could be also configured on commandline with -D option

# daemon 1

# dbengine: mysql, postgresql or oracle (mysql by default)

dbengine mysql

# Database credentials. A VERY important configuration.
# This must be the same credentials used by your Pandora FMS Console
# but could be different if your console is not running in the same
# host than the server. Check your console setup in /include/config.php

# dbname: Database name (pandora by default)

dbname pandora

# dbuser:  Database user name (pandora by default)

dbuser pandora

# dbpass: Database password

dbpass *******

# dbhost: Database hostname or IP address

dbhost localhost

# dbport: Database port number
# Default value depends on the dbengine (mysql: 3306, postgresql: 5432, oracle: 1521)

#dbport 3306

# By default, parent agent will not be updated

#update_parent 0

# verbosity: level of detail on errors/messages (0 default, 1 verbose, 2 debug.... 10 noisy)
# -v in command line (verbose) or -d (debug). Set this to 10 when try to locate problems and
# set to 0 or 1 on production enviroments.

verbosity 1

# Master Server, 1 if master server (normal mode), 0 for slave mode (slave in multi-server setup)

master 1

# Activate Pandora SNMP console (depending on snmptrapd)
#snmpconsole 0

snmpconsole 1

# snmptrapd will ignore authenticationFailure traps if set to 1.

snmp_ignore_authfailure 1

# snmptrapd will read the PDU source address instead of the agent-addr field is set to 1.

snmp_pdu_address 0

# Activate (1) Pandora Network Server

networkserver 1

# Activate (1) Pandora Data Server

dataserver 1

# Activate (1) Pandora FMS Recon server
#reconserver 1
reconserver 0

# pluginserver : 1 or 0. Set to 1 to activate plugin server with this setup

pluginserver 1

# Pandora FMS Plugin exec tool filepath (by default at /usr/bin)
plugin_exec /usr/bin/pandora_exec.server
#plugin_exec /usr/bin/timeout

# predictionserver : 1 or 0. Set to 1 to activate prediction server with this setup
# DISABLED BY DEFAULT

predictionserver 0

# wmiserver : 1 or 0. Set to 1 to activate WMI server with this setup
# DISABLED BY DEFAULT

wmiserver 0

# Network timeout (in seconds) for timeout in network connections for Network agents

network_timeout 4

# Server keepalive (in seconds)

server_keepalive 45

# Server Threshold: defines number of seconds of main loop (in sec)
server_threshold 15
#server_threshold 5

# Network threads: Do not set too high (~40). Each threads make a network module check.
network_threads 10
#network_threads 4

# icmp_checks x : defines number of pings for each icmp_proc module type. at least one of
# that ping should be 1 to report 1

icmp_checks 2

# tcp specific options :
# tcp_checks: number of tcp retries if first attempt fails.
# tcp_timeout: specific timeout for tcp connections

tcp_checks 1
tcp_timeout 30

# snmp specific options :
# snmp_checks: number of snmp request retries if first attempt fails.
# snmp_timeout: specific timeout for snmp request.

snmp_checks 1
snmp_timeout 4

# snmp_proc_deadresponse 1 (default): Return DOWN if cannot contact
# or receive NULL from a SNMP PROC module.

snmp_proc_deadresponse 1

# plugin_threads: Specify number of plugin server threads for processing plugin calls

plugin_threads 2

# plugin_timeout: Specify number of seconds calling plugin exec waiting for response
# after this time, call is aborted and result is "unknown".

plugin_timeout 15

# wmi_timeout : specific timeout for wmi request.

wmi_timeout 7

# wmi_threads: Specify number of WMI server threads for processing WMI remote calls

wmi_threads 1

# recon_threads. Each thread will scan a different scantask.

recon_threads 2

# dataserver_threads: Number of threads for data server (XML processing threads)
dataserver_threads 5
#dataserver_threads 1

# mta_address: External Mailer (MTA) IP Address to be used by Pandora FMS internal email capabilities

mta_address localhost

# mta_port, this is the mail server port (default 25)

#mta_port 25

# mta_user MTA User (if needed for auth, FQD or simple user, depending on your server)

#mta_user [email protected]

# mta_pass MTA Pass (if needed for auth)

#mta_pass mypassword

# mta_auth MTA Auth system (if needed, it supports LOGIN, PLAIN, CRAM-MD5, DIGEST-MD)

#mta_auth LOGIN

# mta_from Email address that sends the mail, by default is [email protected]
#          probably you need to change it to avoid problems with your antispam

#mta_from Pandora FMS <[email protected]>

# Set 1 if want eMail deliver alert in separate mail  (default).
# Set 0 if want eMail deliver shared mail by all destination.
mail_in_separate 1


# xprobe2: Optional package to detect OS types using advanced TCP/IP
# fingerprinting tecniques, much more accurates than stadard nmap.
# If not provided, nmap is used insted xprobe2

xprobe2 /usr/bin/xprobe2

# nmap: If provided, is used to detect OS type with recon server using
# advanded OS fingerprint technique. Xprobe2 gives more accurate results
# Nmap is also used to do TCP port scanning in detected host.

nmap /usr/bin/nmap

# snmpget: Needed to do SNMP checks. By default is on /usr/bin/snmpget

snmpget /usr/bin/snmpget

# Location of the braa binary needed by the Enterprise SNMP Server
# /usr/bin/braa by default (PANDORA FMS ENTERPRISE ONLY).

braa /usr/bin/braa

# Number of retries before braa hands a module over to the Network Server (PANDORA FMS ENTERPRISE ONLY).

braa_retries 3

# Default group id for new agents created with Pandora FMS Data Server
# If this token is enabled and Agent is setup with a fixed group, server settings will override agent settings

autocreate_group 2

# Set to 1 if want to autocreate agents with Pandora FMS Data Server,
# set to 0 to disable (for security purposes, for example).

autocreate 1

# max_log_size: Specify max size of Pandora FMS server log file (1MB by default). If
# log file grows above this limit, is renamed to "pandora_server.log.old".

max_log_size 65536

# max_queue_files (500 by default)
# When server have more than max_queue_files in incoming directory, skips the read
# the directory to avoid filesystem overhead.
max_queue_files 1000
#max_queue_files 500

# Use the XML file last modification time as timestamp.

# use_xml_timestamp 1

# Pandora FMS will autorestart itself each XXX seconds, use this if you experience problems with
# shutting down threads, or other stability problems.

# auto_restart 86400

# Pandora FMS will restart after restart_delay seconds on critical errors.

restart 1
#restart_delay 60

# More information about GIS Setup in /usr/share/pandora_server/util/gis.README
# Flag to activate GIS (positional information for agents and maps)
# by default it is desactivated

activate_gis 1

# Radius of error in meters to consider two gis locations as the same location.

location_error 50

# Recon reverse geolocation mode [disabled, sql, file]
#  disabled    The recon task doesn't try to geolocate the ip discovered.
#  sql        The recon task trys to query the SQL database to geolocate the
#              ip discovered
#  file        The recon task trys to find the geolocation information of the
#              ip discovered in the file indicated in the
#                recon_reverse_geolocation_file parameter

recon_reverse_geolocation_mode file

# Recon reverse geolocation file. This is the database with the reverse
# geolocation information using MaxMind GPL GeoLiteCity.dat format).

recon_reverse_geolocation_file /usr/local/share/GeoIP/GeoIPCity.dat

# Radius (in meters) of the circle in where the agents will be place randomly
# when finded by a recon task. Center of the circle is guessed
# by geolocating the IP.

recon_location_scatter_radius 1000

# Pandora Server self-monitoring (embedded agent) (by default enabled)

self_monitoring 1

# Update parent from the agent xml

#update_parent 1
#
#
# This enable realtime reverse geocoding using Google Maps public api.
# This requires internet access, and could have performance penalties processing GIS
# information due the connetion needed to resolve all GIS input.
# NOTE: If you dont pay the service to google, they will ban your IP in a few days.

# google_maps_description 1

# This enable realtime reverse geocoding using Openstreet Maps public api.
# This requires internet access, and could have performance penalties processing GIS
# information due the connetion needed to resolve all GIS input.
# You can alter the code to use a local (your own) openstreet maps server.

openstreetmaps_description 1

# Enable (1) or disable (0) Pandora FMS Event Web Server (PANDORA FMS ENTERPRISE ONLY).

webserver 1

# Number of threads for the Web Server (PANDORA FMS ENTERPRISE ONLY).

web_threads 1

# Uncomment to perform web checks with CURL instead of LWP.
#web_engine curl

# Enable (1) or disable (0) Pandora FMS Inventory Server (PANDORA FMS ENTERPRISE ONLY).

inventoryserver 1

# Number of threads for the Web Server (PANDORA FMS ENTERPRISE ONLY).

inventory_threads 1

# Enable (1) or disable (0) Pandora FMS Export Server (PANDORA FMS ENTERPRISE ONLY).

exportserver 0

# Number of threads for the Export Server (PANDORA FMS ENTERPRISE ONLY).

export_threads 1

# Enable (1) or disable (0) Pandora FMS Event Server (PANDORA FMS ENTERPRISE ONLY).

eventserver 1

# Event Server event window in seconds (3600 by default) (PANDORA FMS ENTERPRISE ONLY).

event_window 3600

# Enable (1) or disable (0) Pandora FMS Enterprise ICMP Server (PANDORA FMS ENTERPRISE ONLY).
# You need nmap 5.20 or higher in order to use this !

icmpserver 1

# Number of threads for the Enterprise ICMP Server (PANDORA FMS ENTERPRISE ONLY).

icmp_threads 2

# Enable (1) or disable (0) Pandora FMS Enterprise SNMP Server (PANDORA FMS ENTERPRISE ONLY).
# Check braa tool is running and operative.

snmpserver 1

# Number of threads for the Enterprise SNMP Server (PANDORA FMS ENTERPRISE ONLY).

snmp_threads 2

# Block size for block producer/consumer servers, that is, the number of modules
# per block (15 by default) (PANDORA FMS ENTERPRISE ONLY).

block_size 25

# If set to 1, process XML data files in a stack instead of a queue. 0 by default.
# WARNING: Incremental modules will not work properly if dataserver_lifo is set to 1!!!

dataserver_lifo 0

# If set to 1, the policy manager is enabled and the server is listening the policy queue.
# 0 by default (PANDORA FMS ENTERPRISE ONLY)

policy_manager 1

# If set to 1, the event replicate process is enabled. 0 by default. (PANDORA FMS ENTERPRISE ONLY)
# WARNING: This process doesn't do anything if is not properly configured from the console setup

event_replication 0

# If set to 1, new events validate older event for the same module. This will
# affect the performance of the server. This was the "normal behaviour" on previous (4.x) versions.
# disable only if you really know what you are doing !!.

event_auto_validation 1

# If defined, events generated by Pandora FMS will be written to the specified text file.
#event_file /var/log/pandora/pandora_events.txt

# Set the maximum number of traps that will be processed from a single source in a
# configured time interval.
snmp_storm_protection 25

# Time interval for snmp_storm protection (in seconds).
snmp_storm_timeout 10

# Default texts for some events. The macros _module_ and _data_ are supported.
#text_going_down_normal Module '_module_' is going to NORMAL (_data_)
#text_going_up_critical Module '_module_' is going to CRITICAL (_data_)
#text_going_up_warning Module '_module_' is going to WARNING (_data_)
#text_going_down_warning Module '_module_' is going to WARNING (_data_)
#text_going_unknown Module '_module_' is going to UNKNOWN

# Events older that the specified time (in seconds) will be auto-validated. Set to 0 to disable this feature.
event_expiry_time 0

# Only events more recent than the specified time window (in seconds) will be auto-validated. This value must
# be greater than event_expiry_time.
#event_expiry_window 86400

# If set to 1, SNMP modules run by the Network Server will be claimed back by
# the SNMP Enterprise Server when pandora_db is run.
claim_back_snmp_modules 1

My my.conf:
Quote:#
# 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
# http://dev.mysql.com/doc/mysql/en/server...ables.html

# 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.
[client]
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.
[mysqld_safe]
socket          = /var/run/mysqld/mysqld.sock
nice            = 0
log-error      = /var/log/mysqld.log
[mysqld]
#
# * Basic Settings
#
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir        = /usr
datadir        = /var/lib/mysql
tmpdir          = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
#bind-address          = 127.0.0.1
#
# * Fine Tuning
#
key_buffer              = 512M
max_allowed_packet      = 512M
thread_stack            = 256K
thread_cache_size      = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover        = BACKUP
max_connections        = 1024

max_heap_table_size    = 1024M
read_buffer_size        = 64M
read_rnd_buffer_size    = 128M
table_cache            = 256
sort_buffer_size        = 8M
max_delayed_threads    = 50

#table_cache            = 64
#thread_concurrency    = 10
#
# * Query Cache Configuration
#
query_cache_min_res_unit        = 1K
query_cache_limit      = 2M
query_cache_size        = 128M

join_buffer_size        = 16M

#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file        = /var/log/mysql/mysql.log
#general_log            = 1
#
# Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# Here you can see queries with especially long duration
#log_slow_queries      = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#      other settings you may need to change.
#server-id              = 1
#log_bin                        = /var/log/mysql/mysql-bin.log
expire_logs_days        = 10
max_binlog_size        = 100M
#binlog_do_db          = include_database_name
#binlog_ignore_db      = include_database_name
#
# * 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!
#

innodb_flush_log_at_trx_commit      = 0
innodb_buffer_pool_size              = 2G
innodb_additional_mem_pool_size      = 4M
innodb_flush_method                  = O_DIRECT
innodb_open_files                    = 700
innodb_thread_sleep_delay            = 1000
innodb_concurrency_tickets            = 250
innodb_lock_wait_timeout        = 180
innodb_thread_concurrency      = 10
innodb_io_capacity              = 100

# * 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



[mysqldump]
quick
quote-names
max_allowed_packet      = 512M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer              = 512M

back_log                = 100
log_warnings
#
# * IMPORTANT: Additional settings that can override those from this file!
#  The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/

This documentations help me a lot:
http://wiki.pandorafms.com/index.php?tit...xo_Upgrade
http://wiki.pandorafms.com/index.php?tit...procedures
http://wiki.pandorafms.com/index.php?tit...timization
https://github.com/pandorafms/pandorafms...181b22e0be

I would like to thank you guys that help me!

-rischfre
-Junichi Satoh
-Kosaka
-Sancho Lerena

 
 Reply


Users browsing this thread: 1 Guest(s)


(c) 2006-2018 Artica Soluciones Tecnológicas. Contents of this wiki are under Create Common Attribution v3 licence. | pandorafms.com | pandorafms.org

Theme © MyBB Themes