Loading ...
Sorry, an error occurred while loading the content.

Re: [LinuxRMS] RMS not usable (crashing?)

Expand Messages
  • Jim Kusznir
    Yep, just the 2m link is left. The 2m link is not connected directly to my rms-running system at all...Its through a node link only. --Jim
    Message 1 of 21 , Aug 7, 2013
    • 0 Attachment
      Yep, just the 2m link is left.

      The 2m link is not connected directly to my rms-running system at all...Its through a node link only.

      --Jim


      On Mon, Jul 29, 2013 at 2:55 PM, Brian R. Eckert - W3SG <eckertb@...> wrote:
       

      Superb!

      Now it's just the 2m link that we need to figure out for reporting, correct?




      On 07/28/2013 09:14 PM, Jim Kusznir wrote:
       
      Thanks, that works.  I'm now reporting.

      Thanks for all your help!

      --Jim


      On Sat, Jul 27, 2013 at 8:42 PM, Brian R. Eckert - W3SG <eckertb@...> wrote:
       

      Looking back to your netstat output:


      --------------
      4) dream:/etc/ax25# netstat --protocol=ax25 -l 
      Active AX.25 sockets
      Dest       Source     Device  State        Vr/Vs    Send-Q  Recv-Q
      *          WINLNK-0   ???     LISTENING    000/000  0       0     
      *          K7LL-10    ???     LISTENING    000/000  0       0     
      *          K7LL-0     ax0     LISTENING    000/000  0       0     
      --------------

      K7LL-10 has no device showing. There are quite a few things going on, and in particular, there is an attempt to match up an ax25 interface with the ip address associated the the kissattach. They aren't matching up as they need to for this script to work :-( .

      For giggles, I'm going t suggest you try Dan's script. From wherever you have the source, try running
      contrib/ifstatus ax25 uhf

      and see what we get.

      If that works, you can copy it to /usr/local/bin, then change your status checker to channels.xml to read like:
      /usr/local/bin/ifstatus $type $name

      If that works, I would say to stay with that for now unless we see different problems.

      73
      -brian W3SG


      On 07/27/2013 11:11 PM, Jim Kusznir wrote:
       
      Jul 27 20:08:31 dream rmsgw_aci[11091]: K7LL-10 - Linux RMS Gateway ACI 2.3.0 Jul 26 2013 (DN16jr)
      Jul 27 20:08:31 dream rmsgw_aci[11091]: Channel: K7LL-10 on uhf (440975000 Hz, mode 3)
      Jul 27 20:08:31 dream rmsgw_aci[11091]: /usr/local/bin/rmschanstat ax25 uhf K7LL-10 reports unavailable
      Jul 27 20:08:31 dream rmsgw_aci[11091]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
      Jul 27 20:08:31 dream rmsgw_aci[11091]: INFO: sendVersion(): assuming destination 'winlink.org'
      Jul 27 20:08:31 dream rmsgw_aci[11091]: INFO: sendVersion(): assuming port/service '8778'


      It appears that its an SSID thing; its looking specifically for K7LL-10, but works with K7LL for some reason...

      kusznir@dream:~$ /usr/local/bin/rmschanstat ax25 uhf K7LL
      channel uhf with callsign K7LL on interface ax0 up
      kusznir@dream:~$ /usr/local/bin/rmschanstat ax25 uhf K7LL-10
      status for interface ax0 unavailable

      My RMS is up and uses K7LL-10, although as its linux, the actual ax0 uses a different SSID (K7LL-1, actually, with netrom being K7LL-6):
      kusznir@dream:~$ /sbin/ifconfig ax0
      ax0       Link encap:AMPR AX.25  HWaddr K7LL-1  
                inet addr:44.12.0.66  Bcast:44.255.255.255  Mask:255.0.0.0
                UP BROADCAST RUNNING  MTU:230  Metric:1
                RX packets:36656 errors:0 dropped:0 overruns:0 frame:0
                TX packets:5405 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:10 
                RX bytes:6427335 (6.1 MiB)  TX bytes:342175 (334.1 KiB)



      On Sat, Jul 27, 2013 at 7:14 PM, Brian R. Eckert - W3SG <eckertb@...> wrote:
       

      Very peculiar...

      What is in syslog for your rmsgw_aci runs?

      As an example, here is the logging for the most recent run:
      Jul 27 21:36:01 legolas rmsgw_aci[25569]: W3SG-10 - Linux RMS Gateway ACI 2.3.0 Jul  4 2013 (FN20dt)
      Jul 27 21:36:01 legolas rmsgw_aci[25569]: shm_init(): shmkey = 330280 (0x50a28)
      Jul 27 21:36:01 legolas rmsgw_aci[25569]: shm_init(): shmid = 1048582 (0x100006)
      Jul 27 21:36:01 legolas rmsgw_aci[25569]: Channel: W3SG-10 on radio (145550000 Hz, mode 1)
      Jul 27 21:36:01 legolas rmsgw_aci[25569]: /usr/local/bin/rmschanstat ax25 radio W3SG-10 reports available

      The line above shows what was executed for the status check, so I'm wondering what your system shows there.

      Also, I have made the code change you suggested on command line argument values getting logged. It will be in the next release (no specific plans for that yet).

      73
      -brian W3SG


      On 07/27/2013 09:27 PM, Jim Kusznir wrote:
       
      Thanks for the reply!

      Interestingly enough, if I run rmschanstat as suggested above, it works (although I've changed channels.xml name to uhf, to match what's in axports and such):

      /usr/local/bin/rmschanstat ax25 uhf K7LL
      channel uhf with callsign K7LL on interface ax0 up
      However as the same user, rmsgw_aci fails:
      $ rmsgw_aci
      status for interface ax0 unavailable

      [...]






    • k4gbb
      Jim, We have a 2 meter port that links a FPAC node via a 440 MHz port to another FPAC node which has the RMS Gate connection. Our problem was how to get the
      Message 2 of 21 , Aug 7, 2013
      • 0 Attachment
        Jim,
          We have a 2 meter port that links a FPAC node via a 440 MHz  port to another FPAC node which has the
        RMS Gate connection. Our problem was how to get the get the 2 meter port reported and displayed on the
        WL2K position map.

        <<Charley>>

        On 08/07/2013 12:32 PM, Jim Kusznir wrote:
        Yep, just the 2m link is left.

        The 2m link is not connected directly to my rms-running system at all...Its through a node link only.

        --Jim


        On Mon, Jul 29, 2013 at 2:55 PM, Brian R. Eckert - W3SG <eckertb@...> wrote:
         

        Superb!

        Now it's just the 2m link that we need to figure out for reporting, correct?




        On 07/28/2013 09:14 PM, Jim Kusznir wrote:
         
        Thanks, that works.  I'm now reporting.

        Thanks for all your help!

        --Jim


        On Sat, Jul 27, 2013 at 8:42 PM, Brian R. Eckert - W3SG <eckertb@...> wrote:
         

        Looking back to your netstat output:


        --------------
        4) dream:/etc/ax25# netstat --protocol=ax25 -l 
        Active AX.25 sockets
        Dest       Source     Device  State        Vr/Vs    Send-Q  Recv-Q
        *          WINLNK-0   ???     LISTENING    000/000  0       0     
        *          K7LL-10    ???     LISTENING    000/000  0       0     
        *          K7LL-0     ax0     LISTENING    000/000  0       0     
        --------------

        K7LL-10 has no device showing. There are quite a few things going on, and in particular, there is an attempt to match up an ax25 interface with the ip address associated the the kissattach. They aren't matching up as they need to for this script to work :-( .

        For giggles, I'm going t suggest you try Dan's script. From wherever you have the source, try running
        contrib/ifstatus ax25 uhf

        and see what we get.

        If that works, you can copy it to /usr/local/bin, then change your status checker to channels.xml to read like:
        /usr/local/bin/ifstatus $type $name

        If that works, I would say to stay with that for now unless we see different problems.

        73
        -brian W3SG


        On 07/27/2013 11:11 PM, Jim Kusznir wrote:
         
        Jul 27 20:08:31 dream rmsgw_aci[11091]: K7LL-10 - Linux RMS Gateway ACI 2.3.0 Jul 26 2013 (DN16jr)
        Jul 27 20:08:31 dream rmsgw_aci[11091]: Channel: K7LL-10 on uhf (440975000 Hz, mode 3)
        Jul 27 20:08:31 dream rmsgw_aci[11091]: /usr/local/bin/rmschanstat ax25 uhf K7LL-10 reports unavailable
        Jul 27 20:08:31 dream rmsgw_aci[11091]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
        Jul 27 20:08:31 dream rmsgw_aci[11091]: INFO: sendVersion(): assuming destination 'winlink.org'
        Jul 27 20:08:31 dream rmsgw_aci[11091]: INFO: sendVersion(): assuming port/service '8778'


        It appears that its an SSID thing; its looking specifically for K7LL-10, but works with K7LL for some reason...

        kusznir@dream:~$/usr/local/bin/rmschanstat ax25 uhf K7LL
        channel uhf with callsign K7LL on interface ax0 up
        kusznir@dream:~$/usr/local/bin/rmschanstat ax25 uhf K7LL-10
        status for interface ax0 unavailable

        My RMS is up and uses K7LL-10, although as its linux, the actual ax0 uses a different SSID (K7LL-1, actually, with netrom being K7LL-6):
        kusznir@dream:~$/sbin/ifconfig ax0
        ax0       Link encap:AMPR AX.25  HWaddr K7LL-1  
                  inet addr:44.12.0.66  Bcast:44.255.255.255 Mask:255.0.0.0
                  UP BROADCAST RUNNING  MTU:230  Metric:1
                  RX packets:36656 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:5405 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:10 
                  RX bytes:6427335 (6.1 MiB)  TX bytes:342175 (334.1 KiB)



        On Sat, Jul 27, 2013 at 7:14 PM, Brian R. Eckert - W3SG <eckertb@...> wrote:
         

        Very peculiar...

        What is in syslog for your rmsgw_aci runs?

        As an example, here is the logging for the most recent run:
        Jul 27 21:36:01 legolas rmsgw_aci[25569]: W3SG-10 - Linux RMS Gateway ACI 2.3.0 Jul  4 2013 (FN20dt)
        Jul 27 21:36:01 legolas rmsgw_aci[25569]: shm_init(): shmkey = 330280 (0x50a28)
        Jul 27 21:36:01 legolas rmsgw_aci[25569]: shm_init(): shmid = 1048582 (0x100006)
        Jul 27 21:36:01 legolas rmsgw_aci[25569]: Channel: W3SG-10 on radio (145550000 Hz, mode 1)
        Jul 27 21:36:01 legolas rmsgw_aci[25569]: /usr/local/bin/rmschanstatax25 radio W3SG-10 reports available

        The line above shows what was executed for the status check, so I'm wondering what your system shows there.

        Also, I have made the code change you suggested on command line argument values getting logged. It will be in the next release (no specific plans for that yet).

        73
        -brian W3SG


        On 07/27/2013 09:27 PM, Jim Kusznir wrote:
         
        Thanks for the reply!

        Interestinglyenough, if I run rmschanstat as suggested above, it works (although I've changed channels.xml name to uhf, to match what's in axports and such):

        /usr/local/bin/rmschanstatax25 uhf K7LL
        channel uhf with callsign K7LL on interface ax0 up
        However as the same user, rmsgw_aci fails:
        $ rmsgw_aci
        status for interface ax0 unavailable

        [...]







      Your message has been successfully submitted and would be delivered to recipients shortly.