Hello Bas,
what I noticed when I looked in /var/log/linuxcnc.log is the following

May 24 09:19:22 beaglebone msgd:0: startup pid=2533 flavor=xenomai 
rtlevel=1 usrlevel=1 halsize=524288 shm=Posix cc=gcc 4.9.2  version=unknown
May 24 09:19:22 beaglebone msgd:0: ØMQ=4.0.5 czmq=3.0.2 protobuf=3.2.0 
atomics=gcc intrinsics    libwebsockets=<no version symbol>
May 24 09:19:22 beaglebone msgd:0: configured: sha=466cbe1
May 24 09:19:22 beaglebone msgd:0: built:      May 23 2017 10:36:45 
sha=466cbe1
May 24 09:19:23 beaglebone msgd:0: register_stuff: actual hostname as 
announced by avahi='beaglebone.local'
May 24 09:19:23 beaglebone msgd:0: zeroconf: registering: 'Log service on 
beaglebone.local pid 2533'
May 24 09:19:23 beaglebone msgd:0: rtapi_app exit detected - scheduled 
shutdown
May 24 09:19:23 beaglebone msgd:0: zeroconf: registered 'Log service on 
beaglebone.local pid 2533' _machinekit._tcp 0 TXT 
"uuid=a42c8c6b-4025-4f83-ba28-dad21114744a" 
"instance=1316fd0c-4062-11e7-af1b-04a316b5de53" "service=log" 
"dsn=ipc:///tmp/0.log.a42c8c6b-4025-4f83-ba28-dad21114744a"
May 24 09:19:25 beaglebone msgd:0: msgd shutting down

As you can see version is mentioned as unknown. All other points are the 
same, up until *rtapi_app exit detected*.

When I start the precompiled version of machinekit on the same image, it 
starts as expected, so it works, but just not with my compiled version.
Does anybody know which version of protobuf is needed?? because i read that 
this can cause problems ( although i don't know it halcmd connects to the 
rtapi_app using protobuf )



Op woensdag 24 mei 2017 11:45:07 UTC+2 schreef Bas de Bruijn:
>
> If you search this string on the google group a few similar threads show 
> up.
>
> If you’re not running as root, then perhaps this link may help.
>
> https://groups.google.com/forum/#!searchin/machinekit/ERROR$3A$20cannot$20attach$20global$20segment$20key$3D0x154711$20No$20such$20file$20or$20directory%7Csort:relevance/machinekit/jNhr3x9rmcU/6FLoXUlMIwAJ
>
> If you “export DEBUG=5” before running machinekit you can get some more 
> (and hopefully better) debug messages in /var/log/linuxcnc.log
>
> On 24 May 2017, at 11:32, michelvand...@gmail.com <javascript:> wrote:
>
> I also found the following information in the print and debug files
>
> *machinekit@beaglebone:~$ cat /tmp/linuxcnc.debug*
> Can not find -sec DISPLAY -var INTRO_GRAPHIC -num 1 
> 2511
>   PID TTY      STAT   TIME COMMAND
> Stopping realtime threads
> Unloading hal components
>
> *machinekit@beaglebone:~$ cat /tmp/linuxcnc.print*
> RUN_IN_PLACE=yes
> LINUXCNC_DIR=
> LINUXCNC_BIN_DIR=/media/machinekit/rootfs/home/debian/machinekit/bin
> LINUXCNC_TCL_DIR=/media/machinekit/rootfs/home/debian/machinekit/tcl
> LINUXCNC_SCRIPT_DIR=
> LINUXCNC_RTLIB_DIR=/media/machinekit/rootfs/home/debian/machinekit/rtlib
> LINUXCNC_CONFIG_DIR=
>
> LINUXCNC_LANG_DIR=/media/machinekit/rootfs/home/debian/machinekit/src/objects
> INIVAR=/media/machinekit/rootfs/home/debian/machinekit/libexec/inivar
> HALCMD=halcmd
> LINUXCNC_EMCSH=/usr/bin/wish8.6
> INIFILE=/opt/nectar-apps/machinekit-config/nectar-dd-02.ini
> PARAMETER_FILE=./pru-stepper.var
> TASK=milltask
> HALUI=
> DISPLAY=tkemc
> Starting Machinekit server program: linuxcncsvr
> Loading Real Time OS, RTAPI, and HAL_LIB modules
> Starting Machinekit IO program: io
> Killing task linuxcncsvr, PID=2511
>
> Op woensdag 24 mei 2017 09:48:15 UTC+2 schreef michelvand...@gmail.com:
>>
>> Hello All,
>> I compiled a vanilla machinekit from git using the steps outlined in : 
>> http://www.machinekit.io/docs/developing/machinekit-developing/
>>
>> It had a problem with protobuf not understanding "syntax" in 
>> lib/python/machinetalk/protobuf/nanopb_pb2.py, which I read is related to 
>> which version protobuf is being used. I have protobuf 3.3.0 on the image i 
>> downloaded.
>> I commented these two syntax lines out, because it automaticly chooses 
>> version2 the lines said.
>>
>> Compilation went without any problem afterwards.
>>
>> I did the "sudo make setuid"
>>
>> when I go to the scripts folder I run ". ./rip-environment", that goes ok.
>>
>> But when I try to start machinekit with ./machinekit my.ini it dies with 
>> the following messages :
>>
>> May 24 06:45:50 beaglebone rtapi:0: rtapi_app:0: ERROR: cannot attach 
>> global segment key=0x154711 No such file or directory
>> May 24 06:45:50 beaglebone rtapi:0: rtapi:0: FATAL - failed to attach to 
>> global segment
>> May 24 06:47:10 beaglebone msgd:0: startup pid=2421 flavor=xenomai 
>> rtlevel=1 usrlevel=1 halsize=524288 shm=Posix cc=gcc 4.9.2 
>>  version=v0.1~-detached~b1ad179
>> May 24 06:47:10 beaglebone msgd:0: ØMQ=4.0.5 czmq=2.2.0 protobuf=2.6.1 
>> atomics=gcc intrinsics    libwebsockets=<no version symbol>
>> May 24 06:47:10 beaglebone msgd:0: configured: sha=b1ad179
>> May 24 06:47:10 beaglebone msgd:0: built:      May 18 2017 17:11:51 
>> sha=b1ad179
>> May 24 06:47:10 beaglebone msgd:0: register_stuff: actual hostname as 
>> announced by avahi='beaglebone.local'
>> May 24 06:47:10 beaglebone msgd:0: zeroconf: registering: 'Log service on 
>> beaglebone.local pid 2421'
>> May 24 06:47:11 beaglebone msgd:0: zeroconf: registered 'Log service on 
>> beaglebone.local pid 2421' _machinekit._tcp 0 TXT 
>> "uuid=a42c8c6b-4025-4f83-ba28-dad21114744a" 
>> "instance=cf9f6c86-404c-11e7-a09a-04a316b5de53" "service=log" "dsn=
>> ipc:///tmp/0.log.a42c8c6b-4025-4f83-ba28-dad21114744a"
>> May 24 06:47:13 beaglebone msgd:0: rtapi_app exit detected - scheduled 
>> shutdown
>> May 24 06:47:15 beaglebone msgd:0: msgd shutting down
>>
>>
>> Anybody an idea why this happens?
>>
>> With regards,
>> Michel
>>
>
> -- 
> 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+...@googlegroups.com <javascript:>.
> 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