[ADMIN] could not fork new process for connection: Cannot allocate memory
Hi, We are running v814 with 8 GB of RAM and 3.5 GB allocated to shared memory. It's never been a problem for us before. We ran into a situation yesterday where we received the message above. At that time our total available memory took a dive to 4GB and cached memory stayed around 4 GB. Soon after that some process ended and everything returned to normal. It alsted around 10 minutes. Too bad I didn't see the query or process at the time it was running. ~DjK _ Try the next generation of search with Windows Live Search today! http://imagine-windowslive.com/minisites/searchlaunch/?locale=en-us&source=hmtagline ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [ADMIN] Log statements that generate an error only ... ?
"Marc G. Fournier" <[EMAIL PROTECTED]> writes: > Is this possible? log_min_error_statement = error regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[ADMIN] Log statements that generate an error only ... ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is this possible? I'm trying to debug a recurring error in MAIA, where its trying to use 'rpad', but I can't find where ... if I turn on 'log_statement="all"', there is just way too much data to weed through, so ... - Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFPXjJ4QvfyHIvDvMRAjDyAJ45kPm/hr22pCU4y0GT3J4XHaM/QACcD21y 1ut7Dld3XrwDNmGipmi0f04= =7z1P -END PGP SIGNATURE- ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[ADMIN] InitDB problem on Win2K Server
Hi All, anyone knows what could be this error above? I'm kind of desperate. D:\PostgreSQL\Data>initdb -E UTF8 --locale=no-locale --auth=trust --username=postgres --pwprompt -D "d:\\postgresql\\data" The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale no-locale. fixing permissions on existing directory d:/postgresql/data ... ok creating directory d:/postgresql/data/global ... ok creating directory d:/postgresql/data/pg_xlog ... ok creating directory d:/postgresql/data/pg_xlog/archive_status ... ok creating directory d:/postgresql/data/pg_clog ... ok creating directory d:/postgresql/data/pg_subtrans ... ok creating directory d:/postgresql/data/pg_twophase ... ok creating directory d:/postgresql/data/pg_multixact/members ... ok creating directory d:/postgresql/data/pg_multixact/offsets ... ok creating directory d:/postgresql/data/base ... ok creating directory d:/postgresql/data/base/1 ... ok creating directory d:/postgresql/data/pg_tblspc ... ok selecting default max_connections ... 10 selecting default shared_buffers ... 50 creating configuration files ... ok creating template1 database in d:/postgresql/data/base/1 ... WARNING: could not query value for 'std' to identify Windows timezone: 2 WARNING: could not find a match for Windows timezone "Hora oficial do Brasil" FATAL: could not create shared memory segment: No such file or directory DETAIL: Failed system call was shmget(key=1, size=1327104, 03600). child process was terminated by signal 1 Thanks in advance.
Re: [ADMIN] FastCgi / PostgreSQL: FATAL: Ident authentication fai
Hello! Your problem is that you have the pg_hba.conf set to do an ident authentication if the connection comes from localhost - this is the default setting imho. Your password settings the in the settings.py won't work since your process will run under the Apache user, nobody or www-data usually. On connect postgresql will check the ident of this user and this fails. We use following setting to prevent this: - connect not on localhost but on the external IP - set up pg_hba.conf to use say MD5 for connections on the external IP The difference between a FastCGI environment and your other tests is the environment. With psql your in a shell with the correct user. I hope this help. -- Matthias > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of binberati > Sent: Wednesday, October 18, 2006 4:35 AM > To: pgsql-admin@postgresql.org > Subject: [ADMIN] FastCgi / PostgreSQL: FATAL: Ident > authentication failed for user "user_name" > > > Hi, > > I have a strange problem running Django on a GrokThis.net shared > hosting account: > > Environment: > -- > Apache/2.0.59 (Unix) > mod_fastcgi/2.4.2 > PostgreSQL 8.1.3 > -- > > > settings.py: > -- > DATABASE_ENGINE = 'postgresql' > DATABASE_USER = 'user_name' > DATABASE_PASSWORD = '***' > -- > or > -- > DATABASE_ENGINE = 'postgresql_psycopg2' > DATABASE_USER = 'user_name' > DATABASE_PASSWORD = '***' > -- > > > Django on FastCgi renders this error: > -- > Traceback (most recent call last): > File > "/home/shared/user_name/django_src/django/template/__init__.py" in > render_node > 706. result = node.render(context) > File > "/home/shared/user_name/django_src/django/template/__init__.py" in > render > 757. return self.encode_output(output) File > "/home/shared/user_name/django_src/django/template/__init__.py" in > encode_output > 739. return str(output) > File "/home/shared/user_name/django_src/django/db/models/query.py" in > __repr__ > 97. return repr(self._get_data()) > File "/home/shared/user_name/django_src/django/db/models/query.py" in > _get_data > 430. self._result_cache = list(self.iterator()) File > "/home/shared/user_name/django_src/django/db/models/query.py" in > iterator > 170. cursor = connection.cursor() > File > "/home/shared/user_name/django_src/django/db/backends/postgres > ql/base.py" > in cursor > 43. self.connection = Database.connect(conn_string) > > OperationalError at / > FATAL: Ident authentication failed for user "user_name" > -- > > Surprisingly, I can succesfully connect to the db using either: > > - psql - PostgreSQL interactive terminal > - django-admin.py shell > - django-admin.py dbshell > - django development server > - Navicat PostgreSQL from my own pc using ssh-tunnel > > The only circumstance in which I cannot seem to connect to the db is > using the FastCgi instance, although it is configured to use the same > settings file as above... > > > [1] Can anybody shed a light on the difference between the FastCgi > context and the ones mentioned above? I suspect it must have something > to do with pg_hba.conf... but I can't see the difference between the > contexts. > > [2] How do I resolve this issue? :) > > > Thanks very much in advance! > > Best regards, > bin > > > ---(end of > broadcast)--- > TIP 9: In versions below 8.0, the planner will ignore your desire to >choose an index scan if your joining column's datatypes do not >match > ---(end of broadcast)--- TIP 6: explain analyze is your friend
