29 Mar
2012
29 Mar
'12
10:54 p.m.
All,
This may be a bug in the kbarcode database connect code. I configured mysql
and tested kbarcode. The database connect failed using the TQMYSQL3 driver
(selected in kbarcode settings) Has anyone got it working in R14? The error
received was:
Unable to open database: kbarcode
could not connect to server: Connection refused Is the server running on host
"localhost" (::1) and accepting TCP/IP connections on port 5432? could not
connect to server: Connection refused Is the server running on host "localhost"
(127.0.0.1) and accepting TCP/IP connections on port 5432?
The user and pass are properly configured in mysql. I also tested my suse kde3
install and setup connected with the 'QMYSQL3' driver without any problems,
installed the tables and added the example data.
Thoughts? Anybody tested this with the 'TQMYSQL3' driver? Seems the 'T'
driver
prefix may be a bit nebulous...
--
David C. Rankin, J.D.,P.E.
29 Mar
29 Mar
10:58 p.m.
New subject: [trinity-devel] kbarcode - mysql db connect error using TQMYSQL3 driver
On Friday 30 March 2012 01:54:36 David C. Rankin wrote:
All,
This may be a bug in the kbarcode database connect code. I configured
mysql and tested kbarcode. The database connect failed using the TQMYSQL3
driver (selected in kbarcode settings) Has anyone got it working in R14?
The error received was:
Unable to open database: kbarcode
could not connect to server: Connection refused Is the server running on
host "localhost" (::1) and accepting TCP/IP connections on port 5432? could
not connect to server: Connection refused Is the server running on host
"localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432?
The user and pass are properly configured in mysql. I also tested my suse
kde3 install and setup connected with the 'QMYSQL3' driver without any
problems, installed the tables and added the example data.
Thoughts? Anybody tested this with the 'TQMYSQL3' driver? Seems the
'T'
driver prefix may be a bit nebulous...
Actually port 5432 is used by postgresql, not by mysql.
--
Serghei
11:14 p.m.
New subject: [trinity-devel] kbarcode - mysql db connect error using TQMYSQL3 driver
On 03/29/2012 05:58 PM, Serghei Amelian wrote:
Actually port 5432 is used by postgresql, not by
mysql.
copied the 1st message - Same thing happen with mysql - different port...
--
David C. Rankin, J.D.,P.E.
11:20 p.m.
New subject: [trinity-devel] kbarcode - mysql db connect error using TQMYSQL3 driver
On Friday 30 March 2012 02:14:14 David C. Rankin wrote:
On 03/29/2012 05:58 PM, Serghei Amelian wrote:
If the connection is refused, then the database daemon is not running or don't
listen on tcp port.
--
Serghei
Actually port 5432 is used by postgresql, not by
mysql.
copied the 1st message - Same thing happen with mysql - different port...
11:32 p.m.
New subject: [trinity-devel] kbarcode - mysql db connect error using TQMYSQL3 driver
On 03/29/2012 06:20 PM, Serghei Amelian wrote:
If the connection is refused, then the database daemon
is not running or don't
listen on tcp port.
No it's kbardcode this time -- it's broken. I can type 'mysql -uuser -p'
in
konsole and I log right into the database. But running kbarcode, it fails to
connect -- at all.
The setup wizard is also broken. When you click "Test Connection" nothing
happens at all. The only way I generate the error is to set the 'automatically
connect' option, then quit and restart kbarcode.
It's not talking to the database at all.
--
David C. Rankin, J.D.,P.E.
11:36 p.m.
New subject: [trinity-devel] kbarcode - mysql db connect error using TQMYSQL3 driver
On Friday 30 March 2012 02:32:00 David C. Rankin wrote:
On 03/29/2012 06:20 PM, Serghei Amelian wrote:
Try mysql -h 127.0.0.1 -uuser -p
--
Serghei
If the connection is refused, then the database
daemon is not running or
don't listen on tcp port.
No it's kbardcode this time -- it's broken. I can type 'mysql -uuser -p'
in
konsole and I log right into the database. But running kbarcode, it fails
to connect -- at all.
11:59 p.m.
New subject: [trinity-devel] kbarcode - mysql db connect error using TQMYSQL3 driver
On 03/29/2012 06:36 PM, Serghei Amelian wrote:
On Friday 30 March 2012 02:32:00 David C. Rankin
wrote:
localhost works fine, but 127.0.0.1 doesn't:
http://www.3111skyline.com/dl/dt/trinity/ss/kbarcode-mysql.jpg
What gives??
--
David C. Rankin, J.D.,P.E.
On 03/29/2012 06:20 PM, Serghei Amelian wrote:
Try mysql -h 127.0.0.1 -uuser -p
If the connection is refused, then the database
daemon is not running or
don't listen on tcp port.
No it's kbardcode this time -- it's broken. I can type 'mysql -uuser -p'
in
konsole and I log right into the database. But running kbarcode, it fails
to connect -- at all. 
30 Mar
30 Mar
12:04 a.m.
New subject: [trinity-devel] kbarcode - mysql db connect error using TQMYSQL3 driver
On Friday 30 March 2012 02:59:22 David C. Rankin wrote:
On 03/29/2012 06:36 PM, Serghei Amelian wrote:
Your mysql is not listening on tcp port. Open /etc/my.conf and
comment "skip-networking". Also, check if you have "bind-address =
127.0.0.1"
--
Serghei
On Friday 30 March 2012 02:32:00 David C. Rankin
wrote:
localhost works fine, but 127.0.0.1 doesn't:
http://www.3111skyline.com/dl/dt/trinity/ss/kbarcode-mysql.jpg
What gives?? On 03/29/2012 06:20 PM, Serghei Amelian wrote:
Try mysql -h 127.0.0.1 -uuser -p If the connection is refused, then the database
daemon is not running
or don't listen on tcp port.
No it's kbardcode this time -- it's broken. I can type 'mysql -uuser -p'
in konsole and I log right into the database. But running kbarcode, it
fails to connect -- at all.
12:20 a.m.
New subject: [trinity-devel] kbarcode - mysql db connect error using TQMYSQL3 driver
On 03/29/2012 07:04 PM, Serghei Amelian wrote:
Done,
I can log in with mysql -h 127.0.0.1 -uuser -p with no problem at all, but
kbarcode 'Test Connection' still does nothing and will not talk to the database
:(
--
David C. Rankin, J.D.,P.E.
What gives??
Your mysql is not listening on tcp port. Open /etc/my.conf and
comment "skip-networking". Also, check if you have "bind-address =
127.0.0.1"
4670
days inactive
4671
days old
8 comments
2 participants
participants (2)
-
David C. Rankin -
Serghei Amelian