Linux Tutorials on the topic “errors”

  • Postfix - mail for example.com loops back to myself

    Postfix - mail for example.com loops back to myself

    Author: • Tags: • Comments: 6 • Updated: Jul 18, 2022

    Error: Postfix - mail for example.com loops back to myself You see the following error in your mail log: Feb 24 21:42:42 mail postfix/smtp[1911]: 8172723F60: to=<[email protected]>, relay=none, delay=0, status=bounced (mail for example.com loops back to myself)

    read more... | PDF view as pdf

  • Postfix - virtual_mailbox_limit is smaller than message_size_limit

    Postfix - virtual_mailbox_limit is smaller than message_size_limit

    Author: • Tags: • Comments: 1

    Error: Postfix - virtual_mailbox_limit is smaller than message_size_limit You get the following error in your mail log: Jul 13 17:12:30 mail postfix/virtual[10486]: fatal: main.cf configuration error: virtual_mailbox_limit is smaller than message_size_limit

    read more... | PDF view as pdf

  • nginx - 413 Request Entity Too Large

    nginx Author: Falko Timme • Tags: , • Comments: 1

    You see the following error in your browser when you try to upload a file through http: 413 Request entity Too Large

    read more... | PDF view as pdf

  • Ubuntu 11.10 + saslauthd: SASL PLAIN authentication failed: no mechanism available

    ubuntu Author: Falko Timme • Tags: • Comments: 12

    Error: Ubuntu 11.10 + saslauthd: SASL PLAIN authentication failed: no mechanism available You have installed Postfix with saslauthd on Ubuntu 11.10 and get the following error in /var/log/mail.log when you try to send an email: server1 postfix/smtpd[7868]: warning: unknown[1.2.3.4]: SASL PLAIN authentication failed: no mechanism available

    read more... | PDF view as pdf

  • Fedora 15 - Error: Package: glibc-2.14-5.i686 (updates) Requires: glibc-common = 2.14-5

    fedora Author: Falko Timme • Tags: • Comments: 0

    Error: Fedora 15 - Error: Package: glibc-2.14-5.i686 (updates) Requires: glibc-common = 2.14-5 You get an error like the following one on Fedora 15: Error: Package: glibc-2.14-5.i686 (updates) Requires: glibc-common = 2.14-5 Installed: glibc-common-2.14-7.x86_64 (@updates-testing) glibc-common = 2.14-7 Available: glibc-common-2.13.90-9.x86_64 (fedora) glibc-common = 2.13.90-9 Available: glibc-common-2.14-5.x86_64 (updates) glibc-common = 2.14-5 You could try using --skip-broken to work around the problem ** Found 2 pre-existing rpmdb problem(s), 'yum check' output follows: nss_db-2.2.3-0.5.pre1.fc15.x86_64 has missing requires of libc.so.6(GLIBC_PRIVATE)(64bit) nss_db-2.2.3-0.5.pre1.fc15.x86_64 has missing requires of libnss_files.so.2(GLIBC_PRIVATE)(64bit)

    read more... | PDF view as pdf

  • Debian/Ubuntu - unable to make backup link of `./usr/sbin/sshd' before installing new version: Operation not permitted

    debian Author: Falko Timme • Tags: • Comments: 5

    Error: Debian/Ubuntu - unable to make backup link of `./usr/sbin/sshd' before installing new version: Operation not permitted You try to upgrade OpenSSH on Debian/Ubuntu (packages openssh-client and openssh-server) and get the following errors: Unpacking replacement openssh-server ... dpkg: error processing /var/cache/apt/archives/openssh-server_1%3a5.5p1-6_amd64.deb (--unpack): unable to make backup link of `./usr/sbin/sshd' before installing new version: Operation not permitted configured to not write apport reports Preparing to replace openssh-client 1:5.1p1-5 (using .../openssh-client_1%3a5.5p1-6_amd64.deb) ... Unpacking replacement openssh-client ... dpkg: error processing /var/cache/apt/archives/openssh-client_1%3a5.5p1-6_amd64.deb (--unpack): unable to make backup link of `./usr/bin/ssh' before installing new version: Operation not permitted

    read more... | PDF view as pdf

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

    centos Author: Falko Timme • Tags: • Comments: 0

    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

    read more... | PDF view as pdf

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

    postfix Author: Falko Timme • Tags: • Comments: 0

    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

    read more... | PDF view as pdf

  • CentOS 5.6 - php53-common conflicts with php-common

    centos Author: Falko Timme • Tags: • Comments: 7

    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 ~]#

    read more... | PDF view as pdf

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

    mysql Author: Falko Timme • Tags: , , • Comments: 6

    You try to create a MySQL database dump and get the following error: 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

    read more... | PDF view as pdf

Page 1 of 4