Description of problem: When i excuted spacewalk-setup several times. The database seems began to fail to work.It just stucked and no errors show up. * Loading answer file: /home/thomasking/spacewalkanswerfile. ** Database: Setting up database connection for PostgreSQL backend. ** Database: Populating database. The Database has schema. Would you like to clear the database [Y]? y ** Database: Clearing database. NOTICE: schema "rpm" does not exist, skipping NOTICE: schema "rhn_exception" does not exist, skipping NOTICE: schema "rhn_quota" does not exist, skipping NOTICE: schema "rhn_config" does not exist, skipping NOTICE: schema "rhn_server" does not exist, skipping NOTICE: schema "rhn_entitlements" does not exist, skipping NOTICE: schema "rhn_bel" does not exist, skipping NOTICE: schema "rhn_cache" does not exist, skipping NOTICE: schema "rhn_channel" does not exist, skipping NOTICE: schema "rhn_config_channel" does not exist, skipping NOTICE: schema "rhn_org" does not exist, skipping NOTICE: schema "rhn_user" does not exist, skipping these schemas' unexisting is because i execute the spacewalk-setup a second time. In the first time, it delete all these schemas above. then Stucked. Because some of the schemas has been deleted, then it shows that they are not existed. And again, it stucked. Version-Release number of selected component (if applicable): spacewalk 1.6 postgresql 8.4.7 How reproducible: I just execute spacewalk-setup several times, because my tomcat always shows some error. Then the database failed. When i setup a new database with the below words, it seems to be corrected, and works fine. su - postgres -c 'PGPASSWORD=spacepw; createdb dba ; createlang plpgsql dba ; yes $PGPASSWORD | createuser -P -sDR namea' But still, after resetup the spacewalk-setup 2 or 3 times, the problem showed up again. Actual results: In the populate_db.log, i found nothing. Expected results: Additional info:
Note that when i delete the db and db user by typing dropdb and dropdbuser, it works again. so, i am not sure whether there is something wrong about the spacewalk's scripts.
These are not errors. You should really investigate the cause that lead to this, which is that something got stuck. Check the PostgreSQL log and see what is the problem in the first place.
Ok, My finding is that: The database may not be deleted clearly by spacewalk, since if i deleted the db and db user manuly, it works fine. but if i use the spacewalk script, it stucked. (In reply to comment #2) > These are not errors. > You should really investigate the cause that lead to this, which is that > something got stuck. Check the PostgreSQL log and see what is the problem in > the first place.
(In reply to comment #3) > Ok, My finding is that: > The database may not be deleted clearly by spacewalk, since if i deleted > the db and db user manuly, it works fine. but if i use the spacewalk script, it > stucked. And this is what will need to be investigated, not the fact that you get those notices from subsequent cleanup run.