Error 404 on renderjson.js three.js and OrbitControls.js

[zhivko]

I get folowing errors in web browser, after I start node-machinetalk-example with:
.../node-machinetalk-example$ node index.js

GET http://localhost:3000/components/renderjson/renderjson.js
localhost/:9 GET http://localhost:3000/components/threejs/build/three.js
localhost/:10 GET http://localhost:3000/components/threejs/examples/js/controls/OrbitControls.js
boundingbox.js:40 Uncaught ReferenceError: THREE is not defined(anonymous function) @ boundingbox.js:40context.execCb @ require.js:1678Module.check @ require.js:878Module.enable @ require.js:1165Module.init @ require.js:783callGetModule @ require.js:1192context.completeLoad @ require.js:1571context.onScriptLoad @ require.js:1699

Seems renderjson/renderjson.js is not part of repository - is this separate nodejs module?

[zhivko]

Here is screenshoot from debugger tools on chromium browser:

[bobvanderlinden]

Have you ran npm install under root by any chance? npm runs bower install after installing. Bower should then install threejs and renderjson.
However, bower refuses to install when ran under root :(. I've had this problem too when running things under Docker, bower silently would not install anything.

Whatever the case, you can run bower install manually:

node_modules/.bin/bower install

[zhivko]

No I have not run
npm install
under root.

Also I cannot do:
node_modules/.bin/bower install
since there is no .bin directory under node_modules.

Probably I should run:
sudo npm install -g bower
and then:
bower install

before:
npm install

If you think that is the right thing to do maybe you could put that into readme.md.

[zhivko]

this can be closed.

[bobvanderlinden]

Probably I should run:
sudo npm install -g bower
and then:
bower install

before:
npm install

This is what npm should be executing automatically using the postinstall script.
What version of npm and node are you running? I'd like to simulate your environment before adding it to the readme.
You can check the versions using:

$ node --version
v5.3.0
$ npm --version
3.5.2

[zhivko]

kz@klemenHp:/mnt/Extra10Gb/git/node-machinetalk-example$ node --version
v0.10.25
kz@klemenHp:/mnt/Extra10Gb/git/node-machinetalk-example$ npm --version
1.4.21
kz@klemenHp:/mnt/Extra10Gb/git/node-machinetalk-example$ uname -a
Linux klemenHp 3.19.0-42-generic #48-Ubuntu SMP Thu Dec 17 22:55:02 UTC 2015 i686 i686 i686 GNU/Linux

I will try to get higher version with on my Ubuntu box with:
curl -sL https://deb.nodesource.com/setup_5.x | sudo -E bash -
sudo apt-get install -y nodejs

OK now I have:
kz@klemenHp:/mnt/Extra10Gb/git/node-machinetalk-example$ node --version
v5.3.0
kz@klemenHp:/mnt/Extra10Gb/git/node-machinetalk-example$ npm --version
3.3.12

Will try to rerun machinekit-example client.

[zhivko]

This could be related to error on BBB - I have in /var/log/syslog:
But I guess I need to open another issue. Do you maybe know what component is not correctly configured?

ec 27 02:03:37 beaglebone msgd:0: ulapi:17587:user hal_xinit:239 HAL: hal_lib17587 initialization complete
Dec 27 02:03:37 beaglebone msgd:0: hal_lib:17587:user hal_xinit:246 HAL: legacy component 'halcmd17587' id=645 initialized
Dec 27 02:03:40 beaglebone avahi-daemon[532]: server.c: Packet too short or invalid while reading known answer record. (Maybe a UTF-8 problem?)
Dec 27 02:03:41 beaglebone avahi-daemon[532]: server.c: Packet too short or invalid while reading known answer record. (Maybe a UTF-8 problem?)
Dec 27 02:03:43 beaglebone avahi-daemon[532]: server.c: Packet too short or invalid while reading known answer record. (Maybe a UTF-8 problem?)
Dec 27 02:03:49 beaglebone avahi-daemon[532]: server.c: Packet too short or invalid while reading known answer record. (Maybe a UTF-8 problem?)

And in linuxcnc.log this line is strange:
Dec 27 08:19:35 beaglebone webtalk: webtalk: talking Machinekit http on '(null)'

on '(null)' ?

Dec 27 08:19:35 beaglebone webtalk: [0.013636] NOTICE:  Compiled with OpenSSL support
Dec 27 08:19:35 beaglebone webtalk: [0.013674] NOTICE:  Using non-SSL mode
Dec 27 08:19:35 beaglebone webtalk: [0.067490] NOTICE:  Listening on port 7681
Dec 27 08:19:35 beaglebone webtalk: register_stuff: actual hostname as announced by avahi='beaglebone.local'
Dec 27 08:19:35 beaglebone webtalk: webtalk: talking Machinekit http on '(null)'
Dec 27 08:19:35 beaglebone webtalk: zeroconf: registering: 'Machinekit on beaglebone.local pid 22444'
Dec 27 08:19:35 beaglebone webtalk: webtalk: signal 15 - 'Terminated' received
Dec 27 08:19:35 beaglebone webtalk: [0.437381] NOTICE: libwebsocket_context_destroy
Dec 27 08:19:35 beaglebone webtalk: webtalk: exiting mainloop (interrupted)
Dec 27 08:19:35 beaglebone webtalk: zeroconf: unregistering 'Machinekit on beaglebone.local pid 22444'
Dec 27 08:22:52 beaglebone msgd:0: msgd:0: got signal 15 - sending SIGTERM to rtapi (pid 17190)
Dec 27 08:22:52 beaglebone msgd:0: msgd:0: Terminated - shutting down
Dec 27 08:22:52 beaglebone msgd:0: zeroconf: unregistering 'Log service on beaglebone.local pid 17183'
Dec 27 08:22:52 beaglebone msgd:0: log buffer hwm: 9% (496 msgs, 47740 bytes out of 524288)
Dec 27 08:22:52 beaglebone msgd:0: sent SIGTERM to rtapi (pid 17190)
Dec 27 08:22:52 beaglebone msgd:0: normal shutdown - global segment detached

[zhivko]

So I can list machines from node-machinetalk:

kz@klemenHp:~/git/node-machinetalk/examples$ node list-machines.js 
*** WARNING *** The program 'nodejs' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs>
*** WARNING *** The program 'nodejs' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs&f=DNSServiceRegister>
Machine 72c3f16f-59c3-4116-ba4f-709959abb157 up
Machine 72c3f16f-59c3-4116-ba4f-709959abb157 : Service log : tcp://beaglebone.local:49152
Machine 72c3f16f-59c3-4116-ba4f-709959abb157 : Service log : tcp://beaglebone.local:49152

but trying node-machinetalk-example project I get:

kz@klemenHp:~/git/node-machinetalk-example$ node index.js 
*** WARNING *** The program 'nodejs' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs>
*** WARNING *** The program 'nodejs' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs&f=DNSServiceRegister>
listening on http://localhost:3000/
Browser error { [Error: getaddrinfo -3008] code: -3008, errno: -3008, syscall: 'getaddrinfo' }
Browser error { [Error: getaddrinfo -3008] code: -3008, errno: -3008, syscall: 'getaddrinfo' }

And no machines listed on
httt://localhost:3000

Any idea?

[bobvanderlinden]

Alright. This is indeed related to #17. node_mdns needs to be fixed. The fix is already available, but was not used yet as it is not in a released version of node_mdns. There isn't a 'stable' version available yet.
However, the latest development version of node-machinetalk-example on Git now points to the latest development version of node-machinetalk, which points to a patched version of node_mdns.
If you pull node-machinetalk-example (git pull), delete node_modules (rm -rf node_modules) and run npm install again, you should get the patched version as well, which should not give the getaddrinfo -3008 errors anymore.

[zhivko]

"latest development version" == bleading branch on node-machinetalk-example?

[zhivko]

OK - there is no error anmore but machines box is still empty :)
although I have machinekit running on bbb:
kz@klemenHp:~/git/node-machinetalk-example$ avahi-browse -a

• wlan0 IPv6 Log service on beaglebone.local pid 3195 _machinekit._tcp local
• wlan0 IPv4 Machinekit _machinekit._tcp local
• wlan0 IPv4 Log service on beaglebone.local pid 3195 _machinekit._tcp local
• wlan0 IPv6 Machinekit on beaglebone.local pid 3162 Web Site local
• wlan0 IPv4 Machinekit on beaglebone.local pid 3162 Web Site local
• wlan0 IPv6 klemenHp [00:22:fa:c5:c4:50] Workstation local
• wlan0 IPv4 klemenHp [00:22:fa:c5:c4:50] Workstation local
• wlan0 IPv6 klemenHp Remote Disk Management local
• wlan0 IPv4 klemenHp Remote Disk Management local
• wlan0 IPv6 beaglebone [54:4a:16:c5:d0:2a] Workstation local
• wlan0 IPv6 beaglebone Remote Disk Management local
• wlan0 IPv4 beaglebone [54:4a:16:c5:d0:2a] Workstation local
• wlan0 IPv4 beaglebone Remote Disk Management local

[bobvanderlinden]

I don't see the machinetalk services being online now in that output,
whereas your earlier comment (
#17 (comment))
did show online machinetalk services (command, error, status, preview,
etc). Are you sure you're running mkwrapper in Machinekit?

On Sun, Dec 27, 2015, 23:34 zhivko notifications@github.com wrote:

OK - there is no error anmore but machines box is still empty :)
although I have machinekit running on bbb:
kz@klemenHp:~/git/node-machinetalk-example$ avahi-browse -a

• wlan0 IPv6 Log service on beaglebone.local pid 3195 _machinekit._tcp
  local
• wlan0 IPv4 Machinekit _machinekit._tcp local
• wlan0 IPv4 Log service on beaglebone.local pid 3195 _machinekit._tcp
  local
• wlan0 IPv6 Machinekit on beaglebone.local pid 3162 Web Site local
• wlan0 IPv4 Machinekit on beaglebone.local pid 3162 Web Site local
• wlan0 IPv6 klemenHp [00:22:fa:c5:c4:50] Workstation local
• wlan0 IPv4 klemenHp [00:22:fa:c5:c4:50] Workstation local
• wlan0 IPv6 klemenHp Remote Disk Management local
• wlan0 IPv4 klemenHp Remote Disk Management local
• wlan0 IPv6 beaglebone [54:4a:16:c5:d0:2a] Workstation local
• wlan0 IPv6 beaglebone Remote Disk Management local
• wlan0 IPv4 beaglebone [54:4a:16:c5:d0:2a] Workstation local
• wlan0 IPv4 beaglebone Remote Disk Management local

—
Reply to this email directly or view it on GitHub
#16 (comment)
.

[zhivko]

Ups :)
I am using

rundemo

from
git/machinekit/src/machinetalk/tutorial/motorctrl

So I suppose mkwrapper is the right tool to run on BBB.
Have I miss that information? It would be nice to put that in readme.MD (I mean what to run on BBB side so node-machinetalk could work).