Public bug reported:
Binary package hint: bind9-host
root@net1:/etc# strace -e open host foo 2>&1 | grep /etc
open("/etc/ld.so.cache", O_RDONLY) = 3
open("/etc/resolv.conf", O_RDONLY) = 6
No attempt to access /etc/host.conf or /etc/nsswitch.conf so all commands
(host, dig, etc.) hang
root@net1# ldd /usr/bin/host | grep libreso
libresolv.so.2 => /lib/libresolv.so.2 (0x7f9ad8d3)
** Summary changed:
- Ubuntu 10.10 host command ignores all conf files
+ Ubuntu 10.10 /etc/hosts ignored by resolv.so
** Summary changed:
- Ubuntu 10.10 /etc/hosts ignored by resolv.s
root@net1# strings /lib/libresolv.so.2 | grep /etc
/etc/hosts
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
https://bugs.launchpad.net/bugs/736149
Title:
Ubuntu 10.10 /etc/hosts ignored by /lib/resolv.so.2
--
Ubu
ping works as expected...
root@net1# strace -e open /bin/ping localhost 2>&1
open("/etc/ld.so.cache", O_RDONLY) = 3
open("/lib/libc.so.6", O_RDONLY)= 3
open("/etc/resolv.conf", O_RDONLY) = 4
open("/etc/resolv.conf", O_RDONLY) = 4
open("/etc/nsswitch.conf", O_RDONLY)= 4
o
Geez this is ugly. If that's the way it is, then I'll just write a
replacement for host to work sensibly.
If this is the designed behavior of the host command, then host will
hang anytime DNS is stopped.
Very bad.
--
You received this bug notification because you are a member of Ubuntu
Server T
This problem has lingered for a year.
Same problem presents in all PHP versions from Tahr to Vivid.
net4-dev# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 15.04
Release:15.04
Codename: vivid
net4-dev# pear install Archive_Tar
Warning:
Public bug reported:
This is a huge problem.
After several iterations of - service mysql {start|stop|restart} - the
mysql service becomes broken + unrecoverable.
The problem becomes - service mysql stop - hangs forever, upon
attempting...
exec systemctl stop mysql.service
What's required
Redneckery to allow reboots till this bug fixed don't work because
apparently systemctl is seriously brain dead.
So the normal shut magic won't work...
echo 'mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf shutdown' >
/etc/rc6.d/K00-msyql-stop
chmod +x /etc/rc6.d/K00-msyql-stop
Will upda
apport-collect 1468804 does not seem to work correctly on headless
(server) systems.
Gets into some infinite loop with lynx or whatever tool is running.
ovhfine# uname -a
Linux fine.bizcooker.com 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
ovhfine
This doesn't work either...
echo 'mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf shutdown' >
/etc/init.d/mysql-hard-stop
ln -s /etc/init.d/mysql-hard-stop /etc/rc0.d/K01-aaa-mysql-hard-stop
ln -s /etc/init.d/mysql-hard-stop /etc/rc6.d/K01-aaa-mysql-hard-stop
--
You received this bug not
Changing the /etc/rc{016}.d/K01mysql scripts to do mysqladmin shutdown
doesn't work, because inotifywait shows these files are never touched at
shutdown.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.
dirwatch /etc | grep OPEN | egrep 'init.d|rc' shows that shutdown
scripts are no longer run sensibly either.
The K01mysql script never runs, so likely there's some other shutdown
script with a dependency which is touching mysql + hanging before the
K01mysql runs.
--
You received this bug notific
Using inotifywait, reboot sequence is very odd...
ovhfine# inotifywait -mr -e OPEN /etc | egrep 'init.d|rc'
Setting up watches. Beware: since -r was given, this may take a while!
Watches established.
/etc/init.d/ OPEN rng-tools
/etc/init.d/ OPEN rng-tools
/etc/init.d/ OPEN ntp
/etc/init.d/ OPEN n
Nothing related shows up in /var/log/syslog at reboot either...
Jun 25 12:03:54 fine systemd[1]: Deactivating swap /dev/sdb3...
Jun 25 12:03:54 fine systemd[1]: Starting Unattended Upgrades...
Jun 25 12:03:54 fine systemd[1]: Deactivating swap /dev/sda3...
Jun 25 12:03:54 fine systemd[1]: Stopped
There is no easy fix to deal with systemd problems.
Other physical servers with Vivid + mysql or mariadb have worse
problems.
After a number of starts/stops, mysql simply won't start. There is no
debug info anywhere.
/var/log/syslog is quiet... Crickets...
Downgrading back to Utopic, as this ap
Steps to reproduce.
1) install fresh copy of Vivid
2) apt-get -yqq install mysql-server libmysqlclient-dev
3) reboot + system hangs forever (because mysql can't seem to be stopped
in all cases by systemd)
4) In another shell - mysqladmin shutdown - allows reboot continues
5) Also - service mys
This failure occurs consistently on every installation of Vivid.
Downgrading to Utopic, which avoids use of systemd, fixes problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/14
I've removed the patch tag + removed the patch file as LXC already has
this bug open + fix will likely come from there.
** Tags removed: patch
** Patch removed: "Unified diff patch file"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471358/+attachment/4424582/+files/lxc-checkconfig.pa
Problem still persists after latest systemd updates.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1468804
Title:
mysql stop/restart fails + breaking mysql + reboots
To manage notifi
Cleanest fix is to downgrade to Utopic, as systemd also fails for many
other services like Apache + fail2ban.
If running Vivid is a required, this hack seems to correctly top +
restart MySQL.
alias mysql-stop='mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf
shutdown'
alias mysql-start='se
IMHO, systemd seems to be the root of all evil.
touch /etc/dnsmasq.conf has no effect.
net4-dev# systemctl restart lxc-net
net4-dev# systemctl status lxc-net
● lxc-net.service - LXC network bridge setup
Loaded: loaded (/lib/systemd/system/lxc-net.service; enabled; vendor preset:
enabled)
A
Okay, a simple fix that seems to work (at least in my case), is to
comment out the first two guards in the stop function.
So...
#[ "x$USE_LXC_BRIDGE" = "xtrue" ] || { exit 0; }
#[ -f "${varrun}/network_up" ] || { exit 0; }
Once these are skipped, the code seems to work.
--
You received this bu
Oh... and - touch /etc/dnsmasq.conf - is still required, so this is
another bug to be fixed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1452601
Title:
vivid container's networking.s
Oh, I see...
I was using OOM as an example. I this case, it appears the missing
/etc/dnsmasq.conf file might be the culprit.
So first start of lxc-net, dnsmasq never starts.
After that, it will never start, unless a hard reboot is done.
--
You received this bug notification because you are a m
I had to remove both lines, in my case.
And this is likely a less than correct fix. I'm under the gun to get a
client machine I'm hosting setup to run many of their sites in LXC
containers, so time I invested looking at this fix was minimal.
Likely the entire stop function is best revisited, to a
Just setting up a fresh Vivid LXC host machine + I was incorrect above.
There's no requirement for /etc/dnsmasq.conf to exist for lxc-net to
start correctly.
There is a requirement though for /etc/resolv.conf to reference at least
one valid name server.
--
You received this bug notification bec
This is a horrible bug + best be fixed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1468804
Title:
mysql stop/restart fails + breaking mysql + reboots
To manage notifications about
Bug still persists.
http://askubuntu.com/questions/615129/systemd-mysql-wont-stop provides
one solution + this is ugly.
Normal mysql should correctly stop itself, without hacking an etc
systemd service override.
--
You received this bug notification because you are a member of Ubuntu
Server Tea
Having bind use .d mechanism seems like the cleanest way to handle this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
To manage not
Public bug reported:
net3# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.10
Release:14.10
Codename: utopic
Different than
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/669005 which has
to do with php5-curl. I deinstalled php5-
>From /var/log/apache2/error.log
[Sun Feb 01 11:39:32.464302 2015] [mpm_prefork:notice] [pid 14428] AH00171:
Graceful restart requested, doing restart
[Sun Feb 01 11:39:32.475487 2015] [core:trace3] [pid 14428] core.c(3051):
Setting LogLevel for all modules to trace8
[Sun Feb 01 11:39:32.502279
Have narrowed problem down to a php module.
a2dismod php5 + restart + reload works, so now onto figuring out which
php5 module is culprit, using apt-get purge on each ph5 module, to
ensure all traces of related module cruft is removed.
--
You received this bug notification because you are a memb
Problem module is php5-librdf, so someone please update this bug report
with how to collect a core dump + I'll attach the data for this bug.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launch
Oh... Maybe the problem is lxcbr0 is up'ed before named starts.
Then if named listens on 0.0.0.0 makes sense it would glom onto the
lxcbr0 address too.
I'll modify named's config files + reboot + see if this fixes the
problem.
--
You received this bug notification because you are a member of Ub
Public bug reported:
This is a clean Vivid install (rather than upgrade).
Maybe I munged something + for the life of me nothing comes to mind.
/var/log/syslog shows somehow bind is polluted with dnsmasq addresses?
All packages updated.
net8-rmt# lsb_release -a
No LSB modules are available.
Dis
Adding the following to /etc/named/named.conf.options seems to have
fixed this problem:
listen-on { 127.0.0.1; 167.114.159.29; };
This seems like a bug to me. Maybe switching to systemd created a subtle
change in order of network config + named + lxc-net start.
This is the first time I've had to
This does appear to relate to initial installs + some type of ordering
change, of how services start.
All other machines I manage had updates, rather than fresh installs +
all the updated machines work.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which i
Public bug reported:
Nothing shown via journalctl -k -b | grep bootchart after boot.
/var/log/bootchart does exist + is empty after boot.
net8-rmt# uname -a
Linux ns515383.ip-167-114-159.net 3.19.0-18-generic #18-Ubuntu SMP Tue May 19
18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
net8-rm
I'd have thought /etc/default/grub should have some directive about
bootchart + there is none.
Maybe this is the problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1458170
Title:
Removed + Reinstalled...
Looks like all's well...
net8-rmt# apt-get install bootchart
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
bootchart
0 upgraded, 1 newly installed, 0 to remove and 0 not upgr
This looks suspicious...
net8-rmt# service bootstart start
Failed to start bootstart.service: Unit bootstart.service failed to load: No
such file or directory.
net8-rmt# systemctl restart bootstart.service
Failed to restart bootstart.service: Unit bootstart.service failed to load: No
such file
lxc-autostart after boot works.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1458173
Title:
Vivid + LXC autostart not working
To manage notifications about this bug go to:
https://bu
Public bug reported:
In previous Ubuntu versions + current Ubuntu docs, boot time autostart
is accomplished by:
1) setting /etc/default/lxc LXC_AUTO="false"
2) adding lxc.start.auto = 1 to config of containers to be started at
boot time
This no longer works.
___
net8-rmt# uname -a
Linux ns
Public bug reported:
The wall command should write a message to all users.
Issuing the command - wall foo - appears to dump dmesg to all users w/o
the message 'foo'.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
This should be assigned to bsdtools as the package.
** Package changed: lxc (Ubuntu) => bootchart (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1458170
Title:
Vivid + bootcha
I believe this is a duplicate of bug 1240757.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1458063
Title:
Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because
name
Public bug reported:
net8-rmt# lxc-attach -n test -- bash -c 'id && egrep ^root /etc/passwd && echo
~ && echo $HOME && pwd'
uid=0(root) gid=0(root) groups=0(root)
root:x:0:0:root:/root:/bin/bash
/root
/root
/
Notice pwd show / instead of /root which is incorrect + causes all
manner of confusion
discussion about this bug
mkdir -p /var/log/drftools
/david-favor/tools/lxc-autostart-boothack
>/var/log/drftools/lxc-autostart-boothack.log 2>&1 &
** Attachment added: "lxc-autostart-boothack"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458173/+attachment/4406
Public bug reported:
This bug has been reported on many versions of Ubuntu. I've gone through many
fix guides. Nothing works. Here's the problem.
___
1) apt-get purge php-pear
2) rm -rf ~/.pearrc /etc/pear.conf /usr/share/php/
/usr/share/doc/php5-common/PEAR (required to purge all things pe
After investing hours trying all sorts of suggestions that worked for
others... None worked for me...
This is what did work...
1) net1# pecl upgrade
pear.php.net is using a unsupported protocol - This should never happen.
Error still occurring...
2) pear upgrade
... snip ...
Public bug reported:
Binary package hint: ntpdate
This is broken the same way in both Maverick and Karmic. Here's the Maverick
data.
___
lsb_release -rd
Description:Ubuntu 10.10
Release:10.10
___
apt-cache policy ntpdate
ntpdate:
Installed: 1:4.2.4p8+dfsg-1ubuntu6
Cand
Ping. Just checking to see if there's any disposition on this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in ubuntu.
https://bugs.launchpad.net/bugs/689343
Title:
ntpdate has no /etc/default/ntpdate reference
--
Ubuntu-ser
ntpdate is usually run manually.
Doing 'strings /usr/sbin/ntpdate | grep /etc/default/' shows no
reference to /etc/default/ntpdate.
The file /etc/default/ntpdate ships with Ubuntu.
This is confusing.
Either /etc/default/ntpdate should be used (fix ntpdate) or should not
(remove file from Ubuntu
Public bug reported:
service apache2 restart works...
[Wed Oct 23 09:58:47.171246 2013] [core:warn] [pid 30408] AH00098: pid file
/var/run/apache2/apache2.pid overwritten -- Unclean shutdown of previous Apache
run?
[Wed Oct 23 09:58:47.175859 2013] [mpm_prefork:notice] [pid 30408] AH00163:
Apa
Public bug reported:
Unsure if package should be apache2 or php5. Setting to apache2 for now.
At first this appeared to be some sort of apache-2.4.6 configuration problem
and the deeper down the Rabbit Hole I go... the more I think this may be some
sort of bug.
---
After upgrading from 13.0
Only occurs if php5-snmp is installed + snmp has not been configured.
Fix is to either deinstall php5-snmp or configure snmp.
Close + marked as fixed.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https:/
Oops... updated wrong bug...
This bug should stay open.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1243741
Title:
apache2 asserts on reload - GLib-GObject-CRITICAL +
g_boxed_
Mark as fixed.
The fix is to replace deprecated with as in this
script...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1243850
Title:
php5 broken after Saucy 13.10 upgrade
T
Getting worse.
Apache crashes periodically with the same error.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1243741
Title:
apache2 asserts on reload - GLib-GObject-CRITICAL +
Alright let's see if I can at least figure out the true source of this
assertion, as Apache seems to have no direct linkage to glib.
First I hacked out two scripts...
lsofunique - prints all unique files of a process ala lsof.
lddflat - prints lib name for every internal reference.
Attached is
** Attachment added: "apache-libs.txt"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1243741/+attachment/3916917/+files/apache-libs.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchp
Alright, tried pecl upgrade-all just to make sure all modules are up to
date. None of the modules referencing glib were upgraded, so now to
disable them all + test Apache reload...
In /etc/php5/mods-available commented out all extension=...so entries in
the files mentioned above...
enchant.ini
im
PASS - enchant.ini
PASS - imagick.ini
PASS - midgard2.ini
PASS - rrd.ini
FAIL! - vtkgdcm.ini
Alright... so vtkgdcm.ini is the culprit... Now what is it...
net1# apt-file search vtkgdcm.ini
php5-vtkgdcm: /etc/php5/mods-available/vtkgdcm.ini
net1# apt-cache show php5-vtkgdcm
VTK PHP bindings to th
Hum... I set the package to lxc + it changed to libcgroup.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libcgroup in Ubuntu.
https://bugs.launchpad.net/bugs/1271000
Title:
lxc-start fails with Out of memory reading cgroups
To man
Public bug reported:
Package might really be libcgroup1.
This seems to have stopped working with latest kernel upgrade.
To replicate failure...
net1# lxc-create -t ubuntu -n test
Checking cache download in /var/cache/lxc/saucy/rootfs-amd64 ...
Copy /var/cache/lxc/saucy/rootfs-amd64 to /usr/lib
net1# uname -a
Linux net1.bizcooker.com 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
net1# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 13.10
Release:13.10
Codename: saucy
net1# lxc-version
net1# cat /proc/self/mounts
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=4071956k,nr_inodes=1017989,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptm
Ugh... deinstalled + reinstall cgroup-lite + now additional errors
occur.
Hum... more errors + start.log looks like I'm actually making progress.
Attaching start.log file for entire log...
net1# lxc-destroy -n test
net1# lxc-create -n test
net1# lxc-start -n test -l trace -o start.out
lxc-start:
Hum... Something is seriously amiss...
The log file says /var/lib/lxc/c1/config is being used, which is
incorrect... as /var/lib/lxc/c1 does note exist.
I'm guessing the config file associated with the container (test) should
be used, which is...
/var/lib/lxc/test/config (test instead of c1) + e
Ah... this works...
lxc-create -t ubuntu -n test
lxc-start -n test
My guess is the default container template is suppose to be the template
matching the default OS, which in this case is ubuntu.
Somehow this isn't being done.
--
You received this bug notification because you are a member of Ub
Correct. It appears the default template processing (default meaning no
template specified) seems like it could use a bit of work.
Seems like specifying no template should either throw an error or create
some form of container that will start.
--
You received this bug notification because you ar
Ah... now I understand...
So this behavior is actually desirable. For example, to generate an
empty rootfs when creating a new OS template or App template. This way
the rootfs can be manually populated + tested before committing details
to the template.
Seems like having '-t none' might be good
Or maybe keep -t optional (so it works like always).
And generate the informational message if -t is missing or '-t none' is
specified.
As more + more people use LXC, having this simple message seems like a
life saver for newbies, like me.
Thanks for the info.
--
You received this bug notifica
73 matches
Mail list logo
