Purchase Linux CDs / DVDs / Flash Drives at OSDisc.com

Welcome to Our Community

While Linux.org has been around for a while, we recently changed management and had to purge most of the content (including users). If you signed up before April 23rd please sign up again. Thanks!

  1. Get $5 off your first Lyft ride while helping us pay for hosting Linux.org! --> $5 Lyft
    Dismiss Notice

Command Going Wrong

Discussion in 'Command Line' started by Amirvbase, Nov 6, 2017.

  1. Amirvbase

    Amirvbase New Member

    Joined:
    Nov 6, 2017
    Messages:
    1
    Likes Received:
    0
    I Run command on my Godaddy Server via SSh
    sudo chown -R Amirvbase /
    after that they hiding all detail from my access and unable to connect via putty
    how I handle to return back to my previous work?


     
  2. JasKinasis

    JasKinasis Active Member

    Joined:
    Apr 25, 2017
    Messages:
    96
    Likes Received:
    144
    This is a classic case of PICNIC (Problem In Chair, Not In Computer).
    "They" aren't hiding anything from you. By recursively changing the permissions/ownership for everything on the root of the file-system, YOU have probably borked your server.

    Why did you run chown recursively on the root of the servers file-system anyway? Was it an accidental typo? or was it deliberate? :/

    Many system components of the Linux OS use (and rely on) POSIX standard permissions/ownership. There are a lot of places in the system where the wrong permissions/ownership will completely break the OS and/or completely expose the computer, breaking security.

    Manual recovery from this would be almost impossible because you'd have to carefully (and manually) restore the correct permissions/ownership for every single system file and folder. If you miss just one of the critical ones - then the system will not work, or will be completely insecure/exposed.

    Because of your recursive chown, I'd guess that the servers OS has probably already crashed. And because the server is remote, I'd guess that there is nothing further that you can do yourself to fix this.

    Your best bet would be to contact Godaddy's customer service, or technical support. Tell them what you did and ask them for assistance. They might have a recent backup/snapshot of your server which they could restore. Otherwise they will have to perform a complete re-install of the OS.

    We all learn by making mistakes. I just hope this isn't a particularly expensive lesson! :S

    Good luck! ;)
     

Share This Page