1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. If you had a PIAF Forum account in the vBulletin days, log in with your old credentials. Otherwise, sign up again and we'll get you back in business as soon as we can.
  3. Guest: We think the problem with locked threads from long message subjects has been resolved. Post a link here if you still see a problem.
Cookies Welcome Back Long Message Subjects SOLVED

Fixed: SSH stops working after update-scripts (VPS)

Discussion in 'Bug Reporting and Fixes' started by Bart, Aug 31, 2008.

  1. Bart Member

    I had a new install done by LYLIX for dedicated VPS - Below is the conversation after SSH failed to start:

    "One of the update- scripts modifies the /dev/null character file. We've corrected the file in the VPS and restarted SSH.

    We've already filed a private report. Whether they act on it or not is out of our hands.

    The specific issue involves 'update-scripts'; if you watch the output closely, you can see a line that reads:

    removed `/dev/null'

    Interestingly, that line is not logged in /var/log/update-scripts.log; upon removal, the file does not exist of course, but some running process automatically re-creates it as a normal file a short while afterwards (most likely attempting to dump garbage output to /dev/null), which is not correct because /dev/null needs to be a character device file with at least global read-write (666) permissions. As-is, sshd will not start/restart if /dev/null is not a proper character device.

    LYLIX Administration"

    Bart

    I see a new update-scripts was released this morning:

    New Update-scripts and Update fixes
    I have released the following:

    Update-scripts #1.2.8 - Fixes errant permission problem

    Update-fixes #1.5.3 - Patch #119 - Fixes some new permission problems.

    Doe this address my specific Bug Report?

    Bart
    Bart, Aug 31, 2008
    #1

  2. darmock PIAF Developer

    already fixed and released


    Tom
    darmock, Aug 31, 2008
    #2

  3. Bart Member

    Was this fixed in the release made TODAY or an EARLIER one?

    I ask because the install and problem was done/found yesterday night

    Bart
    Bart, Aug 31, 2008
    #3

  4. darmock PIAF Developer

    PIAF-PROG-1.4
    update-fixes

    * Date 083108 - TAK
    - Version 1.5.3
    -Patch #119
    - Checks for and fixes any errors in /dev
    ^^^^^^^^^^^^^^^^

    You can always look thru the latest changelogs at

    http://www.piafdevcorp.com/changelogweb/changelog.html

    Generally this is updated as needed.

    Thus it was fixed today as per my announcement this morning.

    Hope that helps

    Tom
    darmock, Aug 31, 2008
    #4

  5. Bart Member

    Still Broken

    OK, I ran update-scripts and update-fixes just now - Now asterisk does not start on it's own either with amportal start/restart or with reboot.

    error: Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)

    The only way to start is using asterisk -vvvvc at command line

    Ran the scripts again - same problem

    Bart
    Bart, Aug 31, 2008
    #5

  6. Bart Member

    After several reboots and amportal restarts, it finally started working - me was scared for a while. However, there some kind of issue with update-scripts that effects up restarting asterisk and access of FreePBX web pages <= restarting Apache seemed to solve this and disabling Fail2Ban for a while was the only things I did, if that helps

    Bart
    Bart, Aug 31, 2008
    #6

  7. darmock PIAF Developer

    Hmm what version are you running? Post the complete output of status please.

    Generally systems from lylix work quite well.

    Unfortunately I cannot duplicate this problem on real machines or virtual running under vmware. While developing the patch for this problem I install on various hardware and vmware platforms to test the patches prior to release. So far none of them exhibit the behavior you are observing with your virtual system.

    I do not have access to a virtual machine from lylix so I have no further suggestions. Soon as the Lylix guys sent me email I located the problem and patched it. Then I implemented a routine in update-fixes that checks for the errors everytime it is run and corrects it if it exists. I know there are a few hoops to go thru to make PIAF run in certain virtual environments and Lylix has been at the forefront of cooperation with us.

    regards

    Tom
    darmock, Aug 31, 2008
    #7

Share This Page