[pskmail] Re: fldigi lockups?
- From: Remi Chateauneu <remi.chateauneu@xxxxxxxxx>
- To: pskmail@xxxxxxxxxxxxx
- Date: Thu, 16 Feb 2012 12:34:13 +0000
There might be a simple reason, because although dome problems
happened to me under special circumstances (Heavy debug-related IOs,
Restarting a new fldigi session when the previous one is not
completely halted.), the rest of the time, it's very stable, even when
running the same process for days! And really, I cannot see why it
should be necessary to reinstall Linux !!
Could a Linux user please generate a core dump when fldigi is stuck ?
Please follow these instructions:
( http://stackoverflow.com/questions/680627/creating-core-dumps-on-linux ):
* Ensure that the content of /proc/sys/kernel/core_pattern is chmod ugo+rwx
* kill -ABRT 'fldigi process'
* Then please make available the core file and your fldigi prog.
Thanks in advance.
R
On Thu, Feb 16, 2012 at 10:56 AM, DAVID GRAY <kf4wbs@xxxxxxxxxxx> wrote:
> Well I have an thought about that too
> I see something similar between the jpskmail client 2.0X and the 1.5x
> when I upgraded to version 2.0x after a 1.5x install there is a config file
> that gets over written
> I found that when I go that route and try to let it overwrite the file the
> 2.0x is not very sable at all however if I remove the config file
> prior to the installation it seems to work much better however if I try to
> go back to the1.5x version
> it wont run at all so I remove the config file and then reinstall then
> it runs as before this is using windows I didnt try it in Linux
> so I don't know why it wont over write correctly but it doesn't
> I see more issues with linux`s permissions then with windows so I would
> think I might be worth a look see
> In my case it is easier to reinstall linux when I see problems like this
> than to find out if that is what the problem is because if
> they are compiled files I cant see what is going on there anyway
> In the case of FLDIGI I don't know where to start looking In the case of
> jpskmail I just got lucky because while I don't mind reinstalling
> Linux I really don't like to reinstall windows the key code is a
> nightmare and if you do that several times you have to call someplace
> and verify your keycode and stuff
>
>
>
> anyway there is a least 33 cents instead of my two cents worth about it
>
>
>
>
>
> --------------------------------------------------
> From: "Pär Crusefalk" <per@xxxxxxxxxxxx>
> Sent: Thursday, February 16, 2012 05:08
>
> To: <pskmail@xxxxxxxxxxxxx>
> Subject: [pskmail] Re: fldigi lockups?
>
>> Hi David,
>>
>> That was the kind of data I was looking for but unfortunately the
>> problem is there regardless of operating system. Also, I have upgraded
>> my server several times and it's been really stable for quite a while
>> now. I would think there is either a thread deadlock or an unhandled
>> exception of some kind in fldigi that gets triggered by something
>> related to PTT handling.
>>
>> 73 de Per
>>
>>
>>
>> DAVID GRAY skrev 2012-02-16 10:57:
>>>
>>> Are all three of you using FLDIGI in linux or windows ?
>>> I have had this happen a long time ago
>>> I have gotten rid of the problem before but you wont like the solution
>>>
>>> A few of you really wont like it ha ha
>>> but if I dban the hard drive and reinstall linux the problem goes away
>>> go figure I don't know for sure but when there are upgrades
>>> maybe there are subfiles that arent needed any more but are still
>>> there and wernt properly written out of the program ????
>>> or maybe they cant be over written for some reason because of the
>>> permissions
>>> I don't know but everything seems to run better on a fresh
>>> install and the problem goes away
>>>
>>> KF4WBS
>>>
>>>
>>>
>>>
>>> --------------------------------------------------
>>> From: "Pär Crusefalk" <per@xxxxxxxxxxxx>
>>> Sent: Thursday, February 16, 2012 04:14
>>> To: <pskmail@xxxxxxxxxxxxx>
>>> Subject: [pskmail] Re: fldigi lockups?
>>>
>>>> Hi all,
>>>>
>>>> Thanks to those that have added rows to the spreadsheet!
>>>> At the moment I can't see any significant fact that could help locate
>>>> these issues. Perhaps if we add more stations to the spreadsheet?
>>>> It is here btw: http://bit.ly/AeKwmx
>>>>
>>>> Larrys suggestion here is something I have done in the past so is worth
>>>> testing. At the moment my server is between crashes so I am waiting for
>>>> the next and will try that again. I have done that in the past so I'm
>>>> afraid it will not fix the situation.
>>>>
>>>> It's very unfortunate that fldigi is so unstable, perhaps we need to
>>>> consider our options here (skype conference?).
>>>> One thing I have done is to prepare a script that kills fldigi and the
>>>> server and then relaunches it. If I can check if fldigi has crashed then
>>>> I can have cron launch that script periodically. It's not a fix for
>>>> fldigi, it's more of an ugly band aid...
>>>>
>>>> 73 de Per, sm0rwo
>>>>
>>>>
>>>> Larry Levesque skrev 2012-02-14 19:57:
>>>>>
>>>>> This is always my first suggestion:
>>>>>
>>>>> Backup and then delete your fldigi configuration directory.
>>>>>
>>>>> Now try running fldigi again. Let us know how it works.
>>>>>
>>>>>
>>>>> On Tue, Feb 14, 2012 at 07:13:39AM -0600, Bernard Dekok wrote:
>>>>>>
>>>>>> I get the flDigi lockup on my little Acer Netbook client all the time
>>>>>> recently. (Not previously.)
>>>>>> Could be memory related, but I doubt it.
>>>>>> Could be RF in the system, maybe..., but testing with low power into a
>>>>>> dummy load, so doubt that too.
>>>>>>
>>>>>> flDigi on my server has been running fine from the gitgo.
>>>>>>
>>>>>> Will investigate the setup differences between the two flDigis and
>>>>>> report
>>>>>> on your spreadsheet.
>>>>>>
>>>>>> KC9SGV
>>>>>>
>>>>>>
>>>>>> On Tue, Feb 14, 2012 at 3:35 AM, Rein Couperus <rein@xxxxxxxxxxxx>
>>>>>> wrote:
>>>>>>
>>>>>>> Very nice initiative, this is my main pain in the butt....
>>>>>>> Have to restart PI4TUE 2x a day...
>>>>>>>
>>>>>>> Rein EA/PA0R/M
>>>>>>>
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> This is an old subject but it seems some are still experiencing
>>>>>>>> lockups.
>>>>>>>> I tried to find the cause earlier and got as far as pointing the
>>>>>>>> finger
>>>>>>>> at rigcat (that part handles ptt and is used even if not selected).
>>>>>>>> I
>>>>>>>> then had a patch on fldigi to try to log more during the next
>>>>>>>> crash but
>>>>>>>> it never came.. What I did find earlier was that it happened
>>>>>>>> during ptt
>>>>>>>> on/off and could be related to frequency change during those
>>>>>>>> events. As
>>>>>>>> some still have to restart fldigi now and then I figured we could
>>>>>>>> perhaps find something in common if we gather some more data about
>>>>>>>> the
>>>>>>>> servers with issues. Its a longshot but could be interesting
>>>>>>>> anyway. I
>>>>>>>> put a simple spreadsheet here:
>>>>>>>> http://bit.ly/AeKwmx
>>>>>>>>
>>>>>>>> You are all welcome to add details to that spreadsheet if you wish,
>>>>>>>> perhaps we can see something that helps thack this issue?
>>>>>>>>
>>>>>>>> 73 de Per, sm0rwo
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Mobile: +46703784299
>>>>
>>>>
>>>
>>
>>
>> --
>> Mobile: +46703784299
>>
>>
>
Other related posts:
