1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
This has been solved.
Turns out that there was a script that on startup changed the default gateway to that of the loadbalancer for some reason. This meant that even a simple ping to 1.1.1.1 or 8.8.8.8 would return zero packets.
route -v was able to display this to me.
It was then a case of establishing which of the start up script had been altered to do this and commenting out the changes to the network configuration and then rebooting a checking ping/routing table to see if the network issues were resolved.
Then it was a simple case of attaching an EIP to each host and upgrading via YUM.
répondu il y a 4 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a 3 mois
- AWS OFFICIELA mis à jour il y a 2 ans