mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #828] Blank disk list in Summary #523
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#523
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @silversword411 on GitHub (Nov 26, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/828
Originally assigned to: @wh1te909 on GitHub.
Have a machine with 7 Disks, but the disk list is blank.
Buffer overflow?
@wh1te909 commented on GitHub (Nov 27, 2021):
I just simulated 7 disks and it shows up properly. Most probably that agent is having issues getting the list of disks. please check in django admin, Agents > Agents and click on the agent hostname then look for the "Disks" field. it might be empty. if so then run the tacticalrpc service in debug mode on the agent, then from summary tab on web UI click the refresh button and send me the full output from the agent
@silversword411 commented on GitHub (Nov 27, 2021):
Well...it started with
and then refreshing with debug made all the disks appear. Computers #ShakesHead
@silversword411 commented on GitHub (Nov 28, 2021):
So apparently it will work fine in debug mode, but not running from standard service.
Completely uninstall tactical agent and reinstalled. No difference.
Tried changing the service to log in debug mode when started from service interface (so running as local system with no service interact with desktop) that didn't work
Any other ideas to try?
@silversword411 commented on GitHub (Nov 28, 2021):
I started checking a little more, thought it was just my PC...but I've found 9 different machines with all different kinds of disk configurations/controllers etc.
Can't find anything consistent between any of them.
Running in debug mode with
"C:\Program Files\TacticalAgent\tacticalrmm.exe" -m rpc -log debug -logto stdoutit starts working. Stopping that, and just running the regular service and the disk config disappears.Side effect from the coloring of the bar graphs?
github.com/wh1te909/tacticalrmm@b6f8d9cb25@wh1te909 commented on GitHub (Nov 29, 2021):
please replace
tacticalrmm.exein prog files with the attached file (stop both services first)then to edit the service parameters you have to use nssm, see screenshot below.
just add
-log debugto the arguments field and the start the servicethen refresh the summary tab and it should log everything to the
agent.logfile, please send me thattacticalrmm-debug.zip
@silversword411 commented on GitHub (Dec 7, 2021):
We found the problem...it was Google Drive fake g: being mounted from user context.
@silversword411 commented on GitHub (May 10, 2022):
Note to self: This also has the side-effect of not being able to create checks for low disk space as well, test that when fixed
https://discord.com/channels/736478043522072608/921073571344830494
@silversword411 commented on GitHub (Aug 28, 2023):
@wh1te909 Reminder: Switching between python and go to detect drive letters was how we worked around it back in 2021 :)
@silversword411 commented on GitHub (Jan 9, 2024):
I wonder if we can filter the Disk list to only physical/USB and then return that data as a workaround.
@cloud303-cdedrick commented on GitHub (Nov 19, 2024):
@wh1te909 Is there any update on this? We are trying to role to our company but many of the users have Google Drive installed.
@volkswagner commented on GitHub (Dec 7, 2024):
I'm seeing the same symptom when client PC has Google Drive mounted. Sometimes the C: drive will show up under disks, typically immediately after reboot or forcing disk check in RMM. (but not always).
RMM server .20.0
Client version 2.8.0
@AdelantiaDev commented on GitHub (Jan 27, 2025):
@wh1te909 Is there any update on this? Or planned to fix?
@wh1te909 commented on GitHub (Apr 21, 2025):
fix will be in the next release