Wikimedia Bugzilla is closed!

Me again adding commentary: 
This is on an Intel mac OS X Server machine.
The installation show above successfully creates the wikidb database in mySql (v.4.1.13) and creates the user 'wikiuser' and gives 
it access to the new db.  But it does not create the LocalSettings.php file as it claims:
            "After setup, a file called LocalSettings.php is created in the "config" directory."

I've seen similar posts before, but no solutions.  I saw a similar post dismissed as a "configuration problem", but this can't be a 
configuration problem because I haven't even gotten to the configuration step yet, and php and mySql are otherise perfectly ok.

please help?

You might want to investigate the connection problem, for instance by trying to connect 
to the database with the parameters you gave.

Filer of bug has given no additional information a week after the bug was filed;
and there's no evidence this is a MediaWiki software issue. Resolving as INVALID.

I can connect to the database with the command line

mysql --user=wikiuser -p

which prompts me for the password, or by supplying the password with 

mysql --user=wikiuser --password=<password>

But apparently this is not how the wiki attempts to access the database.

When I reinstall using the webpage http://myhostname/wiki, it seems to be happy, detecting that the database is 
already set up, but then I get the same mysterious connection error at the end.  Can someone tell me how mediawiki is 
trying to connect to the database?  Thanks.
-------------------
MediaWiki 1.8.2 Installation

Don't forget security updates! Keep an eye on the low-traffic release announcements mailing list.
Checking environment...

Please include all of the lines below when reporting installation problems.
PHP 5.1.6 installed
Found database drivers for: MySQL PostgreSQL
PHP server API is apache; ok, using pretty URLs (index.php/Page_Title)
Have XML / Latin1-UTF-8 conversion support.
PHP is configured with no memory_limit.
Have zlib support; enabling output compression.
Couldn't find Turck MMCache, eAccelerator or APC. Object caching functions cannot be used.
Found GNU diff3: /usr/bin/diff3.
Found GD graphics library built-in, image thumbnailing will be enabled if you enable uploads.
Installation directory: /Library/WebServer/Documents/wiki
Script URI path: /wiki
Environment checked. You can install MediaWiki.
Generating configuration file...
Database type: MySQL
Loading class: DatabaseMysql
Attempting to connect to database server as root...success.
Connected to 4.1.13a-log
Database wikidb exists
There are already MediaWiki tables in this database. Checking if updates are needed...
Granting user permissions...
...hitcounter table already exists.
...querycache table already exists.
...objectcache table already exists.
...categorylinks table already exists.
...logging table already exists.
...user_newtalk table already exists.
...transcache table already exists.
...trackbacks table already exists.
...externallinks table already exists.
...job table already exists.
...langlinks table already exists.
...querycache_info table already exists.
...filearchive table already exists.
...have ipb_id field in ipblocks table.
...have ipb_expiry field in ipblocks table.
...have rc_type field in recentchanges table.
...have rc_ip field in recentchanges table.
...have rc_id field in recentchanges table.
...have rc_patrolled field in recentchanges table.
...have user_real_name field in user table.
...have user_token field in user table.
...have user_email_token field in user table.
...have user_registration field in user table.
...have log_params field in logging table.
...have ar_rev_id field in archive table.
...have ar_text_id field in archive table.
...have page_len field in page table.
...have rev_deleted field in revision table.
...have img_width field in image table.
...have img_metadata field in image table.
...have img_media_type field in image table.
...have ss_total_pages field in site_stats table.
...have iw_trans field in interwiki table.
...have ipb_range_start field in ipblocks table.
...have ss_images field in site_stats table.
...have ipb_anon_only field in ipblocks table.
...already have interwiki table
...indexes seem up to 20031107 standards
Already have pagelinks; skipping old links table updates.
...image primary key already set.
The watchlist table is already set up for email notification.
...watchlist talk page rows already present
...user table does not contain old email authentication field.
Logging table has correct title encoding.
...page table already exists.
revision timestamp indexes already up to 2005-03-13
...rev_text_id already in place.
...page_namespace is already a full int (int(11)).
...ar_namespace is already a full int (int(11)).
...rc_namespace is already a full int (int(11)).
...wl_namespace is already a full int (int(11)).
...qc_namespace is already a full int (int(11)).
...log_namespace is already a full int (int(11)).
...already have pagelinks table.
...templatelinks table already exists
No img_type field in image table; Good.
Already have unique user_name index.
...user_groups table already exists.
...user_groups is in current format.
...wl_notificationtimestamp is already nullable.
...timestamp key on logging already exists.
Setting page_random to a random value on rows where it equals 0...changed 0 rows
Checking for additional recent changes indices...
...seems to be ok
Initialising "MediaWiki" namespace for language code en...
DB connection error: Unknown error (<my hostname>)

Check the error log; MediaWiki uses the standard PHP libraries depending upon
the driver in use.

Changing the priority down. This is NOT really a software issue - it's more
support for a customer who hasn't got their environment set up right.

> Check the error log; MediaWiki uses the standard PHP libraries depending upon
> the driver in use.

Where is the error log?

See http://www.php.net/manual/en/ref.errorfunc.php#ini.error-log.

(In reply to comment #7)
> Changing the priority down. This is NOT really a software issue - it's more
> support for a customer who hasn't got their environment set up right.

Closing as INVALID. No response from customer in over 2 years, and it wasn't really a bug in the software to begin with.