destroy() callback invoked after mount when running as a service
Alexandros Paraskevaides
Bill Zissimopoulos
This sounds like your file system is failing to start.
To verify this open the Event Viewer and search in the “Application” log for messages with a “WinFsp” source. You will likely see that your file system terminates immediately after being launched.
It is not straightforward to troubleshoot problems for file systems running in the Windows service context, but here are some suggestions.
- You can try running your file system under the SYSTEM account using PSEXEC. Try something like `psexec -d -i -s cmd.exe` to get a command prompt under the SYSTEM account and then launch your file system.
- You can redirect WinFsp debug log output to a file using FspDebugLogSetHandle. However this may not be available to you as it sounds like you are using WinFsp via a Java layer.
- If your file system logs to stderr, these error messages are lost when running in the Windows service context. However you can capture them into a file by specifying a registry setting with name Stderr and value the full file path. You would place this registry setting under the registry key for your file system (e.g. HKLM\SOFTWARE\WOW6432Node\WinFsp\Services\YourFileSystem). This assumes that you are using the WinFsp launcher to run your file system; for more see the Service Architecture document.
- It is also possible to use a debugger such as Visual Studio or WinDbg to debug your file system running in the Windows service context. You would have to run the debugger as administrator, although I have only done this for native code.
Bill
--
You received this message because you are subscribed to the Google Groups "WinFsp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
winfsp+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/winfsp/565bdeca-6327-4f68-9b45-ec43f38047e6n%40googlegroups.com.
Alexandros Paraskevaides
- I've tried PSEXEC and running it under the SYSTEM account doesn't seem to recreate the problem.
- As you said, i'm using WinFsp via a Java layer (jnr-fuse) so that wouldn't be possible.
- As I mentioned above, I've configured log4j to log any stdout or stderr messages to the application's log, but although my application's stdout and stderr messages are being logged, any winfsp messages are not (if I run my application as a java application, I can see the WinFsp messages in the console). Any idea why this is the case?
- Not sure if this would work with Java code, I've tried connecting to the java process and can debug successfully with Intellij, but no messages are being printed on the console view.
Bill Zissimopoulos
As I mentioned above, I've configured log4j to log any stdout or stderr messages to the application's log, but although my application's stdout and stderr messages are being logged, any winfsp messages are not (if I run my application as a java application, I can see the WinFsp messages in the console). Any idea why this is the case?
It is likely that log4j knows how to redirect its own messages to a log file, but it does not know how to do this for code that outputs to the process STDOUT and STDERR handles directly. WinFsp-FUSE (i.e. the FUSE layer of WinFsp, which jnr-fuse uses) outputs to the regular process STDERR and would bypass any log4j redirection.
In addition to the methods I already listed earlier, you may also try the `-o DebugLog=FILE` FUSE command line option. This should redirect WinFsp debug logs to FILE.
To view this discussion on the web visit https://groups.google.com/d/msgid/winfsp/1b9f89a4-3ebc-496f-b65a-40a72f0c8cdfn%40googlegroups.com.
Alexandros Paraskevaides
Bill Zissimopoulos
Yes, it sounds like your file system does not even start, so you would not get any debug logs from WinFsp. I believe something is failing while your file system is initializing itself, because the environment that it runs in (the Windows service context) can be very different from the environment of a regular user.
If you are using the WinFsp launcher, try the Stderr capture trick I mentioned in my first mail. Otherwise if you are running the file system as a Windows service yourself, you will have to find another way to figure out what is failing.
To view this discussion on the web visit https://groups.google.com/d/msgid/winfsp/0c73d09a-5cb4-4191-b820-b1ef0ef1b351n%40googlegroups.com.
