[Samba] ERROR(runtime): uncaught exception - (3221225524, 'The object name is not found.')
Rowland Penny
rpenny at samba.org
Mon Aug 22 20:24:42 UTC 2022
On Tue, 2022-08-23 at 07:48 +1200, Michael Doerner | TechnologyWise via
samba wrote:
> On 23/08/22 00:03, Rowland Penny via samba wrote:
> > On Mon, 2022-08-22 at 23:09 +1200, Michael Doerner | TechnologyWise
> > via
> > samba wrote:
> > > Hi Louis
> > >
> > > thank you for the input. I will run that script tomorrow and will
> > > try
> > > to
> > > understand the output/results.
> > >
> > > Sorry for missing info about OS. This is a Samba Docker container
> > > (from
> > > Ubuntu sources) running on a Debian 9 (Stretch) Docker host.
> > >
> > > /etc/resolv.conf looks OK (compared with our own Samba instance
> > > which
> > > is
> > > actually an up to date version 4.15.9)
> > It might be a permissions problem, but I doubt it, mainly because
> > you
> > have already done what the script does with 'samba-tool gpo
> > aclcheck'
> >
> > Samba stores the GPO's in AD and mainly in Sysvol, 'samba-tool gpo
> > aclcheck' iterates over the GPO data in AD and checks every GPO in
> > Sysvol, it seems to be failing at 'share_pool' because it cannot be
> > found.
> >
> > Rowland
> Thank you Rowland.
>
> The script output looks OK to me (as further below) and the
> 'share_pool'
> definitions are below. I will continue and hope to find a solution
> (and
> report back here).
>
> Michael
>
>
> from smb.conf:
>
> ...
> [sysvol]
> path = /var/lib/samba/sysvol
> read only = No
>
> [usr_profiles]
> path = /data/usr_profiles
> read only = no
> ..
> [share_pool]
> path = /data/share_pool
> read only = no
Something odd here, you posted this:
root at dmh002sv:/# samba-tool gpo aclcheck -UAdministrator
Processing section "[netlogon]"
Processing section "[sysvol]"
Processing section "[usr_profiles]"
.. cut ..
Processing section "[vpn_certs]"
Processing section "[share_pool]"
Which is all well and good, but 'share_pool' isn't a GPO, it is a share
(something I should have realised earlier)
I think we need to see the entire output of the command, or failing
that, the output of the command with '-d0' on the end of it.
I think the output is getting polluted because there is a high log
level set in smb.conf, all those 'Processing section' lines are
probably meaningless.
Rowland
More information about the samba
mailing list