Looks like exec podcupdate has about 5 possible reasons to return false. It should log the reason then return false.
So please try 'exec podcupdate' again, then immediately look at the log for the error.
Here is the most likely one:
LogPrintf("\n PODCUpdate::Failed to Sign CPID Signature. %s ",sError.c_str());
I believe that is happening when you dont have a CPID in the chain as of yet...
NOTE to all users: You will never need to manually run exec podcupdate under normal circumstances; this is just to force it if your machine was off for long periods of time.
As far as the waiting for confirm: Check the last block timestamp, its probably a lagging block.
** We just solved 33049; it probably confirmed
The transaction I sent myself is getting confrimations now. The error I'm getting is:
2018-03-05 04:06:47
PODCUpdate::Error: Insufficient funds.
But there is plenty of BBP in my wallet. Does it have to be under a certain wallet address? This is in production by the way.
UPDATE:
I think the issue might be the receiving address that is associated with my CPID doesn't have enough BBP in it. Trying again now.
UPDATE 2:
podcupdate returned true. I didn't know it was only using a certain receiving address. Thanks guys!