Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The "default config" fallback doesn't work properly #3

Closed
Tracked by #1
srenatus opened this issue May 8, 2014 · 6 comments
Closed
Tracked by #1

The "default config" fallback doesn't work properly #3

srenatus opened this issue May 8, 2014 · 6 comments
Assignees
Labels

Comments

@srenatus
Copy link
Contributor

srenatus commented May 8, 2014

As figured out in #2, when there's an error in the config file, packetbeat logs that it will use the defaults. However, the following pcap.Openlive fails to open device:

# packetbeat -e -c /root/packetbeat.conf 
TOML config parsing failed on /root/packetbeat.conf: Near line 21, key 'protocols.http.ports': Near line 21: Expected an array value terminator ',' or an array terminator ']', but got '8' instead.. We will use defaults.
main.go:225: ERR  pcap.Openlive failed(): : No such device exists (SIOCGIFHWADDR: No such device))

I don't find any reference to defaults in the code either, but I've never used toml before...

Thanks
Stephan

@packetb-old packetb-old added the bug label May 8, 2014
@packetb-old packetb-old self-assigned this May 8, 2014
@packetb-old
Copy link

Thank you, I chose to just exit in case of errors to keep things simple.

@srenatus
Copy link
Contributor Author

srenatus commented May 9, 2014

Better indeed. Thanks. :)

@ubaidvh
Copy link

ubaidvh commented May 5, 2015

I have problem when i run this script :

docker run --net='container:ub-mysql' -t -i --name packetbeat-agent-ub packetbeat/packetbeat-agent packetbeat -e -c ~/ubaid/packetbeat.conf

this a response :
TOML config parsing failed on /home/administrator/ubaid/packetbeat.conf: open /home/administrator/ubaid/packetbeat.conf: no such file or directory. Exiting.

how to solve...????
couse packetbeat.conf is right file and in folder.
thank you....

@srenatus
Copy link
Contributor Author

srenatus commented May 5, 2015

@ubaidvh just a guess, but your shell might resolv the ~/ubaid/packetbeat.conf to /home/administrator/ubaid/packetbeat.conf, which doesn't exist in the container. Either correct the path or put the file there (cannot guess what you've done before). Not a packetbeat problem, I think.

@ubaidvh
Copy link

ubaidvh commented May 5, 2015

the file packetbeat.conf in my host.....
should be in a container...???

@srenatus
Copy link
Contributor Author

srenatus commented May 5, 2015

It should end in the container... (see the how to)

ruflin pushed a commit to ruflin/beats that referenced this issue Dec 2, 2015
shaunrampersad pushed a commit to shaunrampersad/packetbeat that referenced this issue Dec 2, 2015
Changed index from packetbeat-* to [packetbeat-]YYYY.MM.DD
tsg pushed a commit to tsg/beats that referenced this issue Jan 20, 2016
cwurm pushed a commit to cwurm/beats that referenced this issue Oct 7, 2019
kvch added a commit to kvch/beats that referenced this issue Dec 2, 2019
Co-Authored-By: DeDe Morton <dede.morton@elastic.co>
paylm pushed a commit to paylm/beats that referenced this issue Mar 2, 2023
Copy fundamental functionality from `github.com/elastic/beats/v7/libbeat/common`
tdancheva added a commit that referenced this issue May 29, 2023
tdancheva added a commit that referenced this issue Jun 5, 2023
* handle EOF on single line content (#33568)

* handle EOF on single line content

* changelog

* fallback to encode_eof if no events in aws-s3 input

* lint

* lint

* collect on EOF in line reader

* remove encode eof

* remove iterN

* fix test

* increase test coverage

* linting

* more linting

* increase coverage

(cherry picked from commit 7b45320)

# Conflicts:
#	libbeat/reader/readfile/line.go
#	libbeat/reader/readfile/line_test.go
#	x-pack/filebeat/input/awss3/s3_objects.go

* Fix conflicts

* Fix failing test - TestMaxBytesLimit

* Fix #2 failing test - TestMaxBytesLimit

* Fix failing test checks

* Fix linter errors

* Fix typo

* Fix linter errors #2

* Fix linter errors #3

* Fix linter errors #4

* Fix linter errors #5

* Changelog clean up

* Change order of publish event

---------

Co-authored-by: Andrea Spacca <andrea.spacca@elastic.co>
Co-authored-by: Tamara Dancheva <tamara.dancheva@elastic.co>
pkoutsovasilis added a commit that referenced this issue Feb 14, 2024
* feat: add helper funcs to get symbol info from /proc/kallsyms

* feat: introduce fixed executor that always runs funcs from the same os thread

* feat: add probe manager to handle building tracing kprobes from tk-btf ones

* feat: define probe events with corresponding alloc and release funcs

* feat: embed stripped btf files and add helper funcs to read them

* feat: add fsnotify, fsnotify_nameremove, fsnotify_parent and vfs_geattr tk-btf probe builders in probe manager

* feat: implement path traverser to produce monitor events by walking a path

* feat: implement directory entries cache

* feat: implement event processor to process probe events and based on directory entry cache emit the respective event

* feat: implement event verifier that validates that the expected sequence of generated fs events are properly emitted

* feat: add perfChannel to reduce tracing.PerfChannel boilerplate code and satisfy testing needs

* feat: implement monitor that ties together path traverser, perf channel and event emitting

* feat: implement probe verification at runtime and the creation of a new monitor based on these

* feat: implement event reader for kprobe-based file integrity module

* doc: update NOTICE.txt to include tk-btf license

* feat: add tests for non-recursive kprobe fim (#3)

* fix: remove existing file from cache when a move operation is overwriting it

* feat: introduce force_backend in for file integrity auditbeat module

* ci: add necessary volume mounts for kprobes backend in auditbeat docker-compose.yml

* feat: add the instantiation of file integrity module with kprobes backend

* doc: update CHANGELOG.next.asciidoc

* fix: address compilation issues for non-linux oses

* fix: correct folder permission for path traverser unit-test

* fix: build kprobe package and unit-tests only for linux

* ci: extend test_file_integrity.py to test kprobes backend of file integrity module

* ci: extend TestNew in monitor to include actual file changes

* ci: mark with nolint prealloc slices that can't be pre-allocated

* chore: inline defer funcs

* fix: return the scanner error if any

* fix: remove redundant runtime os checks for linux

* doc: comment that dEntryCache is not thread-safe

* fix: set the appropriate verbosity of errors of watcher

* fix: check for scanner.Err and return err from parsing mountinfo lines

* fix: remove redundant fim_backends list from test_file_integrity.py

* fix: gofumpt kprobes package

* fix: highlight unused context in event processor

* fix: increase interval period of wait_output as kprobes require more time to verify the probes and print output

* fix: proper formatting for auditbeat.reference.yml

* fix: proper formatting for x-pack/auditbeat/auditbeat.reference.yml

---------

Co-authored-by: Maxwell Borden <Tacklebox@users.noreply.github.com>
michel-laterman added a commit that referenced this issue May 15, 2024
michel-laterman added a commit that referenced this issue May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants