Re: In Windows Server 2008 PostgreSQL8.3 service on Local Computer started and then stopped.

From: Rodriguez Fernando <rodriguez(at)ort(dot)edu(dot)uy>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: In Windows Server 2008 PostgreSQL8.3 service on Local Computer started and then stopped.
Date: 2011-09-07 11:50:46
Message-ID: 4E675A96.1040406@ort.edu.uy
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

El 06/09/2011 22:11, Jack_Wu escribió:
> Windows Task Manager: PostgreSQL8.3's status is stopped.
> In Services:PostgreSQL8.3's status is stopped.
> When I start this service manually in Services,it notes that The
> PostgreSQL8.3 service on Local Computer started and then stopped.Some
> services stop automatically if they are not in use by other services or
> programs.
>
> In Event viewer it shows PostgreSQL 8.3's Error that:
> 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:
>
> FATAL: no pg_hba.conf entry for host "::1", user "SYSTEM", database
> "postgres", SSL off.
>
> --
> View this message in context: http://postgresql.1045698.n5.nabble.com/In-Windows-Server-2008-PostgreSQL8-3-service-on-Local-Computer-started-and-then-stopped-tp4776719p4776719.html
> Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
>
Are you using ipv6?
::1 is localhost in ipv6
there isn't a line in pg_hba.conf (verify this file)
# IPv6 local connections:
host all all ::1/128 ident

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Josh Kupershmidt 2011-09-07 13:21:06 Re: [BUGS] documentation bug - behave of NEW a OLD in plpgsql's triggers
Previous Message Bruce Momjian 2011-09-07 02:54:39 Re: [BUGS] documentation bug - behave of NEW a OLD in plpgsql's triggers