Skip to main content

Cannot access gvfs Transport endpoint is not connected

Cannot access gvfs Transport endpoint is not connected


While doing df -h getting below error:

df -h

df: â/run/user/0/gvfsâ: Transport endpoint is not connected

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/ol-root 40G 6.7G 34G 17% /
devtmpfs 3.8G 0 3.8G 0% /dev
tmpfs 3.8G 172K 3.8G 1% /dev/shm
tmpfs 3.8G 494M 3.3G 13% /run


Solutions:


The error message "ls: cannot access 'gvfs': Transport endpoint is not connected" typically occurs when there is an issue with the GVFS (GNOME Virtual File System) service in Linux. GVFS is responsible for providing a virtual file system layer that allows applications to access files and folders


Solution 1:

cd /run/user/0

fusermount -zu gvfs

For me this solution fixed the problem

Solution 2:

Restart the GVFS service: Restarting the GVFS service may resolve the problem. You can do this by restarting the corresponding service using the following command:

systemctl --user restart gvfs-goa-volume-monitor.service



Solution 3:

gvfsd --kill

Afterward, the GVFS daemon will automatically restart.



If you like please follow and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

EBS 12.2 ADOP Interview Questions With Scenarios

EBS 12.2 ADOP Interview Questions With Scenarios Note: Check the patch cycle log is important to fix any issues.  Location: $ADOP_LOG_HOME Useful Adop Commands Click here 1.What is ADOP concept in oracle apps Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. 'adop' is the utility we use to apply patches in R12.2 2.What is PATCH_TOP directory in R12.2 In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to $NE_BASE/EBSapps/patch $NE_BASE points to <Non-Editioned-filesystem-directory> Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files. If you are planning to put patches in non-defualt location then you need to use adop parameter 'patchtop=<patch_path>' to...