Everything 1.5.0.1423b (x64)
Everything Server Plugin 1.0.4.5.x66
Everything HTTP Server Plugin 1.0.4.5.x64
Setting up some trials on my homelab to index my network drive from a VM and serve that up to my local PCs and other VMs.
So ... I think all is working properly except the HTTP Server Logging ...
Everything.exe is located in and running from C:\EverythingServer\Everthing.exe. The Server and HTTP plugins in the Plugins subfolder of the same directory, AppData is turned off and it seems all ini and other files (including the .db) are created inside that same directory. The service is installed and works correctly starting up as the VM boots before any user logs in. Everything responds instantly on remote machines to queries both in a client with the Remote Index setup -or- from a browser accessing the HTTP Server. It also seems to work properly when the service is stopped and C:\EverythingServer\Everthing.exe is launched as Administrator.
Life is all good ... Except ... except that i cant seem to get the HTTP_Server_Log.txt to populate with anything. It remains completely blank.
At first I was also struggling with basic Search History.csv, but I discovered that i needed to go into all of the folders' security settings and fully enable all permissions for both Administrator and SYSTEM users for the app mode and service mode respectively. Once I did that, the app mode interface now logs queries to the Search History.csv file ... but I'm still unable to get the HTTP Server to log anything to HTTP_Server_Log.txt. I have tried inside the C:\EverythingServer\Logs\ folder too (again, with all permissions set to full access) and no luck there. Somewhere i also read about creating a HTTP Server subfolder (i think that was ChatGPT, actually -- and the suggestion was based on a .gif warning that was coming up in the logs) but that didnt help and the folder has remained empty.
Thoughts?
Also, side question that maybe i should post separately about: is there a way to log queries that hit the Everything Server (not the HTTP one ... the one that serves out to the remote client installs of Everything)? I know they can be logged via the local client to the local client's machine, but I'm wondering if they also could be logged server-side?
HTTP Server Logging not working
-
void
- Developer
- Posts: 20303
- Joined: Fri Oct 16, 2009 11:31 pm
Re: HTTP Server Logging not working
Everything HTTP Server 1.0.5.6 adds log flushing.
Sorry, this was added a while ago and I never published it.
Old versions would buffer the log before writing it to disk.
The debug logs can grow very quickly.
The logs show basic connection information, disconnects, request information, snapshot creation and journal requests.
Sorry, this was added a while ago and I never published it.
Old versions would buffer the log before writing it to disk.
Debug logging can be enabled in Everything hosting the Everything Server.Also, side question that maybe i should post separately about: is there a way to log queries that hit the Everything Server
The debug logs can grow very quickly.
The logs show basic connection information, disconnects, request information, snapshot creation and journal requests.
-
fji
- Posts: 2
- Joined: Thu Sep 17, 2026 3:43 pm
Re: HTTP Server Logging not working
Thanks! This seems to be logging now.void wrote: Fri Sep 18, 2026 3:02 am Everything HTTP Server 1.0.5.6 adds log flushing.
Sorry, this was added a while ago and I never published it.
Old versions would buffer the log before writing it to disk.
Okay. I checked it out quickly. It doesnt seem to log the search terms typed into a remote client. Is that because each client stores its own copy of the database locally?void wrote: Fri Sep 18, 2026 3:02 am Debug logging can be enabled in Everything hosting the Everything Server.
-
void
- Developer
- Posts: 20303
- Joined: Fri Oct 16, 2009 11:31 pm
Re: HTTP Server Logging not working
Yes, clients have a copy of the server index and perform the search locally.Okay. I checked it out quickly. It doesnt seem to log the search terms typed into a remote client. Is that because each client stores its own copy of the database locally?