rmadison crashed with OperationalError; database "projectb" does not exist

Bug #529935 reported by Hew
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devscripts (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: devscripts

This crash is reproducible. I haven't had a problem running it on other packages.

$ rmadison -u debian libc0.1
Traceback (most recent call last):
  File "/usr/local/bin/dak", line 238, in <module>
    main()
  File "/usr/local/bin/dak", line 218, in main
    module.main()
  File "/srv/ftp.debian.org/dak/dak/ls.py", line 91, in main
    session = DBConn().session()
  File "/srv/ftp.debian.org/dak/daklib/dbconn.py", line 2751, in __init__
    self.__createconn()
  File "/srv/ftp.debian.org/dak/daklib/dbconn.py", line 3096, in __createconn
    self.__setuptables()
  File "/srv/ftp.debian.org/dak/daklib/dbconn.py", line 2803, in __setuptables
    table = Table(table_name, self.db_meta, autoload=True)
  File "/var/lib/python-support/python2.5/sqlalchemy/schema.py", line 108, in __call__
    return type.__call__(self, name, metadata, *args, **kwargs)
  File "/var/lib/python-support/python2.5/sqlalchemy/schema.py", line 236, in __init__
    _bind_or_error(metadata).reflecttable(self, include_columns=include_columns)
  File "/var/lib/python-support/python2.5/sqlalchemy/engine/base.py", line 1261, in reflecttable
    conn = self.contextual_connect()
  File "/var/lib/python-support/python2.5/sqlalchemy/engine/base.py", line 1229, in contextual_connect
    return self.Connection(self, self.pool.connect(), close_with_result=close_with_result, **kwargs)
  File "/var/lib/python-support/python2.5/sqlalchemy/pool.py", line 142, in connect
    return _ConnectionFairy(self).checkout()
  File "/var/lib/python-support/python2.5/sqlalchemy/pool.py", line 304, in __init__
    rec = self._connection_record = pool.get()
  File "/var/lib/python-support/python2.5/sqlalchemy/pool.py", line 161, in get
    return self.do_get()
  File "/var/lib/python-support/python2.5/sqlalchemy/pool.py", line 642, in do_get
    con = self.create_connection()
  File "/var/lib/python-support/python2.5/sqlalchemy/pool.py", line 122, in create_connection
    return _ConnectionRecord(self)
  File "/var/lib/python-support/python2.5/sqlalchemy/pool.py", line 198, in __init__
    self.connection = self.__connect()
  File "/var/lib/python-support/python2.5/sqlalchemy/pool.py", line 261, in __connect
    connection = self.__pool._creator()
  File "/var/lib/python-support/python2.5/sqlalchemy/engine/strategies.py", line 80, in connect
    raise exc.DBAPIError.instance(None, None, e)
sqlalchemy.exc.OperationalError: (OperationalError) FATAL: database "projectb" does not exist
 None None

Hew (hew)
Changed in devscripts (Ubuntu):
importance: Undecided → Medium
Revision history for this message
James McCoy (jamessan) wrote :

This is a transient error that occurs during dinstall runs. The database is temporarily removed and then rebuilt. There is nothing the rmadison script can do about this as the error is occurring on Debian's server, not in devscripts' rmadison script.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.