Forum Discussion

sking's avatar
sking
Novice I
4 years ago
Solved

Does anyone have any advice for stork pods that keep restarting

Does anyone have any advice for stork pods that keep restarting with: ``` Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference) panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x29aad38]``` I'm running storkctl Version: 2.7.0-2e5098a and k8s version 1.22.5

announcement
help
  • adani's avatar
    adani
    4 years ago
    Hello Scott, Pawan from our team is working with you and he will take forward this issue.

14 Replies

  • adani's avatar
    adani
    Novice I
    4 years ago
    Do you have the complete stork log ? We will need that to pin point what caused the nil exception.
  • sking's avatar
    sking
    Novice I
    4 years ago
    adani happy to send them. This is from one of the pods.
  • adani's avatar
    adani
    Novice I
    4 years ago
    Thanks for the logs! Can you also send me the output of ```kubectl get pvc -n test-csqs -oyaml```
  • adani's avatar
    adani
    Novice I
    4 years ago
    sking Thanks for providing this. Can you also share ```kubectl get applicationbackup -oyaml -n test-csqs``` once you trigger a backup from PX-Backup UI ?
  • adani's avatar
    adani
    Novice I
    4 years ago
    Also what version of PX-Backup are you using ?
  • sking's avatar
    sking
    Novice I
    4 years ago
    adani I upgraded stork to 2.11.0 from 2.9.0 in the storagecluster, and tried a backup. i'm not seeing seg faults this time.
  • sking's avatar
    sking
    Novice I
    4 years ago
    however, the backup still failed "snapshot timeout out after 5m0s"