[Xastir] Xastir going down at night

[Eric Christensen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Interestingly enough when I upgraded to version 1.9.1 the problem went
away.  I seem to remember a similar problem when I installed Xastir on
my Windoze box back in November.

Not sure what the differences are between the two versions (except for
1.9.1 is developmental and the other is "stable").

73s,
Eric W4OTN


Gerry Creager wrote:
> cvs update (or is it svn now?) and then a make clean, configure, make,
> make install.  Pretty easy.
> 
> My thought of a memory or controller issue is a device failure.  Like
> Curt, I've seen this happen and the failure modes are more numerous than
> I thought they'd be.
> 
> gerry
> 
> Eric Christensen wrote:
>> I'm not even running the Firenet scripts (if you have them please send
>> them my way).  I've only dipped into swap once and that was for 52kB and
>> that was during a brute force attack on a password.  With Xastir only
>> taking 0.5% of my physical memory (about 20MB of RAM) I can't see it
>> being a memory problem.  It might be a video problem but I can surf over
>> to another workspace and I don't have any problems.  Actually the
>> problem seems to happen when I'm looking at it and when I'm on a
>> different workspace.
>>
>> I just trimmed back to a 14580 port vice 2023 just encase.
>>
>> I just noticed something.  I'm using 1.8.4 when others are using 1.9.1.
>>  I'm forgetting what I need to do to update my install.  Isn't it
>> something easy?
>>
>> Eric
>>
>>
>>
>> Gerry Creager wrote:
>>> Eric,
>>>
>>> If I start dipping into swap I tend to get more RAM.  You're already
>>> well outfitted with 4GB physical memory.  You'd said that you're running
>>> the firenet scripts and Xastir.  That shouldn't be an exhaustive load.
>>> However, if you dip into swap, you're memory-bound, almost certainly.
>>>
>>> I wouldn't discount Curt's suggestion of a hardware (memory or memory
>>> controller) issue.
>>>
>>> gerry
>>>
>>> Eric Christensen wrote:
>>> Hi Chip,
>>>
>>> My setup is as follows:
>>>
>>> Processor: AMD Athlon 64 X2 6000+ Windsor 3.0GHz
>>> HHD: 500GB
>>> RAM: 4GB
>>> Motherboard: ASUS M2N32-SLI
>>>
>>> I'm running Fedora 7 with the 2.6.22.1-27.fc7 kernel.
>>>
>>> I'm currently not connected to a TNC (gotta get a longer serial cable)
>>> so all my data is coming off the IS.
>>>
>>> I'm setup to have 8GB of swap and I've only gotten that far when running
>>> John the Ripper.  Otherwise I've never seen utilization over 2.5GB.  Per
>>> Curt's request I will check for mem spillage as that could be a problem.
>>>
>>> 73s,
>>> Eric W4OTN
>>>
>>>
>>> Chip G. wrote:
>>>>>> Yes. Can you tell us more about your setup? What OS are you using
>>>>>> (and
>>>>>> version)? What version of Xastir are you using? What interfaces do
>>>>>> you
>>>>>> have configured? Are you using a serial (TNC) connection? If so,
>>>>>> how is
>>>>>> the TNC connected to the computer?
>>>>>>
>>>>>> On Jul 25, 2007, at 06:06, Eric Christensen wrote:
>>>>>>
>>>>>>> I've noticed some odd behavior from Xastir over the past couple of
>>>>>>> days. I left it up and running last night and when I went to bed my
>>>>>>> network lights were happily blinking like crazy as I was attached to
>>>>>>> the FireNet IS. When I got up this morning Xastir was sitting there
>>>>>>> with no map and no stations showing on the screen. There was also no
>>>>>>> activity on the network. It just seemed dead. I had to argue a
>>>>>>> little
>>>>>>> with it to make it close down. Has anyone else seen this kind of
>>>>>>> behavior?
>>>>>>>
>>>>>>> 73s,
>>>>>>> Eric W4OTN
>>>>>>
>>>>>> 73,
>>>>>> --de Chip (N1MIE) FN41bn
>> _______________________________________________
>> Xastir mailing list
>> Xastir at xastir.org
>> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
>>
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iQIVAwUBRqwJW1PETzpAxiDcAQJtsA/+LeBYipQmdijggHuccHXd9XQMte3VBC1Z
dTngJpuscFgk0BpdLCb6BAP6/Sx8jeeNEOKpomj+u3glKijR+cfZI0pNVpEFKtKN
EBA74PPUOUxfT8AaygaKcBQMhAlu6Z+AiyXmlLYqjcpOSHnkqy+Ts9DyFxcqsZD9
EIYzwez4z+CWIoh1prG8y7YI+EP8ngkpf8w+7hx+cF3t4kszNfMtnBECD2UEgm4C
2BhaO7lO5pscz58mazQWvjCoJCAh3VFcN6tmJtmUX48Scm0SSbhEk/3uSQLOS1XF
Yd04tBSZ+jtCQ1L0w/6uSulC076CQdrz+TryyEalIIfiyw8fm550HmEhdATK3ZZ8
N3IiBqAQnVuDybCI+CoXx/fFSWYIGxsKkHV+m3KCLKx3pn2epPqT7WwjlRNsrMAg
GG89nM3F0DxWxfy8vzGg0GFIft2YbxkDmORQvkiLaoc7CNWo4GiUlwcum032U9NX
bM4Ppxw/OmNWDRHLC3QwW7ZvS2ofZ/fi/zl+xD2sI9ZaU1U4yYtjChh2yYKBt7LU
0CKDT9l4kMW6gxHH0GCwU04jMQFPuFRrlogNk8WCCzZnq/bSxQlEooIRsC6Y5Ix1
urlWlo3bzRMR2PUVT9uY3B5VT69JBTUwjudIxBxswsOvmBnIw4XuIF2bdI/ocFs8
CyePc86c+7g=
=aZ49
-----END PGP SIGNATURE-----