Thanks for setting it up. You mentioned in yesterday's e-mail that you gave me root access. However, I apparently need a password for that. The app itself only needs read access. It reads data from the SQL database and from other files stored on disk and displays it. The scripts generating the data run independently of the app. They require read and write access to the database and the directories the app uses and are initiated by a scheduling system. Installing and updating the app requires more extensive permissions. I need full access to Docker and ShinyProxy for that. How about two accounts? One handles the app and has minor access rights. And the other generates the data, controls the Docker images and ShinyProxy and has larger access permissions. For security reasons I suggest that these accounts can only access the new CollEc's database within MariaDB. This prevents any repercussions on non-CollEc databases. When setting these permissions we should make sure that "LOAD DATA LOCAL INFILE" or " LOAD DATA INFILE" are still available. Restricted access apparently tends to block these statements which I use to insert large data sets. Feel free to choose any name you like for the account(s) and the database. Christian Düben Research Associate Chair of Macroeconomics Hamburg University Von-Melle-Park 5, Room 3102 20146 Hamburg Germany +49 40 42838 1898 christian.dueben@uni-hamburg.de http://www.christian-dueben.com -----Original Message----- From: Thomas Krichel <krichel@openlib.org> Sent: Donnerstag, 4. Juni 2020 08:32 To: Düben, Christian <Christian.Dueben@uni-hamburg.de> Cc: CollEc Run <collec-run@lists.openlib.org> Subject: Re: [CollEc] RePEc Visual Thomas Krichel writes
root@darni ~ # sudo systemctl restart docker Failed to restart docker.service: Unit docker.service not found.
Well it turns out I had to get docker.io root@darni ~ # apt install docker.io ... root@darni ~ # systemctl start docker Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. root@darni ~ # systemctl status docker.service ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/docker.service.d └─override.conf Active: failed (Result: exit-code) since Thu 2020-06-04 06:17:12 UTC; 57s ago TriggeredBy: ● docker.socket Docs: https://docs.docker.com Process: 3288749 ExecStart=/usr/bin/dockerd -H unix:// -D -H tcp://127.0.0.1:2375 (code=exi> Main PID: 3288749 (code=exited, status=203/EXEC) Jun 04 06:17:12 darni systemd[1]: docker.service: Scheduled restart job, restart counter is at > Jun 04 06:17:12 darni systemd[1]: Stopped Docker Application Container Engine. Jun 04 06:17:12 darni systemd[1]: docker.service: Start request repeated too quickly. Jun 04 06:17:12 darni systemd[1]: docker.service: Failed with result 'exit-code'. Jun 04 06:17:12 darni systemd[1]: Failed to start Docker Application Container Engine. Jun 04 06:18:06 darni systemd[1]: docker.service: Start request repeated too quickly. Jun 04 06:18:06 darni systemd[1]: docker.service: Failed with result 'exit-code'. Jun 04 06:18:06 darni systemd[1]: Failed to start Docker Application Container Engine. overwrite.conf looks for docker in /usr/bin/dockerd, but root@darni ~ # which dockerd /usr/sbin/dockerd says it's in another place. I needed to add the 's' in /etc/systemd/system/docker.service.d/override.conf Then root@darni ~ # systemctl daemon-reload root@darni ~ # systemctl start docker and it's up and running. I suspect the shiny app should be run as an unpriviledged user. Let me know if you want to keep icanis or want a different one. We can then accumulate the sudo instructions for that user It would also be good to have the mysql database with the same name? -- Cheers, Thomas Krichel http://openlib.org/home/krichel skype:thomaskrichel