Nethserver 8 netdata install issue

NethServer Version: NS8
Module: netdata

I have decided to start fresh with Nethserver 8 and document my issues, feedback with the community with hope that I can find solution or bring them to light so they can be addressed in coming releases.

I am not sure if i want to open a new thread with each issue. Perhaps using this single thread to log the journey is better way to go?

I have created a fresh VM, installed Debian 12 then installed NS8 using the curl command as described in the wiki. After logging in the first time, i created the a cluster, then rebooted. I wanted to try the netdata as first app to install. Installation ended with error as following:

Even though tthe install was unsuccesful it created the app instance and this is how it looks:

I tried to uninstall the app but again ended up with the following error. The app remained uninstalled. Even after several attempt the app remained uninstalled.

I did take a snapshot of the vanilla debian so i can always revert back. But the question is why the fresh nethserver 8 with nothing confgured at all have issue installing a simple app such as netdata? Any idea?

4 Likes

Thanks for starting over and explaining the issues.

I think that the relevant error information is hidden behind the “Show more
” links (bottom right of the error textbox) in the first screenshot.
It should be possible to get it from the system logs page.

The best way to keep it clean is one support thread for one issue, also because it’s better for finding solutions and reading in general.

Just an idea: Maybe there’s a conflicting cloud-init config?

Here is a screenshot of error when trying to uninstall the netdata app. I have clicked on Show More , so both details are showing complete info. It does look like the issue is due to incomplete Install which was the original issue. How can I remove faulty install?

I am not adding much to the issue at hand, but it strikes me that many issues (not just this one, but many more) seem to be Debian related. I simply thought I mention this, that’s all. No flaming intended here at all.

Ok, dumb section here

On NS7 NetData is a wonderful tool to understand how data flows in and out from the OS for every service.
Into a container
 which “oject”'s traffic is monitoring?

Since NS8 is all container based, technically OS should not matter. I think that was one of the reason to go with container.

An update on the netdata broken install, I am surprised myself. So if anyone got any explanation for this I would greatly appreciate it.

I could not uninstall the netdata no matter what. Installing new instances also was unsuccessful. I always use ext4 file system for OSs. Since I am trying many things to see what could be causing the issue, I decided to try btrfs instead of ext4. NS8 GUI did seem little more responsive to me, and then to my surprise, netdata installed on first try. Then I installed SAMBA and that install worked on first try as well. I was going to open a new thread for samba issue and post full error log because that also had unsuccessful install issue.

I should mention here, beside the btrfs in the VM, everything else is identical as before. VM stored on same storage, same configuration, same steps to install NS8 and netdata as first app install.

I am going to try to install mail, webtop and nextcloud next and see if they work. As I mentioned I am finding the GUI more responsive than before, enough to be useable.

I know btrfs is the faster file system, but why that should make such difference for podman based container? Anything in the neth design that makes btrfs suitable? I use debian for everrything and dont want to try anything else. So all my tests are on Debian 12.

3 Likes

Fair enough, but still Nethesis insists to use Rocky Linux, hence they only ‘officially’ support Rocky.

At the moment, NethServer 8 seems to be the only candidate in the Debian universe having basic problems even installing on bare metal? Proxmox, OpenmediaVault, Ubuntu and others are all based of Debian - and all can be installed without any issues.

Yet NethServer 8, at the moment is VERY flakey on Debian, a little less on Rocky Linux.
Seems Rocky gets more support, dev resources

I really wonder why Nethesis insisted on using and thus also supporting “Nobody” Linux

Gregory Kurtzer isn’t really known for creating anything open source, just as acting a parrot for code


I am not really happy with the situation at the moment.

I will be testing another Debian based VM tonight (Different environment / Client), will see how it goes


My 2 cents
Andy

1 Like

I run for example an NS8 Debian 12 cluster using 3 nodes without issues for some time now with many installed apps including community ones. 1 on Proxmox at home (local NVME) , 1 Strato VPS, 1 Contabo VPS.
Debian for example uses an older podman version so there may be issues but so far everything is working here.

I’d really like to find out why these issues occur


I can fully understand that a not working system doesn’t make one happy.
Did you already try an installation on a local disk on the node to check if it’s maybe a NAS issue?

EDIT:

Good luck for the installation tonight!

2 Likes

That’s planned for tonight, the other client’s NS7 is just simply too big
 (1.4 TB).

:slight_smile:

Not working? Not even released half a year ago, yet can’t even install a basic system (Completly empty)?

That’s too much!

:frowning:

I did promise a certain unnamed dev here some feedback on Zabbix, but after a week, I’m still fighting issues on setting up the basic system


:slight_smile:

My 2 cents
Andy

1 Like

Just for the heck of it, I tested again with Debian+ext4, and all the issue of bad app install returned.
Looks like if NS8 used Debian, then btrfs should be used. For the most part this seems to be the solution for Debian users. Some issue still occurred such as WebTop DB issue i mentioned in the other post, but it is usable.

It is a valid point really. But the containerization should mean it works on all(most) flavours. For somebody like me who are reluctant to use any other OS except Debian, it does provide option to use NS8. After CentOS lost it’s charm, I am not all for going with rolling centos flavours.

I also follow the same ideals
 Nothing RHEL based for me anymore - I just don’t trust them anymore, they are on the same level as anyone singing the “blues” (Big Blue
).

I had the same issues with XFS as file system I trust more than ext4, although I also tried ext4, both gave the same results. :frowning:

I’ve never really used Debian with BTRfs, although I use BTRfs on a lot of systems, amoung them Synology NAS and a few Linux variants (Rock Store)


My fav is still ZFS, but only if the system fully supports it. I won’t attempt to run a system on ZFS if it doesn’t support ZFS out of the box.

One thing that still makes me stop from using BTRfs is the fact that Proxmox Backup Server can’t really provide file / folder level restore with BTRfs, as it’s not supported there. Ext4 and XFS are well supported.
And all machines run as VMs in Proxmox for me & my clients.

The only exception to that are 2 Novell Netware servers, they are running on VMWare ESXi (supported!), which itself runs in Proxmox (Yes, that works rock solid!). This is only for historical / legal archival reasons!

You were careful enough to use the “should” form
 :slight_smile:

My 2 cents
Andy

I have never used netdata on NS7. So I am not the most experience one to answer. But from what I can tell, it looks like it’s monitoring the VM/machine itself.

There is a dedicated section in netdata named Container and VM and that seem to show data related to container environment. It would be good to know if netdata can show stats for individual containers to see which app using how much resources. Perhaps the options are there and I need to spend more time with netdata.

This is probably digresses the original topic of this thread, but that right there is an absolute crucial piece of information. I also run 100% Proxmox environment with heavy proxmox backup server. I am running a backup right now to see it for myself.
I dont want to say this will be a deal breaker if that is the case. Because I am not sure how much file/folder I do have access now inside the container environment. Say I deploy nextcloud on NS8, how much visibility do I have inside the container with PBS or without.

1 Like

@wahmed

You wern’t aware of the caveat with BtrFS & PBS?

I became aware of that when virtualizing MacOS with PBS as backup

Windows NTFS is not a problem for PBS.

But as it is mission critical for me, I don’t trust OS backups too much for disaster recovery, or for file / folder fast restore, wheras PBS does cover that.

Note: I usually do 4 different Backups: Proxmox PBS, Proxmox NAS, OS Backups and my own Rsync script, grown after more than 20 years


PBS File / Folder restore works AFAIK for Containers too, as for LXC containers on Proxmox. PBS & Proxmox need to be able to handle the file system, that seems it

(HFS+ or BTRfs could be installed on both
)

My strategy:

Better doing a backup too many, than one too little!

My 2 cents
Andy

It’s also possible that Proxmox adds these additional file systems, these guys have been moving fast in the past years!

1 Like

@Andy_Wismer I just tested the Proxmox backup server for NS8 on Debian+btrfs. I can browse and restore file/folder without issue. I have two disk in the NS8. 2nd disk mounted as /home and BTRFS. I can see the folder structure and restore a single file from the backup.

Could you please confirm if I misunderstood you regarding BTRFS and single file restore on PBS? My PBS version is 2.4-6.

1 Like

As said, when I last tested
 :slight_smile:

My PBS is 3.1.5, and I haven’t had time to retest these things lately


I do like Proxmox, and the speed they’ve been moving forwards!

:slight_smile:

But thanks for confirming that it does work now!

I just checked myself, it even reads BSD based file systems nowadays!
OPNsense here:

A MacOS file system still can’t be read:

Proxmox really rocks!

1 Like

Great! Thanks for confirming Andy!.

As of now looks like the main issue of this topic is fixed. Debian with BTRFS was the answer for a working NS8 and netdata app.

1 Like

If this is the case, how do does this finding get across to the devs for confirmation?