search

kerberos-io / web

(DEPRECATED) An open source GUI to configure the machinery and to view events that were detected by the machinery.
https://www.kerberos.io
225 stars 69 forks source link

API system/os call returning error, system page blocked in spinner #153

Closed dschuetz closed 4 years ago

dschuetz commented 4 years ago

I moved my setup from one intel NUC to another, and now the system page (System and Kerberos.io blocks) won't display.

I'm using the kerberos-io docker image, and everything else seems to be working fine. If I dig into the web page, I see it's pulling data from:

and when I try to fetch that directly, I get the following error:

(1/1) UnexpectedValueExceptionThe Response content must be a string or object implementing __toString(), "boolean" given.

in Response.php line 388 at Response->setContent(false)in Response.php line 41

at Response->setContent(false)in Response.php line 201

at Response->__construct(array('system' => object(LinuxSystem), 'uptime' => '18 hours, 47 minutes, 5 seconds', 'board' => '', 'model' => '��������������������������������� (Intel Corporation NUC5i5RYB)', 'os' => 'Linux', 'kernel' => '4.15.0-64-generic', 'hostname' => '1a2cb1ad181b', 'numberOfCPU' => 4, 'cpu' => array(array('Vendor' => 'GenuineIntel', 'Model' => 'Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz'

It's looking like (perhaps?) the string of unicode or whatnot at the beginning of the "model" field is breaking the __construct() call, which then returns a "false"?

The other NUC is the same model (5i5RYB), but differs in the underlying OS (the system it's working on is Ubuntu 16.04, the one which shows the bug is 18.04).

dschuetz commented 4 years ago

Okay, I think I found the problem, and it's way out of your control. :(

The DMI data being returned on the system is messed up. Specifically:

$ cat /sys/devices/virtual/dmi/id/product_name ????????????????????????????????? $

So my immediate problem is figuring out how to change the DMI / SMBIOS data, which may involve booting off some windows USB stick and doing..god only knows what.

The next step is for me to report this as a bug to the maintainer of Linfo.

Anyway, thanks for the great system, and I look forward to the next version (coming real soon, I hope?)