Alle 14:05, luned� 24 gennaio 2005, Henri Kaukola ha scritto: > Yes, after installation, there should be tables in it > (like article, topic, snippet, etc.). Yes, the tables > must be inside the db before running import with datagard.
How can I create those tables now? Do I have to re-install Midgard? Do I have to run any SQL dump script that came with the distribution? Can I proceed without creating the tabels and rely on the fact that Datagard/Repligard will take care of creating them at the next run? > So it shouldn't be the MySQL end that is lacking but > the Midgard end - the error message is basically saying that > there's no user with the username/password defined in <login /> > in repligard.conf. As long as I can see, there are 3 different users involved with the communication between Midgard and MySQL: - midgard, apparently used to access the midgard database during the normal run - admin, apparently used by Repligard to create and manage the DB tables during the install/import stage - SG0, used as a sitegroup administrator (I have not had the opportunity to use it, yet) Which of them is the one to be used for this Datagard "import" operation? I tried to run datagard using all of these 3 different user profiles against the midgard database (and cross checking that they have access to the midgard db using the MySQL client). In all of the 3 cases I have got the same "midgard critical: error logging into the database" message. The user SG0 cannot access the db just because I do not know the default password associated with this username... (I'm sure it is written somewhere but I did not find it...:-( ) > Try to import the SG0 administrator account with the following command: > > repligard -c /etc/midgard/repligard.conf -a -i > /usr/local/share/midgard/admin_user.xml > > (everything on one line, the path's may vary!) No way: I have got the usual nessage: debian:~# repligard -c /etc/midgard/repligard.conf -a -i /usr/share/midgard/admin_user.xml repligard-Message: Reading config file /etc/midgard/repligard.conf repligard-CRITICAL **: Error logging into Database debian:~# > You can enable Midgard logging by placing the following to > the Midgard VHost configuration: > > MidgardLog Debug+ /var/log/midgard.log I tried. No log files were created and/or written during the next datagard run. > Midgard is an Apache module. So you must make the Apache > to Listen to each port where you want to run Midgard. > Midgard will steal the reguest from Apache if the Vhost > configuration and host-table in the Midgard db match > with the reguest. I tried but I was unable to stop and restart apache2. It complains that the ports are already in use. Now, I tried to shutdown the PC and restart with mandrake (that I'm using to write you). I will tell you weather apache2 will be able to listen on these ports after the next Debian boot. Thanks again --------------------------------- Alessandro Bottoni --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
