[Bug 280053] Re: xinetd enabled is not overruled by disable in service declaration
Where in the documentation does it say that the disable = yes takes precedence? In the quoted text: Note that the service disable attribute and DISABLE flag can prevent a service from being enabled despite being listed in this attribute. It _can_ prevent a service from being enabled, but not it _will_, meaning that no deterministic behaviour is indicated for this case. ** Changed in: xinetd (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xinetd in Ubuntu. https://bugs.launchpad.net/bugs/280053 Title: xinetd enabled is not overruled by disable in service declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinetd/+bug/280053/+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 982704] Re: package samba-common-bin 2:3.6.3-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: samba (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/982704 Title: package samba-common-bin 2:3.6.3-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/982704/+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 1241641] Re: package apache2 2.4.6-2ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apache2 (Ubuntu) Status: New = Confirmed -- 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/1241641 Title: package apache2 2.4.6-2ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1241641/+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 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
[Bug 920749]
Hello, is there a workaround for this issue? I want to be able to send some VAR* variables but it seems impossible at the moment. I have tried many different configurations. Is there any PAM conf change I can do to disable this behaviour and allow me to inject variables? Regards Alessandro -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/920749 Title: pam configuration for SSH prevents LANG override To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/920749/+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 1242363] [NEW] Puppet package needs ruby-hiera (unmapped dep)
Public bug reported: Puppet does not work without ruby-hiera package, but it also does not have this dependency mapped: $ sudo apt-get install puppet-common $ sudo puppet apply /etc/puppet/manifests/site.pp --verbose Info: Loading facts in /etc/puppet/modules/php/lib/facter/php_config.rb Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/root_home.rb Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/pe_version.rb Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb Error: Puppet::Parser::AST::Resource failed with error RuntimeError: Hiera terminus not supported without hiera library at /etc/puppet/manifests/abstracts.pp:10 on node graphite.local Error: Puppet::Parser::AST::Resource failed with error RuntimeError: Hiera terminus not supported without hiera library at /etc/puppet/manifests/abstracts.pp:10 on node graphite.local Need to install ruby-hiera to be able to run $ sudo apt-get install ruby-hiera ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: puppet 3.2.4-2ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 20 12:30:10 2013 InstallationDate: Installed on 2013-10-19 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: puppet UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: puppet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1242363 Title: Puppet package needs ruby-hiera (unmapped dep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1242363/+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 1242365] [NEW] dovecot imapd process crashes using dovecot-solr
Public bug reported: I had my dovecot successfully configured for using solr for fulltext search with dovecot on my ubuntu 13.04. Now I have upgraded to 13.10 and I now see this in the log crashing the imapd process(and I don't quite understand why maxfd can less than zero. I Did try disable apparmor but it didn't help): Oct 20 16:38:11 pris dovecot: imap(hhj): Panic: file solr-connection.c: line 545 (solr_connection_post_more): assertion failed: (maxfd = 0) Oct 20 16:38:11 pris dovecot: imap(hhj): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x3b297) [0x7fdab6a1e297] - /usr/lib/dovecot/libdovecot.so.0(+0x3b35e) [0x7fdab6a1e35e] - /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fdab69f6763] - /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(solr_connection_post_more+0x259) [0x7fdab53891b9] - /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(solr_connection_post+0x27) [0x7fdab5389377] - /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(+0x415f) [0x7fdab538615f] - /usr/lib/dovecot/libdovecot-storage.so.0(+0x41d3c) [0x7fdab6caad3c] - /usr/lib/dovecot/libdovecot-storage.so.0(+0x46ca0) [0x7fdab6cafca0] - /usr/lib/dovecot/libdovecot-storage.so.0(maildir_file_do+0x3d) [0x7fdab6cb00dd] - /usr/lib/dovecot/libdovecot-storage.so.0(maildir_sync_index+0x2d1) [0x7fdab6cab361] - /usr/lib/dovecot/libdovecot-storage.so.0(+0x41028) [0x7fdab6caa028] - /usr/lib/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xdd) [0x7fdab6c aa74d] - /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x29) [0x7fdab6cd7309] - /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7fdab6cd7417] - dovecot/imap(cmd_select_full+0x137) [0x7fdab7195407] - dovecot/imap(command_exec+0x3c) [0x7fdab719905c] - dovecot/imap(+0x1107b) [0x7fdab719807b] - dovecot/imap(+0x1112d) [0x7fdab719812d] - dovecot/imap(client_handle_input+0x12d) [0x7fdab71983dd] - dovecot/imap(client_input+0x65) [0x7fdab7198ba5] - /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x27) [0x7fdab6a2a9f7] - /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) [0x7fdab6a2b6e7] - /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7fdab6a2a5f8] - /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fdab6a17ae3] - dovecot/imap(main+0x2ba) [0x7fdab719084a] - /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fdab663cde5] - dovecot/imap(+0x99b4) [0x7fdab71909b4] Oct 20 16:38:11 pris dovecot: imap(hhj): Fatal: master: service(imap): child 4788 killed with signal 6 (core dumped) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: dovecot-solr 1:2.1.7-7ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 20 16:46:40 2013 InstallationDate: Installed on 2011-06-24 (848 days ago) InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64 (20110426) MarkForUpload: True SourcePackage: dovecot UpgradeStatus: Upgraded to saucy on 2013-10-20 (0 days ago) ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1242365 Title: dovecot imapd process crashes using dovecot-solr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1242365/+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 1241963] Re: package spamassassin 3.3.2-6ubuntu2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1241963 Title: package spamassassin 3.3.2-6ubuntu2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1241963/+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 1242153] Re: package nova-common 1:2013.2~rc2-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1242153 Title: package nova-common 1:2013.2~rc2-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1242153/+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 1241957] Re: package squid3 3.3.8-1ubuntu3 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1241957 Title: package squid3 3.3.8-1ubuntu3 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1241957/+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 1242376] Re: reload php5-fpm crashes
Note that the move to upstart for php5-fpm happened with Ubuntu 13.10 Its not relevant for older releases. -- 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/1242376 Title: reload php5-fpm crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1242376/+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 1242376] [NEW] reload php5-fpm crashes
Public bug reported: reload php5-fpm with upstart does not work. php5-fpm will crash and leave non-working child processes hanging around that will block any recovery until they are killed off manually. This is because php5-fpm does not handle SIGHUP. It results in an uncontrolled exit. After telling upstart to instead use SIGUSR2 on reload*, things work as expected. * reload signal SIGUSR2 in upstart php5-fpm.conf Signals handled by php5-fpm seems to be: * SIGINT, SIGTERM: immediate termination * SIGQUIT: graceful stop * SIGUSR1: re-open log file * SIGUSR2: graceful reload of all workers + reload of fpm conf/binary Ubuntu 13.10, amd64 ii php5-fpm 5.5.3+dfsg-1ubuntu2 amd64 server-side, HTML-embedded scripting language (FPM-CGI binary) ** 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/1242376 Title: reload php5-fpm crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1242376/+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 1242365] Re: dovecot imapd process crashes using dovecot-solr
Sorry. I think this bug can be closed. It works now. I think it just needed to be reindexed ** Changed in: dovecot (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1242365 Title: dovecot imapd process crashes using dovecot-solr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1242365/+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 280053] Re: xinetd enabled is not overruled by disable in service declaration
I reported it because I believe that disable should take precedence from my reading of the man-page. Furthermore making disable overrule enable is the most secure thing to do if there is any ambiguity about whether a service should be enabled or disabled in the configuration file. If you have read the entire man-page and determined that my understanding is wrong, please feel free to close the bug. I have no need to argue further about a 5 year old bug-report that no one has looked at in 4 years, and which exists in a piece of unloved legacy software. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xinetd in Ubuntu. https://bugs.launchpad.net/bugs/280053 Title: xinetd enabled is not overruled by disable in service declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinetd/+bug/280053/+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 1242363] Re: Puppet package needs ruby-hiera (unmapped dep)
Correct. This packaging bug was fixed in the debian repository just before the 3.3.0-1 release, with commit id 11a376f8348dfa2c254b19f7b29aec13940aeb92. The ruby-hiera dependency was moved from the puppetmaster-common package to the puppet-common package. Previously, this was only needed by the puppet master, and the dependency was not moved to the correct place until 3.3.0-1 See also http://anonscm.debian.org/gitweb/?p=pkg- puppet/puppet.git;a=commitdiff;h=11a376f8348dfa2c254b19f7b29aec13940aeb92 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1242363 Title: Puppet package needs ruby-hiera (unmapped dep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1242363/+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
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 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
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 1242363] Re: Puppet package needs ruby-hiera (unmapped dep)
Thank you for taking the time to report this bug and helping to make Ubuntu better. I can run puppet apply with an empty manifest and also a trivial manifest with a single static file defined, using puppet-common 3.2.4-2ubuntu2 on Saucy and without ruby-hiera installed. What exactly is the failure case here, please? What do you have in /etc/puppet/manifests/abstracts.pp:10? If you have something that specifically needs hiera, but puppet doesn't need hiera in all cases, then shouldn't this be at best a recommendation rather than a hard dependency? We should certainly pick up the ruby-hiera dependency in puppet-common on the next merge from Debian for Trusty, as I see no reason to diverge from Debian on this. But do we need Saucy fixed? If so, what is the justification, please? Triaged for Trusty, since we should merge Debian's ruby-hiera dependency. ** Changed in: puppet (Ubuntu) Status: New = Triaged ** Changed in: puppet (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1242363 Title: Puppet package needs ruby-hiera (unmapped dep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1242363/+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 1242376] Re: reload php5-fpm crashes
Thank you for taking the time to report this bug and helping to make Ubuntu better. Confirmed: php5-fpm(8) documents USR2 as the reload signal, and the upstart script defaults to HUP. Workaround (untested): add the line reload signal USR2 to /etc/init/php5-fpm.conf. This also exists in Debian so should be filed there too. I'll do it when I look at fixing this in Ubuntu, unless someone else gets to it first. ** Changed in: php5 (Ubuntu) Status: New = Triaged ** Changed in: php5 (Ubuntu) Importance: Undecided = High -- 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/1242376 Title: reload php5-fpm crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1242376/+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 1242363] Re: Puppet package needs ruby-hiera (unmapped dep)
Hi,
I'm not using nothing specific to Hiera, but I don't know if some 3rd
party module is (stdlib?).
There are the first 15 lines of the abstracts.pp file:
node 'debian-like-linux' {
class { 'apt':
always_apt_update= false,
disable_keys = undef,
proxy_host = false,
proxy_port = '8080',
purge_preferences_d = false,
purge_sources_list = false,
purge_sources_list_d = false,
}
sysctl { 'fs.file-max': value = '999' }
sysctl { 'fs.inotify.max_user_watches': value = '10' }
sysctl { 'fs.nr_open': value = '999' }
sysctl { 'net.core.netdev_max_backlog': value = '4096' }
sysctl { 'net.core.rmem_max': value= '16777216' }
...
}
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1242363
Title:
Puppet package needs ruby-hiera (unmapped dep)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1242363/+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] Re: lxc-ls shows wrong status
Drat my comment got lost. The lxc-instance job ends up starting containers as 'anonymous'. You can see them using lxc-list -P /var/lib/lxc_anon The autostart code is currently being reworked but I think this is worth fixing in older releases. It coudl be fixed in one of two ways - or both: the lxc-instance job could detect that linked file is a standard container's config and start it that way (without specifying -f); or lxc-start could detect that the passed-in rcfile is a link to a standard $lxcpath/$name/config, and not start the container anonymously. ** Changed in: lxc (Ubuntu) Importance: Undecided = Medium ** Changed in: lxc (Ubuntu) Status: Incomplete = Triaged -- 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
