-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello Alessandro,
alessandro bottoni wrote:
| 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? |
No need to re-install. Just run datagard again, and use the Install option. AFAIK, the Import (which is used to install Midgard applications) will not do any modifications to the targeted db.
However, the Import will create a temporary db for MultiLang conversion.
Piotras, what account is the datagard using to create the temp db and blobdirs? Where is it accessible? I'm thinking that the problem might lie there...
| As long as I can see, there are 3 different users involved with the | communication between Midgard and MySQL:
Actually, there are two kinds of accounts.
| - midgard, apparently used to access the midgard database during the normal | run
The MySQL db account - an account used to access the db itself. This can be set in the Apache VirtualHost configurations with the MidgardDatabase command.
| - admin, apparently used by Repligard to create and manage the DB tables | during the install/import stage
As Piotras explained, this is a Midgard user account. The default system administrator account credentials are admin/password. FYI: This user account is often called as SG0 admin.
| - SG0, used as a sitegroup administrator (I have not had the opportunity to | use it, yet)
Some confusion here. :) The SG0 = Sitegroup 0, that being the "magical" system db of the Midgard installations. Basically, all Midgard applications (like Aegir or Spider-admin) are installed to the SG0. As soon as you get Midgard fully operational, you'll understand this one. ;)
| Which of them is the one to be used for this Datagard "import" operation?
Well, both. You need the db account to access the db in the first place. Then you'll need the Midgard SG0 admin account to import the application.
| 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...:-( )
The correct SG0 Midgard administrator account is: admin / password
|>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:~#
In case the db is totally empty (no tables created), I guess this might make sense. If the datagard's Install option is failing, you could create the db by hand.
You should find an empty SQL dump in the same dir you have the admin_user.xml file.
# mysql -u midgard -p midgard < empty.sql
After that, run datagard and use the Upgrade option to convert your db into MultiLang format.
| |>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. |
This is correct. The Datagard itself is not using Apache to access the Midgard, so there cannot be anything in the log.
|>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.
Ah, there was some trick for the Apache2 in this sense. Help, anyone???
| Thanks again | | --------------------------------- | Alessandro Bottoni
Cheers!
~ //Henri
- -- Henri Kaukola [EMAIL PROTECTED] Consultant Tel: +358-20-198 6037 Nemein Oy http://www.nemein.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB9fDe3xWc2AolrKgRAs8oAJ9yeYCr6Io3r99FYXrKjhUy5J3GhwCg09T2 BOI52DLPMvW9iYzHF+/asV8= =G2XL -----END PGP SIGNATURE-----
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
