I am currently using 2.3 TB to store data.Īny assistance or guidance (aside from "don't mess with /etc") would be greatly appreciated. ![]() Click Done (for DSM 7.0 and above) or OK (for DSM 6.2 and earlier). In the Permission Editor window, modify the settings to manage ACL permissions for the file or folder. Unless you are attempying to access from the server itself, you should not be able to access port 9475. I have 2x 4 TB HDDs, configured in RAID 1. On the Permissions tab, select the Custom checkbox for the user whose permissions you wish to customize. From the internet it should be The internal port of 9475 is where the reverse proxy sends the incoming connection. I did some reading into this, and it seems like I am out of luck - that I need to reimage completely because so many underlying processes rely on the successful execution of "su" and "sudo." Apparently, over time the operating system will degrade so much due to this that it will become unusable.Īny suggestions as to what I can do to fix this or mitigate data loss? For reference, I have already reached out to Synology requesting assistance. Now, when I try to sudo anything, I get the 3 error messages: "sudo: /etc/sudoers is world writable" "sudo: no valid sudoers sources found, quitting" "sudo: unable to initialize policy plugin" and the command fails. More advanced Linux users know that this is where my mistake was galvanized. Then I ran "exit" to end my "su -i" session. So I input "sudo -i" (as recommended by Synology here: 's%20password%3A,logged%20in%20with%20root%20permission.) ) and input "chmod 777 /etc/sudoers" then "vi /etc/sudoers" to add my user account to the list of authorized users. But in order to change /etc/sudoers, I needed to make it editable. ![]() I know that /etc/sudoers can be edited to allow other users to sudo. I grew frustrated that I could not "su -" or "sudo xxx" on a product that I own. I recently enabled SSH on my Synology DS716+II and was playing around. The command (… new-plugin) still freezes after the first question.As the ominous title implies, I may have messed up big-time. ![]() I have tried running the command with sudo, and I have changed the user:group to my name (under Synology, all users have the group ‘users’). However,įreezes after the first question (the name of the plugin) is answered. For instance: docker:x:2200:admin Stop and re-start docker package. After running the script, I can run bin/gpm list and get the correct output. Add a group docker in /etc/group - see group (5). But what is my problem Im trying to install " docker" on my Syno. I have a bash script (based on the script in the GRAV documentation) that sets all files and directories to have group ‘http’ (the Synology Group for apache) and the permissions as per Grav. Im really at the beginning of diving into Linux world and its CLI, so I apologize for my lack of knowledge in this matter. If I connect to the Synology machine using ssh in order to use the command line, I cannot always get bin/gpm to work, especially after some operations with the admin plugin. However, I can use (see below) bin/gpm install plugin. The error on the admin page after clicking on Add is connection to GPM cannot be established. For security reasons, I would like to only allow connection through ssh with user account (john) and then do sudo root/admin if required. ![]() However, the admin plugin cannot add a new plugin. There is something I do not understand : I can ssh via an admin account, root account (yes, I shouldn't be according to docs) and my user account (john) which is in administrators group. I have a Grav site working and I have the admin plugin working. There are some problems as Synology is also running nginx and then passing control to apache My cronjob that calls Python3 keeps saying /bin/sh: python3: command not found but /bin/sh exists and I am able to call Python3 from. Synology allows for both php 5.6 and php 7. My Synology NAS just upgraded and a lot of things have broken. Synology uses mustache files to generate the nginx config files, and I don’t want to break anything. NOTE: This may not work with all Zigbee controllers, but has been tested with the CC2531. To access the superuser, run the command sudo su. The Synology SSH root password will be the password to the account you’re currently connected with. I have been unable to find a configuration to run Grav directly under nginx. The sudo -i command below will allow you to access the root user. I have set it up to run apache 2.4 as the backend for the web, which is the only way I have managed to find to get Grav to work. The operating system is a variety of Linux.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |