The strange thing is that usually the first install or two will work on any new machine but then it suddenly won't. I had this experience on QEMU 2.13 on a different machine. There is something finicky or buggy about the CUCM installer even when choosing the same virtual hardware specs.
QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2-2.506.el6_10.1), Copyright (c) 2003-2008 Fabrice Bellard
Your database uses Antelope as the file format. Full UTF-8 support in MySQL and MariaDB requires the Barracuda file format. Please switch to the Barracuda file format. See the documentation MySQL full unicode support for details.
In /etc/my.cnf under [mysqld]
180827 21:43:14 InnoDB: 5.5.59 started; log sequence number 1589339
180827 21:43:14 [ERROR] /usr/libexec/mysqld: unknown variable 'db_file_format=Ba........
Jul 3 22:12:17mailserver postfix/smtpd: fatal: no SASL authentication mechanisms
Jul 3 22:12:18mailserver postfix/master: warning: process /usr/libexec/postfix/smtpd pid 6195 exit status 1
Jul 3 22:12:18mailserver postfix/master: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
This only ever happens in my experience when the authentication method is actually Dovecot. Usually the problem........
This happened on Centos for no apparent reason with no obvious issue in the logs. Data could be read fine but not written (possibly due to some corruption or out of memory issue in the OpenVZ container is the best guess).
All mysql update and insert queries failed freezing without any error log on any database and table.
Tried to restart:
service mysqld restart
Timeout error occurred trying to stop MySQL........
The solution is simple but strange, if you copy your /var/lib/mysql directory to another server and think it will work, be sure to check if you have /var/log/mysql and binary log files. If you do, the server will not work and will give you errors like below and crash without the proper log files.
UPDATE user SET password=password("newpass") WHERE user='root';
ERROR 2013 (HY000): Lost connection to MySQL server durin........
170110 5:35:23 [Note] /usr/libexec/mysqld: Normal shutdown
170110 5:35:23 [Note] Event Scheduler: Purging the queue. 0 events
170110 5:35:23 InnoDB: Starting shutdown...
170110 5:35:24 InnoDB: Shutdown completed; log sequence number 0 12765401
170110 5:35:24 [Note] /usr/libexec/mysqld: Shutdown complete
170110 05:35:24 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended........
You are checking your MySQL logs in /var/log/mysqld.log and come across an error like this:
161222 18:03:40 [ERROR] /usr/libexec/mysqld: Table './eximstats/sends' is marked as crashed and last (automatic?) repair failed
myisamchk -r sends.MYI
- recovering (with sort) MyISAM-table 'sends.MYI'
Data records: 71129........
Thsi is very handy when doing your own kernel development.
-m specifies how much ram (in the example it is 768MB)
-kernel specifies the path to the kernel file
-net tap,ifname=tap1,script=no (the ifname=tap1 is what you need to change and setup manually).
*Run "tunctl -b" to create a tap device and use the one it gives you for ifname=
Enable networking to the outside like this:
*Note we assume that your bridge is br0 i........
First of all if you're getting this error it is a result of extreme database activity. If you aren't expecting it or it doesn't make sense to you 99% of the time this is a database driven script being exploited (some common examples I see often are things like phpBB being hit by dozens, hundreds or thousands of bots making constant DB write requests).
The easiest way to identify this is to restart MySQL and then run the third party tool "mtop" and you'll see all........
I am running a 64-bit host and was running a 32-bit XPguest which was crawling no matter what I was doing with it,in fact it frequently used 100% CPU power while having no real work load. I experienced with this other guests and wondered why KVM was slow compared to say Xen or Virtualbox.
This is because you need to use the "-cpu" flag.
For a full list of options run:
/usr/libexec/qemu-kvm -cpu ?
Centos 5 Postfix and SPAMASSASSIN Tutorial
yum install spamassassin
chkconfig spamassassin on
#rewrite_header Subject [SPAM]
#5 is the least restrictive (means only the most obvious SPAM is caught. 0 is obviously the most restrictive/sensitive and would have lots of false positives
don't delete /var/lib/mysql/ib_logfile0 or ibdata1 or mysql won't restart
I didn't realize they were internal and not part of replication like the relay files!
/usr/libexec/mysqld: ready for connections.
Version: '4.1.22-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
110127 16:31:00 [Note] /usr/libexec/mysqld: Normal shutdown
110127 16:31:00 InnoDB: Starting shutdown...........
100215 07:02:24 mysqld started
/usr/libexec/mysqld: Can't read dir of '/tmp/' (Errcode: 13)
/usr/libexec/mysqld: Can't create/write to file '/tmp/ibyP1qUC' (Errcode: 13)
100215 7:02:24 InnoDB: Error: unable to create temporary file; errno: 13
100215 7:02:24 [ERROR] Can't init databases
100215 7:02:24 [ERROR] Aborting
100215 7:02:24 [Note] /usr/libexec/mysqld: Shutdown complete