Make: *** No rule to make target `setup'. Stop.- Custom beat

visasimbu · April 22, 2020, 10:34am

I am able to create custom beat and build (mage build) as per the documentation. But I am getting below error while executing make setup. Documentation is here.

[user@machineName test3]$ make setup
make: *** No rule to make target `setup'.  Stop.
[user@machineName test3]$ pwd
/home/user/elk/src/github.com/elastic/test3

Since this step is not successful, yml file is not created and resulted in execution error on beat. Am I missing something here ?

[user@machineName test3]$ ./test3 -e -d "*"
Exiting: error loading config file: stat test1.yml: no such file or directory

My input while creating beat

Enter the beat name [examplebeat]: test1
Enter your github name [your-github-name]: test2
Enter the beat path [github.com/test2/test1]: github.com/elastic/test3
Enter your full name [Firstname Lastname]: test4
Enter the beat type [beat]: beat
Enter the github.com/elastic/beats revision [master]: master

I have Makefile in /home/user/elk/src/github.com/elastic/test3.

Content of the make file is below

BEAT_NAME=test1
BEAT_PATH=github.com/elastic/test3
BEAT_GOPATH=$(firstword $(subst :, ,${GOPATH}))
SYSTEM_TESTS=false
TEST_ENVIRONMENT=false
ES_BEATS_IMPORT_PATH=github.com/elastic/beats/v7
ES_BEATS?=vendor/${ES_BEATS_IMPORT_PATH}
LIBBEAT_MAKEFILE=$(ES_BEATS)/libbeat/scripts/Makefile
GOPACKAGES=$(shell go list ${BEAT_PATH}/... | grep -v /tools)
GOBUILD_FLAGS=-i -ldflags "-X ${ES_BEATS_IMPORT_PATH}/libbeat/version.buildTime=$(NOW) -X ${ES_BEATS_IMPORT_PATH}/libbeat/version.commit=$(COMMIT_ID)"
MAGE_IMPORT_PATH=github.com/magefile/mage
NO_COLLECT=true
CHECK_HEADERS_DISABLED=true

# Path to the libbeat Makefile
-include $(LIBBEAT_MAKEFILE)

.PHONY: copy-vendor
copy-vendor:
 mage vendorUpdate

I have tried below make commands. Because i have seen same in MakeFile ($(GOPATH)/src/github.com/elastic/test3/vendor/github.com/elastic/beats/v7/libbeat/scripts)

make release
make snapshot

Error

Doing `require 'backports'` is deprecated and will not load any backport in the next major release.
Require just the needed backports instead, or 'backports/latest'.
>> Testing package contents
--- FAIL: TestRPM (0.00s)
    --- FAIL: TestRPM/test3-8.0.0-SNAPSHOT-aarch64.rpm_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestRPM/test3-8.0.0-SNAPSHOT-aarch64.rpm_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestRPM/test3-8.0.0-SNAPSHOT-i686.rpm_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestRPM/test3-8.0.0-SNAPSHOT-i686.rpm_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestRPM/test3-8.0.0-SNAPSHOT-x86_64.rpm_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestRPM/test3-8.0.0-SNAPSHOT-x86_64.rpm_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestRPM/test3-8.0.0-aarch64.rpm_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestRPM/test3-8.0.0-aarch64.rpm_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestRPM/test3-8.0.0-i686.rpm_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestRPM/test3-8.0.0-i686.rpm_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestRPM/test3-8.0.0-x86_64.rpm_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestRPM/test3-8.0.0-x86_64.rpm_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
--- FAIL: TestDeb (2.41s)
    --- FAIL: TestDeb/test3-8.0.0-SNAPSHOT-amd64.deb_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestDeb/test3-8.0.0-SNAPSHOT-amd64.deb_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestDeb/test3-8.0.0-SNAPSHOT-arm64.deb_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestDeb/test3-8.0.0-SNAPSHOT-arm64.deb_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestDeb/test3-8.0.0-SNAPSHOT-i386.deb_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestDeb/test3-8.0.0-SNAPSHOT-i386.deb_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestDeb/test3-8.0.0-amd64.deb_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestDeb/test3-8.0.0-amd64.deb_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestDeb/test3-8.0.0-arm64.deb_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestDeb/test3-8.0.0-arm64.deb_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestDeb/test3-8.0.0-i386.deb_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestDeb/test3-8.0.0-i386.deb_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
--- FAIL: TestTar (3.04s)
    --- FAIL: TestTar/test3-8.0.0-SNAPSHOT-darwin-x86_64.tar.gz_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-SNAPSHOT-darwin-x86_64.tar.gz_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-SNAPSHOT-linux-arm64.tar.gz_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-SNAPSHOT-linux-arm64.tar.gz_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-SNAPSHOT-linux-x86.tar.gz_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-SNAPSHOT-linux-x86.tar.gz_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-SNAPSHOT-linux-x86_64.tar.gz_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-SNAPSHOT-linux-x86_64.tar.gz_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-darwin-x86_64.tar.gz_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-darwin-x86_64.tar.gz_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-linux-arm64.tar.gz_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-linux-arm64.tar.gz_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-linux-x86.tar.gz_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-linux-x86.tar.gz_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-linux-x86_64.tar.gz_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: TestTar/test3-8.0.0-linux-x86_64.tar.gz_config_file_owner (0.00s)
        package_test.go:237: no config file found matching .*beat\.yml$|apm-server\.yml$
--- FAIL: Testuser (6.36s)
    --- FAIL: Testuser/test3-8.0.0-SNAPSHOT-linux-amd64.user.tar.gz_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
    --- FAIL: Testuser/test3-8.0.0-linux-amd64.user.tar.gz_config_file_permissions (0.00s)
        package_test.go:212: no config file found matching .*beat\.yml$|apm-server\.yml$
FAIL
FAIL    command-line-arguments  11.822s
FAIL
package ran for 2m53.153574155s
Error: running "go test /home/user/elk/src/github.com/elastic/test3/vendor/github.com/elastic/beats/v7/dev-tools/packaging/package_test.go -root-owner -files /home/user/elk/src/github.com/elastic/test3/build/distributions/*" failed with exit code 1
make: *** [release] Error 1
[user@mymachine test3]$

These also throws me an error from test folder. Still not sure what i am missing here ? Can anyone give some help on this ?

Note : I have python3 (Python 3.6.8) installed in my machine. I am using linux(RHEL 7) machine

whatgeorgemade · April 27, 2020, 10:50pm

Try make update. That should generate the config and fields files.

visasimbu · May 5, 2020, 8:51pm

Thanks for your reply. The given reply helped me to resolve my issue. Thank you.

system · June 6, 2020, 11:24am

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Unknown target specified: setup Beats	10	1438	February 2, 2019
Creating new beat throws an error Beats	1	279	April 4, 2019
Make setup throwing error Beats	4	319	January 24, 2019
Creating custom beat, "make package" fails with "make: *** No rule to make target 'package'. Stop." Beats beats-development	5	1803	May 8, 2019
Error creating new beat Beats beats-development	2	1136	May 9, 2020

Make: *** No rule to make target `setup'. Stop.- Custom beat

Related topics