Mini-Howtos

Want to support HowtoForge? Become a subscriber!
 

CentOS 5.6/Dovecot - Fatal: listen(::, 143) failed: Address already in use

Error: CentOS 5.6/Dovecot - Fatal: listen(::, 143) failed: Address already in use

You try to start Dovecot on CentOS 5.6 and get the following error:

Fatal: listen(::, 143) failed: Address already in use

Postfix/Greyfix - warning: problem talking to server private/greyfix: No such file or directory

Error: Postfix/Greyfix - warning: problem talking to server private/greyfix: No such file or directory

You get the following error in your mail log:

Aug 26 16:20:00 server1 postfix/smtpd[8471]: warning: problem talking to server private/greyfix: No such file or directory

CentOS 5.6 - php53-common conflicts with php-common

Error: CentOS 5.6 - php53-common conflicts with php-common

You have PHP 5.1.6 installed on CentOS 5.6 and want to update to PHP 5.3 like this:

yum install php53 php53-cli php53-common php53-gd php53-imap php53-intl php53-mbstring php53-mysql php53-odbc php53-pdo php53-pspell php53-snmp php53-xml php53-xmlrpc

The update aborts with the following error:

[root@server1 ~]# yum install php53 php53-cli php53-common php53-gd php53-imap php53-intl php53-mbstring php53-mysql php53-odbc php53-pdo php53-pspell php53-snmp php53-xml php53-xmlrpc
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.weepeetelecom.be
 * extras: centos.weepeetelecom.be
 * updates: ftp.belnet.be
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package php53.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-cli.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-common.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-gd.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-imap.x86_64 0:5.3.3-1.el5_6.1 set to be updated
--> Processing Dependency: libc-client.so.1()(64bit) for package: php53-imap
---> Package php53-intl.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-mbstring.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-mysql.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-odbc.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-pdo.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-pspell.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-snmp.x86_64 0:5.3.3-1.el5_6.1 set to be updated
--> Processing Dependency: net-snmp for package: php53-snmp
---> Package php53-xml.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-xmlrpc.x86_64 0:5.3.3-1.el5_6.1 set to be updated
--> Running transaction check
---> Package libc-client.x86_64 0:2004g-2.2.1 set to be updated
---> Package net-snmp.x86_64 1:5.3.2.2-9.el5_5.1 set to be updated
--> Processing Dependency: libsensors.so.3()(64bit) for package: net-snmp
--> Running transaction check
---> Package lm_sensors.x86_64 0:2.10.7-9.el5 set to be updated
--> Processing Conflict: php53-common conflicts php-common
--> Finished Dependency Resolution
php53-common-5.3.3-1.el5_6.1.x86_64 from updates has depsolving problems
  --> php53-common conflicts with php-common
Error: php53-common conflicts with php-common
 You could try using --skip-broken to work around the problem
 You could try running: package-cleanup --problems
                        package-cleanup --dupes
                        rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.
[root@server1 ~]#

MySQL - mysqldump: Got error: 1016: Can't open file: './exampledb/xxx.frm' (errno: 24) when using LOCK TABLES

Error: MySQL - mysqldump: Got error: 1016: Can't open file: './exampledb/xxx.frm' (errno: 24) when using LOCK TABLES

You try to create a MySQL database dump and get the following error:

mysqldump -u root -pmysecretpassword --opt exampledb > exampledb.sql

root@server11:/tmp/mysql# mysqldump -u root -pmysecretpassword --opt exampledb > exampledb.sql
mysqldump: Got error: 1016: Can't open file: './exampledb/xxx.frm' (errno: 24) when using LOCK TABLES
root@server1:/tmp/mysql#

Postfix/Dovecot - warning: SASL: Connect to private/auth failed: No such file or directory

Error: Postfix/Dovecot - warning: SASL: Connect to private/auth failed: No such file or directory

You have the following error messages in your mail log:

Aug 23 15:55:01 server1 postfix/smtpd[15194]: warning: SASL: Connect to private/auth failed: No such file or directory
Aug 23 15:55:01 server1 postfix/smtpd[15194]: fatal: no SASL authentication mechanisms
Aug 23 15:55:02 server1 postfix/master[3979]: warning: process /usr/libexec/postfix/smtpd pid 15194 exit status 1
Aug 23 15:55:02 server1 postfix/master[3979]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling

SpamAssassin - config: no rules were found! Do you need to run 'sa-update'?

Error: SpamAssassin - config: no rules were found! Do you need to run 'sa-update'?

You run

spamassassin --lint

and get the following output:

[root ~]# spamassassin --lint
config: no rules were found! Do you need to run 'sa-update'?
[root ~]#

Nagios/Icinga (Debian Squeeze) - NRPE: Command 'check_procs' not defined

Error: Nagios/Icinga (Debian Squeeze) - NRPE: Command 'check_procs' not defined

You monitor a remote server with Nagios or Icinga and see the following errors in your Nagios/Icinga web interface:

NRPE: Command 'check_all_disks' not defined
NRPE: Command 'check_mysql_cmdlinecred' not defined
NRPE: Command 'check_procs' not defined

Nagios/Icinga (Debian Squeeze) - CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.

Error: Nagios/Icinga (Debian Squeeze) - CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.

You monitor a remote server with Nagios or Icinga and see the following error in your Nagios/Icinga web interface:

CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.

In /var/log/syslog on the remote server you see these messages:

Aug 23 14:20:20 server2 nrpe[11496]: Error: Request contained command arguments, but argument option is not enabled!
Aug 23 14:20:20 server2 nrpe[11496]: Client request was invalid, bailing out...

Nagios/Icinga (Debian Squeeze) - CHECK_NRPE: Error - Could not complete SSL handshake.

Error: Nagios/Icinga (Debian Squeeze) - CHECK_NRPE: Error - Could not complete SSL handshake.

You try to connect from your Nagios/Icinga host to a remote Nagios NRPE server like this...

/usr/lib/nagios/plugins/check_nrpe -H 9.8.7.6

... and get the following error:

root@server1:/etc/nagios-plugins/config# /usr/lib/nagios/plugins/check_nrpe -H 9.8.7.6
CHECK_NRPE: Error - Could not complete SSL handshake.
root@server1:/etc/nagios-plugins/config#

OpenSUSE - Can't connect to UNIX socket /var/run/clamav/clamd: No such file or directory

Error: OpenSUSE - Can't connect to UNIX socket /var/run/clamav/clamd: No such file or directory

You get the following error in your mail log:

Jul 7 09:13:35 hades amavis[21674]: (21674-01) (!!)ClamAV-clamd av-scanner FAILED: run_av error: Too many retries to talk to /var/run/clamav/clamd (Can't connect to UNIX socket /var/run/clamav/clamd: No such file or directory) at (eval 101) line 325.

first page
previous page
3
...
next page
last page