From jfricke at solvatis.de Wed Dec 14 05:01:29 2016 From: jfricke at solvatis.de (=?iso-8859-1?Q?j=FCrgen_fricke?=) Date: Wed, 14 Dec 2016 12:01:29 +0000 Subject: [Machinery] No machinery-helper available Message-ID: Hi folks, i try to gather information with machinery on a virtual server running a debian 8.6. Every time i got this error message: "There is no machinery-helper available for the remote system architecture x86_64" I check all requirements like tar, find, sed etc.pp. but i can't find what's going wrong. Any suggestions? Regards J?rgen -- Solvatis Consult GmbH & Co.KG Hohenzollernring 21-23, 50672 K?ln Tel +49-221-454 6400 Fax +49-221-454 6499 Internet www.solvatis.de From thardeck at suse.de Wed Dec 14 05:21:01 2016 From: thardeck at suse.de (Tim Hardeck) Date: Wed, 14 Dec 2016 13:21:01 +0100 Subject: [Machinery] No machinery-helper available In-Reply-To: References: Message-ID: <1ccbe956-69ed-9aa9-8f48-b3c5a0fa4872@suse.de> Hi J?rgen, On 14.12.2016 13:01, j?rgen fricke wrote: > Hi folks, > > > i try to gather information with machinery on a virtual server running a > debian 8.6. > > Every time i got this error message: "There is no machinery-helper > available for the remote system architecture x86_64" > > I check all requirements like tar, find, sed etc.pp. but i can't find > what's going wrong. > > Any suggestions? what did you use to run Machinery? Did you install one of our packages, the gem or do you use our git repository? And what architecture and OS does your host/machinery system have. Our package is shipped with helpers for different architectures, for the gem they should be build during installation time as a native extension and for Git they will be compiled on the first run. If you have an old Go version on a 32 bit distribution though and run Machinery from the sources or have installed the gem, then you would end up with only an i686 executable. In this case you could upate your Go version (at least 1.5) or copy the `machinery-helper-i686` binary in the machinery-helper directory to `machinery-helper-x86_64` which should work as long as 32 bit binaries are still executable on your x86_64 inspection system. Regards Tim -- SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) From jfricke at solvatis.de Thu Dec 15 05:34:13 2016 From: jfricke at solvatis.de (=?iso-8859-1?Q?j=FCrgen_fricke?=) Date: Thu, 15 Dec 2016 12:34:13 +0000 Subject: [Machinery] No machinery-helper available References: <1ccbe956-69ed-9aa9-8f48-b3c5a0fa4872@suse.de> <10944e95-d2b1-d7a4-bd06-dbc591f3f791@suse.de> Message-ID: > Anyway in the meantime you can go to the helper directory and run `go > build` and copy the `machinery-helper` binary to > `machinery-helper-x86_64` and `machinery-helper-i686` in the same directory. > > Afterwards the helper should be usable. > > Sorry, but now there is another error. :-( I build and copy the machinery-helper binarys as you recommend. Now the script is missing a directory at the remote server. "Error output: bash: /home/machinery/machinery-helper: No such file or directory" Regards J?rgen -- Solvatis Consult GmbH & Co.KG Hohenzollernring 21-23, 50672 K?ln Tel +49-221-454 6400 Fax +49-221-454 6499 Internet www.solvatis.de