Menu

LCM worked yesterday, but doesn't today

Help
2006-03-07
2013-04-08
  • Anthony_C_C

    Anthony_C_C - 2006-03-07

    Hello,

    LCM was working great yesterday. However, when I ran /usr/local/lcm/lcm today, the gui started up and died instantly. I was able to see that it had retained the nodes I had entered in in yesterday.

    Here is the ouput to the terminal when it dies:

    couldn't open socket: host is unreachable
        while executing
    "# Compiled -- no source code available
    error "called a copy of a compiled script""
        (procedure "get_status" line 1)
        invoked from within
    "# Compiled -- no source code available
    error "called a copy of a compiled script""
        (procedure "main_window" line 1)
        invoked from within
    "# Compiled -- no source code available
    error "called a copy of a compiled script""
        (procedure "initial_connect" line 1)
        invoked from within
    "# Compiled -- no source code available
    error "called a copy of a compiled script""
        invoked from within
    "tbcload::bceval {
    TclPro ByteCode 2 0 1.4 8.4
    135 0 1610 288 0 0 1220 0 4 135 135 -1 -1
    1610
    w0E<!-fSs!)?W<!<uW<!@Iy*'-W&=!@uW<!Ha++'1oJ=!DuW<!PwP+'52..."
        (file "/usr/local/lcm/lcm/lib/application/lcm.tcl line 4)
        invoked from within
    "source      $startup"
        (file "/usr/local/lcm/lcm/main.tcl" line 18)

    I checked the /etc/lcm.log file, but there was nothing supicious in it. I tried changing the mac address in lcm.conf from ifcfg-eth* to specify the complete address, but it didn't help. I rebooted the machine, didn't help either.

    Here is the system I am running it on:

    Linux sysimg 2.6.5-7.97-smp #1 SMP Fri Jul 2 14:21:59 UTC 2004 x86_64 x86_64 x86_64 GNU/Linux

    Please help!
    Thanks,
    --Anthony

     
    • Michael England

      Michael England - 2006-03-08

      The lcm.conf is for imaging defaults so doesn't impact the initial socket connections.  The cluster information is kept in /etc/cluster.conf.  An easy check to see if there are errors in this file is to temporarily move it to another name.  LCM should start with a blank screen.

      Another place to check is /var/log/lcm.log for each of the nodes.  It is possible one of them has a problem (a bug) that needs to be addressed.

       

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.