Other Firefox profiles problem on NFS Home Directories

Datapanic

Datapanic

I've had this problem for a while, since upgrading from FreeBSD 11.4 to 12.2 with Firefox and its profiles directory located on my home directory on a FreeBSD 12.2 ZFS filesystem exported to NFS.

The specific error is, when Firefox (versions from at least 90.0 to 93.0) first starts up on my FreeBSD 12.2 workstation: "The bookmarks and history system will not be functional because one of Firefox's files is in use by another application. Some security software can cause this problem. " Then there is a link to: https://support.mozilla.org/en-US/kb/fix-bookmarks-and-history-will-not-be-functional The solutions provided to fix the problem do not work, nor does removing the ~/.mozilla and ~/.cache/.mozilla directories and starting fresh.

When I reconfigure the workstation to use a home directory on local storage, everything works and the error does not occur. The ~/.mozilla and ~/.cache/.mozilla files and permissions are identical on the local storage and NFS mount, except for the random profile subdirectory names.

I also duplicated the error on an eeePC netbook.

On the ZFS storage system, my zpool is named VD0 and the contents of /etc/exports is:

/mnt/VD0 -alldirs -maproot=root:wheel -network x.x.x.0/24

On the workstation, /etc/fstabs has this:

x.x.x.12:/mnt/VD0/HOME /usr/home nfs rw 0 0

Firefox is at the latest version 93.0 built on my Poudriere system with default options and the FreeBSD workstation and ZFS storage are at 12.2-RELEASE p10.

I didn't have this problem when the workstation and storage were running FreeBSD 11.4. I'm at a loss on this one and it would be great to get some help solving the problem because I want to use my networked home directory again.
 
At <https://firefox-storage-test.glitch.me/> do you have Good: Totally Working. (fullyOperational) for all four subsystems?

When you log out from your desktop environment, shut down or restart: do you first quit Firefox and ensure that its processes have ceased running?

We have a few mentions of NFS in <https://cgit.freebsd.org/src/tree/UPDATING>, anything relevant?

Datapanic said:
… removing the ~/.mozilla …
Click to expand...

If removal could be the workaround, it would probably suffice to remove just one file: the lock, from the root directory of the affected profile.

Here, without NFS, whilst Firefox runs:

Code: 
% file ./lock
./lock: broken symbolic link to 127.0.0.1:+49702
%

An htop(1) view of the tree for the corresponding process ID (49702):

1633749410447.png

Also:

Code: 
% file ./.parentlock
./.parentlock: empty
% pkg info -x firefox
firefox-93.0,2
% uname -KU
1400034 1400034
% freebsd-version -kru
14.0-CURRENT
14.0-CURRENT
14.0-CURRENT
%

I can't recall the significance of .parentlock, but it's present here for at least one non-running profile so for your case, it might be negligible.

Side note

FreeBSD bug 259020 – sysutils/htop manual page for htop(1) not found
 
grahamperrin said:
At <https://firefox-storage-test.glitch.me/> do you have Good: Totally Working. (fullyOperational) for all four subsystems?
Click to expand...

When running that test with a local home directory, it's all good, but with a networked home directory and a never ran before instance of firefox and its creation of the .mozilla directory and a new profile, I get this:

Code: 
Overview:
Storage is broken. This is your first visit or all storage was automatically cleared.
Specific Subsystem Statuses:

LocalStorage
    Bad: Our test logic is broken, please copy and paste the contents of 'Debug Info' below and anything in the devtools console and send to :asuth. (unexpectedBreakage)
QuotaManager
    Bad: Totally Broken. (fullyBroken)
IndexedDB
    Bad: Totally Broken. (fullyBroken)
Cache API
    Bad: Totally Broken. (fullyBroken)

Debug Info:


storage.estimate() threw: Internal error while estimating storage usage
Failed to create "persistent" IDB.
Failed to create "transient" IDB.

{
  "v": 1,
  "curVersion": 93,
  "prevVersion": 0,
  "ls": {},
  "qm": {
    "lastWorkedIn": 0
  },
  "idb": {
    "persistentCreatedIn": 0,
    "persistentLastOpenedIn": 0,
    "clearDetectedIn": 0
  },
  "cache": {
    "firstCacheCreatedIn": 0,
    "unpaddedOpaqueCreatedIn": 0,
    "paddedOpaqueCreatedIn": 0
  }
}

I'm not sure what to make of that and the "Our test logic is broken" message. I do not think my storage is broken - I also tried it on another FreeBSD 12 NFS server with a freebsd-ufs partition and exported a mount point for a networked home directory and got the same error.

I am also going through the notes at https://cgit.freebsd.org/src/tree/UPDATING

Thanks for helping!
 
Datapanic said:
I'm not sure what to make of that and the "Our test logic is broken" message.
Click to expand...

I'm similarly unsure. If it helps, via <https://old.reddit.com/comments/9nmtwj/firefox_storage_test/e7niccg/>:
– beware of what may be false negatives if the test is run in that context.

Better to test with <https://firefox-storage-test.glitch.me/>.

With a new profile and a local home directory: Good: Totally Working. (fullyOperational)
 
You must log in or register to reply here.
Back
Top