boagent
boagent copied to clipboard
Published
20 hours ago •
Boavizta
Boavizta
Error in parsing disks
On a Hetzner server with two SSDs in RAID1, I get a 500 Error when it's trying to sort the disks to prepare for the Boavizta API call.
I included the JSON from hardware_info below for debugging:
{
"disks": [
{
"capacity": 476,
"manufacturer": "SAMSUNG",
"type": "ssd"
},
{
"capacity": 476,
"manufacturer": "SAMSUNG",
"type": "ssd"
}
],
"cpus": [
{
"vendor": "GenuineIntel",
"name": "13th Gen Intel(R) Core(TM) i5-13500\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000",
"microarch": [
"nehalem",
""
],
"vector_instructions": {
"sse": "Yes",
"sse2": "Yes",
"sse3": "Yes",
"ssse3": "Yes",
"sse4.1": "Yes",
"sse4.2": "Yes",
"sse4a": "--",
"avx": "Yes",
"avx2": "--",
"bmi1": "--",
"bmi2": "--"
},
"cpu_info": {
"python_version": "3.10.12.final.0 (64 bit)",
"cpuinfo_version": [
9,
0,
0
],
"cpuinfo_version_string": "9.0.0",
"arch": "X86_64",
"bits": 64,
"count": 20,
"arch_string_raw": "x86_64",
"vendor_id_raw": "GenuineIntel",
"brand_raw": "13th Gen Intel(R) Core(TM) i5-13500",
"hz_advertised_friendly": "2.5000 GHz",
"hz_actual_friendly": "2.5000 GHz",
"hz_advertised": [
2500000000,
0
],
"hz_actual": [
2500000000,
0
],
"stepping": 2,
"model": 191,
"family": 6,
"flags": [
"3dnowprefetch",
"abm",
"acpi",
"adx",
"aes",
"aperfmperf",
"apic",
"arat",
"arch_capabilities",
"arch_lbr",
"arch_perfmon",
"art",
"avx",
"avx2",
"avx_vnni",
"bmi1",
"bmi2",
"bts",
"clflush",
"clflushopt",
"clwb",
"cmov",
"constant_tsc",
"cpuid",
"cpuid_fault",
"cx16",
"cx8",
"de",
"ds_cpl",
"dtes64",
"dtherm",
"dts",
"epb",
"ept",
"ept_ad",
"erms",
"est",
"f16c",
"flexpriority",
"flush_l1d",
"fma",
"fpu",
"fsgsbase",
"fsrm",
"fxsr",
"gfni",
"ht",
"hwp",
"hwp_act_window",
"hwp_epp",
"hwp_notify",
"hwp_pkg_req",
"ibpb",
"ibrs",
"ibrs_enhanced",
"ida",
"intel_pt",
"invpcid",
"invpcid_single",
"lahf_lm",
"lm",
"mca",
"mce",
"md_clear",
"mmx",
"monitor",
"movbe",
"movdir64b",
"movdiri",
"msr",
"mtrr",
"nonstop_tsc",
"nopl",
"nx",
"ospke",
"osxsave",
"pae",
"pat",
"pbe",
"pcid",
"pclmulqdq",
"pconfig",
"pdcm",
"pdpe1gb",
"pebs",
"pge",
"pku",
"pln",
"pni",
"popcnt",
"pse",
"pse36",
"pts",
"rdpid",
"rdrand",
"rdrnd",
"rdseed",
"rdtscp",
"rep_good",
"sdbg",
"sep",
"serialize",
"sha",
"sha_ni",
"smap",
"smep",
"smx",
"split_lock_detect",
"ss",
"ssbd",
"sse",
"sse2",
"sse4_1",
"sse4_2",
"ssse3",
"stibp",
"syscall",
"tm",
"tm2",
"tme",
"tpr_shadow",
"tsc",
"tsc_adjust",
"tsc_deadline_timer",
"tsc_known_freq",
"tscdeadline",
"umip",
"vaes",
"vme",
"vmx",
"vnmi",
"vpclmulqdq",
"vpid",
"waitpkg",
"x2apic",
"xgetbv1",
"xsave",
"xsavec",
"xsaveopt",
"xsaves",
"xtopology",
"xtpr"
],
"l3_cache_size": 25165824,
"l2_cache_size": "11.5 MiB",
"l1_data_cache_size": 557056,
"l1_instruction_cache_size": 720896,
"l2_cache_line_size": 1280,
"l2_cache_associativity": 7
},
"core_units": 20,
"family": "Nehalem"
}
],
"rams": [
{
"capacity": 62
}
],
"mother_board": {}
Hello @maxschulze!
I looked into this issue and it seemed like it was a problem with how the hash-map was formatted for disks. Commit 6ed5017 corrected the formatting, I do not have a 500 Internal Server Error anymore with your hardware JSON file.
If you can reproduce your query in the Boagent API, that would be great!
