Portal for ArcGIS 10.7 issue: internal portal database does not appear to be running or accepting connections

13081
26
07-28-2019 04:00 PM
MwalimuKaranja
New Contributor II

Hi! I was running Portal for ArcGIS on a Windows Server 2012 R2 server for a while until up to a week ago when it suddenly went down. The Portal for ArcGIS Windows Service shows that the service is running but it is not possible to access the portal site on port 7443. I took a look at some of the logs and this is what I got from the Portal logs in the arcgisportal folder:

Failed to start the portal. The observer's beforeStart() function returned a failure.

Also had a look at the logs in the C:\Program Files\ArcGIS\Portal\framework\service\logs folder and got the following in the service-0.log:

<Msg time="2019-07-28T18:13:49,381" type="SEVERE" code="218010" source="Portal Admin" process="1592" thread="1" methodName="" machine="" user="" elapsed="">The portal has been initialized and configured but is not accessible. The internal portal database does not appear to be running or accepting connections. Restart the portal machine or machines and if the problem persists, contact Esri technical support (U.S.) or your distributor (customers outside the U.S.).</Msg>

Got the following on the service-error-0.log:

Sun Jul 28 18:13:54.019 EAT 2019 java.lang.NullPointerException
Sun Jul 28 18:13:54.019 EAT 2019 at com.esri.arcgis.portal.observers.ConfigObserver.c(ConfigObserver.java:793)
Sun Jul 28 18:13:54.019 EAT 2019 at com.esri.arcgis.portal.observers.ConfigObserver.e(ConfigObserver.java:900)
Sun Jul 28 18:13:54.019 EAT 2019 at com.esri.arcgis.portal.observers.ConfigObserver.beforeStart(ConfigObserver.java:191)
Sun Jul 28 18:13:54.019 EAT 2019 at com.esri.arcgis.portal.impl.ObserverManager.beforeStart(ObserverManager.java:159)
Sun Jul 28 18:13:54.019 EAT 2019 at com.esri.arcgis.portal.impl.NodeAgent.start(NodeAgent.java:246)
Sun Jul 28 18:13:54.019 EAT 2019 at com.esri.arcgis.portal.impl.Main.start(Main.java:83)

Might anyone have an idea how to solve this issue. What might I be doing wrong?

0 Kudos
26 Replies
StephenKaranja
New Contributor III

Hi Russell,

We're also running ArcGIS Enterprise 10.8.1. I used the server.xml posted by Fred. After restarting the server machine (restarting just the Portal for ArcGIS service didn't work for me), the Portal for ArcGIS service started correctly, and I believe it modified the server.xml file (I determined this by looking at the file's modification time after startup). I would have posted the server.xml file from our server but I can't access it at the moment.

0 Kudos
RussellEgypt
New Contributor II

Hi Stephen,

Thank You, the file from Fred worked!

 

0 Kudos
DuongHB
New Contributor II

We faced the same issue with 10.6.1 (updated all security patches until Dec 2020). We followed all of your steps and it worked. Just change a bit at step 4, we needed to restart the machine since restart just Portal service seems not work.

Thanks for your guide!

0 Kudos
IhabHassan
Esri Contributor

for some reason I wasn't able to publish any hosted layer/table on my local Portal, reindexing fixed the issue.
Thanks Craig 

Regards
Ihab
CraigRussell
Esri Contributor

Hi Mwalimu

You've probably checked this already, but is there anything useful/notable in Windows Event Viewer when you restart the Portal service?

Craig

0 Kudos
MwalimuKaranja
New Contributor II

Hi Craig,

The Event Viewer has multiple Portal for ArcGIS information activities noted, that's all. A sample can be seen below:

Event Viewer log

0 Kudos
CraigRussell
Esri Contributor

Hi Mwalimu

Apologies, I missed your last reply.  Did you get this resolved?  If not then what are the Postgres errors in the Event Viewer?  These might be relevant considering your logs suggest a problem with the internal Portal database.


Regards

Craig

0 Kudos
subbaraoP
New Contributor

Dear Craig,

 

I am also facing the same issue. Could you please provide the work around. 

Regards

Venkat

0 Kudos
JonathanQuinn
Esri Frequent Contributor

If the postgres.exe processes aren't running on your machine, you'll need to investigate the Event Viewer to see why Postgres is failing to start. You can ignore the entries like "is server running" or "postmaster.pid can't be found".

deleted-user-WQSTY6mGb8c7
New Contributor III

We're having the same issue:  After stopping/starting the Portal for ArcGIS Windows service, not all java executables were started, the postgres.exe process is not running on the machine, and the portal (including the portaladmin endpoint) became unresponsive.  The java.exe process was started (I'm guessing this is the Windows service), but no javaw.exe processes.  Eventually the indexer javaw.exe process started (after a few minutes). 

The portal logs contained serveral instances of this error:

The portal has been initialized and configured but is not accessible. The internal portal database does not appear to be running or accepting connections. Restart the portal machine or machines and if the problem persists, contact Esri technical support (U.S.) ...

And the Windows Event Viewer had half a dozen PostgreSQL errors of two different variations...

1)

The description for Event ID 0 from source PostgreSQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

pg_ctl: PID file "E:/arcgisportal/db/postmaster.pid" does not exist

2)

The description for Event ID 0 from source PostgreSQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Is server running?

... both of which we've been told to ignore in the previous post.

The same conditions persisted after rebooting the machine.

As the local PostgreSQL db is installed as an Esri component of the portal and is software-managed without the usual PostgreSQL client applications, perhaps Esri could provide additional feedback on how to troubleshoot this issue.