Re: shared_preload_libraries = $libdir/plugins/plugin_debugger.dll causes server not started

From: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Bui, Michelle P *EXTERN*" <michelle(dot)p(dot)bui(at)boeing(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: shared_preload_libraries = $libdir/plugins/plugin_debugger.dll causes server not started
Date: 2014-04-18 07:56:36
Message-ID: A737B7A37273E048B164557ADEF4A58B17CF1AF0@ntex2010i.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Michelle P Bui wrote:
>>> I tried re-starting the process (actually the service that runs the
>>> server), I got the message: “The operation could not be completed, access is denied”.

> When running in the foreground, I have the same problem when running postgres.exe with super user
> postgres. I don't think it is a permission problem. The service Postgresql-x64-9.3 is shown stopped.
>
>
> Server [localhost]:
> Database [postgres]:
> Port [5432]:
> Username [postgres]:
> psql: could not connect to server: Connection refused (0x0000274D/10061)
> Is the server running on host "localhost" (::1) and accepting
> TCP/IP connections on port 5432?
> could not connect to server: Connection refused (0x0000274D/10061)
> Is the server running on host "localhost" (127.0.0.1) and accepting
> TCP/IP connections on port 5432?
>
>
> When I commented out the above # shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' in
> the postgres.conf file, no problem!

The message from psql is not important - it just shows that the server isn't running.

The important thing would be to know the messages that the *server* emits
when you try to start it in the foreground. They should be either printed
to the console or written to the PostgreSQL log file.

Why are you certain that it is not a permission problem? Maybe the
"super user postgres" has no permission.

I guess that you have double-checked that the DLL is for the correct
PostgreSQL version and architecture.

One thing that you could do is using Procmon to find out what actually
happens during server start and where the error occurs.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Eric Jankowski 2014-04-18 14:01:44 database system was not properly shut down
Previous Message David G Johnston 2014-04-18 03:54:25 Re: Difference between fsync and open_sync