Samba DC is not starting

NethServer Version: 8
Module: Samba DC

After a Reboot this Morning, to reconfigute some memory the samba DC is’nt starting anymore.
I run NS8 on Proxmox.
the CPU usage as the memory usage is verry high.
grafik
I added the memory because I was copying files from my NAS to NS8 because I want so reduce soem infrasructure and want to use the NS8 as Fileserver instead of the NAS. This coppying was verry slow, I often had wa of over 90 seen with the command top.

What can I do now to bring the DC up and waht to do with the poor disk performance?

Let’s check the service status of the samba-dc:

runagent -m samba1 systemctl --user status samba-dc

You could try to restart the service:

runagent -m samba1 systemctl --user restart samba-dc

Are there interesting log entries after restarting the service?

Which disks do you use?
Did you check the hardware for errors?

I think ist a hardware problem, Samba started after like 10 minutes. But the system is slow as hell.
On my proxmox I added a 8TB samsung disk as ZFS and moved the NS-cluster to this storage and resized the VM Disk to 3,3TB. I dont see any errors on that Disk, in my proxmox Interface it says “no Known Data Errors” after a Scrub yesterday

Good morning @pnemenz

Please post the hardware settings of the VM as you have defined them in the PVE. So processor, memory and so on. And then I recommend that you activate the Quemu agent, which you may need to install on the OS under the NS8 beforehand.

Regards…

Uwe

Knowing what base OS you are running, and if self installed or from downloaded image might also help to know…

What core / app version?

Some data about the Proxmox host would also help here.

I do not see ANY of these base infos anywhere in this post…

My 2 cents
Andy

1 Like

Hi Uwe,
grafik

I just enabled the quemu agent.

@Andy_Wismer: I use the Image, The server was runnig already good until I moved it to the other, bigger Disk

@pnemenz

Well, for performance issues, knowing a bit about the hardware you are using, what disks, how is ZFS memory (limited?) set would really help.

As to Proxmox:

I would suggest using the Q35 base image, instead of i440fx. The Q35 virtual VM definition is about 15 years newer than the i440fx, which is so old (1990ies…). Linux will acept a change without issues AFTER installation.

Why is the hard disk defined as IDE?
This is the slowest of all options!
Better would be to use a virtual HD with virtIO SCSI.

My Home NS8:


→ This also worked well with 8 GB RAM.

Note:
Only activate Directsync once you have verified it works without cache!
Mine is on Debian, self installed and using BtrFS as file system.
I wouldn’t dream of using ext4 as a file system on a server!

Do you actually use the firewall on Proxmox? I never do, and NONE of my VMs will use it!
Deactivate the Proxmox firewall on the VM-NIC Interface!

And it would be better to use a VirtIO NIC (You get a 10 GBE Nic in Proxmox, vs a 1 GBE Nic when using the old e1000…

Hope these suggestions help.
But I could suggest more if knowing your Proxmox hardware and settings better!

My 2 cents
Andy

1 Like

I have just read that my personal Proxmox teacher @Andy_Wismer has already written the essentials. Do it the way he described it. Then you can continue.

2 Likes

Thanks for this sugestions, can I change the Mashine, SCSI Controller and the networkdevice now or would I need to build a new VM?

My Hardware is a HP Worklstation, Z400 I think, a few Years old. HDDs are :slight_smile:

How can I get you the informatioen about the ZFS Memmory?

1 Like

I assume you are refering to the VM, as on Proxmox itself you need to change “real” hardware!
:slight_smile:

The Machine Type can be changed - without issues. But do it when the VM is turned off, a reboot will not suffice, on Proxmox the VM actually needs to be turned off before a change is recognized and used.

As your only HD is using IDE (ide0) changing the SCSI controller will not affect anything. You would also need to install the stuff on a VirtIO SCSI disk. But you can do it, no probs will arise.

You can change the network device, but you may need to reallocate it in Rocky. Using the qemu-guest-agent is strongly advised, this gives you stable and fast shutdowns from the Proxmox console (Also if using a UPS…). But the best part is it will show you all IPs (IPv4 and IPv6) used by the VM!

Here is a Win10 “Admin-PC” running as VM in Proxmox. Note the Network NIC speed!

This also uses the VirtIO network drivers - the ones from RedHat on a ISO, best installed directly when installing Windows!
And also use VirtIO SCSI drivers (And the serial driver needed for the Qemu guest agent…).


Proxmox ZFS Memory Limits

Follow the instructions here under " Limit ZFS Memory Usage" from this official doc:

https://pve.proxmox.com/wiki/ZFS_on_Linux#sysadmin_zfs_limit_memory_usage

and ZFS also this:

https://pve.proxmox.com/wiki/ZFS:_Tips_and_Tricks#Snapshot_of_LXC_on_ZFS

A very important note on ZFS booting:

When installing Proxmox with ZFS for booting it is important to note that you will NOT have any working Swap!
The trick is to install Proxmox on the disk (or mirror, which you are not using…) and in the advanced options of the disk settings, reduce the disk size by 16 GB. This can be formatted as a swap partition later on, after the install, with normal Debian commands, as Proxmox is based on Debian! I can help with this if needed.

For those who still think swap is not needed on Linux or Proxmox, I’ll show this:

This box still has ample 20% of 128 GB RAM unused - so why is swap maxed out?
And this box is NOT underpowered: 40 CPU cores…


ZFS RAM settings:

Show contents of nano /etc/modprobe.d/zfs.conf

:slight_smile:

If I missed out anything, just ask!


I strongly suggest to follow / read this:

and install your VM and Proxmox exactly the way you want it, so that it can and will run the next 5 years or longer, hardware defects aside!


As you run Proxmox, do things step by step, make backups (not snapshots) in between!
A backup is independant, a snapshot still needs the original disk. As changing the disks might be an option, a snapshot restore might present issues…

Good luck!

My 2 cents
Andy

3 Likes

my proxmox isnt booting from zfs, its on the nvme0n1p2 partition, but I dont remember what filsystem I used there, probably the default from the proxmox installer.
ZFS RAM Settings:
options zfs zfs_arc_max=4294967296

I did the other changes you sugested. Let’s see if it gets better.
As for the SCSI Disk: Is there a way to move the NS8 to such a disk or do I have to start over?
I realy dont know why I have the IDE on here, the other VM’s on my Proxmox are VirtIO SCSI Single, as yours.
The same with the Networkcard.

1 Like

How much RAM do you have on the PVE host?

This is what the utilization looks like on my main PVE. There are currently three VMs and 14 LXCs running simultaneously.


2 Likes

I have 64GB of RAM
this is my PVE:


I have 6 VM and 1 LXC running, but most of them are just play around. I guess I should clean this mess up soon :smiley:

2 Likes

@pnemenz

What do you use for Backup?

proxmox backup to a NASon a diffent hardware

Do yourself a BIG favor:
If you can spare a box for PBS, try to do so. a NAS just can’t compare!

Mine has 32 GB RAM, OS on a 256 GB NVME, 2x 16 TB Seagate Exos Enterprise Class Disks 7200 RPM, all in ZFS.
A low powered Odroid H3+ as base… :slight_smile:

Incremental Backups - MUCH faster!
40x Compression and Deduplication - your NAS will get max 2-3x.
And much more!

My 2 cents
Andy

Hi @pnemenz

In case you’re wondering, @transocean and I use the same hardware for Proxmox (and PBS also!):

These boxes are also available from other resellers…

Maximum power usage 120W, low heat generation, built in 2x 2.5 GBE networking.
For Proxmox, only using one NVME, max power use is only 60 W !!!

:slight_smile:

My 2 cents
Andy

Youre right, I have to much hardware and VM here. I’m trying to reduce. Actualy I want to get rid of the NAS and put the tings on there on a NS8 Fileserver and also reduce unnecessairy Data so mybe I can backup to some cloud.
First I try to get NS8 up andrunning, nethsecurity runs already nicly. Then I can migrate all the Data und kill my old Trunas. :slight_smile:

My Tip:

Split up your data storage.

My rule of thumb:

User Home directories stay on NS8.
Smaller shares also.

Larger shares I move to an OpenMediaVault (OVM) NAS-V on Proxmox.

This is a clients server, not my home one!

PBS backup of the 8 TB on this virtual NAS takes 2.5 minutes!
All still using 1 GBE networking, we plan on switching to 2.5 GB/S soon.

:slight_smile:

The OMV is attached to the NS8, so all users and groups can be used as needed. And it is seperate from NS8, in case of issues. This takes “a bit longer” to restore than a few mails!

OMV uses half the resources of TrueNAS, when running as a VM - we tested!

My 2 cents
Andy

1 Like

@pnemenz

If you want and have the time later, I can offer a free session with Anydesk (Screen sharing for you to view my setup) and a voice chat with Telegram ( I do not use anything by Zuckerberg, so no WhatsApp!). But Telegram is free, works on almost all smartphones and on PCs and Macs and has good audio quality, but also the ability like WhatsApp to instantly send large files or whatever.

Drop me a PM and I’ll send details.

My 2 cents
Andy