scofra

Hi alf7, You might try chmod 600 That worked for me when I ran into the Unprotected Private Key problem. I'm using command line SFTP and OpenSSH. I found this AWS link helpful: https://docs.aws.amazon.com/transfer/latest/userguide/getting-started-use-the-service.html Good luck!

Hi Bart, Thanks again! I saw the --norecord option in your example unit and found it on the cmd-line options page. Makes sense; and the signals that toggle recording on/off work perfectly, as per the docs. I really appreciate all the info! Best, Scott

Issue resolved! @Bart, thanks for the updated unit. I modified it slightly, adding logging and my personalized welcome message. Seems setting "ProtectHome=False" did the trick. @Vincenzo, I tried running the exec string as a simple command and yes, it seems like it would work. Shell output claims "Recording state enabled." Ultimately I'm using the service unit approach and toggling recording on/off with propagated signals, as per the docs. Thanks for the suggestions! Scott

Hi Vicenzo, Great suggestion! I tried your chmod cmd, but the problem persists. Taking a closer look at permissions, I note that my home/ and ubuntu/ directories have the same permissions as var/ -- and jamulus is happily writing its logfiles. I've set my recordings/ permissions even more open. drwxr-xr-x 13 root root 4096 Jul 16 10:14 var/ drwxr-xr-x 3 root root 4096 Nov 9 13:48 home/ drwxr-xr-x 5 ubuntu ubuntu 4096 Dec 3 14:02 ubuntu/ drwxrwxrwx 2 ubuntu ubuntu 4096 Dec 1 13:33 recordings/ Service...

Hi Vicenzo, Great suggestion! I tried your chmod cmd, but the problem persists. Taking a closer look at permissions, I note that my home/ and /ubuntu/ directories have the same permissions as var/ -- and jamulus is happily writing its logfiles. I've set my recordings/ permissions even more open. drwxr-xr-x 13 root root 4096 Jul 16 10:14 var/ drwxr-xr-x 3 root root 4096 Nov 9 13:48 home/ drwxr-xr-x 5 ubuntu ubuntu 4096 Dec 3 14:02 ubuntu/ drwxrwxrwx 2 ubuntu ubuntu 4096 Dec 1 13:33 recordings/ Service...

Hello, What's the best way to configure recording on a headless private Linux server running in the cloud? I followed the instructions (https://jamulus.io/wiki/Server-Linux), but recording isn't working. (Everything else appears to work very well!) My jamulus service exec string sets the -R flag and passes a directory for new recordings: ExecStart=/usr/local/bin/llcon-jamulus/Jamulus --server --nogui \ --log /var/log/jamulus/jamulus.log \ --serverinfo "<my_server_name>;<my_city>;<my_code>" \ --welcomemessage...

I see you're passing the absolute path as an argument to the -w flag. Assuming you've run an ls -l to ensure the file exists and has data in it, I wonder if a symlink would work: pointing from wherever you want your welcome text file to live, back to the Jamulus executable directory.

Weird that link didn't work; but glad you got to the right page! Feel free to reach out with any questions. Best, Scott