After a system failure caused by hard reboot, disk full (file system) etc that does not involve a database restart, post may be in INTERNAL OPERATION state without moving at all.
This is caused by previous shareplex user sessions in the database holding exclussive locks on shareplex_trans table. Subsequent efforts by post to recover or progress by updating this table is put on hold by the previous locks held by this same user id.
First, stop post. Kill all shareplex user connection to the database, ensure that the locks are released before starting post again.
This may involve shutting down shareplex force if post is in 'stopping' for a very long time.
Do not truncate shareplex_trans