Secondary Site Server Still Pending

Hi all!
 
I have installed a secondary site server from our primary.  Looking on the secondary, it has correctly installed to C:\Program Files (x86)\Microsoft Configuration Manager, however it is still showing up as pending.
 
What log files should I start looking at to troubleshoot this issue?
 
--------------------------------------------------------------
Edit:
In the despool.log on the secondary shows this-
 
Hman.box\Pubkey Inbox not defined yet.
Waiting for the inbox manager to create the inboxes, retry in 10 seconds.
CPublicKeyLookup::Initialize("C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\hman.box\pubkey")
CPublicKeyLookup::Initialize()  Initializing the Public Key Store Path to C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\hman.box\pubkey
Waiting for ready instruction file....
Waiting for ready instruction file....
Waiting for ready instruction file....
 
Since I did it yesterday, it keeps adding 'Waiting for ready instruction file'' to the log every 5 minutes
-------------------------------------------------------------- 

Many thanks!
SCCM Noob

What exactly is showing up as "pending"?

Not sure if this will help in your situation, but we typically do our Secondary Sites from media on the Secondary site server and have had something "sort of" like this happen on many Secondary Site Rebuilds, where the new 2ndary site doesn't show up in the console after a reinstall and all looks good on the new 2ndary.  You might be able to try either of the two following steps, the #2 always seems to work for us.
 
1)  On the child site run <SMS Drive>: SMS\bin\i386\00000409\PREINST.EXE /KEYFORPARENT and place the generated file onto the parents <SMS Drive>:\SMS\inboxes\hman.box and monitor the hman.log on the parent site for information as to whether this has completed successfully
2)  (Use with CAUTION) Copy the site control file from the secondary site to a local folder and rename it to SITECRTL.CT2. Place the renamed file in the HMAN.BOX of the parent site and monitor the HMAN.LOG for entries pertaining to the new
secondary site. Refresh the console and you should see the new site. Keep in mind that this procedure does not correct any communications issues