Bug 114551 - Remote connection - Max open sessions reached (NOT per host)
Summary: Remote connection - Max open sessions reached (NOT per host)
Keywords:
Status: CLOSED DUPLICATE of bug 113154
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 1
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-01-29 15:00 UTC by Need Real Name
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:00:59 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Need Real Name 2004-01-29 15:00:18 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6)
Gecko/20040113

Description of problem:
Gnome
GDM
Using X terminals to connect

After approx 10 days of use no client is able to connect to the server.

Fatal server error:

XDMCP fatal error: Session declined Maximum number of open sessions
reached

Even when there are no current connections.



Version-Release number of selected component (if applicable):
GDM Gnome

How reproducible:
Sometimes

Steps to Reproduce:
1.try to connecto to X on the server
2.Connection refused
3.
    

Actual Results:  Session declined

Expected Results:  Connection established

Additional info:

It would seem sessions are closing off correctly.
Comment 1 Mike A. Harris 2004-01-29 22:00:25 UTC 
This is not an XFree86 bug/problem, it is a bug in gdm, which is
known, and already reported in bugzilla.  I don't have the
bug ID handy, so I'm reassigning it to gdm, for the package owner
to triage.
Comment 2 Need Real Name 2004-01-30 09:56:24 UTC 
Thanks

Any pointers as to what I should look out for or log?
Comment 3 Bart Martens 2004-02-02 23:16:45 UTC 
Probably duplicate of bug 113154. Right?
Comment 4 Jef Spaleta 2004-02-03 00:45:59 UTC 

*** This bug has been marked as a duplicate of 113154 ***
Comment 5 Red Hat Bugzilla 2006-02-21 19:00:59 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.