[Bug 1240757] Re: Bridge not created if bind9 is on
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1240757/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
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 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468804/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468804/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
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 allow functioning across dnsmasq failing to start or dying. -- 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.service fails on boot with signal=PIPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
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 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.service fails on boot with signal=PIPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
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 member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1452601 Title: vivid container's networking.service fails on boot with signal=PIPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
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) Active: active (exited) since Fri 2015-08-28 18:20:16 CDT; 9s ago Process: 15219 ExecStop=/usr/lib/x86_64-linux-gnu/lxc/lxc-net stop (code=exited, status=0/SUCCESS) Process: 15223 ExecStart=/usr/lib/x86_64-linux-gnu/lxc/lxc-net start (code=exited, status=0/SUCCESS) Main PID: 15223 (code=exited, status=0/SUCCESS) Shows lxc-net reported status of success + dnsmasq is never run. There's just so much wrong here... The entire /usr/lib/x86_64-linux-gnu/lxc/lxc-net script seems never to require a rethink. The problem is whoever wrote this imagined the Linux runtime environment works sensibly (no edge conditions). Many times they don't. A simple situation is if OOM (Out of Memory Killer) runs + scavenges/kill dnsmasq, then much of the state (files/directories) lxc-net depends on is out of sync... meaning there's no test for dnsmasq actually running. There's only a test for the lxcbr0 state files existing. This is an insufficient approach. I think the solution is to rewrite stop() to handle any edge condition, so lxc-net can recover normal errors without manual intervention. I'll take a stab at a rewrite + if my code isn't to embarrassing, I'll post it. -- 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.service fails on boot with signal=PIPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
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.service fails on boot with signal=PIPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
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 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.service fails on boot with signal=PIPE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
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='service mysql restart' alias mysql-restart='mysql-stop ; mysql-start' Only way I've found to get around systemd hang. -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468804/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468804/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1471358] Re: lxc-checkconfig shows Mainline PPA Wily-4.0.7 kernel missing memory controller
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.patch -- 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/1471358 Title: lxc-checkconfig shows Mainline PPA Wily-4.0.7 kernel missing memory controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471358/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
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/1468804 Title: mysql stop/restart fails + breaking mysql + reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468804/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
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 mysql stop - hangs forever, so only way to consistently stop mysql is via - mysqladmin shutdown This situation only occurs after several mysql restarts + this situation seems to occur on every Vivid install I've done. Down leveling to Utopic is how I've had to fix this. -- 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/1468804 Title: mysql stop/restart fails + breaking mysql + reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468804/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
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 appears to be the last stable version of Ubuntu. While the basic plumbing for systemd exists in Utopic, the actual /etc/init.d scripts are still working (non-systemd) versions. -- 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/1468804 Title: mysql stop/restart fails + breaking mysql + reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468804/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] [NEW] mysql stop/restart fails + breaking mysql + reboots
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 then is one of these...
mysqladmin -uroot -p shutdown
pkill mysqld
Neither of these is acceptable.
The biggest problem is this breakage also breaks reboots.
The reboot sequence depends on services doing what's expected, so when
systemctl stop mysql.service hangs, reboot hangs too.
Because of the lunacy of the entire systemctl subsystem, sshd is
correctly killed off while msqld hangs.
At this point, there's no way to ssh into system + a power recycle must
be done to complete a reboot sequence.
/bin/systemctl is an executable with no apparent way to debug it's
logic.
Please update this bug with details about how to debug /bin/systemctl +
I'll post output.
** Affects: mysql-dfsg-5.1 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1468804
Title:
mysql stop/restart fails + breaking mysql + reboots
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/1468804/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
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 update when I determine a workaround. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/1468804 Title: mysql stop/restart fails + breaking mysql + reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/1468804/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
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.launchpad.net/bugs/1468804
Title:
mysql stop/restart fails + breaking mysql + reboots
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468804/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
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 notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1468804 Title: mysql stop/restart fails + breaking mysql + reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468804/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
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 Setup Virtual Console. Jun 25 12:03:54 fine systemd[1]: Stopping Setup Virtual Console... Jun 25 12:03:54 fine systemd[1]: Stopped target Timers. Jun 25 12:03:54 fine systemd[1]: Stopping Timers. Jun 25 12:03:54 fine systemd[1]: Stopped Daily Cleanup of Temporary Directories. Jun 25 12:03:54 fine systemd[1]: Stopping Daily Cleanup of Temporary Directories. Jun 25 12:03:54 fine systemd[1]: Stopping Authenticate and Authorize Users to Run Privileged Tasks... Jun 25 12:03:54 fine systemd[1]: Stopped target Graphical Interface. Jun 25 12:03:54 fine systemd[1]: Stopping Graphical Interface. Jun 25 12:03:54 fine systemd[1]: Stopped target Multi-User System. Jun 25 12:03:54 fine systemd[1]: Stopping Multi-User System. Jun 25 12:03:54 fine systemd[1]: Stopping Login Service... Jun 25 12:03:54 fine systemd[1]: Stopping Regular background program processing daemon... Jun 25 12:03:54 fine systemd[1]: Stopping LSB: Cleans up any mess left by 0dns-up... Jun 25 12:03:54 fine systemd[1]: Stopped target Login Prompts. Jun 25 12:03:54 fine systemd[1]: Stopping Login Prompts. Jun 25 12:03:54 fine systemd[1]: Stopping Getty on tty1... Jun 25 12:03:54 fine systemd[1]: Stopping LSB: disk temperature monitoring daemon... Jun 25 12:03:54 fine systemd[1]: Stopping Fail2Ban Service... Jun 25 12:03:54 fine rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=1027 x-info=http://www.rsyslog.com;] exiting on signal 15. -- 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/1468804 Title: mysql stop/restart fails + breaking mysql + reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468804/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
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 ntp /etc/init.d/ OPEN hddtemp /etc/init.d/ OPEN hddtemp /etc/init.d/ OPEN apport /etc/init.d/ OPEN apport /etc/init.d/ OPEN grub-common /etc/init.d/ OPEN grub-common /etc/default/ OPEN rcS /etc/init.d/ OPEN mdadm /etc/init.d/ OPEN mdadm /etc/init.d/ OPEN preload /etc/init.d/ OPEN preload /etc/init.d/ OPEN ondemand /etc/init.d/ OPEN ondemand /etc/default/ OPEN rcS /etc/init.d/ OPEN sysstat /etc/init.d/ OPEN sysstat /etc/init.d/ OPEN apache2 /etc/init.d/ OPEN apache2 /etc/default/ OPEN rcS /etc/init.d/ OPEN rollerd /etc/init.d/ OPEN rollerd /etc/default/ OPEN rcS /etc/init.d/ OPEN dns-clean /etc/init.d/ OPEN dns-clean /etc/default/ OPEN rcS /etc/init.d/ OPEN irqbalance /etc/init.d/ OPEN irqbalance /etc/apt/apt.conf.d/ OPEN 20archive Notice the mysql shutdown script is never accessed. Looking at the apache2 shutdown script, there seems to be no connection which might interfere with mysql. Placing mysqladmin shutdown in /etc/init.d/apache2 fails to allow reboot either. -- 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/1468804 Title: mysql stop/restart fails + breaking mysql + reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468804/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
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 notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1468804 Title: mysql stop/restart fails + breaking mysql + reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468804/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1468804] Re: mysql stop/restart fails + breaking mysql + reboots
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# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 15.04 Release:15.04 Codename: vivid ovhfine# dpkg -l | egrep ^mysql ovhfine# dpkg -l | egrep mysql ii libdbd-mysql-perl 4.028-2 amd64Perl5 database interface to the MySQL database ii libmysqlclient-dev 5.6.24-0ubuntu2 amd64MySQL database development files ii libmysqlclient18:amd64 5.6.24-0ubuntu2 amd64MySQL database client library ii mysql-client-5.65.6.24-0ubuntu2 amd64MySQL database client binaries ii mysql-client-core-5.6 5.6.24-0ubuntu2 amd64MySQL database core client binaries ii mysql-common5.6.24-0ubuntu2 all MySQL database common files, e.g. /etc/mysql/my.cnf ii mysql-server5.6.24-0ubuntu2 all MySQL database server (metapackage depending on the latest version) ii mysql-server-5.65.6.24-0ubuntu2 amd64MySQL database server binaries and system database setup ii mysql-server-core-5.6 5.6.24-0ubuntu2 amd64MySQL database server binaries ii php5-mysql 5.6.4+dfsg-4ubuntu6 amd64MySQL module for php5 All packages up to date. ** Package changed: mysql-dfsg-5.1 (Ubuntu) = mysql-5.6 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/1468804 Title: mysql stop/restart fails + breaking mysql + reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1468804/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1330542] Re: php-pear broken in trusty tahr - channel wrapper missing
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: file_exists(): Unable to find the wrapper channel - did you forget
to enable it when you configured PHP? in PEAR/Downloader/Package.php on line
1518
PHP Warning: file_exists(): Unable to find the wrapper channel - did you
forget to enable it when you configured PHP? in
/usr/share/php/PEAR/Downloader/Package.php on line 1518
PHP Stack trace:
PHP 1. {main}() /usr/share/php/pearcmd.php:0
PHP 2. PEAR_Command_Common-run() /usr/share/php/pearcmd.php:307
PHP 3. PEAR_Command_Install-doInstall()
/usr/share/php/PEAR/Command/Common.php:271
PHP 4. PEAR_Downloader-download() /usr/share/php/PEAR/Command/Install.php:661
PHP 5. PEAR_Downloader_Package-initialize()
/usr/share/php/PEAR/Downloader.php:279
PHP 6. PEAR_Downloader_Package-_fromFile()
/usr/share/php/PEAR/Downloader/Package.php:160
PHP 7. file_exists() /usr/share/php/PEAR/Downloader/Package.php:1518
Warning: is_file(): Unable to find the wrapper channel - did you forget to
enable it when you configured PHP? in PEAR/Downloader/Package.php on line 1528
PHP Warning: is_file(): Unable to find the wrapper channel - did you forget
to enable it when you configured PHP? in
/usr/share/php/PEAR/Downloader/Package.php on line 1528
PHP Stack trace:
PHP 1. {main}() /usr/share/php/pearcmd.php:0
PHP 2. PEAR_Command_Common-run() /usr/share/php/pearcmd.php:307
PHP 3. PEAR_Command_Install-doInstall()
/usr/share/php/PEAR/Command/Common.php:271
PHP 4. PEAR_Downloader-download() /usr/share/php/PEAR/Command/Install.php:661
PHP 5. PEAR_Downloader_Package-initialize()
/usr/share/php/PEAR/Downloader.php:279
PHP 6. PEAR_Downloader_Package-_fromFile()
/usr/share/php/PEAR/Downloader/Package.php:160
PHP 7. is_file() /usr/share/php/PEAR/Downloader/Package.php:1528
Warning: is_file(): Unable to find the wrapper channel - did you forget to
enable it when you configured PHP? in PEAR/Downloader/Package.php on line 1528
PHP Warning: is_file(): Unable to find the wrapper channel - did you forget
to enable it when you configured PHP? in
/usr/share/php/PEAR/Downloader/Package.php on line 1528
PHP Stack trace:
PHP 1. {main}() /usr/share/php/pearcmd.php:0
PHP 2. PEAR_Command_Common-run() /usr/share/php/pearcmd.php:307
PHP 3. PEAR_Command_Install-doInstall()
/usr/share/php/PEAR/Command/Common.php:271
PHP 4. PEAR_Downloader-download() /usr/share/php/PEAR/Command/Install.php:661
PHP 5. PEAR_Downloader_Package-initialize()
/usr/share/php/PEAR/Downloader.php:279
PHP 6. PEAR_Downloader_Package-_fromFile()
/usr/share/php/PEAR/Downloader/Package.php:160
PHP 7. is_file() /usr/share/php/PEAR/Downloader/Package.php:1528
downloading Archive_Tar-1.3.16.tgz ...
Starting to download Archive_Tar-1.3.16.tgz (20,024 bytes)
...done: 20,024 bytes
Warning: unlink(/usr/share/php/Archive/Tar.php): No such file or directory in
PEAR/Installer.php on line 870
PHP Warning: unlink(/usr/share/php/Archive/Tar.php): No such file or directory
in /usr/share/php/PEAR/Installer.php on line 870
PHP Stack trace:
PHP 1. {main}() /usr/share/php/pearcmd.php:0
PHP 2. PEAR_Command_Common-run() /usr/share/php/pearcmd.php:307
PHP 3. PEAR_Command_Install-doInstall()
/usr/share/php/PEAR/Command/Common.php:271
PHP 4. PEAR_Installer-install() /usr/share/php/PEAR/Command/Install.php:708
PHP 5. PEAR_Installer-commitFileTransaction()
/usr/share/php/PEAR/Installer.php:1449
PHP 6. unlink() /usr/share/php/PEAR/Installer.php:870
Could not delete /usr/share/php/Archive/Tar.php, cannot rename
/usr/share/php/Archive/.tmpTar.php
ERROR: commit failed
Warning: unlink(/tmp/glibctestntGkBm): No such file or directory in System.php
on line 232
PHP Warning: unlink(/tmp/glibctestntGkBm): No such file or directory in
/usr/share/php/System.php on line 232
PHP Stack trace:
PHP 1. _PEAR_call_destructors() /usr/share/php/PEAR.php:0
PHP 2. call_user_func_array:{/usr/share/php/PEAR.php:774}()
/usr/share/php/PEAR.php:774
PHP 3. System::_removeTmpFiles() /usr/share/php/PEAR.php:774
PHP 4. System::rm() /usr/share/php/System.php:466
PHP 5. unlink() /usr/share/php/System.php:232
Warning: unlink(/tmp/pear/temp/pearR3yiIK): No such file or directory in
System.php on line 232
PHP Warning: unlink(/tmp/pear/temp/pearR3yiIK): No such file or directory in
/usr/share/php/System.php on line 232
PHP Stack trace:
PHP 1. _PEAR_call_destructors() /usr/share/php/PEAR.php:0
PHP 2. call_user_func_array:{/usr/share/php/PEAR.php:774}()
/usr/share/php/PEAR.php:774
PHP 3. System::_removeTmpFiles() /usr/share/php/PEAR.php:774
PHP 4. System::rm() /usr/share/php/System.php:466
PHP 5. unlink() /usr/share/php/System.php:232
--
You received this bug notification because you are a member of
[Bug 1458173] Re: Vivid + LXC autostart not working
Workaround is to run a script in /etc/rc.local that waits for the bridge adapter to come up + then runs lxc-autostart. This script can be run in background, for example... /etc/rc.local snippet... # LXC autostart boot hack # Track https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458173 for discussion about this bug mkdir -p /var/log/drftools /david-favor/tools/lxc-autostart-boothack /var/log/drftools/lxc-autostart-boothack.log 21 ** Attachment added: lxc-autostart-boothack https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458173/+attachment/4406621/+files/lxc-autostart-boothack -- 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://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458173/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458063] Re: Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address
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 named listening to UDP on LXC address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458063/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1459751] [NEW] lxc-attach runs in wrong container directory
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 when debugging path related problems. 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-rmt# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 15.04 Release:15.04 Codename: vivid Same behavior with containers created with precise through wily releases. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/1459751 Title: lxc-attach runs in wrong container directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1459751/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458170] Re: Vivid + bootchart quietly fails
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 + bootchart quietly fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bootchart/+bug/1458170/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458170] [NEW] Vivid + bootchart quietly fails
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-rmt# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 15.04 Release:15.04 Codename: vivid net8-rmt# pkg-list | grep bootchart bootchart 0.90.2-8ubuntu2 pybootchartgui 0+r141-0ubuntu5 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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 + bootchart quietly fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458170/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458170] Re: Vivid + bootchart quietly fails
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: Vivid + bootchart quietly fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458170/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458180] [NEW] Vivid + wall badly broken
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 member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1458180 Title: Vivid + wall badly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458180/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458063] Re: Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address
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 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 named listening to UDP on LXC address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458063/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458170] Re: Vivid + bootchart quietly fails
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 upgraded. Need to get 0 B/11.2 kB of archives. After this operation, 98.3 kB of additional disk space will be used. Selecting previously unselected package bootchart. (Reading database ... 84900 files and directories currently installed.) Preparing to unpack .../bootchart_0.90.2-8ubuntu2_amd64.deb ... Unpacking bootchart (0.90.2-8ubuntu2) ... Processing triggers for systemd (219-7ubuntu5) ... Setting up bootchart (0.90.2-8ubuntu2) ... update-initramfs: Generating /boot/initrd.img-3.19.0-18-generic update-initramfs: Generating /boot/initrd.img-3.19.0-16-generic Processing triggers for systemd (219-7ubuntu5) ... net8-rmt# sys-ll | grep bootchart dev-.bootchart-proc.mount loaded active mounted /dev/.bootchart/proc Reboot + /var/log/bootchart still empty. -- 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 + bootchart quietly fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458170/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458170] Re: Vivid + bootchart quietly fails
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 or directory. Ah... net8-rmt# sys-ll | grep bootchart dev-.bootchart-proc.mount loaded active mounted /dev/.bootchart/proc Shows there is no bootstart.service available, so likely 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: Vivid + bootchart quietly fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458170/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458173] [NEW] Vivid + LXC autostart not working
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 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-rmt# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 15.04 Release:15.04 Codename: vivid net8-rmt# pkg-list | egrep -e lxc -e cgroup cgroup-bin 0.38-1ubuntu2 cgroup-lite 1.10 libcgroup1 0.38-1ubuntu2 liblxc1 1.1.2-0ubuntu3 lxc 1.1.2-0ubuntu3 lxc-templates 1.1.2-0ubuntu3 lxcfs 0.7-0ubuntu4 lxctl 0.3.1+debian-3 python3-lxc 1.1.2-0ubuntu3 net8-rmt# lxc-ls --fancy NAME STATEIPV4 IPV6 GROUPS AUTOSTART test STOPPED - - - YES net8-rmt# egrep AUTO /etc/default/lxc # LXC_AUTO - whether or not to start containers symlinked under LXC_AUTO=false ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458173/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458173] Re: Vivid + LXC autostart not working
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://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458173/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458063] Re: Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address
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 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 named listening to UDP on LXC address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458063/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458063] [NEW] Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address
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. Distributor ID: Ubuntu Description:Ubuntu 15.04 Release:15.04 Codename: vivid 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-rmt# pkg-list | egrep -e lxc -e cgroup cgroup-bin 0.38-1ubuntu2 cgroup-lite 1.10 libcgroup1 0.38-1ubuntu2 liblxc1 1.1.2-0ubuntu3 lxc 1.1.2-0ubuntu3 lxc-templates 1.1.2-0ubuntu3 lxcfs 0.7-0ubuntu4 lxctl 0.3.1+debian-3 python3-lxc 1.1.2-0ubuntu3 Behavior is this. 1) After reboot, lxcbr0 is missing 2) /usr/lib/x86_64-linux-gnu/lxc/lxc-net restart reports 10.0.3.1 (set in /etc/default/lxc-net ) as being in use. 3) netstat reports bind/named has the address, at least UDP, no TCP. 4) /var/log/syslog from last boot shows this... net8-rmt# grep 10.0.3.1 /var/log/syslog May 22 16:03:01 ns515383 named[1355]: listening on IPv4 interface lxcbr0, 10.0.3.1#53 May 22 16:03:02 ns515383 ntpd[1453]: Listen normally on 5 lxcbr0 10.0.3.1 UDP 123 May 22 16:03:04 ns515383 lxc-net[1360]: dnsmasq: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:03:04 ns515383 dnsmasq[1768]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:03:06 ns515383 ntpd[1453]: Deleting interface #5 lxcbr0, 10.0.3.1#123, interface stats: received=0, sent=0, dropped=0, active_time=4 secs May 22 16:21:04 ns515383 dnsmasq[10991]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:21:30 ns515383 dnsmasq[11156]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:24:15 ns515383 dnsmasq[12092]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:25:36 ns515383 dnsmasq[12576]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:29:54 ns515383 dnsmasq[14015]: failed to create listening socket for 10.0.3.1: Address already in use May 22 16:34:55 ns515383 named[1355]: no longer listening on 10.0.3.1#53 May 22 16:35:10 ns515383 ntpd[1453]: Listen normally on 9 lxcbr0 10.0.3.1 UDP 123 May 22 16:35:26 ns515383 ntpd[1453]: Deleting interface #9 lxcbr0, 10.0.3.1#123, interface stats: received=0, sent=0, dropped=0, active_time=16 secs May 22 16:52:50 ns515383 ntpd[1453]: Listen normally on 11 lxcbr0 10.0.3.1 UDP 123 5) Nothing in named config referencing the LXC IP. 6) Then after server minutes, named stops listening to this address, at which time /usr/lib/x86_64-linux-gnu/lxc/lxc-net restart begins working as expected. 7) If /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop is issued + service bind9 restart issued, named no longer attempts to connect to 10.0.3.1 so all's well. Any suggestions on why named might be grabbing the LXC address at boot time are appreciated. I reported this as a bug, because none of the named config files reference the LXC IP address, so to me, named should never touch this address. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time + Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening on LXC address ** Summary changed: - Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening on LXC address + Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address -- 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 named listening to UDP on LXC address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458063/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1458063] Re: Vivid /usr/lib/x86_64-linux-gnu/lxc/lxc-net fails at boot time because named listening to UDP on LXC address
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 edit bind's config files to have LXC
networking start at boot time.
--
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
named listening to UDP on LXC address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1458063/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1416875] [NEW] apache-2.4.10 dies in reload
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-curl + had no effect. Using trace8 provides no additional detail. Unable to get apache to generate a core dump, even after reading many articles + trying many command line incantations. Someone tell me how to get a core dump + I'll post the stack trace of failure. Thanks. ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New -- 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/1416875 Title: apache-2.4.10 dies in reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1416875/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1416875] Re: apache-2.4.10 dies in reload
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 2015] [core:notice] [pid 14428] AH00060: seg fault or similar nasty error detected in the parent process -- 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/1416875 Title: apache-2.4.10 dies in reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1416875/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1416875] Re: apache-2.4.10 dies in reload
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.launchpad.net/bugs/1416875 Title: apache-2.4.10 dies in reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1416875/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1416875] Re: apache-2.4.10 dies in reload
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 member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1416875 Title: apache-2.4.10 dies in reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1416875/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1330542] Re: php-pear broken in trusty tahr - channel wrapper missing
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 ... pear/pear dependency package pear/XML_Util downloaded version 1.2.3 is not the recommended version 1.2.1, but may be compatible, use --force to install pear/XML_Util cannot be installed, conflicts with installed packages So pear gives more info... great... Now to cram through a forced update... 3) pear install --force XML_Util 4) pecl upgrade works now. Very ugly. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1330542 Title: php-pear broken in trusty tahr - channel wrapper missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1330542/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1330542] [NEW] php-pear broken in trusty tahr - channel wrapper missing
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 pear)
3) apt-get install php-pear
4) pear list-channels
nap-net1# pear list-channels
Registered Channels:
Channel Alias Summary
doc.php.net phpdocs PHP Documentation Team
pear.php.net pearPHP Extension and Application
Repository
pecl.php.net peclPHP Extension Community Library
__uri__uri Pseudo-channel for static packages
nap-net1# pear install foo
Warning: file_exists(): Unable to find the wrapper channel - did you forget
to enable it when you configured PHP? in PEAR/Downloader/Package.php on line
1518
PHP Warning: file_exists(): Unable to find the wrapper channel - did you
forget to enable it when you configured PHP? in
/usr/share/php/PEAR/Downloader/Package.php on line 1518
PHP Stack trace:
PHP 1. {main}() /usr/share/php/pearcmd.php:0
PHP 2. PEAR_Command_Common-run() /usr/share/php/pearcmd.php:305
PHP 3. PEAR_Command_Install-doInstall()
/usr/share/php/PEAR/Command/Common.php:271
PHP 4. PEAR_Downloader-download() /usr/share/php/PEAR/Command/Install.php:661
PHP 5. PEAR_Downloader_Package-initialize()
/usr/share/php/PEAR/Downloader.php:279
PHP 6. PEAR_Downloader_Package-_fromFile()
/usr/share/php/PEAR/Downloader/Package.php:160
PHP 7. file_exists() /usr/share/php/PEAR/Downloader/Package.php:1518
Warning: is_file(): Unable to find the wrapper channel - did you forget to
enable it when you configured PHP? in PEAR/Downloader/Package.php on line 1528
PHP Warning: is_file(): Unable to find the wrapper channel - did you forget
to enable it when you configured PHP? in
/usr/share/php/PEAR/Downloader/Package.php on line 1528
PHP Stack trace:
PHP 1. {main}() /usr/share/php/pearcmd.php:0
PHP 2. PEAR_Command_Common-run() /usr/share/php/pearcmd.php:305
PHP 3. PEAR_Command_Install-doInstall()
/usr/share/php/PEAR/Command/Common.php:271
PHP 4. PEAR_Downloader-download() /usr/share/php/PEAR/Command/Install.php:661
PHP 5. PEAR_Downloader_Package-initialize()
/usr/share/php/PEAR/Downloader.php:279
PHP 6. PEAR_Downloader_Package-_fromFile()
/usr/share/php/PEAR/Downloader/Package.php:160
PHP 7. is_file() /usr/share/php/PEAR/Downloader/Package.php:1528
Warning: is_file(): Unable to find the wrapper channel - did you forget to
enable it when you configured PHP? in PEAR/Downloader/Package.php on line 1528
PHP Warning: is_file(): Unable to find the wrapper channel - did you forget
to enable it when you configured PHP? in
/usr/share/php/PEAR/Downloader/Package.php on line 1528
PHP Stack trace:
PHP 1. {main}() /usr/share/php/pearcmd.php:0
PHP 2. PEAR_Command_Common-run() /usr/share/php/pearcmd.php:305
PHP 3. PEAR_Command_Install-doInstall()
/usr/share/php/PEAR/Command/Common.php:271
PHP 4. PEAR_Downloader-download() /usr/share/php/PEAR/Command/Install.php:661
PHP 5. PEAR_Downloader_Package-initialize()
/usr/share/php/PEAR/Downloader.php:279
PHP 6. PEAR_Downloader_Package-_fromFile()
/usr/share/php/PEAR/Downloader/Package.php:160
PHP 7. is_file() /usr/share/php/PEAR/Downloader/Package.php:1528
No releases available for package pear.php.net/foo
install failed
** Affects: php5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1330542
Title:
php-pear broken in trusty tahr - channel wrapper missing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1330542/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271000] Re: lxc-start fails with Out of memory reading cgroups
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 to roll into the code, so -t template is always required. Then when '-t none' is specified, maybe issue a simple informational message... something like... Creating container with an empty rootfs. Be sure to manually create rootfs to meet your needs. Or similar. Thanks for the info. This makes perfect sense now. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271000] Re: lxc-start fails with Out of memory reading cgroups
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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271000] Re: lxc-start fails with Out of memory reading cgroups
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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271000] Re: lxc-start fails with Out of memory reading cgroups
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,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=816440k,mode=755 0 0 /dev/disk/by-uuid/849acaae-87ce-407a-b01c-80910dbad24e / ext4 rw,noatime,nodiratime,errors=remount-ro,data=ordered 0 0 none /sys/fs/cgroup tmpfs rw,relatime,size=4k,mode=755 0 0 none /sys/fs/fuse/connections fusectl rw,relatime 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 none /sys/kernel/security securityfs rw,relatime 0 0 tmpfs /tmp tmpfs rw,noatime,nodiratime,size=816440k 0 0 none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0 none /run/shm tmpfs rw,nosuid,nodev,relatime 0 0 none /run/user tmpfs rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755 0 0 none /sys/fs/pstore pstore rw,relatime 0 0 tmpfs /var/tmp tmpfs rw,noatime,nodiratime,size=816440k 0 0 /dev/sda1 /boot ext3 rw,noatime,nodiratime,errors=continue,user_xattr,acl,barrier=1,data=ordered 0 0 systemd /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,name=systemd 0 0 cgroup /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset,clone_children 0 0 cgroup /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0 cgroup /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0 cgroup /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0 cgroup /sys/fs/cgroup/devices cgroup rw,relatime,devices 0 0 cgroup /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,relatime,blkio 0 0 cgroup /sys/fs/cgroup/perf_event cgroup rw,relatime,perf_event 0 0 cgroup /sys/fs/cgroup/hugetlb cgroup rw,relatime,hugetlb 0 0 none /sys/fs/cgroup tmpfs rw,relatime 0 0 net1# lxc-start -n c1 -l trace -o start.out lxc-start: Executing '/sbin/init' with no configuration file may crash the host net1# cat start.out lxc-start 1390511075.386 INFO lxc_start_ui - using rcfile /var/lib/lxc/c1/config lxc-start 1390511075.386 WARN lxc_log - lxc_log_init called with log already initialized lxc-start 1390511075.386 ERRORlxc_start_ui - Executing '/sbin/init' with no configuration file may crash the host Hum... Looks like I have both libcgroup1 + cgroup-lite installed. I'll try a deinstall libcgroup1... Nope... Did apt-get purge libcgroup1 + still get the same error. Other suggestions? -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271000] Re: lxc-start fails with Out of memory reading cgroups
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: No such file or directory - failed to create symlink for kmsg lxc-start: failed to setup kmsg for 'test' lxc-start: No such file or directory - failed to mount /proc in the container. lxc-start: failed to setup the container lxc-start: invalid sequence number 1. expected 2 lxc-start: failed to spawn 'test' ** Attachment added: start.out https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+attachment/3955379/+files/start.out -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271000] Re: lxc-start fails with Out of memory reading cgroups
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) + even trying to supply this config file manually, it's ignored... as in... lxc-start -n test -f /var/lib/lxc/test/config -l trace -o start.out So it appears the problems are... 1) The config file associated with the container is incorrectly determined. 2) If the correct config file is specified, it's quietly ignored. Suggestions? -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271000] Re: lxc-start fails with Out of memory reading cgroups
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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271000] Re: lxc-start fails with Out of memory reading cgroups
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 lxc version: 1.0.0.alpha1 -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271000] Re: lxc-start fails with Out of memory reading cgroups
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271000] [NEW] lxc-start fails with Out of memory reading cgroups
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/x86_64-linux-gnu/lxc ... Copying rootfs to /usr/lib/x86_64-linux-gnu/lxc ... Generating locales... en_US.UTF-8... up-to-date Generation complete. Creating SSH2 RSA key; this may take some time ... Creating SSH2 DSA key; this may take some time ... Creating SSH2 ECDSA key; this may take some time ... invoke-rc.d: policy-rc.d denied execution of start. ## # The default user is 'ubuntu' with password 'ubuntu'! # Use the 'sudo' command to run tasks as root in the container. ## net1# lxc-start -n test lxc-start: Out of memory reading cgroups lxc-start: failed to spawn 'test' Also now cgroup namespaces no longer shows up as enabled. Seems like this did show up as enabled in previous kernel. Reading other bugs reports, this seems to be okay + will be fixed upstream + I mention it here because it's a difference. net1# lxc-checkconfig | grep -v enabled Kernel configuration not found at /proc/config.gz; searching... Kernel configuration found at /boot/config-3.11.0-15-generic --- Namespaces --- User namespace: missing --- Control groups --- Cgroup namespace: required The cgroup mount point is showing up... net1# mount | grep cgroup none on /sys/fs/cgroup type tmpfs (rw) systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd) none on /sys/fs/cgroup type tmpfs (rw) And there is now filesystem entry for the container named test under /sys/fs/cgroup so this may also suggest a problem. net1# ls /sys/fs/cgroup net1# ** Affects: libcgroup (Ubuntu) Importance: Undecided Status: New -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243741] Re: apache2 asserts on reload - GLib-GObject-CRITICAL + g_boxed_type_register_static
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 the full output off - lddflat $(lsofunique apache2 | grep '\.so') | grep glib The lines that pop out relate to PHP... as I suspected... /usr/lib/php5/20121212/enchant.so /lib/x86_64-linux-gnu/libglib-2.0.so.0 /usr/lib/php5/20121212/imagick.so /lib/x86_64-linux-gnu/libglib-2.0.so.0 /usr/lib/php5/20121212/midgard2.so /lib/x86_64-linux-gnu/libglib-2.0.so.0 /usr/lib/php5/20121212/midgard2.so /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 /usr/lib/php5/20121212/rrd.so /lib/x86_64-linux-gnu/libglib-2.0.so.0 /usr/lib/php5/20121212/vtkgdcm.so /lib/x86_64-linux-gnu/libglib-2.0.so.0 I'll turn off all these modules, then turn them back on, one-by-one, to identify the culprit. I'll update this ticket with the nefarious module throwing the assertion. -- 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_type_register_static To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1243741/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243741] Re: apache2 asserts on reload - GLib-GObject-CRITICAL + g_boxed_type_register_static
** 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.launchpad.net/bugs/1243741 Title: apache2 asserts on reload - GLib-GObject-CRITICAL + g_boxed_type_register_static To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1243741/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243741] Re: apache2 asserts on reload - GLib-GObject-CRITICAL + g_boxed_type_register_static
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 imagick.ini midgard2.ini rrd.ini vtkgdcm.ini service apache2 restart lddflat $(lsofunique apache2 | grep '\.so') | grep glib | grep php5 - yields nothing, so we're good to test reload function. Success! Apache now reloads w/o the glib assertion... Whew... No to figure out which php module is throwing the assertion. -- 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_type_register_static To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1243741/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243741] Re: apache2 asserts on reload - GLib-GObject-CRITICAL + g_boxed_type_register_static
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 the GDCM DICOM library. Hum... Just going to remove this package, as I'm unsure what dependency this package satisfies. So fix/resolution for this bug is... apt-get purge php5-vtkgdcm I'm unsure what to do next. Likely a bug ought to be opened against php5-vtkgdcm referencing this ticket. In the meantime, since many people are reporting this bug, maybe there's some way upstream can flag the following package as broken... php5-vtkgdcm-2.2.3 -- 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_type_register_static To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1243741/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243741] Re: apache2 asserts on reload - GLib-GObject-CRITICAL + g_boxed_type_register_static
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 + g_boxed_type_register_static To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1243741/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243741] [NEW] apache2 asserts on reload - GLib-GObject-CRITICAL + g_boxed_type_register_static
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: Apache/2.4.6 (Ubuntu) PHP/5.5.3-1ubuntu2 configured -- resuming normal operations [Wed Oct 23 09:58:47.175938 2013] [core:notice] [pid 30408] AH00094: Command line: '/usr/sbin/apache2' service apache2 reload fails... [Wed Oct 23 10:02:15.429601 2013] [mpm_prefork:notice] [pid 30591] AH00171: Graceful restart requested, doing restart (process:30591): GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed ** ERROR:gda-init.c:166:gda_init: assertion failed: (type) [Wed Oct 23 10:02:15.495609 2013] [core:notice] [pid 30591] AH00060: seg fault or similar nasty error detected in the parent process ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New -- 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_type_register_static To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1243741/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243850] [NEW] php5 broken after Saucy 13.10 upgrade
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.04 to 13.10 + adding Require all granted where appropriate, all php files are returned as text rather than executing. No info in error.log (with LogLevel debug) only access.log shows the file returned. It appears the relationship between .php files + x-httpd-php handler is somehow broken. I've tried debugging via strace + apache2 -X with no joy. Questions are... 1) What's the best way to debug this situation? 2) If this is a known problem, what's the fix? - server-status shows... Server Version: Apache/2.4.6 (Ubuntu) PHP/5.5.3-1ubuntu2 Server MPM: prefork Server Built: Aug 9 2013 14:28:56 server-info shows... In file: /etc/apache2/mods-enabled/php5.conf 1: FilesMatch .+\.ph(p[345]?|t|tml)$ 2: SetHandler application/x-httpd-php : /FilesMatch 5: FilesMatch .+\.phps$ 6: SetHandler application/x-httpd-php-source : /FilesMatch net1# apt-get install libapache2-mod-php5 Reading package lists... Done Building dependency tree Reading state information... Done libapache2-mod-php5 is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Config for directory in question... Directory /.../phptest AllowOverride All Options +ExecCGI AddHandler cgi-script .php .cgi .pl .sh Require all granted /Directory In the directory is a file phpinfo.php with following characteristics... net1# find phptest -ls 98355754 drwxr-xr-x 2 www-data www-data 4096 Oct 23 11:41 phptest 98355734 -rwxr-xr-x 1 www-data www-data 17 Oct 23 10:36 phptest/phpinfo.php The file contains... net1# cat phptest/phpinfo.php ? phpinfo() ?; ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1243850/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243741] Re: apache2 asserts on reload - GLib-GObject-CRITICAL + g_boxed_type_register_static
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://bugs.launchpad.net/bugs/1243741 Title: apache2 asserts on reload - GLib-GObject-CRITICAL + g_boxed_type_register_static To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1243741/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243741] Re: apache2 asserts on reload - GLib-GObject-CRITICAL + g_boxed_type_register_static
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_type_register_static To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1243741/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1243850] Re: php5 broken after Saucy 13.10 upgrade
Mark as fixed. The fix is to replace deprecated ? ... ? with ?php ... ? as in this script... ?php print_r (phpinfo()); ? -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1243850/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 736149] Re: Ubuntu 10.10 /etc/hosts ignored by /lib/resolv.so.2
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 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 736149] [NEW] Ubuntu 10.10 host command ignores all conf files
Public bug reported: Binary package hint: bind9-host root@net1:/etc# strace -e open host foo 21 | 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 in the resolver code if the bind service is stopped. ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New -- 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 host command ignores all conf files -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 736149] Re: Ubuntu 10.10 /etc/hosts ignored by resolv.so
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.so + Ubuntu 10.10 /etc/hosts ignored by /lib/resolv.so.2 -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 736149] Re: Ubuntu 10.10 /etc/hosts ignored by /lib/resolv.so.2
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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 736149] Re: Ubuntu 10.10 /etc/hosts ignored by /lib/resolv.so.2
ping works as expected... root@net1# strace -e open /bin/ping localhost 21 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 open(/etc/ld.so.cache, O_RDONLY) = 4 open(/lib/libnss_files.so.2, O_RDONLY) = 4 open(/etc/host.conf, O_RDONLY)= 4 open(/etc/hosts, O_RDONLY|O_CLOEXEC) = 4 Hum... Looks like resolver conf files are walked in libc... root@net1# ldd /bin/ping linux-vdso.so.1 = (0x7fff63452000) libc.so.6 = /lib/libc.so.6 (0x7f6585db6000) /lib64/ld-linux-x86-64.so.2 (0x7f6586145000) root@net1# strings /lib/libc.so.6 | grep /etc /etc/localtime /etc/gai.conf /etc/mtab /etc/hostid /etc/ttys /etc/shells /etc/fstab /etc/.pwd.lock /etc/resolv.conf /etc/host.conf /etc/nsswitch.conf /etc/hosts.equiv /etc/bindresvport.blacklist So the question is why the host command ignores all these files and ping honors them. Or rather howto configure system wide honoring of all these files for resolver access from any command. -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 689343] Re: ntpdate has no /etc/default/ntpdate reference
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). -- 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 689343] Re: ntpdate has no /etc/default/ntpdate reference
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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 689343] [NEW] ntpdate has no /etc/default/ntpdate reference
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 Candidate: 1:4.2.4p8+dfsg-1ubuntu6 Version table: *** 1:4.2.4p8+dfsg-1ubuntu6 0 500 http://us.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages 100 /var/lib/dpkg/status ___ After hours of messing with /etc/default/ntpdate and reading reams of postings here's what I've learned. 1) Camping /etc/default (inotifywait -mr /etc/default) showed no activity when ntpdate is run. 2) Checking the man page (man ntpdate) produces no reference to /etc/default/ntpdate. 3) Brute checking ntpdate (strings /usr/sbin/ntpdate | grep /etc/default/ntpdate) shows no reference. Looks like someone's asleep at the wheel. Best to either fix ntpdate or... Remove /etc/default/ntpdate references (dpkg -L ntpdate | grep /etc/default/ntpdate) from the ntpdate package. Preferably fix ntpdate to actually use this file. Thanks. ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
