<< | Index | >>
Requirements as per E-Mail from Zeno
/var/www/oddb.org/jobs/export_oddb2tdat)
root 3425 3407 0 08:36 ? 00:00:00 supervise ch.oddb-swissindex_nonpharma root 3434 3425 0 08:36 ? 00:00:00 sudo -u apache /var/www/oddb.org/ext/swissindex/bin/swissindex_nonpharmad apache 3497 3434 0 08:36 ? 00:00:00 ruby /var/www/oddb.org/ext/swissindex/bin/swissindex_nonpharmad
Forced using postgresql 8.4 by calling sudo eselect postgresql set 8.4. Then emerge --unmerge dev-db/postgresql-base-9.2.4
On thinpower migel uses the database migel.ruby193 as defined in /var/www/migel/etc/migel.yml.
Creating the file /etc/migel/migel.yml via puppet. But still cannot connect to database migel.
This script does not work, as it cannot connect to the postgresql database.
On Thinpower the command psql -U postgres migel.ruby193 works.
On my vagrant system I must use sudo -u apache psql migel or I cannot connect to the db.
On Thinpower had a look at the grants.
psql -U postgres migel.ruby193
Dies ist psql 8.3.8, das interaktive PostgreSQL-Terminal.
migel.ruby193=# \dg
Liste der Rollen
Rollenname | Superuser | Rolle erzeugen | DB erzeugen | Verbindungen | Mitglied von
----------------+-----------+----------------+-------------+--------------------+--------------
migel | nein | nein | ja | keine Beschränkung | {}
oddb | nein | nein | nein | keine Beschränkung | {}
postgres | ja | ja | ja | keine Beschränkung | {}
After changing the db_user to apache in /etc/migel/migel.yml I get
sudo -u apache /var/www/migel/bin/migeld
/var/www/migel/bin/migeld:6: warning: variable $KCODE is no longer effective; ignored
ERROR: relation "object" already exists
ERROR: must be owner of relation object
ERROR: must be owner of relation object
ERROR: relation "object_connection" already exists
ERROR: must be owner of relation object_connection
ERROR: relation "collection" already exists
ERROR: permission denied for relation object
/usr/local/lib64/ruby/gems/1.9.1/gems/dbd-pg-0.3.9/lib/dbd/pg/statement.rb:62:in `rescue in execute': ERROR: permission denied for relation object (DBI::ProgrammingError)
from /usr/local/lib64/ruby/gems/1.9.1/gems/dbd-pg-0.3.9/lib/dbd/pg/statement.rb:37:in `execute'
from /usr/local/lib64/ruby/gems/1.9.1/gems/dbi-0.4.5/lib/dbi/base_classes/database.rb:96:in `execute'
from /usr/local/lib64/ruby/gems/1.9.1/gems/dbi-0.4.5/lib/dbi/handles/database.rb:81:in `execute'
from /usr/local/lib64/ruby/gems/1.9.1/gems/dbi-0.4.5/lib/dbi/handles/database.rb:115:in `select_one'
from /usr/local/lib64/ruby/gems/1.9.1/gems/odba-1.1.0/lib/odba/connection_pool.rb:39:in `block in method_missing'
from /usr/local/lib64/ruby/gems/1.9.1/gems/odba-1.1.0/lib/odba/connection_pool.rb:29:in `next_connection'
from /usr/local/lib64/ruby/gems/1.9.1/gems/odba-1.1.0/lib/odba/connection_pool.rb:38:in `method_missing'
from /usr/local/lib64/ruby/gems/1.9.1/gems/odba-1.1.0/lib/odba/storage.rb:513:in `restore_named'
from /usr/local/lib64/ruby/gems/1.9.1/gems/odba-1.1.0/lib/odba/cache.rb:297:in `block in fetch_named'
from /usr/local/lib64/ruby/gems/1.9.1/gems/odba-1.1.0/lib/odba/cache.rb:313:in `call'
from /usr/local/lib64/ruby/gems/1.9.1/gems/odba-1.1.0/lib/odba/cache.rb:313:in `fetch_or_do'
from /usr/local/lib64/ruby/gems/1.9.1/gems/odba-1.1.0/lib/odba/cache.rb:296:in `fetch_named'
from /usr/local/lib64/ruby/gems/1.9.1/gems/odba-1.1.0/lib/odba/cache.rb:351:in `indices'
from /usr/local/lib64/ruby/gems/1.9.1/gems/odba-1.1.0/lib/odba/cache.rb:474:in `setup'
from /var/www/migel/lib/migel/persistence/odba.rb:21:in `<module:Migel>'
from /var/www/migel/lib/migel/persistence/odba.rb:15:in `<top (required)>'
from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /var/www/migel/lib/migel/persistence.rb:9:in `<module:Migel>'
from /var/www/migel/lib/migel/persistence.rb:8:in `<top (required)>'
from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
Ran sudo emerge --oneshot portage to avoid warning An update to portage is available. It is _highly_ recommended when restarting vagrant.
Conclusion: must also bring pg_hba.conf pg_ident.conf postgresql.conf in /etc/postgresql-8.4/ into vagrant.
May be I should also install etckeeper. But must configure git before.
In parallel tried to bring up a new instance of vagrant. Made the following corrections
Access via git to scm.ywesee.com not possible, as server is being restored. There a lot of stuff does not work.
Finally made a simple funtoo box come up with vagrant > 1.2.2. See https://github.com/mitchellh/vagrant/pull/1826
There are other people interested in funtoo/vagrant. See
Committed changes to fix [[https://github.com/ngiger/vagrant/commit/5d68c4d19ff972bc39f2a4e60b85d398ca381dce | funtoo network configuration ]