Hi,
We increased the CPU count of one of the samba-ad servers in Data Center
B, and the problem seems to have come under control, despite an
observable delay. It is also observed that on one of the servers that
held PDC Emulator, naming, dnsname, forestdns FSMO roles, the CPU
consumption was consistently over 85% consistently and even spiking to
100% . Except samba-ad-dc, no other services are running on these servers.
Samba version is 4.19.5
Thanks & Regards,
Anantha Raghava H A
DISCLAIMER:
This e-mail communication and any attachments may be privileged and
confidential to Exza Technology Consulting & Services, Indryve Inc &
their group companies, and are intended only for the use of the
recipients named above If you are not the addressee you may not copy,
forward, disclose or use any part of it. If you have received this
message in error, please delete it and all copies from your system and
notify the sender immediately by return e-mail. Internet communications
cannot be guaranteed to be timely, secure, error or virus-free. The
sender does not accept liability for any errors or omissions.
Do not print this e-mail unless required. Save Paper & trees.
On 17/05/24 1:06 pm, Anantha Raghava via samba wrote:> Hi,
>
> We are having totally 5 samba-ad servers (2 servers in "Data Center
A"
> and 3 in "Data Center B") in our setup providing AD services.
>
> We have been having trouble whenever we do an activity called "DR
> Activity" during which we bring down 2 servers in "Data Center -
A"
> and try to run our entire infrastructure with 3 samba-ad severs in
> "Data Center B".
>
> DNS is Samba Internal DNS.
>
> Whenever we do this activity, we find that DNS queries and hence the
> authentication times out, causing major issues in our setup. We find
> that even logs are not getting printed in the servers in Data Center
> B. Surprising part is when restart other 2 servers in Data Center A,
> all things go normal.
>
> All 5 servers have the same configuration - 8 Core CPU, 64 GB RAM and
> 5 Gbps NIC, RHEL 8.x OS.
>
> It is also observed that 1 of the servers in Data Center B has 1
> server in Data Center A as replication partner. This causes the
> replication also to all over whenever we do this mandatory activity.
> every month and every month we fail in this activity we have an audit
> remark.
>
> May I request the community to advice how to go about trouble shooting
> this situation?
>