Elias Pereira
2023-Dec-05 19:59 UTC
[Samba] Failed to store repsFrom - Indexed and full searches both failed!
hi, After an update to our DC4, I started to notice the error "Failed to store repsFrom - Indexed and full searches both failed!" in the logs. root at dc4:~# tail -f /var/log/samba/log.samba Copyright Andrew Tridgell and the Samba Team 1992-2023 [2023/12/05 14:09:06.191978, 0] ../../lib/util/become_daemon.c:150(daemon_status) daemon_status: daemon 'samba' : Starting process... [2023/12/05 14:09:06.373562, 0] ../../source4/samba/server.c:896(binary_smbd_main) binary_smbd_main: samba: using 'prefork' process model [2023/12/05 16:05:04.141027, 0] ../../source4/dsdb/kcc/kcc_periodic.c:790(samba_kcc_done) ../../source4/dsdb/kcc/kcc_periodic.c:790: Failed samba_kcc - NT_STATUS_IO_TIMEOUT [2023/12/05 16:06:30.931069, 0] ../../source4/dsdb/common/util.c:3482(dsdb_savereps) Failed to store repsFrom - Indexed and full searches both failed! I tried running a "samba-tool drs replicate...", but the error occurs: ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (3221225653, '{Device Timeout} The specified I/O operation on %hs was not completed before the time-out period expired.') File "/usr/lib/python3/dist-packages/samba/netcmd/drs.py", line 567, in run drs_utils.sendDsReplicaSync(server_bind, server_bind_handle, source_dsa_guid, NC, req_options) File "/usr/lib/python3/dist-packages/samba/drs_utils.py", line 100, in sendDsReplicaSync raise drsException("DsReplicaSync failed %s" % estr) Pastebin with -d10 drs replicate: https://pastebin.com/raw/LZNTqssa Some points: - samba_dnsupdate --verbose --all-names is ok - samba-tool dbcheck --cross-ncs --reset-well-known-acls --fix is ok - samba-tool drs showrepl is ok (it takes +/- 1 minute for the result) Researching, I saw that it could be the corrupted database, and only demote the DC in question would solve it. Is that really the case? If so, can I demote and use the same server, including the same hostname and IP? Thanks!!! -- Elias Pereira
Elias Pereira
2023-Dec-06 15:45 UTC
[Samba] Failed to store repsFrom - Indexed and full searches both failed!
Any thoughts? :D On Tue, Dec 5, 2023 at 4:59?PM Elias Pereira <empbilly at gmail.com> wrote:> hi, > > After an update to our DC4, I started to notice the error "Failed to store > repsFrom - Indexed and full searches both failed!" in the logs. > > root at dc4:~# tail -f /var/log/samba/log.samba > Copyright Andrew Tridgell and the Samba Team 1992-2023 > [2023/12/05 14:09:06.191978, 0] > ../../lib/util/become_daemon.c:150(daemon_status) > daemon_status: daemon 'samba' : Starting process... > [2023/12/05 14:09:06.373562, 0] > ../../source4/samba/server.c:896(binary_smbd_main) > binary_smbd_main: samba: using 'prefork' process model > [2023/12/05 16:05:04.141027, 0] > ../../source4/dsdb/kcc/kcc_periodic.c:790(samba_kcc_done) > ../../source4/dsdb/kcc/kcc_periodic.c:790: Failed samba_kcc - > NT_STATUS_IO_TIMEOUT > [2023/12/05 16:06:30.931069, 0] > ../../source4/dsdb/common/util.c:3482(dsdb_savereps) > Failed to store repsFrom - Indexed and full searches both failed! > > I tried running a "samba-tool drs replicate...", but the error occurs: > > ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - > drsException: DsReplicaSync failed (3221225653, '{Device Timeout} The > specified I/O operation on %hs was not completed before the time-out period > expired.') > File "/usr/lib/python3/dist-packages/samba/netcmd/drs.py", line 567, in > run > drs_utils.sendDsReplicaSync(server_bind, server_bind_handle, > source_dsa_guid, NC, req_options) > File "/usr/lib/python3/dist-packages/samba/drs_utils.py", line 100, in > sendDsReplicaSync > raise drsException("DsReplicaSync failed %s" % estr) > > Pastebin with -d10 drs replicate: > https://pastebin.com/raw/LZNTqssa > > Some points: > - samba_dnsupdate --verbose --all-names is ok > - samba-tool dbcheck --cross-ncs --reset-well-known-acls --fix is ok > - samba-tool drs showrepl is ok (it takes +/- 1 minute for the result) > > Researching, I saw that it could be the corrupted database, and only > demote the DC in question would solve it. > > Is that really the case? If so, can I demote and use the same server, > including the same hostname and IP? > > Thanks!!! > > -- > Elias Pereira >-- Elias Pereira