babbu9
Flexera beginner

/dev/shm/FlexNetFs.77240’: Transport endpoint is not connected

We are noticing an error on RedHat Linux 7.9 when checking the filesystems.

 

-bash-4.2$ df -h
df: ‘/dev/shm/FlexNetFs.77240’: Transport endpoint is not connected

 

What is this error and how to resolve it. 

0 Kudos
6 Replies
jyadav
Revenera
Revenera

@babbu9  This is more of a environment specific error(not specific to FNP) and here are a few things you could try

1.Reboot the system and see if it resolves the issue.

2.Simply unmount and remount the mountpoint with elevated privileges. 

This typically is caused by the mount directory being left mounted due to a crash of your filesystem.

0 Kudos
abhayparashar
Active participant

This observation is mostly reported in case the application exited unexpectedly and the FUSE mount-point was orphaned (and unusable) and a new mount-point will be created. This should be fixed post a system restart.

To add, these file systems are not designed to be accessed by any application other than FNP.

0 Kudos

Hi

Thank you for the reply. The issue is happening so often that reboot is not an option. Is there a permanent fix to the issue. 

0 Kudos

Can you confirm the FNP toolkit version in use?

0 Kudos

version is 11.17.2.0.

0 Kudos
babbu9
Flexera beginner

Hi

Thanks for helping out on this. Do you have an update as to what is causing this?

Below is additional info I would like to share:

-bash-4.2$ df -h
df: ‘/dev/shm/FlexNetFs.25387’: Transport endpoint is not connected
Filesystem Size Used Avail Use% Mounted on
devtmpfs 16G 8.0K 16G 1% /dev
tmpfs 16G 340M 16G 3% /dev/shm

-bash-4.2$ ll/dev/shm output: There is one directory that has transport issue (FlexNetFs.25387) and another new directory that is created by the FlexNet process.

-bash-4.2$ ll/dev/shm

d?????????? ? ? ? ? ? FlexNetFs.25387
dr-xr-xr-x. 3 owner owner 1024 Aug 17 22:18 FlexNetFs.70835

0 Kudos