disconnected from service, yet updates updated - Mostly
i was running a "FILELIST" instance -read-only -no-db,
orig 1318 (or so), then i changed that to 1332 once that was out
& during most of that time, my regular 15 instance was 1331
though
oh suckatash! i'm still running 1331 !
how did i manage that? well, there's only one way - me .
how do you like that! i put 1332 in, but actually ran 1331 instead of 1332!
oh well. anyhow...
so i'll often rename or delete or whatever in FILELIST
& with -no-db, i don't have realtime updates, so i kind of run blind,
unless i update the filelist.efu
& i do that as needed - easy
so anyhow, in FILELIST, i copied & deleted & updated (FILELIST),
but on FILELIST reload, it did not show all my changes,
as in 1 of the renamed files still shows the old filename
& 1 of my copies also does not show
- but, they both did happen
the renamed file is there, the copied file is there
but FILELSIT does not show it
& most oddly, neither does my (live) 15 instance
NOW, these changes were occurring on my H: drive
H:... oh, may not always be there, more so on cold days, & not too long
ago it was not, but the follow day (the next time i woke the computer
from sleep) it was back, & it's remained back till yesterday when it
decided not to turn up (oddly, as it was relatively warm), though today
it is back with me...
SMART shows UDMA CRC Error Count of 2
now when that became (2) i don't know? perhaps just now, & that caused
this oddity (or maybe its been there & now that i happen to be looking,
having noticed "something"... ?
OK, 11-2021 Count was 0. (At least by) 10-2022, Count was 2.
so that is unchanged to now.
FILELIST has no journal
1.5 journal shows 1 of 2 renames (but not the 1 on H:)
1.5 journal shows 1 of 2 creates (but not the 1 on H:)
the files, 1 created, 1 renamed, DO exist on H: & are valid & correct
but (the H: ones) are not seen in Everything 15 or FILELIST
if i rename them... ?
(i never got that far)
AH !!!
disconnected from service
Name: Everything
Version: 1.5.0.1331a (x86)
OS: Windows NT 6.1 7601 (x64)
IsAdmin: 0
Service: 6
Command line: -instance 15
why does it say that? though it sees changes nonetheless?
you know, when you do a dm:today & it happens to be the witching hour,
you oddly might not see a whole lot turn up
ok, so it is not seeing changes made to H:
(it does see changes elsewhere)
so... if i quit Everything, quit the service,
(& this time, correctly) fire up 1332... ?
& i'm back
both FILELIST (after updating it) & 15 are now correct
odd.
oh, & no longer, "disconnected from service"
---
note that when i reference "yesterday" & "today", above, it now is not longer yesterday or today - but more like last year .
disconnected from service, yet updates updated - Mostly
Re: disconnected from service, yet updates updated - Mostly
Heh. Shorter version.
I made changes (that were effected)
Changes did not show up (in Everything)
Notice, "disconnected from service"
Yet only 1 drive, H: as it was, was actually "disconnected from service" (or at least seemingly)
And all other drives looked (or at least the one other I experimented with), Everything did see those changes.
Odd.
I made changes (that were effected)
Changes did not show up (in Everything)
Notice, "disconnected from service"
Yet only 1 drive, H: as it was, was actually "disconnected from service" (or at least seemingly)
And all other drives looked (or at least the one other I experimented with), Everything did see those changes.
Odd.
Re: disconnected from service, yet updates updated - Mostly
Kind of related. (Or kind of not, but...)
Can I have a FILELIST -instance, with a .db, that is -read-only, that piggy-backs on my existing 15.db?
Such that -instance FILELIST isn't running using/update any FILELIST.db, but rather 15.db?
And kind of related to that (or kind of not, but...)...
If ES.exe requires GUI, can I likewise have a GUI -instance, that is always running (totally hidden is fine too), & that -instance GUI, also piggy-backs on my existing 15.db?
Such that -instance 15 can be closed (as odd as that might be), yet, ES.exe -instance GUI, would continue to work as expected, as it would actually be piggy-backing off of the 15.db.
Can I have a FILELIST -instance, with a .db, that is -read-only, that piggy-backs on my existing 15.db?
Such that -instance FILELIST isn't running using/update any FILELIST.db, but rather 15.db?
And kind of related to that (or kind of not, but...)...
If ES.exe requires GUI, can I likewise have a GUI -instance, that is always running (totally hidden is fine too), & that -instance GUI, also piggy-backs on my existing 15.db?
Such that -instance 15 can be closed (as odd as that might be), yet, ES.exe -instance GUI, would continue to work as expected, as it would actually be piggy-backing off of the 15.db.
Re: disconnected from service, yet updates updated - Mostly
Everything only needs the Everything Service to monitor changes to "system" volumes.
Everything can read changes to non-system volumes without administrative privileges.
A volume is determined to be "system" by the OS.
Typically the volume storing the OS or a pagefile is a "system" volume.
The question is now, why was the Everything Service not running?
(Everything 1.5 should automatically start the Everything Service)
Everything can read changes to non-system volumes without administrative privileges.
A volume is determined to be "system" by the OS.
Typically the volume storing the OS or a pagefile is a "system" volume.
The question is now, why was the Everything Service not running?
(Everything 1.5 should automatically start the Everything Service)
Re: disconnected from service, yet updates updated - Mostly
Not easily.Can I have a FILELIST -instance, with a .db, that is -read-only, that piggy-backs on my existing 15.db?
It could be done by disabling db_save_on_exit and using -db
Everything will load from the existing db, but never save to the db.
Your indexes would have to match, otherwise Everything would perform a fast reindex on startup.
ES requires the GUI.If ES.exe requires GUI, can I likewise have a GUI -instance, that is always running (totally hidden is fine too), & that -instance GUI, also piggy-backs on my existing 15.db?
It would be possible with the above steps.
However, you'll be double the amount of RAM and CPU everything uses.
I would recommend just keeping the normal 15 instance running.
Re: disconnected from service, yet updates updated - Mostly
So you're saying when the Console said "disconnected from service", that in fact means that the Service was not running - at all?The question is now, why was the Everything Service not running?
I took it to mean, in this case... well, I didn't really know what it meant, but I assumed, wrongly seemingly, that "something was wrong". And that, in this case, it "was" working for all drives, except for H:.
But you're saying it was simply not working at all.
(And other recent threads... I'm going to have to re-read...)
So, if it wasn't running at all, unless it happened to "crash" - unlikely, could it be that when I did (not, in actuality) switch from 1331 to 1332, that it was in fact not running all of that time? (I do manually -uninstall-service, & then -install-service when I change versions.) If I forgot to actually run the wanted version (1332), maybe ? I also forgot to actually -install-service too? While it is possible, these are the same motions I go through every time I put in a new version.
When I actually, correctly, put in 1332 (better said ran 1332), I didn't actually check to see if the Service was running, I just -uninstall-service, threw 1332 .exe in there, then -install-service. (And at that point, Console no longer showed "disconnected from service".)
And while we're here, Ctrl+`, isn't opening Console, here, for some reason.
Wonder why that is. (That's a puzzle that might have to wait.)
(Different -instance & 1324 works.)
(Different -instance & 1332 works.)
debug_console_keys are the same.
1354 & 448 are not duplicated anywhere in the .ini.
Ctrl+Shift+J (not that I ever knew that existed) works.
Heh. How silly (of me).
I should have opened Console, thrown out a Ctrl+`, & looked to see what it might have said.
Too late! I looked, & said, oh, I'm at a position where I can close... so I did.
(And on Everything restart, Ctrl+` is back.)
Re: disconnected from service, yet updates updated - Mostly
If I -uninstall-service, I get: "Service: 0 (disconnected / not installed)", which is different from the message above.
With the Service uninstalled, local NTFS updates are not seen.
With the Service uninstalled, local NTFS updates are not seen.
Code: Select all
Open pipe failed 2
Name: Everything
Version: 1.5.0.1332a (x86)
OS: Windows NT 6.1 7601 (x64)
IsAdmin: 0
Service: 0 (disconnected / not installed)
Command line: -instance 15
Binary: C:\DEV\LOCATE\Everything.exe
Profile: C:\DEV\LOCATE\Everything-15.ini
Database: C:\DEV\LOCATE\Everything-15.db
Instance: 15
Re: disconnected from service, yet updates updated - Mostly
Ah, I didn't pick this up immediately and now see the confusion.disconnected from service
Name: Everything
Version: 1.5.0.1331a (x86)
OS: Windows NT 6.1 7601 (x64)
IsAdmin: 0
Service: 6
"disconnected from service" here means Everything connected to the service to see if it is up and running.
It is up and running, so Everything then disconnects.
The "disconnected from service" message is just saying Everything checked for a connection (connected, then disconnected immediately).
Service: 6 shows the true status.
6 means: connected and service is partially installed.
This just means the Everything service is running (either as a normal admin process / index as admin process or another Everything.exe is hosting the Everything Service)
The message is a little different in v1332 and shows the service status tip, eg: Service 6 (connected / partially installed)