Unix Technical Forum

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

This is a discussion on BUG #4081: Running Postgres as Windows service vs regular applications within the pgsql Bugs forums, part of the PostgreSQL category; --> The following bug has been logged online: Bug reference: 4081 Logged by: Pavel Alexei Email address: pa@msys.md PostgreSQL version: ...


Go Back   Unix Technical Forum > Database Server Software > PostgreSQL > pgsql Bugs

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 04-10-2008, 11:15 AM
Pavel Alexei
 
Posts: n/a
Default BUG #4081: Running Postgres as Windows service vs regular applications


The following bug has been logged online:

Bug reference: 4081
Logged by: Pavel Alexei
Email address: pa@msys.md
PostgreSQL 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 port=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 port=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 port=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 port=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 port=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 port=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 port=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 port=13687
2008-04-01 16:43:12 lua lua authenticationLOG: connection authorized:
user=lua database=lua

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

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 02:44 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com