Bug 11193 - libsmbd_base.so: cannot open shared object file: No such file or directory
Summary: libsmbd_base.so: cannot open shared object file: No such file or directory
Status: RESOLVED FIXED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: VFS Modules (show other bugs)
Version: 4.1.6
Hardware: x86 Linux
: P5 minor (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-02 22:57 UTC by ponsifiax
Modified: 2015-04-03 07:53 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ponsifiax 2015-04-02 22:57:18 UTC
Hi,

During a development of new VFS module, i see this error :  libsmbd_base.so: cannot open shared object file: No such file or directory

Now my module is empty, it's a clone of : skel_transparent.c
I tryed to use directly skel_transparent.c, it's the same !

Thanks for your help !



Stacktrace :

[2015/04/03 00:50:09.324334,  3] ../source3/lib/access.c:338(allow_access)
  Allowed connection from 192.168.56.1 (192.168.56.1)
[2015/04/03 00:50:09.324602,  3] ../source3/smbd/service.c:612(make_connection_snum)
  Connect path is '/home/myapps' for service [myapps_vf]
[2015/04/03 00:50:09.324858,  3] ../source3/smbd/vfs.c:113(vfs_init_default)
  Initialising default vfs hooks
[2015/04/03 00:50:09.325085,  3] ../source3/smbd/vfs.c:139(vfs_init_custom)
  Initialising custom vfs hooks from [/[Default VFS]/]
[2015/04/03 00:50:09.325313,  3] ../source3/smbd/vfs.c:139(vfs_init_custom)
  Initialising custom vfs hooks from [myapps]
[2015/04/03 00:50:09.325891,  0] ../lib/util/modules.c:48(load_module)
  Error loading module '/usr/lib/x86_64-linux-gnu/samba/vfs/myapps.so': libsmbd_base.so: cannot open shared object file: No such file or directory
[2015/04/03 00:50:09.326138,  0] ../source3/smbd/vfs.c:184(vfs_init_custom)
  error probing vfs module 'myapps': NT_STATUS_UNSUCCESSFUL
Comment 1 ponsifiax 2015-04-03 07:53:47 UTC
sorry ... it was too late ...