Help save net neutrality! Learn more.
Close

#49047 Shell services issue

closed
5
2003-09-06
2003-08-25
No

Unable to login to shell.

$ ssh -l zed shell.sf.net
zed@shell.sf.net's password:
Connection to shell.sf.net closed by remote host.
Connection to shell.sf.net closed.

Password is correct, as entering a wrong one gives a
different error. CVS access still works, however.

Discussion

  • David Burley

    David Burley - 2003-08-25
    • summary: shell login not working --> Shell services issue
    • assigned_to: nobody --> burley
    • milestone: --> Second Level Support
     
  • David Burley

    David Burley - 2003-08-25

    Logged In: YES
    user_id=597273

    Greetings,

    This canned response is used by the SourceForge.net team to
    convey information about how this Support Request will be
    handled. Please read the entirety of this comment before taking
    any further action; information enclosed in this comment will
    help you to ensure that you have an excellent support experience.

    The SourceForge.net team takes all reported issues seriously; we
    will work to provide you a complete, accurate, and timely
    response to your inquiry. Information about our support policies
    and procedures may be found at:
    https://sourceforge.net/docman/display_doc.php?docid=11230&group_id=1

    ABOUT THIS ISSUE: Based on the initial review of this request, we
    have determined that this issue will be considered to have
    Moderate Priority (this is signified by the summary line we use
    on this request, not by the Priority setting on this request).
    Issues within this category typically include service questions,
    usage problems, and specialized requests (such as those requiring
    significant administrative overview, or which require the
    development of a custom solution). A description of this class
    of issues may be found at:
    https://sourceforge.net/docman/display_doc.php?docid=11230&group_id=1#issueclass_moderate

    TRIAGE PROCESS: The initial review of this issue has resulted in
    a member of the SourceForge.net staff determining who should
    process this issue, and a change in the Priority, Summary,
    Assignee, Group and Category settings for this request. We use
    these settings solely for grouping purposes; as the submitter,
    you SHOULD NOT change any of these settings. Since we use all of
    these settings to group issues for faster response, you should
    understand that changing any of these settings (particularly the
    listed Priority setting) will result in significant delays in the
    processing of your request.

    WHAT TO EXPECT: Issues of this nature will typically be reviewed
    again by the assigned member of the SourceForge.net team within 5
    business days (the SourceForge.net team works at least Monday
    through Friday, 9am to 5pm Pacific, excepting holidays). Within
    our next response, we will typically request additional
    information about the problem you have reported, or provide you
    specific troubleshooting instructions. Please wait patiently for
    our next review of, and response to, this request.

    INQUIRING ABOUT THE STATUS OF THIS ISSUE: Should you have
    questions or concerns regarding the status of this issue, simply
    add a comment to this support request. All comments you post to
    this support request will be received by the SourceForge.net team
    member who has been assigned this issue. Please do not submit a
    second support request about this issue (add a comment to this
    request instead), and do not attempt to contact the assignee of
    this request via email; all additional information or comments
    about this request should be posted as a comment to this request.

    Thank you,

    SourceForge.net support

     
  • Jacob Moorman

    Jacob Moorman - 2003-08-26

    Logged In: YES
    user_id=152443

    Greetings,

    The issue you reported is covered by the SourceForge.net
    Site Status page (accessible using the "Site Status" link in
    the left navbar of the SourceForge.net site).

    On 2003-08-23, one project file server (of seven) sufferred
    a multi-disk failure; data from this file server has been
    restored from tape. The failed server previously served
    data for projects starting with the letters j, q, s and y;
    and for users starting with the letters c, i, r and z.

    The data from this fileserver has been restored from tape to
    an alternate machine. The project web servers have mounted
    the group filesystem for these projects read-only, to ensure
    project web sites will continue to function (more or less)
    in the interim (this was done late Saturday/early Sunday, to
    help minimize impact to projects). Users whose home
    directories are served from the impacted fileserver will be
    unable to login to the project shell server until this
    matter is fully resolved (see below).

    At this time, we are waiting for the completion of a fsck on
    the old fileserver. Pending completion of this fsck
    (morning of 2003-08-26, Pacific):

    - The restored group data (derived from our 2003-08-19
    backup, since the fileserver failed in the middle of our
    next backup) will be mounted on the project shell server.

    - The project web servers will mount the restored data
    read-write at that time.

    - The old fileserver will be mounted on the shell server (at
    a mount point to be named later), to permit users to try to
    salvage data generated since the backup we used for data
    restoration.

    - User home directories will be brought back online at that
    time.

    This work is expected to be completed during the business
    hours on 2003-08-26.

    Additional information will be posted to the Site Status
    page and the Message of the Day (motd) on the project shell
    server when this work is completed. This request will be
    left open in the mean time. Should you have further
    questions or concerns which are not answered by this
    response, please feel free to add a comment to this Support
    Request (provided you are the original submitted of this
    request; if not, please submit your own Support Request on
    the subject).

    Your patience is appreciated.

    Jacob Moorman
    Quality of Service Manager, SourceForge.net

     
  • Jacob Moorman

    Jacob Moorman - 2003-08-26
    • summary: Shell services issue --> Shell services issue (PENDING RES/26)
     
  • Jacob Moorman

    Jacob Moorman - 2003-08-26
    • priority: 5 --> 1
     
  • Jacob Moorman

    Jacob Moorman - 2003-09-06
    • assigned_to: burley --> moorman
     
  • Jacob Moorman

    Jacob Moorman - 2003-09-06
    • summary: Shell services issue (PENDING RES/26) --> Shell services issue
     
  • Jacob Moorman

    Jacob Moorman - 2003-09-06
    • priority: 1 --> 5
    • status: open --> closed
     
  • Jacob Moorman

    Jacob Moorman - 2003-09-06

    Logged In: YES
    user_id=152443

    Greetings,

    This message provides a complete status update regarding the
    multi-disk project file server failure that occurred last month.
    Not all of the issues covered in this message will necessarily
    apply to your project. If you believe any of the covered issues
    is still present for your project, follow the instructions at the
    bottom of this message.

    Projects impacted by this outage start with the following
    letters: j, q, s, and y

    In recovering from the multi-disk crash in one project file
    server, user and group ownership on some files within the project
    web space for impacted projects was mangled. Ownership and
    permissions on all restored data have now been corrected as to
    permit management of that data by project teams.

    Project group directories for projects approved between the time
    of the backup (which was used to restore project data) and the
    time of the disk crash have been created, permitting new projects
    to proceed with posting their content.

    All project web spaces and user home directory spaces are online
    at this time and read-write. As a member of a project, you
    should be able to manage the web content within the group
    directory space for your project (unless another member of your
    team has changed these permissions).

    All restored data is from the 19 August, 2003 backup.

    The data recovered from the failed project file server, which may
    be newer than the data restored from backup, is available for
    perusal in the /var/local directory structure on the project
    shell servers. You are welcome to retrieve data from the
    recovered copy of your project web space as you desire, but you
    should be careful to validate its integrity (this data may be
    corrupt) before overwriting the restored copy of this data. This
    data will be available until 2003-09-20.

    As always, projects should make sure they have established a
    suitable backup and recovery plan, as described at:
    https://sourceforge.net/docman/display_doc.php?docid=6840&group_id=1
    As documented, we provide data restoration only in the case of
    catastrophic system failure (such as this case, where drives
    failed in the file server). AGAIN: Please ensure your project
    has established a suitable backup plan which generates offsite
    backups of your project data.

    We regret any inconvenience this outage may have caused you or
    your project. We have been working steadily behind-the-scenes to
    assess the impact of this outage and to provide timely, complete
    resolution to all known issues, minimizing project impact and the
    potential for data loss. Your patience has been appreciated.

    At this time, no known issues remain (related to this outage).
    If you believe your user account or project has a remaining
    issue, please submit a NEW support request at this time (do not
    add a comment to this Support Request). Any reported issues will
    be treated on a case-by-case basis (do not tack your issue on to
    any existing request) and will be processed with high priority.
    That said, we are not aware of any outstanding issues at this time.

    Thank you,

    Jacob Moorman
    Quality of Service Manager, SourceForge.net