On Friday 08 May 2015 05:19:49 Mark Wendt wrote:
> On Thu, May 7, 2015 at 8:08 PM, Gene Heskett <ghesk...@wdtv.com> wrote:
> > > On your first xauth on coyote, it looks like an IPv6 magic cookie.
> > > Do you have IPv6 enabled? This here:
> > > [fe80::21f:c6ff:fe62:fcbb]:0 looks suspiciously like some kind of
> > > local IPv6 address. Try disabling IPv6 on coyote. Ssh will
> > > automagically try to make it's connection on IPv6 and if it's not
> > > available, can either sit there till it times out, or cause other
> > > problems.
> >
> > Where would I tell it to skip the IPV6 stuffs? AFAIK, there are no
> > ipv6 things enabled, and my little 8 port switch does not to my
> > knowledge even know what ipv6 is. And ALL paths go thru that
> > switch.
> >
> > > You might try connecting with this string: #ssh -4 -Y <machine?
> > > -vvv
> > >
> > > the -4 tells ssh to skip the IPv6 attempt and go right to an IPv4
> > > connection.
> > >
> > > Mark
> >
> > I just moved my known_hosts to known_hosts.old, then reaccepted the
> > keys from both machines. Still no luck.
> >
> > Logging into lathe and running linuxcnc returns:
> >
> > gene@coyote:~$ ssh -4 -Y lathe
> > The authenticity of host 'lathe (192.168.71.5)' can't be
> > established. RSA key fingerprint is
> > 1a:75:8f:b3:aa:d7:83:bd:7a:5e:d3:dc:82:76:9c:4f. Are you sure you
> > want to continue connecting (yes/no)? yes
> > Warning: Permanently added 'lathe,192.168.71.5' (RSA) to the list of
> > known hosts.
> > gene@lathe's password:
> > Linux lathe 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian
> > 3.4.55-4linuxcnc i686
> >
> > The programs included with the Debian GNU/Linux system are free
> > software; the exact distribution terms for each program are
> > described in the individual files in /usr/share/doc/*/copyright.
> >
> > Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
> > permitted by applicable law.
> > Last login: Thu May 7 19:49:19 2015 from coyote.coyote.den
>
> Okay, so far, so good.
>
> > gene@lathe:~$ linuxcnc
> > LINUXCNC - 2.8.0-pre1-602-gfa8867a
> > Application initialization failed: unknown color name "BACKGROUND"
> > Error in startup script: can't invoke "image" command: application
> > has been destroyed
> > while executing
> > "image create photo -file $f/$i.gif"
> > invoked from within
> > "if [file exists $f/$i.gif] {
> > return [image create photo -file $f/$i.gif]
> > }"
> > (procedure "linuxcnc::image_search" line 7)
> > invoked from within
> > "linuxcnc::image_search linuxcnc-wizard"
> > invoked from within
> > "set logo [linuxcnc::image_search linuxcnc-wizard]"
> > (file "/usr/lib/tcltk/linuxcnc/bin/pickconfig.tcl" line 31)
> > Application initialization failed: unknown color name "BACKGROUND"
>
> 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.
> > Into shop, I get this:
> > gene@coyote:~$ ssh -4 -Y shop
> > The authenticity of host 'shop (192.168.71.4)' can't be established.
> > RSA key fingerprint is
> > 7a:b4:de:b0:7f:fa:73:24:83:7f:9f:cd:19:56:65:8a. Are you sure you
> > want to continue connecting (yes/no)? yes
> > Warning: Permanently added 'shop,192.168.71.4' (RSA) to the list of
> > known hosts.
> > gene@shop's password:
> > Linux shop 2.6.32-122-rtai #rtai SMP Tue Jul 27 12:44:07 CDT 2010
> > i686 GNU/Linux
> > Ubuntu 10.04.4 LTS
> >
> > Welcome to Ubuntu!
> > * Documentation: https://help.ubuntu.com/
> >
> > New release 'precise' available.
> > Run 'do-release-upgrade' to upgrade to it.
> >
> > Last login: Mon May 4 10:44:12 2015 from coyote.coyote.den
> >
> > gene@shop:~$ linuxcnc -l
> > LINUXCNC - 2.6.7
> > Machine configuration directory
> > is '/home/gene/linuxcnc/configs/my-mill-atom-3'
> > Machine configuration file is 'my-mill-atom-3.ini'
> > Starting LinuxCNC...
> > Traceback (most recent call last):
> > File "/usr/bin/hal_manualtoolchange", line 62, in <module>
> > app = Tkinter.Tk(className="AxisToolChanger")
> > File "/usr/lib/python2.6/lib-tk/Tkinter.py", line 1646, in
> > __init__ self.tk = _tkinter.create(screenName, baseName, className,
> > interactive, wantobjects, useTk, sync, use)
> > _tkinter.TclError: unknown color name "BACKGROUND"
> > Traceback (most recent call last):
> > File "/usr/bin/axis", line 121, in <module>
> > root_window = Tkinter.Tk(className="Axis")
> > File "/usr/bin/axis", line 44, in __init__
> > OldTk.__init__(self, *args, **kw)
> > File "/usr/lib/python2.6/lib-tk/Tkinter.py", line 1646, in
> > __init__ self.tk = _tkinter.create(screenName, baseName, className,
> > interactive, wantobjects, useTk, sync, use)
> > _tkinter.TclError: unknown color name "BACKGROUND"
> > Shutting down and cleaning up LinuxCNC...
> > Traceback (most recent call last):
> > File "/usr/bin/axis-remote", line 78, in <module>
> > t = Tkinter.Tk(); t.wm_withdraw()
> > File "/usr/lib/python2.6/lib-tk/Tkinter.py", line 1646, in
> > __init__ self.tk = _tkinter.create(screenName, baseName, className,
> > interactive, wantobjects, useTk, sync, use)
> > _tkinter.TclError: unknown color name "BACKGROUND"
> > Application initialization failed: unknown color name "BACKGROUND"
> > 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
>
> 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.
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)
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.
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 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...
Thanks Mark.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
------------------------------------------------------------------------------
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
