mssql Error: 17113, Severity: 16, State: 1. Error 5 (Access Denied)

[christiaan-bronkhorst]

Hi all,

I have been running a couple of sql-server in kubernetes for over a year now and never had this issue. This specific sql-server instance has been running for over 4 months without any issues, today it suddenly crashed and received this error:

We do however use hostpath storage where the host is using ISCSI & multipathing to our SAN. I've checked the host where the pod was running and it did not lose connection to the SAN whatsoever.

Here is the paths to the SAN:
3600c0ff00065d27e5363ea6301000000 dm-3 HPE,MSA 2050 SAN
size=742G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| |- 8:0:0:1 sdq 65:0 active ready running
| |- 1:0:0:1 sdl 8:176 active ready running
| |- 2:0:0:1 sdn 8:208 active ready running
| - 5:0:0:1 sdp 8:240 active ready running -+- policy='service-time 0' prio=10 status=enabled
|- 6:0:0:1 sdk 8:160 active ready running
|- 3:0:0:1 sdj 8:144 active ready running
|- 4:0:0:1 sdm 8:192 active ready running
`- 7:0:0:1 sdo 8:224 active ready running

I have three other sql-server instances that also make use of this same LUN. They are still healthy and running strong.

I investigated the file permissions and ACL's and nothing changed...

See below my security context and image tag used:
securityContext:
runAsUser: 10001
runAsGroup: 0
fsGroup: 0
hostname: sql-server
containers:
- image: mcr.microsoft.com/mssql/server:2019-latest
name: sql-server

SOLUTION:

After restarting the deployment the sql-server was healthy again...