Ticket #603 (closed defect: fixed)

Opened 11 years ago

Last modified 9 years ago

edsc should deal with unexpected discuss errors

Reported by: kchen Owned by:
Priority: low Milestone: The Distant Future
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description

My .meetings file contains entries including:

1:0:313:spatula-city.MIT.EDU:/var/spool/discuss/dates:dates,dates:
1:0:0:dragons-lair.MIT.EDU:/var/spool/discuss/generic:Generic,generic:

When I run command-line discuss, I get:
discuss: RPC server too old while authenticating to discuss server

for these meetings. diswww.mit.edu doesn't have any problem with generic, but reports "Connection reset by peer (104)" for dates. (I have no idea what dates is anyway.)

In any case, this seems to cause problems for edsc. When I start up emacs and run M-x discuss, I get:

error in process filter: End of file during parsing

and I am unable to use discuss in emacs. If I remove these two meetings from my .meetings file, I am able to successfully use discuss in emacs.

Change History

comment:1 Changed 11 years ago by kchen

Evan writes (in response to my debathena@… mail):

Sounds like there are a couple of bugs at play here

discuss: RPC server too old while authenticating to discuss server

That sounds to me like the server in question only supports krb4
authentication, and not krb5. As part of our preparation for
Karmic/Lucid/Squeeze? (which have krb5 >=1.7), we stopped building many
of our packages with krb4 support, including discuss.

If you can get the owners of those machines to upgrade the discussd, I
suspect it would fix that error

error in process filter: End of file during parsing

That sounds like something worth opening a Trac ticket about, although
I suspect it'll be ultra-low priority for us to fix.

comment:2 Changed 11 years ago by jweiss

I'm fairly certain that dragons-lair is running an old krb4 only discussd. I think spatula-city's discussd may be "more broken than that" since I can't seem to connect to it from a krb4 enabled client.

comment:3 Changed 10 years ago by mitchb

As a poor substitute for fixing the problem, I'll answer the implied question. dates was the archive of LIST:dates, which received mail something like a few days before and on the day of every holiday. The list moved to be hosted by a ktools.org mailman list, but it looks like that's AWOL as well.
Note that dragons-lair was upgraded, so at this point I suspect spatula-city is the only thing out there still causing problems, and I'd happily provide a working discussd for it if given the opportunity.

comment:4 Changed 10 years ago by jdreed

Can we close this? It sounds like this ticket has devolved into "spatula-city has bitrotted" which is totally not our problem.

comment:5 Changed 10 years ago by jdreed

  • Status changed from new to closed
  • Resolution set to invalid

comment:6 Changed 10 years ago by kchen

Ideally, edsc should be able to handle unexpected discuss output, so I'd consider this an edsc problem, not a spatula-city problem (although much of the discussion has been about spatula-city specifically).

comment:7 Changed 10 years ago by jdreed

  • Status changed from closed to reopened
  • Resolution invalid deleted
  • Summary changed from edsc and "RPC server too old while authenticating to discuss server" to edsc should deal with unexpected discuss errors

comment:8 Changed 10 years ago by jdreed

  • Status changed from reopened to committed

r25411

Someone who speaks C should sanity-check my commit, but it sounds like this is precisely what set_com_err_hook is for.

comment:9 Changed 10 years ago by jdreed

This at least works, as I get:

 Flags   Meeting name
 -----   ------------
 c       Athena Release Announcements, release-announce
 c       sipb@mit.edu archive, sipb@mit.edu
 c       Consulting_FYI, cfyi
 c       New_Meetings, new_meetings
 c       The Cryptographic File System users list, cfs
 c       SIPB-EC, sipb-ec
   X     dates (Connection reset by peer: spatula-city.MIT.EDU)

comment:10 Changed 9 years ago by jdreed

  • Status changed from committed to proposed

This got built in the Precise build. 10.0.15 is in proposed for not-precise, and in production for precise.

comment:11 Changed 9 years ago by jdreed

  • Status changed from proposed to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.