On Fri, May 8, 2015 at 7:49 AM, Gene Heskett <ghesk...@wdtv.com> wrote:

>
> >
> > Okay, the ssh logins are working correctly.  Now we have a Linuxcnc
> > problem.  Just to verify the ssh logins are working correctly, can you
> > bring up any other X applications, like gears, or the eyes?
>
> xeyes and glxgears both work, albeit gears is a bit slow, 21 fps.
>

Good.  That may be network related, but with X, who knows?  May even be a
framebuffer issue.


>
>
>
> >
> > Okay, this kinda goes back to the same error as above - the
> > "BACKGROUND ." It keeps trying to invoke the 'image" command on
> > something which doesn't exist.  Here's one workaround I found:
> >
> > "Workaround:
> >
> > Create ~/.Xresources plain text file with content:
> >
> > *.background: gray75
> >
> > then
> > $xrdb -load ~/.Xresources"
> >
> >
> > This may not set up the right color for the "BACKGROUND", but try it
> > to see if the errors go away.
> >
> You da man. But I think I just found an error, a file that has not been
> included in my backups, bad dog, no biscuit.
> The startup gui to select the machine config now shows up, but then it
> dies.  Trace:
> Found file:./my_LinuxCNC_machine2.hal
> ./my_LinuxCNC_machine2.hal:12: Can't find module 'boot'
> in /usr/realtime-3.4-9-rtai-686-pae/modules/linuxcnc
> Shutting down and cleaning up LinuxCNC...
> Running HAL shutdown script
> LinuxCNC terminated with an error.  You can find more information in the
> log:
>     /home/gene/linuxcnc_debug.txt
> and
>     /home/gene/linuxcnc_print.txt
> as well as in the output of the shell command 'dmesg' and in the terminal
>
> So it appears I will have to reinvent that module as I had used something
> Jon suggested, with the pulses lengthened and a 2 or 3 repeat loop
> added, its the powerup enable for his pwm driven servo amplifier, which
> I am using to drive the lathes spindle motor.
>
> I may have a copy of it on this machine, if I'd recognize it when I saw
> it.
>

Normally that file is a user created file, however, some programs may
create that automagically in your home directory.  Not sure if the install
of Linuxcnc does that or not.  I'll have to check that on my machine at
home.


> Humm, tried to run a sim/axis/lathe, it asked me to allow a copy to be
> made on my configs dir, I click yes, and the startup script baled out:
>
> gene@lathe:~$ linuxcnc
> LINUXCNC - 2.8.0-pre1-602-gfa8867a
> Error in startup script: error
> deleting "/home/gene/linuxcnc/nc_files/ngcgui_lib": directory not empty
>     while executing
> "file delete $linkname"
>     (procedure "prompt_copy" line 69)
>     invoked from within
> "prompt_copy $::inifile"
>     invoked from within
> "if [ok_to_copy_config $::inifile] {
>             set copied_inifile [prompt_copy $::inifile]
>             if {$copied_inifile == ""} {
>                 c..."
>     ("while" body line 6)
>     invoked from within
> "while {1} {
>     focus $::tree
>     vwait ::choice
>
>     if { $::choice == "OK" } {
>         if [ok_to_copy_config $::inifile] {
>             set copied_in..."
>     (file "/usr/lib/tcltk/linuxcnc/bin/pickconfig.tcl" line 806)
>

Wonder why it's trying to delete an existing directory, with files in it?
Since that's the case, rename the ncgui_lib directory to some other name
and see if it will run.


>
> So I'll go see if I can find a local copy of that missing boot module.  I
> also need to move a copy of 5i25.zip to there but until I can make the
> nfs share mountpoint directory on this machine, thats not going to work.
> sftp to the rescue for that.
>
> My nfs shares are all mounted at /net/machinename, but for some reason I,
> nor sudo, cannot mkdir lathe, no permission.  For all I know it could be
> this funkity drive.
>

Nope, /net directories are controlled, I believe by autofs, and only autofs
can make or destroy directories there.


>
> example trace:
> WTF?  Now the directory already exists, and the mount is working.
>
> gene@coyote:/etc/apt$ cd /net
> gene@coyote:/net$ sudo mkdir lathe
> mkdir: cannot create directory `lathe': File exists
> gene@coyote:/net$ ls
> lappy  lathe  shop
> gene@coyote:/net$
> gene@coyote:/net$ ls -l /lathe
> ls: cannot access /lathe: No such file or directory
> gene@coyote:/net$ ls -l lathe
> total 108
> drwxr-xr-x   2 root   root  4096 May  6 13:18 bin
> drwxr-xr-x   2 root   root  4096 May  6 12:56 boot
> drwxr-xr-x   4 root   root  4096 May  6 12:56 dev
> drwxr-xr-x 130 root   root 12288 May  8 00:54 etc
> drwxr-xr-x   2 backup disk  4096 May  6 17:35 GenesAmandaHelper-0.61
> drwxr-xr-x   4 root   root  4096 May  6 21:40 home
> lrwxrwxrwx   1 root   root    35 May  6 12:56
> initrd.img -> /boot/initrd.img-3.4-9-rtai-686-pae
> drwxr-xr-x  15 root   root  4096 May  6 13:15 lib
> drwx------   2 root   root 16384 May  6 12:05 lost+found
> drwxr-xr-x   3 root   root  4096 Jul  3  2014 media
> drwxr-xr-x   2 root   root  4096 Apr 19  2014 mnt
> drwxr-xr-x   2 root   root  4096 May  8 07:28 net
> drwxr-xr-x   2 root   root  4096 Jul  3  2014 opt
> drwxr-xr-x   2 root   root  4096 Apr 19  2014 proc
> drwx------   8 root   root  4096 May  7 02:29 root
> drwxr-xr-x   2 root   root  4096 May  6 13:08 run
> drwxr-xr-x   2 root   root  4096 May  6 13:19 sbin
> drwxr-xr-x   2 root   root  4096 Jun 10  2012 selinux
> drwxr-xr-x   2 root   root  4096 Jul  3  2014 srv
> drwxr-xr-x   2 root   root  4096 Jul 17  2013 sys
> drwxrwxrwt   9 root   root  4096 May  8 07:35 tmp
> drwxr-xr-x  12 root   root  4096 May  6 14:18 usr
> drwxr-xr-x  12 root   root  4096 May  6 14:18 var
> lrwxrwxrwx   1 root   root    31 May  6 13:03 vmlinuz ->
> boot/vmlinuz-3.4-9-rtai-686-pae
>
> Exactly what I expected.  That will greatly facilitate making it all fly
> again.  Now I better go & make us some starter fluid, aka coffee.  Come
> to think of it, I had apt-get install the nfs-kernel-server about an
> hour ago, on that machine because I noticed it was missing from
> the /etc/init.d directory.  Duh.  Thats what I get for doing all this
> without any morning caffeine.  The damned dots don't connect. :(
>

I can empathize.  I'm worthless till I hook up the caffeine IV.  ;-)


>
> I found an ~/.xsession-errors file on this machine, and it just logged
> this:
>
> 07:27:27 libtorsocks(14607): connect: Connection is to a local address
> (192.168.71.1), may be a TCP DNS request to a local DNS server so have
> to reject to be safe. Please report a bug to
> http://code.google.com/p/torsocks/issues/entry if this is preventing a
> program from working properly with torsocks.
> ?: keys.gnupg.net: Host not found
> gpgkeys: HTTP fetch error 7: couldn't connect: Connection refused
> gpg: requesting key BBB51E42 from hkp server keys.gnupg.net
> gpg: no valid OpenPGP data found.
> gpg: Total number processed: 0
>  at /usr/share/perl5/App/Parcimonie/Daemon.pm line 247
>
> I don't even know if Parcimonie is a required service.  WTH?  Just nuked
> it.  I thought maybe it would help kmail by autofetching keys.  But
> torsocks?  I am not that paranoid.
>
> And that session of synaptic just caused x to log:
> X Error: BadWindow (invalid Window parameter) 3
>   Major opcode:  19
>   Minor opcode:  0
>   Resource id:  0x440004d
>
> But the wondow looked normal.  Sigh...
>

I think that has something to do with a bad exit code from KDE/Gnome etc.
I've seen that message before.  It's no big deal.  Some places have said
that if you use shutdown from a terminal rather than either an init 6 or
init 0, or the shutdown menu item you may see that.  You can ignore that.

Another place to look when troubleshooting X, is /var/log/Xorg.0.log.  That
gets updated and rotated at the beginning of every X session.


> Thanks Mark.
>
> Cheers, Gene Heskett
>

Cheers,
Mark
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to