- Le plus récent
- Le plus de votes
- La plupart des commentaires
Is it the same AMI on both - obviously the AMI ID won't be same (different regions) but the RHEL versions should match.
Also, check the kernel is at the same level on both, and that SELinux isn't enforcing on one and permissive on the other, the host-based firewall isn't blocking any ports, and it isn't something like being out of diskspace on one of them.
cat /etc/redhat-release
uname -a
sestatus
sudo firewall-cmd --list-all
df -h
df -i
java -version
mysql -V
Thanks a lot, Steve. It ended up being a memory issue. T2 micro in AP South does not seem to have 1 Gig allocated unlike North Virginia. I don't know why. I switched to T2 small in AP South and it fixed my issue. That is the reason the application was failing at different points each time.
Please see the images below.
North Virginia - Memory footprint. First command is Top
Ap South - Memory footprint. First command is Top
Contenus pertinents
- demandé il y a 7 jours
- demandé il y a 7 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 9 mois