To reload a running prometheus instance configuration without stopping and starting use the following to make prometheus reload the configuration file:
killall -HUP prometheusReload running prometheus configuration
Reply
Convert epub file to pdf in Linux CLI
If you would like to convert an epub file to pdf in Linux, you can use calibre.
First install it using
sudo apt-get install calibreand then you should be able to use it to convert the file like
ebook-convert file.epub file.pdfKey is stored in legacy trusted.gpg keyring
As described in the post [here](https://itsfoss.com/key-is-stored-in-legacy-trusted-gpg/) you would need to export the key to its own file under the trusted.gpg.d directory.
So for example if the warning is for something like forticlient, first find the key using sudo apt-key gpg list and then taking the last eight characters and removing the space, export the key to its file (ie forticlient.gpg)
sudo apt-key export 5E54716D | sudo gpg --dearmour -o /etc/apt/trusted.gpg.d/forticlient.gpg
client version 1.43 is too new. Maximum supported API version is 1.41
Problem
Trying to use the Docker API to create/stop/delete a container gives the error
client version 1.43 is too new. Maximum supported API version is 1.41
Solution
Use the following
export DOCKER_API_VERSION=1.41
as described here
Linux sort files by human readable size
To sort the files in a directory use the following
du -sh -- * | sort -hTaken from https://unix.stackexchange.com/a/4682
gunzip, k8up, ‘unexpected end of file’
Problem
When using the k8up annotations for a postgresql backup with :
k8up.io/backupcommand: /bin/bash -c 'pg_dumpall --clean | gzip --stdout
do not finish correctly, and as a result the gunzip complains about "unexpected end of file"
Solution
There is a workaround by first saving the file and then sending it to the standard output with
k8up.io/backupcommand: /bin/bash -c 'pg_dumpall --clean | gzip -c > /tmp/backup.gz
&& cat /tmp/backup.gz && rm /tmp/backup.gz'Thanks Simon Beck for the suggestion https://community.appuio.ch/channel/k8up/thread/j8AcG6ZjgGbQAzth5?msg=xgTanRqqJbBkNj9sd
PostgreSQL upgrading from 9.6 to 15.3 has authentication failed (PG::ConnectionBad)
After upgrading a PostgreSQL instance from version 9.6 to the currently latest version 15.3, your application cannot connect to the server, giving an authentication error even if the user/password used is still the same.
This seems to be the result of a change in the method used in the pg_hba.conf file.
Version 9.6 uses md5 but version 15.3 uses scram-sha-256
Changing this in the file pg_hba.conf file from scram-sha-256 to md5 and reloading the configuration file from inside the database with select pg_reload_conf(); , results in the application being able to connect to the database server again.
Update: It is possible to use the recommended scram-sha-256 hash, by doing the following:
- Uncomment the line with
#password_encryption = scram-sha-256 # scram-sha-256 or md5in file/var/lib/postgresql/data/pgdata/postgresql.conf - reload the configuration in the database
select pg_reload_conf(); - recreate the password with the new encryption
production=# alter user user_name with password 'password';
Downloading gitlab database backup from s3
You want to download a copy of your gitlab backup (ie when upgrading to version 7.0.0 as described in [here](https://docs.gitlab.com/charts/installation/database_upgrade.html#steps-for-upgrading-the-bundled-postgresql) ).
Login to the toolbox pod and get the credentials file for s3
cat /etc/gitlab/.s3cfg
Create a new file locally (ie ~/.s3cfg_gitlab) and then download the file locally with
s3cmd get s3://gitlab-backups/database_upgrade_6_gitlab_backup.tar 20230531_gitlab_backup.tar -c ~/.s3cfg_gitlabValidating yaml to json conversion
When using yaml to json conversion as it happens when using Terraform’s helm provider with a helm chart’s values.yaml file, it won’t be possible to check and get any useful validation errors, even when your terraform plan is run.
In order to check before running your plan or if you have any errors you can use yq passing as below using the values.yaml file
yq -p yaml -o json values.yamlDisplaying postgresql query results as a table
To display the results of a postgresql query as a table (in the example postgresql runs as a docker container locally) use something like the following
psql -h localhost -p 5555 -U postgres database_name -xc 'select * from table_name where id=29'