You encounter the following output from 'status' in sp_ctrl with corresponding entries in the event_log file as below:
sp_ctrl> status
Process Source Target State PID
---------- ------------------------ ------------ -------------------- ------
Capture o.PRPVG01 Running 25425
Read o.PRPVG01 Running 25428
Import x4100b x4100a Stopped - disk is full
Post o.PRPVG02-x4100b o.PRPVG01 Stopping 25427
Export x4100a x4100b Running 2560
sp_ctrl> show log reverse
02/19/20 17:46 Process exited sp_ocap (for o.PRPVG01) [pid = 25425] - exit(0)
02/19/20 17:46 Notice: shutting down by request [sp_ocap/25425]
02/19/20 17:46 Disk is full /nfs/prvg_vardir/vardir2200/rim
02/19/20 17:46 Process exited sp_mport (from x4100b.i.abc.com queue x4100b) [pid = 2559] - exit(0)
02/19/20 17:46 Disk is full /nfs/prvg_vardir/vardir2200/rim
02/19/20 17:46 Disk is full /nfs/prvg_vardir/vardir2200/rim
02/19/20 17:46 Disk is full /nfs/prvg_vardir/vardir2200/rim
02/19/20 17:45 Warning: sp_opst didn't shutdown [sp_cop/25178]
Check the available disk space in vardir using "df -k" or any equivalent Unix command and find that it is not yet 100% full.
And in certain situations, it may be well below 100%.