Don't know why this so often happens, but it does. I'll look for hours for a solution to a problem, finally give up and ask for help, and then find a solution. I just solved my problem. I started looking at permissions on the database location folders. Saw that NETWORK SERVICE had full security permissions for the 9.3 folder in the path "D:\mysoftware\PostgreSQL\9.3" and also had full permissions to folders underneath 9.3. It had no permissions for the PostgreSQL folder. For grins I added it to the security settings for the the PostgreSQL folder and gave it full permissions. After doing that starting Postgres as a Windows service is working again. No idea if those permissions were previously on the PostgreSQL folder and somehow disappeared, but adding the permissions fixed the problem. Lisa On 1/26/2021 6:19 PM, Lisa Ruby wrote: > I am using Postgres 9.3 on a Windows 8.1 computer. I've been using it > for over 5 years on the same computer to provide a database for a local > JIRA Server. I did a normal restart of my computer last night and ever > since then the Postgres service fails to start. I am able to start > Postgres from the command line using pg_ctl start -D <path to database> > -w, and JIRA is then able to connect to the database. > > When I try (or the system tries) to start the Postgres Service from > Windows Services the event log shows this error for Postgres: > > 2021-01-25 23:37:36 PST FATAL: data directory > "D:/mysoftware/PostgreSQL/9.3" does not exist > > The database does exist in this data directory, and I use the same exact > path for it when starting Postgres from the command line. This error > started appearing when Postgres stopped correctly starting as a service. > > There are no other errors/warnings in the Event log that aren't always > there. > > The latest entries in the postgresql log look like this: > > 2021-01-26 17:21:05 PST LOG: database system was shut down at > 2021-01-26 17:20:31 PST > 2021-01-26 17:21:05 PST LOG: MultiXact member wraparound protections > are now enabled > 2021-01-26 17:21:05 PST LOG: database system is ready to accept connections > 2021-01-26 17:21:05 PST LOG: autovacuum launcher started > 2021-01-26 17:25:05 PST LOG: server process (PID 2372) was terminated > by exception 0xC000013A > 2021-01-26 17:25:05 PST DETAIL: Failed process was running: UPDATE > public.clusteredjob SET VERSION = $1 , NEXT_RUN = $2 WHERE JOB_ID=$3 > AND VERSION=$4 > 2021-01-26 17:25:05 PST HINT: See C include file "ntstatus.h" for a > description of the hexadecimal value. > 2021-01-26 17:25:05 PST LOG: terminating any other active server processes > 2021-01-26 17:25:05 PST WARNING: terminating connection because of > crash of another server process > 2021-01-26 17:25:05 PST DETAIL: The postmaster has commanded this > server process to roll back the current transaction and exit, because > another server process exited abnormally and possibly corrupted shared > memory. > 2021-01-26 17:25:05 PST HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2021-01-26 17:25:05 PST WARNING: terminating connection because of > crash of another server process > 2021-01-26 17:25:05 PST DETAIL: The postmaster has commanded this > server process to roll back the current transaction and exit, because > another server process exited abnormally and possibly corrupted shared > memory. > 2021-01-26 17:25:05 PST HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2021-01-26 17:25:05 PST WARNING: terminating connection because of > crash of another server process > 2021-01-26 17:25:05 PST DETAIL: The postmaster has commanded this > server process to roll back the current transaction and exit, because > another server process exited abnormally and possibly corrupted shared > memory. > 2021-01-26 17:25:05 PST HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2021-01-26 17:25:05 PST WARNING: terminating connection because of > crash of another server process > 2021-01-26 17:25:05 PST DETAIL: The postmaster has commanded this > server process to roll back the current transaction and exit, because > another server process exited abnormally and possibly corrupted shared > memory. > 2021-01-26 17:25:05 PST HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2021-01-26 17:25:05 PST WARNING: terminating connection because of > crash of another server process > 2021-01-26 17:25:05 PST DETAIL: The postmaster has commanded this > server process to roll back the current transaction and exit, because > another server process exited abnormally and possibly corrupted shared > memory. > 2021-01-26 17:25:05 PST HINT: In a moment you should be able to > reconnect to the database and repeat your command. > 2021-01-26 17:25:05 PST LOG: all server processes terminated; > reinitializing > 2021-01-26 17:25:05 PST LOG: database system was interrupted; last > known up at 2021-01-26 17:21:05 PST > 2021-01-26 17:25:07 PST LOG: startup process (PID 5376) was terminated > by exception 0xC000013A > 2021-01-26 17:25:07 PST HINT: See C include file "ntstatus.h" for a > description of the hexadecimal value. > 2021-01-26 17:25:07 PST LOG: aborting startup due to startup process > failure > > Can anyone help me fix this so that Postgres will again start as a > Windows service like it has been for the last 5 years, until last night? > > Thank you. > > Lisa > > >
