Naufal Jamal
11/30/2022, 6:48 PMsudo python setup.py install
its contacting internet to fetch these packages and just gets stuck. these packages are already in the host. how do i avoid fetching these packages from outside? currently my install stops at
Searching for argparse>=1.1
Reading <https://pypi.python.org/simple/argparse/>
install_requires=[
"thrift>=0.10",
"argparse>=1.1",
"future",
],
peanut butter
11/30/2022, 6:48 PMNaufal Jamal
11/30/2022, 10:06 PM>>> import osquery
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "build/bdist.linux-x86_64/egg/osquery/__init__.py", line 33, in <module>
File "build/bdist.linux-x86_64/egg/osquery/config_plugin.py", line 16, in <module>
File "build/bdist.linux-x86_64/egg/osquery/extensions/ttypes.py", line 9, in <module>
ImportError: No module named thrift.Thrift
>>>
Sandeep
12/01/2022, 1:25 AMNaufal Jamal
12/01/2022, 11:43 AM(osqueryvenv) python3 ./osquery_lldp_extension.py --socket /export/home/njamal/.osquery/shell.em
Traceback (most recent call last):
File "./osquery_lldp_extension.py", line 25, in <module>
@osquery.register_plugin
AttributeError: module 'osquery' has no attribute 'register_plugin'
Anoop K V
12/02/2022, 10:37 AMMo Zhu
12/02/2022, 6:47 PMKunal
12/05/2022, 4:03 PMReza Kazemy
12/05/2022, 4:41 PMwennan.he
12/07/2022, 12:26 AMAlexis
12/07/2022, 9:48 AMsystemd_units
table. I'm currently leveraging this table to make sure some services are running and be alerted otherwise. One of the use case is to monitor that we are wazuh-agent
running. However, on a couple of machines, Osquery results is not reliable:
Example:
Wazuh is running on this machine (using systemctl):
systemctl status wazuh-agent
β wazuh-agent.service - Wazuh agent
Loaded: loaded (/usr/lib/systemd/system/wazuh-agent.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2022-12-07 09:22:20 UTC; 19min ago
Process: 19921 ExecStop=/usr/bin/env /var/ossec/bin/wazuh-control stop (code=exited, status=0/SUCCESS)
Process: 19991 ExecStart=/usr/bin/env /var/ossec/bin/wazuh-control start (code=exited, status=0/SUCCESS)
Memory: 11.3M
CGroup: /system.slice/wazuh-agent.service
ββ20022 /var/ossec/bin/wazuh-execd
ββ20075 /var/ossec/bin/wazuh-agentd
ββ20094 /var/ossec/bin/wazuh-syscheckd
ββ20119 /var/ossec/bin/wazuh-logcollector
ββ20138 /var/ossec/bin/wazuh-modulesd
However, Osquery does not see at all this service on the box:
osquery> SELECT id, description, active_state, sub_state, fragment_path, user FROM systemd_units WHERE id LIKE 'wazuh%';
osquery>
This behaviour is just present on few machines - on all others, it 's working as expected.
Would someone know how can I debug this? Is there a solution?
Thank you.Graham Anderson
12/07/2022, 10:17 AMlevel=error ts=2022-12-07T10:10:15.110183011Z query=fleet_detail_query_network_interface_unix message="distributed query is denylisted" hostID=1
...
level=error ts=2022-12-07T10:10:35.499363345Z component=http method=POST uri=/api/v1/osquery/distributed/write took=3.131795221s ip_addr=10.244.3.87 x_for_ip_addr=10.244.3.87 ingestion-err="ingesting query software_linux: update host software: get software: context canceled" ingestion-err="ingest detail query: selecting app config: context canceled" ingestion-err="ingest detail query: selecting app config: context canceled" ingestion-err="ingest detail query: selecting app config: context canceled" ingestion-err="ingest detail query: selecting app config: context canceled" ingestion-err="ingest detail query: selecting app config: context canceled" ingestion-err="ingest detail query: selecting app config: context canceled" ingestion-err="ingest detail query: selecting app config: context canceled" ingestion-err="ingest detail query: selecting app config: context canceled" ingestion-err="ingest detail query: selecting app config: context canceled" ingestion-err="ingest detail query: selecting app config: context canceled" ingestion-err="ingest detail query: selecting app config: context canceled" ingestion-err="ingest detail query: selecting app config: context canceled" ingestion-err="ingest detail query: selecting app config: context canceled" err="error in query ingestion || error in query ingestion || error in query ingestion || error in query ingestion || error in query ingestion || error in query ingestion || error in query ingestion || error in query ingestion || error in query ingestion || error in query ingestion || error in query ingestion || error in query ingestion || error in query ingestion || error in query ingestion || getting app config: selecting app config: context canceled"
For the first type of error, in osquery docs it states:
If the watchdog stops the daemon while a distributed query was running then such query will be denylisted from running for 24 hours.However the host config using query shell
.show
offers the following:
Non-default flags/options:
database_path: /opt/orbit/shell/osquery.db
disable_events: true
disable_logging: true
disable_watchdog: true
So how can I prevent the NIC distributed query from being "denylisted"?
For the second error, I really don't know where to start for help resolving software packages being available for the hosts in fleet server π€·Artemis Tosini
12/07/2022, 8:45 PMJonathan H
12/08/2022, 12:28 AMMike Myers
12/08/2022, 6:59 AMpeanut butter
12/08/2022, 5:25 PMMichael Greenberg
12/11/2022, 11:20 AMosquery --json
via stdin) were
select sha1 from certificates where store_location = "LocalMachine" and upper(sha1) = '0C40F468D84B158856FFD52406378E397C016EF2' ;
select key from registry where key = 'HKEY_LOCAL_MACHINE\SOFTWARE\xxxxx' and name = 'yyyyy' and data like '0' ;
select name from windows_security_products where type = 'Antivirus' and state = 'On';
Is there any known issue that might cause this to happen ? Is there a way I can debug this?
This is with osquery 5.4.0
Thanksnick fury
12/12/2022, 7:54 AMR
12/12/2022, 2:34 PMAayush Jain
12/13/2022, 11:14 AMCould not connect to any of ['/tmp/pyosqsockndnbir6z']
My code was :
import osquery
instance = osquery.SpawnInstance()
instance.open()
result = instance.client.query("SELECT interface FROM interface_details;")
Is the correct way or I am doing something wrong ?Michael Greenberg
12/13/2022, 4:28 PMMario Bardowell
12/13/2022, 8:35 PMTruong Nhat
12/15/2022, 9:33 AMDavid
12/15/2022, 5:26 PMGenerating your osquery installer...
Windows Installer XML Toolset Toolset Harvester version
Copyright (c) .NET Foundation and contributors. All rights reserved.
=================================================================
Native Crash Reporting
=================================================================
Got a UNKNOWN while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
wine client error:2a:
=================================================================
Managed Stacktrace:
=================================================================
=================================================================
write: Bad file descriptor
Error: package root files: heat failed: exit status 1
Another user had this issue earlier this spring and following the recommendations found here https://github.com/fleetdm/fleet/issues/5713
I tried
docker buildx build --platform=linux/amd64
but got the following error any suggestions?
ERROR: "docker buildx build" requires exactly 1 argument.
Brandon Mesa
12/15/2022, 6:08 PMSlackbot
12/15/2022, 6:29 PMBamisebi OLuwapelumi
12/18/2022, 6:42 AMy0d4
12/20/2022, 1:12 PMwennan.he
12/21/2022, 7:24 PMEric G
12/21/2022, 7:40 PM