[Bug 1170585] Re: whitelist incorrect rule
Well, now that I use the tool above, I don't have the WL issue anylonger (yeah, I forgot to say it in the first place). The only issue I could find up to now is WL with vars having '[', ']' in their names. There's an open bug report on their Google code place. And even applying the workaround from there fails. Likely a told old naxsi release. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1170585 Title: whitelist incorrect rule To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1170585/+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 750786] Re: nmbd job fails to start on boot
** Changed in: samba (Ubuntu) Status: Expired => 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/750786 Title: nmbd job fails to start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/750786/+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 1315254] Re: package python-samba 2:4.1.6+dfsg-1ubuntu2 failed to install/upgrade: yeni pre-removal betiği alt işlemi çıkış durumunda hata döndürdü : 139
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that a package failed to install due to a segmentation fault in the application being used for the package installation process. Unfortunately, this bug report isn't very useful in its current state and a crash report would be much more useful. Could you try recreating this issue by enabling apport to catch the crash report 'sudo service apport start force_start=1' and then trying to install the same package again? This process will create a new bug report so I am marking this one as Invalid. Thanks again for helping out! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: package-install-segfault ** Changed in: samba (Ubuntu) Status: New => Invalid -- 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/1315254 Title: package python-samba 2:4.1.6+dfsg-1ubuntu2 failed to install/upgrade: yeni pre-removal betiği alt işlemi çıkış durumunda hata döndürdü : 139 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1315254/+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 1272857] Re: apache2 crashed with SIGSEGV in ()
Now I could sharpen the problem. It only shows up if using AuthPG libapache2-mod-auth-pgsql in connection with a cgi script. To reproduce put the following in /etc/apache2/conf.d/authpgtest.conf and then execute a2enconf authpgtest.conf and service apache2 reload . Alias /authpgtest /export/scratch/authpgtest Options +ExecCGI +FollowSymLinks AddHandler cgi-script .pl AuthName "TestRealm" AuthType Basic AuthBasicProvider pgsql Auth_PG_host /var/run/postgresql Auth_PG_port 5432 Auth_PG_database authpgtestdb Auth_PG_pwd_table ident_users Auth_PG_uid_field uname Auth_PG_pwd_field password Auth_PG_encrypted off Require valid-user Of course the postgres db authpgtestdb with table ident_users with columns uname and password have to exist, or the params adapted. Under /export/scratch/authpgtest/hw.pl put the follwing. #!/usr/bin/perl print "Content-type: text/html\n\n"; print "Hello, World!\n"; Then call http:///authpgtest/hw.pl in your browser while tail -f tail -f /var/log/apache2/error.log is running. Press the reload button of the browser a few times. Without using AuthPG-Realm I think the errors do not show up. Unfortunately, I need this for production and a workaround seems not to doable. Chris -- 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/1272857 Title: apache2 crashed with SIGSEGV in () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1272857/+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 750786] Re: nmbd job fails to start on boot
On Ubuntu 14.04 nmbd fails to start on boot. There may be a regression in the upstart script. The following change fixed the problem for me: Change the "start on" condition in /etc/init/nmbd.conf to: start on (started smbd) (Thanks to Dan Corso who proposed this fix in comment #49 in bug #596064) -- 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/750786 Title: nmbd job fails to start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/750786/+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 1278466] Re: [FFe] ceph firefly stable release
For anyone following this bug waiting for firefly, I've pushed the 0.80~rc1 to: https://launchpad.net/~ceph-ubuntu/+archive/edgers Tests OK on a 25 node setup. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1278466 Title: [FFe] ceph firefly stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1278466/+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 1311810] Re: /etc/init.d/rsyslog is an init script not a link to /lib/init/upstart-job
This change was made intentionally according to a policy change: https://wiki.ubuntu.com/UpstartCompatibleInitScripts So I'm not going to change openssh itself, nor I think should rsyslog be changed. However, I believe some of the Upstart folks were looking into a quite different centralised solution to the underlying problem you're encountering; I forget the details but I think it was to have /lib/lsb /init-functions deal with automatically redirecting manual /etc/init.d/foo calls to the corresponding Upstart jobs. (Note, though, that you can and should use the "service" command, which abstracts away these changes.) ** Changed in: openssh (Ubuntu) Status: Confirmed => Won't Fix -- 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/1311810 Title: /etc/init.d/rsyslog is an init script not a link to /lib/init/upstart- job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1311810/+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 1310781] Re: bad bignum encoding for curve25519-sha256 at libssh.org
openssh (1:6.6p1-4) unstable; urgency=medium * Debconf translations: - Spanish (thanks, Matías Bellone; closes: #744867). * Apply upstream-recommended patch to fix bignum encoding for curve25519-sha...@libssh.org, fixing occasional key exchange failures. -- Colin Watson Mon, 21 Apr 2014 21:29:53 +0100 ** Also affects: openssh (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu Trusty) Status: New => Triaged ** Changed in: openssh (Ubuntu Trusty) Importance: Undecided => High ** Changed in: openssh (Ubuntu Trusty) Assignee: (unassigned) => Colin Watson (cjwatson) ** Changed in: openssh (Ubuntu Trusty) Milestone: None => ubuntu-14.04.1 ** Changed in: openssh (Ubuntu) Status: Triaged => Fix Released ** Changed in: openssh (Ubuntu Trusty) Status: Triaged => In Progress ** Description changed: + [Impact] Occasional key exchange failure with ED25519. + [Test Case] I don't have a clear one, but perhaps attempting lots of connections to a fixed server would do it. + [Regression Potential] We should test with an unpatched server to make sure that it properly falls back to skipping that key exchange method. + There's an occasional (one in 512 or so) key exchange failure in the curve25519-sha256 key exchange method, which affects OpenSSH 6.5 and 6.6. Upstream gives more details here and has recommended that distributors apply this patch: - https://lists.mindrot.org/pipermail/openssh-unix- + https://lists.mindrot.org/pipermail/openssh-unix- dev/2014-April/032494.html We should issue this as an update for trusty. -- 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/1310781 Title: bad bignum encoding for curve25519-sha256 at libssh.org To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1310781/+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 1312928] Re: SSH-Agent not working in KDE/X-Session if user's login shell is a tcsh
** Description changed: + [Impact] ssh-agent startup via Upstart doesn't work if the user's shell is [t]csh. + [Test Case] Create a guest account whose shell is tcsh and make sure that they can start a session and get ssh-agent. Note that this may not work for GNOME-flavoured sessions due to gnome-keyring taking precedence. + [Regression Potential] Confined to the ssh-agent started via Upstart, and in any event should be trivial since -s is already the default for most (just not all) users. + For X11/KDE sessions ssh-agent is started via upstart using configuration file /usr/share/upstart/sessions/ssh-agent.conf with the instruction ``eval "$(ssh-agent)" >/dev/null''. If the user's login shell is tcsh or csh ssh-agent will return c-shell like setenv commands which upstart/shell do not recognize. Thus environment variables $SSH_* are not propagated into the user's desktop session and neither ssh nor ssh-add are able to contact ssh-agent. Solution: use ``eval "$(ssh-agent -s)"'' to force sh-like output of ssh-agent (context diff included as attachment) Addition information: Bug occures at least in 13.10 and 14.04 amd64 architecture. In 14.04 the affected openssh-client package version is 1:6.2p2-6ubuntu0.3 ** Changed in: openssh (Ubuntu Trusty) Status: Triaged => In Progress -- 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/1312928 Title: SSH-Agent not working in KDE/X-Session if user's login shell is a tcsh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1312928/+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 1312928] Re: SSH-Agent not working in KDE/X-Session if user's login shell is a tcsh
** Changed in: openssh (Ubuntu Saucy) Status: Triaged => In Progress -- 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/1312928 Title: SSH-Agent not working in KDE/X-Session if user's login shell is a tcsh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1312928/+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 1315306] [NEW] Kernel Panic in gre_cisco_err
Public bug reported: When use gre vport, openvswitch register a gre_cisco_protocol but does not supply a err_handler with it. The gre_cisco_err() in net/ipv4/gre_demux.c expect err_handler be provided with the gre_cisco_protocol implementation, and call ->err_handler() without existence check, cause the kernel crash. http://git.openvswitch.org/cgi- bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=43f31ef528f5e4b4751036ce2ef90ea1334bbe3f fixes the issue ProblemType: KernelCrash Architecture: amd64 Date: Fri May 2 05:28:03 2014 DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic Uname: Linux 3.13.0-24-generic x86_64 VmCoreDmesg: base64 H4sICAAC/1ZtQ29yZURtZXNnAA== 3X1pe+M4kubn2V+BrfpQzh5LJg6CoLZc274y01Npp9t2VlVvbj56KB422xKlIiUf/es3AuApUpfTvTO7rkpbIhEvAlcgAggEvhL4sfqW/vlGzpN4Hnvj+J9xckf8u3S6mJFsMcpeMuLPFlk4/29fdyHYLbXn+y38T3GyeCaPYZrF04TwPuV9q8dE7y5MwjT2yd5oEY+D4K8zLxlPk7t3ZO/O98v0oq/6jOx9GS2S+cJ861F3ob/Sd+Qd+VHIXv725uKK3N4vyNEsJdQi1B1QOrAU+XJ7QphFRQlTMtEH4oIP/dB9t8z+yXQy8ZKAjOMkHJDjz59vh+cXRx/ODg9G0+n84HECLxb/7LXLlcLrwy9fzk8PLdsd8cAPegL+9kTkj3ou81hPhIHls5GnRMQhOfGnSTYdh4fz+YtV/3JD9ym1mWUliiTTSTCZJkEQFR/j7In4qZfdP4RpEo4PuRIXvQFl6mK5KL+eXV+efYLmms2m6TwMdIcYLKci0MbzcEw+hMkCyqy/tNMcXZySo8X8PkzmsQ9f2ilO4JW3SIu/H73FOFtOFSpmQaWef77pzdLpYxwAU7P7lyz2vTG5ProgE2/WYlAnN5RfJ+GEWM/W0k+v8chVoyj6RhaZNxqHO4G5ym+BRRGCpWEWpo9hsBNc2OYtej0cXS6q7wU8iF5TVKQMl8D8QASv5A1p23C20HBHJ1fn5PK3m53gbLsJFwQyDF9VVKSMlsGcYPTKoiKtvwynWPBK3hQLl8Fcab2y3pCWLsFFThS+tqhAG7XholcVNVKtkRqNolePhij0W3D46NVwQRsusPjr4ajfgqOvL2zY5i58fWGjdlNEr24K2pbBipZw3d3k8g+yd/Yc+ot5SE5jneQdgflgHvpz0AEGxIO/jy2ymwvkgrC+A4mBz2TeX05yenE+IDeLWZhOYh9m2D+odfPpovf+oPiwr0tCaJ+OCKUHFj0ARYF3T1OLWeABh0vVV5SzVj5yePjLy pozWGk4mT7WsbwKa31dTcnRhysySuPgLiTRdJGsyGHsZfPhLErIIWQAT+AHZtPnoZf69+VzUZRiGePi9vqaBGEEk/aczF9moPosEt/z77t40omj+Bkm79RL7sKMhAmmCzp0C1Nn7nv4IU9pPA97I89/6NAvdLpjnW51zqBl6HQnNby847STnuqkZ84myDOUTb33myF1uR+9NNaNvrnoZORlIalmcGiP7IE4qvy+rkJoTq2WqN+fbUPNirzPVlGvqxFOAjMsg/Y7seadveadXPPOWfNOrXnnrnz3rCS5OrotWwdVX2Ltk+k4gGHgWMKSkE7/3SdJ+KQf0vwh/F3Gm6bxXZyAklo2P3aGln6bhneYC9b9gFgfjvdNLxkQzvALDizy+3EXFS2oTMqczKbsYj0dK+lssAO6Kb+cLFPOp/Nc4fZBLKVYQZw5sm1CvEeBQ6azeTwBArAm52gHRtOUTOZpSvxx6CUgKFtNcwdsDLP4n8CJFL+Sf/PvF8lD/UGymAyB/wG0Pfm38RT6quYEecKaa4lBaKJXVv3WNV+vePph22rfqbV4QSZqZGJDXqIgUjUitYHILoiorBdLbiCTr+iGXbNlWM2W0ZI2sMVs2ZjLAtQdd5jK9Byp1wYurnpznaM3r828USCjYuaFj8AXGJ0zmMswFTKqjMjV6b61lBDfSxIcA5R4aehleiyMp08E8KfpC/TiNF3MUI1pqVAokPNU89SbzKa4xLCcq8t0Yv2H4HghTNhOSx59yZCHD8dk5uEkhEwEcQpzli4MvFsmiJN4PjS5D/Mkg27VxjRWa0SvSauZIKI1DR1f/0q+QjoaBahf75P8s6a5+nB7dPzpbA1NWKMJt6SJajTROpp19QEKbKlxV8rsqhrpTm3qhF2s5lUT5byG1ut59a1a7sEmXrtSr+J1bb61jqDoaFMddaZ+Tb61dZBy/WN1X62tmdD1fbWiYQUN39SWBY2oCjdq0tAPq2j8isb3RtvlAw pbq+yryrOuDmsLLOXCyso8q7Twcbs69P1yQASBvV3ZgJGKpljs2ShXQlobQ3Q7GRGyGg177birLQSVC0Cry9ZO+5p2q63IlCsxK/PsSPuaPOv2vRNtkoXdqVeNBdD1Ts9vfi3z4iKK8vUwLp1IduWEy2IDcn1zekXqy6qWcC39gAmy92gxcvPl6uz64l03+R83p7ektmzGJdjj+sHxCZLTnBy0iJPzXu/imIAkcaDfuOTo4lwbtVBSylfAv4c/dXjBR64yRBre/j740xb3NELuT90jWS98Db4w+s4vbz/h1gizHEpXc39Th7cjsEH1A2F1UxxdnZ80y+t7urygzSBD/Dur86pZXsEDkTMk3qC1Pl2dL8Mrw729qjMU1Qnw/eKbvQL+5qbFfajhbSiEhidXk+swIuRktrDOs7lOzLdtrRa84EzDH52qJrzO4GryvfAwQPEBe8/a3N9+N/e2FWnuuWhxfzTbGf7i5P2HJrzIew7fNM4vbt4XnLnOCvir66PTJfh8pJycmYGIKc5Pif57e14mpjk8N99WwH+8OluqHJiJDfdqc7/fvWPatun33HVyeG/uXYf6zy3YUaRY731l04JNAw84O7MK+JssmJPy73LTWi6llK2Cv4KhXYfHrbtcShkZe0QuCIx+8vnsopG4UTnWKhl7cXS9BJ/3HJVzD0yefSL65+PN76RqWs198W0F/Nn55X8swfsanvJCKBAtvPBfI7HJcQP3Z9c3zbpXQWRGbQkPwGfXBr6eeCv4j2dL8K7FTOUcqRb3jcRbwR+fXS/D+yrvHS34RuKt4D9NcbNZz1leEKRhloHqUeyxdCy/X365OMLd+Si+W6QeWvbdy/DvvQe0yT2STIOlJYcVm9WrbUv0ukDqLJwvZgbQ6rDA1xin5PLz6dnw9Oj2qGanRpFTIxx1EV7rhRm9wMEUiJRpVKxZQIkcS8AjXGyoOSCQvZuXbA5Z6KU7zqQLid61NUTkM/Rq9VA8ACm S64lXF6ek90u5HgKPZZUUHgDbhTkBrWCqZTmj/zVNirX5jjV5GNemk9Qqs9wzXVmXQMVZnYq2V7c6WmCa4qJpp3K8uuUupo96zeqfWI5s7qVzXeGh59/rEi+nP/PS8UvRRrpKTOHb/OiX8GjQWXiY5rqL0UG2hQneJtvK6myTbWVodZBtYyu1ybZro89F5zML6XoNbkAUl66yVXenw+bEpe98wW6RhYFZRg8nYHKto2E0p1m1ZlpPzF03T75PPp2//0xG3ty/H1ir+rShotxVdAfOSkLlCkfyjgw5XTke8iypdLjcNs8GqSNA67DEVrnmitpF7zaehCk5/0yupul8gC0N4uQNJoicRKfe8/xZPIwDvc7wjYy9WeznX3Fp22xFvdsWgTUR2O4IvIkgdkcQTQS5O4LdRKC7I8gmAt8dwWki2LsjqCaCsxXC8BL0kxoKTlv38d09CXErfxwnc3hIv62AOP9suCgZyPsiAuXeL9/IXRYPcb/mq9WGMQDwZkBy1onar/wy2X6jdxvEffLhBjTlHuMrmLq8Hd5cnww//3aNfpwZ7nEvsmGc/gmf7sbTkTfWXxgJojH+e7czjlvHcU2FjcPHcCXU9d8sI0BGLwS3ENM4CPsr07Id0rqb05p9GO2rtXcBNt47LcZw86mpMcZJhCKsa1+oZuzFwUAvlivpORYt9jKfC/ekZcpsMkOf1AE5Go+nT8iIIidXX0AmWuR+Op+NF3f6+zJdkmLlZkPoPQPSXtS5AjXuOryLQalLofjJNPMei52ruu7gqkp3UF3T5NZAbgUUfQ9Qzakm+C6gcNN22FZANTfL0r3ydUCVg2XpWPkqoJo3ZOkF+Uqg0nWxdFl8JVDptFg6K74OKHcxRJ3cib6j1WquitHou4CqvbYoHH0PUOXtWHo5vhqIlkDfxVFQcZQ7Sr4aSJRAdPQ9QIXPZelr+VogVhXtu+oorOoo/K5WC6tW+64OGW02Wxs+nl1jiniPXjzW JipOdVcn5yQIH2O/bXEew9yEk9LMS73HOJ0v8BgJMJcvG8CsOPLSkNx7afAEH1qzG659DGdh6s8WA3J5PYSp7GbAbInzFzxDh7bhKJ5ntWeg5GQDhV/QPtPfWibB1dk1IA3I2WQUBngAgbnGlDhAH7G/VksNZtCRTEkOlkqqqAtqDROY24JJRoVYhp4BQs+DydgfrCMjOskh/QsDo5vabB0M6G8wm1PQqDgRxCaSOKRV0Yt4PIc0aB6NoQtkoG6YdZBpGoTpPplMR/E4nr8QfX4H22Sa9Am51V5ghfXKuGvZLUeTq+k
[Bug 1310629] Re: Nova configuration template has deprecated items ( > grizzly )
** Also affects: nova (Ubuntu) Importance: Undecided Status: New ** Also affects: nova (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: nova (Ubuntu Utopic) Status: New => Triaged ** Changed in: nova-compute (Juju Charms Collection) Status: New => Triaged -- 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/1310629 Title: Nova configuration template has deprecated items ( > grizzly ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1310629/+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 1309860] Re: missing ipmi module
This is a patch to the bug. This is extracted from the current openipmi centos package. It handles the fact the the IPMI modules may now be built into the kernel. ** Patch added: "Patch to bug" https://bugs.launchpad.net/ubuntu/trusty/+source/openipmi/+bug/1309860/+attachment/4103133/+files/openipmi.msghandler.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1309860 Title: missing ipmi module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860/+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 1310629] Re: Nova configuration template has deprecated items ( > grizzly )
** Changed in: nova (Ubuntu Utopic) Importance: Undecided => Low ** Changed in: nova-compute (Juju Charms Collection) Importance: Undecided => Low -- 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/1310629 Title: Nova configuration template has deprecated items ( > grizzly ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1310629/+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 1219857] Re: vsftpd connections fail on amd64: "500 OOPS: child died"
3.0.2-1ubuntu2.14.04.1 fixed the bug for me. Tested on amd64 with Linux 3.13.0-24-generic. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/1219857 Title: vsftpd connections fail on amd64: "500 OOPS: child died" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1219857/+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 1314697] Re: Upon upgrade, DNS resolution no longer works
LSOF output below. I tried to put a strace in init.d but failed miserably lsof | grep dnsmasq dnsmasq 1430 dnsmasq cwd unknown /proc/1430/cwd (readlink: Permission denied) dnsmasq 1430 dnsmasq rtd unknown /proc/1430/root (readlink: Permission denied) dnsmasq 1430 dnsmasq txt unknown /proc/1430/exe (readlink: Permission denied) dnsmasq 1430 dnsmasq NOFD /proc/1430/fd (opendir: Permission denied) dnsmasq 2066 nobody cwd unknown /proc/2066/cwd (readlink: Permission denied) dnsmasq 2066 nobody rtd unknown /proc/2066/root (readlink: Permission denied) dnsmasq 2066 nobody txt unknown /proc/2066/exe (readlink: Permission denied) dnsmasq 2066 nobody NOFD /proc/2066/fd (opendir: Permission denied) dnsmasq 3176 libvirt-dnsmasq cwd unknown /proc/3176/cwd (readlink: Permission denied) dnsmasq 3176 libvirt-dnsmasq rtd unknown /proc/3176/root (readlink: Permission denied) dnsmasq 3176 libvirt-dnsmasq txt unknown /proc/3176/exe (readlink: Permission denied) dnsmasq 3176 libvirt-dnsmasq NOFD /proc/3176/fd (opendir: Permission denied) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1314697 Title: Upon upgrade, DNS resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1314697/+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 1313566] Re: mysql 5.6.17 security update tracking bug
** Changed in: mysql-5.6 (Ubuntu Trusty) Status: New => In Progress -- 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/1313566 Title: mysql 5.6.17 security update tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1313566/+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 1309860] Re: missing ipmi module
The attachment "patch from centos" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1309860 Title: missing ipmi module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860/+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 1312936] Re: Post-installation script fails
Strange. I just tested this on a fresh 14.04 VM with 512Mb RAM. >From the original message : "AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld in /etc/apparmor.d/usr.sbin.mysqld at line 44: Could not open 'local/usr.sbin.mysqld'", the apparmor problem seems clear. That doesn't mean there isn't something else wrong. On my new setup, MySQL 5.6 installed without trouble (created my empty file beforehand. I'll have to check it without) and runs. It requires 1.1 Gb of virtual RAM, but only occupies 440Mb at startup, so it runs fine (granted, it should run into trouble soon). Maybe the difference is what other packages you installed : apache2 itself would eat enough RAM to OOM a machine on Mysql install. The innodb buffer pool seems to be 128Mb on my machine, which is the official default value. mysqlcalculator states that RAM usage at 128Mb buffer pool is close to 700Mb (to be compared with the 576Mb RAM occupied by the previous 8Mb 5.5 default buffer pool) => Neither should be able to run out of the box with 512Mb RAM only. With small machines, I think your best bet would be to deploy a my.cnf file prior to the mysql package installation (or to put a file in /etc/mysql/conf.d) with some alterations to the configuration (max_connections = 50 alone shaves 200Mb off RAM requirements) to ensure mysql will start and run fine. -- 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/1312936 Title: Post-installation script fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1312936/+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 1313566] Re: mysql 5.6.17 security update tracking bug
Looks good, ACK. Building now and will release as a security update once built. Thanks! ** Changed in: mysql-5.6 (Ubuntu Trusty) Status: In Progress => Fix Committed -- 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/1313566 Title: mysql 5.6.17 security update tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1313566/+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 1315188] Re: No init.d script included in icehouse ubuntu packaging
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: keystone (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1315188 Title: No init.d script included in icehouse ubuntu packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1315188/+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 1315402] [NEW] No easy way to use hugetlbfs with QEMU
Public bug reported: In previous releases (tested with Saucy), if one wanted to use hugetlbfs for a VM, the needed procedure was: 1) Add "vm.nr_hugepages" to /etc/sysctl.d/60-hugepages.conf 2) start procps 3) Set KVM_HUGEPAGES=1 in /etc/default/qemu-kvm 4) restart qemu-kvm 5) Enable " " in the libvirt guest definition 6) Restart the guest Now with Trusty, this doesn't work anymore as there is no (obvious?) way to have the hugetlbfs mounted where QEMU expects it. On Saucy, the upstart job for qemu-kvm contains this: # mount hugepages if available and requested if [ "$KVM_HUGEPAGES" -eq "1" ]; then if ! grep -q hugetlbfs /proc/filesystems; then logger -t qemu-kvm "Error: hugepages not available in the kernel!" elif grep -q /run/hugepages/kvm /proc/mounts; then logger -t qemu-kvm "/run/hugepages/kvm already mounted" elif ! grep -q kvm /etc/group; then logger -t qemu-kvm "Error: group kvm does not exist!" else kvmgid=`grep kvm /etc/group | cut -d: -f 3` mkdir -p /run/hugepages/kvm mount -t hugetlbfs hugetlbfs-kvm -o mode=775,gid=$kvmgid /run/hugepages/kvm fi fi But it seems there is nothing similar in Trusty and manually mounting the hugetlbfs doesn't help as qemu cannot find it there. Host information: $ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 $ apt-cache policy qemu-system-x86 libvirt-bin qemu-system-x86: Installed: 2.0.0+dfsg-2ubuntu1 Candidate: 2.0.0+dfsg-2ubuntu1 Version table: *** 2.0.0+dfsg-2ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.0.0~rc1+dfsg-0ubuntu3.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 2.0.0~rc1+dfsg-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages libvirt-bin: Installed: 1.2.2-0ubuntu13.1 Candidate: 1.2.2-0ubuntu13.1 Version table: *** 1.2.2-0ubuntu13.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu13 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-common 2.0.0+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 10:05:18 2014 InstallationDate: Installed on 2014-01-26 (95 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1315402 Title: No easy way to use hugetlbfs with QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1315402/+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 1315402] Re: No easy way to use hugetlbfs with QEMU
Hi, could you show the contents of your /etc/init/qemu-kvm.conf? The package still provides the code you seem to be referring to, and on my laptop /run/hugepages/kvm is still mounted, so I'm curious what is going on on your system. ** Changed in: qemu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1315402 Title: No easy way to use hugetlbfs with QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1315402/+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 1315260] Re: Spamassassin: sa-learn fails in cronjob
** Changed in: spamassassin (Ubuntu) Importance: Undecided => Medium -- 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/1315260 Title: Spamassassin: sa-learn fails in cronjob To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1315260/+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 1315402] Re: No easy way to use hugetlbfs with QEMU
Hi Serge, On 14-05-02 10:48 AM, Serge Hallyn wrote: > could you show the contents of your /etc/init/qemu-kvm.conf? The > package still provides the code you seem to be referring to, and on my > laptop /run/hugepages/kvm is still mounted, so I'm curious what is going > on on your system. In fact, the qemu-kvm (transitional) package was missing on my system. Installing it didn't help though as it doesn't provide /etc/init/qemu-kvm.conf $ find /etc/init -name '*qemu*.conf' # nothing -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1315402 Title: No easy way to use hugetlbfs with QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1315402/+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 1315426] [NEW] nginx not built as position independent
Public bug reported: nginx (1.4.6-1ubuntu3) is not being built with -fPIE -pie. I am running ubuntu 14.04 LTS. I've included the output when scanning apache2 with hardening-check just for comparison purposes. $ hardening-check /usr/sbin/nginx /usr/sbin/nginx: Position Independent Executable: no, normal executable! Stack protected: yes Fortify Source functions: yes (some protected functions found) Read-only relocations: yes Immediate binding: no, not found! $ dpkg -l | grep "nginx-core" ii nginx-core1.4.6-1ubuntu3 amd64nginx web/proxy server (core version) $ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 $ hardening-check /usr/sbin/apache2 /usr/sbin/apache2: Position Independent Executable: yes Stack protected: yes Fortify Source functions: yes (some protected functions found) Read-only relocations: yes Immediate binding: yes ** Affects: nginx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1315426 Title: nginx not built as position independent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1315426/+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 1315188] Re: No init.d script included in icehouse ubuntu packaging
This is confusing as some services like rabbitmq-server still have an init script: root@stackforge-ubuntu:~# dpkg -S /etc/init.d/rabbitmq-server rabbitmq-server: /etc/init.d/rabbitmq-server root@stackforge-ubuntu:~# ls -al /etc/init.d/rabbitmq-server -rwxr-xr-x 1 root root 3991 Mar 5 21:32 /etc/init.d/rabbitmq-server root@stackforge-ubuntu:~# apt-cache policy rabbitmq-server rabbitmq-server: Installed: 3.2.4-1 Candidate: 3.2.4-1 Version table: *** 3.2.4-1 0 500 http://mirror.rackspace.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status root@stackforge-ubuntu:~# -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1315188 Title: No init.d script included in icehouse ubuntu packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1315188/+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 1315402] Re: No easy way to use hugetlbfs with QEMU
Quoting Simon Déziel (1315...@bugs.launchpad.net): > Hi Serge, > > On 14-05-02 10:48 AM, Serge Hallyn wrote: > > could you show the contents of your /etc/init/qemu-kvm.conf? The > > package still provides the code you seem to be referring to, and on my > > laptop /run/hugepages/kvm is still mounted, so I'm curious what is going > > on on your system. > > In fact, the qemu-kvm (transitional) package was missing on my system. The qemu-kvm.conf file is provided by qemu-system-x86 (the old name was kept to ease transitions) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1315402 Title: No easy way to use hugetlbfs with QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1315402/+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 1315402] Re: No easy way to use hugetlbfs with QEMU
On 14-05-02 12:04 PM, Serge Hallyn wrote: > Quoting Simon Déziel (1315...@bugs.launchpad.net): >> Hi Serge, >> >> On 14-05-02 10:48 AM, Serge Hallyn wrote: >>> could you show the contents of your /etc/init/qemu-kvm.conf? The >>> package still provides the code you seem to be referring to, and on my >>> laptop /run/hugepages/kvm is still mounted, so I'm curious what is going >>> on on your system. >> >> In fact, the qemu-kvm (transitional) package was missing on my system. > > The qemu-kvm.conf file is provided by qemu-system-x86 (the old name > was kept to ease transitions) Understood but this package doesn't provide the upstart job you have. May I ask to which package provided the file you have? Maybe the -proposed package accidentally dropped the upstart job? Some more info: $ dpkg -L qemu-system-x86 | grep init /etc/init.d /etc/init.d/qemu-system-x86 $ apt-cache policy qemu-system-x86 qemu-system-x86: Installed: 2.0.0+dfsg-2ubuntu1 Candidate: 2.0.0+dfsg-2ubuntu1 Version table: *** 2.0.0+dfsg-2ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.0.0~rc1+dfsg-0ubuntu3.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 2.0.0~rc1+dfsg-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1315402 Title: No easy way to use hugetlbfs with QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1315402/+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 1315402] Re: No easy way to use hugetlbfs with QEMU
D'oh, right you are. debian/rules now has the wrong dh_installinit line. Thanks! ** Changed in: qemu (Ubuntu) Status: Incomplete => In Progress ** Changed in: qemu (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1315402 Title: No easy way to use hugetlbfs with QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1315402/+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 1315402] Re: No easy way to use hugetlbfs with QEMU
Pushed a fix to utopic. Since there is a package in trusty-proposed, we'll have to wait for that to clear before fixing this in trusty. ** Also affects: qemu (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Trusty) Importance: Undecided => High ** Changed in: qemu (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1315402 Title: No easy way to use hugetlbfs with QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1315402/+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 1307027] Re: php5-fpm: Possible privilege escalation due to insecure default permissions of sockets
** Bug watch added: bugs.php.net/ #67060 http://bugs.php.net/bug.php?id=67060 ** Also affects: php via http://bugs.php.net/bug.php?id=67060 Importance: Unknown Status: Unknown -- 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/1307027 Title: php5-fpm: Possible privilege escalation due to insecure default permissions of sockets To manage notifications about this bug go to: https://bugs.launchpad.net/php/+bug/1307027/+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
[Blueprint servercloud-u-lxc] LXC work for Utopic
Blueprint changed by Serge Hallyn: Work items set to: Work items: [stgraber] Shorten the cgroup path in logind so we don't get too much of a performance impact: POSTPONED [stgraber] Update lxc-start-ephemeral to use the clone function: POSTPONED [serge-hallyn] Test apparmor stacked profiles (2d): POSTPONED [serge-hallyn] Update the upstart job to setup the LXC apparmor profile as a namespace (.5d): POSTPONED [serge-hallyn] Investigate the syslog namespace and try to get things forward a bit (1d): POSTPONED [jjohansen] Provide a test PPA for stacked apparmor profiles: POSTPONED -- LXC work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-lxc -- 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 1313935] Re: tenant is required for quota-update but not for quota-show
** Also affects: cinder Importance: Undecided Status: New ** Changed in: cinder Assignee: (unassigned) => Thang Pham (thang-pham) -- 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/1313935 Title: tenant is required for quota-update but not for quota-show To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1313935/+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 1313935] Fix proposed to nova (master)
Fix proposed to branch: master Review: https://review.openstack.org/91866 -- 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/1313935 Title: tenant is required for quota-update but not for quota-show To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1313935/+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 1315402] Re: No easy way to use hugetlbfs with QEMU
This bug was fixed in the package qemu - 2.0.0+dfsg-2ubuntu2 --- qemu (2.0.0+dfsg-2ubuntu2) utopic; urgency=medium * debian/rules: install the proper /etc/init/qemu-kvm.conf (LP: #1315402) * debian/control: drop the versioning requirement from libfdt-dev build-dependency, as it is longer needed (LP: #1295072) -- Serge HallynFri, 02 May 2014 11:43:44 -0500 ** Changed in: qemu (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1315402 Title: No easy way to use hugetlbfs with QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1315402/+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 1309452] Re: Merge 2.0.0+dfsg-2 to fix spice crashes
This bug was fixed in the package qemu - 2.0.0+dfsg-2ubuntu2 --- qemu (2.0.0+dfsg-2ubuntu2) utopic; urgency=medium * debian/rules: install the proper /etc/init/qemu-kvm.conf (LP: #1315402) * debian/control: drop the versioning requirement from libfdt-dev build-dependency, as it is longer needed (LP: #1295072) -- Serge HallynFri, 02 May 2014 11:43:44 -0500 ** Changed in: qemu (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1309452 Title: Merge 2.0.0+dfsg-2 to fix spice crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1309452/+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 1312156] Re: [Precise] Potential for data corruption
Here is the patch fixing corosync misbehavior described above. Description: Remove buggy logic to prevent secondary dc fencing On logic before commit 82aa2d8d17 the node responsible for fencing (executioner) the dc was responsible also for updating cib. If this update failed (due to a executioner fail, for ex) the dc would be fenced a second time because the cluster would not know about fencing result. On upstream commit 82aa2d8d17, a logic trying to avoid this second dc fencing was introduced. If this node was not the dc fence executioner it would keep its name. With its name, in the case executioner node died and this node became the new dc it would be able to update cib telling the result of last dc fencing. Problem is that this list is never cleaned and there might be cases wrong cib update is given (when a dc takeover has to run) resulting in a bad, bad thing: same resource running on different nodes. It is much more acceptable for SRU to restore old behavior, known to be safe even if it implies killing dc twice, than to backport several pieces of code to implement a logic that was not there on the stable version release. ** Patch added: "precise_pacemaker_1.1.6-2ubuntu3.3.diff" https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1312156/+attachment/4103593/+files/precise_pacemaker_1.1.6-2ubuntu3.3.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1312156 Title: [Precise] Potential for data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1312156/+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 1312156] Re: [Precise] Potential for data corruption
** Also affects: pacemaker (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: pacemaker (Ubuntu Precise) Assignee: (unassigned) => Rafael David Tinoco (inaddy) ** Changed in: pacemaker (Ubuntu) Assignee: Rafael David Tinoco (inaddy) => (unassigned) ** Changed in: pacemaker (Ubuntu) Status: In Progress => Fix Released ** Changed in: pacemaker (Ubuntu Precise) Status: New => In Progress ** Changed in: pacemaker (Ubuntu Precise) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1312156 Title: [Precise] Potential for data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1312156/+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 1312156] Re: [Precise] Potential for data corruption
** Description changed: + [Impact] + + * Pacemaker designated controller can make wrong decisions based on + uncleared node status on a rare specific situation. This situation can + make the same resource starts on two nodes at the same time, resulting + in data corruption. + + [Test Case] + + * The bug trigger is very hard hard to achieve: + + 1) If stonith was successful on fencing a node (any node was fenced). + 2) If the target and origin are the same (node killed itself). + 3) If we do not have a dc or the fenced node is our dc (our dc killed itself). + 4) If the executor is not this node (at least 3 nodes). + 5) If this node is elected new DC anytime in the future. + 7) If a policy engine was not yet scheduled. + 8) If takeover runs before policy engine. + + * The bug couldn't be reproduced so far: the patch was made based on a + community report (https://www.mail- + archive.com/pacema...@oss.clusterlabs.org/msg19509.html) analyzed by + upstream code developer (Andrew Beekhof). + + [Regression Potential] + + * On logic before commit 82aa2d8d17 the node responsible for fencing + (executioner) the dc was responsible also for updating cib. If this + update failed (due to a executioner fail, for ex) the dc would be fenced + a second time because the cluster would not know about fencing result. + On upstream commit 82aa2d8d17, a logic trying to avoid this second dc + fencing was introduced. This logic by itself is buggy. + + * To minimize any kind of regression, instead of going forward on + pacemaker versions, it was decided to go backwards removing only this + piece of code. + + * It is much more acceptable for SRU to restore old behavior, known to + be safe even if it implies killing dc twice, than to backport several + pieces of code to implement a logic that was not there on the stable + version release. + + [Other Info / Original Description] + Under certain conditions there is faulty logic in function tengine_stonith_notify() which can incorrectly add successfully fenced nodes to a list, causing Pacemaker to subsequently erase that node’s status section when the next DC (Designated Controller) election occurs. With the status section erased, the cluster considers that node is down and starts corresponding services on other nodes. Multiple instances of the same service can cause data corruption. Conditions: 1. fenced node must have been the previous DC and been sufficiently functional to request its own fencing 2. fencing notification must arrive after the new DC has been elected but before it invokes the policy engine Pacemaker versions affected: 1.1.6 - 1.1.9 Stable Ubuntu releases affected: Ubuntu 12.04 LTS Ubuntu 12.10 (EOL?) Fix: https://github.com/ClusterLabs/pacemaker/commit/f30e1e43 References: https://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg19509.html http://blog.clusterlabs.org/blog/2014/potential-for-data-corruption-in-pacemaker-1-dot-1-6-through-1-dot-1-9/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1312156 Title: [Precise] Potential for data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1312156/+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 1315521] [NEW] wrong cgroup on login to container
Public bug reported: When starting a privileged container with cgmanager, cgroups look like: 3:cpuset:/lxc/u5 2:name=systemd:/user/1000.user/c2.session where all controllers other than name=systemd are correct. lxc needs to set the new cgroup for name=systemd, and cgmanager needs to fix a bug where name=systemd was not being handled right. ** Affects: cgmanager (Ubuntu) Importance: High Status: Fix Released ** Affects: lxc (Ubuntu) Importance: High Status: Fix Committed ** Affects: cgmanager (Ubuntu Trusty) Importance: High Status: Confirmed ** Affects: lxc (Ubuntu Trusty) Importance: High Status: Confirmed ** Also affects: lxc (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cgmanager (Ubuntu) Importance: Undecided Status: New ** Changed in: cgmanager (Ubuntu) Status: New => Fix Released ** Changed in: cgmanager (Ubuntu) Importance: Undecided => High ** Changed in: cgmanager (Ubuntu Trusty) Importance: Undecided => High ** Changed in: lxc (Ubuntu) Importance: Undecided => High ** Changed in: lxc (Ubuntu Trusty) Importance: Undecided => High ** Changed in: lxc (Ubuntu) Status: New => Fix Committed ** Changed in: lxc (Ubuntu Trusty) Status: New => Confirmed ** Changed in: cgmanager (Ubuntu Trusty) Status: New => Confirmed -- 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/1315521 Title: wrong cgroup on login to container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1315521/+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 1315521] Re: wrong cgroup on login to container
Patch for lxc has been sent to the mailing list (hence the 'fix committed' status). -- 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/1315521 Title: wrong cgroup on login to container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1315521/+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 1315188] Re: No init.d script included in icehouse ubuntu packaging
Was this removal intentional? I just assumed it was an omission since it's setup process still exists in the package, and it's assumed to be that way in the docs. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1315188 Title: No init.d script included in icehouse ubuntu packaging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1315188/+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
[Blueprint servercloud-u-server-core] General server work for Utopic
Blueprint changed by Patricia Gaughen: Work items changed: Work items: determine ssd caching solution: TODO add scribe (https://github.com/facebook/scribe) to universe: TODO add meteor to universe: TODO + investigate support of ruby for puppet: TODO -- General server work for Utopic https://blueprints.launchpad.net/ubuntu/+spec/servercloud-u-server-core -- 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 1315562] [NEW] libnss-winbind should allow installation of the 32 bit libarary in trusty
Public bug reported: This is a regression. Prior versions of Ubuntu allowed the 32 bit and 64 bit libnss-winbind library to co-exist on the same system. $ apt-get install libnss-winbind:i386 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libnss-winbind:i386 : Depends: winbind:i386 (= 2:4.1.6+dfsg-1ubuntu2) but it is not going to be installed Depends: samba-libs:i386 (= 2:4.1.6+dfsg-1ubuntu2) but it is not going to be installed E: Unable to correct problems, you have held broken packages. This is important as 32 bit binaries running on a 64 bit system can still access NSS services and must still be able to load the nss-winbind plugin. The same comment applies to PAM as well, but I have no 32 bit apps using PAM so it isn't as interesting ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- 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/1315562 Title: libnss-winbind should allow installation of the 32 bit libarary in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1315562/+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 1315560] [NEW] winbind segfaults during pam login
Public bug reported: Attempting to login via PAM causes winbind to segfault and log this to syslog: May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.540190, 0] ../lib/util/fault.c:72(fault_report) May 2 16:25:54 jggl winbindd[2416]: === May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.540238, 0] ../lib/util/fault.c:73(fault_report) May 2 16:25:54 jggl winbindd[2416]: INTERNAL ERROR: Signal 11 in pid 2416 (4.1.6-Ubuntu) May 2 16:25:54 jggl winbindd[2416]: Please read the Trouble-Shooting section of the Samba HOWTO May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.540263, 0] ../lib/util/fault.c:75(fault_report) May 2 16:25:54 jggl winbindd[2416]: === May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.540295, 0] ../source3/lib/util.c:785(smb_panic_s3) May 2 16:25:54 jggl winbindd[2416]: PANIC (pid 2416): internal error May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.585897, 0] ../source3/lib/util.c:896(log_stack_trace) May 2 16:25:54 jggl winbindd[2416]: BACKTRACE: 27 stack frames: May 2 16:25:54 jggl winbindd[2416]:#0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1a) [0x7f6d3e2fff3a] May 2 16:25:54 jggl winbindd[2416]:#1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f6d3e300010] May 2 16:25:54 jggl winbindd[2416]:#2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7f6d425d9c6f] May 2 16:25:54 jggl winbindd[2416]:#3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x1ae86) [0x7f6d425d9e86] May 2 16:25:54 jggl winbindd[2416]:#4 /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f6d42a07340] May 2 16:25:54 jggl winbindd[2416]:#5 /usr/lib/x86_64-linux-gnu(krb5_storage_free+0x1) [0x7f6d3ce45441] May 2 16:25:54 jggl winbindd[2416]:#6 /usr/lib/x86_64-linux-gnu(+0x42465) [0x7f6d3ce2b465] May 2 16:25:54 jggl winbindd[2416]:#7 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(+0x86b1) [0x7f6d3ee756b1] May 2 16:25:54 jggl winbindd[2416]:#8 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(gse_krb5_get_server_keytab+0xfb) [0x7f6d3ee75beb] May 2 16:25:54 jggl winbindd[2416]:#9 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(+0xa7aa) [0x7f6d3ee777aa] May 2 16:25:54 jggl winbindd[2416]:#10 /usr/lib/x86_64-linux-gnu/libgensec.so.0(gensec_start_mech+0x71) [0x7f6d3f3012b1] May 2 16:25:54 jggl winbindd[2416]:#11 /usr/lib/x86_64-linux-gnu/libgensec.so.0(gensec_start_mech_by_oid+0x26) [0x7f6d3f301586] May 2 16:25:54 jggl winbindd[2416]:#12 /usr/sbin/winbindd(kerberos_return_pac+0x435) [0x7f6d42e66da5] May 2 16:25:54 jggl winbindd[2416]:#13 /usr/sbin/winbindd(winbindd_dual_pam_auth+0xec4) [0x7f6d42e78884] May 2 16:25:54 jggl winbindd[2416]:#14 /usr/sbin/winbindd(+0x5337c) [0x7f6d42e8d37c] May 2 16:25:54 jggl winbindd[2416]:#15 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x867b) [0x7f6d3c37167b] May 2 16:25:54 jggl winbindd[2416]:#16 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x6b27) [0x7f6d3c36fb27] May 2 16:25:54 jggl winbindd[2416]:#17 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7f6d3c36c5ed] May 2 16:25:54 jggl winbindd[2416]:#18 /usr/sbin/winbindd(+0x55702) [0x7f6d42e8f702] May 2 16:25:54 jggl winbindd[2416]:#19 /usr/sbin/winbindd(+0x55db5) [0x7f6d42e8fdb5] May 2 16:25:54 jggl winbindd[2416]:#20 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_immediate+0xd4) [0x7f6d3c36ce14] May 2 16:25:54 jggl winbindd[2416]:#21 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x8437) [0x7f6d3c371437] May 2 16:25:54 jggl winbindd[2416]:#22 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x6b27) [0x7f6d3c36fb27] May 2 16:25:54 jggl winbindd[2416]:#23 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7f6d3c36c5ed] May 2 16:25:54 jggl winbindd[2416]:#24 /usr/sbin/winbindd(main+0xad2) [0x7f6d42e5ee42] May 2 16:25:54 jggl winbindd[2416]:#25 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f6d3bfc4ec5] May 2 16:25:54 jggl winbindd[2416]:#26 /usr/sbin/winbindd(+0x25532) [0x7f6d42e5f532] May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.586279, 0] ../source3/lib/dumpcore.c:312(dump_core) May 2 16:25:54 jggl winbindd[2416]: unable to change to /var/log/samba/cores/winbindd May 2 16:25:54 jggl winbindd[2416]: refusing to dump core Attempting to validate passwords via wbinfo works fine, nss works fine, etc. The segfault prevents the login from succeeding, so pam winbind is basically unusable. This is a regression, this config has worked here on various Ubuntu's for at least 5 years. $ cat /etc/security/pam_winbind.conf [global] ;debug=yes ;debug_state=yes require_membership_of=ORCORP\orc krb5_auth=yes $ cat /etc/samba/smb.conf [global] workgroup = ORCORP realm = ADS.ORCORP.CA os level = 0 log l
[Bug 1315565] [NEW] nss-winbind is returing -1 for supplemental groups
Public bug reported: This is a regression in trusty. Consider: $wbinfo -r jgg 1000 -1 10009 10011 10004 10003 -1 1002 -1 Results in: $ getent initgroups jgg jgg 4 24 27 30 46 108 124 1000 10009 10011 10004 10003 1002 $ id jgg uid=2009(jgg) gid=1000(orc) groups=1000(orc),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),108(lpadmin),124(sambashare),4294967295,10009(vpn_users),10011(xweb_users),10004(accounting),10003(domain_users),4294967295,1002(wsudoers),4294967295 Those 4294967295 values should not be in the group list. The underlying issue is that some of the AD groups the user is a part of are not UNIX groups, they are just general AD groups: $ ldapsearch uid=jgg memberOf dn: CN=Jason Gunthorpe,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=XWEB Users,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=VPN Users,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=accounting,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=wsudoers,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=Boards website editors,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=Parts website editors,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=adm,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=Domain Users,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=Print Operators,CN=Builtin,DC=ads,DC=orcorp,DC=ca For instance, 'Print Operators' is not a UNIX group, it doesn't have the RFC2307 schema elements. # Print Operators, Builtin, ads.orcorp.ca dn: CN=Print Operators,CN=Builtin,DC=ads,DC=orcorp,DC=ca objectClass: top objectClass: group cn: Print Operators description: Members can administer domain printers member: CN=Jason Gunthorpe,CN=Users,DC=ads,DC=orcorp,DC=ca member: CN=Ian Crowe,CN=Users,DC=ads,DC=orcorp,DC=ca distinguishedName: CN=Print Operators,CN=Builtin,DC=ads,DC=orcorp,DC=ca instanceType: 4 whenCreated: 20080729165935.0Z whenChanged: 20080808163035.0Z uSNCreated: 8209 uSNChanged: 30817 name: Print Operators objectGUID:: SBkgyF4upEG4GO6bRhj17g== objectSid:: AQIAAAUgJgIAAA== adminCount: 1 sAMAccountName: Print Operators sAMAccountType: 536870912 systemFlags: -1946157056 groupType: -2147483643 objectCategory: CN=Group,CN=Schema,CN=Configuration,DC=ads,DC=orcorp,DC=ca isCriticalSystemObject: TRUE # wsudoers, Users, ads.orcorp.ca dn: CN=wsudoers,CN=Users,DC=ads,DC=orcorp,DC=ca objectClass: top objectClass: group cn: wsudoers description: Workstation Sudoers member: CN=Rolf Manderscheid,CN=Users,DC=ads,DC=orcorp,DC=ca member: CN=Jason Gunthorpe,CN=Users,DC=ads,DC=orcorp,DC=ca member: CN=Ian Crowe,CN=Users,DC=ads,DC=orcorp,DC=ca distinguishedName: CN=wsudoers,CN=Users,DC=ads,DC=orcorp,DC=ca instanceType: 4 whenCreated: 20080808044201.0Z whenChanged: 2030193544.0Z uSNCreated: 30255 info: Members can use sudo on the workstations uSNChanged: 2007454 name: wsudoers objectGUID:: oYEd5AZTyESv6SHZoxBGeQ== objectSid:: AQUAAAUVmm48yDCxnAEu012CfgQAAA== sAMAccountName: wsudoers sAMAccountType: 536870912 managedBy: CN=Jason Gunthorpe,CN=Users,DC=ads,DC=orcorp,DC=ca groupType: -2147483644 objectCategory: CN=Group,CN=Schema,CN=Configuration,DC=ads,DC=orcorp,DC=ca msSFU30Name: wsudoers msSFU30NisDomain: ads gidNumber: 1002 ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- 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/1315565 Title: nss-winbind is returing -1 for supplemental groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1315565/+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 1278635] Re: Panic or segfault in Samba
*** This bug is a duplicate of bug 1276414 *** https://bugs.launchpad.net/bugs/1276414 ** This bug has been marked a duplicate of bug 1276414 Panic or segfault in Samba -- 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/1278635 Title: Panic or segfault in Samba To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1278635/+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 1287408] Re: Panic or segfault in Samba
*** This bug is a duplicate of bug 1276414 *** https://bugs.launchpad.net/bugs/1276414 ** This bug has been marked a duplicate of bug 1276414 Panic or segfault in Samba -- 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/1287408 Title: Panic or segfault in Samba To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1287408/+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 1277625] Re: Panic or segfault in Samba
*** This bug is a duplicate of bug 1276414 *** https://bugs.launchpad.net/bugs/1276414 ** This bug has been marked a duplicate of bug 1276414 Panic or segfault in Samba -- 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/1277625 Title: Panic or segfault in Samba To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1277625/+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 1261898] Re: pci_devices does not terminate at computer shutdown
*** This bug is a duplicate of bug 1263704 *** https://bugs.launchpad.net/bugs/1263704 ** This bug has been marked a duplicate of bug 1263704 pci_devices does not terminate at computer shutdown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1261898 Title: pci_devices does not terminate at computer shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1261898/+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 1267564] Re: etckeeper with git breaks upgrade from Precise to Trusty
This is getting really annoying since 14.04 again. After each installation of a packet via the software center there comes the message again, that the username and email should not be set although they are set. ** Changed in: etckeeper (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1267564 Title: etckeeper with git breaks upgrade from Precise to Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1267564/+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 1315576] [NEW] package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 126
Public bug reported: subprocess installed post-installation script returned error exit status 126 ProblemType: Package DistroRelease: Ubuntu 12.04 Package: samba4 4.0.0~alpha18.dfsg1-4ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-61.92-generic-pae 3.2.55 Uname: Linux 3.2.0-61-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 Date: Fri May 2 21:11:26 2014 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 126 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MarkForUpload: True SourcePackage: samba4 Title: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 126 UpgradeStatus: Upgraded to precise on 2014-05-01 (1 days ago) ** Affects: samba4 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba4 in Ubuntu. https://bugs.launchpad.net/bugs/1315576 Title: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 126 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1315576/+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 1273462] Re: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists
** Also affects: upstart (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: mysql-5.5 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: upstart (Ubuntu Utopic) Importance: Critical Assignee: Dimitri John Ledkov (xnox) Status: Triaged ** Also affects: mysql-5.5 (Ubuntu Utopic) Importance: Medium Status: Invalid ** Changed in: mysql-5.5 (Ubuntu Trusty) Status: New => Invalid ** Changed in: upstart (Ubuntu Trusty) Status: New => Triaged ** Changed in: upstart (Ubuntu Trusty) Importance: Undecided => High ** Changed in: upstart (Ubuntu Trusty) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: upstart (Ubuntu Utopic) Status: Triaged => In Progress ** Bug watch added: Debian Bug tracker #712763 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712763 ** Also affects: upstart (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712763 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1273462 Title: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/+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 1173952] Re: Suspend and hibernate not working in 13.04/13.10 with alx module
Id did not happen with 13.04, but now after automated update to 14.04 LTS. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1173952 Title: Suspend and hibernate not working in 13.04/13.10 with alx module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173952/+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
