sgjava

Ha, no, I don't work for Oracle. In fact, I use Zulu Open JDK https://www.azul.com/products/zulu-enterprise/jdk-comparison-matrix since it's easier to download and doesn't require an account like Oracle JDKs. I actually develop Java Periphery on a x86-64 platform and test on ARM 32/64. Zulu is a great OpenJDK implementation. I've used XenServer a lot, but OpenStack is very interesting. The main issue with RedHat is not to fall into the "Enterprise" trap which is their paid for software and services. RedHat is famous for wrapping Open Source in their GUIs and selling that to Enterprise customers. Also, since IBM took over I suspect they will continue that trend.

So basically the topic drifted from Zabbix (omni monitoring tool) to Cockpit (admin tool) and you mentioning Node.js which is based on an event loop. My point was the thread vs. event loop argument was solved decades ago, but people keep reinventing event loops as more scalable. They probably didn't read the seminal research already out there. There are interesting structures like ring buffers that can scale massively and replace queues. https://lmax-exchange.github.io/disruptor. Any ways, I'm not falling into the JS/TS/Node.js trap. I'll stick with Java/Python/C/C++ as most of my work doesn't involve UI. Also, check out my https://github.com/sgjava/java-periphery library if you want to leverage userspace IO on Armbian. It uses code generation to wrap C code into a nifty Java API. Enough drifting off topic for now before Igor stops by

It's funny you mention Node.js as the question of event loop vs. threads was answered back in the 70s. This paper explains it and even it is 17 years old. https://people.eecs.berkeley.edu/~brewer/papers/threads-hotos-2003.pdf Any ways, newer isn't always better.

I'm really not looking at Zabbix as a development platform. It's a tool and that's what I use it for, so the underlying stack is not that interesting to me. Also, Zabbix can be served up with nginx or use PostgreSQL if that matters. Cockpit is more of an admin tool with limited monitoring (compared to Zabbix) from what I can tell and it's only for Linux. Zabbix has cross platform agents and can monitor diverse things like DBs, web endpoints, switches (or my refrigerator). Plus I'll let Zabbix fix issues for me automatically without any intervention. They are fundamentally different tools. https://www.zabbix.com/features https://www.redhat.com/sysadmin/intro-cockpit

Actually Zabbix is monitoring software that collects telemetry and allows actions such as emailing, texting, restarting services or servers based on conditions and escalations. I've totally automated network admin type roles with it and things at home like monitoring the power state of my beer refrigerator in the garage. It's super flexible and easy to add stuff to the agent for client specific needs. It can also scale to millions of devices or just a handful at home. Also, the agent is now golang, not C. Cockpit looks more like Webmin on steroids. It's also Linux only from what I can tell. Zabbix is cross platform if you ever have to manage a mixed environment with Linux and Windows servers.

I've used Zabbix professionally and at home to monitor servers, IoT, and IP devices. I've built scripts for the server and client to automate the install process including moving the MySQL database, so you can locate it to a NFS mount instead of serving the database from the slower SD card. The deb packages do not work for ARM, so you have to build it from source using my scripts. Install Zabbix

@Igor I can verify M1 image now works, thanks!

@Igor I hate when that happens. I've been stuck on something for days and weeks sometimes and it's something crazy like that. Happens to every dev.

@Igor I know you probably tried this, but focal builds were work around mid-May. Can you see any deltas to your build scripts after that?

I was able to get the M1 focal image to boot with local build as well. So are you still having issues with automated builds or just this one?

I just created a VirtualBox VM and built NanoPi Duo and NanoPi M1 fine. Duo working fine, still need to test M1 image.

@Igor I built Armbian_20.08.0-trunk_Nanopiduo_focal_current_5.4.43_minimal.img local and it boots fine. I will try Armbian_20.08.0-trunk_Nanopim1_focal_current_5.4.43_minimal.img later tonight. At least I have a work around. Sorry I cannot be more help for the automated issue.

@Igor Armbian_20.05.1_Nanopiduo_focal_current_5.4.43.img same issue as M1 image.

OK, I'll try M1 focal manually.

@Igor Does this happen if you build manually? If not, then I will try to build locally. I should learn how to do this any ways.