Closed bazinski closed 8 years ago
after rebooting grid-se2 to be able to get in, it would seem that it is locked off from the 172.20.100 network
it can see neither grid-xrootd02 (its data store) nor other machines on the 172.20.100 network, yet it thinks its 172.20.100. network is up
dmesg says : igb 0000:07:00.0: added PHC on eth2 igb 0000:07:00.0: eth2: (PCIe:5.0Gb/s:Width x2) b8:ca:3a:6c:5d:44 igb 0000:07:00.0: eth2: PBA No: G61346-000 ADDRCONF(NETDEV_UP): eth2: link is not ready
so either, cable was pulled out, cable is broken, or port is broken. This will require someone on site to take a look
so lets attempt to route all traffic over the public interface
it appears that eos hardcodes the ip ? it wont boot up the fst's fs boot grid-xrootd02.chpc.ac.za:/data/1 returns error
well this is not ideal :
xrootd: page allocation failure. order:1, mode:0x20 Pid: 19484, comm: xrootd Not tainted 2.6.32-504.23.4.el6.x86_64 Call Trace:
ip's are back to internal the rerouting of traffic is problematic. internal connection to grid-se2 is in urgent need of fixing.
network cable is loose and its clippy thing is not great, cable re inserted. It was not completely out.
This just makes the network reconfig in # #21 all the more urgent
tests from alice central services are failing on ailce::za_chpc::eos