For all of you having services failing to start

Question

For all of you having services failing to start

After 48 hours of struggle with this same issue and 6 clean re-installs of Lion Server I have found the bug in Lion Server causing all ruby based collaboration services (Device Manager, Wiki, ical, some adress book features ie: major screw up in services around server admin tools and server app). The most visible one is in Profile Manager because as you all pointed out it even says sometimes "Error Reading Settings". And if you take a look at the logs its even worst...full of errors...

that's how I found out, yes reading all the logs took time:

Basically they all fail because they use Postgresql database.

At first I did 2 clean re-installs and noticed everytime, after having spent some time configuring the server (open directory/kerneros, creating accounts/mailboxes, profiles etc.). I would do a reboot and everything would break.

Now I won't go over all the diggin I did but I finally manage to understand why Postgres at some point was failing.

it seems there is a bug.

If you turn "Dedicate Resources to Server Services" in the Server.app Hardware Section (next to Push Notifications switch", postgres doesn't start and all depending services (lots) fail.

The Solution: Just turn that OFF as shown below and restart. Everything should get back in order. If you still see some "push_notify: not connected" erros in you console logs (it happened to me even thoug all servcies were restored) the solution is easy. Hit change and redo the setup with you appleid. You'll be issued new certs by Apple and everything shoudl work fine.

That's all.

Hope this helps the many people that are frustrated like I was. Now that everything works, it's the perfect server for a mini Cloud. You'll love Profile Manager for provisioning payload to your devices. Elegant, efficient and simple, yet very flexible with the openDirectory backend.

Cheers everyone !

Eric

twitter: @teknologism

Mac OS X (10.7)

Posted on Jul 24, 2011 7:17 PM

Reply

Answer 1

Jun 2, 2017 3:25 PM in response to Alex Zavatone

Well, Apple isn't letting me edit and update my post, so here is the edited and updated information. Sorry for the duplicate information spam.

I have this error on Server install and can't get past "Preparing Wiki service"

I just updated Mac OS to 10.12.5 and. Server to 5.3.1, did fresh install. Third Server download of the day.

In the ServerSetup_WikiServer.log, the first error I see is this:

Jun 2 14:55:03.042 WikiServer<7fb8bacda310> Running 'collabd_database_loader --mode start'

Traceback (most recent call last):

File "/Applications/Server.app/Contents/ServerRoot/usr/bin/xpg_ctl", line 2546, in <module>

os._exit(exitCode[0])

TypeError: an integer is required

createuser: could not connect to database postgres: could not connect to server: No such file or directory

Is the server running locally and accepting

connections on Unix domain socket "/Library/Server/Wiki/PostgresSocket/.s.PGSQL.5432"?

createdb: could not connect to database template1: could not connect to server: No such file or directory

Is the server running locally and accepting

connections on Unix domain socket "/Library/Server/Wiki/PostgresSocket/.s.PGSQL.5432"?

And then after that, the process continues and then I get the same error again. and then one more time and the server installation hangs.

xpg_ctl", line 2546, in <module>

os._exit(exitCode[0])

TypeError: an integer is required

What's infuriating is that this is on install, so I can't edit any settings in Server, because it's not even set up yet.

Link to my recently posted question on this:

https://discussions.apple.com/thread/7972249

Reply

Answer 2

Jun 2, 2017 3:06 PM in response to The Teknologist

I have this error on Server install and can't get past "Preparing Wiki service"

I just updated Mac OS to 10.12.5 and. Server to 5.3.1, did fresh install. Third Server download of the day.

In the ServerSetup_WikiServer.log, the first error I see is this:

Jun 2 14:55:03.042 WikiServer<7fb8bacda310> Running 'collabd_database_loader --mode start'

Traceback (most recent call last):

File "/Applications/Server.app/Contents/ServerRoot/usr/bin/xpg_ctl", line 2546, in <module>

os._exit(exitCode[0])

TypeError: an integer is required

createuser: could not connect to database postgres: could not connect to server: No such file or directory

Is the server running locally and accepting

connections on Unix domain socket "/Library/Server/Wiki/PostgresSocket/.s.PGSQL.5432"?

createdb: could not connect to database template1: could not connect to server: No such file or directory

Is the server running locally and accepting

connections on Unix domain socket "/Library/Server/Wiki/PostgresSocket/.s.PGSQL.5432"?

And then after that, the process continues and then I get the same error again. and then one more time and the server installation hangs.

xpg_ctl", line 2546, in <module>

os._exit(exitCode[0])

TypeError: an integer is required

What's infuriating is that this is on install.

Reply

Answer 3

Jul 24, 2011 11:26 PM in response to The Teknologist

To put this simply... i love you

Reply

Answer 4

dreness

Level 1

60 points

Jul 24, 2011 11:44 PM in response to The Teknologist

Hi,

Having "Dedicate system resources to server services" enabled is certainly not supposed to completley break postgres, and does not on any lion server systems I've used.

I would encourage you to file a bug with apple so they can get more info about your configuration to find out what is wrong. http://bugreporter.apple.com. Be sure to attach a system profiler report, along with whatever logs you used to figure out why turning off this option allows postgres to start on your system.

Cheers,

-dre

Reply

Answer 5

Tim Harris

Level 4

1,481 points

Jul 25, 2011 12:23 AM in response to The Teknologist

Can you post the extract's form the logs where Postgresql is trying to load. Personally I have not see problem you have reported.

Reply

Answer 6

Jul 25, 2011 8:21 AM in response to The Teknologist

The relevant logs (at the time of the failure loop):

PostgreSQL.log @ 2:43 I reboot the server and that's what we have after reboot...

2011-07-25 02:43:07 CEST LOG: database system is shut down

2011-07-25 02:54:00 CEST LOG: database system was shut down at 2011-07-25 02:43:07 CEST

2011-07-25 02:54:00 CEST LOG: autovacuum launcher started

2011-07-25 02:54:00 CEST LOG: database system is ready to accept connections

2011-07-25 02:54:03 CEST LOG: connection received: host=[local]

2011-07-25 02:54:03 CEST LOG: connection authorized: user=collab database=collab

2011-07-25 02:54:05 CEST LOG: connection received: host=[local]

2011-07-25 02:54:05 CEST LOG: connection authorized: user=collab database=collab

2011-07-25 02:54:05 CEST ERROR: duplicate key value violates unique constraint "global_settings_pkey"

2011-07-25 02:54:05 CEST DETAIL: Key (key)=(com.apple.setting.schema_version) already exists.

2011-07-25 02:54:05 CEST STATEMENT: INSERT INTO global_settings (key, value_int) VALUES ('com.apple.setting.schema_version', $1)

2011-07-25 02:54:05 CEST LOG: unexpected EOF on client connection

2011-07-25 02:54:05 CEST LOG: connection received: host=[local]

2011-07-25 02:54:05 CEST LOG: connection authorized: user=collab database=collab

2011-07-25 02:54:05 CEST LOG: connection received: host=[local]

2011-07-25 02:54:05 CEST LOG: connection authorized: user=collab database=collab

2011-07-25 02:55:21 CEST LOG: connection received: host=[local]

2011-07-25 02:55:21 CEST LOG: connection authorized: user=_postgres database=postgres

2011-07-25 02:55:22 CEST LOG: unexpected EOF on client connection

2011-07-25 02:55:22 CEST LOG: received smart shutdown request

2011-07-25 02:55:22 CEST LOG: autovacuum launcher shutting down

2011-07-25 02:55:22 CEST LOG: shutting down

2011-07-25 02:55:22 CEST LOG: database system is shut down

And that is the relevant part in the system.log:

Jul 25 02:43:01 teknologism org.clamav.freshclam[608]: ClamAV update process started at Mon Jul 25 02:43:01 2011

Jul 25 02:43:01 teknologism freshclam[608]: Your ClamAV installation is OUTDATED!

Jul 25 02:43:01 teknologism freshclam[608]: Local version: 0.97 Recommended version: 0.97.1

Jul 25 02:43:01 teknologism org.clamav.freshclam[608]: WARNING: Your ClamAV installation is OUTDATED!

Jul 25 02:43:01 teknologism org.clamav.freshclam[608]: WARNING: Local version: 0.97 Recommended version: 0.97.1

Jul 25 02:43:01 teknologism org.clamav.freshclam[608]: DON'T PANIC! Read http://www.clamav.net/support/faq

Jul 25 02:43:01 teknologism org.clamav.freshclam[608]: main.cvd is up to date (version: 53, sigs: 846214, f-level: 53, builder: sven)

Jul 25 02:43:01 teknologism org.clamav.freshclam[608]: daily.cld is up to date (version: 13356, sigs: 161751, f-level: 60, builder: ccordes)

Jul 25 02:43:02 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 4 seconds

Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=596

Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=595

Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=594

Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=593

Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=592

Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=591

Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=590

Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=589

Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=588

Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=587

Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: caldav caldav [local] idle", pid=370

Jul 25 02:43:10 teknologism servermgrd[118]: servermgr_ipfilter:ipfw config:Notice:Flushed IPv4 rules

Jul 25 02:43:10 teknologism servermgrd[118]: servermgr_ipfilter:ipfw config:Notice:Flushed IPv6 rules

Jul 25 02:43:11 teknologism com.apple.collabd.podcast-cache-updater[640]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)

Jul 25 02:43:11 teknologism com.apple.collabd.podcast-cache-updater[640]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'

Jul 25 02:43:11 teknologism com.apple.collabd.podcast-cache-updater[640]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'

Jul 25 02:43:11 teknologism com.apple.collabd.podcast-cache-updater[640]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'

Jul 25 02:43:11 teknologism com.apple.collabd.podcast-cache-updater[640]: from /usr/share/collabd/server/ruby/../../coreclient/vendor/plugins/podcasts/app/hel pers/podcast_cache_util.rb:23:in `initialize'

Jul 25 02:43:11 teknologism com.apple.collabd.podcast-cache-updater[640]: from /usr/share/collabd/server/ruby/podcast_cache_updater.rb:24:in `new'

Jul 25 02:43:11 teknologism com.apple.collabd.podcast-cache-updater[640]: from /usr/share/collabd/server/ruby/podcast_cache_updater.rb:24

Jul 25 02:43:11 teknologism com.apple.launchd[1] (com.apple.collabd.podcast-cache-updater[640]): Exited with code: 1

Jul 25 02:43:13 teknologism servermgrd[118]: servermgr_postgres: waiting for postgres to respond

Jul 25 02:43:13 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 3 seconds

Jul 25 02:43:14 teknologism servermgrd[118]: servermgr_postgres: waiting for postgres to respond

Jul 25 02:43:15: --- last message repeated 2 times ---

Jul 25 02:43:15 teknologism servermgrd[118]: servermgr_postgres: Timed out trying to start postgres.

Jul 25 02:43:17 teknologism mdworker[660]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 132970 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/39/44/041-1233/K2dbQDWBvBwvYXpkr5v 3qkvMvqYGq3Y94D/AlKybdFirmwareUpdate.smd.previous, exiting to clean up.

Jul 25 02:43:19 teknologism servermgrd[118]: servermgr_devicemgr: prepareForOffline: error db:migrate: 1

Jul 25 02:43:19 teknologism pcastwatcher[479]: Cluster member role changed to LEADER

Jul 25 02:43:21 teknologism servermgrd[118]: servermgr_postgres: waiting for postgres to respond

Jul 25 02:43:22 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds

Jul 25 02:43:22 teknologism servermgrd[118]: servermgr_postgres: waiting for postgres to respond

Jul 25 02:43:23: --- last message repeated 2 times ---

Jul 25 02:43:23 teknologism servermgrd[118]: servermgr_postgres: Timed out trying to start postgres.

Jul 25 02:43:27 teknologism mdworker[674]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 134078 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/16/52/061-3533/rMnHGtg5jbQBVQFSLzH WnNdVRmZNWgcM3Q/MacBookProEFIUpdate1.3.smd.previous, exiting to clean up.

Jul 25 02:43:27 teknologism servermgrd[118]: servermgr_devicemgr: prepareForOffline: error db:migrate: 1

Jul 25 02:43:32 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds

Jul 25 02:43:37 teknologism mdworker[678]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 130851 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/40/21/061-5964/S27D5FnWT54LZjFmRFb N46dSTSYhxy8QyG/MacBookSMCUpdate.smd.previous, exiting to clean up.

Jul 25 02:43:42 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds

Jul 25 02:43:47 teknologism mdworker[296]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 132280 swapped: 2 regions: 417), hit usage threshold importing /Users/teknologist/Library/Saved Application State/com.apple.Console.savedState/windows.plist, exiting to clean up.

Jul 25 02:43:52 teknologism mdworker[683]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 132244 swapped: 2 regions: 412), hit usage threshold importing /private/var/db/swupd/html/content/downloads/42/28/061-5258/Nhf7yJ5zHRDgGqW3CrN WPQYvTSxLMykkgP/HP_PrinterSupport.smd, exiting to clean up.

Jul 25 02:43:58 teknologism mdworker[691]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 131620 swapped: 2 regions: 413), hit usage threshold importing /private/var/pgsql/base/16389/17282, exiting to clean up.

Jul 25 02:44:03 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds

Jul 25 02:44:08 teknologism mdworker[695]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 131245 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/63/62/061-3767/swJZDhd67fxx4fY4Pkk QHNvxhQvF6vgyqz/CinemaToolsUpdate4.0.1.smd.previous, exiting to clean up.

Jul 25 02:44:13 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds

Jul 25 02:44:18 teknologism mdworker[699]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 131620 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/16/19/061-3508/LQHLx2HjZkYbPnvsTJZ G9DFP5hLzRqmmG3/FrontRowUpdate1.3.1.smd.previous, exiting to clean up.

Jul 25 02:44:23 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds

Jul 25 02:44:24 teknologism serveradmin[704]: servermgr_postgres: waiting for postgres to respond

Jul 25 02:44:26: --- last message repeated 3 times ---

Jul 25 02:44:26 teknologism serveradmin[704]: servermgr_postgres: Timed out trying to start postgres.

Jul 25 02:44:26 teknologism serveradmin[704]: posting dist not

Jul 25 02:44:26 teknologism com.apple.collabd.notifications[154]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)

Jul 25 02:44:26 teknologism com.apple.collabd.notifications[154]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'

Jul 25 02:44:26 teknologism com.apple.collabd.notifications[154]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'

Jul 25 02:44:26 teknologism com.apple.collabd.notifications[154]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'

Jul 25 02:44:26 teknologism com.apple.collabd.notifications[154]: from notifications.rb:145:in `initialize'

Jul 25 02:44:26 teknologism com.apple.collabd.notifications[154]: from notifications.rb:439:in `new'

Jul 25 02:44:26 teknologism com.apple.collabd.notifications[154]: from notifications.rb:439

Jul 25 02:44:26 teknologism com.apple.launchd[1] (com.apple.collabd.notifications[154]): Exited with code: 1

Jul 25 02:44:28 teknologism postfix/smtpd[716]: warning: unknown[192.168.176.150]: SASL CRAM-MD5 authentication failed

Jul 25 02:44:28 teknologism com.apple.collabd.notifications[709]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)

Jul 25 02:44:28 teknologism com.apple.collabd.notifications[709]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'

Jul 25 02:44:28 teknologism com.apple.collabd.notifications[709]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'

Jul 25 02:44:28 teknologism com.apple.collabd.notifications[709]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'

Jul 25 02:44:28 teknologism com.apple.collabd.notifications[709]: from notifications.rb:145:in `initialize'

Jul 25 02:44:28 teknologism com.apple.collabd.notifications[709]: from notifications.rb:439:in `new'

Jul 25 02:44:28 teknologism com.apple.collabd.notifications[709]: from notifications.rb:439

Jul 25 02:44:28 teknologism com.apple.launchd[1] (com.apple.collabd.notifications[709]): Exited with code: 1

Jul 25 02:44:28 teknologism com.apple.launchd[1] (com.apple.collabd.notifications): Throttling respawn: Will start in 9 seconds

Jul 25 02:44:28 teknologism mdworker[729]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 136258 swapped: 2 regions: 414), hit usage threshold importing /private/var/db/swupd/html/content/downloads/46/49/061-4414/KfF9HYN5nxHSkVvYhqf 9JTW3kFs6R3bmgr/MacProGraphicsFWUpdate.smd.previous, exiting to clean up.

Jul 25 02:44:33 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds

Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'

Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: : Couldn't connect to server (Curl::Err::ConnectionFailedError)

Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'

Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'

Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'

Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: from notifications.rb:145:in `initialize'

Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: from notifications.rb:439:in `new'

Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: from notifications.rb:439

Jul 25 02:44:38 teknologism com.apple.launchd[1] (com.apple.collabd.notifications[732]): Exited with code: 1

Jul 25 02:44:38 teknologism com.apple.launchd[1] (com.apple.collabd.notifications): Throttling respawn: Will start in 9 seconds

Jul 25 02:44:39 teknologism mdworker[734]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 135883 swapped: 2 regions: 414), hit usage threshold importing /private/var/db/swupd/html/content/downloads/15/21/061-7052/gSgFsrpjkJ5vvNrbcsd MwphFYDcTpKWTmC/Savin_PrinterSupport.smd.previous, exiting to clean up.

Jul 25 02:44:44 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds

Jul 25 02:44:48 teknologism com.apple.collabd.notifications[738]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)

Jul 25 02:44:48 teknologism com.apple.collabd.notifications[738]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'

Jul 25 02:44:48 teknologism com.apple.collabd.notifications[738]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'

Jul 25 02:44:48 teknologism com.apple.collabd.notifications[738]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'

Jul 25 02:44:48 teknologism com.apple.collabd.notifications[738]: from notifications.rb:145:in `initialize'

Jul 25 02:44:48 teknologism com.apple.collabd.notifications[738]: from notifications.rb:439:in `new'

Jul 25 02:44:48 teknologism com.apple.collabd.notifications[738]: from notifications.rb:439

Jul 25 02:44:48 teknologism com.apple.launchd[1] (com.apple.collabd.notifications[738]): Exited with code: 1

Jul 25 02:44:48 teknologism com.apple.launchd[1] (com.apple.collabd.notifications): Throttling respawn: Will start in 9 seconds

Jul 25 02:44:49 teknologism mdworker[740]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 136255 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/22/25/061-6334/r6zDxQxCRGzSsfDfdLN X4hJcGmS7ckVTrT/Aperture2.1.4Update.smd, exiting to clean up.

Jul 25 02:44:54 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds

Jul 25 02:44:59 teknologism com.apple.collabd.notifications[746]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)

Jul 25 02:44:59 teknologism com.apple.collabd.notifications[746]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'

Jul 25 02:44:59 teknologism com.apple.collabd.notifications[746]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'

Jul 25 02:44:59 teknologism com.apple.collabd.notifications[746]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'

Jul 25 02:44:59 teknologism com.apple.collabd.notifications[746]: from notifications.rb:145:in `initialize'

Jul 25 02:44:59 teknologism com.apple.collabd.notifications[746]: from notifications.rb:439:in `new'

Jul 25 02:44:59 teknologism com.apple.collabd.notifications[746]: from notifications.rb:439

Jul 25 02:44:59 teknologism com.apple.launchd[1] (com.apple.collabd.notifications[746]): Exited with code: 1

Jul 25 02:44:59 teknologism com.apple.launchd[1] (com.apple.collabd.notifications): Throttling respawn: Will start in 9 seconds

Jul 25 02:44:59 teknologism mdworker[749]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 135390 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/09/53/061-4083/DvcrdMLDXTGwQck8TgQ gxWWqGDZJyCvC6X/iMacSoftwareUpdate1.2.1.smd, exiting to clean up.

Jul 25 02:45:04 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds

Jul 25 02:45:06 teknologism xscertd-helper[323]: idle timer triggered, exiting

Jul 25 02:45:09 teknologism com.apple.collabd.notifications[757]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)

Jul 25 02:45:09 teknologism com.apple.collabd.notifications[757]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'

Jul 25 02:45:09 teknologism com.apple.collabd.notifications[757]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'

Jul 25 02:45:09 teknologism com.apple.collabd.notifications[757]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'

Jul 25 02:45:09 teknologism com.apple.collabd.notifications[757]: from notifications.rb:145:in `initialize'

Jul 25 02:45:09 teknologism com.apple.collabd.notifications[757]: from notifications.rb:439:in `new'

Jul 25 02:45:09 teknologism com.apple.collabd.notifications[757]: from notifications.rb:439

Jul 25 02:45:09 teknologism com.apple.launchd[1] (com.apple.collabd.notifications[757]): Exited with code: 1

Jul 25 02:45:09 teknologism com.apple.launchd[1] (com.apple.collabd.notifications): Throttling respawn: Will start in 9 seconds

Jul 25 02:45:09 teknologism mdworker[759]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 133619 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/51/53/061-5114/Bsmt5MYcHbnbGDpMnGZ vVFhfcs9vX7PhzB/Numbers_103.smd, exiting to clean up.

Jul 25 02:45:14 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds

Jul 25 02:45:19 teknologism com.apple.collabd.notifications[773]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)

Jul 25 02:45:19 teknologism com.apple.collabd.notifications[773]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'

Jul 25 02:45:19 teknologism com.apple.collabd.notifications[773]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'

Jul 25 02:45:19 teknologism com.apple.collabd.notifications[773]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'

Jul 25 02:45:19 teknologism com.apple.collabd.notifications[773]: from notifications.rb:145:in `initialize'

Jul 25 02:45:19 teknologism com.apple.collabd.notifications[773]: from notifications.rb:439:in `new'

Jul 25 02:45:19 teknologism com.apple.collabd.notifications[773]: from notifications.rb:439

Jul 25 02:45:19 teknologism com.apple.launchd[1] (com.apple.collabd.notifications[773]): Exited with code: 1

Jul 25 02:45:19 teknologism com.apple.launchd[1] (com.apple.collabd.notifications): Throttling respawn: Will start in 9 seconds

The last few lines go in a loop and they also tend to bring the CPU high unti it's fixed.

As soon as I turn off "Dedicate Resources to System Services" and I reboot this problem disappears...

Thanks for any help you may briong.

Anyway, the server runs perfectly well without that option...

Reply

Answer 7

Aug 1, 2011 7:56 AM in response to The Teknologist

Ran into the same issue here - only disabling that option and restarting didn't make everything work agian. Is there a trick to getting the web services up and running again? Web service won't start.

Here's the error I see in the web browser:

Curl::Err::ConnectionFailedError in SourcesController#index

Any information would be helpful. It does not appear that anything is being logged anywhere ecept to the browser, even when trying to start the web service.

The only thing in logs right now is (hundreds of times): 11-08-01 8:54:27.000 AM kernel: nstat_lookup_entry failed: 2

Reply

Answer 8

Aug 1, 2011 8:05 AM in response to Michael C M

For me it appears 'the system' is shutting down postgres.

2011-08-01 09:00:39 MDT LOG: database system was shut down at 2011-08-01 08:38:08 MDT

2011-08-01 09:00:39 MDT LOG: autovacuum launcher started

2011-08-01 09:00:39 MDT LOG: database system is ready to accept connections

2011-08-01 09:01:08 MDT LOG: connection received: host=[local]

2011-08-01 09:01:08 MDT LOG: connection authorized: user=caldav database=caldav

2011-08-01 09:02:48 MDT LOG: connection received: host=[local]

2011-08-01 09:02:48 MDT LOG: connection authorized: user=_postgres database=postgres

2011-08-01 09:02:49 MDT FATAL: terminating connection due to administrator command

2011-08-01 09:02:49 MDT LOG: received smart shutdown request

2011-08-01 09:02:49 MDT LOG: autovacuum launcher shutting down

2011-08-01 09:02:49 MDT LOG: shutting down

2011-08-01 09:02:49 MDT LOG: database system is shut down

Reply

Answer 9

jsherald

Level 1

0 points

Aug 1, 2011 5:55 PM in response to The Teknologist

Experiencing the same issue, however I don't have resources dedicated to the server to begin with...

Reply

Answer 10

Aug 2, 2011 5:20 AM in response to jsherald

Hi Everyone,

after some days of observation, it seems that turning off the option and having my server work again was pure coincidence.

Nevertheless I think I have figured out what breaks the server in my case.

Having resintalled from scratch a couple of times I can definetly say that I know what breaks postgres (makes it shut down immediately) and breaks all services relying on postgres, at least in my case:

My server is setup with OpenDirectory as standalone service on this server. All servcies are setup except for DNS,PodcastProducer and Xgrid (all configurable in ServerAdmin tools).

Now, everytime I launch the configuration of the Xgrid service and podcast producer (which relies on Xgrid), it does some configuration in OpenDirectory and Keberos.

Then after a reboot I experience the problems described in my earlier posts (postgres failing).

This is the exact symptoms reported by other users in this discussion.

My solution: for the moement stay away from anything relayed to Xgrid/PodcastProducer.

The problem described is systematic and 100% reproducible, at least on my server.

Hope this helps others.

Reply

Answer 11

Aug 2, 2011 5:50 AM in response to The Teknologist

Well, in disabling the "Dedicate…" option, that did in fact fix our server. Can't explain why it even broke since we don't use Podcast Producer or Xgrid.

Reply

Answer 12

jsherald

Level 1

0 points

Aug 3, 2011 5:49 PM in response to The Teknologist

I'm not using Xgrid or Podcast Producer and I'm still continuously getting "Error Reading Settings" in the Server app for both Wiki and Profile Manager services. I disabled all services, rebooted, and restarted the services once with success. Later that day, everything stopped working again. Reboot won't even fix it.

At this point, I spent $50 for a product that doesn't provide a single service. Is it worth trying to fix or should I just seek a refund?

Reply

Answer 13

minilo1

Level 1

0 points

Aug 5, 2011 3:01 PM in response to The Teknologist

I'm having huge problems with too with exactly the same symptoms/results.

After a reinstalling, things work for a while and then postgres seems to fail along with most services. Have reinstalled three times and wasted huge amounts of time on this trying to manually follow up issues listed in the logs (such as the datahase not having permission to write a log, preventing it from starting)...

I suspect that it might have something to do with permissions being repaired during the "daily" maintenance as running "repair permissions" seems to screw things up. e.g. reinstalling, making sure the services I need are running, then repairing permissions, followed by a reboot results in broken services.

When things are mostly working after a reinstall, I cannot turn off the podcast producer via Server. Yesterday morning I did a full reinstall, didn't touch repair permissions, had everything working and then today it's back in the same screwed up state again...

I've never had so much trouble with an Apple system upgrade in over 20 years and I cannot see a way out of this beyond reverting to SL. Can't understand how this sysyem can be so broken as I'm only using a the address book, calendar, web, wiki and file sharing services so my configuration is really simlple.

Has anyone found a workaround for this? We're clearly not alone suffering with this...

Reply

Answer 14

Aug 5, 2011 6:05 PM in response to minilo1

Much of what you are describing (restart kills things, intermitent and assorted errors etc.) are also happening when users are trying to bind to an Active Directory service with 10.7 client. There are a couple of threads where the AD problems are listed. From the similarities I am wondering if there is a common denominator to both your services and my Active directorry problems.

Reply

Answer 15

minilo1

Level 1

0 points

Aug 6, 2011 3:27 AM in response to Joe Pyrdek

Joe, thanks for the response. I'm currently testing with the server itself (a mac mini) and a macbook pro on a private network, and neither are using Active Directory services, or requesting them so if the symptoms are the same then there is a chance that your problems with Active Directory might not be related to AD at all? I think the database shuts down and won't restart, possibly due to pemission problems/corruption, preventing all of the services that depend on it from operating.

Reply