The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

FreeBSD - rsync.core - DNS not working - package add failing - other oddities

Discussion in 'Bind / DNS / Nameserver Issues' started by djordan, May 10, 2003.

  1. djordan

    djordan Registered

    Joined:
    May 10, 2003
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    FreeBSD 4.7-RELEASE
    WHM 6.2.0 Cpanel 6.4.0-R19 FreeBSD 4.7-RELEASE
    named 8.3.3-REL Wed Oct 9 12:19:59 GMT 2002 root@builder.freebsdmall.com:/usr/obj/usr/src/usr.sbin/named
    ==========================================
    We installed Cpanel fresh.. there were no accounts on these boxes at all.. 100% clean vanilla basic FreeBSD 4.7 install.

    Problem #1
    ===========
    Still having MAJOR problems setting up our customer servers.
    Our basic configuration consists of one master name server, and all this machine does is DNS.. period - nothing else. We then have 5 other servers which are going to be where the customers accounts will be served from.

    We have established a Master Server Trust as instructed by Tech support, however everytime we add a test account we are bludgeoned with this:

    Keeping Shell Access
    Copying skel files from /root/cpanel3-skel/ to /usr/home/testme/
    Using Freebsd Copy
    /root/cpanel3-skel/public_html -> /usr/home/testme/public_html
    /root/cpanel3-skel/public_ftp -> /usr/home/testme/public_ftp
    Using redhat 6.x/freebsd support
    Name Virtual Host already exists
    Added Entries to httpd.conf (ip)
    Adding Proftpd conf entry
    Added DomainAlias Entry
    Added Named Entry
    Added Named File
    Permission denied, please try again.
    Permission denied, please try again.
    Permission denied.
    Permission denied, please try again.
    Permission denied, please try again.
    Permission denied.
    Permission denied, please try again.
    Permission denied, please try again.
    Permission denied.
    Permission denied, please try again.
    Permission denied, please try again.
    Permission denied.
    Permission denied, please try again.
    Permission denied, please try again.
    Permission denied.
    Added Remote Named File
    Rebuilding DNS Zones List from master server .....
    Permission denied, please try again.
    Permission denied, please try again.
    Permission denied.
    Scp failed!
    Restarting apache
    Restarting proftpd
    Ftp Password Files synced
    Vhost Passwords synced
    wwwacct creation finished
    Account Creation Complete!!!

    Any ideas?

    Problem #2
    ===============
    We thought that perhaps we should update to Bind9. So from the 'Install Ports' section:
    Click on the path to the port to install it!
    Port: bind9-9.2.2
    Path /usr/ports/net/bind9
    Info: Completely new version of the BIND DNS server
    Maint: DougB@FreeBSD.org
    Index: net ipv6
    B-deps:
    R-deps:

    So I click on the port and get this:
    make: no target to make.
    make: don't know how to make install. Stop
    make: don't know how to make clean. Stop

    Wonderful huh?

    Oh it gets better..

    We thought we should perhaps use the WHM to get the latest WHM version, and clicked on 'Upgrade To Latest Version' and ended up with the installed screen running in circles, again and again and again, which now that I remember, it did this during installation too:
    Stop in /usr/ports/archivers.
    *** Error code 1

    Stop in /usr/ports.
    ===> Script "configure" failed unexpectedly.
    Please report the problem to sobomax@FreeBSD.org [maintainer] and
    attach
    the "/usr/ports/archivers/cabextract/work/cabextract-0.6/config.log"
    including the output of the failure of your make command. Also, it
    might
    be a good idea to provide an overview of all packages installed on
    your
    system (e.g. an `ls /var/db/pkg`).
    *** Error code 1

    Stop in /usr/ports/archivers/cabextract.
    *** Error code 1

    Stop in /usr/ports/archivers.
    *** Error code 1

    Stop in /usr/ports.
    ===> archivers
    ===> archivers/9e
    ===> Installing for 9e-1.0
    ===> 9e-1.0 is already installed - perhaps an older version?

    Then I decided to take a look at /var/log/messages:
    May 10 08:11:45 bugs /kernel: pid 65236 (rsync), uid 0: exited on signal 11 (core dumped)
    May 10 08:12:17 bugs /kernel: pid 74487 (rsync), uid 0: exited on signal 11 (core dumped)
    May 10 08:12:34 bugs /kernel: pid 79105 (rsync), uid 0: exited on signal 11 (core dumped)
    May 10 08:13:26 bugs /kernel: pid 93066 (rsync), uid 0: exited on signal 11 (core dumped)
    May 10 08:13:43 bugs /kernel: pid 97675 (rsync), uid 0: exited on signal 11 (core dumped)
    May 10 08:14:00 bugs /kernel: pid 2408 (rsync), uid 0: exited on signal 11 (core dumped)
    May 10 08:14:13 bugs /kernel: pid 6021 (rsync), uid 0: exited on signal 11 (core dumped)
    May 10 08:15:39 bugs /kernel: pid 10966 (rsync), uid 0: exited on signal 11 (core dumped)
    May 10 08:16:11 bugs /kernel: pid 20215 (rsync), uid 0: exited on signal 11 (core dumped)
    May 10 08:16:28 bugs /kernel: pid 24825 (rsync), uid 0: exited on signal 11 (core dumped)
    May 10 08:17:20 bugs /kernel: pid 38725 (rsync), uid 0: exited on signal 11 (core dumped)
    May 10 08:17:36 bugs /kernel: pid 43337 (rsync), uid 0: exited on signal 11 (core dumped)
    May 10 08:17:53 bugs /kernel: pid 47943 (rsync), uid 0: exited on signal 11 (core dumped)
    May 10 08:18:03 bugs /kernel: pid 51545 (rsync), uid 0: exited on signal 11 (core dumped)

    And that is just the short version.. I'd say there were well over 1000 lines of error messages all throughout the archivers port install attempts.

    Problem #3
    ==============
    Attempting to get this dns talking to the master DNS server, we established the trust - all seems well.. then:
    Rebuilding DNS Zones List from master server .....
    Scp failed!

    So I look, named isnt even running.. when I attempt to start named thru WHM it says:
    Waiting for bind to restart.... . . . . . . . . . . finished.
    Usage: named {start|stop} bind status bind did not return a status report
    bind started ok

    Ahh... but it really didnt start.. A quick check of /var/log/messages doesnt show any errors at all, NOR did it show any zones loading obviously.. its not running. Yes, I've seen the threads on this DNS issue in the forums here, but it does not fix our problem.


    Has anyone sucessfully installed this on FreeBSD? I've used FreeBSD for years and am more than comfortable from CLI but have reached a point that Im about to trash this and look for something else.

    D.
    =======
     
  2. howard

    howard Well-Known Member

    Joined:
    Apr 20, 2003
    Messages:
    233
    Likes Received:
    0
    Trophy Points:
    16
    not sure about the other problems however in problem #1 it looks like the trust relationship was not properly established what do the logs on the dnsmaster (i think thats where its ssh'ing to) say?
     
  3. djordan

    djordan Registered

    Joined:
    May 10, 2003
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    /var/log/messages on the Master DNS server is littered with this:

    May 10 08:21:15 ns1 sshd[52896]: fatal: msg_send: write
    May 10 08:23:00 ns1 sshd[52906]: fatal: msg_send: write
    May 10 08:23:00 ns1 sshd[52908]: fatal: msg_send: write
    May 10 08:23:20 ns1 sshd[52910]: fatal: msg_send: write
    May 10 08:23:20 ns1 sshd[52912]: fatal: msg_send: write
    May 10 08:23:30 ns1 sshd[52914]: fatal: msg_send: write

    When we created the master trust relationship originally from one of the customer/client machines per Cpanel tech support, it DID say it created the trust and that the PGP key was generated, etc etc.
     

Share This Page