[Postfixbuch-users] Fehlermeldung: postfix/trivial-rewrite, table lookup problem?

[Patrick Ben Koetter]

* Christian Frankerl <MainNewz at gmx.net>:
> Also angefangen hat's heute um 12:26 mit folgendem, vorher ist kein
> mysql Eintrag zu finden:
> 
> -------------------------------------------------------------------
> Jun 30 12:26:33 spooky /etc/init.d/mysql[7604]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
> Jun 30 12:26:33 spooky mysqld_safe[7608]: started
> Jun 30 12:26:33 spooky /etc/init.d/mysql[7604]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
> Jun 30 12:26:33 spooky /etc/init.d/mysql[7604]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
> Jun 30 12:26:33 spooky /etc/init.d/mysql[7604]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
> Jun 30 12:26:33 spooky /etc/init.d/mysql[7604]:
> Jun 30 12:28:07 spooky mysqld[7640]: 050630 12:28:07  InnoDB: Database was not shut down normally!
> Jun 30 12:28:07 spooky mysqld[7640]: InnoDB: Starting crash recovery.
> Jun 30 12:28:07 spooky mysqld[7640]: InnoDB: Reading tablespace information from the .ibd files...
> Jun 30 12:28:42 spooky mysqld[7640]: InnoDB: Restoring possible half-written data pages from the doublewrite
> Jun 30 12:28:42 spooky mysqld[7640]: InnoDB: buffer...
> Jun 30 12:29:31 spooky mysqld[7640]: 050630 12:29:31  InnoDB: Starting log scan based on checkpoint at
> Jun 30 12:29:31 spooky mysqld[7640]: InnoDB: log sequence number 0 45962.
> Jun 30 12:29:37 spooky mysqld[7640]: InnoDB: Doing recovery: scanned up to log sequence number 0 47344
> Jun 30 12:30:00 spooky mysqld[7640]: InnoDB: Last MySQL binlog file position 0 4, file name /var/log/mysql/mysql-bin.000098
> Jun 30 12:30:00 spooky mysqld[7640]: 050630 12:30:00  InnoDB: Flushing modified pages from the buffer pool...
> Jun 30 12:30:01 spooky mysqld[7640]: 050630 12:30:01  InnoDB: Started; log sequence number 0 47344
> Jun 30 12:30:58 spooky mysqld[7640]: /usr/sbin/mysqld: ready for connections.
> Jun 30 12:30:58 spooky mysqld[7640]: Version: '4.1.11-Debian_4-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution
> Jun 30 12:31:15 spooky authdaemond.mysql: modules="authmysql", daemons=5
> 
> Jun 30 12:36:09 spooky postfix/trivial-rewrite[14124]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
> Jun 30 12:36:09 spooky postfix/trivial-rewrite[14124]: fatal: mysql:/etc/postfix/forward.mysql(0,100): table lookup problem
> Jun 30 12:36:11 spooky postfix/trivial-rewrite[14208]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
> Jun 30 12:36:11 spooky postfix/trivial-rewrite[14208]: fatal: mysql:/etc/postfix/forward.mysql(0,100): table lookup problem
> [Das setzt sich dann Seitenweise fort bis 16 Uhr, da hab ich mysql restarted]
> -------------------------------------------------------------------
> 
> Anscheinend hatte die Datenbank ein problem, aber woher kann sowas
> kommen? Es wurde nichts am Server geändert, Platz sind noch 50% der
> Platte frei und sonst läuft auch alles ganz normal. (zumindest sieht's
> so aus)
> 
> Noch ne Idee?

Ja, Du weißt noch zu wenig. Du mußt Dir mehr Informationen beschaffen. Teste
einzelne Abschnitte, um die Ursache einzukreisen:

1. Kannst Du mit mysql auf die table zugreifen?
2. Gehen Abfragen?
3. Liefern sie die richtigen Ergebnisse?
4. Läuft Postfix chrooted?
5. Kann Postfix auf /var/run/mysqld/mysqld.sock zugreifen?

p at rick


-- 
The Book of Postfix
<http://www.postfix-book.com>
SMTP AUTH debug utility:
<http://postfix.state-of-mind.de/patrick.koetter/saslfinger/>