How to use debug log to troubleshoot Everything freezing while scanning/indexing a mapped network drive

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
Skinerrrr!
Posts: 3
Joined: Tue May 05, 2020 5:56 pm

How to use debug log to troubleshoot Everything freezing while scanning/indexing a mapped network drive

Post by Skinerrrr! » Tue May 05, 2020 7:43 pm

I think Everything might be encountering a file or folder that's giving it trouble and I would like to troubleshoot this further.

The network drive in question is on a Mac computer, and the sharing protocol is SFTP. Windows sees it as mapped network drive "M:". I've been using this setup successfully for over a decade and I don't know what has suddenly changed. I upgraded to the latest version of Everything but it doesn't seem to have made a difference. I've also tried force rebuilding the database; no difference. When it freezes with "Scanning M:\" in the status line, it can sit there for hours. I try to close the Everything window and it goes to "Not Responding".

I can do

Code: Select all

dir m:\ /s/b
and it completes without an issue.

I made sure Everything was not showing as active in the Taskbar and System Tray, then launched Everything from a CMD prompt:

Code: Select all

C:\Program Files\Everything>everything -debug -debug-log
It doesn't run very long in the debug console, but the result doesn't show any of the file or folders it's scanning at all, neither C:\ nor the suspect M:\.

Code: Select all

C:\Program Files\Everything>type "%temp%\Everything Debug Log.txt"
2020-05-05 12:13:51.135: Everything
2020-05-05 12:13:51.141: Version 1.4.1.969 (x64)
2020-05-05 12:13:51.148: Windows NT 6.2
2020-05-05 12:13:51.155: Processors 8
2020-05-05 12:13:51.164: IsAdmin 0
2020-05-05 12:13:51.171: AppData 1
2020-05-05 12:13:51.181: Service 1
2020-05-05 12:13:51.188: cmdline everything  -debug -debug-log
2020-05-05 12:13:51.196: load localization
2020-05-05 12:13:51.206: lng file opened!
2020-05-05 12:13:51.223: header size 865
2020-05-05 12:13:51.234: version 1
2020-05-05 12:13:51.239: got header
2020-05-05 12:13:51.247: system default lid 0409
2020-05-05 12:13:51.254: count 37
2020-05-05 12:13:51.487: ole initialize: 00000000
2020-05-05 12:13:51.529: create mutex
2020-05-05 12:14:21.539: version send message failed
2020-05-05 12:14:21.645: mutex exists
2020-05-05 12:14:21.649: shutdown
2020-05-05 12:14:21.654: kill
2020-05-05 12:14:21.660: event start 0000000000000000

C:\Program Files\Everything>
Does anyone have any ideas on what I should try next?

void
Site Admin
Posts: 5367
Joined: Fri Oct 16, 2009 11:31 pm

Re: How to use debug log to troubleshoot Everything freezing while scanning/indexing a mapped network drive

Post by void » Wed May 06, 2020 2:52 am

Please try running a fresh Everything.exe process in debug mode:
  • Completely exit Everything (Right click the Everything tray icon and click Exit)
  • If there is a window open that is not responding, use the task manager to terminate Everything (make sure the Service process is still running)
  • Run Everything with the following command line option:
    Everything.exe -debug -verbose
  • As Everything indexes your network drive, each folder should be shown in yellow text in the debug console.

Skinerrrr!
Posts: 3
Joined: Tue May 05, 2020 5:56 pm

Re: How to use debug log to troubleshoot Everything freezing while scanning/indexing a mapped network drive

Post by Skinerrrr! » Thu May 14, 2020 1:57 am

The rescan has been running for days and it seems to be stuck in a loop, but it's difficult for me to figure out which file or directory because the debug screen scrolls so fast. I tried to resize the debug console wider in order to have it NOT line wrap, but the resize width is limited to the current desktop width. I tried the scroll lock but it doesn't do anything. If I hit the pause key, it'll stop but then I can't figure out how to have it resume without aborting with ctrl-c and starting over. If I go into the windows properties (Defaults, Properties) and expand the width to say 300 and the height to say 1000, it doesn't seem to make a difference. The most I've been able to capture to the clipboard is about 195 lines, but that isn't enough to detect where it reloops.

I hesitate to capture the log to a disk file as I fear it will fill up the drive too quickly but if I have to it would help if I could point it to a network drive instead of a local drive.

What are my options at this point?

void
Site Admin
Posts: 5367
Joined: Fri Oct 16, 2009 11:31 pm

Re: How to use debug log to troubleshoot Everything freezing while scanning/indexing a mapped network drive

Post by void » Fri May 15, 2020 7:51 am

Please try entering mark mode:
  • In the Everything Debug console, right click the window caption.
  • Under the Edit menu, click Mark.
  • This will pause Everything execution and allow you to read the console.
  • Use the mouse cursor to mask a selection.
  • Right click the selection to copy it to the clipboard (right clicking will end the mark mode and resume Everything execution).

Skinerrrr!
Posts: 3
Joined: Tue May 05, 2020 5:56 pm

Re: How to use debug log to troubleshoot Everything freezing while scanning/indexing a mapped network drive

Post by Skinerrrr! » Fri May 15, 2020 4:55 pm

use the task manager to terminate Everything (make sure the Service process is still running)
When nothing is visibly running (task bar, system tray), task manager sometimes shows two instances of Everything.exe, one with arg "-svc" (which I've been leaving running based on your comment above), and one with arg "-start" (which sometimes seems to disappear on its own).

While doing the debugging steps you've suggested, if I see an instance with "-start", should I terminate it or leave it?

therube
Posts: 2539
Joined: Thu Sep 03, 2009 6:48 pm

Re: How to use debug log to troubleshoot Everything freezing while scanning/indexing a mapped network drive

Post by therube » Fri May 15, 2020 7:30 pm

I see an instance with "-start"
I'm not seeing "-start"?
I see, "-startup" (& others) but not "-start"?


The -svc, is the Everything service, & that is fine.


-startup, if that is what it is, would run Everything - in the background (with no UI).
(You could then run Everything [or something like, Everything -instance xyz, if you used a named instance] to bring up a UI to interact with it).
(The -startup switch would still continue to show, because that is how you opened it, originally.)

Post Reply