Roberto Dip
08cd206de7
In https://github.com/fleetdm/fleet/pull/6630 I added a new config for packaging, but when I started the server I got: ``` ~/fleet $ ./build/fleet serve --dev --dev_license level=info ts=2022-07-13T21:36:06.055998Z component=redis mode=standalone fatal error: newproc: function arguments too large for new goroutine runtime stack: runtime.throw({0x103d85259, 0x37}) /Users/roperzh/.gvm/gos/go1.17/src/runtime/panic.go:1198 +0x54 runtime.newproc1(0x104569a30, 0x14000ffda28, 0x7f8, 0x140000001a0, 0x103bc85a4) /Users/roperzh/.gvm/gos/go1.17/src/runtime/proc.go:4299 +0x4d0 runtime.newproc.func1() /Users/roperzh/.gvm/gos/go1.17/src/runtime/proc.go:4255 +0x4c runtime.systemstack() /Users/roperzh/.gvm/gos/go1.17/src/runtime/asm_arm64.s:230 +0x6c goroutine 1 [running]: runtime.systemstack_switch() /Users/roperzh/.gvm/gos/go1.17/src/runtime/asm_arm64.s:187 +0x8 fp=0x14000ffd9c0 sp=0x14000ffd9b0 pc=0x102b60958 runtime.newproc(0x7f8, 0x104569a30) /Users/roperzh/.gvm/gos/go1.17/src/runtime/proc.go:4254 +0x54 fp=0x14000ffda10 sp=0x14000ffd9c0 pc=0x102b38034 main.runCrons({0x1045cd500, 0x14000262990}, {0x104611a38, 0x14000262930}, 0x14000298190, {0x1045a0480, 0x140009c9f20}, {{{0x103d1adc4, 0x3}, {0x103d2b188, ...}, ...}, ...}, ...) /Users/roperzh/fleet/cmd/fleet/serve.go:694 +0x2c4 fp=0x14000ffe260 sp=0x14000ffda10 pc=0x103bc85a4 main.createServeCmd.func1(0x1400027ca00, {0x140000bcb40, 0x0, 0x2}) ``` With my local changes, `serve.go:694` is this line: https://github.com/fleetdm/fleet/blob/7559988000efc3d7408d9914edd5a3f2f1052138/cmd/fleet/serve.go#L685-L686 After passing only a subset of the config the issue was solved.
Website News Report a bug
Fleet is the most widely used open source osquery manager. Deploying osquery with Fleet enables programmable live queries, streaming logs, and effective management of osquery across 100,000+ servers, containers, and laptops. It's especially useful for talking to multiple devices at the same time.
Try Fleet
With Node.js and Docker installed:
# Install the Fleet command-line tool
sudo npm install -g fleetctl
# Run a local demo of the Fleet server
sudo fleetctl preview
Windows users can omit
sudo, and should run the command inCmd/PowerShellas administrators.
The Fleet UI is now available at http://localhost:1337.
Now what?
Check out the Ask questions about your devices tutorial to learn where to see your devices in Fleet, how to add Fleet's standard query library, and how to ask questions about your devices by running queries.
Team
Fleet is independently backed and actively maintained with the help of many amazing contributors.
📖 In keeping with our value of openness, Fleet Device Management's company handbook is public and open source. You can read about the history of Fleet and osquery and our commitment to improving the product. To upgrade from Fleet ≤3.2.0, just follow the upgrading steps for the latest release from this repository (it'll work out of the box).
Documentation
Documentation for Fleet can be found here.
Community
Chat
Please join us in the #fleet channel on osquery Slack.
Contributing
Contributions are welcome, whether you answer questions on Slack/GitHub/StackOverflow/Twitter, improve the documentation or website, write a tutorial, give a talk, start a local osquery meetup, troubleshoot reported issues, or submit a patch. The Fleet code of conduct is on GitHub.
