Hello, I am trying to install PeerTube in my Server which contains one SSD for the OS and software and one HDD for data. PeerTube is installed in the SSD and data will be stored in the HDD but in the first start of the instance, PeerTube can not start because it does not have the permission to write in the data folder.
There is the portion of the edited configuration:
tmp: ‹ /home/peertube/storage/tmp/ ›
avatars: ‹ /home/peertube/storage/avatars/ ›
videos: ‹ /home/peertube/storage/videos/ ›
streaming_playlists: ‹ /home/peertube/storage/streaming-playlists/ ›
redundancy: ‹ /home/peertube/storage/redundancy/ ›
logs: ‹ /home/peertube/storage/logs/ ›
previews: ‹ /home/peertube/storage/previews/ ›
thumbnails: ‹ /home/peertube/storage/thumbnails/ ›
torrents: ‹ /home/peertube/storage/torrents/ ›
captions: ‹ /home/peertube/storage/captions/ ›
cache: ‹ /home/peertube/storage/cache/ ›
plugins: ‹ /home/peertube/storage/plugins/ ›
There is the error displayed by the Journal
:/var/www/peertube/versions/peertube-v2.1.1/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:45
: throw err0
: ^
: Error: EACCES: permission denied, mkdir ‹ /home/peertube/logs ›
: at Object.mkdirSync (fs.js:757:3)
: at Object.mkdirsSync (/var/www/peertube/versions/peertube-v2.1.1/node_modules/fs-extra/lib/mkdirs/mkdirs-sync.js:31:9)
: at Object. (/var/www/peertube/versions/peertube-v2.1.1/dist/server/helpers/logger.js:10:12)
: at Module._compile (internal/modules/cjs/loader.js:778:30)
: at Object.Module._extensions…js (internal/modules/cjs/loader.js:789:10)
: at Module.load (internal/modules/cjs/loader.js:653:32)
: at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
: at Function.Module._load (internal/modules/cjs/loader.js:585:3)
: at Module.require (internal/modules/cjs/loader.js:692:17)
: at require (internal/modules/cjs/helpers.js:25:18)
: npm ERR! code ELIFECYCLE
: npm ERR! errno 1
: npm ERR! peertube@2.1.1 start: node dist/server
: npm ERR! Exit status 1
: npm ERR!
: npm ERR! Failed at the peertube@2.1.1 start script.
: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
: npm ERR! A complete log of this run can be found in:
: npm ERR! /var/www/peertube/.npm/_logs/2020-03-30T13_10_30_075Z-debug.log
Please paste the content of your systemd script and run ls -l /home and ls -l /home/peertube
The output of the command ls -l /home:
total 32
drwxr-xr-x 19 ■■■■■■■ ■■■■■■■ 4096 mars 30 11:14 ■■■■■■■
drwxr-xr-x 24 root root 4096 mars 6 2018 littledev
drwx------ 2 root root 16384 août 16 2019 lost+found
drwxrwx--- 6 www-data root 4096 févr. 9 13:28 nextcloud
drwxr-xr-x 3 peertube peertube 4096 mars 30 11:37 peertube
The output of the command ls -l /home/peertube
total 0
The content of my systemd script:
[Unit]
Description=PeerTube daemon
After=network.target postgresql.service redis-server.service
[Service]
Type=simple
Environment=NODE_ENV=production
Environment=NODE_CONFIG_DIR=/var/www/peertube/config
User=peertube
Group=peertube
ExecStart=/usr/bin/npm start
WorkingDirectory=/var/www/peertube/peertube-latest
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=peertube
Restart=always
; Some security directives.
; Mount /usr, /boot, and /etc as read-only for processes invoked by this service.
ProtectSystem=full
; Sets up a new /dev mount for the process and only adds API pseudo devices
; like /dev/null, /dev/zero or /dev/random but not physical devices. Disabled
; by default because it may not work on devices like the Raspberry Pi.
PrivateDevices=false
; Ensures that the service process and all its children can never gain new
; privileges through execve().
NoNewPrivileges=true
; This makes /home, /root, and /run/user inaccessible and empty for processes invoked
; by this unit. Make sure that you do not depend on data inside these folders.
ProtectHome=true
; Drops the sys admin capability from the daemon.
CapabilityBoundingSet=~CAP_SYS_ADMIN
[Install]
WantedBy=multi-user.target
Remove ProtectHome=true from your systemd template
Effectively, I did not read this file. Thank you 