Hi Mwalimu
The first thing to check would be disk space, although Portal should include specific errors/warnings in the logs when this is becoming a problem.
I came across the 218010 error code last week, which in that instance turned out to be caused by corrupt indexes preventing the indexing service (and consequently Portal itself) from starting properly. While the indexing service javaw.exe process was visible in task manager, the Portal java.exe process wasn't running; do you see at least two Java processes?
Also, do you also see this warning coming up repeatedly in the portal logs?
<Msg time="2019-07-24T17:38:19,196" type="WARNING" code="218014" source="Portal" process="9980" thread="1" methodName="" machine="portal.domain.com" user="" elapsed="">Starting Index Service.</Msg>
Assuming this looks like your issue and you can login to the Portal Administrator Directory then you could try reindexing your portal by going to system > indexer > reindex with Mode=Full. If you can't access the administrator directory (I couldn't with my issue last week) then try the following:
- Stop the Portal service
- Backup your Portal index folder - e.g. C:\arcgisportal\index
- Replace the content of C:\arcgisportal\index\nodes\0\indices with content of C:\Program Files\ArcGIS\Portal\framework\template\empty_index.zip
- Start Portal service
- Recreate indexes by running https://portal.domain.com/arcgis/portaladmin/system/indexer/reindex with Mode=Full
Note that I didn't see anything in the service-error-0.log, so while there might be similar contributing factors, this doesn't look like it's exactly the same issue.
Hope this helps.
Craig