Odi's astoundingly incomplete notes

These are the syscalls caused by Java's mapped byte buffers:

FileChannel fc = FileChannel.open(f.toPath(), StandardOpenOption.READ, StandardOpenOption.WRITE);
// mmap(NULL, 2147483647, PROT_READ|PROT_WRITE, MAP_SHARED, 4, 0)
MappedByteBuffer buf = fc.map(MapMode.READ_WRITE, 0, Integer.MAX_VALUE);
// madvise(0x7f4294000000, 2147483647, MADV_WILLNEED) = 0
buf.load();

When the buffer is garbage collected the munmap call happens.
posted on 2019-09-11 11:30 UTC in Code | 0 comments | permalink

Perform the migration on an existing SonarQube installation. You can not do it at the same time as upgrading to a newer SonarQube version!

1. Create an emtpy Postgresql DB (no password is used here, depending on settings in pg_hba.conf):

psql -U postgres
create user sonar;
create database sonarqube owner sonar;

2. Change the DB connection of the existing SonarQube installation in sonar.properties:

sonar.jdbc.username=sonar
#sonar.jdbc.password=
sonar.jdbc.url=jdbc:postgresql://localhost/sonarqube?currentSchema=public

3. Start up the SonarQube instance so that it creates the DB schema in Postgresql.

4. Shut down the SonarQube instance again for migration.

5. Delete the sonar/data/es6/nodes folder.

4. Run the mysql-migrator utility.

5. Startup the SonarQube instance again.

6. If you want to update to a newer SonarQube version then do that now.


posted on 2019-08-15 09:47 UTC in Code | 0 comments | permalink

In case you wonder how Java NIO uses epoll under Linux:

• The Selector allocates an epoll file descriptor and two FDs (a pipe) for timeout/wakeup. Failing to close the Selector will leak those.
• It uses epoll as level-triggered interface (no EPOLLET)
• It is important to remove a selected key from the Selector's selectedKeys Set. Only then the next select() call will reset its readyOps.

posted on 2019-06-19 09:36 UTC in Code | 0 comments | permalink

With Java 8 the atomic primitives have gained a very useful function: getAndUpdate(). It takes a lamda function to atomically update the value. This simplifies previous complicated code that used compareAndSet in a loop into a one-liner.

As an example look at a piece of code that is used to keep track of a maximum value.

private AtomicInteger max = new AtomicInteger();

public void oldSample(int v) {
  int old;
  do {
      old = c.get();
  } while (!c.compareAndSet(old, Math.max(old, v)));
}

public void newSample(int v) {
  max.getAndUpdate(old -> Math.max(old, v));
}

posted on 2019-05-21 09:45 UTC in Code | 0 comments | permalink

I see sites often disable caching of resources completely with really bad headers like:

Cache-Control: no-store, no-cache, must-revalidate
Expires: Wed, 4 Jun 1980 06:02:09 GMT
Pragma: nocache

It makes a lot more sense to let the client cache and tell it to check if the resource has been modified in the mean time. The easiest way to do that is to pass the Last-Modified header together with:

Cache-Control: max-age=0, must-revalidate

This will enable caching in the browser and the browser will request the resource with the If-Modified-Since header. The server will respond with 304 Not Modified if the resource's last-modified date is still the same, saving the transfer. If you need more control over the content of the resource and a last-modified date is not enough or can not easily be given, you can set the ETag header. ETag is a hash or version number of the content and changes as the resource's content changes. But careful: ETag may change with the Content-Encoding (compression). Carefully test if it behaves correctly with your gateway (reverse proxy).

Maybe this practice comes from bad defaults in Apache. I have not seen any default Apache config that sets sensible Cache-Control. Therefore no header is sent and browsers cache such responses forever, not even clicking the Reload button will fetch it again. This of course makes developers take the simple but radical option to disable caching.

A much better default for Apache is:

Header set Cache-Control "max-age=0, must-revalidate"

posted on 2019-05-06 11:02 UTC in Code | 0 comments | permalink

After running some updates I noticed that sshd (including active sessions) were somehow killed sometimes. After much debugging I found the reason: udev and cgroups. It looks like udev can send kill signals to all members of its cgroup if it thinks that it's a systemd system. But on OpenRC systems that just does a lot of harm.

That udev triggering happens for example during:

• grub-install
• startup of qemu with kvm

The problem occurs after restarting udev with: /etc/init.d/udev -D restart. The culplrit being the -D flag. The flag causes cgroups to be not set. So udev ends up in the main cgroup!

Note the absent udev directory under /sys/fs/cgroup/openrc

This also explains why the problem is fixed by a reboot.

I have filed a bug against OpenRC.


posted on 2019-04-08 08:37 UTC in Code | 0 comments | permalink

iptables -t mangle -A INPUT -i eth0 -d 255.255.255.255 -j TEE --gateway 10.1.1.255

The above iptables rule copies broadcast traffic received on the eth0 network interface to another network interface (the one whose broadcast address is 10.1.1.255). Note that this is one-way only. We can't add a second rule for the other direction without creating an infinite packet loop. We need to play tricks with the TTL for that!

Incoming broadcast packets typically have a TTL of 64 or 128. TEE uses the kernel function nf_dup_ipv4() to copy the packet, which already decrements the TTL if the rule is in INPUT or PREROUTING. Note that a packet with TTL=0 will still be accepted by the destination, but will no longer be routed. But TEE itself does not check for TTL=0 and happily copies such packets. So we need to prevent that too, since what we do is effectively routing.

The improved rule adds TTL sanity check:

iptables -t mangle -A INPUT -i eth0 -d 255.255.255.255 -m ttl --ttl-gt 0 -j TEE --gateway 10.1.1.255

If we want to add a rule for the other direction as well...

iptables -t mangle -A INPUT -i eth1 -d 255.255.255.255 -m ttl --ttl-gt 0 -j TEE --gateway 10.1.0.255

then we easily create a packet loop, since the copy of a packet on eth0 will now also match the rule on eth1. To prevent that we need to ensure that the copied packet has TTL=0. We can do that by simply setting the TTL=1 of all incoming broadcasts before passing them to TEE. Then no more loops should occur. The complete rule set for merging a broadcast domain across networks is then:

iptables -t mangle -A INPUT -i eth0 -d 255.255.255.255 -m ttl --ttl-gt 0 -j TTL --ttl-set 1
iptables -t mangle -A INPUT -i eth1 -d 255.255.255.255 -m ttl --ttl-gt 0 -j TTL --ttl-set 1
iptables -t mangle -A INPUT -i eth0 -d 255.255.255.255 -m ttl --ttl-gt 0 -j TEE --gateway 10.1.1.255
iptables -t mangle -A INPUT -i eth1 -d 255.255.255.255 -m ttl --ttl-gt 0 -j TEE --gateway 10.1.0.255

Make sure to monitor your broadcast traffic to detect any misconfiguration after that change:

tcpdump -vnpi eth0 ip broadcast

posted on 2018-12-18 18:36 UTC in Code | 0 comments | permalink

Add Unix groups to CUPS:
/etc/cups/cups-files:

SystemGroup lpadmin root

Set permissions to access the local secret:

chgrp -R lpadmin /run/cups/certs

This directory contains a secret that is read by CUPS utilities like cupsenable. They pass that secret in HTTP Authorization headers to the local HTTP socket when sending command.

Add your user to that group:

usermod -a -G lpadmin myuser

posted on 2018-10-29 15:48 UTC in Code | 0 comments | permalink

Be careful when doing something stupid!

CNAME records are useful. Especially together with external hosting services.
You run your domain and control DNS yourself but you host a website on an external service. They manage the IP of that site and give you a name that may look like examplesite383.hostingprovider.biz and already points to the correct IP. You want to map it into your DNS zone with a nice name like www.fancyproduct.com so creating a CNAME that points tha name www to your hosting provider's name is a practical way to go. You also want to do the same without the www prefix, but mind you! Creating a CNAME for fancyproduct.com would redirect the complete zone to a different one!

Never create a CNAME record for the zone name!

Also when caches start picking up the SOA information of the wrong zone, they apply the TTL values of that zone. So getting control of your zone back may not be easy and is not under your control anymore.

Also any secondary DNS server will pickup the zone redirect and may completely stop updating the zone from your authorative server. You need to manually fix that on the secondary DNS!

posted on 2018-10-02 10:01 UTC in Code | 0 comments | permalink

If your Oracle database does not register with the listener, you get ORA-12505. Normally the DB registeres automatically after a while. But you can force it to do that.

As SYS:

ALTER SYSTEM REGISTER;

However, if it did not register automatically, chances are that this does not help either.

Check the listener status:

lsnrctl status

Check the listener's log file (filename is in the status output).

Check which listener the DB wants to register with:

select name, value from v$parameter where name in ('local_listener', 'remote_listener');

This gives you a TNS name. Check that this TNS name is defined in $ORACLE_HOME/network/admin/tnsnames.ora Such an entry looks like:

LISTENER_SID = (ADDRESS = (PROTOCOL = TCP)(HOST = oracle.example.com)(PORT = 1521))

posted on 2018-09-12 15:09 UTC in Code | 0 comments | permalink