I am looking for help to install perlbrew on my shared webspace (Provider: uberspace.de). I used the usually documentation an perlbrew.pl and put:
\curl -L http://install.perlbrew.pl | bash
In my terminal.
Download completed, but than the terminal says:
$ curl -L http://install.perlbrew.pl | bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
103 1247 103 1247 0 0 1274 0 --:--:-- --:--:-- --:--:-- 1274
## Download the latest perlbrew
## Installing perlbrew
print() on closed filehandle $fh at perlbrew.YQFev9 line 893.
perlbrew is installed: /package/host/localhost/perlbrew/bin/perlbrew
NOTICE: /package/host/localhost/perlbrew/etc/bashrc already exists and not updated.
NOTICE: /package/host/localhost/perlbrew/etc/cshrc already exists and not updated.
Fail to create /package/host/localhost/perlbrew/etc/csh_reinit. Please check the permission of /package/host/localhost/perlbrew/etc and try `perlbrew init` again. at perlbrew.YQFev9 line 806.
I have no permission to access /package/host/localhost/perlbrew/...
I think that perlbrew has to install on /perl5/perlbrew, right?
How can I change the location of the installation?
Or is there another problem?
Thanks!
Related
I'm attempting to install a new perl version with perlbrew:
perlbrew install perl-5.34.1
but this produces the error:
Fetching perl 5.34.1 as /home/703404669/perl5/perlbrew/dists/perl-5.34.1.tar.gz
Download https://cpan.metacpan.org/authors/id/S/SH/SHAY/perl-5.34.1.tar.gz to /home/703404669/perl5/perlbrew/dists/perl-5.34.1.tar.gz
ERROR: Failed to download https://cpan.metacpan.org/authors/id/S/SH/SHAY/perl-5.34.1.tar.gz
ERROR: Failed to execute the command
curl --silent --location --fail -o /home/703404669/perl5/perlbrew/dists/perl-5.34.1.tar.gz https://cpan.metacpan.org/authors/id/S/SH/SHAY/perl-5.34.1.tar.gz
Reason:
5888
which I'm unable to find on Google searches.
I know that there isn't any typo, because when I intentionally write something wrong, I get a different error.
I have no idea why this is happening, nor to fix it.
EDIT:
the command
curl --location https://cpan.metacpan.org/authors/id/S/SH/SHAY/perl-5.34.1.tar.gz > /dev/null
outputs
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 17.3M 100 17.3M 0 0 68.5M 0 --:--:-- --:--:-- --:--:-- 68.5M
How can I install a perl version with perlbrew?
5888 is 0x1700. This could be $? for a program that used exit(0x17), which is to say exit(23). curl uses that exit code when
23 Write error. Curl couldn't write data to a local filesystem or similar.
Sounds like it can't write to /home/703404669/perl5/perlbrew/dists/perl-5.34.1.tar.gz.
If the directory doesn't exist, maybe you didn't properly install perlbrew.
Ways to install perlbrew:
\curl -L https://install.perlbrew.pl | bash
\wget -O - https://install.perlbrew.pl | bash
\fetch -o- https://install.perlbrew.pl | sh
sudo cpan App::perlbrew
perlbrew init
You also need to place a command in your shell's interactive startup script as instructed.
Or maybe you don't have enough disk space. Did you mean to install perlbrew somewhere other than /home/703404669/perl5/perlbrew?
The default perlbrew root directory is ~/perl5/perlbrew, which can be changed by setting PERLBREW_ROOT environment variable before the installation and initialization.
In my case the problem was that it would not create the destination folder for that download. So what fixed it for me was:
mkdir $HOME/perl5/perlbrew/dists -p
In the above case just:
mkdir -p /home/703404669/perl5/perlbrew/dists
I'm downloading minikube on OS X (Catalina 10.15.7) from releases/latest/minikube-darwin-amd64 and it fails when run, see below:
minikube version
/usr/local/bin/minikube: line 1: syntax error near unexpected token `<'
/usr/local/bin/minikube: line 1: `<?xml version='1.0' encoding='UTF-8'?><Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Details>No such object: minikube/releases/latest/minikube-darwin-amd</Details></Error>'
Not sure what key it refers to.
This problem was caused by an invalid URL in the curl command. Looking at the error message, my guess is that the 64 was missing at the end.
I've reproduced this error and we can see that the error message is exactly the same as in the question (I'm using Linux so instead of minikube-darwin-amd64 I used minikube-linux-amd64):
NOTE: I didn't provide 64 at the end.
$ curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 205 100 205 0 0 6029 0 --:--:-- --:--:-- --:--:-- 6029
$ sudo install minikube-linux-amd /usr/local/bin/minikube
The size is too small for the minikube:
$ ls -lh /usr/local/bin/minikube
-rwxr-xr-x 1 root root 205 Aug 13 07:30 /usr/local/bin/minikube
The error message:
$ minikube version
/usr/local/bin/minikube: line 1: syntax error near unexpected token `<'
/usr/local/bin/minikube: line 1: `<?xml version='1.0' encoding='UTF-8'?><Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Details>No such object: minikube/releases/latest/minikube-linux-amd</Details></Error>'
Now let's install the minikube correctly:
$ curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64
$ sudo install minikube-linux-amd64 /usr/local/bin/minikube
We can see that the real size of the minikube is >65M:
$ ls -lh /usr/local/bin/minikube
-rwxr-xr-x 1 root root 67M Aug 13 07:32 /usr/local/bin/minikube
And everything works as expected:
$ minikube version
minikube version: v1.22.0
commit: a03fbcf166e6f74ef224d4a63be4277d017bb62e
I try to install semver on my Postgresql 12. I installed postgis successfully and used following command to install pg-semver (semver extension) on my Centos 7 server:
yum install pg-semver
Then i ran
CREATE EXTENSION semver;
I got following error:
couldn't open extension control file
/usr/pgsql-12/share/extension/semver.control : No such file or
directory
I copied all files from "/usr/share/pgsql/extension/" to "/usr/pgsql-12/share/extension". Now I'm getting following error:
ERROR: ERROR: could not access file "semver": No such file or
directory
UPDATE (28.02.2020):
I removed pg-semver because it delivers for PSQL 9.2. I try to now build itself by using the documentation which developer provided.
I downloaded the semver extension from https://github.com/theory/pg-semver/archive/master.zip and then unzipped. After that I run following command:
make
and get:
make: There is nothing to do for the "all" target.
then:
make install
and get:
/bin/sh /usr/lib64/pgsql/pgxs/src/makefiles/../../config/install-sh -c
-m 644 ./semver.control '/usr/share/pgsql/extension/' /bin/sh /usr/lib64/pgsql/pgxs/src/makefiles/../../config/install-sh -c -m 644
./sql/semver--0.20.0.sql ./sql/semver--unpackaged--0.2.1.sql
./sql/semver--0.20.0--0.21.0.sql ./sql/semver--0.12.0--0.13.0.sql
./sql/semver--0.3.0--0.4.0.sql ./sql/semver--0.16.0--0.17.0.sql
./sql/semver--0.13.0--0.15.0.sql ./sql/semver--0.11.0--0.12.0.sql
./sql/semver--0.2.4--0.3.0.sql ./sql/semver--0.2.1--0.2.4.sql
./sql/semver--0.5.0--0.10.0.sql ./sql/semver--0.10.0--0.11.0.sql
./sql/semver.sql ./sql/semver--0.17.0--0.20.0.sql
./sql/semver--0.15.0--0.16.0.sql '/usr/share/pgsql/extension/'
/bin/sh /usr/lib64/pgsql/pgxs/src/makefiles/../../config/install-sh -c
-m 755 src/semver.so '/usr/lib64/pgsql/' /bin/sh /usr/lib64/pgsql/pgxs/src/makefiles/../../config/install-sh -c -m 644
./doc/semver.mmd '/usr/share/doc/pgsql/extension/'
then:
make installcheck
and get:
============== dropping database "contrib_regression" ============== DROP DATABASE
============== creating database "contrib_regression" ============== CREATE DATABASE ALTER DATABASE
============== installing plpgsql ============== CREATE LANGUAGE
============== running regression test queries ============== test base ... FAILED (test process exited with
exit code 3)
--------------- 1 of 1 tests failed.
The differences that caused some tests to fail can be viewed in the
file "/tmp/ttt/pg-semver-master/regression.diffs". A copy of the test
summary that you see above is saved in the file
"/tmp/ttt/pg-semver-master/regression.out".
make: *** [installcheck] Error 1
the content of regression.out:
...... ! ok 278 - minor version check ! ok 279 - Function
get_semver_patch() should exist ! ok 280 - semver ! ok 281 - Function
get_semver_patch() should return integer ! ok 282 - patch version
check ! ok 283 - Function get_semver_prerelease() should exist ! ok
284 - semver ! ok 285 - Function get_semver_prerelease() should return
text ! ok 286 - prerelease label check ! ok 287 - 1.0.0 should be in
range [1.0.0, 2.0.0] ! ok 288 - 1.0.0 should not be in range [1.0.1,
2.0.0] ! ok 289 - 2.0.0 should not be in range [1.0.1, 2.0.0) ! ok 290 - 1.9999.9999 should be in range [1.0.1, 2.0.0) ! ok 291 - 1000.0.0 should be in range [1.0.0,) ! ok 292 - Should be able to work with
arrays of semverranges
--- 1,2 ---- \set ECHO none ! psql:sql/semver.sql:30: ERROR: could not access file "semver": No such file or directory
There is no semver.so in /usr/pgsql-12/lib/, there is a semver.so in /usr/lib64/pgsql/ but it's also for version 9.2 ?
The reason why you are unable to install semver is twofold:
You are getting the error could not access file "semver": No such file or directory because you didn't copy /usr/lib64/pgsql/semver.so to /usr/pgsql-12/lib. However, you can't simply copy that over because of this following second reason:
yum install pg-semver will install semver from the EPEL library, which is the pre-packaged PostgreSQL version 9.2 that is shipped with CentOS 7. You installed PostgreSQL version 12 (either by compiling it yourself or downloading the PGDG repo and installing the postgresql12 package). The semver.so file that is shipped with the EPEL repo is not compatible, as it was compiled against PostgreSQL version 9.2, not version 12. If you attempt to load the EPEL semver.so into your v.12 database, you will see:
postgres=# create extension semver;
ERROR: incompatible library "/usr/pgsql-12/lib/semver.so": version mismatch
DETAIL: Server is version 12, library is version 9.2.
Therefore, the only way for you to install semver is by following the compilation steps detailed in the documentation:
make
make install
make installcheck
psql -c "CREATE EXTENSION semver;"
If you have not done so already (and you installed postgresql 12 via PGDG RPM), you will need to do the following in order to download and compile:
yum -y install postgresql12-devel
yum -y groupinstall "Development Tools"
You may also run into issues with compilation, like: clang: error: unknown argument: '-flto=thin' because the PGDG RPM was compiled with clang -- you can bypass that by doing:
with_llvm=no make -e
with_llvm=no make -e install
with_llvm=no make -e installcheck
psql -c "create extension semver"
Disclosure: I work for EnterpriseDB (EDB)
Follow this guide to install semver:
https://pgxn.org/dist/semver/
I am trying to install docker compose on the Ubuntu 18.04.2 LTS.
I tried installing using the official link here and followed the Docker Compose documentation given, but when i run the command
sudo curl -L "https://github.com/docker/compose/releases/download/1.24.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
then after some time it gives me this error
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 617 0 617 0 0 613 0 --:--:-- 0:00:01 --:--:-- 613
24 8280k 24 2056k 0 0 789 0 2:59:06 0:44:27 2:14:39 0
**curl: (56) OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 104**
Kindly help me on this i have tried many times but it is not working.
I had the same problem. I assume that you are using Docker Docs, which are usually outdated. You should go to Docker Compose Github instead.
Solution
1 - Open Linux Terminal by pressing Ctrl + Alt + T
2 - Install curl:
sudo apt install curl
3 - Turn on root privileges in terminal for your user (something like admin in Windows OS), with command:
sudo -i
4 - Go to Docker Compose Github. In releases you will find this code. Run it in your linux terminal.
curl -L https://github.com/docker/compose/releases/download/1.25.1-rc1/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose
5 - Turn off root privileges in terminal for your user, with command:
exit
6 - Check if docker-compose is installed with command:
docker-compose version
Outcome: In your terminal, you should see docker-compose version number and some other informations.
vnstat is updating only one interface every five minutes. I have to use
vnstat -u
to manually update the rest of interfaces. All interfaces are already enabled, but only one interface is updating every 5 minutes.
Check which user the vnstat daemon is running as using ps aux | grep [v]nstat.
I recently had the same problem and after priming the database with
vnstat -u -i eth0 as root the vnstat process couldn't write to the /var/lib/vnstat/eth0
file as it was running as user "vnstat".
If vnstat is running as user "vnstat" ensure that it has permission to write to /var/lib/vnstat/eth0.
When you add the interface for eth0 or ppp0 or whatever, make sure you do it as the vnstat user. ie
sudo -u vnstat vnstat -i ppp0 -u
If you run this as root first you are will have problems even if you chmod the file in /var/lib/vnstat. This is due to the creation of a back file called .ppp0 which you might miss if you are not looking for it. There will be an error in syslog saying that the backup file cannot be written.
So I was having a similar problem where i was getting the following:
$ vnstat -i eno1
eno1: not enough data available yet
I also tried every other command while pointing to eno1. I would sometimes even get:
Error: Unable to create database backup "/var/lib/vnstat/.eno1"
OR
Segmentation fault (core dumped)
I tried reinstalling, and everything else under the sun.
Following Andrew's answer to the 't' returned:
Error: Unable to open database "/var/lib/vnstat/eno1" for writing: Permission denied
so instead I did the following, but I'm not sure which one of these commands did the trick.
$ sudo vnstat -i eno1 -u
$ sudo vnstat -u -i eno1
Then I checked to see if the interface was working again:
$ sudo vnstat -i eno1
which returned:
>
Database updated: Wed Dec 5 10:17:37 2018
(eno1) since 1969-12-31
rx: 2 KiB tx: 1 KiB total: 3 KiB
monthly
rx | tx | total | avg. rate
------------------------+-------------+-------------+---------------
Dec '69 2 KiB | 1 KiB | 3 KiB | 0.00 kbit/s
------------------------+-------------+-------------+---------------
estimated -- | -- | -- |
daily
rx | tx | total | avg. rate
------------------------+-------------+-------------+---------------
today 2 KiB | 1 KiB | 3 KiB | 0.00 kbit/s
------------------------+-------------+-------------+---------------
estimated -- | -- | -- |
Now its finally able to read and write to eno1 log. I noticed this problem since conky was not showing up any stats reports on today && Month && total. I wasn't expecting anything under month, but after a couple days I was expecting something under hours.
I realise the rest will take a while to populate with data. But now I know for sure it is working. Also, my conky app is finally displaying the information.
However, prior to this solution, I had already chmod the file.
Additional info for newbies such as myself:
- make sure to check which interface you are using, I often see solutions for eth0 and others that do not appear when using "$ ifconfig". Enter:
$ ifconfig
and you should see on the left hand side of the results the interface name. Mine are, eno1, lo, and wlo1.
next to the label: "Link encap:" it should say if it is wireless, ethernet, or local loopback
lo is the local loopback a.k.a localhost/127.0.0.1
What I am not sure of, in my case, is the difference between eno1 and wlo1. they both say "Ethernet". I wonder if doesn't have something to do with my direct wifi printer.