#400: Postgres error (apparently won't start)
------------------------------------+---------------------------------------
Reporter: mrzom...@… | Owner: wsanc...@…
Type: Defect | Status: new
Priority: 5: Not set | Milestone:
Component: Calendar Server | Severity: Other
Keywords: |
------------------------------------+---------------------------------------
Comment(by d...@…):
Replying to [comment:1 d...@…]:
> It seems this was due to Mr. Zombie having a separate instance of
postgres running. When he terminated that instance, calendar server was
able to start its own postgres instance. This requires investigation...
Have a look at CalendarServer/CalendarServer/data/Logs/postgres.log. This
hopefully will contain some information about why calendar server's
postgres instance failed to start. I've got a dollar that says it's kernel
shared memory limits. If this is true, what you encountered is not a bug,
but rather a configuration issue, and you can read more about the tunings
you would need to run multiple instances here:
http://www.postgresql.org/docs/8.1/static/kernel-resources.html.
Also note that although there is a postgres.conf config file, a couple key
settings are specified as command line options when calendar server starts
postgres. They are: -c shared_buffers=30 -c max_connections=20. I mention
this only because the command line args always take precedence over what's
in the config file.
--
Ticket URL: <http://trac.calendarserver.org/ticket/400#comment:2>
Calendar and Contacts Server </>
HTTP/WebDAV/CalDAV Server
_______________________________________________
calendarserver-dev mailing list
calendarserver-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-dev
