cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
cjustinek
Level 3

DPLT: terminating due to failure in creation of AF_LOCAL/AF_UNIX socket

Jump to solution

Hi there,

We are using FNP on a Windows Server 2016 machine with our VD v11.18.0.0 build 275847 x64_n6 ( build 275847 (ipv6)). We struggle to start the License service on that particular machine. 

In the customer environment on a Windows 10 machine it is running fine.

Are there any logging specific prerequisites on the server os?

 

20:35:27 (vd-name-string) TCP_NODELAY NOT enabled
20:35:27 (vd-name-string) Listener Thread: running
20:35:27 (vd-name-string) Starting diagnostics port listener thread (DPLT)
20:35:27 (vd-name-string) Starting diagnostics output thread (DRQT)
20:35:27 (vd-name-string) DPLT: running
20:35:27 (vd-name-string) DRQT: running
20:35:27 (vd-name-string) DPLT: terminating due to failure in creation of AF_LOCAL/AF_UNIX socket
20:35:27 (vd-name-string) DPLT: terminated
0 Kudos
(1) Solution

Hi  @cjustinek ,

Well checking any permission will not help in your use case as Windows Server 2016 is being used and we unfortunately do not support Diagnostic Functionality on this platform.

View solution in original post

0 Kudos
(4) Replies
jyadav
Flexera Alumni

Hi   @cjustinek,

The creation of the new socket file will fail if the calling process does not has write permission on the directory where the file is being created. Similarly, for connecting to a stream socket, the connecting process should have write permission on the socket.

Can you check the permissions of the toolkit directories?

To add to the above ,  Diagnostic Functionality is not supported on Windows Server 2016 platform. If you upgrade to 11.18.1 you will see the message has changed from 

8:05:50 (demo) DPLT: terminating due to failure in creation of AF_LOCAL/AF_UNIX socket 8:05:50 (demo) DPLT: terminated

to

8:05:50 (demo) DPLT: Diagnostic Functionality is unable to access AF_UNIX socket

8:05:50 (demo) DPLT: Diagnostic Functionality is not supported on this platform

cjustinek
Level 3

I don't get it fully. The license service which runs lmgrd.exe creates the debug log file without any issue. The lmgrd.exe starts the VD with the same user.

Which permission should I check here?

0 Kudos

Hi  @cjustinek ,

Well checking any permission will not help in your use case as Windows Server 2016 is being used and we unfortunately do not support Diagnostic Functionality on this platform.

0 Kudos
cjustinek
Level 3

Now I get your first original post. Thank you.

0 Kudos