Could not open tdb: No such file or directory (both account_policy.tdb and registry.tdb) #79
Comments
|
thanks I'll take a look :) |
|
Great! Thank you! :) Oh and also I tried rebuilding the image, but that made no difference either. |
|
okay I've just started the latest image, it works without a problem on my side. logs are kinda messed up like: but I'm able to connect and browser and everything works as expected. the container on your side is up and running, you use network_mode: host, this means there can be problems if your host system has services which are using the same ports - avahi for example. or maybe a locally installed samba service. what's you host OS, do you use docker or any other system? |
|
the thing is, you don't seem to be the only one with wierd issues - it seems that some people can't use this container at all, while I and most people just start the compose file and it works I also testet on raspberry pi 4 and a fresh ubuntu install and didn't have a problem super super strange, I hope we find and solve this kind of issue! :) |
|
Huh! I see... It could be but I don't think so.
I don't think any other service would interfere, but maybe syncthing does? It is containerized as well. I'll have a look. |
|
yeah might be the case - or you shutdown most of the containers and just try samba as "standalone" if possible you might be able to start samba on another server/computer and check if connection works there |
|
Alright, I've now stopped all other docker containers. The only one running is CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f0b5904f8956 ghcr.io/servercontainers/samba "/container/scripts/…" 5 minutes ago Up 4 minutes (healthy) samba-samba-1I also restarted everything:
Now I started up another computer and On my Android phone,
I don't have any other service running on the host outside of docker. |
|
Here's what's currently running on my RPI: The output of
|
|
Alright, I think I solved it, at least partly so. I found this bit of information:
I guess this is the main culprit. I solved it by following the instructions provided:
Didn't bother with hostname. The errors in the log did not go away but I did manage to log in to the samba server from my iMac, but not my Linux computer for some reason. IIRC I managed to log in via my Android phone as well but only manually by IP and not FQDN. An alternative solution is also mentioned, where you use the macvlan driver in Docker. I did not have any success with that solution though. Not sure why. I'm going to leave this though, because I became aware that Time Machine in OS X 10.11 El Capitan unfortunately does not handle Samba. I wish I'd known that from the beginning :) So now I use your Netatalk image instead. Anyway that seems to have solved it for me. And maybe it does for somebody else too, thanks to mbentley/docker-timemachine! |
|
ohhh interessting, so there is a mtls service running on raspberry os. if on the outside there is an avahi running, you could mount the avahi config into the container, so the container puts it's service into the folder and it should be announced by the host - and the container doesn't start avahi - so there should be no conflict. |
I get "No such file or directory" for both
registry.tdbandaccount_policy.tdbin/var/lib/samba/. I have no idea why that is and I cannot connect to my samba server.Yesterday, when I first started, I immediately got connection timeout upon connecting. Later on I think it somehow confused
StorageServerwith my other samba server running on my Synology NAS. Not sure though. I also tried manually connecting to it (smb://rpi.local), it did not timeout immediately but could not connect any way. Seemed like it could not find the server. The first time I tired connecting it had logged my main computers LAN IP, though.But today, after a restart,
StorageServerdoesn't show up at all. First I though well maybe it's because the server was not running before I started my main computer, but that doesn't really make any sense. Connecting to it manually though, I now get connection timeout immediately. Today it doesn't log my IP. Anyhow, I have no clue what's going on.I read somewhere that it might be due to a wireless connection. I tried wired connection but the issue is still the same.
Here's some context for you:
docker-compose.ymlfileConsole log: level 3
and also (because of the 65536 character limit here):
Today when I manually try to connect, I get this in the logs (level 10):
I also should mention that the
docker-compose.ymlexample file does no difference except also complaining about WSDD2. The issue(s?) is exactly the same.Any pointers? Please help!
The text was updated successfully, but these errors were encountered: