Postgres error (apparently won't start)

[macosforgebot]

mrzombie@… originally submitted this as ticket:400

---

Using Mac OS X 10.6.4 and the README file directions, I couldn't get the Calendar Server to start. Find enclosed in an attachment the logfile.

[macosforgebot]

mrzombie@… originally submitted this as attachment:logfile:⁠ticket:400

• Attachment logfile (8.7 KB) added

---

Log file

[macosforgebot]

@dreness originally submitted this as comment:1:⁠ticket:400

---

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...

[macosforgebot]

@dreness originally submitted this as comment:2:⁠ticket:400

---

Replying to dre@…:

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.

[macosforgebot]

@wsanchez originally submitted this as comment:3:⁠ticket:400

• Status changed from new to closed
• Resolution changed from to Configuration changed