Chase access w/ linux
Michael Butash
michael at butash.net
Tue Oct 23 19:49:12 MST 2012
I do get chromium getting cranky when my system depletes of memory,
usually it'll start hanging, I'll start getting various JS errors and
"Aww Snap's" with it flat out giving up. I'm assuming you've rebooted
at some point to clear memory or you've checked vmstat and htop for
memory usage?
Otherwise I've used chase's ebanking for someone prior and it worked
fine for me a few months back.
>>> Going to https://mfasa.chase.com/ in a browser gives me 1 line of cryptic
>>> diagnostic/monitoring text.
>> "Prod Core LPAR, cigp01b4a002 Auth2 Web"
>
> I get something similar. Different hex string, possibly.
>
Your's sounds server-side almost...
cigp01b4a002 sounds like a cryptic server name, "chase internet gateway,
prod cluster 01, building 4, app002" vm/lpar would be my guess.
If you're constantly trying the base site and being directed there, it
sounds like a load-balancer is sticking you to the same server based on
a source-ip, which is common for persistence. Kind of odd this happens
indefinitely, but you could be "stuck" to a bad server. Seems unlikely
though you're the only one to see that. Try to grab a different ip and
try then.
Load-balancing is kind of a cryptic art, sometimes the apps and the
hardware doing the balancing do strange things the more Layer 7 they get...
-mb
More information about the PLUG-discuss
mailing list