[Xastir] Xastir shutting down prematurely

[John Wilson]

Well, that didn't take long. Crashed two minutes after starting. The log
file was blank though.

John


On Fri, Mar 22, 2013 at 6:21 AM, John Wilson <kc4lzn at gmail.com> wrote:

> Well, after running now for three days, it did crash again...xastir that
> is. I'm not sure on the computer memory being the culprit because the
> computer itself is still running. No other faults have been recorded with
> nothing other than Xastir.
>
> I am going to start Xastir with the log file mentioned previously and see
> what I get.
>
> John
>
>
> On Tue, Mar 19, 2013 at 7:43 AM, John Wilson <kc4lzn at gmail.com> wrote:
>
>> Prior to running memory checks, I looked at the Interface Control device
>> (KISS TNC) and noted that I had not turned on the igate function. It had
>> been done under File, Configure, Defaults but not for the device itself. It
>> is now turned on and I will see if it crashes again. Igate logging is on
>> and terminal open so I can see what is recorded.
>>
>> John
>>
>>
>>
>> On Tue, Mar 19, 2013 at 5:26 AM, John Wilson <kc4lzn at gmail.com> wrote:
>>
>>> As of this writing, it has been running for about 12 hours with no
>>> failures. Gremlins must be running a muck.
>>>
>>> Running the memory test was next on the list. I plan on running that
>>> several times to check for any inconstancies in the outcome.
>>>
>>> John
>>> On Mar 18, 2013 4:31 PM, "Curt, WE7U" <curt.we7u at gmail.com> wrote:
>>>
>>>> On Mon, 18 Mar 2013, John Wilson wrote:
>>>>
>>>>  Not that I haven't seen it before but being this was a newly built
>>>>> computer, I really didn't want to accept that I had acquired failed
>>>>> parts
>>>>> in this brand new machine.
>>>>>
>>>>> I stopped the last thing I initiated in Xastir.
>>>>>
>>>>> Igate interface.
>>>>>
>>>>> It has been 18 hours since I stopped it and it has not shut down. Is
>>>>> there
>>>>> a buffer setting for Igate traffic in Xastir?
>>>>>
>>>>
>>>> Nope.  It just uses the last-heard-on-rf times for any particular
>>>> station to decide whether to gate the traffic to RF.
>>>>
>>>> More than likely Xastir's memory image is growing over time just 'cuz
>>>> of the station list and the associated data for each station.  Once it
>>>> grows enough you might be heading over to another bit of memory that has
>>>> issues.  You can minimize that by running filters on your INET connections
>>>> to limit the number of stations you're receiving.
>>>>
>>>> You might run a memtest for a while to see if it's truly a memory
>>>> problem.  That's the quickest way to figure it out.  If it's not in your
>>>> boot menu, many of the install DVD's have it.
>>>>
>>>> --
>>>> Curt, WE7U.        http://wetnet.net/~we7u
>>>> APRS Client Capabilities:  http://wetnet.net/~we7u/aprs_**
>>>> capabilities.html <http://wetnet.net/~we7u/aprs_capabilities.html>
>>>> ______________________________**_________________
>>>> Xastir mailing list
>>>> Xastir at lists.xastir.org
>>>> http://lists.xastir.org/cgi-**bin/mailman/listinfo/xastir<http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir>
>>>>
>>>
>>
>