collabauthd in log file

Question

collabauthd in log file

I'm getting the following over and over in my server log file...

Jul 27 20:53:49 myserver sandboxd[151] ([726]): ruby(726) deny file-read-metadata /private/var/folders/zz/zyxvpxvq6csfxvn_n00000vm00006x

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/runtime.rb:31:in `setup'

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: :

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: You have already activated rack 1.2.2, but your Gemfile requires rack 1.2.1. Consider using bundle exec.

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: (

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: Gem::LoadError

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: )

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/spec_set.rb:12:in `each'

Jul 27 20:53:49: --- last message repeated 1 time ---

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/runtime.rb:17:in `setup'

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler.rb:107:in `setup'

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /usr/share/collabd/webauthd/config/boot.rb:14

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `gem_original_require'

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `require'

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /usr/share/collabd/webauthd/config/application.rb:12

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `gem_original_require'

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `require'

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /usr/share/collabd/webauthd/config/environment.rb:11

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `gem_original_require'

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygem s/custom_require.rb:31:in `require'

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /usr/share/collabd/webauthd/config.ru:12

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /Library/Ruby/Gems/1.8/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /Library/Ruby/Gems/1.8/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /usr/share/collabd/webauthd/config.ru:1:in `new'

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: from /usr/share/collabd/webauthd/config.ru:1

Jul 27 20:53:49 myserver com.apple.collabauthd[726]: >> Using rack adapter

Jul 27 20:53:49 myserver com.apple.launchd[1] (com.apple.collabauthd[726]): Exited with code: 1

Jul 27 20:53:49 myserver com.apple.launchd[1] (com.apple.collabauthd): Throttling respawn: Will start in 10 seconds

What is going wrong?

Mac OS X (10.7)

Posted on Jul 27, 2011 3:59 AM

Reply

Answer 1

Jul 28, 2011 5:26 AM in response to Intelligencer

I am having the same problem. It looks like this might have something to do with a collaboration server. The errors seem to be generated around "ruby" and not being able to get correct permissions.

The config files are all located here:

/System/Library/LaunchDaemons/com.apple.collab*

My guess is there was an issue when I tried installing the new Lion Server tools and this is the result. Not sure how to stop it from a tool but I can stop it from the command line.

# Switch to root user sudo su - # Now unload all the LaunchDaemons launchctl unload /System/Library/LaunchDaemons/com.apple.collab*

After doing that I noticed my messages went away, but then I started getting the following:

7/28/11 8:25:07.232 AM org.postgresql.postgres: postgres cannot access the server configuration file "/var/pgsql/postgresql.conf": No such file or directory 7/28/11 8:25:07.232 AM com.apple.launchd: (org.postgresql.postgres[44450]) Exited with code: 2 7/28/11 8:25:07.232 AM com.apple.launchd: (org.postgresql.postgres) Throttling respawn: Will start in 10 seconds 7/28/11 8:25:12.673 AM com.apple.launchd: (com.google.keystone.daemon[44455]) bootstrap_register() erroneously called instead of bootstrap_check_in(). Mach service: com.google.Keystone.Daemon 7/28/11 8:25:12.676 AM com.apple.launchd: (com.google.keystone.daemon[44455]) Exited with code: 1 7/28/11 8:25:12.676 AM com.apple.launchd: (com.google.keystone.daemon) Throttling respawn: Will start in 10 seconds 7/28/11 8:25:17.250 AM org.postgresql.postgres: postgres cannot access the server configuration file "/var/pgsql/postgresql.conf": No such file or directory 7/28/11 8:25:17.251 AM com.apple.launchd: (org.postgresql.postgres[44462]) Exited with code: 2 7/28/11 8:25:17.251 AM com.apple.launchd: (org.postgresql.postgres) Throttling respawn: Will start in 10 seconds 7/28/11 8:25:22.715 AM com.apple.launchd: (com.google.keystone.daemon[44467]) bootstrap_register() erroneously called instead of bootstrap_check_in(). Mach service: com.google.Keystone.Daemon 7/28/11 8:25:22.718 AM com.apple.launchd: (com.google.keystone.daemon[44467]) Exited with code: 1 7/28/11 8:25:22.718 AM com.apple.launchd: (com.google.keystone.daemon) Throttling respawn: Will start in 10 seconds

Reply

Answer 2

Aug 4, 2011 5:57 AM in response to Intelligencer

This may not work for you, but it did for me as I was having similar problems. It seems that both of these errors are ultimately caused by Postgres not being able to start due to a permissioning error in the /Library/Logs dir when it tries to open the PostgreSQL.log file.

I corrected it by issuing the following commands in Terminal

sudo touch /Library/Logs/PostgreSQL.log

sudo chown _postgres:admin /Library/Logs/PostgreSQL.log

This will create the log file and give it the proper ownership for Postgres to have its way with it. After that, launchd should be able to start up Postgres without any problems.

Reply