Fwd: DHCP problem?

[Albano Serrano]

Hi

I am installing the beta version of Rocks 7 using VMware virtual
machines and I am having some problems.
After installation, I found that some services have not been properly
installed and that they were not active.
Namely, the DHCP and HTTP services were not configured.
I had to configure them manually.

Why did this happen?

At this stage I intend to install a compute node but the insert-ether
aborts when the node requests the IP address by DHCP.
It gives this error:

# insert-ethers
error - list index out of range
Traceback (most recent call last):
File "/opt/rocks/sbin/insert-ethers", line 1689, in <module>
app.run()
File "/opt/rocks/sbin/insert-ethers", line 1670, in run
self.insertor.run()
File "/opt/rocks/sbin/insert-ethers", line 1472, in run
self.listenDhcp(syslog_line)
File "/opt/rocks/sbin/insert-ethers", line 1328, in listenDhcp
if not self.discover(tokens[7], interface):
File "/opt/rocks/sbin/insert-ethers", line 1226, in discover
ipaddr = self.getnextIP(self.subnet)
File "/opt/rocks/sbin/insert-ethers", line 1149, in getnextIP
text = self.commands.command('report.nextip', args)
File "/opt/rocks/lib/python2.7/site-packages/rocks/commands/__init__.py",
line 1546, in command
o.runWrapper(name, args)
File "/opt/rocks/lib/python2.7/site-packages/rocks/commands/__init__.py",
line 1941, in runWrapper
self.run(self._params, self._args)
File "/opt/rocks/lib/python2.7/site-packages/rocks/commands/report/nextip/__init__.py",
line 114, in run
bcast_ip = rocks.ip.IPAddr(network_ip | rocks.ip.IPAddr(~mask_ip))
File "/opt/rocks/lib/python2.7/site-packages/rocks/ip.py", line 201,
in __invert__
return ~self.address()
File "/opt/rocks/lib/python2.7/site-packages/rocks/ip.py", line 183,
in address
(self.list[1] << 8) + self.list[0])
IndexError: list index out of range

It seems to be a DHCP service problem. How can I solve it?

Thank you very much.
Regards,

--
albano serrano

--
albano serrano

[Trevor Cooper]

Albano,

This is not normal and suggests a problem with the install of your frontend.

These services should have been configured in <post> install sections during install.

Before going too much further can you provide specifics on what you did to 'configure' DHCP and HTTPD?

Also, can you provide the attributes stored in your Rocks DB prefixed with "Kickstart" and "Info" using the following command...

# rocks list attr | egrep "^Kickstart|^Info" | sort

Trevor

[Philip Papadopoulos]

What rolls did you choose?

P

--
You received this message because you are subscribed to the Google Groups "rocks7-beta" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rocks7-beta+unsubscribe@googlegroups.com.
To post to this group, send email to rocks...@googlegroups.com.
Visit this group at https://groups.google.com/group/rocks7-beta.
To view this discussion on the web visit https://groups.google.com/d/msgid/rocks7-beta/b8a0a512-aa3b-4378-83e1-a3e0413a8df8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Albano Serrano]

Philip,

We chose the following rolls:

[root@search3 ~]# rocks list roll

NAME                     VERSION    ARCH   ENABLED

area51:                  7.0        x86_64 yes

base:                    7.0        x86_64 yes

CentOS:                  7.4.1708   x86_64 yes

core:                    7.0        x86_64 yes

ganglia:                 7.0        x86_64 yes

hpc:                     7.0        x86_64 yes

kernel:                  7.0        x86_64 yes

perl:                    7.0        x86_64 yes

python:                  7.0        x86_64 yes

serf:                    0.8.1      x86_64 yes

sge:                     7.0        x86_64 yes

Updates-CentOS-7.4.1708: 2017-09-25 x86_64 yes

zfs-linux:               0.7.1      x86_64 yes

Thank you and regards,

--

albano serrano

Sem vírus. www.avg.com

To view this discussion on the web visit https://groups.google.com/d/msgid/rocks7-beta/CAG7Zqt2gX3v3vC2g%2BTJSBQ9-Rg%2B6EXtiMLZRaO8BcMXH7WesrQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

albano serrano

[Albano Serrano]

Trevor,

Regarding the DHCP service, I had to configure /etc/dhcp/dhcpd.conf, since it was empty:

[root@search3 ~]# cat /etc/dhcp/dhcpd.conf

# dhcpd.conf

#

# Sample configuration file for ISC dhcpd

#

# A slightly different configuration for an internal subnet.

ddns-update-style none;

subnet 172.27.7.0 netmask 255.255.255.0 {

  option domain-name-servers 172.27.7.1;

  option domain-name "local";

  option routers 172.27.7.1;

  option broadcast-address 172.27.7.255;

  default-lease-time 600;

  max-lease-time 7200;

  group "local" {

                host search3-ens160 {

                        hardware ethernet 00:0c:29:04:68:f8;

                        option host-name "search3";

                        fixed-address 172.27.7.1;

                        filename "pxelinux.0";

                        next-server 172.27.7.1;

                }

 }

}

Regarding at the HTTPD, I just had to activate the service:

# service httpd start

The attributes stored in our Rocks DB are as follows:

# rocks list attr | egrep "^Kickstart|^Info" | sort

[root@search3 dhcp]# rocks list attr | egrep "^Kickstart|^Info" | sort
Info_CertificateCountry:           PT
Info_CertificateLocality:          Braga
Info_CertificateOrganization:      UMINHO
Info_CertificateState:             BRaga
Info_ClusterContact:               alb...@di.uminho.pt
Info_ClusterLatLong:               N41 W8
Info_ClusterName:                  SeARCH7
Info_ClusterURL:                   http://search3.di.uminho.pt
Info_GoogleOTPRoot:                yes
Info_GoogleOTPUsers:               yes
Kickstart_DistroDir:               /export/rocks
Kickstart_Keyboard:                us
Kickstart_Lang:                    en_US.UTF-8
Kickstart_Langsupport:             en_US.UTF-8
Kickstart_PrivateAddress:          172.27.7.1
Kickstart_PrivateDNSDomain:        local
Kickstart_PrivateDNSServers:       172.27.7.1
Kickstart_PrivateGateway:          172.27.7.1
Kickstart_PrivateHostname:         search3
Kickstart_PrivateInterface:        ens160
Kickstart_PrivateKickstartBasedir: install
Kickstart_PrivateKickstartCGI:     sbin/kickstart.cgi
Kickstart_PrivateKickstartHost:    172.27.7.1
Kickstart_PrivateMTU:              9000
Kickstart_PrivateNetmask:          24
Kickstart_PrivateNetmaskCIDR:      33
Kickstart_PrivateNetwork:          8
Kickstart_PrivateNTPHost:          search3.local
Kickstart_PrivateSyslogHost:       172.27.7.1
Kickstart_PublicAddress:           193.136.19.163
Kickstart_PublicDNSDomain:         di.uminho.pt
Kickstart_PublicDNSServers:        193.136.19.1
Kickstart_PublicFQDN:              search3.di.uminho.pt
Kickstart_PublicGateway:           193.136.19.254
Kickstart_PublicHostname:          search3
Kickstart_PublicInterface:         ens32
Kickstart_PublicKickstartHost:     central.rocksclusters.org
Kickstart_PublicMTU:               1500
Kickstart_PublicNetmask:           255.255.255.0
Kickstart_PublicNetwork:           193.136.19.0
Kickstart_PublicNTPHost:           pool.ntp.org
Kickstart_Timezone:                Europe/Lisbon

Tkank you and regards,

--

albano serrano

--

albano serrano

Sem vírus. www.avg.com

--

albano serrano

[Trevor Cooper]

Albano,

Two things...

First, if you don't reinstall your frontend (see below) you can generate the correct content for your dhcpd with...

# rocks report host dhcpd

If this command doesn't generate proper output it suggests a problem with your database (see below).

Second, your public hostname is listed as...

Kickstart_PublicHostname:          search3

...but should be...

Kickstart_PublicHostname:          search3.di.uminho.pt

You need to enter the full hostname when configuring your public network interface during initial frontend install.

Since this attribute is also used when generating your httpd server configuration it's likely it also may be related to your httpd server not starting up.

While you can update the attribute above with...

# rocks set host attr attr=Kickstart_PublicHostname value=search3.di.uminho.pt

...it might be better to reinstall your frontend being sure to specify the fully qualified hostname when configuring your public interface.

Hope this helps...

Trevor

To unsubscribe from this group and stop receiving emails from it, send an email to rocks7-beta...@googlegroups.com.

To post to this group, send email to rocks...@googlegroups.com.
Visit this group at https://groups.google.com/group/rocks7-beta.
To view this discussion on the web visit https://groups.google.com/d/msgid/rocks7-beta/b8a0a512-aa3b-4378-83e1-a3e0413a8df8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

albano serrano

Sem vírus. www.avg.com

--

albano serrano