2021 Jul 23, 02:32 PM
(2021 Jul 23, 02:06 PM)dan Wrote: Paul,
Sorry, I should have included "sudo" in the instructions I provided. It is a Linux security feature.
I usually log into my development Pi as root which allows me to save files and do other actions without using sudo and I sometimes forget to include it in instructions. If you don't use sudo you will often not be able to install software or run programs but will get a "permission denied" error message.
I'm glad to hear that your slave setup is working.
Dan
Dan,
That makes sense then.
By the way, I came across this thread when trying to fix the OSError above about socket creation permission.
https://nosack.com/sipforum/showthread.p...be+created
Would sudo-install be a better a solution than changing the port ("htp": 80,) in SIP/data/sd.json?
I did change the port and the permission error went away, but it created another problem when I press the "clear log" button under the Log menu:
It didn't clear the log and I have to press the back button to get back the SIP screen.
And because I was running "python sip.py" manually in the background I saw this error message, a permission error accessing log.json :
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 14.0px Menlo; color: #000000} span.s1 {font-variant-ligatures: no-common-ligatures}
PermissionError: [Errno 13] Permission denied: './data/log.json'
I saw similar types of permission error when I used other the web UI functions but I can't remember which ones now.
So maybe the best practice overall is to ssh as root user into the pi.
Paul