Elias Pereira
2024-Jan-17 14:23 UTC
[Samba] {Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
hi, Still dealing with the error. In some posts on the internet, a user reported that he has more than 40k objects in samba and that's why the error occurs. When running the command "samba-tool dbcheck --cross-ncs --fix --yes" reports that it has "Checking 16529 objects (Checked 16529 objects (0 errors))". So it wouldn't be my case. Running "samba-tool drs showrepl" doesn't show an error, but the replica does. When I replicate with the sub-options below, the replication is successful. DC=ForestDnsZones CN=Configuration DC=DomainDnsZones CN=Schema,CN=Configuration When I leave only the domain ?DC=campus,DC=sertao,DC=ifrs,DC=edu,DC=br? the error occurs. What are other ways of troubleshooting? On Thu, Jan 4, 2024 at 10:30?AM Elias Pereira <empbilly at gmail.com> wrote:> Hi Rowland, > > Could you tell me what the correct permissions are for the bind9 files? > > On Wed, Jan 3, 2024 at 5:46?PM Elias Pereira <empbilly at gmail.com> wrote: > >> The only 'problem' I can see is that the group is set to 'bind' instead >>> of 'root', why is this ? >> >> If I'm not mistaken, I did it on the wiki, but maybe I needed an older >> version. >> I've corrected it to root:root >> >> Not that I am aware, but the mention of 'bind' above makes me wonder if >>> you are using Bind9 instead of the Samba builtin dns server. >> >> yes, I'm using BIND_DLZ backend for DNS. >> >> Do you think it might be something with the bind confs? >> >> >> >> On Wed, Jan 3, 2024 at 5:35?PM Rowland Penny via samba < >> samba at lists.samba.org> wrote: >> >>> On Wed, 3 Jan 2024 17:24:34 -0300 >>> Elias Pereira <empbilly at gmail.com> wrote: >>> >>> > > >>> > > Everything looks okay, so I am not sure what is going on here, >>> > > kerberos??? >>> > >>> > I don't know either! :( >>> > >>> > What is in /etc/krb5.conf ? >>> > >>> > >>> > root at dc2:~# cat /etc/krb5.conf >>> > [libdefaults] >>> > dns_lookup_realm = false >>> > dns_lookup_kdc = true >>> > default_realm = CAMPUS.SERTAO.IFRS.EDU.BR >>> > root at dc2:~# ls -laht /etc/krb5.conf >>> > -rw-r--r-- 1 root bind 115 Dec 12 15:31 /etc/krb5.conf >>> > >>> > root at dc3:~# cat /etc/krb5.conf >>> > [libdefaults] >>> > dns_lookup_realm = false >>> > dns_lookup_kdc = true >>> > default_realm = CAMPUS.SERTAO.IFRS.EDU.BR >>> > root at dc3:~# ls -laht /etc/krb5.conf >>> > -rw-r--r-- 1 root bind 115 Jul 7 11:33 /etc/krb5.conf >>> >>> The only 'problem' I can see is that the group is set to 'bind' instead >>> of 'root', why is this ? >>> >>> > >>> > Is there any way I can increase the timeout in the command? >>> > >>> >>> Not that I am aware, but the mention of 'bind' above makes me wonder if >>> you are using Bind9 instead of the Samba builtin dns server. >>> >>> Rowland >>> >>> -- >>> To unsubscribe from this list go to the following URL and read the >>> instructions: https://lists.samba.org/mailman/options/samba >>> >> >> >> -- >> Elias Pereira >> > > > -- > Elias Pereira >-- Elias Pereira
Rowland Penny
2024-Jan-17 15:11 UTC
[Samba] {Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
On Wed, 17 Jan 2024 11:23:12 -0300 Elias Pereira <empbilly at gmail.com> wrote:> hi, > > Still dealing with the error. > > In some posts on the internet, a user reported that he has more than > 40k objects in samba and that's why the error occurs. > > When running the command "samba-tool dbcheck --cross-ncs --fix --yes" > reports that it has "Checking 16529 objects (Checked 16529 objects (0 > errors))". So it wouldn't be my case. >Try adding '--async-op' to your replication command, lets see if that helps. Rowland
Apparently Analagous Threads
- {Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
- {Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
- {Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
- {Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
- {Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired