Hi Adam,

I have checked the output from the debug which is attached in link below and indeed ifHC values for ALL PORTS are returning as 0

BUT this doesnt explain why it works on my old setup no problem, that has values and graphs?

And why it doesnt work on the new setup?

Only different is im using ARM instead of x64 and stable release instead of rolling?

Also why is it detecting only first 4 ports as 64bit?

Any ideas?

Regards

Simon - Hestor Ltd

On 8 Mar 2021, at 15:13, Adam Armstrong via observium observium@observium.org wrote:

Probably dumb tplink device returning empty HC counters for those ports.

Walk ifHC[In|Out]Octets.

Adam.

From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org> On Behalf Of Simon Smith via observium Sent: 08 March 2021 15:11 To: Observium <observium@observium.org mailto:observium@observium.org> Cc: Simon Smith <simonsmith5521@gmail.com mailto:simonsmith5521@gmail.com> Subject: [Observium] No graphs for 64bit network ports on arm

Hi All,

Ive spotted a few weird issue with my new setup running on arm?

1. The first 4 ports on our TPLink switches are being detected as 64Bit and then the rest of the ports are 32Bit ?
2. the 64bit graphs are showing 0 for everything, even though the output from the command line shows stats? (See https://pastebin.com/raw/qP4T1Fa9 https://pastebin.com/raw/qP4T1Fa9)
3. The graphs are being generated so the RRDs are fine, but the graphs are blank?

Regards

Simon _______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

Hi Adam,

That sounds ok, what’s the query I need to sorts run/check in the database?

Regards

Simon

On 8 Mar 2021, at 15:33, Adam Armstrong via observium observium@observium.org wrote:

Dunno. Once something is set to 64bit counters it’ll never go back, else they’d flipflop like crazy during network issues.

It’s likely that it returned non-zero counters for these ports for one poll or something like that. You can manually remove the 64bit flag in the database for these ports.

Adam.

From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org> On Behalf Of Simon Smith via observium Sent: 08 March 2021 15:19 To: Observium <observium@observium.org mailto:observium@observium.org> Cc: Simon Smith <simonsmith5521@gmail.com mailto:simonsmith5521@gmail.com> Subject: Re: [Observium] No graphs for 64bit network ports on arm

Hi Adam,

I have checked the output from the debug which is attached in link below and indeed ifHC values for ALL PORTS are returning as 0

BUT this doesnt explain why it works on my old setup no problem, that has values and graphs?

And why it doesnt work on the new setup?

Only different is im using ARM instead of x64 and stable release instead of rolling?

Also why is it detecting only first 4 ports as 64bit?

Any ideas?

Regards

Simon - Hestor Ltd

...

On 8 Mar 2021, at 15:13, Adam Armstrong via observium <observium@observium.org mailto:observium@observium.org> wrote:

Probably dumb tplink device returning empty HC counters for those ports.

Walk ifHC[In|Out]Octets.

Adam.

From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org> On Behalf Of Simon Smith via observium Sent: 08 March 2021 15:11 To: Observium <observium@observium.org mailto:observium@observium.org> Cc: Simon Smith <simonsmith5521@gmail.com mailto:simonsmith5521@gmail.com> Subject: [Observium] No graphs for 64bit network ports on arm

Hi All,

Ive spotted a few weird issue with my new setup running on arm?

1. The first 4 ports on our TPLink switches are being detected as 64Bit and then the rest of the ports are 32Bit ?
2. the 64bit graphs are showing 0 for everything, even though the output from the command line shows stats? (See https://pastebin.com/raw/qP4T1Fa9 https://pastebin.com/raw/qP4T1Fa9)
3. The graphs are being generated so the RRDs are fine, but the graphs are blank?

Regards

Simon _______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

---

observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

Hi,

So it appears after changing the version from 2c to 1 its now showing all the data correctly!

Who knows? Weird devices

Regards

Simon

On 8 Mar 2021, at 15:33, Adam Armstrong via observium observium@observium.org wrote:

Dunno. Once something is set to 64bit counters it’ll never go back, else they’d flipflop like crazy during network issues.

It’s likely that it returned non-zero counters for these ports for one poll or something like that. You can manually remove the 64bit flag in the database for these ports.

Adam.

From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org> On Behalf Of Simon Smith via observium Sent: 08 March 2021 15:19 To: Observium <observium@observium.org mailto:observium@observium.org> Cc: Simon Smith <simonsmith5521@gmail.com mailto:simonsmith5521@gmail.com> Subject: Re: [Observium] No graphs for 64bit network ports on arm

Hi Adam,

I have checked the output from the debug which is attached in link below and indeed ifHC values for ALL PORTS are returning as 0

BUT this doesnt explain why it works on my old setup no problem, that has values and graphs?

And why it doesnt work on the new setup?

Only different is im using ARM instead of x64 and stable release instead of rolling?

Also why is it detecting only first 4 ports as 64bit?

Any ideas?

Regards

Simon - Hestor Ltd

...

On 8 Mar 2021, at 15:13, Adam Armstrong via observium <observium@observium.org mailto:observium@observium.org> wrote:

Probably dumb tplink device returning empty HC counters for those ports.

Walk ifHC[In|Out]Octets.

Adam.

From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org> On Behalf Of Simon Smith via observium Sent: 08 March 2021 15:11 To: Observium <observium@observium.org mailto:observium@observium.org> Cc: Simon Smith <simonsmith5521@gmail.com mailto:simonsmith5521@gmail.com> Subject: [Observium] No graphs for 64bit network ports on arm

Hi All,

Ive spotted a few weird issue with my new setup running on arm?

1. The first 4 ports on our TPLink switches are being detected as 64Bit and then the rest of the ports are 32Bit ?
2. the 64bit graphs are showing 0 for everything, even though the output from the command line shows stats? (See https://pastebin.com/raw/qP4T1Fa9 https://pastebin.com/raw/qP4T1Fa9)
3. The graphs are being generated so the RRDs are fine, but the graphs are blank?

Regards

Simon _______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

---

observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

Hi All

Ive now spotted all these errors inside the output of poller.php for the devices now?

1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 1 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 1 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 2 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 2 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 3 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 3 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 4 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 4 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 5 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 5 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 6 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 6 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 7 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 7 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 8 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 8 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 9 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 9

Any ideas?

Regards

Simon

On 8 Mar 2021, at 15:33, Adam Armstrong via observium observium@observium.org wrote:

Dunno. Once something is set to 64bit counters it’ll never go back, else they’d flipflop like crazy during network issues.

It’s likely that it returned non-zero counters for these ports for one poll or something like that. You can manually remove the 64bit flag in the database for these ports.

Adam.

From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org> On Behalf Of Simon Smith via observium Sent: 08 March 2021 15:19 To: Observium <observium@observium.org mailto:observium@observium.org> Cc: Simon Smith <simonsmith5521@gmail.com mailto:simonsmith5521@gmail.com> Subject: Re: [Observium] No graphs for 64bit network ports on arm

Hi Adam,

I have checked the output from the debug which is attached in link below and indeed ifHC values for ALL PORTS are returning as 0

BUT this doesnt explain why it works on my old setup no problem, that has values and graphs?

And why it doesnt work on the new setup?

Only different is im using ARM instead of x64 and stable release instead of rolling?

Also why is it detecting only first 4 ports as 64bit?

Any ideas?

Regards

Simon - Hestor Ltd

...

On 8 Mar 2021, at 15:13, Adam Armstrong via observium <observium@observium.org mailto:observium@observium.org> wrote:

Probably dumb tplink device returning empty HC counters for those ports.

Walk ifHC[In|Out]Octets.

Adam.

From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org> On Behalf Of Simon Smith via observium Sent: 08 March 2021 15:11 To: Observium <observium@observium.org mailto:observium@observium.org> Cc: Simon Smith <simonsmith5521@gmail.com mailto:simonsmith5521@gmail.com> Subject: [Observium] No graphs for 64bit network ports on arm

Hi All,

Ive spotted a few weird issue with my new setup running on arm?

1. The first 4 ports on our TPLink switches are being detected as 64Bit and then the rest of the ports are 32Bit ?
2. the 64bit graphs are showing 0 for everything, even though the output from the command line shows stats? (See https://pastebin.com/raw/qP4T1Fa9 https://pastebin.com/raw/qP4T1Fa9)
3. The graphs are being generated so the RRDs are fine, but the graphs are blank?

Regards

Simon _______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

---

observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

Hi

No it’s a standard Ubuntu 20.04 setup using the observium script

Regards

Simon

Sent from my iPhone

On 8 Mar 2021, at 19:15, Adam Armstrong via observium observium@observium.org wrote:

 Very new versions of mariadb?

Let me do a guess. Debian?

What’s with all these dumbass projects introducing changes that break things?

Adam.

From: observium observium-bounces@observium.org On Behalf Of Simon Smith via observium Sent: 08 March 2021 18:17 To: Observium observium@observium.org Cc: Simon Smith simonsmith5521@gmail.com Subject: Re: [Observium] No graphs for 64bit network ports on arm

Hi All

Ive now spotted all these errors inside the output of poller.php for the devices now?

1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1287: 'VALUES function' is deprecated and will be removed in a future release. Please use an alias (INSERT INTO ... VALUES (...) AS alias) and replace VALUES(col) in the ON DUPLICATE KEY UPDATE clause with alias.col instead 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 1 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 1 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 2 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 2 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 3 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 3 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 4 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 4 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 5 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 5 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 6 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 6 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 7 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 7 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 8 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 8 1366: Incorrect integer value: '' for column 'ifOutErrors' at row 9 1366: Incorrect integer value: '' for column 'ifInDiscards' at row 9

Any ideas?

Regards

Simon

On 8 Mar 2021, at 15:33, Adam Armstrong via observium observium@observium.org wrote:

Dunno. Once something is set to 64bit counters it’ll never go back, else they’d flipflop like crazy during network issues.

It’s likely that it returned non-zero counters for these ports for one poll or something like that. You can manually remove the 64bit flag in the database for these ports.

Adam.

From: observium observium-bounces@observium.org On Behalf Of Simon Smith via observium Sent: 08 March 2021 15:19 To: Observium observium@observium.org Cc: Simon Smith simonsmith5521@gmail.com Subject: Re: [Observium] No graphs for 64bit network ports on arm

Hi Adam,

I have checked the output from the debug which is attached in link below and indeed ifHC values for ALL PORTS are returning as 0

BUT this doesnt explain why it works on my old setup no problem, that has values and graphs?

And why it doesnt work on the new setup?

Only different is im using ARM instead of x64 and stable release instead of rolling?

Also why is it detecting only first 4 ports as 64bit?

Any ideas?

Regards

Simon - Hestor Ltd

On 8 Mar 2021, at 15:13, Adam Armstrong via observium observium@observium.org wrote:

Probably dumb tplink device returning empty HC counters for those ports.

Walk ifHC[In|Out]Octets.

Adam.

From: observium observium-bounces@observium.org On Behalf Of Simon Smith via observium Sent: 08 March 2021 15:11 To: Observium observium@observium.org Cc: Simon Smith simonsmith5521@gmail.com Subject: [Observium] No graphs for 64bit network ports on arm

Hi All,

Ive spotted a few weird issue with my new setup running on arm?

1. The first 4 ports on our TPLink switches are being detected as 64Bit and then the rest of the ports are 32Bit ?
2. the 64bit graphs are showing 0 for everything, even though the output from the command line shows stats? (See https://pastebin.com/raw/qP4T1Fa9)
3. The graphs are being generated so the RRDs are fine, but the graphs are blank?

Regards

Simon _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

---

observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

---

observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium