Hi,
today i wanted to update my peer from 6.1.0 to 6.2.0
The update.sh fails at « yarn install --production --pure-lockfile »
Unknown Syntax Error: Unsupported option name (« –pure-lockfile »)
I´m not in expert in these things.
I´m shure you need more information, please tell me what you need.
It would be nice if anyone can help me here.
Peertube run at a Debian GNU/Linux 12 on a virtual Server
Hi,
I think you have not installed the appropriate yarn command. Please remove it apt remove yarn and install it using Installation | Yarn
Hey Chocobozzz,
thank`s for your help.
apt remove yarn says
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Note, selecting ‹ cmdtest › instead of ‹ yarn ›
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
This looks like nothing happens?
Then « npm install --global yarn »
sayd:
changed 1 package in 626ms
Now « yarn --version »:
3.6.1
Sorry, the error is still the same… 
Hi,
sudo npm uninstall -g yarn
Then use the Alternatives section of Installation | Yarn
As stated in the documentation PeerTube requires yarn 1.x 
Hi,
I think I have installed the right version
aptitude -V -s install yarn
yarn is already installed at the requested version (1.22.22-1)
yarn is already installed at the requested version (1.22.22-1)
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Would download/install/remove packages.
But:
yarn --version
3.6.1
What is happening here?
I think I have installed the right version, but there is another version too?
I´ll be happy if days have more than 24hours, so that I can learn much more about software, but in this moment it is a challenge for me to understand what is happening here…
The update-script still don`t work…
Okay, this helped Me:
Now, the Updatescript runs till the end, after an restart Peertube exits with an errorcode, let me try to find the problem by myself…
For this moment:
Thank you very much for yout Time an knowledge @Chocobozzz <3
Puuh…
sorry…
I have no idea what happend with my installation, but this happend when I start the update.
extracting: peertube-v6.2.0/support/docker/production/.gitignore
inflating: peertube-v6.2.0/support/docker/gitpod/Dockerfile
inflating: peertube-v6.2.0/support/docker/gitpod/setup_postgres.sql
inflating: peertube-v6.2.0/support/systemd/peertube.service
inflating: peertube-v6.2.0/yarn.lock
yarn install v1.22.22
[1/5] Validating package.json…
[2/5] Resolving packages…
[3/5] Fetching packages…
[######################--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 127/1494/var/www/peertube/config/production.yaml.new generated
You can review it and replace your existing production.yaml configuration==========================================================
Please read the IMPORTANT NOTES on Release v6.2.0 · Chocobozzz/PeerTube · GitHub
Then restart PeerTube!
This looks like yarn do not complete the job?
Then, when I want to restart Peertube it fails with this log:
Jul 21 11:00:29 91151083-4692-4341-a481-732b3b3746df systemd[1]: Stopping peertube.service - PeerTube daemon…
Jul 21 11:00:29 91151083-4692-4341-a481-732b3b3746df systemd[1]: peertube.service: Deactivated successfully.
Jul 21 11:00:29 91151083-4692-4341-a481-732b3b3746df systemd[1]: Stopped peertube.service - PeerTube daemon.
Jul 21 11:00:29 91151083-4692-4341-a481-732b3b3746df systemd[1]: peertube.service: Consumed 7.239s CPU time.
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df systemd[1]: Started peertube.service - PeerTube daemon.
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df peertube[2014]: node:internal/modules/esm/resolve:842
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df peertube[2014]: throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df peertube[2014]: ^
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df peertube[2014]: Error [ERR_MODULE_NOT_FOUND]: Cannot find package ‹ express › imported from /var/www/peertube/versions/peertube-v6.2.0/dist/server.js
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df peertube[2014]: at packageResolve (node:internal/modules/esm/resolve:842:9)
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df peertube[2014]: at moduleResolve (node:internal/modules/esm/resolve:915:18)
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df peertube[2014]: at defaultResolve (node:internal/modules/esm/resolve:1124:11)
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df peertube[2014]: at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df peertube[2014]: at ModuleLoader.resolve (node:internal/modules/esm/loader:526:25)
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df peertube[2014]: at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:249:38)
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df peertube[2014]: at ModuleJob._link (node:internal/modules/esm/module_job:126:49) {
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df peertube[2014]: code: ‹ ERR_MODULE_NOT_FOUND ›
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df peertube[2014]: }
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df peertube[2014]: Node.js v22.5.0
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df systemd[1]: peertube.service: Main process exited, code=exited, status=1/FAILURE
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df systemd[1]: peertube.service: Failed with result ‹ exit-code ›.
Jul 21 11:00:37 91151083-4692-4341-a481-732b3b3746df systemd[1]: peertube.service: Scheduled restart job, restart counter is at 1.
I have no Idea where to search for the beginning of this problem.
Can you try to run the upgrade process again?
Hello,
update.sh says:
yarn install v1.22.22
[1/5] Validating package.json…
[2/5] Resolving packages…
[3/5] Fetching packages…
[#######################------------------------------------------------------------------------------------------------------------------------------------] 226/1494/var/www/peertube/config/production.yaml.new generated
You can review it and replace your existing production.yaml configuration==========================================================
Please read the IMPORTANT NOTES on Release v6.2.0 · Chocobozzz/PeerTube · GitHub
Then restart PeerTube!
Okay, another number, but again it looks to me that yarn not worked till the end…
…checked production.yaml.new
…and restart
I´m sorry, but still the same message:
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df systemd[1]: Started peertube.service - PeerTube daemon.
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29355]: node:internal/modules/esm/resolve:842
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29355]: throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29355]: ^
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29355]: Error [ERR_MODULE_NOT_FOUND]: Cannot find package ‹ express › imported from /var/www/peertube/versions/peertube-v6.2.0/dist/server.js
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29355]: at packageResolve (node:internal/modules/esm/resolve:842:9)
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29355]: at moduleResolve (node:internal/modules/esm/resolve:915:18)
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29355]: at defaultResolve (node:internal/modules/esm/resolve:1124:11)
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29355]: at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29355]: at ModuleLoader.resolve (node:internal/modules/esm/loader:526:25)
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29355]: at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:249:38)
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29355]: at ModuleJob._link (node:internal/modules/esm/module_job:126:49) {
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29355]: code: ‹ ERR_MODULE_NOT_FOUND ›
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29355]: }
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29355]: Node.js v22.5.0
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df systemd[1]: peertube.service: Main process exited, code=exited, status=1/FAILURE
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df systemd[1]: peertube.service: Failed with result ‹ exit-code ›.
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df systemd[1]: peertube.service: Scheduled restart job, restart counter is at 1.
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df systemd[1]: Stopped peertube.service - PeerTube daemon.
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df systemd[1]: Started peertube.service - PeerTube daemon.
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29367]: node:internal/modules/esm/resolve:842
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29367]: throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
Jul 22 13:33:37 91151083-4692-4341-a481-732b3b3746df peertube[29367]: ^
Can you paste the output of cd /var/www/peertube/peertube-latest && yarn install --pure-lockfile?
Hey there,
here is the output:
~# cd /var/www/peertube/peertube-latest && yarn install --pure-lockfile
yarn install v1.22.22
[1/5] Validating package.json…
[2/5] Resolving packages…
[3/5] Fetching packages…
error Error: C09C2421947F0000:error:0A0003FC:SSL routines:ssl3_read_bytes:sslv3 alert bad record mac:…/deps/openssl/openssl/ssl/record/rec_layer_s3.c:1590:SSL alert number 20info Visit yarn install | Yarn for documentation about this command.
edit:
I found this site witch describe this issue:
but i`m not shure if it is a good idea to test something on my own in this Momentand they use another version of yarn.
Edit2:
When I start yarn a few times with every run the progress ist a bit better:
[1/5] Validating package.json…
[2/5] Resolving packages…
[3/5] Fetching packages…
[##################----------------------------------------------------------------------------------------------------------------------------------------------------] 161/1461r
[1/5] Validating package.json…
[2/5] Resolving packages…
[3/5] Fetching packages…
[################################--------------------------------------------------------------------------------------------------------------------------------------] 285/1461r
[1/5] Validating package.json…
[2/5] Resolving packages…
[3/5] Fetching packages…
[################################--------------------------------------------------------------------------------------------------------------------------------------] 285/1461r
at the end only 3 packages are left.
[1/5] Validating package.json…
[2/5] Resolving packages…
[3/5] Fetching packages…
[#####################################################################################################################################################################] 1458/1461
now i get an network error:
info There appears to be trouble with your network connection. Retrying…
have I tried it too often?
have I triggered an IP-filter?
Do you have a stable network connection?
I askd myself the same question. I saw yarn completed some jobs with every run, but dont make it to the end.
Now, i can not complete the 4 last packets.
This looks like there is a network problem.
The Server is an VServer at Strato. de
Pings are okay…
(I inserted spaces to aviod sending links)
ping peertubevdb. de
PING peertubevdb.de (195.20.227.146) 56(84) Bytes an Daten.
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=1 ttl=56 Zeit=13.0 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=2 ttl=56 Zeit=11.1 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=3 ttl=56 Zeit=11.2 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=4 ttl=56 Zeit=11.7 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=5 ttl=56 Zeit=11.6 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=6 ttl=56 Zeit=11.3 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=7 ttl=56 Zeit=11.3 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=8 ttl=56 Zeit=11.2 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=9 ttl=56 Zeit=11.7 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=10 ttl=56 Zeit=11.1 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=11 ttl=56 Zeit=11.3 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=12 ttl=56 Zeit=11.1 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=13 ttl=56 Zeit=11.3 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=14 ttl=56 Zeit=11.4 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=15 ttl=56 Zeit=11.7 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=16 ttl=56 Zeit=11.7 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=17 ttl=56 Zeit=11.1 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=18 ttl=56 Zeit=11.6 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=19 ttl=56 Zeit=11.8 ms
64 Bytes von ip195-20-227-146.pbiaas. com (195.20.227.146): icmp_seq=20 ttl=56 Zeit=12.3 ms
What is a little bit confusing is the reverseDNS don`t send my domain. I asked the strato service about this.
I can make livestreams with 1080p and 60Hz with 6000kbps with OBS with no problems, view the videos and anything is okay, only this update will not work.
Hello,
okay, Strato has a problem with ReverseDNS, but I think (or hope) this is not our Problem?
I want to know a little but more and do:
cd /var/www/peertube/peertube-latest && yarn install --pure-lockfile --verbose
there is a lot more information:
(again I added spaced to be able to send this post)
yarn install v1.22.22
verbose 0.235741502 Checking for configuration file « /var/www/peertube/versions/peertube-v6.1.0/.npmrc ».
verbose 0.235993941 Checking for configuration file « /usr/local/share/.npmrc ».
verbose 0.23631191 Checking for configuration file « /usr/etc/npmrc ».
verbose 0.236585719 Checking for configuration file « /root/.npmrc ».
verbose 0.236717008 Checking for configuration file « /var/www/peertube/versions/peertube-v6.1.0/.npmrc ».
verbose 0.236824248 Checking for configuration file « /var/www/peertube/versions/.npmrc ».
verbose 0.236939917 Checking for configuration file « /var/www/peertube/.npmrc ».
verbose 0.237058297 Checking for configuration file « /var/www/.npmrc ».
verbose 0.237221056 Checking for configuration file « /var/.npmrc ».
verbose 0.237652985 Checking for configuration file « /var/www/peertube/versions/peertube-v6.1.0/.yarnrc ».
verbose 0.237808474 Checking for configuration file « /usr/local/share/.yarnrc ».
verbose 0.237926294 Found configuration file « /usr/local/share/.yarnrc ».
verbose 0.238174003 Checking for configuration file « /usr/etc/yarnrc ».
verbose 0.238295453 Checking for configuration file « /root/.yarnrc ».
verbose 0.238400132 Checking for configuration file « /var/www/peertube/versions/peertube-v6.1.0/.yarnrc ».
verbose 0.238501572 Checking for configuration file « /var/www/peertube/versions/.yarnrc ».
verbose 0.238607111 Checking for configuration file « /var/www/peertube/.yarnrc ».
verbose 0.238683611 Found configuration file « /var/www/peertube/.yarnrc ».
verbose 0.23889153 Checking for configuration file « /var/www/.yarnrc ».
verbose 0.23898868 Checking for configuration file « /var/.yarnrc ».
verbose 0.243580464 current time: 2024-07-25T14:47:43.121Z
verbose 0.288982832 Performing « GET » request to « h ttps://yarnpkg.com/latest-version ».
[1/5] Validating package.json…
[2/5] Resolving packages…
[3/5] Fetching packages…
verbose 0.931177837 Request « h ttps://yarnpkg.com/latest-version » finished with status code 200.
verbose 1.340474491 Performing « GET » request to « h ttps://registry.yarnpkg.com/date-fns/-/date-fns-2.30.0.tgz ».
verbose 1.34920435 Performing « GET » request to « h ttps://registry.yarnpkg.com/rxjs/-/rxjs-7.8.1.tgz ».
verbose 1.451678165 Performing « GET » request to « h ttps://registry.yarnpkg.com/es-abstract/-/es-abstract-1.22.4.tgz ».
info There appears to be trouble with your network connection. Retrying…
verbose 34.458533644 Performing « GET » request to « h ttps://registry.yarnpkg.com/date-fns/-/date-fns-2.30.0.tgz ».
verbose 34.459892679 Performing « GET » request to « h ttps://registry.yarnpkg.com/rxjs/-/rxjs-7.8.1.tgz ».
verbose 34.528284004 Error: write EPROTO C00CF0C2EF7F0000:error:0A000095:SSL routines:tls_process_finished:digest check failed:…/deps/openssl/openssl/ssl/statem/statem_lib.c:864:at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:95:16)error Error: write EPROTO C00CF0C2EF7F0000:error:0A000095:SSL routines:tls_process_finished:digest check failed:…/deps/openssl/openssl/ssl/statem/statem_lib.c:864:
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:95:16)info Visit h ttps://yarnpkg.com/en/docs/cli/install for documentation about this command.
Is there a SSL-problem?
Pining the Server from install is okay I think:
ping registry.yarnpkg. com
PING registry.yarnpkg. com(2606:4700::6810:1c22 (2606:4700::6810:1c22)) 56 data bytes
64 bytes from 2606:4700::6810:1c22 (2606:4700::6810:1c22): icmp_seq=1 ttl=59 time=2.08 ms
64 bytes from 2606:4700::6810:1c22 (2606:4700::6810:1c22): icmp_seq=2 ttl=59 time=1.11 ms
64 bytes from 2606:4700::6810:1c22 (2606:4700::6810:1c22): icmp_seq=3 ttl=59 time=1.00 ms
64 bytes from 2606:4700::6810:1c22 (2606:4700::6810:1c22): icmp_seq=4 ttl=59 time=2.38 ms
64 bytes from 2606:4700::6810:1c22 (2606:4700::6810:1c22): icmp_seq=5 ttl=59 time=1.09 ms
64 bytes from 2606:4700::6810:1c22 (2606:4700::6810:1c22): icmp_seq=6 ttl=59 time=1.12 ms
64 bytes from 2606:4700::6810:1c22 (2606:4700::6810:1c22): icmp_seq=7 ttl=59 time=1.16 ms
64 bytes from 2606:4700::6810:1c22 (2606:4700::6810:1c22): icmp_seq=8 ttl=59 time=1.07 ms
64 bytes from 2606:4700::6810:1c22 (2606:4700::6810:1c22): icmp_seq=9 ttl=59 time=1.14 ms
Your server may have an issue, is it possible to try with another one? Maybe on another provider?
Is the server datetime correctly set? Sometimes it can explain some certificates validation errors (as it may think that the certificate date is outdated). Seems not related to your error message, but…