Find the InfluxDB configuration file in /etc/influxdb/influxdb.conf and adjust the following line:
# Determines whether HTTP request logging is enabled.
log-enabled = false
My personal knowledge base, online.
Find the InfluxDB configuration file in /etc/influxdb/influxdb.conf and adjust the following line:
# Determines whether HTTP request logging is enabled.
log-enabled = false
If you echo nothing to a file, it will clear the content to empty it. Just using sudo will not work, you need to be root!
sudo su
echo "" > logfile
To configure a fixed IP address on the HUE bridge, you need to browse to the bridge using:
http://x.x.x.x/api/[bridge-user]/config
Use a HTTP PUT command to configure the IP address and use as body:
{ "ipaddress":"[new-ip]", "dhcp":false, "netmask": "[network-netmask]", "gateway": "[network-gateway]" }
Alternatively, you can use the HUE app and change the network settings in the bridge configuration.
Stop running containers using docker-compose and remove the containers.
docker-compose stop
docker rm docker_nginx_1
docker rm docker_connectivity_1
docker rm docker_gateway_1
docker rm docker_things_1
docker rm docker_concierge_1
docker rm docker_things-search_1
docker rm docker_policies_1
docker rm docker_mongodb_1
docker rm docker_swagger-ui_1
docker system prune -a
Download the latest Ditto zip from Github and re-run docker-compose.yaml.
This folder contains an example docker-compose.yml
which can be used to start Eclipse Ditto with its backing Database – MongoDB – and a reverse proxy – nginx – in front of the HTTP and WebSocket API.
Source: https://github.com/eclipse/ditto/blob/master/deployment/docker/README.md
The nginx’s configuration is located in the nginx.conf
file and contains a “Basic authentication” for accessing the HTTP and WebSocket API. The users for this sample authentication are configured in the nginx.httpasswd
file also located in this directory.
In order to add a new entry to this file, use the “openssl passwd” tool to create a hashed password:
openssl passwd -quiet
Password: <enter password>
Verifying - Password: <enter password>
Append the printed hash in the nginx.httpasswd
file placing the username who shall receive this password in front like this:
ditto:A6BgmB8IEtPTs
You may configure each service via passing variables to the java VM in the entrypoint section for each service.
...
# Alternative approach for configuration of the service
command: java -Dditto.gateway.authentication.devops.password=foobar -jar starter.jar
To get a list of available configuration options you may retrieve them from a running instance via:
# Substitute gateway with the service you are interested in
curl http://devops:foobar@localhost:8080/devops/config/gateway/?path=ditto
Or by going through the configuration files in this repository e.g. /services/gateway/starter/src/main/resources/gateway.conf.
docker-compose up -d
Check the logs after starting up:
docker-compose logs -f
docker-compose down
Create a folder, for example /app/dotnet6, and assign ownership to the right user:
sudo mkdir /app/dotnet6
sudo chown -R pi /app/
Download the .NET 6 SDK at Microsoft:
wget https://download.visualstudio.microsoft.com/download/pr/adcd9310-5072-4179-9b8b-16563b897995/15a7595966f488c74909e4a9273c0e24/dotnet-sdk-6.0.100-linux-arm64.tar.gz
Extract the tar.gz file in the /app/dotnet6 directory:
sudo tar zxf dotnet-sdk-6.0.100-linux-arm64.tar.gz -C /app/dotnet6
Test the .NET6 installation by browsing to the installation directory and execute the dotnet –info command:
cd /app/dotnet6
./dotnet --info
.NET SDK (reflecting any global.json):
Version: 5.0.101
Commit: d05174dc5a
Runtime Environment:
OS Name: debian
OS Version: 10
OS Platform: Linux
RID: debian.10-arm64
Base Path: /app/dotnet/sdk/5.0.101/
Host (useful for support):
Version: 5.0.1
Commit: b02e13abab
.NET SDKs installed:
5.0.101 [/app/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 5.0.1 [/app/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 5.0.1 [/app/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-download
Locate php.ini. For Debian this file is located in:
/etc/php/7.4/apache2
Search for the following configuration lines (in nano use CTRL+W for search) and replace the existing configuration values with acceptable values.
max_execution_time = 60
memory_limit = 128M
post_max_size = 64M
upload_max_filesize = 64M
max_input_time = 60
file_uploads = On
safe_mode = Off
Locate .htaccess file in the root of your wordpress directory and add or adjust:
php_value upload_max_filesize 64M
php_value post_max_size 128M
php_value memory_limit 256M
php_value max_execution_time 300
php_value max_input_time 300
When you open the media library in WordPress and try to upload a file it should reflect the maximum configured upload file size:
Source: https://www.mindtheproduct.com/mtp-panel-defining-your-okrs-in-2022/
OKRs: the essence of what we do, building metrics, achieving outcomes.
What are the foundational steps of building good OKRs?
Prerequisite: psychological safety and a real vision: where are we going? Understanding where you are as an organisation helps. The organisation needs to be comfortable with metrics.
The reason we are doing OKRs is alignment: we want to work towards the same goal and everyone needs to have the same expectations.
Use SMART: Specific, Measurable, Actionable, Relevance, Time-bound. Focus on outcomes over outputs. Focus on positive change.
If you’re spending less than 50% of your time on achieving the objectives then you should ask what the goal of using OKR is? If you didn’t work on the objective, it might not be the most important objective to achieve. Does the priority fit?
Here is what I want to do to achieve this objective.
Upgrading InfluxDB failed. For some reason the update caused permission issues with the start-up script:
usr/lib/influxdb/scripts/influxd-systemd-start.sh
When I gave this file permission to execute the InfluxDB service started again:
chmod +x /usr/lib/influxdb/scripts/influxd-systemd-start.sh
Then, the next problem appeared: systemctl didn’t recognise that the service was actually running: it was stuck in the state “activating”. Then I found an article on serverfault that described my problem.
I’m running InfluxDB on Debian so couldn’t apply the suggestion solution, but needed to interpret this a bit. I edited the file:
/etc/systemd/system/influxd.service
I changed the type to simple, as indicated in this code sample:
[Unit]
Description=InfluxDB is an open-source, distributed, time series database
Documentation=https://docs.influxdata.com/influxdb/
After=network-online.target
[Service]
User=influxdb
Group=influxdb
LimitNOFILE=65536
EnvironmentFile=-/etc/default/influxdb
ExecStart=/usr/lib/influxdb/scripts/influxd-systemd-start.sh
KillMode=control-group
Restart=on-failure
Type=simple
PIDFile=/var/lib/influxdb/influxd.pid
[Install]
WantedBy=multi-user.target
Alias=influxd.service
The QWIC Performance RD 11 speed is not just a normal e-bike. It’s a real monster! Push it and it tops out at ~45km/h (~28mph).
The distance between my home and work is, by bike, roughly 25km. By car, it takes me 25 minutes to get to the office. When I get back from work, I go running or work out a bit. Effectively, I’m spending 25 minutes to get to the office, 25 minutes to get back, and an additional 45 minutes or so to work out and de-stress from work. I was already looking at these bikes (speed pedelecs) for a while and knew their capabilities. Let’s take the mathematical approach: 25km with an average of, let’s say, 40km/h, would take me 37 minutes. Let’s round that up to 45 minutes. A round trip would cost me 90 minutes, roughly the same as my round trip with the car and de-stress session afterwards. This seems to be the perfect opportunity to reduce my impact on the climate and keep moving without spending additional time.
Let’s have a look at the options in the market. Stromer is the Mercedes Benz of the speed pedelecs. My first test drive on a speed pedelec was on a Stomer ST3.
That first experience: WOW! This thing is crazy fast… But then I started looking at prices. The Stromer ST3 starts at ~7000 EUR and, including the large battery pack, seat suspension, and suspension fork, goes up to 8665 EUR. This does not include insurance or other accessories, for example, a helmet or glasses. That was a bit more than I was hoping for.
QWIC produces three types of speed pedelecs:
My first test-drive was on an MA11. Compared to the Stromer ST3 it was a bit of a disappointment: it wasn’t as snappy and I struggled reaching 45km/h. Doing a bit of background research this seems to be a known “issue” with mid-engined speed pedelecs: they do not feel as powerful as their rear-engined counter parts. Looking back, this could’ve also been related to a combination of the bike configuration and the cold windy weather at the day I made this test-drive. I recommend you to experience the difference between a mid-engined and rear-engined bike yourself.
Unfortunately, I couldn’t find a local dealer that an RD11 on stock for a test-drive. I figured out that QWIC build a showroom near Amsterdam. I reached out to them and I made an appointment to try the RD11.
This experience felt totally different compared to the MA11: it felt like the Stromer! I only managed to reach 27km in roughly one hour, which was not really impressive. However, the battery wasn’t fully charged and I experienced a very strong head-wind. All things considered, this was a very positive experience! Now I just had to find a local dealer.
Next step: finding a dealer. I asked a couple of dealers to make an offer and decided to have a chat with Fietsenmaker Venlo. The prices where, more or less, the same.
After some discussions I returned home with a really positive feeling. The owner seemed to have a lot of experience with QWIC e-bikes. Even though this would be the first speed-pedelec he would sell, I was confident this was the right dealer. In the end we agreed on a full package price, including helmet, glasses, security lock, 735wh battery, display, and additional charger (so I can leave one charger behind at the office). Total price: ~4500 EUR. On top, I selected an ENRA speed-pedelec insurance (link refers to Dutch website) that would set me back roughly 200 EUR/year.
I own the bike now for almost six full weeks, and I really enjoy the daily ride! In the first weeks it was making some squeaky noises, but a quick check-up at the dealer solved those problems. This seemed to be normal after using it for roughly 500km. The gallery below shows some pictures of the bike after using it for 800km and some rain. The orange colour looks really cool in my opinion!
It takes me roughly 45 minutes to travel 27-30km, depending on the wind speed. An average of 37km/h is doable. My record is 30km at 45:13 with an average speed of 39.2km/h and a top speed of 56.9km/h (which I’m not sure is correct).
The battery performs as expected: on an average drive (one way) it consumes between 60-70% of its capacity. This gives me some room for the colder autumn and winter, and some degradation over the next couple of years. This is something I should keep an eye on over the next couple months.
Today, one of my virtual systems ran out of disk space. To find the root cause I needed to find the directory that was filling up. Using the right parameters, the du command returns a list of directories and their disk space consumption.
du -hc --max-depth=0 /var
For example:
root@DB152:/# du -hc --max-depth 1 /var
704K /var/tmp
4.0K /var/mail
23M /var/log
1.1M /var/backups
4.0K /var/local
3.2G /var/lib
20K /var/spool
734M /var/cache
4.0K /var/opt
3.9G /var
3.9G total
Removing files of a certain type recursively:
find . -name "*json.log" -type f -delete
Clearing (system) log files:
truncate /var/log/* --size 0