AIOps - Installation failed due to Postgres fails to startup : could not link file "pg_wal/xlogtemp.29"to "pg_wal/00000000001" : Input/output error
Article ID: 233579
Updated On:
Products
Issue/Introduction
We are using HP Storonce 5200 model NAS and not the standard NFS storage.
The installation failed with below reports below errors:
...
[create] [ OK ] Deployment axaservices-readserver
[verify] [ ERROR ] Verification pods of Deployment axaservices-readserver: [Pending]
[verify] [ ERROR ] Pod axaservices-readserver-85b45d58f5-f2wbp Initialized: False -> containers with incomplete status: [readserver-init-postgresql readserver-init-amq readserver-init-jarvis-apis]
[verify] [ ERROR ] Pod axaservices-readserver-85b45d58f5-f2wbp Ready: False -> containers with unready status: [axaservices-readserver]
[verify] [ ERROR ] Pod axaservices-readserver-85b45d58f5-f2wbp ContainersReady: False -> containers with unready status: [axaservices-readserver]
[verify] [ ERROR ] Pod axaservices-readserver-85b45d58f5-f2wbp PodScheduled: True -> null
[verify] [ ERROR ] Pod of Deployment axaservices-readserver has failed to start in the given timeframe.
[ERROR] Installation failed
Environment
DX Platform 20.x, 21.x
Cause
Unsupported NAS provider
The startup of postgres creates system links so if the storage doesn't supported filesystem links it will affect postgres, the below message will be reported in the postgres log:
kubectl logs -n<namespace> <dxi-postgressql-pod>
could not link file "pg_wal/xlogtemp.29"to "pg_wal/00000000001" : Input/output error
Other references:
https://serverfault.com/questions/699966/fail-to-start-postgresql-when-used-with-vagrant
https://www.postgresql.org/message-id/CABUevEwA9TFdA9WHtbjotbpU-bsR=cLw8DD2m_FYY8Of2h3n0g@mail.gmail.com
Resolution
Solution: None
Workaround: You can try a hybrid solution : Use a NFS for Postgres only and use NAS only all other services (TAS, NASS, Metadata, etc)
Additional Information
Feedback
