Master server fail

Discussion in 'Installation/Configuration' started by mmidgett, Sep 21, 2012.

  1. mmidgett

    mmidgett Member

    I am trying to replace the working files from an old master to make a new master. I am having trouble with postfix-mysql. Here are error that I am getting.


    Sep 21 14:03:16 web1 postfix/trivial-rewrite[4293]: warning: proxy:mysql:/etc/postfix/mysql-virtual_domains.cf: table lookup problem
    Sep 21 14:03:16 web1 postfix/trivial-rewrite[4293]: warning: virtual_mailbox_domains lookup failure
    Sep 21 14:03:16 web1 postfix/trivial-rewrite[4293]: warning: proxy:mysql:/etc/postfix/mysql-virtual_domains.cf: table lookup problem
    Sep 21 14:03:16 web1 postfix/trivial-rewrite[4293]: warning: virtual_mailbox_domains lookup failure
    Sep 21 14:03:16 web1 postfix/smtpd[4300]: warning: mysql:/etc/postfix/mysql-virtual_client.cf: table lookup problem


    My mysql table is loaded and I think that I have the correct password in those files.

    My client is been down for 24 hours. They are not happy with me.

    Please shead some insite as ftp and mail are not working

    I know its something to do with access to the DB for lookups but I haven't been able to find it on google.

    Thanks
     
  2. mmidgett

    mmidgett Member

    I am also having an apache problem....Iv'e never been this stumped before

    * Starting web server apache2 [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.145:80 overlaps with VirtualHost 216.249.106.145:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.143:80 overlaps with VirtualHost 216.249.106.143:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.137:80 overlaps with VirtualHost 216.249.106.137:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.144:80 overlaps with VirtualHost 216.249.106.144:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.144:80 overlaps with VirtualHost 216.249.106.144:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.144:80 overlaps with VirtualHost 216.249.106.144:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.144:80 overlaps with VirtualHost 216.249.106.144:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.144:80 overlaps with VirtualHost 216.249.106.144:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.145:80 overlaps with VirtualHost 216.249.106.145:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.137:80 overlaps with VirtualHost 216.249.106.137:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.137:80 overlaps with VirtualHost 216.249.106.137:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.146:80 overlaps with VirtualHost 216.249.106.146:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.144:80 overlaps with VirtualHost 216.249.106.144:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.145:80 overlaps with VirtualHost 216.249.106.145:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.144:80 overlaps with VirtualHost 216.249.106.144:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.145:80 overlaps with VirtualHost 216.249.106.145:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.144:80 overlaps with VirtualHost 216.249.106.144:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.144:80 overlaps with VirtualHost 216.249.106.144:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.144:80 overlaps with VirtualHost 216.249.106.144:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.144:80 overlaps with VirtualHost 216.249.106.144:80, the first has precedence, perhaps you need a NameVirtualHost directive
    [Fri Sep 21 18:08:15 2012] [warn] VirtualHost 216.249.106.147:80 overlaps with VirtualHost 216.249.106.147:80, the first has precedence, perhaps you need a NameVirtualHost directive

    I copyed the the Apache setup from the old working server that has kernel panics now after a upgrade that went wrong. All the sites are there and the permissions are just fine. I cant figure out why this worked before. I just need to get this operational today
     
  3. mmidgett

    mmidgett Member

    Forgot to tell you that its Ubuntu 12.04 Server 64, Fresh install with the perfect server install from the 10.04 as I need the courier setup as old server used courer and I though it would be simpler that way.

    I copyed the /var/lib/mysql and the postfix and apache and the www folder and I thought this would be simple. I also copied the the /usr/local/ispconfig folder and overlayed it also so I thought that this would think it was installed this way.
    Is there something simple that I have forgotten.

    Right now apache wont start and you can't get mail in or out due it postfix not able to do its lookups. The ispconfig username and pasword for the transport maps works on the command line to log into mysql so I do no know what to check. I also know unless I can get the web interface up amavis and postfix can't talk once I get the other problem fix due to not being able to adjust the firewall on this new install
     
  4. mmidgett

    mmidgett Member

    After 48 hours of banging my head I've got this working now mostly.
    The only problem that I have left is my ftp users are not able to see their directorys or files. They can connect but get a blank pane. Im currently working to find a solution for this on the internet.
     
  5. falko

    falko Super Moderator ISPConfig Developer

    Did you try both active and passive transfers in your FTP client?
     
  6. mmidgett

    mmidgett Member

    No I had the client set to auto,

    Here is the connection in active

    Status: Resolving address of web1.w3fc.com
    Status: Connecting to 216.249.106.135:21...
    Status: Connection established, waiting for welcome message...
    Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
    Response: 220-You are user number 1 of 50 allowed.
    Response: 220-Local time is now 10:09. Server port: 21.
    Response: 220-This is a private system - No anonymous login
    Response: 220-IPv6 connections are also welcome on this server.
    Response: 220 You will be disconnected after 15 minutes of inactivity.
    Command: USER mmidgett
    Response: 331 User mmidgett OK. Password required
    Command: PASS ********
    Response: 230 OK. Current restricted directory is /
    Command: SYST
    Response: 215 UNIX Type: L8
    Command: FEAT
    Response: 211-Extensions supported:
    Response: EPRT
    Response: IDLE
    Response: MDTM
    Response: SIZE
    Response: MFMT
    Response: REST STREAM
    Response: MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
    Response: MLSD
    Response: AUTH TLS
    Response: PBSZ
    Response: PROT
    Response: UTF8
    Response: ESTA
    Response: PASV
    Response: EPSV
    Response: SPSV
    Response: ESTP
    Response: 211 End.
    Command: OPTS UTF8 ON
    Response: 200 OK, UTF-8 enabled
    Status: Connected
    Status: Retrieving directory listing...
    Command: PWD
    Response: 257 "/" is your current location
    Command: TYPE I
    Response: 200 TYPE is now 8-bit binary
    Command: PORT 192,168,8,105,133,34
    Response: 200 PORT command successful
    Command: MLSD
    Response: 150 Connecting to port 2372
    Response: 226-Sorry, we were unable to read [.] <-----------I think this is the problem
    Response: 226-Options: -a -l
    Response: 226 0 matches total
    Status: Directory listing successful

    Here in passive


    Status: Resolving address of web1.w3fc.com
    Status: Connecting to 216.249.106.135:21...
    Status: Connection established, waiting for welcome message...
    Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
    Response: 220-You are user number 1 of 50 allowed.
    Response: 220-Local time is now 10:11. Server port: 21.
    Response: 220-This is a private system - No anonymous login
    Response: 220-IPv6 connections are also welcome on this server.
    Response: 220 You will be disconnected after 15 minutes of inactivity.
    Command: USER mmidgett
    Response: 331 User mmidgett OK. Password required
    Command: PASS ********
    Response: 230 OK. Current restricted directory is /
    Command: SYST
    Response: 215 UNIX Type: L8
    Command: FEAT
    Response: 211-Extensions supported:
    Response: EPRT
    Response: IDLE
    Response: MDTM
    Response: SIZE
    Response: MFMT
    Response: REST STREAM
    Response: MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
    Response: MLSD
    Response: AUTH TLS
    Response: PBSZ
    Response: PROT
    Response: UTF8
    Response: ESTA
    Response: PASV
    Response: EPSV
    Response: SPSV
    Response: ESTP
    Response: 211 End.
    Command: OPTS UTF8 ON
    Response: 200 OK, UTF-8 enabled
    Status: Connected
    Status: Retrieving directory listing...
    Command: PWD
    Response: 257 "/" is your current location
    Command: TYPE I
    Response: 200 TYPE is now 8-bit binary
    Command: PASV
    Response: 227 Entering Passive Mode (216,249,106,135,157,3)
    Command: MLSD
    Response: 150 Accepted data connection
    Response: 226-Sorry, we were unable to read [.] <------same issue
    Response: 226-Options: -a -l
    Response: 226 0 matches total
    Status: Directory listing successful



    I also tried plain ftp and tls setting to make sure that this wasn't the problem.

    I just fixed this by chowning the .. to the username and group

    What I can't understand is when I did chown -R username:group web
    that is didn't set the permissions right on the .. as it did on all the other files. I spent over 2 hours yesterday going through all the websites and setting the correct owner and group on all the directortys as they go messed up when i restored the backup. Do you have a quick and dirty solution to help speed of the process or am I going to have to do the same again?

    Once this has been done I will have sucessfully made a new master server for my multi-server setup.
     
  7. falko

    falko Super Moderator ISPConfig Developer

    Did this (wrong ownerships) happen only for restored websites, or also for websites you didn't restore?
     
  8. mmidgett

    mmidgett Member

    I didn't get notified about you posting back to my question. But to answer it now it only affected the websites that I copied. New creations are fine. I think that I might have forgot to preserve on the tar command or maybe the restore and copy. I was so tired that week from no sleep I messed up alot of things that I normally wouldn't do.

    Now that I am out of the red zone and smooth sailing I think that I'm going to move the master CP to another server but use nginx instead b/c i need apache to server a different CP for scrollout F1 for mail scanning. I hope this works well. so the new serer setup will look like this.

    ispconfig CP and scrollout F1 on small vm
    web1 / mail on server 2
    and 2 ns servers as usual
     

Share This Page