[Bug 1902903] [NEW] monit disregards start delay period in LXC container
Public bug reported: Monit has a start delay timer, to prevent service from starting other services too early (before they are ready). This bug has been reported to monit developer and is fixed with commit https://bitbucket.org/tildeslash/monit/commits/2dae91df32ac7bd0e02c6e6ee8522e75958f4324. Main problem here is, that boot time is read from /proc/stat # grep btime /proc/stat This boot time is from host though and a wrong reference in this case. It differs from /proc/uptime. It is probably a major bug, because it can disrupt boot order. If monit starts pretty early and detects other services are not running, it will immediately (re-)start them. In case of apps with databases, this could lead to problems. # lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 # apt-cache policy monit monit: Installed: 1:5.26.0-4 Candidate: 1:5.26.0-4 Version table: *** 1:5.26.0-4 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: monit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902903 Title: monit disregards start delay period in LXC container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monit/+bug/1902903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895514] [NEW] pfqueue: double free or corruption
Public bug reported: After starting pfqueue I can switch between modes with 3, 4, 5...BUT if I press 1 or 2 to get to the "deferred" or "active" queue the program terminates with the following code: "double free or corruption (out) Aborted" # lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal # aptitude show pfqueue Package: pfqueue Version: 0.5.6-9build3 State: installed ** Affects: monit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895514 Title: pfqueue: double free or corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monit/+bug/1895514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880662] [NEW] munin node config for mysql not working
Public bug reported:
I just installed a fresh Ubuntu 20.04 with mysql and munin.
It previously worked quite well with Ubuntu 18.04, but now the default
plugin-conf.d/munin-node file seems to not work anymore for mysql.
Here is the output of it:
# munin-run mysql_commands
DBI
connect('mysql;mysql_read_default_file=/etc/mysql/debian.cnf;mysql_connect_timeout=5','root',...)
failed: Access denied for user 'root'@'localhost' (using password: YES) at
/etc/munin/plugins/mysql_commands line 1071.
Warning: the execution of 'munin-run' via 'systemd-run' returned an error. This
may either be caused by a problem with the plugin to be executed or a failure
of the 'systemd-run' wrapper. Details of the latter can be found via
'journalctl'.
The mysql section in /etc/munin/plugin-conf.d/munin-node looks like:
[mysql*]
user root
env.mysqlopts --defaults-file=/etc/mysql/debian.cnf
env.mysqluser root
env.mysqlconnection
DBI:mysql:mysql;mysql_read_default_file=/etc/mysql/debian.cnf
which will result in an error using e.g. mysql_commands or so.
Changing this section to...
[mysql*]
user root
env.mysqluser debian-sys-maint
env.mysqlconnection
DBI:mysql:mysql;mysql_read_default_file=/etc/mysql/debian.cnf
...did the trick for my installation.
The main problem seems to be the mysqluser set to root even though the
default file contains only a "debian-sys-maint" user.
** Affects: munin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880662
Title:
munin node config for mysql not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1880662/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
The last status change happened on accident. The fix has not been released, yet. I cannot change the status back to "Fix Committed" though. Can anyone help with this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760848] Re: lxc-create can't create bionic container on xenial
In my case the underlying host is an ubuntu 16.04. I don't know, if that can cause trouble? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760848 Title: lxc-create can't create bionic container on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1760848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629818] [NEW] mpt-statusd reports RAID changes even when there is no RAID
Public bug reported: when using the mpt-statusd on a server, which has the RAID hardware installed but currently no disks attached, it will continuously send out emails stating that: "This is a RAID status update from mpt-statusd. The mpt-status program reports that one of the RAIDs changed state: Report from /etc/init.d/mpt-statusd on ..." This message comes up every 5 minutes, even though the status of the RAID can't have changed. Line 51 in the /etc/init/mpt.statusd file is the problem here: 48 # Check ever $PERIOD seconds, send email on every status 49 # change and repeat ever $REMIND seconds if the raid is still 50 # bad. 51 if (mpt-status -i $ID) |grep -q 'state OPTIMAL' ; then 52 BADRAID=false 53 else 54 BADRAID=true 55 logger -t mpt-statusd "detected non-optimal RAID status" 56 fi The "grep" in line 51 return 1, even if there is no output of mpt-status at all. This is normal behaviour of grep though. But i think the script should also check, if there is ANY output at all. Because it it doesn't, it will continue to send out emails. I know, i could uninstall it or do some other things to avoid this situation, but there are some reasons why it make sense to have it running on those machines. - if someone temporarily removes the drives or put some drive in the server at a later point of time, it is easy to forget about the statusd - in times of ansible, puppet, and other, more scripts are just checking for hardware and installing packages like statusd automatically - the email is just wrong. there is no changed state. it is a bug - other people might have more reasons - I would expect that the statusd is not reporting on any changes or alike, if there is no RAID configured or disks attached. - # lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 - # apt-cache policy mpt-status mpt-status: Installed: 1.2.0-8 Candidate: 1.2.0-8 Version table: *** 1.2.0-8 500 500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status 1.2.0-4.2.hwraid1 500 500 http://hwraid.le-vert.net/ubuntu wily/main amd64 Packages ** Affects: mpt-status (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629818 Title: mpt-statusd reports RAID changes even when there is no RAID To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpt-status/+bug/1629818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624262] Re: clamav unable to create pid file using systemd
I forgot to mention that the above solution works within our LXC guest environments, but it is not sufficient when running on physical hardware. It seems, that the clamav startup scripts are executed a bit too early. When they are started, the folder /run or /var/run is not yet a tmpfs. So the PID files will be written to the harddisk instead of the tmpfs. When the system is now putting the tmpfs over /run the PIDs are virtually gone and the monitoring service is unable to see them. The systemd scripts clamav-daemon.service and clamav-freshclam.service both require clamav-daemon.socket, so it is necessary to postpone the execution of it a little bit. I have added the following line to /lib/systemd/system/clamav-daemon.socket: After=network.target Honestly I don't know which service is the best one to wait for here. I just chose network.target, because I knew it is going to be late enough. Maybe someone has a better idea here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624262 Title: clamav unable to create pid file using systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1624262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624262] [NEW] clamav unable to create pid file using systemd
Public bug reported: We are using clamav-daemon as well as clamav-freshclam on Ubuntu 16.04. Because we like to monitor those processes with monit we need the PID files. So when booting the system, we never get the PID files, because the services are unable to write into the default /var/run/clamav folder. The message in the log files is "ERROR: Can't save PID in file /var/run/clamav/clamd.pid". When we (re-)start the services manually with e.g. "service clamav- daemon restart", everything works. There are two different problems here: 1. the init script /etc/init.d/clamav-daemon is changing the permissions on the folder /var/run/clamav no matter if you start/stop/restart or whatsoever, BUT the systemd script used at boot time in /lib/systemd/system/clamav-daemon.service is not. So it won't be able to create the PID file. 2. folder /var/run is a tmpfs and will be created with every reboot, so changing the permissions once, won't last long. The systemd or init script has to change the permissions itself. So one solutions could be to add the following two lines to /lib/systemd/system/clamav-daemon.service and /lib/systemd/system/clamav-freshclam.service ExecStartPre=/bin/mkdir -p /var/run/clamav ExecStartPre=/bin/chown clamav /var/run/clamav ** Affects: clamav (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624262 Title: clamav unable to create pid file using systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1624262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598506] Re: apparmor profile prevents fwknop-server from starting
If you run fwknopd within an LXC container for example, the problem does NOT occur. Maybe the underlying apparmor rules for the container allow certain operations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598506 Title: apparmor profile prevents fwknop-server from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwknop/+bug/1598506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598506] Re: apparmor profile prevents fwknop-server from starting
This problem only occurs if the package "fwknop-apparmor-profile" is installed as well, which is creating the apparmor profile for fwknopd in /etc/apparmor.d/usr.sbin.fwknopd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598506 Title: apparmor profile prevents fwknop-server from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwknop/+bug/1598506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598506] Re: apparmor profile prevents fwknop-server from starting
The problems seems to be apparmor, which is restricting permissions. Problem can be solved by changing the file /etc/apparmor.d/usr.sbin.fwknopd and add the following lines: /run/xtables.lock rwk, network inet dgram, network inet6 dgram, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598506 Title: apparmor profile prevents fwknop-server from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwknop/+bug/1598506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576583] [NEW] vim paste option bracks expandtab option
Public bug reported: i am using ubuntu xenial. when I use vim options at the end of a file like the following: # vim: syntax=yaml ts=2 sw=2 et sr softtabstop=2 autoindent paste it should convert an entered tab into spaces (pressing tab should result into 2 spaces). in the past it actually did. currently it does not anymore. the problem here seems to be the last option "paste". if i leave out the paste options the expandtab (et) option works again. the paste option should not have any effect on the expandtab option though. steps to reproduce: - create a file with "# vim: syntax=yaml ts=2 sw=2 et sr softtabstop=2 autoindent paste" at the end of the file. - save it - reopen it with vim - in insert mode: press tab key - the tab should have been converted into 2 spaces (but it doesn't) - remove the paste option "# vim: syntax=yaml ts=2 sw=2 et sr softtabstop=2 autoindent" - save it - reopen it with vim - in insert mode: press tab key again - now the tab is converted into 2 spaces ** Affects: vim (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576583 Title: vim paste option bracks expandtab option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1576583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576567] [NEW] Monit template for postfix has wrong path
Public bug reported: The monit template for postfix in /etc/monit/conf-available/postfix is not up-to-date anymore. it checks for the master file as follows: check file master_bin with path /usr/lib/postfix/master group postfix include /etc/monit/templates/rootbin the problem is, that the master file moved to "/usr/lib/postfix/sbin/master". The wrong path leads to Process 'postfix' Initializing - start pending File 'master_bin' Does not exist ** Affects: monit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576567 Title: Monit template for postfix has wrong path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monit/+bug/1576567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318317] [NEW] openipmi startup script removes kernel modules
Public bug reported: I need some IPMI kernel modules, so I load them during startup. This worked quite well until I upgraded to Ubuntu 14.04. As you can see I have the modules in /etc/modules: # grep ipmi /etc/modules ipmi_watchdog ipmi_devintf ipmi_poweroff ipmi_si Right after reboot, the modules are there: # lsmod |grep -i ipm ipmi_si53257 2 ipmi_poweroff 14366 0 ipmi_devintf 17572 0 ipmi_watchdog 24912 0 but disappear after a few seconds/minute. I found out, that the cause is the /etc/init.d/openipmi script. The behaviour of the script is quite strange because a stop/start will behave differently then a restart. I loaded the modules manually using modprobe: ipmi_si53257 2 ipmi_poweroff 14366 0 ipmi_devintf 17572 0 ipmi_watchdog 24912 0 when I execute: # service openipmi stop the module ipmi_devintf gets removed: ipmi_si53257 2 ipmi_poweroff 14366 0 ipmi_watchdog 24912 0 starting the service again with: # service openipmi start will remove ALL IPMI kernel modules: # lsmod |grep -i ipm # One of the reasons seems to be the module ipmi_msghandler. This is already integrated and causes some of the problems. When I remove it from /etc/init.d/openipmi like this: 65,66c65 #MODULES_BASE=ipmi_msghandler MODULES_BASE= --- MODULES_BASE=ipmi_msghandler 325,326c324,325 # modprobe ipmi_msghandler /dev/null 21 # modules_loaded ipmi_msghandler --- modprobe ipmi_msghandler /dev/null 21 modules_loaded ipmi_msghandler stoping and starting the service works again. But restarting the service will still remove all modules and will not load them anymore. ** Affects: ejabberd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318317 Title: openipmi startup script removes kernel modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1318317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318168] [NEW] su: Failed to create session: No such file or directory
Public bug reported: I am using the command su quite often without any problems. The following su is just a senseless example, but it will demonstrate the problem quite well. In this example I want to make an echo as sshd user (could be any other user like www-data, rabbitmq, or others as well): su sshd -s /bin/sh -c echo Doing this worked find, but beginning with Ubuntu 14.04, I get strange log entries in /var/log/auth.log like: May 10 14:21:18 abel su[22315]: Successful su for sshd by root May 10 14:21:18 abel su[22315]: + /dev/pts/2 root:sshd May 10 14:21:18 abel su[22315]: pam_unix(su:session): session opened for user sshd by root(uid=0) May 10 14:21:18 abel su[22315]: pam_systemd(su:session): Failed to create session: No such file or directory May 10 14:21:18 abel su[22315]: pam_unix(su:session): session closed for user sshd Especially the 4th line with Failed to create session: No such file or directory didn't appear on earlier system. With Ubuntu 13.10 it looked like this: May 10 14:22:30 davy su[18202]: Successful su for sshd by root May 10 14:22:30 davy su[18202]: + /dev/pts/1 root:sshd May 10 14:22:30 davy su[18202]: pam_unix(su:session): session opened for user sshd by root(uid=0) May 10 14:22:30 davy su[18202]: pam_unix(su:session): session closed for user sshd the /etc/passwd for user sshd is the same on 13.10 and 14.04: sshd:x:103:65534::/var/run/sshd:/usr/sbin/nologin Changing shell to /bin/false or /bin/sh or alike doesn't help. The problem is, that certain monitoring or security systems don't this entry and are complaining all the time. ** Affects: ejabberd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318168 Title: su: Failed to create session: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1318168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318168] Re: su: Failed to create session: No such file or directory
Maybe I should add, that this problem occurs on a LXC guest system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318168 Title: su: Failed to create session: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1318168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1279819] [NEW] php5-fpm reload kills master process without its children
Public bug reported: php-fpm uses a master process to control its children. the problem is, that a service reload is going to kill this master process without recovering it or killing its children. here is an example: # ps aux|grep fpm root 20590 1.3 0.0 190264 22380 ?Ss 14:54 0:00 php-fpm: master process (/etc/php5/fpm/php-fpm.conf) www-data 20592 0.0 0.0 190264 14456 ?S14:54 0:00 php-fpm: pool www www-data 20593 0.0 0.0 190264 14456 ?S14:54 0:00 php-fpm: pool www www-data 20594 0.0 0.0 190264 14456 ?S14:54 0:00 php-fpm: pool www www-data 20595 0.0 0.0 190264 14456 ?S14:54 0:00 php-fpm: pool www root 20597 0.0 0.0 118224 948 pts/2S+ 14:54 0:00 grep --color=auto fpm FPM is running, but if I do a reload now, the master will disappear # service php5-fpm reload # ps aux|grep fpm www-data 22316 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www www-data 22317 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www www-data 22318 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www www-data 22319 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www root 22418 0.0 0.0 118224 948 pts/2S+ 14:59 0:00 grep --color=auto fpm when this happens, there is basically no easy way of reloading or restarting or stopping this service again, because even a restart cannot find them anymore: # service php5-fpm restart stop: Unknown instance: php5-fpm start/running, process 23494 root@davy ~ # ps aux|grep fpm www-data 22316 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www www-data 22317 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www www-data 22318 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www www-data 22319 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www root 23949 0.0 0.0 118224 948 pts/2S+ 15:00 0:00 grep --color=auto fpm the master service is still gone. if i use a restart or stop/start only, everything seems to work find. The bug seems to be in reload functionality only. # lsb_release -rd Description:Ubuntu 13.10 Release:13.10 # apt-cache policy php5-fpm php5-fpm: Installed: 5.5.3+dfsg-1ubuntu2.1 Candidate: 5.5.3+dfsg-1ubuntu2.1 Version table: *** 5.5.3+dfsg-1ubuntu2.1 0 500 http://mirror.hetzner.de/ubuntu/packages/ saucy-updates/universe amd64 Packages 500 http://mirror.hetzner.de/ubuntu/security/ saucy-security/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu/ saucy-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ saucy-security/universe amd64 Packages 100 /var/lib/dpkg/status 5.5.3+dfsg-1ubuntu2 0 500 http://mirror.hetzner.de/ubuntu/packages/ saucy/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: php5 php5-fpm reload service ** Tags added: php5 ** Tags added: php5-fpm reload service -- 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/1279819 Title: php5-fpm reload kills master process without its children To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1279819/+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 1279819] [NEW] php5-fpm reload kills master process without its children
Public bug reported: php-fpm uses a master process to control its children. the problem is, that a service reload is going to kill this master process without recovering it or killing its children. here is an example: # ps aux|grep fpm root 20590 1.3 0.0 190264 22380 ?Ss 14:54 0:00 php-fpm: master process (/etc/php5/fpm/php-fpm.conf) www-data 20592 0.0 0.0 190264 14456 ?S14:54 0:00 php-fpm: pool www www-data 20593 0.0 0.0 190264 14456 ?S14:54 0:00 php-fpm: pool www www-data 20594 0.0 0.0 190264 14456 ?S14:54 0:00 php-fpm: pool www www-data 20595 0.0 0.0 190264 14456 ?S14:54 0:00 php-fpm: pool www root 20597 0.0 0.0 118224 948 pts/2S+ 14:54 0:00 grep --color=auto fpm FPM is running, but if I do a reload now, the master will disappear # service php5-fpm reload # ps aux|grep fpm www-data 22316 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www www-data 22317 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www www-data 22318 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www www-data 22319 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www root 22418 0.0 0.0 118224 948 pts/2S+ 14:59 0:00 grep --color=auto fpm when this happens, there is basically no easy way of reloading or restarting or stopping this service again, because even a restart cannot find them anymore: # service php5-fpm restart stop: Unknown instance: php5-fpm start/running, process 23494 root@davy ~ # ps aux|grep fpm www-data 22316 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www www-data 22317 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www www-data 22318 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www www-data 22319 0.0 0.0 190264 14456 ?S14:57 0:00 php-fpm: pool www root 23949 0.0 0.0 118224 948 pts/2S+ 15:00 0:00 grep --color=auto fpm the master service is still gone. if i use a restart or stop/start only, everything seems to work find. The bug seems to be in reload functionality only. # lsb_release -rd Description:Ubuntu 13.10 Release:13.10 # apt-cache policy php5-fpm php5-fpm: Installed: 5.5.3+dfsg-1ubuntu2.1 Candidate: 5.5.3+dfsg-1ubuntu2.1 Version table: *** 5.5.3+dfsg-1ubuntu2.1 0 500 http://mirror.hetzner.de/ubuntu/packages/ saucy-updates/universe amd64 Packages 500 http://mirror.hetzner.de/ubuntu/security/ saucy-security/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu/ saucy-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ saucy-security/universe amd64 Packages 100 /var/lib/dpkg/status 5.5.3+dfsg-1ubuntu2 0 500 http://mirror.hetzner.de/ubuntu/packages/ saucy/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: php5 php5-fpm reload service ** Tags added: php5 ** Tags added: php5-fpm reload service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279819 Title: php5-fpm reload kills master process without its children To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1279819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924337] Re: lxc on precise is not working with lucid containers (container does not reach runlevel 2)
Is it possible that this bug returned? I updated the host to ubuntu saucy and lxc was working fine with the virtual machine jenkins. Once I updated the guest system to saucy as well, it seemed not to boot, but I was wrong. It never reached the runlevel (5), which it did before. Here is the output of lxc-ls # lxc-ls --fancy NAME STATEIPV4 IPV6 AUTOSTART - jenkinsRUNNING 192.168.1.30 - NO php-54-32 STOPPED - - NO test STOPPED - - NO as you can see it is running, but not reachable by ssh. so I entered: # lxc-attach -n jenkins -- runlevel unknown it doesn't know in which runlevel it is. even though the network is up within the guest system: # lxc-attach -n jenkins -- ifconfig eth0 Link encap:Ethernet HWaddr 10:16:3e:53:5b:7a inet addr:192.168.1.30 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::1216:3eff:fe53:5b7a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:277 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:44733 (44.7 KB) TX bytes:648 (648.0 B) as soon as I force the runlevel with: lxc-attach -n jenkins -- init 5 everything is working, until I reboot the guest again. -- 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/924337 Title: lxc on precise is not working with lucid containers (container does not reach runlevel 2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337/+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
Re: [Bug 1242074] [NEW] lxc-ls shows wrong status
it was autostarted Sent from my iPad On 20.10.2013, at 22:12, Serge Hallyn 1242...@bugs.launchpad.net wrote: Thanks for submitting this bug. Can you confirm whether the jenkins machine was auto-started by lxc-instance? If not, can you please run 'apport-collect 1242074' to have apport upload more information, and tell us the path and type of container, and how you created and started it? status: incomplete ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1242074 Title: lxc-ls shows wrong status Status in “lxc” package in Ubuntu: Incomplete Bug description: I just upgraded to ubuntu saucy and found a strange behaviour. The command lxc-ls doesn't show the correct status of running machines. as you can see my output for jenkins is stopped, but I am logged into the system (jenkins) at the very same moment, so it is running. I can also do thinks within the virtual machine, but the status doesn't change. # lxc-ls --fancy NAME STATEIPV4 IPV6 AUTOSTART - jenkinsSTOPPED - - NO php-54-32 STOPPED - - NO test STOPPED - - NO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions -- 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/1242074 Title: lxc-ls shows wrong status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+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 924337] Re: lxc on precise is not working with lucid containers (container does not reach runlevel 2)
Is it possible that this bug returned? I updated the host to ubuntu saucy and lxc was working fine with the virtual machine jenkins. Once I updated the guest system to saucy as well, it seemed not to boot, but I was wrong. It never reached the runlevel (5), which it did before. Here is the output of lxc-ls # lxc-ls --fancy NAME STATEIPV4 IPV6 AUTOSTART - jenkinsRUNNING 192.168.1.30 - NO php-54-32 STOPPED - - NO test STOPPED - - NO as you can see it is running, but not reachable by ssh. so I entered: # lxc-attach -n jenkins -- runlevel unknown it doesn't know in which runlevel it is. even though the network is up within the guest system: # lxc-attach -n jenkins -- ifconfig eth0 Link encap:Ethernet HWaddr 10:16:3e:53:5b:7a inet addr:192.168.1.30 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::1216:3eff:fe53:5b7a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:277 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:44733 (44.7 KB) TX bytes:648 (648.0 B) as soon as I force the runlevel with: lxc-attach -n jenkins -- init 5 everything is working, until I reboot the guest again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924337 Title: lxc on precise is not working with lucid containers (container does not reach runlevel 2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1242074] [NEW] lxc-ls shows wrong status
it was autostarted Sent from my iPad On 20.10.2013, at 22:12, Serge Hallyn 1242...@bugs.launchpad.net wrote: Thanks for submitting this bug. Can you confirm whether the jenkins machine was auto-started by lxc-instance? If not, can you please run 'apport-collect 1242074' to have apport upload more information, and tell us the path and type of container, and how you created and started it? status: incomplete ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1242074 Title: lxc-ls shows wrong status Status in “lxc” package in Ubuntu: Incomplete Bug description: I just upgraded to ubuntu saucy and found a strange behaviour. The command lxc-ls doesn't show the correct status of running machines. as you can see my output for jenkins is stopped, but I am logged into the system (jenkins) at the very same moment, so it is running. I can also do thinks within the virtual machine, but the status doesn't change. # lxc-ls --fancy NAME STATEIPV4 IPV6 AUTOSTART - jenkinsSTOPPED - - NO php-54-32 STOPPED - - NO test STOPPED - - NO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242074 Title: lxc-ls shows wrong status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242074] [NEW] lxc-ls shows wrong status
Public bug reported: I just upgraded to ubuntu saucy and found a strange behaviour. The command lxc-ls doesn't show the correct status of running machines. as you can see my output for jenkins is stopped, but I am logged into the system (jenkins) at the very same moment, so it is running. I can also do thinks within the virtual machine, but the status doesn't change. # lxc-ls --fancy NAME STATEIPV4 IPV6 AUTOSTART - jenkinsSTOPPED - - NO php-54-32 STOPPED - - NO test STOPPED - - NO ** 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/1242074 Title: lxc-ls shows wrong status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+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 1242074] [NEW] lxc-ls shows wrong status
Public bug reported: I just upgraded to ubuntu saucy and found a strange behaviour. The command lxc-ls doesn't show the correct status of running machines. as you can see my output for jenkins is stopped, but I am logged into the system (jenkins) at the very same moment, so it is running. I can also do thinks within the virtual machine, but the status doesn't change. # lxc-ls --fancy NAME STATEIPV4 IPV6 AUTOSTART - jenkinsSTOPPED - - NO php-54-32 STOPPED - - NO test STOPPED - - NO ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242074 Title: lxc-ls shows wrong status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241632] [NEW] LDAP support auth not working
Public bug reported:
I updated to ubuntu saucy and after the update, the LDAP auth is not
working anymore. I didn't change the configuration and the LDAP itself
is running and working for many other services. Only ejabberd is unable
to bind.
The following log entries repeat constantly without users trying to
access the system.
=INFO REPORT 2013-10-18 13:17:31 ===
I(0.291.0:eldap:983) : LDAP connection on bohr.teqneers.de:389
=WARNING REPORT 2013-10-18 13:17:31 ===
W(0.288.0:eldap:931) : LDAP bind failed on bohr.teqneers.de:389
Reason: {undef,[{asn1rt_ber_bin,decode_tag,
[48,13,2,2,3,49,97,7,10,1,0,4,0,4,0],
[]},
{eldap,check_tag,1,[{file,eldap.erl},{line,911}]},
{eldap,recvd_wait_bind_response,2,
[{file,eldap.erl},{line,876}]},
{eldap,handle_info,3,[{file,eldap.erl},{line,571}]},
{gen_fsm,handle_msg,7,[{file,gen_fsm.erl},{line,505}]},
{proc_lib,init_p_do_apply,3,
[{file,proc_lib.erl},{line,239}]}]}
=INFO REPORT 2013-10-18 13:17:31 ===
I(0.38.0:ejabberd_app:89) : ejabberd 2.1.10 is stopped in the node
ejabberd@bohr
== /var/log/ejabberd/erlang.log ==
supervisor: {local,ejabberd_sup}
started: [{pid,0.493.0},
{name,'ejabberd_mod_caps_chat.teqneers.de'},
{mfargs,{mod_caps,start_link,[chat.teqneers.de,[]]}},
{restart_type,transient},
{shutdown,1000},
{child_type,worker}]
=PROGRESS REPORT 18-Oct-2013::13:10:20 ===
supervisor: {local,ejabberd_sup}
started: [{pid,0.500.0},
{name,'ejabberd_mod_irc_sup_chat.teqneers.de'},
{mfargs,
{ejabberd_tmp_sup,start_link,
['ejabberd_mod_irc_sup_chat.teqneers.de',
mod_irc_connection]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT 18-Oct-2013::13:10:20 ===
supervisor: {local,ejabberd_sup}
started: [{pid,0.501.0},
{name,'ejabberd_mod_irc_chat.teqneers.de'},
{mfargs,{mod_irc,start_link,[chat.teqneers.de,[]]}},
{restart_type,temporary},
{shutdown,1000},
{child_type,worker}]
=PROGRESS REPORT 18-Oct-2013::13:10:20 ===
supervisor: {local,ejabberd_sup}
started: [{pid,0.506.0},
{name,'ejabberd_mod_muc_sup_chat.teqneers.de'},
{mfargs,
{ejabberd_tmp_sup,start_link,
['ejabberd_mod_muc_sup_chat.teqneers.de',
mod_muc_room]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]
=PROGRESS REPORT 18-Oct-2013::13:10:20 ===
supervisor: {local,ejabberd_sup}
started: [{pid,0.507.0},
{name,'ejabberd_mod_muc_chat.teqneers.de'},
{mfargs,
{mod_muc,start_link,
[chat.teqneers.de,
[{access,muc},
{access_create,muc},
{access_persistent,muc},
{access_admin,muc_admin},
{history_size,5000},
{max_users,500},
{default_room_options,
[{allow_change_subj,false},
{allow_private_messages,true},
{allow_user_invites,false},
{anonymous,false},
{logging,true},
{members_by_default,true},
{persistent,false},
{public,false},
{public_list,false}]}]]}},
{restart_type,temporary},
{shutdown,1000},
{child_type,worker}]
** Affects: ejabberd (Ubuntu)
Importance: Undecided
Status: New
** Tags: authentication ldap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241632
Title:
LDAP support auth not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1241632/+subscriptions
--
ubuntu-bugs mailing
[Bug 1241632] Re: LDAP support auth not working
Sorry, forgot my current LDAP conf from ejabberd.conf
%%% ==
%%% AUTHENTICATION
%%
%% auth_method: Method used to authenticate the users.
%% The default method is the internal.
%% If you want to use a different method,
%% comment this line and enable the correct ones.
%%
%%{auth_method, internal}.
%%
%% Authentication using external script
%% Make sure the script is executable by ejabberd.
%%
%%{auth_method, external}.
%%{extauth_program, /path/to/authentication/script}.
%%
%% Authentication using ODBC
%% Remember to setup a database in the next section.
%%
%%{auth_method, odbc}.
%%
%% Authentication using PAM
%%
%%{auth_method, pam}.
%%{pam_service, pamservicename}.
%%
%% Authentication using LDAP
%%
{auth_method, ldap}.
%%
%% List of LDAP servers:
{ldap_servers, [localhost]}.
%%
%% Encryption of connection to LDAP servers (LDAPS):
{ldap_encrypt, none}.
%%{ldap_encrypt, tls}.
%%
%% Port connect to LDAP server:
{ldap_port, 389}.
%%{ldap_port, 636}.
%%
%% LDAP manager:
%%{ldap_rootdn, dc=example,dc=com}.
%%
%% Password to LDAP manager:
%%{ldap_password, }.
%%
%% Search base of LDAP directory:
{ldap_base, ou=group,dc=teqneers,dc=de}.
%%
%% LDAP attribute that holds user ID:
%%{ldap_uids, [{mail, %u...@mail.example.org}]}.
{ldap_uids, [{uid,%u}]}.
%%
%% LDAP filter:
%%{ldap_filter, (objectClass=shadowAccount)}.
{ldap_filter, (objectClass=shadowAccount)}.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241632
Title:
LDAP support auth not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1241632/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1186501] [NEW] LXC won't tear down VETH device on shutdown
Public bug reported:
I am using Ubuntu 13.04 with latest update and the package LXC to run
some virtual machines in it.
I am using the following parameter for one of the machines:
- CONFIG
lxc.network.type=veth
lxc.network.link=br0
lxc.network.flags=up
lxc.network.hwaddr = 10:16:3e:53:5b:7a
lxc.network.veth.pair = veth_jenkins
lxc.network.ipv4 = 192.168.1.30/24
#lxc.network.ipv6 = 2003:db8:1:0:214:1234:fe0b:3597
lxc.rootfs = /var/lib/lxc/jenkins/rootfs
lxc.utsname = jenkins
lxc.devttydir = lxc
lxc.tty = 4
lxc.pts = 1024
lxc.mount = /var/lib/lxc/jenkins/fstab
lxc.arch = amd64
lxc.cap.drop = sys_module mac_admin mac_override
lxc.pivotdir = lxc_putold
# uncomment the next line to run the container unconfined:
#lxc.aa_profile = unconfined
lxc.cgroup.devices.deny = a
# Allow any mknod (but not using the node)
lxc.cgroup.devices.allow = c *:* m
lxc.cgroup.devices.allow = b *:* m
# /dev/null and zero
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
# consoles
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
#lxc.cgroup.devices.allow = c 4:0 rwm
#lxc.cgroup.devices.allow = c 4:1 rwm
# /dev/{,u}random
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 136:* rwm
lxc.cgroup.devices.allow = c 5:2 rwm
# rtc
lxc.cgroup.devices.allow = c 254:0 rwm
#fuse
lxc.cgroup.devices.allow = c 10:229 rwm
#tun
lxc.cgroup.devices.allow = c 10:200 rwm
#full
lxc.cgroup.devices.allow = c 1:7 rwm
#hpet
lxc.cgroup.devices.allow = c 10:228 rwm
#kvm
lxc.cgroup.devices.allow = c 10:232 rwm
lxc.cgroup.memory.limit_in_bytes = 8G
lxc.cgroup.memory.soft_limit_in_bytes = 2G
lxc.cgroup.cpuset.cpus = 0-3
- /CONFIG
When I start this LXC container, the network will be started as expected as you
can see in the ifconfig output:
veth_jenkins Link encap:Ethernet HWaddr fe:31:67:cb:ef:25
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:145 errors:0 dropped:0 overruns:0 frame:0
TX packets:350 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:25708 (25.7 KB) TX bytes:59185 (59.1 KB)
The issue I have is the following: when I shutdown the LXC container, the
veth_jenkins interface stays active and will not teared down with the
machine. This is not so nice, but it is really ugly, if you try to start the
machine again, because then it will not start anymore, because it says, that
the interface name is not unique...of course not, but I would like to not use
random name, because I like to be able to identify the related interfaces.
** Affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
** Tags: interface lxc network virtualization vm
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1186501
Title:
LXC won't tear down VETH device on shutdown
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1186501/+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 1186501] [NEW] LXC won't tear down VETH device on shutdown
Public bug reported:
I am using Ubuntu 13.04 with latest update and the package LXC to run
some virtual machines in it.
I am using the following parameter for one of the machines:
- CONFIG
lxc.network.type=veth
lxc.network.link=br0
lxc.network.flags=up
lxc.network.hwaddr = 10:16:3e:53:5b:7a
lxc.network.veth.pair = veth_jenkins
lxc.network.ipv4 = 192.168.1.30/24
#lxc.network.ipv6 = 2003:db8:1:0:214:1234:fe0b:3597
lxc.rootfs = /var/lib/lxc/jenkins/rootfs
lxc.utsname = jenkins
lxc.devttydir = lxc
lxc.tty = 4
lxc.pts = 1024
lxc.mount = /var/lib/lxc/jenkins/fstab
lxc.arch = amd64
lxc.cap.drop = sys_module mac_admin mac_override
lxc.pivotdir = lxc_putold
# uncomment the next line to run the container unconfined:
#lxc.aa_profile = unconfined
lxc.cgroup.devices.deny = a
# Allow any mknod (but not using the node)
lxc.cgroup.devices.allow = c *:* m
lxc.cgroup.devices.allow = b *:* m
# /dev/null and zero
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
# consoles
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
#lxc.cgroup.devices.allow = c 4:0 rwm
#lxc.cgroup.devices.allow = c 4:1 rwm
# /dev/{,u}random
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 136:* rwm
lxc.cgroup.devices.allow = c 5:2 rwm
# rtc
lxc.cgroup.devices.allow = c 254:0 rwm
#fuse
lxc.cgroup.devices.allow = c 10:229 rwm
#tun
lxc.cgroup.devices.allow = c 10:200 rwm
#full
lxc.cgroup.devices.allow = c 1:7 rwm
#hpet
lxc.cgroup.devices.allow = c 10:228 rwm
#kvm
lxc.cgroup.devices.allow = c 10:232 rwm
lxc.cgroup.memory.limit_in_bytes = 8G
lxc.cgroup.memory.soft_limit_in_bytes = 2G
lxc.cgroup.cpuset.cpus = 0-3
- /CONFIG
When I start this LXC container, the network will be started as expected as you
can see in the ifconfig output:
veth_jenkins Link encap:Ethernet HWaddr fe:31:67:cb:ef:25
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:145 errors:0 dropped:0 overruns:0 frame:0
TX packets:350 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:25708 (25.7 KB) TX bytes:59185 (59.1 KB)
The issue I have is the following: when I shutdown the LXC container, the
veth_jenkins interface stays active and will not teared down with the
machine. This is not so nice, but it is really ugly, if you try to start the
machine again, because then it will not start anymore, because it says, that
the interface name is not unique...of course not, but I would like to not use
random name, because I like to be able to identify the related interfaces.
** Affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
** Tags: interface lxc network virtualization vm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1186501
Title:
LXC won't tear down VETH device on shutdown
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1186501/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1182372] [NEW] WebSVN not compatible with php5-fpm
Public bug reported: WebSVN should be compatible with php5-fpm package, because it is just another php implementation also using a web server to deliver its content (see e.g. phpmyadmin). In the current dependency line Depends: apache2 | httpd, libapache2-mod-php5 | php5 | php5-cgi | libapache2-mod-php4 | php4 (= 4.1.0) | php4-cgi, subversion, debconf (= 0.5) | debconf-2.0, po-debconf, ucf (= 0.8), php-geshi the php5-fpm is missing. would be nice to have that in there as well, otherwise websvn cannot be installed/used with system package. The package phpmyadmin has the following implemented as dependency: Depends: libapache2-mod-php5 | libapache2-mod-php5filter | php5-cgi | php5-fpm | php5, php5-mysql | php5-mysqli | php5-mysqlnd, php5-mcrypt, perl, debconf (= 0.5) | debconf-2.0, ... I am using an Ubuntu 13.04. Package is: websvn: Installed: 2.3.3-1.1 Candidate: 2.3.3-1.1 Version table: *** 2.3.3-1.1 0 500 http://de.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: websvn (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1182372 Title: WebSVN not compatible with php5-fpm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/websvn/+bug/1182372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1182372] Re: WebSVN not compatible with php5-fpm
The same problem exists with phppgadmin. This package is also unable to cope with php5-fpm, but it should. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1182372 Title: WebSVN not compatible with php5-fpm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/websvn/+bug/1182372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
