I think the 5th line tells all:
/usr/libexec/linuxcnc/rtapi_msgd: FATAL - will not run as root

As you run machinekit as root.

Why do you run as root?

Did you build machinekit from source?
If so, did you 'sudo make setuid' after building?


> On 20 May 2017, at 14:15, Simon Mali <smal....@gmail.com> wrote:
> 
> Hello
> @Bas de Bruijn: I have enabled all debug printouts as proposed but I can 
> still not localize the error in printout.
> 4a. I have put this in my ini file:
> 
> DEBUG = 0x7fffff
> 
> 4b. Then I have opened my LX-root terminal and I was trying to start 
> machinekit manually:
> 
> export DEBUG=5
> root@beaglebone:/home/machinekit# sudo machinekit 
> /home/machinekit/machinekit/configs/CNC_3D_UHU_SEM600/BBB-3D-CNC.ini |&tee 
> /tmp/log.txt
> 
> As an answer from machinekit here is the printout from this log.txt:
> 
> MACHINEKIT - 0.1
> Machine configuration directory is 
> '/home/machinekit/machinekit/configs/CNC_3D_UHU_SEM600'
> Machine configuration file is 'BBB-3D-CNC.ini'
> Starting Machinekit...
> (time=1495280034.307189,pid=1455): Registering server on TCP port 5005.
> (time=1495280034.307766,pid=1455): running server for TCP port 5005 
> (connection_socket = 3).
> /usr/libexec/linuxcnc/rtapi_msgd: FATAL - will not run as root
> rtapi_msgd startup failed - aborting
> rtapi_app startup failed - aborting
> halcmd: cant connect to rtapi_app: -1 (uri= 
> uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc(): reply timeout
> 
> halcmd: the rtapi:0 RT demon is not running - please investigate 
> /var/log/linuxcnc.log
> halcmd: the msgd:0 logger demon is not running - please investigate 
> /var/log/linuxcnc.log
> io started
> halcmd: cant connect to rtapi_app: -1 (uri= 
> uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc(): reply timeout
> 
> halcmd: the rtapi:0 RT demon is not running - please investigate 
> /var/log/linuxcnc.log
> halcmd: the msgd:0 logger demon is not running - please investigate 
> /var/log/linuxcnc.log
> halcmd loadusr io started
> 
> I have no problem starting machinekit over shortcut on desktop. What I am 
> doing wrong? Printout from linuxcnc.log regarding this issue:
> May 20 13:33:59 beaglebone rtapi:0: rtapi_app:0: ERROR: cannot attach global 
> segment key=0x154711 No such file or directory
> May 20 13:33:59 beaglebone rtapi:0: rtapi:0: FATAL - failed to attach to 
> global segment
> 
> @Klemen
> I have tested this command NO_FORCE_HOMING ... and is working as expected. 
> Thank you very much. Regarding other questions:
> I can not remember exactly what I was doing in the time between 17:39 to 
> 18:13. Probably there was a problem with restating the machinekit after 
> correcting the ini file. Have you seen any suspicious things in printout in 
> this time interval? I am now working with my second BBB board but the problem 
> remains the same. I am executing following g-code:
> 
> (T)
> (DATE=DD-MM-YY - 14-05-17 TIME=HH:MM - 11:06)
> (MCX FILE - T)
> (NC FILE - C:\USERS\EGON1\DESKTOP\T.NC)
> (MATERIAL - ALUMINUM MM - 2024)
> ( T1 |    8. FLAT ENDMILL | H1 )
> N100 G21
> N102 G0 G17 G40 G49 G80 G90
> N104 T1 M6
> N106 G0 G90 G54 X21. Y-21. S12000 M3
> N108 Z10.
> N110 G1 Z-1. F100.
> N112 Y21. F400.
> N114 X-21.
> N116 Y-21.
> N118 X21.
> N120 G0 Z10.
> N122 M5
> N124 G91 G28 Z0.
> N126 G28 X0. Y0.
> N128 M30
> %
> 
> Problem here is that the execution of the g-code stops at point N108. Line 
> N108 is executed and the machine moved to X21, -Y21, Z10. In the line N110 
> z-axis should go to X21, -Y21, Z-1 with speed 100. But this never happened. 
> Execution of g-code simply stops there. Can you test this g-code on your 
> machine if it is performing ok? Printout from linuxcnc.log after activating 
> machinekit loading g-code executing it and turning down machinekit:
> 
> 
> May 20 14:02:50 beaglebone msgd:0: startup pid=1355 flavor=xenomai rtlevel=1 
> usrlevel=1 halsize=524288 shm=Posix cc=gcc 4.9.2  version=unknown
> May 20 14:02:50 beaglebone msgd:0: ØMQ=4.0.5 czmq=2.2.0 protobuf=2.4.1 
> atomics=gcc intrinsics    libwebsockets=<no version symbol>
> May 20 14:02:50 beaglebone msgd:0: configured: sha=32e5e60
> May 20 14:02:50 beaglebone msgd:0: built:      Mar 20 2017 18:27:02 
> sha=32e5e60
> May 20 14:02:53 beaglebone msgd:0: register_stuff: actual hostname as 
> announced by avahi='beaglebone.local'
> May 20 14:02:53 beaglebone msgd:0: zeroconf: registering: 'Log service on 
> beaglebone.local pid 1355'
> May 20 14:02:54 beaglebone msgd:0: zeroconf: registered 'Log service on 
> beaglebone.local pid 1355' _machinekit._tcp 0 TXT 
> "uuid=a42c8c6b-4025-4f83-ba28-dad21114744a" 
> "instance=3f2e0612-3d54-11e7-886c-1cba8ce211c4" "service=log" 
> "dsn=ipc:///tmp/0.log.a42c8c6b-4025-4f83-ba28-dad21114744a"
> May 20 14:06:13 beaglebone rtapi:0: unload: 'trivkins' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'tp' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'threads' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'sim_spindle' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'pwmgen' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'or2' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'near' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'motmod' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'lowpass' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'limit2' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'limit1' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'hypot' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'hal_pru_generic' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'hal_bb_gpio' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'ddt' not loaded
> May 20 14:06:13 beaglebone rtapi:0: unload: 'comp' not loaded
> May 20 14:06:13 beaglebone msgd:0: rtapi_app exit detected - scheduled 
> shutdown
> May 20 14:06:15 beaglebone msgd:0: msgd shutting down
> May 20 14:06:15 beaglebone msgd:0: zeroconf: unregistering 'Log service on 
> beaglebone.local pid 1355'
> May 20 14:06:15 beaglebone msgd:0: log buffer hwm: 0% (0 msgs, 0 bytes out of 
> 524288)
> May 20 14:06:15 beaglebone msgd:0: normal shutdown - global segment detached
> 
> I can not see any inconsistencies.
> 
> 
> -- 
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
> https://github.com/machinekit
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to machinekit+unsubscr...@googlegroups.com.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to