ifmonitor broken by mysql RH9 errata and FC1

[Warren Togami]

https://bugzilla.fedora.us/show_bug.cgi?id=946

http://videl.ics.hawaii.edu/~warren/fedora/ifmonitor-0.30-0.fdr.3.src.rpm
http://videl.ics.hawaii.edu/~warren/fedora/md5sums.asc

ifmonitor is a very simple MySQL + PHP bandwidth monitor for Linux hosts. A
simple C daemon stores your bandwidth usage in a MySQL table, and the bandwidth
data can be viewed with a simple PHP web interface.

Known Problem:
ifmonitor fails to insert data into mysql-3.23.56-1.9 from RH9 Errata and
mysql-3.23.58-4 from FC1. The original mysql-3.23.54a-11 from RH9 stock works
fine with ifmonitor.

The upstream author does not have any Red Hat boxes or time so he cannot look at
the problem. Any ideas?

Warren Togami
***@togami.com

[Lamar Owen]

Post by Warren Togami
ifmonitor is a very simple MySQL + PHP bandwidth monitor for Linux hosts.
A simple C daemon stores your bandwidth usage in a MySQL table, and the
bandwidth data can be viewed with a simple PHP web interface.
ifmonitor fails to insert data into mysql-3.23.56-1.9 from RH9 Errata and
mysql-3.23.58-4 from FC1. The original mysql-3.23.54a-11 from RH9 stock
works fine with ifmonitor.

Does mysql have an equivalent to PostgreSQL's tcpip_socket config setting?
That is, can the server daemon be set to not listen to TCP/IP ports and only
to a unix domain socket? This sort of complaint is common with PostgreSQL;
the canonical answer is to set tcpip_socket=true. No, I don't use mysql.
PostgreSQL does everything I need; but the concept is similar.

What does netstat -a --inet say with the FC1/RH9update mysql running? Diff to
the RH9 stock?

[Warren Togami]

Post by Lamar Owen

Post by Warren Togami
ifmonitor fails to insert data into mysql-3.23.56-1.9 from RH9 Errata and
mysql-3.23.58-4 from FC1. The original mysql-3.23.54a-11 from RH9 stock
works fine with ifmonitor.

Does mysql have an equivalent to PostgreSQL's tcpip_socket config setting?
That is, can the server daemon be set to not listen to TCP/IP ports and only
to a unix domain socket? This sort of complaint is common with PostgreSQL;
the canonical answer is to set tcpip_socket=true. No, I don't use mysql.
PostgreSQL does everything I need; but the concept is similar.
What does netstat -a --inet say with the FC1/RH9update mysql running? Diff to
the RH9 stock?

Doesn't appear to be any difference between the two with netstat.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=109536
Filed in Bugzilla

Warren