Troubleshooting
Collecting diagnostics
When something goes wrong and you write to support@yuvired.com, the fastest answer comes from a few facts and, for an install or service problem, one ZIP file from the support collector.
What YuviRed never does. The product has no crash reporter, no usage analytics and no support upload. Nothing leaves your computer unless you send it. The collector writes a file on the administrator's Desktop. You look through it and decide whether to send it.
1. Safe checks you can make first
These only read. They change nothing. Run them in Windows PowerShell as administrator on the server.
| Check | Command or place | Healthy result |
|---|---|---|
| Services | Get-Service YuviRed, YuviRedPostgres, YuviRedAgent | All three Running. (On another computer the agent service is SyntinelRedAgent, shown as YuviRed Endpoint Agent: Get-Service SyntinelRedAgent. The service name carries the product's earlier name; it will change in a later release.) |
| Service state | & "C:\Program Files\YuviRed\runtime\python.exe" "C:\Program Files\YuviRed\runtime\yuvired_service.py" status | Prints RUNNING (or STOPPED, START_PENDING, STOP_PENDING). It does not print the boot phase: read the next row for that. |
| Boot status file | Get-Content C:\ProgramData\YuviRed\status\boot-status.json | "phase": "YuviRed Ready". It carries no secrets. A phase of Error names the failed step. |
| Health | Invoke-WebRequest https://127.0.0.1:8443/api/health -SkipCertificateCheck (PowerShell 7) | Status code 200. In Windows PowerShell 5, open https://127.0.0.1:8443/api/health in a browser instead. |
| Ports | Get-NetTCPConnection -LocalPort 8443, 5440 -State Listen | Both listening |
| Network mode | & "C:\Program Files\YuviRed\runtime\python.exe" "C:\Program Files\YuviRed\runtime\yuvired_service.py" network --status | Shows the bind address, the firewall rule and whether it applies |
| Disk space | Get-PSDrive C | Free space is not close to zero |
| Time | w32tm /query /status | A recent "Last Successful Sync Time" |
Write down what you see. A line from the boot status file, or the phase from status, tells support more
than "it does not work".
2. Where the logs are
| Log | Where | Holds |
|---|---|---|
| Server application log | C:\ProgramData\YuviRed\logs\syntinel-red.log | The server's own messages. Rotates: 10 MB, 5 old files. |
| Service start logs | C:\ProgramData\YuviRed\logs\agent-start.log and local-enroll.log | How the server's own agent started and enrolled. |
| Database log | C:\ProgramData\YuviRed\pg\data\log\postgresql-<date>.log | One file per day. |
| Boot status | C:\ProgramData\YuviRed\status\boot-status.json | The boot phase and any error, no secrets. |
| Windows Event Log | Event Viewer, Windows Logs, Application, sources YuviRed and YuviRedAgent on the server, SyntinelRedAgent on another computer; and System, source Service Control Manager | Start and stop of the service. An error "YuviRed stopped at phase ..." names the phase it stopped in. |
| Server agent log | C:\ProgramData\SyntinelRed\logs\syntinel-agent.log | The server's own agent (the folder carries the earlier name, see section 1). |
| Agent log on another computer | C:\ProgramData\SyntinelRed\logs\syntinel-agent.log | Check-ins, errors, refused registrations. Up to 5 files of 5 MB. |
| Installer logs | %TEMP% of the administrator who ran the installer, and C:\Windows\Temp; names start YuviRed_Lite_ | What happened during an install. |
| In the console | Admin, System Logs | Live logs and the status of features, for administrators. |
3. Run the support collector
3.1 What it is
collect-install-evidence.ps1 is a script installed with the server. It only reads: it starts,
stops, deletes and repairs nothing. It makes one ZIP file.
It is made for a failed install or a service that does not run, but its ZIP is also the best starting point for most server problems.
3.2 Before you run it
Do not restart the computer, uninstall, repair or clean anything first. A restart finishes pending service deletions, and cleaning deletes the registrations. Either destroys the state that explains the failure. Run the collector first.
3.3 How to run it
Prerequisites. An administrator account on the computer where the problem is.
Steps.
- Open File Explorer at
C:\Program Files\YuviRed\support. If the install failed so early that nothing was installed there, write to support@yuvired.com and ask for the script. The script is installed on the server only. For a problem on a computer you added with **Add Computer**, copycollect-install-evidence.ps1from the server to that computer (any folder, for example the Desktop) and run it there: its10-agent.txtpart is made for that computer. Right-click
collect-install-evidence.ps1, Run with PowerShell. Or, in a PowerShell window:powershell -NoProfile -ExecutionPolicy Bypass -File "C:\Program Files\YuviRed\support\collect-install-evidence.ps1"If you are not an administrator, it asks for permission through the Windows prompt (UAC) and starts again.
- Wait until it prints the path of the ZIP. By default it looks back 3 days in the Windows event logs.
You can change it with
-Days 7.
You should see: a message that names the file:
YuviRed-install-evidence-<computer>-<yyyyMMdd-HHmmss>.zip on the Desktop of the administrator who ran it.
Options.
| Option | Does |
|---|---|
-Days 7 | Looks back 7 days in the Windows event logs (default 3). |
-OutDir D:\Evidence | Writes the ZIP there, not on the Desktop. |
-IncludeRawEventLogs | Also exports the raw Windows event logs. Do not use unless support asks. They cover every program on the computer and cannot be redacted. |
How to confirm. The ZIP exists, and opens, and README.txt inside lists what was collected and any
file that was removed because it could not be made safe. If the script cannot make a file safe and
cannot remove it, it makes no ZIP at all.
Common problems.
| Problem | What to do |
|---|---|
| "running scripts is disabled" | Use the full command above, which allows this one script. |
| No ZIP on the Desktop | You may have run it as a different administrator: look at that account's Desktop. Or the script named a file it could not make safe and stopped. |
| The script runs for a long time | It reads Windows logs and all installer logs. Wait a few minutes. |
Rollback. Nothing was changed. Delete the ZIP when it is no longer needed.
4. What the ZIP holds
Every text file is passed through a cleaner before it is packed. The ZIP holds:
| File or folder | Contents |
|---|---|
00-summary.txt | Windows version and build, language, last restart time, the Visual C++ runtime, antivirus and security software present, pending restarts, the installer file fingerprints |
01-services.txt | State, start type, account and failure settings of the three services, and the "marked for deletion" flag |
02-processes-network.txt | The YuviRed and database processes, what listens on ports 8443 and 5440, and the health check answer |
03-installed-products.txt | Installed YuviRed entries in Apps and Features, Windows Installer and the installer cache |
04-program-files.txt | The files under C:\Program Files\YuviRed, the current version file |
05-acls.txt | Folder permissions (names only) of the program and data folders |
06-programdata.txt | The names, sizes and times of the data folder, and copies of the status files, the logs, the database logs and the update journal |
07-logs\ | The installer logs that name YuviRed, from every user's temporary folder and C:\Windows\Temp |
08-msi-log-extract.txt | The lines of those logs about services, custom actions and errors |
09-eventlogs\ | A text extract of the Service Control Manager, Windows Installer, YuviRed and crash events |
10-agent.txt | On a computer added with Add Computer: the state of the agent service SyntinelRedAgent, versions, file names (never the agent's state folder or its settings file) and, under programdata\agent-logs\, the agent's logs. On the server itself this part reports that service as absent (the server's agent is YuviRedAgent); the agent's logs are still copied |
README.txt | What was collected, and what was removed |
What it deliberately leaves out: the secrets file yuvired.env, the database password file, the
HTTPS private key, the identity folder (private key and license cache), the database files, and the
agent's state and settings files.
What the cleaner does: known secret formats (passwords, keys, tokens, enrollment keys, key blocks, bearer headers) are replaced. Database logs keep only the time, severity and message header. The application log loses its SQL and parameter blocks.
5. What is sensitive in it, and what to remove
The cleaner only knows known formats. It is a best effort, not a guarantee. **Read the ZIP before you send it.**
Things the ZIP does contain that you may want to keep private:
- The computer name, the Windows user names that ran the installer (they appear in file paths and logs), and your server's address or DNS name.
- The names of other security software found on the computer.
- Server log lines that can mention computer names, user names and IP addresses of your endpoints and the email address of a person who signed in.
- File and folder names under the YuviRed folders.
- The product versions and the license state.
What to do:
- Unzip the file into a folder.
- Search it for anything you do not want to share (a person's name, a customer name, an address) and edit or delete that line or file. Say in your email what you removed.
- Zip the result again, or send the original if you removed nothing.
- Send it to support@yuvired.com. Do not post it in a public place. If it is too large for email, say so, and support will tell you how to send it.
Never send: the config folder, yuvired.env, the database folder, a password, an MFA or recovery
code, or an unused activation code.
6. What to write with it
- Your server's YuviRed version and build (console footer) and the installation ID.
- What you did, what you expected, what happened, and when (with the time zone).
- What you already tried.
- Whether any computers are affected, and which Windows versions.