forum : mysql4.1.22 error

You must be logged in to post Login Register

Forums Kontrollbase – issues and solutions mysql4.1.22 error

mysql4.1.22 error
Page:   1  
UserPost

3:03 am
December 21, 2009


mandys

New Member

posts 1
1

Hi,

I know that mysql 4.x is not officially supported and I might be expecting too much here, but due to legacy reasons I cannot migrate to mysql 5.x just yet.

I followed the instructions and got everything setup (ssh is working fine so is the online tool).

Running the crons gives me the following error (I am sure it’s to do with mysql 4.x schema)

However, I am running mysql 4.1.22 (I can’t upgrade to mysql 5.x immediately due to legacy reasons)

But, now I am getting somewhere with this:

This is the error I get on the server script:

[kontrollbase@105951 bin]$ ./kontroll-server_loop-5.0.x_linux-x86-2.0.1.pl
2009-12-19 02:11:50 | DEBUG | server-loop-5.0.x_linux-x86: LOG TRUNCATED
2009-12-19 02:11:50 | DEBUG | server-loop-5.0.x_linux-x86: #### server-loop process start

EXEC kontroll-client-5.0.x_linux-x86-2.0.1.pl client script for host: localhost kontrollbase@127.0.0.1
EXEC stats gather script for host: localhost kontrollbase@127.0.0.1 active: 1
2009-12-19 02:11:51 | DEBUG | stats-gather-5.0.x_linux-x86: ## process start
2009-12-19 02:11:51 | DEBUG | stats-gather-5.0.x_linux-x86: 105951.105951-db1.votigo.com [starting]
2009-12-19 02:11:51 | DEBUG | stats-gather-5.0.x_linux-x86: 105951.105951-db1.votigo.com xml datetime = 2009-12-19 02:11:50
2009-12-19 02:11:51 | DEBUG | stats-gather-5.0.x_linux-x86: error = ‘You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near \’status\’ at line 1 ‘
2009-12-19 02:11:51 | DEBUG | stats-gather-5.0.x_linux-x86: error type = mysql
Illegal division by zero at ./kontroll-stats-gather-5.0.x_linux-x86-2.0.1.pl line 1642.
2009-12-19 02:11:52 | DEBUG | server-loop-5.0.x_linux-x86: #### server-loop process end
[kontrollbase@105951 bin]$

Reporter gives the following error:

[kontrollbase@105951 bin]$ ./kontroll-reporter-5.0.x_linux-x86-2.0.1.pl
Useless use of private variable in void context at ./kontroll-reporter-5.0.x_linux-x86-2.0.1.pl line 138.
Useless use of private variable in void context at ./kontroll-reporter-5.0.x_linux-x86-2.0.1.pl line 138.
2009-12-19 02:13:05 | DEBUG | reporter-5.0.x_linux-x86: #### reporter process start
2009-12-19 02:13:05 | DEBUG | reporter-5.0.x_linux-x86: working on test,14, localhost

Argument “You have an error in your SQL syntax; check the manual t…” isn’t numeric in numeric eq (==) at ./kontroll-reporter-5.0.x_linux-x86-2.0.1.pl line 2009.
2009-12-19 02:13:05 | DEBUG | reporter-5.0.x_linux-x86: truncating tmp/kontrollbase-reporter-2009-12-19021304.log
######################ENTERED report
2009-12-19 02:13:05 | DEBUG | reporter-5.0.x_linux-x86: #### reporter process end
[kontrollbase@105951 bin]$

I am hoping that even though mysql 4.x is not officially supported by you this could be “probably” a small change that you can advise me on how to fix and then we can add it to your troubleshooting section ?

Let me know.

Thanks,
Mandy.

12:31 pm
January 5, 2010


themattreid

Admin

Nevada

posts 52
2

MySQL 4.x is, somewhat unfortunately, never going to be supported because it lacks the INFORMATION_SCHEMA so pulling lots of vital information about the client servers is not possible and would require a new function to handle the table/schema information gathering via 'show table status' and schema looping to gather the necessary data. Tests have also shown that the schema loop and 'show table status' method is a good 10x slower than polling from INFORMATION_SCHEMA. That slower method impacts polling time on servers with many schemas or many tables or a combination of the two, which then impacts the overall polling process since it is currently a serial method and not parallel – so one server with a long polling time using the old method will end up slowing the whole data gathering business down and potentially over-run the 5 minute polling interval… etc etc. 


Basically there are good reasons 4.x isn't supported from a technical standpoint but the biggest reason is that 4.x is several years out of support and really shouldn't be used in production anymore either. In addition, official 5.0.x support from MySQL ended 2010-01-01 so you should be using 5.1.x from here on out. 

http://kontrollsoft.com http://themattreid.com
Page:   1  
 

About the kontrollsoft forum

Most Users Ever Online:

9


Currently Online:

6 Guests

Forum Stats:

Groups: 3

Forums: 12

Topics: 43

Posts: 93

Membership:

There are 539 Members

There has been 1 Guest

There is 1 Admin

There are 0 Moderators

Top Posters:

xstar – 16

Prabhat – 3

Brince – 3

massoo – 2

j2ict – 2

christian.keil – 2

Administrators: themattreid (52 Posts)