Re: MySQL in TIGER
Re: MySQL in TIGER
- Subject: Re: MySQL in TIGER
- From: Wolfram Stebel <email@hidden>
- Date: Fri, 20 Jan 2006 11:50:25 +0100
- Thread-topic: MySQL in TIGER
Am 20.01.2006 10:00 Uhr schrieb ".::welemski::." unter <email@hidden>:
> Hi,
I really had a big problem in MySQL.
Im running a Tiger server since it
> is built in from the time it was
installed I just
don't have any idea why
> myWebApp can't connect to mysql?
I search through the internet and I found
> many people complaining about
MySQL in Tiger.
Now I have no choice but to
> revert back to Panther. I still would like to go
in Tiger though.
Does anyone
> have a solution for MySQL in Tiger?
--
-- -- -- -- -- -- -- -- -- -- --
> welemski
-- -- -- -- -- -- --
Try the solution in the attached mail
It is a copy of from a thread two days ago.
Wolfram
--- Begin Message ---
- Subject: SOLVED: Re: Urgent: WO error after server update to 10.4.4
- From: Wolfram Stebel <email@hidden>
- Date: Mon, 16 Jan 2006 17:13:07 +0100
- Delivery-date: Mon, 16 Jan 2006 18:52:58 +0100
- Envelope-to: email@hidden
- Thread-topic: SOLVED: Re: Urgent: WO error after server update to 10.4.4
Am 16.01.2006 15:02 Uhr schrieb "Ute Hoffmann" unter
<email@hidden>:
Hallo Ute,
nenn' mir deine Kontonummer! Du hast's mal wieder getroffen.
Continued in english!
As Ute mentioned, there was something on the list short before and i found
it by the magic words (mysql, network) Ute told me!
I should have recognized the tick mark in MySQLManager (Apple startup tool)!
To honor the man who solved it:
>Subject: 10.4.3, mysql, webobjects gotcha
>From: Graham J Lee <email@hidden>
>Date: Fri, 4 Nov 2005 18:29:09 +0000
>Hi all,
>just had a hairy half hour with a load of webobjects instances failing after
You must be glad, i was helpless for hours.
>upgrading to 10.4.3. The problem was that with the software update, rather than
>executing /usr/bin/mysqld_options the MySQL StartupItem now gets its options
>from /usr/bin/ mysqld_manager_options. Its default behaviour is just to
>disallow network connections (it appends the argument --skip-networking to the
>mysqld_safe invocation). JDBC connects over the network even on localhost, so
>none of the instances could connect to the database. To fix this (not sure why
>it was changed in the first place, frankly) edit /etc/mysqlManager.plist and
>change the "no" which appears there to a "yes", then restart MySQL.
>Hope that helps someone,
Indeed it did!!!
Thanks to:
>Graham.
--
Graham Lee GPG Key ID: 01D5B9D8
UNIX Systems Manager,
Oxford Physics Practical Course
http://nextstep.sdf-eu.org 01865 273450
> Hallo Wolfram,
> war da nicht mal ein Thread über geänderte Mysql Privilegien und dass
> der Zugang über das Netz plötzlich inaktiv/aus war. Ich glaube man
> musste im config-File was Network Connection erlauben und mysql neu
> starten...
>
> Vielleicht hilft das was...?
>
> Viele Grüße
>
> Ute
>
> Am Montag, 16.01.06 um 14:27 Uhr schrieb Wolfram Stebel:
>
>> Hi list,
>>
>> i update server to 10.4.4.
>>
>> Starting my applications in monitor results in :
>>
>> ...
>>
>> java.net.SocketException
>> MESSAGE: java.net.ConnectException: Connection refused
>>
>> STACKTRACE:
>>
>> java.net.SocketException: java.net.ConnectException: Connection refused
>> at com.mysql.jdbc.StandardSocketFactory.connect
>> (StandardSocketFactory.java:156)
>> at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:284)
>> ...
>>
>>
>> Last packet sent to the server was 0 ms ago.
>> [2006-01-16 11:52:50 CET] <main> A fatal exception occurred:
>> _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext
>> com.webobjects.eoaccess.EODatabaseContext@c488c: failed to open
>> database channel. Check your connection dictionary, and ensure your
>> database is correctly configured.
>> [2006-01-16 11:52:50 CET] <main> java.lang.IllegalStateException:
>> _obtainOpenChannel -- com.webobjects.eoaccess.EODatabaseContext
>> com.webobjects.eoaccess.EODatabaseContext@c488c: failed to open
>> database channel. Check your connection dictionary, and ensure your
>> database is correctly configured.
>> at com.webobjects.eoaccess.EODatabaseContext._obtainOpenChannel
>> (EODatabaseContext.java:2131)
>>
>>
>> ------
>>
>>
>> i'm able to connect with MySQLAdministrator and manually with the user
>> and
>> password the application uses.
>> i tried a new jdbc driver.
>> i have my.cnf in /etc/:
>>
>> [mysqld]
>> datadir=/Volumes/Sonne-Data/mySQL-Data
>> pid-file=/Volumes/Sonne-Data/mySQL-Data/Sonne.local.pid
>> socket=/var/mysql/mysql.sock
>> port=3306
>> character-set-server=latin1
>> collation-server=latin1_german1_ci
>>
>>
>> [mysql.server]
>> basedir=/usr/bin
>>
>> -------
>>
>> Any tips?
>>
>> Please hurry :-)
>>
>> Wolfram
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
--- End Message ---
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden