There was no server log anywhere, there were no entries in the Event Viewer (under Application, Security or System) and I ensured the entire directory structure is set to Full Control for the user (and the user is in the local Administrators group)... Nothing other than the service its trying to start, and then it times out.
When I used 'pg_ctl start -D ..\Data -U postgres -l ..\Data\pg_log\pglog.log' I get a log file opened, and the "server starting" message in the CMD window, but nothing written to the window, and no active connection in the pgAdmin III window. When I perform a pg_ctl stop it shows "server stopped" but again nothing in the logs... When I do the pg_ctl start ..... I can see the postamster.pid file created, and it gets deleted when I do a pg_ctl stop, but I am still unable to connect to the database using pgAdmin: it never gets created when I start the service in the Service MMC. This is a proof of concept/capability research check only, so I don't care about the platform for the database at this point. If I can get it going on CentOS, that's fine... as long as I can connect to the database with OpenNMS to do my research, its all good. Thanks so far! Roger -- View this message in context: http://postgresql.1045698.n5.nabble.com/Postgres-service-won-t-start-doesn-t-log-any-errors-tp3218164p3286452.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
