Warning: could not download https://pkg.julialang.org/registries - julia

I live in a country with a high level of internet censorship. It's been a while since I updated my packages, and I'm unsuccessful in updating them.
(#v1.8) pkg> up
┌ Warning: could not download https://pkg.julialang.org/registries
│ exception = schannel: failed to receive handshake, SSL/TLS connection failed while requesting https://pkg.julialang.org/registries
└ # Pkg.Registry C:\workdir\usr\share\julia\stdlib\v1.8\Pkg\src\Registry\Registry.jl:68
Updating registry at `C:\Users\<A GEEK>\.julia\registries\General.toml`
Updating git-repo `https://github.com/peng1999/PkgDependency.jl`
No Changes to `C:\Users\<A GEEK>\.julia\environments\v1.8\Project.toml`
No Changes to `C:\Users\<A GEEK>\.julia\environments\v1.8\Manifest.toml`
I tried using a Virtual private network to bypass the censorship, but the error still exists. How can I solve this?
Update:
I tried another server for my VPN, and it was helpful until I got this error:
(#v1.8) pkg> update
Updating registry at `C:\Users\<A GEEK>\.julia\registries\General.toml`
Downloading [=> ] 0.6 %
# I didn't monitor it and switched the window to another application. After a minute I came to check the progress, and I was confronted with the following log:
(#v1.8) pkg> update
Updating registry at `C:\Users\<A GEEK>\.julia\registries\General.toml`
┌ Error: Some registries failed to update:
│ — C:\Users\<A GEEK>\.julia\registries\General.toml — failed to download from https://pkg.julialang.org/registry/23338594-aafe-5451-b93e-139f81909106/80cc6104fbf941669a72a24525a38330e308ae6c. Exception: HTTP/1.1 200 OK (Operation too slow. Less than 1 bytes/sec transferred the last 20 seconds) while requesting https://pkg.julialang.org/registry/23338594-aafe-5451-b93e-139f81909106/80cc6104fbf941669a72a24525a38330e308ae6c
└ # Pkg.Registry C:\workdir\usr\share\julia\stdlib\v1.8\Pkg\src\Registry\Registry.jl:449
Updating git-repo `https://github.com/peng1999/PkgDependency.jl`
No Changes to `C:\Users\<A GEEK>\.julia\environments\v1.8\Project.toml`
No Changes to `C:\Users\<A GEEK>\.julia\environments\v1.8\Manifest.toml`
# I tried it again and the content of the exception changed:
│ exception = HTTP/1.1 301 AS -> IN internal redirect trigger (schannel: failed to receive handshake, SSL/TLS connection failed) while requesting https://pkg.julialang.org/registries
└ # Pkg.Registry C:\workdir\usr\share\julia\stdlib\v1.8\Pkg\src\Registry\Registry.jl:68

Related

py3.11: Unable to install pip packages (directly or using requirements.txt)

I have just cloned one of my repos from github to work on it only to be met with this error:
$ pip install -r deps/requirements.txt
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f287e110a50>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/django/
i have also tried to install packages directly:
$ pip install django
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fc4e628ba10>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/django/
i have also tried clearing cache but the problem still persists.
Why is my pip fetching from /simple/django/ ?
I have finally managed to make things work by changing /etc/resolv.conf.
nameserver 8.8.8.8 # Added these lines
nameserver 8.8.4.4 # Added these lines
nameserver 127.0.0.53
options edns0 trust-ad
search .
Relied on this question: How do I add a DNS server via resolv.conf?
Update:
Unfortunately, my method gets overwritten on reboot, I will keep digging for ways to make it permanent.
Update #2
I have managed to make my changes permanent by updating /etc/resolvconf/resolv.conf.d/tail, on every #reboot the system will append the content of the file to /etc/resolv.conf.
# Add these lines to /etc/resolvconf/resolv.conf.d/tail
nameserver 8.8.8.8
nameserver 8.8.4.4

Issues with persistent volume on DigitalOcean Kubernetes cluster

Just created a managed 2-node Kubernetes (ver. 1.22.8) cluster on DigitalOcean (DO).
After installing WordPress using Bitnami Helm chart, and then installing a WP plugin, the site became unreachable.
Looking into DO K8s dashboard in the deployment section, the wordpress deployment shows the following error:
0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims.
AttachVolume.Attach failed for volume "pvc-c859847e-f250-4e71-9ed3-63c92cc01f50" : rpc error: code = DeadlineExceeded desc = context deadline exceeded
MountVolume.MountDevice failed for volume "pvc-c859847e-f250-4e71-9ed3-63c92cc01f50" : rpc error: code = Internal desc = formatting disk failed: exit status 1 cmd: 'mkfs.ext4 -F /dev/disk/by-id/scsi-0DO_Volume_pvc-c859847e-f250-4e71-9ed3-63c92cc01f50' output: "mke2fs 1.45.5 (07-Jan-2020)\nThe file /dev/disk/by-id/scsi-0DO_Volume_pvc-c859847e-f250-4e71-9ed3-63c92cc01f50 does not exist and no size was specified.\n"
Readiness probe failed: HTTP probe failed with statuscode: 404
As I'm quite new to K8s, I don't know much how to troubleshoot this.
Any help would be much appreciated.
UPDATE
I was able to reproduce the error and found what triggers it.
WordPress Bitnami charts installs several WP plugins by default. As soon as I try to delete them, the error shows up and the persistent volume gets corrupted...
Is this maybe a bug or it's standard behavior?

Riak is Not Starting After Reboot

I'm seeing an IO error on the Riak console. I'm not sure what the cause is as the owner of the directory is riak. Here's how the error looks.
2018-01-25 23:18:06.922 [info] <0.2301.0>#riak_kv_vnode:maybe_create_hashtrees:234 riak_kv/730750818665451459101842416358141509827966271488: unable to start index_hashtree: {error,{{badmatch,{error,{db_open,"IO error: lock /var/lib/riak/anti_entropy/v0/730750818665451459101842416358141509827966271488/LOCK: already held by process"}}},[{hashtree,new_segment_store,2,[{file,"src/hashtree.erl"},{line,725}]},{hashtree,new,2,[{file,"src/hashtree.erl"},{line,246}]},{riak_kv_index_hashtree,do_new_tree,3,[{file,"src/riak_kv_index_hashtree.erl"},{line,712}]},{lists,foldl,3,[{file,"lists.erl"},{line,1248}]},{riak_kv_index_hashtree,init_trees,3,[{file,"src/riak_kv_index_hashtree.erl"},{line,565}]},{riak_kv_index_hashtree,init,1,[{file,"src/riak_kv_index_hashtree.erl"},{line,308}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,304}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,239}]}]}}
2018-01-25 23:18:06.927 [info] <0.2315.0>#riak_kv_vnode:maybe_create_hashtrees:234 riak_kv/890602560248518965780370444936484965102833893376: unable to start index_hashtree: {error,{{badmatch,{error,{db_open,"IO error: lock /var/lib/riak/anti_entropy/v0/890602560248518965780370444936484965102833893376/LOCK: already held by process"}}},[{hashtree,new_segment_store,2,[{file,"src/hashtree.erl"},{line,725}]},{hashtree,new,2,[{file,"src/hashtree.erl"},{line,246}]},{riak_kv_index_hashtree,do_new_tree,3,[{file,"src/riak_kv_index_hashtree.erl"},{line,712}]},{lists,foldl,3,[{file,"lists.erl"},{line,1248}]},{riak_kv_index_hashtree,init_trees,3,[{file,"src/riak_kv_index_hashtree.erl"},{line,565}]},{riak_kv_index_hashtree,init,1,[{file,"src/riak_kv_index_hashtree.erl"},{line,308}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,304}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,239}]}]}}
2018-01-25 23:18:06.928 [error] <0.27284.0> CRASH REPORT Process <0.27284.0> with 0 neighbours exited with reason: no match of right hand value {error,{db_open,"IO error: lock /var/lib/riak/anti_entropy/v0/890602560248518965780370444936484965102833893376/LOCK: already held by process"}} in hashtree:new_segment_store/2 line 725 in gen_server:init_it/6 line 328
Any ideas on what the problem could be?

Centos sudo yum update fails

I have the following error when trying to update yum for security can someone advise a fix, i have run yum clean metadata and that didnt work i am worried about running yum clean all as this was suggested as a fix in another post as i am not sure what it does?
sudo yum update
Loaded plugins: priorities, update-motd, upgrade-helper
amzn-main/latest | 2.1 kB 00:00
amzn-updates/latest | 2.3 kB 00:00
centos | 3.7 kB 00:00
http://apt.sw.be/redhat/el5/en/x86_64/dag/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
epel/x86_64/metalink | 23 kB 00:00
epel/x86_64 | 4.3 kB 00:00
epel/x86_64/updateinfo | 736 kB 00:00
epel/x86_64/primary_db | 5.9 MB 00:00
http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
rpmforge | 1.9 kB 00:00
4028 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package aws-cli.noarch 0:1.10.46-1.40.amzn1 will be updated
---> Package aws-cli.noarch 0:1.10.56-1.41.amzn1 will be an update
---> Package compat-libtiff3.x86_64 0:3.9.4-10.13.amzn1 will be updated
---> Package compat-libtiff3.x86_64 0:3.9.4-18.14.amzn1 will be an update
---> Package curl.x86_64 0:7.40.0-8.58.amzn1 will be updated
---> Package curl.x86_64 0:7.40.0-8.59.amzn1 will be an update
---> Package dracut.noarch 0:004-336.28.amzn1 will be updated
---> Package dracut.noarch 0:004-409.31.amzn1 will be an update
http://apt.sw.be/redhat/el5/en/x86_64/dag/repodata/filelists.sqlite.bz2: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
Thanks
You should delete invalid repo file in /etc/yum.repos.d/ directory.
First detect repo file with:
# grep -l apt.sw.be /etc/yum.repos.d/
Delete invalid repo file and clean yum cache with:
# sudo yum clean all
Although AliOkan provided a valid answer, here is the reason why it fails in the first place, as I've hit the similar issue as well.
As from your trace (you actually had a ref to el5 btw, which is not maintained anymore):
http://apt.sw.be/redhat/el[5|6]/en/x86_64/dag/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
This error points to some issue with RPMForge repo, then on the official repo there's this info:
RPMforge/RepoForge status
RPMForge/RepoForge is a dead project. It is not maintained. DO NOT
USE.
See also https://github.com/repoforge/rpms/issues/375
It's not officially maintained anymore, but if needed, there are mirrors in place, see git issue above.

Chef::Exceptions::ChecksumMismatch when installing nginx-1.4.4 from source

I am having the error described here:
Chef::Exceptions::ChecksumMismatch when installing nginx-1.7.8 from source
However, that fix does not work for me.
Following the suggestions on that page, I created a shasum:
shasum -a 256 nginx-1.4.4.tar
ed744d916a19e426fd6885e14036d64156f4b6f6aca1d22a1b9307de8d46e8d3 nginx-1.4.4.tar
then I opened this file:
vi /opt/chef/cookbooks/nginx/recipes/source.rb
and I found this block:
remote_file nginx_url do
source nginx_url
checksum node['nginx']['source']['checksum']
path src_filepath
backup false
end
which I changed to this:
remote_file nginx_url do
source nginx_url
checksum 'ed744d916a19e426fd6885e14036d64156f4b6f6aca1d22a1b9307de8d46e8d3'
path src_filepath
backup false
end
but I continue to get this error:
Recipe: nginx::source
* yum_package[pcre-devel] action install (up to date)
* yum_package[openssl-devel] action install (up to date)
* remote_file[http://nginx.org/download/nginx-1.4.4.tar.gz] action create
================================================================================
Error executing action `create` on resource 'remote_file[http://nginx.org/download/nginx-1.4.4.tar.gz]'
================================================================================
Chef::Exceptions::ChecksumMismatch
----------------------------------
Checksum on resource (ed744d) does not match checksum on content (7c989a)
Resource Declaration:
---------------------
# In /opt/chef/cookbooks/nginx/recipes/source.rb
58: remote_file nginx_url do
59: source nginx_url
60: checksum 'ed744d916a19e426fd6885e14036d64156f4b6f6aca1d22a1b9307de8d46e8d3'
61: path src_filepath
62: backup false
63: end
64:
Compiled Resource:
------------------
# Declared in /opt/chef/cookbooks/nginx/recipes/source.rb:58:in `from_file'
remote_file("http://nginx.org/download/nginx-1.4.4.tar.gz") do
provider Chef::Provider::RemoteFile
action [:create]
retries 0
retry_delay 2
default_guard_interpreter :default
source ["http://nginx.org/download/nginx-1.4.4.tar.gz"]
use_etag true
use_last_modified true
declared_type :remote_file
cookbook_name :nginx
recipe_name "source"
checksum "ed744d916a19e426fd6885e14036d64156f4b6f6aca1d22a1b9307de8d46e8d3"
path "/var/chef/cache/nginx-1.4.4.tar.gz"
atomic_update true
end
Running handlers:
[2016-02-16T15:40:44+00:00] ERROR: Running exception handlers
Running handlers complete
[2016-02-16T15:40:44+00:00] ERROR: Exception handlers complete
Chef Client failed. 5 resources updated in 19 seconds
[2016-02-16T15:40:44+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2016-02-16T15:40:44+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2016-02-16T15:40:44+00:00] ERROR: remote_file[http://nginx.org/download/nginx-1.4.4.tar.gz] (nginx::source line 58) had an error: Chef::Exceptions::ChecksumMismatch: Checksum on resource (ed744d) does not match checksum on content (7c989a)
[2016-02-16T15:40:44+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
Does anyone have any advice?
I am running this inside of vagrant, on my local machine (a Mac).
It sounds like this was resolved in comments above, but for the record you need to make sure the checksum exactly the file being downloaded. This can be confusing in cases with gzip compression.
Run sha256sum command against the file and use the output as checksum. Seems like you're using md5 or sha1 hash algorithm as checksum

Resources