Re: [BUGS] BUG #4768: FATAL:could not reattach to shared memory:487
Stopping and starting does not seem to fix the problem. I stopped and started my Windows server today. The problem reappeared the second time I launched my db update scripts. Cordialement, Ghislain ROUVIGNAC g...@sylob.com Editeur-Intégrateur de solutions ERP 7 rue Marcel Dassault - Z.A. La Mouline - 81990 Cambon d'Albi - FRANCE Tél : (+33) (0)5 63 53 08 18 - Fax : (+33) (0)5 63 53 07 42 - www.sylob.com Hot line : (+33) (0)5 63 53 78 35 - mailto:supp...@sylob.com Entreprise certifiée ISO 9001 version 2000 par le BVQI. -Message d'origine- De : Bruce Momjian [mailto:br...@momjian.us] Envoyé : mardi 21 avril 2009 16:53 À : Ghislain ROUVIGNAC Cc : pgsql-bugs@postgresql.org Objet : Re: [BUGS] BUG #4768: FATAL:could not reattach to shared memory:487 Ghislain ROUVIGNAC wrote: > I didn't tried to reboot the windows server. > I'll try it when i will have time. > > > Thank you for the references to the problem. OK, let us know if it does not fix the problem. As you can see this bug has been around for a while. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #4768: FATAL:could not reattach to shared memory:487
Thanks for your answer. Stoping/starting the server does not solve the problem. It reappears quickly. As a work around I still run my DB on Linux Red Hat with Postgres 8.1, but i would like to move to the new Windows 2008 server. How can I know when a fix will be released ? -Message d'origine- De : Bruce Momjian [mailto:br...@momjian.us] Envoyé : mardi 21 avril 2009 16:14 À : grouvi Cc : pgsql-bugs@postgresql.org Objet : Re: [BUGS] BUG #4768: FATAL:could not reattach to shared memory:487 This is a known problem. I think stoping/starting the server will fix it. We hope to find the cause soon. --- grouvi wrote: > > The following bug has been logged online: > > Bug reference: 4768 > Logged by: grouvi > Email address: g...@sylob.com > PostgreSQL version: 8.3.7 > Operating system: Windows 2008 x64 > Description:FATAL:could not reattach to shared memory:487 > Details: > > Symptoms: > My DB update scripts crashes with the following error message > FATAL: could not reattach to shared memory (key=288, addr=0202): 487 > The problem occurs with both autovacuum turned on or off. > > > Configuration: > -> PostgreSQL 8.3.7 > ->Windows 2008 64 bits. > It is a normal install. > I have no antivirus nor Firewall. > There is the Windows Firewall but the problem still occurs while it is > turned off. > > > > Thanks for help. > > > Here is my full postgresql.conf > > # - > # PostgreSQL configuration file > # - > # > # This file consists of lines of the form: > # > # name = value > # > # (The "=" is optional.) Whitespace may be used. Comments are introduced > with > # "#" anywhere on a line. The complete list of parameter names and allowed > # values can be found in the PostgreSQL documentation. > # > # The commented-out settings shown in this file represent the default > values. > # Re-commenting a setting is NOT sufficient to revert it to the default > value; > # you need to reload the server. > # > # This file is read on server startup and when the server receives a SIGHUP > # signal. If you edit the file on a running system, you have to SIGHUP the > # server for the changes to take effect, or use "pg_ctl reload". Some > # parameters, which are marked below, require a server shutdown and restart > to > # take effect. > # > # Any parameter can also be given as a command-line option to the server, > e.g., > # "postgres -c log_connections=on". Some paramters can be changed at run > time > # with the "SET" SQL command. > # > # Memory units: kB = kilobytes MB = megabytes GB = gigabytes > # Time units:ms = milliseconds s = seconds min = minutes h = hours d = > days > > > #--- > --- > # FILE LOCATIONS > #--- > --- > > # The default values of these variables are driven from the -D command-line > # option or PGDATA environment variable, represented here as ConfigDir. > > #data_directory = 'ConfigDir'# use data in another directory > # (change requires restart) > #hba_file = 'ConfigDir/pg_hba.conf'# host-based authentication file > # (change requires restart) > #ident_file = 'ConfigDir/pg_ident.conf'# ident configuration file > # (change requires restart) > > # If external_pid_file is not explicitly set, no extra PID file is written. > #external_pid_file = '(none)'# write an extra PID file > # (change requires restart) > > > #--- > --- > # CONNECTIONS AND AUTHENTICATION > #--- > --- > > # - Connection Settings - > > listen_addresses = '*'# what IP address(es) to listen on; > # comma-separated list of addresses; > # defaults to 'localhost', '*' = all > # (change requires restart) > port = 5432# (change requires restart) > max_connections = 200# 200 pour éviter des "too many clients already" > # Note: Increasing max_connections costs ~400 bytes of shared memory per > # connection slot, plus lock space (see max_locks_per_transaction). You > might > # also need to raise shared_buffers to
Re: [BUGS] BUG #4768: FATAL:could not reattach to shared memory:487
Ghislain ROUVIGNAC wrote: > I didn't tried to reboot the windows server. > I'll try it when i will have time. > > > Thank you for the references to the problem. OK, let us know if it does not fix the problem. As you can see this bug has been around for a while. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #4768: FATAL:could not reattach to shared memory:487
Bruce Momjian wrote: > Ghislain ROUVIGNAC wrote: > > Thanks for your answer. > > > > > > Stoping/starting the server does not solve the problem. > > It reappears quickly. > > > > As a work around I still run my DB on Linux Red Hat with Postgres 8.1, but i > > would like to move to the new Windows 2008 server. > > > > > > How can I know when a fix will be released ? > > Uh, have you tried rebooting the server? Here is our TODO item: > > Diagnose problem where shared memory can sometimes not be attached by > postmaster children > > * FATAL: could not reattach to shared memory (Win32) Oh, sorry, here is the URL describing the problem: http://archives.postgresql.org/pgsql-general/2007-08/msg01377.php -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #4768: FATAL:could not reattach to shared memory:487
Ghislain ROUVIGNAC wrote: > Thanks for your answer. > > > Stoping/starting the server does not solve the problem. > It reappears quickly. > > As a work around I still run my DB on Linux Red Hat with Postgres 8.1, but i > would like to move to the new Windows 2008 server. > > > How can I know when a fix will be released ? Uh, have you tried rebooting the server? Here is our TODO item: Diagnose problem where shared memory can sometimes not be attached by postmaster children * FATAL: could not reattach to shared memory (Win32) -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #4768: FATAL:could not reattach to shared memory:487
This is a known problem. I think stoping/starting the server will fix it. We hope to find the cause soon. --- grouvi wrote: > > The following bug has been logged online: > > Bug reference: 4768 > Logged by: grouvi > Email address: g...@sylob.com > PostgreSQL version: 8.3.7 > Operating system: Windows 2008 x64 > Description:FATAL:could not reattach to shared memory:487 > Details: > > Symptoms: > My DB update scripts crashes with the following error message > FATAL: could not reattach to shared memory (key=288, addr=0202): 487 > The problem occurs with both autovacuum turned on or off. > > > Configuration: > -> PostgreSQL 8.3.7 > ->Windows 2008 64 bits. > It is a normal install. > I have no antivirus nor Firewall. > There is the Windows Firewall but the problem still occurs while it is > turned off. > > > > Thanks for help. > > > Here is my full postgresql.conf > > # - > # PostgreSQL configuration file > # - > # > # This file consists of lines of the form: > # > # name = value > # > # (The "=" is optional.) Whitespace may be used. Comments are introduced > with > # "#" anywhere on a line. The complete list of parameter names and allowed > # values can be found in the PostgreSQL documentation. > # > # The commented-out settings shown in this file represent the default > values. > # Re-commenting a setting is NOT sufficient to revert it to the default > value; > # you need to reload the server. > # > # This file is read on server startup and when the server receives a SIGHUP > # signal. If you edit the file on a running system, you have to SIGHUP the > # server for the changes to take effect, or use "pg_ctl reload". Some > # parameters, which are marked below, require a server shutdown and restart > to > # take effect. > # > # Any parameter can also be given as a command-line option to the server, > e.g., > # "postgres -c log_connections=on". Some paramters can be changed at run > time > # with the "SET" SQL command. > # > # Memory units: kB = kilobytes MB = megabytes GB = gigabytes > # Time units:ms = milliseconds s = seconds min = minutes h = hours d = > days > > > #--- > --- > # FILE LOCATIONS > #--- > --- > > # The default values of these variables are driven from the -D command-line > # option or PGDATA environment variable, represented here as ConfigDir. > > #data_directory = 'ConfigDir'# use data in another directory > # (change requires restart) > #hba_file = 'ConfigDir/pg_hba.conf'# host-based authentication file > # (change requires restart) > #ident_file = 'ConfigDir/pg_ident.conf'# ident configuration file > # (change requires restart) > > # If external_pid_file is not explicitly set, no extra PID file is written. > #external_pid_file = '(none)'# write an extra PID file > # (change requires restart) > > > #--- > --- > # CONNECTIONS AND AUTHENTICATION > #--- > --- > > # - Connection Settings - > > listen_addresses = '*'# what IP address(es) to listen on; > # comma-separated list of addresses; > # defaults to 'localhost', '*' = all > # (change requires restart) > port = 5432# (change requires restart) > max_connections = 200# 200 pour ??viter des "too many clients already" > # Note: Increasing max_connections costs ~400 bytes of shared memory per > # connection slot, plus lock space (see max_locks_per_transaction). You > might > # also need to raise shared_buffers to support more connections. > #superuser_reserved_connections = 3# (change requires restart) > #unix_socket_directory = ''# (change requires restart) > #unix_socket_group = ''# (change requires restart) > #unix_socket_permissions = 0777# begin with 0 to use octal notation > # (change requires restart) > #bonjour_name = ''# defaults to the computer name > # (change requires restart) > > # - Security and Authentication - > > #authentication_timeout = 1min# 1s-600s > #ssl = off# (change requires restart) > #ssl_ciphers = 'ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH'# allowed SSL ciphers > # (change requires restart) > #password_encryption = on > #db_user_namespace = off > > # Kerberos and GSSAPI > #krb_server_keyfile = ''# (change requires restart) > #krb_srvname = 'postgres'# (change requires restart, Kerberos only) > #krb_server_ho
[BUGS] BUG #4768: FATAL:could not reattach to shared memory:487
The following bug has been logged online: Bug reference: 4768 Logged by: grouvi Email address: g...@sylob.com PostgreSQL version: 8.3.7 Operating system: Windows 2008 x64 Description:FATAL:could not reattach to shared memory:487 Details: Symptoms: My DB update scripts crashes with the following error message FATAL: could not reattach to shared memory (key=288, addr=0202): 487 The problem occurs with both autovacuum turned on or off. Configuration: -> PostgreSQL 8.3.7 ->Windows 2008 64 bits. It is a normal install. I have no antivirus nor Firewall. There is the Windows Firewall but the problem still occurs while it is turned off. Thanks for help. Here is my full postgresql.conf # - # PostgreSQL configuration file # - # # This file consists of lines of the form: # # name = value # # (The "=" is optional.) Whitespace may be used. Comments are introduced with # "#" anywhere on a line. The complete list of parameter names and allowed # values can be found in the PostgreSQL documentation. # # The commented-out settings shown in this file represent the default values. # Re-commenting a setting is NOT sufficient to revert it to the default value; # you need to reload the server. # # This file is read on server startup and when the server receives a SIGHUP # signal. If you edit the file on a running system, you have to SIGHUP the # server for the changes to take effect, or use "pg_ctl reload". Some # parameters, which are marked below, require a server shutdown and restart to # take effect. # # Any parameter can also be given as a command-line option to the server, e.g., # "postgres -c log_connections=on". Some paramters can be changed at run time # with the "SET" SQL command. # # Memory units: kB = kilobytes MB = megabytes GB = gigabytes # Time units:ms = milliseconds s = seconds min = minutes h = hours d = days #--- --- # FILE LOCATIONS #--- --- # The default values of these variables are driven from the -D command-line # option or PGDATA environment variable, represented here as ConfigDir. #data_directory = 'ConfigDir'# use data in another directory # (change requires restart) #hba_file = 'ConfigDir/pg_hba.conf'# host-based authentication file # (change requires restart) #ident_file = 'ConfigDir/pg_ident.conf'# ident configuration file # (change requires restart) # If external_pid_file is not explicitly set, no extra PID file is written. #external_pid_file = '(none)'# write an extra PID file # (change requires restart) #--- --- # CONNECTIONS AND AUTHENTICATION #--- --- # - Connection Settings - listen_addresses = '*'# what IP address(es) to listen on; # comma-separated list of addresses; # defaults to 'localhost', '*' = all # (change requires restart) port = 5432# (change requires restart) max_connections = 200# 200 pour éviter des "too many clients already" # Note: Increasing max_connections costs ~400 bytes of shared memory per # connection slot, plus lock space (see max_locks_per_transaction). You might # also need to raise shared_buffers to support more connections. #superuser_reserved_connections = 3# (change requires restart) #unix_socket_directory = ''# (change requires restart) #unix_socket_group = ''# (change requires restart) #unix_socket_permissions = 0777# begin with 0 to use octal notation # (change requires restart) #bonjour_name = ''# defaults to the computer name # (change requires restart) # - Security and Authentication - #authentication_timeout = 1min# 1s-600s #ssl = off# (change requires restart) #ssl_ciphers = 'ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH'# allowed SSL ciphers # (change requires restart) #password_encryption = on #db_user_namespace = off # Kerberos and GSSAPI #krb_server_keyfile = ''# (change requires restart) #krb_srvname = 'postgres'# (change requires restart, Kerberos only) #krb_server_hostname = ''# empty string matches any keytab entry # (change requires restart, Kerberos only) #krb_caseins_users = off# (change requires restart) #krb_realm = '' # (change requires restart) # - TCP Keepalives - # see "man 7 tcp" for details #tcp_keepalives_idle = 0# TCP_KEEPIDLE, in seconds; # 0 selects the system default #tcp_keepalives_interval = 0# TCP_KEEPINTVL
