Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Bugs > BUG #4081: Runn...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 1 Topic 3671 of 3967
Post > Topic >>

BUG #4081: Running Postgres as Windows service vs regular applications

by pa@[EMAIL PROTECTED] ("Pavel Alexei") Apr 1, 2008 at 02:21 PM

The following bug has been logged online:

Bug reference:      4081
Logged by:          Pavel Alexei
Email address:      pa@[EMAIL PROTECTED]
 version: 8.2.7
Operating system:   Windows XP SP2
Description:        Running Postgres as Windows service vs regular
applications
Details: 

I faced with problem connecting to Postgres running as Windows service.
After installing I tried to connect using pgAdmin, but I’ve got errors
regarding troubles in connecting and found next errors in logfile:
>connection received: host=127.0.0.1 ****t=13683
>could not receive data from client: An operation was attempted on
something
that is not a socket.
>incomplete startup packet
I found through Google a lot of messages, several people had same problem.
But I didn’t find solution. The only advice was to launch Postgres as
simple application (pg_ctl.exe start instead runservice). It was worked
for
me too. But I decided to get understood problem. 
I tried to get more details and raised all logging parameters in
configuration file to debug5 (“client_min_messages”,
“log_min_messages”, “log_min_error_statement”), but after this
errors disappeared. I turned back all parameters and got same errors.
After
several experiments I got “right” target. If I put
“log_min_messages” to debug2 or higher (2-5) everything is ok. But is
enough to set this parameter to debug1 or lower and I’ve got same
problem.

Very strange thing to be coincidence. 

Logfile with log_min_messages = debug1
2008-04-01 16:42:24   LOG:  database system was shut down at 2008-04-01
16:42:23
2008-04-01 16:42:24   LOG:  checkpoint record is at 0/173E990
2008-04-01 16:42:24   LOG:  redo record is at 0/173E990; undo record is at
0/0; shutdown TRUE
2008-04-01 16:42:24   LOG:  next transaction ID: 0/24871; next OID: 25829
2008-04-01 16:42:24   LOG:  next MultiXactId: 1; next MultiXactOffset: 0
2008-04-01 16:42:24   LOG:  database system is ready
2008-04-01 16:42:24   DEBUG:  transaction ID wrap limit is 2147484171,
limited by database "postgres"
2008-04-01 16:42:33 [unknown] [unknown] LOG:  connection received:
host=127.0.0.1 ****t=13682
2008-04-01 16:42:33 postgres lua authenticationLOG:  connection
authorized:
user=lua database=postgres
2008-04-01 16:42:33 [unknown] [unknown] LOG:  connection received:
host=127.0.0.1 ****t=13683
2008-04-01 16:42:33 [unknown] [unknown] LOG:  could not receive data from
client: An operation was attempted on something that is not a socket.
2008-04-01 16:42:33 [unknown] [unknown] LOG:  incomplete startup packet
2008-04-01 16:42:35 [unknown] [unknown] LOG:  connection received:
host=127.0.0.1 ****t=13684
2008-04-01 16:42:35 lua lua authenticationLOG:  connection authorized:
user=lua database=lua
2008-04-01 16:42:50   LOG:  received fast shutdown request
2008-04-01 16:42:50   LOG:  aborting any active transactions
2008-04-01 16:42:50 lua lua idleFATAL:  terminating connection due to
administrator command
2008-04-01 16:42:50 postgres lua idleFATAL:  terminating connection due to
administrator command
2008-04-01 16:42:50 postgres lua idleLOG:  disconnection: session time:
0:00:17.081 user=lua database=postgres host=127.0.0.1 ****t=13682
2008-04-01 16:42:50 lua lua idleLOG:  disconnection: session time:
0:00:15.440 user=lua database=lua host=127.0.0.1 ****t=13684
2008-04-01 16:42:50   LOG:  shutting down
2008-04-01 16:42:50   LOG:  database system is shut down
2008-04-01 16:42:51   LOG:  logger shutting down

Logfile with log_min_messages = debug2
2008-04-01 16:42:52   LOG:  database system was shut down at 2008-04-01
16:42:50
2008-04-01 16:42:52   LOG:  checkpoint record is at 0/173E9E0
2008-04-01 16:42:52   LOG:  redo record is at 0/173E9E0; undo record is at
0/0; shutdown TRUE
2008-04-01 16:42:52   LOG:  next transaction ID: 0/24910; next OID: 25829
2008-04-01 16:42:52   LOG:  next MultiXactId: 1; next MultiXactOffset: 0
2008-04-01 16:42:52   LOG:  database system is ready
2008-04-01 16:42:52   DEBUG:  transaction ID wrap limit is 2147484171,
limited by database "postgres"
2008-04-01 16:43:11   DEBUG:  forked new backend, pid=6856 socket=1368
2008-04-01 16:43:12 [unknown] [unknown] LOG:  connection received:
host=127.0.0.1 ****t=13686
2008-04-01 16:43:12 postgres lua authenticationLOG:  connection
authorized:
user=lua database=postgres
2008-04-01 16:43:12   DEBUG:  forked new backend, pid=4464 socket=1380
2008-04-01 16:43:12 [unknown] [unknown] LOG:  connection received:
host=127.0.0.1 ****t=13687
2008-04-01 16:43:12 lua lua authenticationLOG:  connection authorized:
user=lua database=lua

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
 




 1 Posts in Topic:
BUG #4081: Running Postgres as Windows service vs regular applic
pa@[EMAIL PROTECTED] (&q  2008-04-01 14:21:31 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Thu Aug 21 22:45:51 CDT 2008.