Closed derekbelrose closed 5 years ago
The shibd process has been dying in the test and demo environments. Adding RAM to the service has fixed this. It's possible that there just wasn't enough RAM. I will be adding URL requests to the log output to see if there's anything fish
Over the week, we've seen no instability with the Shibboleth container. It appears that it was a resource issue and it has been resolved.
The shibd process has been dying in the test and demo environments. Adding RAM to the service has fixed this. It's possible that there just wasn't enough RAM. I will be adding URL requests to the log output to see if there's anything fish