[LON-CAPA-admin] new access servers can't connect to msu

[Stuart Raeburn]

Hi,

>
> Any ideas on what to look at to fix this?
>

Evidently, the IP addresses associated with the hostnames:

loncapa.chem.binghamton.edu
loncapa2.chem.binghamton.edu

have been changed from what they were a year ago.

The following seven binghamton.edu IP addresses are currently  
permitted access to the LON-CAPA ports on the msu and msudemo domain  
LON-CAPA servers by network border rules managed by MSU IT Services.

128.226.130.122
128.226.130.15
128.226.130.232
128.226.130.233
128.226.130.234
128.226.130.9
128.226.136.56

Those IP addresses were included in the complete list of LON-CAPA  
nodes forwarded to MSU IT services on 1/6/2017.

Of those seven, reverse DNS for the following three returns: "not found"

128.226.130.122
128.226.130.15
128.226.130.9

so I am assuming two of those used to be assigned to:  
loncapa.chem.binghamton.edu and loncapa2.chem.binghamton.edu

which are now:

128.226.136.82 and 128.226.136.79 respectively.

If this change is to be permanent, then I will submit a request to MSU  
IT Services to adjust their network border firewall rules to remove:  
128.226.130.122, 128.226.130.15 and 128.226.130.9, and add:  
128.226.136.82 and 128.226.136.79.

MSU IT services requires at least 48 hours to update MSU network border rules.

For more information about these changes, specific to msu, see:

mail.lon-capa.org/pipermail/lon-capa-users/2017-January/005155.html
mail.lon-capa.org/pipermail/lon-capa-admin/2017-August/003277.html

My recommendation is for any domains planning to change IP addresses  
for their LON-CAPA nodes is to contact me (off-list) at least 48 hours  
prior to the change, so the new IP addresses can be sent to MSU IT  
Services.

Note: both the old IP addresses and the new IP addresses can co-exist  
in the MSU network border rules for a time. At a later time I would  
then submit a request to MSU IT Services for removal of the old IP  
addresses from the MSU network border rules.


Stuart Raeburn
LON-CAPA Academic Consortium


Quoting Bob Gonzales <rgonzal at binghamton.edu>:

> Hi,
>
> I've got 2 new access servers that can't connect to the msu domain. 
When I
> browse to the msu domain from 'Course Editor'  I get the message:
>
>               Directory temporarily not accessible.
>
> Entries from lonc.log for all msu servers are like these:
>
> Thu Jan 25 05:11:45 2018 (9177) [loncapa.msu.edu] [Thu Jan 25
05:11:42
> 2018: Connected to loncapa.msu.edu] <font color='red'>CRITICAL:
Failed to
> make a connection with lond.</font>
> Thu Jan 25 05:11:45 2018 (9177) [loncapa.msu.edu] [Thu Jan 25
05:11:42
> 2018: Connected to loncapa.msu.edu] <font color='blue'>WARNING:
Failing
> transaction sethost</font>
> Thu Jan 25 05:14:27 2018 (9177) [loncapa.msu.edu] [Thu Jan 25
05:11:42
> 2018: Connected to loncapa.msu.edu] <font color='red'>CRITICAL:
Failed to
> make a connection with lond.</font>
> Thu Jan 25 05:14:27 2018 (9177) [loncapa.msu.edu] [Thu Jan 25
05:11:42
> 2018: Connected to loncapa.msu.edu] <font color='blue'>WARNING:
Failing
> transaction sethost</font>
>
> The access servers are:
>
> loncapa.chem.binghamton.edu - acting as a load balancer
> loncapa2.chem.binghamton.edu - acting as a normal access server
>
> They are virtual machines that were cloned from my library server
virtual
> machine, loncapal1.chem.binghamton.edu.  They are running Centos 7.4
and I
> updated them from 2.11.1 to 2.11.2 after cloning.
>
> Both servers are able to connect to servers in other domains. They
seem to
> be running normally with the exception of getting resources from
msu.
>
> Any ideas on what to look at to fix this?
>
> Thanks,
> Bob Gonzales
> Chemistry Dept
> Binghamton University