`tilespath` and `webpath` on samba drive not working
See original GitHub issueIssue Description: Dynmap is not able write to a network mounted drive (via SMB) On the server I can properly see the drive is mounted and accessible ( since I managed to send the web folder)
<kbd></kbd>
But java says it doesn’t exist :
[Dynmap Render Thread/FATAL]: [Dynmap] Exception while writing JSON-file - Z:\standalone\dynmap_config.json.new
java.io.FileNotFoundException: Z:\standalone\dynmap_config.json.new (The system cannot find the path specified)
at java.io.RandomAccessFile.open0(Native Method) ~[?:?]
at java.io.RandomAccessFile.open(RandomAccessFile.java:344) ~[?:?]
at java.io.RandomAccessFile.<init>(RandomAccessFile.java:259) ~[?:?]
at java.io.RandomAccessFile.<init>(RandomAccessFile.java:213) ~[?:?]
at org.dynmap.storage.MapStorage.setStandaloneFile(MapStorage.java:272) [Dynmap-3.3-beta-4-fabric-1.18.jar:?]
at org.dynmap.JsonFileClientUpdateComponent$FileProcessor.run(JsonFileClientUpdateComponent.java:88) [Dynmap-3.3-beta-4-fabric-1.18.jar:?]
at org.dynmap.MapManager$DynmapScheduledThreadPoolExecutor$1.run(MapManager.java:229) [Dynmap-3.3-beta-4-fabric-1.18.jar:?]
at org.dynmap.MapManager$DynmapScheduledThreadPoolExecutor$2.run(MapManager.java:245) [Dynmap-3.3-beta-4-fabric-1.18.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
at java.lang.Thread.run(Thread.java:833) [?:?]
- Dynmap Version: 3.3-beta-4
- Server Version: 1.18.1 with Fabric Loader 0.12.11
- Pastebin of Configuration.txt: https://pastebin.com/A0u8peVp
- Relevant logs https://pastebin.com/2gnkRgRM
[x] I have looked at all other issues and this is not a duplicate
[x] I have been able to replicate this
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Can't open network drive (smb / samba) programatically with ...
I have problems opening a network drive programmatically. I have used the way described here:Access a Remote Directory from C#.
Read more >How to share files with Samba | Enable Sysadmin - Red Hat
Configure Samba To configure shares and users, edit the /etc/samba/smb. conf file. The default file has several good examples of common options ...
Read more >Samba Network Path not found - Super User
Same problem on debian 10. Solution: sudo apt install samba-vfs-modules. P.S. My problem was because of module widelinks.so. Share.
Read more >SAMBA Issues: Core file & Cannot See Share from certain Win ...
I can see and access the UbuntuShare folder from my Windows 10 laptop, but only if I type in the computer name or...
Read more >Smb file share not showing correct free space
I've been having issues with my samba share. ... but when trying to move files to the share, windows tells me there is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The other thing, particularly relative to SAMBA or a network drive, is to be sure that the user account you are running the server under has the needed access to the file system: literally, there is nothing in our code that would yield a path not found that we control - either your settings are pointing the wrong place, or the user account the MC server is running under lacks the needed permissions for the path and files there. Basically, from the java VM point of view, a file system path is a file system path, and being able to access it is ‘above our pay grade’, if you get my drift. I don’t know your setup - if you are running on windows with the server as a local service, they tend to (by default) lack network drive access, IIRC. I recall there being a way to use a ‘network service’ account for that case, but I’ve been away from Windows as a main platform for a few years, so details are fuzzy.
Well you were spot on on that indeed. When I tried running the server as a user with the share mounted it worked perfectly. And it turns out AMP software is a service that runs as
Network Service
user so I added a scheduled task to mount the drive as that user and now it works. 🎉Thanks all for your help !