[Dxspider-support] Daily user disconnections

Michael Carper, Ph.D. mike at wa9pie.net
Wed Nov 2 15:55:14 GMT 2016


Yep... my plan was to try to help them with instructions about SSIDs.
Hadn't thought about locking them out... but that could happen too.  Maybe
I'll say something to that effect in an email.

Heck, I should post something about this as an article on QRZ or eHam
probably... make it generic (not product specific; I'm not trying to sell
HRD here.  I'm trying to help these folks).

Mike, WA9PIE

On Wed, Nov 2, 2016 at 7:59 AM, Mike McCarthy, W1NR <lists at w1nr.net> wrote:

> I see this all the time. An email explaining how to use SSID's usually
> works but for the few that I get no answer from I lock them out.
>
> Mike, W1NR
>
> On 11/02/2016 08:49 AM, Michael Carper, Ph.D. via Dxspider-support wrote:
> > Lee,
> >
> > This thread goes back several months, but I found something that I
> > thought I'd share with you.
> >
> > I was watching the login/logout activity on my cluster.  I reached out
> > to one of the users who I can see that will logout... and immediately
> > login (and there are about 10% of my connected users who do this).  I
> > wanted to find out if it was a software problem with HRD.
> >
> > The user I reviewed was constantly logging out... logging in.
> >
> > Turns out... after investigating... he had HRD installed on two
> > computers (which is fine)... and he was attempting to connect using the
> > same call from both computers to my cluster.  He was using the
> > "Reconnect on disconnect" option on both.
> >
> > So when the second instance of HRD connected... it logged out the
> > previous one... and logged in from the new one... and this process kept
> > repeating itself in an alternating manner indefinitely.
> >
> > My plan is to contact the users on my cluster and provide them a
> > document about using SSIDs and see if that helps the remaining users.
> >
> > Mike, WA9PIE
> >
> > On Sat, Apr 23, 2016 at 9:11 PM, Lee Sawkins <ve7cc at shaw.ca
> > <mailto:ve7cc at shaw.ca>> wrote:
> >
> >     You might not like to hear this, but HRD is the source of my
> >     frequent user disconnects.   My HRD users are coming and going all
> >     the time.  I have complained about this before, but nothing has ever
> >     been done.  It appears if the node does not reply to HRD immediately
> >     the program will disconnect.  ALL other user client programs are
> >     stable and do not do this.
> >
> >     Lee VE7CC
> >
> >     ------------------------------------------------------------
> ------------
> >     *From: *"Michael Carper, Ph.D." <mike at wa9pie.net
> >     <mailto:mike at wa9pie.net>>
> >     *To: *"The DXSpider Support list" <dxspider-support at dxcluster.org
> >     <mailto:dxspider-support at dxcluster.org>>
> >     *Sent: *Saturday, April 23, 2016 11:39:52 PM
> >     *Subject: *Re: [Dxspider-support] Daily user disconnections
> >
> >
> >     I don't have that line in my crontab... but I still have frequent
> >     user disconnections.  I haven't yet figured it out.
> >
> >     Mike, WA9PIE
> >
> >     On Sat, Apr 23, 2016 at 4:47 PM, ei6iz.Brendan Minish
> >     <ei6iz.brendan at gmail.com <mailto:ei6iz.brendan at gmail.com>> wrote:
> >
> >         It's been bugging me for a while that ei7mre seems to kick off
> >         users every day, despite the cluster remaining running
> >         Today I did a bit of digging and this seems to coincide exactly
> >         with the cronjob that  is run by the system  from
> >         cmd/crontab at 3AM
> >         the offending entry appears to be
> >
> >         0 3 * * * Spot::daily()
> >
> >         is this because the job called is taking too long and it's in
> >         the main thread? or do I have a problem elsewhere I should be
> >         investigating?
> >         Do I risk really messing things up if I change the schedule of
> >         this job to run at a time when I might be awake, to allow me to
> >         do a bit more debugging
> >
> >         ei7mre runs on a Centos7 VM with adequate resources (20G of SSD
> >         backed Storage, 1G ram)  and the dxspider process never actually
> >         crashes (up-time is 250 days at present)
> >         ei7mre typically has ~ 140 Users at weekends these days and
> >         never feels in the least bit sluggish, very light CPU load
> >         (0.04) most of the time
> >
> >
> >         --
> >         73
> >         Brendan EI6IZ
> >
> >         _______________________________________________
> >         Dxspider-support mailing list
> >         Dxspider-support at dxcluster.org
> >         <mailto:Dxspider-support at dxcluster.org>
> >         http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
> >         <http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support>
> >
> >
> >
> >     _______________________________________________
> >     Dxspider-support mailing list
> >     Dxspider-support at dxcluster.org <mailto:Dxspider-support@
> dxcluster.org>
> >     http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
> >     <http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support>
> >
> >
> >     _______________________________________________
> >     Dxspider-support mailing list
> >     Dxspider-support at dxcluster.org <mailto:Dxspider-support@
> dxcluster.org>
> >     http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
> >     <http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support>
> >
> >
> >
> >
> > _______________________________________________
> > Dxspider-support mailing list
> > Dxspider-support at dxcluster.org
> > http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20161102/58d33901/attachment.html>


More information about the Dxspider-support mailing list