← Back to team overview

ubuntu-389-directory-server team mailing list archive

seemingly unrelated 389-admin sigsegv.


Occured running tonight's packages of 389 from precise.
Here's the strace output, relevant sections.  Attached is the entire thing.

The procedure to reproduce is simple yet time consuming.
1) Install oneiric ocelot using vmbuilder.
master@ichigo:~$ cat ~/.vmbuilder.cfg
flavour = virtual
arch = amd64
suite = oneiric
arch = amd64
components = main, restricted, universe, multiverse
flavour = virtual
addpkg = aptitude, acpid, htop, byobu, vim, python-software-properties, unattended-upgrades, openssh-server, openssl-blacklist, openssl-blacklist-extra, openssh-blacklist, openssh-blacklist-extra
bridge = br0
arch = amd64
libvirt = qemu:///system

2) Upgrade to precise pangolin: https://wiki.ubuntu.com/PrecisePangolin/TechnicalOverview/Alpha1#Upgrading_from_Ubuntu_11.10
3) Install 389.
sudo apt-add-repository ppa:ubuntu-389-directory-server/ppa
sudo aptitude update
sudo aptitude install 389-ds-base 389-admin apache2
sudo -e /etc/sysctl.d/10-network-timeout.conf
cat /etc/sysctl.d/10-network-timeout.conf
net.ipv4.tcp_keepalive_time = 60
sudo setup-ds-admin
When prompted to specify an existing management server, do so. Make sure it's an existing WORKING management server. 4) Crash! It occurs at the end of the setup script, and subsequently when running sudo start-ds-admin .

Attachment: strace.txt.gz
Description: GNU Zip compressed data