search for: causeof

Displaying 4 results from an estimated 4 matches for "causeof".

Did you mean: cause
2024 Mar 09
1
kcc_periodic output
I've been grappling with a recurring set of errors for quite some time now: - UpdateRefs failed with NT_STATUS_IO_TIMEOUT - Failed samba_kcc - NT_STATUS_IO_TIMEOUT - IRPC callback failed for DsReplicaSync - NT_STATUS_IO_TIMEOUT Despite cranking up the log level to 10, the returned information remains frustratingly cryptic and hard to decipher. This error, being overly generic, continues to
2024 Mar 10
1
kcc_periodic output
...reveal any problems, yet executing > thecommand while monitoring the Samba log with "tail -f" exposes > errorsidenticalto those described above. > Interestingly, samba-tool drs showrepl doesn't report any errors. > So, what additional steps can be taken to unearth the root causeof > these persistent NT_STATUS_IO_TIMEOUT errors? > > On Fri, Mar 1, 2024 at 10:32?PM Elias Pereira <empbilly at gmail.com> > wrote: > > There is probably nothing wrong with your log, but Firefox doesn't > > > like it, it thinks it contains a virus. > > &g...
2024 Mar 10
1
kcc_periodic output
> > Is the drepl local processes very busy doing inbound replication? How can I check this? My instinct is either the server is very busy (and this should show up in > CPU use) or a transaction is being held open excessively. I use VMs on Proxmox. In DC1, I installed the Proxmox agent, and CPU usage via the dashboard is very low. However, when I checked using 'top,' the LDAP
2024 Mar 11
1
How to diagnose a busy LDAP server process in the Samba AD DC
...mmand while monitoring the Samba log with "tail > > > -f" exposes errorsidenticalto those described above. > > > Interestingly, samba-tool drs showrepl doesn't report any errors. > > > So, what additional steps can be taken to unearth the root > > > causeof these persistent NT_STATUS_IO_TIMEOUT errors? > > > > > > On Fri, Mar 1, 2024 at 10:32?PM Elias Pereira <empbilly at gmail.com > > > > wrote: > > > > There is probably nothing wrong with your log, but Firefox > > > > doesn't > > &g...