sparse-candle-40017
03/13/2024, 5:55 AMcareful-iron-36678
03/13/2024, 8:09 AMload database
from state.db
into <postgresql://postgres>:<passwd>@127.0.0.1:5432/postgres
with include drop, create tables, create indexes, reset sequences
set work_mem to '16MB', maintenance_work_mem to '512 MB';
Logs:
➜ ~ pgloader load_script.load
2024-03-13T03:49:59.004747-04:00 LOG pgloader version "3.6.9"
2024-03-13T03:49:59.103343-04:00 LOG Migrating from #<SQLITE-CONNECTION sqlite:///Users/jolly/state.db {700C6A4F13}>
2024-03-13T03:49:59.103466-04:00 LOG Migrating into #<PGSQL-CONNECTION <pgsql://postgres@127.0.0.1:5432/postgres> {700C6A5383}>
2024-03-13T03:49:59.254798-04:00 ERROR Error while formatting a row from "kine":
2024-03-13T03:49:59.254947-04:00 ERROR junk in string "compact_rev_key"
2024-03-13T03:49:59.256998-04:00 ERROR The value
NIL
is not of type
NUMBER
2024-03-13T03:49:59.429966-04:00 LOG report summary reset
table name errors rows bytes total time
----------------------- --------- --------- --------- --------------
fetch 0 0 0.000s
fetch meta data 0 7 0.020s
Create Schemas 0 0 0.002s
Create SQL Types 0 0 0.009s
Create tables 0 2 0.019s
Set Table OIDs 0 1 0.004s
----------------------- --------- --------- --------- --------------
kine 2 0 0.038s
----------------------- --------- --------- --------- --------------
COPY Threads Completion 0 4 0.039s
Index Build Completion 0 6 0.074s
Create Indexes 0 6 0.047s
Reset Sequences 0 1 0.049s
Primary Keys 0 1 0.005s
Create Foreign Keys 0 0 0.000s
Create Triggers 0 0 0.002s
Install Comments 0 0 0.000s
----------------------- --------- --------- --------- --------------
Total import time 2 0 0.216s
It created the table in my target database after the migration though:
postgres=# \dt public.*
List of relations
Schema | Name | Type | Owner
--------+------+-------+----------
public | kine | table | postgres
(1 row)
postgres=# select * from kine limit 10;
id | name | created | deleted | create_revision | prev_revision | lease | value | old_value
----+------+---------+---------+-----------------+---------------+-------+-------+-----------
(0 rows)
postgres=#
Hoping I can get some help! 🤞refined-autumn-58375
03/13/2024, 9:15 AMdry-country-38018
03/13/2024, 9:22 AMrefined-autumn-58375
03/13/2024, 9:25 AMfierce-translator-86983
03/13/2024, 10:13 AMmountType: 9p
mounts:
- location: "/private/var/folders/"
9p:
securityModel: mapped-xattr
cache: "mmap"
but in windows one needs to use .start file:
https://docs.rancherdesktop.io/how-to-guides/provisioning-scripts/
would someone know how to do a .start file for configuring mountType and mount in windows? Thanks in advance!!tall-hydrogen-17043
03/13/2024, 10:24 AMhelm install rancher rancher-alpha/rancher \
--namespace cattle-system \
--set hostname=rancher.xxx.internal \
--set bootstrapPassword=ZG2EhSbPVyxCkz8X \
--set ingress.tls.source=secret
--set privateCA=true
After I have done that I take my certificate that I have gotten and rename to tls.crt and tls.key and run the following command
kubectl -n cattle-system create secret tls tls-rancher-ingress \
--cert=tls.crt \
--key=tls.key
I think after this the webpage in chrome stopped saying that the site is not secure.
The last step I do is to create the tls-ca secret from a pem file.
And this is the part I am uncertain about.
I have my crt and key.
I open the crt in windows, I select the root certificate in the chain and saves it to a .crt-file.
After that I run this command to convert it to a pem file:
openssl x509 -inform der -in rancherroot.cer -out certificate.pem
But the problem is that I cannot add a cluster to rancher.
I select that I want to import a cluster.
First I try the first command in the registration-page:
kubectl apply -f <https://rancher.boliden.internal/v3/import/5tkgn64q776bwqb9cjxz9n89t4gc8dfxcn8hw9ss5c8j6jhqpjrrnh_c-m-btpnxxpg.yaml>
But since it is a private CA it fails with the message:
Unable to connect to the server: tls: failed to verify certificate: x509: certificate signed by unknown authority
So I run the second command in the registration-page:
curl --insecure -sfL <https://rancher.boliden.internal/v3/import/5tkgn64q776bwqb9cjxz9n89t4gc8dfxcn8hw9ss5c8j6jhqpjrrnh_c-m-btpnxxpg.yaml> | kubectl apply -f -
This creates the namespace and workloads.
But when examining the rancher-agent logs it keeps saying:
time="2024-03-13T10:17:39Z" level=info msg="Listening on /tmp/log.sock"
time="2024-03-13T10:17:39Z" level=info msg="Rancher agent version v2.8.2 is starting"
time="2024-03-13T10:17:39Z" level=info msg="Certificate details from <https://rancher.xxx.internal>"
time="2024-03-13T10:17:39Z" level=info msg="Certificate #0 (<https://rancher.xxx.internal>)"
time="2024-03-13T10:17:39Z" level=info msg="Subject: CN=rancher.xxx.internal,OU=IT,O=xxx AB,L=xxx,C=SE"
time="2024-03-13T10:17:39Z" level=info msg="Issuer: CN=xxx T0 Issuing CA 2,0.9.2342.19200300.100.1.25=#1307626f6c6964656e,0.9.2342.19200300.100.1.25=#1308696e7465726e616c"
time="2024-03-13T10:17:39Z" level=info msg="IsCA: false"
time="2024-03-13T10:17:39Z" level=info msg="DNS Names: [rancher.xxx.internal]"
time="2024-03-13T10:17:39Z" level=info msg="IPAddresses: <none>"
time="2024-03-13T10:17:39Z" level=info msg="NotBefore: 2024-03-06 12:31:57 +0000 UTC"
time="2024-03-13T10:17:39Z" level=info msg="NotAfter: 2025-03-06 12:31:57 +0000 UTC"
time="2024-03-13T10:17:39Z" level=info msg="SignatureAlgorithm: SHA256-RSA"
time="2024-03-13T10:17:39Z" level=info msg="PublicKeyAlgorithm: RSA"
time="2024-03-13T10:17:39Z" level=fatal msg="Certificate chain is not complete, please check if all needed intermediate certificates are included in the server certificate (in the correct order) and if the cacerts setting in Rancher either contains the correct CA certificate (in the case of using self signed certificates) or is empty (in the case of using a certificate signed by a recognized CA). Certificate information is displayed above. error: Get \"<https://rancher.boliden.internal>\": tls: failed to verify certificate: x509: certificate signed by unknown authority"
The ca certs setting in Rancher seems to be empty, see image.
Can someone please tell me what I am doing wrong?tall-london-66300
03/13/2024, 12:47 PMERROR: error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Get "<http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/info>": open //./pipe/docker_engine: The system cannot find the file specified.
I run Rancher Desktop in admin mode, which always worked. Looking at the logs and docker.log specifically, I see that no new docker instance has been started during stand. Where/how do I proceed to have the above issues resolved?steep-airplane-89460
03/13/2024, 7:39 PMlimited-pizza-33551
03/14/2024, 2:22 AMhappy-magazine-89037
03/14/2024, 5:50 AMrapid-ambulance-5993
03/14/2024, 9:00 AMcool-gpu-54244
03/14/2024, 9:34 AMcool-gpu-54244
03/14/2024, 9:35 AMcool-gpu-54244
03/14/2024, 9:35 AManonymous
03/14/2024, 11:58 AMwooden-zoo-32094
joined #general.limited-pizza-33551
03/14/2024, 12:08 PMminiature-piano-74169
03/14/2024, 1:17 PMsystemclt restart rke2-server
doesn't apply changes to the config.yaml file.
Am I missing something, is there a way to make changes to config.yaml take effect without doing a full uninstall, and re-install?
Also what do I need to do after making changes to aws tagging on a running cluster?salmon-morning-84088
03/15/2024, 12:05 PMfoo
get pods in namespace bar
across all clusters? Or does such a rule need to be added via Role and RoleBindings manually in each cluster?abundant-hair-58573
03/15/2024, 2:10 PMorange-breakfast-78817
03/15/2024, 7:46 PMnarrow-electrician-19186
03/16/2024, 8:09 AMmelodic-motorcycle-85490
03/18/2024, 12:47 AMhelm install --namespace=cattle-ui-plugin-system --timeout=10m0s --values=/home/shell/helm/values-elemental-1.3.0.yaml --version=1.3.0 --wait=true elemental-operator /home/shell/helm/elemental-1.3.0.tgz
creating 1 resource(s)
beginning wait for 1 resources with timeout of 10m0s
NAME: elemental-operator
LAST DEPLOYED: Mon Mar 18 00:38:51 2024
NAMESPACE: cattle-ui-plugin-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
---------------------------------------------------------------------
SUCCESS: helm install --namespace=cattle-ui-plugin-system --timeout=10m0s --values=/home/shell/helm/values-elemental-1.3.0.yaml --version=1.3.0 --wait=true elemental-operator /home/shell/helm/elemental-1.3.0.tgz
---------------------------------------------------------------------
but then.. nothing happens. I see a CR of uiplugins.catalog.cattle.io is created - but I don't see anything beyond this happening. The UI plugin operator logs, if relevant, are:
time="2024-03-18T00:40:42Z" level=info msg="Applying CRD <http://uiplugins.catalog.cattle.io|uiplugins.catalog.cattle.io>"
I0318 00:40:42.900504 1 leaderelection.go:248] attempting to acquire leader lease cattle-ui-plugin-system/plugin-operator-lock...
I0318 00:40:42.919803 1 leaderelection.go:258] successfully acquired lease cattle-ui-plugin-system/plugin-operator-lock
time="2024-03-18T00:40:43Z" level=info msg="All controllers have been started"
time="2024-03-18T00:40:43Z" level=info msg="Starting <http://catalog.cattle.io/v1|catalog.cattle.io/v1>, Kind=UIPlugin controller"
limited-pizza-33551
03/18/2024, 1:30 AMloud-mechanic-37127
03/18/2024, 6:52 AMrkecontrolplane was already initialized but no etcd machines exist that have plans, indicating the etcd plane has been entirely replaced. Restoration from etcd snapshot is required.
Not sure that how to resolved this kind of problem. Thank you.loud-mechanic-37127
03/18/2024, 6:58 AMsquare-insurance-96134
03/18/2024, 7:34 AMbulky-potato-22114
03/18/2024, 9:37 AM2024-03-18T09:30:40.391Z: Registered distributions: Ubuntu,rancher-desktop,rancher-desktop-data
2024-03-18T09:30:40.969Z: Registered distributions:
2024-03-18T09:30:41.281Z: WSL failed to execute wsl.exe --import rancher-desktop C:\Users\user.Name\AppData\Local\rancher-desktop\distro C:\Program Files\Rancher Desktop\resources\resources\win32\distro-0.55.tar --version 2: Error: wsl.exe exited with code 4294967295
executing the command my self gives:
Import in progress, this may take a few minutes.
A distribution with the supplied name already exists.
Error code: Wsl/Service/0x800700b7
but i noticed that the command requires " around the tar filename... cause it has space in the path namefresh-hydrogen-62807
03/18/2024, 10:00 AMAuthentication test failed, please check your credentials
brave-van-86625
03/18/2024, 4:37 PM