Postfix problemy z smtp po zmianie domeny.

Konfiguracja serwerów, usług, itp.
miras_w
Beginner
Posty: 199
Rejestracja: 13 czerwca 2007, 19:32
Lokalizacja: Wejherowo

Postfix problemy z smtp po zmianie domeny.

Post autor: miras_w »

Wypluwa coś takiego:

Kod: Zaznacz cały

Nov  6 13:16:31 wozio mysqld[2977]: refused connect from 127.0.0.1
Nov  6 13:16:31 wozio postfix/proxymap[23025]: warning: connect to mysql server 127.0.0.1: Lost connection to MySQL server at 'reading initial communication packet', system error: 0
Nov  6 13:16:32 wozio mysqld[2977]: refused connect from 127.0.0.1
Nov  6 13:16:32 wozio postfix/proxymap[23025]: warning: connect to mysql server 127.0.0.1: Lost connection to MySQL server at 'reading initial communication packet', system error: 0
Nov  6 13:16:32 wozio postfix/trivial-rewrite[23024]: fatal: proxy:mysql:/etc/postfix/mysql-virtual_domains.cf(0,lock|fold_fix): table lookup problem
Nov  6 13:16:33 wozio postfix/qmgr[22354]: warning: premature end-of-input on private/rewrite socket while reading input attribute name
Nov  6 13:16:33 wozio postfix/qmgr[22354]: warning: problem talking to service rewrite: Success
Nov  6 13:16:33 wozio postfix/master[22348]: warning: process /usr/lib/postfix/trivial-rewrite pid 23024 exit status 1
Nov  6 13:16:33 wozio postfix/master[22348]: warning: /usr/lib/postfix/trivial-rewrite: bad command startup -- throttling
Nov  6 13:17:01 wozio CRON[23188]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov  6 13:17:01 wozio /USR/SBIN/CRON[23189]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Nov  6 13:17:01 wozio CRON[23188]: pam_unix(cron:session): session closed for user root
Co może być nie tak?
Awatar użytkownika
ShinnRa
Beginner
Posty: 457
Rejestracja: 05 marca 2007, 23:05
Lokalizacja: Gdynia

Post autor: ShinnRa »

po pierwsze

Kod: Zaznacz cały

Nov  6 13:16:31 wozio mysqld[2977]: refused connect from 127.0.0.1 
zezwól w mysql na połaczenia z 127.0.0.1
miras_w
Beginner
Posty: 199
Rejestracja: 13 czerwca 2007, 19:32
Lokalizacja: Wejherowo

Post autor: miras_w »

Mam tak

Kod: Zaznacz cały

$F -A INPUT -s 127.0.0.0/8 -j ACCEPT
Awatar użytkownika
ShinnRa
Beginner
Posty: 457
Rejestracja: 05 marca 2007, 23:05
Lokalizacja: Gdynia

Post autor: ShinnRa »

a co Ci zwróci:

Kod: Zaznacz cały

mysql -h 127.0.0.1 -u root -p
miras_w
Beginner
Posty: 199
Rejestracja: 13 czerwca 2007, 19:32
Lokalizacja: Wejherowo

Post autor: miras_w »

Kod: Zaznacz cały

mysql -h 127.0.0.1 -u root -p
Enter password:
ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 0
Awatar użytkownika
ShinnRa
Beginner
Posty: 457
Rejestracja: 05 marca 2007, 23:05
Lokalizacja: Gdynia

Post autor: ShinnRa »

czy w /etc/mysql/my.cnf masz takie coś:

Kod: Zaznacz cały

bind-address = 127.0.0.1 
miras_w
Beginner
Posty: 199
Rejestracja: 13 czerwca 2007, 19:32
Lokalizacja: Wejherowo

Post autor: miras_w »

tak mam.

Kod: Zaznacz cały

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
# [url]http://dev.mysql.com/doc/mysql/en/server-system-variables.html[/url]

# 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

[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
language        = /usr/share/mysql/english
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              = 16M
max_allowed_packet      = 16M
thread_stack            = 128K
thread_cache_size       = 8
#max_connections        = 100
#table_cache            = 64
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit       = 1M
query_cache_size        = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log            = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement :)
#
# 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
# WARNING: Using expire_logs_days without bin_log crashes the server! See README.Debian!
expire_logs_days        = 10
max_binlog_size         = 100M
#binlog_do_db           = include_database_name
#binlog_ignore_db       = include_database_name
#
# * BerkeleyDB
#
# Using BerkeleyDB is now discouraged as its support will cease in 5.1.12.
skip-bdb
#
# * 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!
# You might want to disable InnoDB to shrink the mysqld process by circa 100MB.
#skip-innodb
#
# * 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      = 16M

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

[isamchk]
key_buffer              = 16M

#
# * NDB Cluster
#
# See /usr/share/doc/mysql-server-*/README.Debian for more information.
#
# The following configuration is read by the NDB Data Nodes (ndbd processes)
# not from the NDB Management Nodes (ndb_mgmd processes).
#
# [MYSQL_CLUSTER]
# ndb-connectstring=127.0.0.1


#
# * IMPORTANT: Additional settings that can override those from this file!
#
!includedir /etc/mysql/conf.d/
Awatar użytkownika
ShinnRa
Beginner
Posty: 457
Rejestracja: 05 marca 2007, 23:05
Lokalizacja: Gdynia

Post autor: ShinnRa »

chyba już kojarzę co może być nie tak. W lennym mysql-server chyba ma jakiegoś buga z tym "lost connection". Miałem coś podobnego tylko w czasie wykonywania zapytania. To było jakoś ze 3-mce temu. Nie wiem czy w najnowszej wersji jest to poprawione.
miras_w
Beginner
Posty: 199
Rejestracja: 13 czerwca 2007, 19:32
Lokalizacja: Wejherowo

Post autor: miras_w »

Juz działa zminiłem na sida, zostawiłem tylko postfixa gdyz mam na nim quote. Potestuję trochę na unstable zobaczymy co z tego wyjdzie pozdrawiam.
ODPOWIEDZ