Menu

mount call failed: permission denied

Lucas
2013-06-04
2013-07-27
  • Lucas

    Lucas - 2013-06-04

    I keep getting a "mount call failed permission denied" error when my client contacts the server. Why does this happen and how do I fix it?

     
  • Lucas

    Lucas - 2013-07-05

    Those don't seem to be the same problem as mine. Could this be happening because my nodes are not matching up with the client's IP address? The drbl setup program setup my nodes as 192.168.0.XXX but I'm not using the DRBL DHCP. I have my existing DHCP server direct the clients to the correct place. They have IP addresses of 192.168.1.XXX. I assume these need to matchup?

    How can I reset my node directories to have the correct name?

     
  • Steven Shiau

    Steven Shiau - 2013-07-07

    OK, so you have another DHCP service. You should check the DHCP server's config on DRBL server, like /etc/dhcp/dhcpd.conf, and migrate the setting to your existing DHCP service. Otherwise different network won't work.

    Steven.

     
  • Lucas

    Lucas - 2013-07-09

    Steven, I don't know how I'd do that. I think I need to change the subnet on the DRBL DHCP config. Here is my existing DHCP config:

    ~~~~~
    option domain-name "domain.com";
    option ldap-server code 95 = text;
    option domain-search-list code 119 = text;

    default-lease-time 7200;
    max-lease-time 86400;
    log-facility local7;
    ddns-update-style none;
    one-lease-per-client true;
    deny duplicates;
    ping-check true;
    authoritative;
    subnet 192.168.0.0 netmask 255.255.252.0 {
    pool {
    range 192.168.1.10 192.168.1.99;
    }
    option routers 192.168.1.1;
    next-server 192.168.1.184;
    option domain-name-servers 192.168.1.188,192.168.1.189,192.168.1.180;
    option netbios-name-servers 192.168.1.188;
    option netbios-node-type 8;
    option ntp-servers 192.168.1.188;
    if substring(hardware, 1, 3) = 00:04:13 {
    # for snom phones (adapt to your needs - HTTP hostnames should also work)
    option tftp-server-name "192.168.1.190";
    } else {
    # for PXE booting...
    option tftp-server-name "192.168.1.184";
    server-name drbl;
    filename "pxelinux.0";
    }

    And here is my DRBL server DHCP config:
    

    default-lease-time 300;
    max-lease-time 300;
    option subnet-mask 255.255.255.0;
    option domain-name-servers 192.168.1.188,192.168.1.189,192.168.1.180,192.168.1.186;
    option domain-name "domain.com";
    ddns-update-style none;
    server-name drbl;
    filename = "pxelinux.0";
    class "DRBL-Client" {
    match if
    (substring(option vendor-class-identifier, 0, 9) = "PXEClient") or
    (substring(option vendor-class-identifier, 0, 9) = "Etherboot") or
    (substring(option vendor-class-identifier, 0, 10) = "DRBLClient") ;
    }
    subnet 192.168.0.0 netmask 255.255.255.0 {
    option subnet-mask 255.255.255.0;
    option routers 192.168.1.1;
    next-server 192.168.1.184;
    pool {
    # allow members of "DRBL-Client";
    range 192.168.0.1 192.168.0.20;
    }
    }
    ~~~~~~

    Can you please help me combine them?

     
  • Lucas

    Lucas - 2013-07-12

    Please help. I'm unsure how to merge to make this work.

     
  • Steven Shiau

    Steven Shiau - 2013-07-27

    So have you finished your merging? If not, which config file you want to use for the main DHCP server?
    The easiest way is to have different subnets, e.g.

    subnet 192.168.1.0 netmask 255.255.255.0 {
    option subnet-mask 255.255.255.0;
    option routers 192.168.1.182;
    next-server 192.168.1.182;

    pool {
      # allow members of "DRBL-Client";
      range 192.168.1.1 192.168.1.3;
    }
    

    }

    subnet 192.168.120.0 netmask 255.255.255.0 {
    option subnet-mask 255.255.255.0;
    option routers 192.168.120.254;
    next-server 192.168.120.254;

    pool {
      # allow members of "DRBL-Client";
      range 192.168.120.1 192.168.120.3;
    }
    

    }

    You can google to find some more examples of dhcpd.conf, and consult the DHCP config manual (man dhcpd.conf), then you can make it.

    Steven.

     

Log in to post a comment.

MongoDB Logo MongoDB