[Bug 1381410] Re: [SRU] 0.80.7 stable update
** Branch linked: lp:~james-page/ubuntu/utopic/ceph/0.80.7 -- 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/1381410 Title: [SRU] 0.80.7 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1381410/+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 1266127] Change abandoned on python-cinderclient (master)
Change abandoned by Chris Buccella (ch...@buccella.org) on branch: master Review: https://review.openstack.org/64981 Reason: common/apiclient/base.py already does this now; this change is no longer needed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-cinderclient in Ubuntu. https://bugs.launchpad.net/bugs/1266127 Title: Use strutils.to_slug() instead of utils.slugify() To manage notifications about this bug go to: https://bugs.launchpad.net/python-cinderclient/+bug/1266127/+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 1280025] Re: libnss-winbind should be installed per default on desktop systems
How can I contribute this change? -- 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/1280025 Title: libnss-winbind should be installed per default on desktop systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1280025/+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 1389897] Re: no way to install "enough qemu for kvm" in a cross platform way
And finally one that builds a package that doesn't scare lintian. ** Patch added: "qemu-kvm-arches-3.diff" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+attachment/4254389/+files/qemu-kvm-arches-3.diff ** Patch removed: "qemu-kvm-arches-2.diff" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+attachment/4254290/+files/qemu-kvm-arches-2.diff ** Patch removed: "qemu-kvm-arches.diff" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+attachment/4254175/+files/qemu-kvm-arches.diff -- 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/1389897 Title: no way to install "enough qemu for kvm" in a cross platform way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1389897/+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 1382190] Re: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries
This was confirmed fixed today by Juan Ciarlante and will go out with 1.7.0. Fantastic! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+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 1389830] Re: Don't use wlan0 for cluster to region communication [when cluster and region are on same machine]
Could packaging detect whether the cluster and region are on the same machine and if so use lo? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1389830 Title: Don't use wlan0 for cluster to region communication [when cluster and region are on same machine] To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1389830/+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 1379144] Re: maas-proxy package won't install when upgrading from older version
** Changed in: maas Status: Invalid => Fix Committed ** Branch linked: lp:~andreserl/maas/release_beta7_utopic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1379144 Title: maas-proxy package won't install when upgrading from older version To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1379144/+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 1389849] Re: sudo service lxc-net restart does not reload dnsmasq when there is a container running
There is also a little more advanced solution, that claims to be compatible with systemd as well: https://github.com/CameronNemo/lxc-net -- 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/1389849 Title: sudo service lxc-net restart does not reload dnsmasq when there is a container running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389849/+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 1389534] Re: package sa-compile 3.4.0-3 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: spamassassin (Ubuntu) Status: New => Confirmed -- 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/1389534 Title: package sa-compile 3.4.0-3 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/spamassassin/+bug/1389534/+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 1390012] [NEW] "/etc/init.d/ssh stop" does not stop ssh server processes
You have been subscribed to a public bug: Running "/etc/init.d/ssh stop" does not result in ssh server being stopped. Running "service ssh stop" works fine. As a result, running "/etc/init.d/ssh restart" does not restart sshd so new settings from sshd_config won't be loaded. Using "service ssh restart" works fine, but ideally using the init script should still work as long as it's still there. ** Affects: openssh (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment ssh -- "/etc/init.d/ssh stop" does not stop ssh server processes https://bugs.launchpad.net/bugs/1390012 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. -- 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 1390012] Re: "/etc/init.d/ssh stop" does not stop ssh server processes
** Package changed: ubuntu => openssh (Ubuntu) -- 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/1390012 Title: "/etc/init.d/ssh stop" does not stop ssh server processes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1390012/+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 1377964] Re: maas-proxy logrotate permission denied
Also affected by this issue: 1.7rc1 (upgraded from 1.5.2) at /var/log/syslog: Nov 6 06:25:01 duck squid3: Cannot open stdio:/var/log/maas/proxy/store.log: (13) Permission denied -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1377964 Title: maas-proxy logrotate permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1377964/+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 1367782] Re: endpoint_type being ignored
Bump. Any ETA on getting this merged? At present Glance is unusable in Juno when using internalURL by default. ** Also affects: python-glanceclient (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-glanceclient in Ubuntu. https://bugs.launchpad.net/bugs/1367782 Title: endpoint_type being ignored To manage notifications about this bug go to: https://bugs.launchpad.net/python-glanceclient/+bug/1367782/+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 1377964] Re: maas-proxy logrotate permission denied
** Changed in: maas (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1377964 Title: maas-proxy logrotate permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1377964/+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 1377964] Re: maas-proxy logrotate permission denied
** Branch linked: lp:~andreserl/maas/lp1377964_proxy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1377964 Title: maas-proxy logrotate permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1377964/+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 497732] Re: backuppc errors: "Tar exited with error 512 ()" due to read permission failures
#15, Wayne Law, the problem is still recurring. Your solution helped me fix it, just wanted to say thanks that it worked for me! :D -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to backuppc in Ubuntu. https://bugs.launchpad.net/bugs/497732 Title: backuppc errors: "Tar exited with error 512 ()" due to read permission failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/497732/+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 1389647] Re: lm-sensors don`t recognize fan in the laptop ASUS M50VN
If sensors-detect doesn't detect it then yea, it's not supported. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1389647 Title: lm-sensors don`t recognize fan in the laptop ASUS M50VN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1389647/+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 1373261] Re: pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
** Description changed:
- Reconfiguring between an IPv4-based and an IPv6-based MAAS_URL broke the
- ‘generator’ setting in my pserv.yaml: it ended up being the full IPv4
- netloc, with most of the IPv6 netloc tacked onto it.
+ Reconfiguring when the existing MAAS_URL used an IPv6 host address broke
+ the ‘generator’ setting in my pserv.yaml: it ended up being the full
+ newly configured netloc, with most of the previous IPv6 netloc tacked
+ onto it.
I think that's because the regex in maas-cluster-controller.postinst
mistakes the first colon in an IPv6 address for the beginning of a port
specifier:
- sed -i "s|MAAS_URL=.*|MAAS_URL=\"$RET\"|" /etc/maas/maas_cluster.conf
- # Extract the hostname part.
- HOSTPART=$(echo $RET|awk '{ split($0,array,"/")} END{print array[3]
}')
- # And substitute it in-place in pserv.yaml on an indented,
non-commented
- # line.
- sed -ri
"s|^([[:space:]]+)(#+[[:space:]]*)?(generator:[[:space:]]+https?://)[^:/]+|\1\3$HOSTPART|"
/etc/maas/pserv.yaml
+ sed -i "s|MAAS_URL=.*|MAAS_URL=\"$RET\"|" /etc/maas/maas_cluster.conf
+ # Extract the hostname part.
+ HOSTPART=$(echo $RET|awk '{ split($0,array,"/")} END{print array[3]
}')
+ # And substitute it in-place in pserv.yaml on an indented,
non-commented
+ # line.
+ sed -ri
"s|^([[:space:]]+)(#+[[:space:]]*)?(generator:[[:space:]]+https?://)[^:/]+|\1\3$HOSTPART|"
/etc/maas/pserv.yaml
These things are still best done in Python I suppose.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1373261
Title:
pserv.yaml rewrite breaks when MAAS URL uses IPv6 address
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1373261/+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 1390132] [NEW] Cannot change the maximum number of filedescriptors
Public bug reported: The max_filedescriptors configuration directive is being ignored on Trusty. To reproduce the problem, set max_filedescriptors in squid.conf and run the following command: squid3 -k parse 2>&1|grep max_filedescriptors The following output should result. 2014/11/06 15:21:15| WARNING: max_filedescriptors disabled. Operating System setrlimit(RLIMIT_NOFILE) is missing. Indeed, regardless of the max_filedescriptors value specified in squid.conf, squid will run with a maximum of 65536 file descriptors available. This can be verified with: grep 'file descriptor' /var/log/squid3/cache.log 2014/11/06 15:30:45| With 65536 file descriptors available The reason for this is that squid has been built with --with- filedescriptors=65536 Rebuilding the package without --with-filedescriptors, squid honors the maximum number of open file descriptors set with ulimit. Fedora also had a similar problem: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=976815 Thanks, Emanuele apt-cache policy squid3 | grep Installed Installed: 3.3.8-1ubuntu6.1 lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New -- 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/1390132 Title: Cannot change the maximum number of filedescriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1390132/+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 1390132] Re: Cannot change the maximum number of filedescriptors
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: squid3 (Ubuntu) Status: New => Confirmed -- 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/1390132 Title: Cannot change the maximum number of filedescriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1390132/+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 1078213] Re: logs are not logrotated
** Changed in: juju-core Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078213 Title: logs are not logrotated To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1078213/+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 1390012] Re: "/etc/init.d/ssh stop" does not stop ssh server processes
What release did you notice this on? It worked fine for me on Vivid. [ 8:26AM ] [ bdmurray@impulse:~ ] $ sudo /etc/init.d/ssh stop ssh stop/waiting [ 8:27AM ] [ bdmurray@impulse:~ ] $ ssh localhost ssh: connect to host localhost port 22: Connection refused ** Changed in: openssh (Ubuntu) Status: Confirmed => Incomplete -- 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/1390012 Title: "/etc/init.d/ssh stop" does not stop ssh server processes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1390012/+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 1390012] Re: "/etc/init.d/ssh stop" does not stop ssh server processes
Confirmed on third installation now, two servers and a desktop. ** Changed in: openssh (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - "/etc/init.d/ssh stop" does not stop ssh server processes + "/etc/init.d/ssh stop" does not stop ssh server processes on 14.04 -- 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/1390012 Title: "/etc/init.d/ssh stop" does not stop ssh server processes on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1390012/+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: [Aims] [Bug 1390012] Re: "/etc/init.d/ssh stop" does not stop ssh server processes
Server and desktop 14.04: 0 root@kontiki:~#ps auxw|grep sshd: root 7361 0.0 0.1 111844 4072 ?Ss Nov03 0:00 sshd: jan [priv] jan 7537 0.0 0.0 111844 2076 ?SNov03 0:00 sshd: jan@pts/9 root 32177 0.0 0.0 8864 652 pts/9S+ 18:37 0:00 grep --color=auto sshd: 0 root@kontiki:~#/etc/init.d/ssh restart 1 root@kontiki:~#ps auxw|grep sshd: root 7361 0.0 0.1 111844 4072 ?Ss Nov03 0:00 sshd: jan [priv] jan 7537 0.0 0.0 111844 2076 ?SNov03 0:00 sshd: jan@pts/9 root 32186 0.0 0.0 8864 652 pts/9S+ 18:37 0:00 grep --color=auto sshd: 0 root@kontiki:~#date Thu Nov 6 18:37:17 SAST 2014 0 root@kontiki:~#/etc/init.d/ssh stop 0 root@kontiki:~#ps axuw|grep sshd root 1513 0.0 0.0 61364 2796 ?Ss Nov02 0:00 /usr/sbin/sshd -D root 7361 0.0 0.1 111844 4072 ?Ss Nov03 0:00 sshd: jan [priv] jan 7537 0.0 0.0 111844 2076 ?SNov03 0:00 sshd: jan@pts/9 root 32198 0.0 0.0 8868 652 pts/9R+ 18:37 0:00 grep --color=auto sshd 0 root@kontiki:~#lsb_release -d Description:Ubuntu 14.04.1 LTS 0 root@kontiki:~# On 6 November 2014 18:36, Jan Groenewald wrote: > 14.04 server installs. > > > On 6 November 2014 18:27, Brian Murray wrote: > >> What release did you notice this on? It worked fine for me on Vivid. >> >> [ 8:26AM ] [ bdmurray@impulse:~ ] >> $ sudo /etc/init.d/ssh stop >> ssh stop/waiting >> [ 8:27AM ] [ bdmurray@impulse:~ ] >> $ ssh localhost >> ssh: connect to host localhost port 22: Connection refused >> >> >> ** Changed in: openssh (Ubuntu) >>Status: Confirmed => Incomplete >> >> -- >> You received this bug notification because you are a member of AIMS, >> which is subscribed to the bug report. >> https://bugs.launchpad.net/bugs/1390012 >> >> Title: >> "/etc/init.d/ssh stop" does not stop ssh server processes >> >> Status in “openssh” package in Ubuntu: >> Incomplete >> >> Bug description: >> Running "/etc/init.d/ssh stop" does not result in ssh server being >> stopped. Running "service ssh stop" works fine. >> >> As a result, running "/etc/init.d/ssh restart" does not restart sshd >> so new settings from sshd_config won't be loaded. >> >> Using "service ssh restart" works fine, but ideally using the init >> script should still work as long as it's still there. >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1390012/+subscriptions >> >> -- >> Mailing list: https://launchpad.net/~aims >> Post to : a...@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~aims >> More help : https://help.launchpad.net/ListHelp >> > > > > -- > .~. > /V\ Jan Groenewald > /( )\www.aims.ac.za > ^^-^^ > -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- 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/1390012 Title: "/etc/init.d/ssh stop" does not stop ssh server processes on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1390012/+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: [Aims] [Bug 1390012] Re: "/etc/init.d/ssh stop" does not stop ssh server processes
14.04 server installs. On 6 November 2014 18:27, Brian Murray wrote: > What release did you notice this on? It worked fine for me on Vivid. > > [ 8:26AM ] [ bdmurray@impulse:~ ] > $ sudo /etc/init.d/ssh stop > ssh stop/waiting > [ 8:27AM ] [ bdmurray@impulse:~ ] > $ ssh localhost > ssh: connect to host localhost port 22: Connection refused > > > ** Changed in: openssh (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are a member of AIMS, > which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/1390012 > > Title: > "/etc/init.d/ssh stop" does not stop ssh server processes > > Status in “openssh” package in Ubuntu: > Incomplete > > Bug description: > Running "/etc/init.d/ssh stop" does not result in ssh server being > stopped. Running "service ssh stop" works fine. > > As a result, running "/etc/init.d/ssh restart" does not restart sshd > so new settings from sshd_config won't be loaded. > > Using "service ssh restart" works fine, but ideally using the init > script should still work as long as it's still there. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1390012/+subscriptions > > -- > Mailing list: https://launchpad.net/~aims > Post to : a...@lists.launchpad.net > Unsubscribe : https://launchpad.net/~aims > More help : https://help.launchpad.net/ListHelp > -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- 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/1390012 Title: "/etc/init.d/ssh stop" does not stop ssh server processes on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1390012/+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: [Aims] [Bug 1390012] Re: "/etc/init.d/ssh stop" does not stop ssh server processes
Bad example in previous post; here it is better: 0 root@kontiki:~#ps axuw|grep sbin/sshd root 32302 0.0 0.0 61364 3052 ?Ss *18:51* 0:00 /usr/sbin/sshd -D root 32310 0.0 0.0 8864 648 pts/9S+ 18:53 0:00 grep --color=auto sbin/sshd 0 root@kontiki:~#date Thu Nov 6 *18:53*:34 SAST 2014 0 root@kontiki:~#/etc/init.d/ssh restart # doesn't work 1 root@kontiki:~#ps axuw|grep sbin/sshd root 32302 0.0 0.0 61364 3052 ?Ss *18:51 * 0:00 /usr/sbin/sshd -D root 32320 0.0 0.0 8864 652 pts/9S+ 18:53 0:00 grep --color=auto sbin/sshd 0 root@kontiki:~#date Thu Nov 6 *18:53*:44 SAST 2014 0 root@kontiki:~#restart ssh # works ssh start/running, process 32325 0 root@kontiki:~#date Thu Nov 6 *18:53*:52 SAST 2014 0 root@kontiki:~#ps axuw|grep sbin/sshd root 32325 0.0 0.0 61364 3048 ?Ss *18:53* 0:00 /usr/sbin/sshd -D root 32329 0.0 0.0 8864 652 pts/9S+ 18:53 0:00 grep --color=auto sbin/sshd 0 root@kontiki:~# On 6 November 2014 18:38, Jan Groenewald wrote: > Server and desktop 14.04: > > 0 root@kontiki:~#ps auxw|grep sshd: > root 7361 0.0 0.1 111844 4072 ?Ss Nov03 0:00 sshd: jan > [priv] > jan 7537 0.0 0.0 111844 2076 ?SNov03 0:00 sshd: > jan@pts/9 > root 32177 0.0 0.0 8864 652 pts/9S+ 18:37 0:00 grep > --color=auto sshd: > 0 root@kontiki:~#/etc/init.d/ssh restart > 1 root@kontiki:~#ps auxw|grep sshd: > root 7361 0.0 0.1 111844 4072 ?Ss Nov03 0:00 sshd: jan > [priv] > jan 7537 0.0 0.0 111844 2076 ?SNov03 0:00 sshd: > jan@pts/9 > root 32186 0.0 0.0 8864 652 pts/9S+ 18:37 0:00 grep > --color=auto sshd: > 0 root@kontiki:~#date > Thu Nov 6 18:37:17 SAST 2014 > 0 root@kontiki:~#/etc/init.d/ssh stop > 0 root@kontiki:~#ps axuw|grep sshd > root 1513 0.0 0.0 61364 2796 ?Ss Nov02 0:00 > /usr/sbin/sshd -D > root 7361 0.0 0.1 111844 4072 ?Ss Nov03 0:00 sshd: jan > [priv] > jan 7537 0.0 0.0 111844 2076 ?SNov03 0:00 sshd: > jan@pts/9 > root 32198 0.0 0.0 8868 652 pts/9R+ 18:37 0:00 grep > --color=auto sshd > 0 root@kontiki:~#lsb_release -d > Description:Ubuntu 14.04.1 LTS > 0 root@kontiki:~# > > > > On 6 November 2014 18:36, Jan Groenewald wrote: > >> 14.04 server installs. >> >> >> On 6 November 2014 18:27, Brian Murray wrote: >> >>> What release did you notice this on? It worked fine for me on Vivid. >>> >>> [ 8:26AM ] [ bdmurray@impulse:~ ] >>> $ sudo /etc/init.d/ssh stop >>> ssh stop/waiting >>> [ 8:27AM ] [ bdmurray@impulse:~ ] >>> $ ssh localhost >>> ssh: connect to host localhost port 22: Connection refused >>> >>> >>> ** Changed in: openssh (Ubuntu) >>>Status: Confirmed => Incomplete >>> >>> -- >>> You received this bug notification because you are a member of AIMS, >>> which is subscribed to the bug report. >>> https://bugs.launchpad.net/bugs/1390012 >>> >>> Title: >>> "/etc/init.d/ssh stop" does not stop ssh server processes >>> >>> Status in “openssh” package in Ubuntu: >>> Incomplete >>> >>> Bug description: >>> Running "/etc/init.d/ssh stop" does not result in ssh server being >>> stopped. Running "service ssh stop" works fine. >>> >>> As a result, running "/etc/init.d/ssh restart" does not restart sshd >>> so new settings from sshd_config won't be loaded. >>> >>> Using "service ssh restart" works fine, but ideally using the init >>> script should still work as long as it's still there. >>> >>> To manage notifications about this bug go to: >>> >>> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1390012/+subscriptions >>> >>> -- >>> Mailing list: https://launchpad.net/~aims >>> Post to : a...@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~aims >>> More help : https://help.launchpad.net/ListHelp >>> >> >> >> >> -- >> .~. >> /V\ Jan Groenewald >> /( )\www.aims.ac.za >> ^^-^^ >> > > > > -- > .~. > /V\ Jan Groenewald > /( )\www.aims.ac.za > ^^-^^ > -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- 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/1390012 Title: "/etc/init.d/ssh stop" does not stop ssh server processes on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1390012/+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 1355813] Re: LXC containers reset bridge MTU on start/restart
why is this bug incomplete? as far as I can see there is sufficient information to triage this... Yes - you have to set the mtu on the lxc container interfaces to match the bridge, otherwise it drops to the lowest MTU of any attached veth. For now I've patched the config files to set the mtu correctly - but as soon as you juju add-unit --to lxc:XX it all collapses again. For OpenStack environments running overlay networks, setting interface MTU's on hosts is absolutely critical. ** Changed in: juju-core Status: Incomplete => New ** Changed in: lxc (Ubuntu) Status: Incomplete => New ** Tags added: cts -- 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/1355813 Title: LXC containers reset bridge MTU on start/restart To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1382257] Re: Add "readme" to Azure's ephemeral (resource) disk
** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => Ben Howard (utlemming) ** Changed in: cloud-init (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1382257 Title: Add "readme" to Azure's ephemeral (resource) disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1382257/+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 1355813] Re: LXC containers reset bridge MTU on start/restart
** Tags added: cts-cloud-review ** Tags added: add-unit ** Changed in: juju-core Status: New => Triaged ** Changed in: juju-core Importance: Undecided => Medium ** Tags added: placement ** Tags added: network ** Changed in: juju-core Milestone: None => 1.22 ** Changed in: juju-core Importance: Medium => High -- 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/1355813 Title: LXC containers reset bridge MTU on start/restart To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1377325] Re: The ppc64/arm versions of Juju should depend on a more recent version of libgo5
Hello Matt, or anyone else affected, Accepted juju-core into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/juju- core/1.20.11-0ubuntu0.14.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: juju-core (Ubuntu Trusty) Status: Triaged => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1377325 Title: The ppc64/arm versions of Juju should depend on a more recent version of libgo5 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1377325/+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 1386144] Re: juju-core 1.20.11 is not packaged in Ubuntu
Hello Robie, or anyone else affected, Accepted juju-core into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/juju- core/1.20.11-0ubuntu0.14.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: juju-core (Ubuntu Trusty) Status: Triaged => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. https://bugs.launchpad.net/bugs/1386144 Title: juju-core 1.20.11 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1386144/+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 1343301] Re: juju-local needs new dep dbus -- specifically to work in lxc
Hello Greg, or anyone else affected, Accepted juju-core into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/juju- core/1.20.11-0ubuntu0.14.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: juju-core (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1343301 Title: juju-local needs new dep dbus -- specifically to work in lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1343301/+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 1377325] Re: The ppc64/arm versions of Juju should depend on a more recent version of libgo5
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1377325 Title: The ppc64/arm versions of Juju should depend on a more recent version of libgo5 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1377325/+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 1386144] Re: juju-core 1.20.11 is not packaged in Ubuntu
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. https://bugs.launchpad.net/bugs/1386144 Title: juju-core 1.20.11 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1386144/+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 1343301] Re: juju-local needs new dep dbus -- specifically to work in lxc
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1343301 Title: juju-local needs new dep dbus -- specifically to work in lxc To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1343301/+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: [Aims] [Bug 1390012] Re: "/etc/init.d/ssh stop" does not stop ssh server processes
Even better: 0 root@snapperkob:~#cat /var/run/sshd.pid 1820 0 root@snapperkob:~#/etc/init.d/ssh restart 1 root@snapperkob:~#cat /var/run/sshd.pid 1820 0 root@snapperkob:~#/etc/init.d/ssh stop 0 root@snapperkob:~#cat /var/run/sshd.pid 1820 0 root@snapperkob:~#stop ssh ssh stop/waiting 0 root@snapperkob:~#cat /var/run/sshd.pid cat: /var/run/sshd.pid: No such file or directory 1 root@snapperkob:~#start ssh ssh start/running, process 6842 0 root@snapperkob:~#cat /var/run/sshd.pid 6842 0 root@snapperkob:~# On 6 November 2014 18:55, Jan Groenewald wrote: > Bad example in previous post; here it is better: > > 0 root@kontiki:~#ps axuw|grep sbin/sshd > root 32302 0.0 0.0 61364 3052 ?Ss *18:51* 0:00 > /usr/sbin/sshd -D > root 32310 0.0 0.0 8864 648 pts/9S+ 18:53 0:00 grep > --color=auto sbin/sshd > 0 root@kontiki:~#date > Thu Nov 6 *18:53*:34 SAST 2014 > 0 root@kontiki:~#/etc/init.d/ssh restart # doesn't work > 1 root@kontiki:~#ps axuw|grep sbin/sshd > root 32302 0.0 0.0 61364 3052 ?Ss *18:51 * 0:00 > /usr/sbin/sshd -D > root 32320 0.0 0.0 8864 652 pts/9S+ 18:53 0:00 grep > --color=auto sbin/sshd > 0 root@kontiki:~#date > Thu Nov 6 *18:53*:44 SAST 2014 > 0 root@kontiki:~#restart ssh # works > ssh start/running, process 32325 > 0 root@kontiki:~#date > Thu Nov 6 *18:53*:52 SAST 2014 > 0 root@kontiki:~#ps axuw|grep sbin/sshd > root 32325 0.0 0.0 61364 3048 ?Ss *18:53* 0:00 > /usr/sbin/sshd -D > root 32329 0.0 0.0 8864 652 pts/9S+ 18:53 0:00 grep > --color=auto sbin/sshd > 0 root@kontiki:~# > > > On 6 November 2014 18:38, Jan Groenewald wrote: > >> Server and desktop 14.04: >> >> 0 root@kontiki:~#ps auxw|grep sshd: >> root 7361 0.0 0.1 111844 4072 ?Ss Nov03 0:00 sshd: >> jan [priv] >> jan 7537 0.0 0.0 111844 2076 ?SNov03 0:00 sshd: >> jan@pts/9 >> root 32177 0.0 0.0 8864 652 pts/9S+ 18:37 0:00 grep >> --color=auto sshd: >> 0 root@kontiki:~#/etc/init.d/ssh restart >> 1 root@kontiki:~#ps auxw|grep sshd: >> root 7361 0.0 0.1 111844 4072 ?Ss Nov03 0:00 sshd: >> jan [priv] >> jan 7537 0.0 0.0 111844 2076 ?SNov03 0:00 sshd: >> jan@pts/9 >> root 32186 0.0 0.0 8864 652 pts/9S+ 18:37 0:00 grep >> --color=auto sshd: >> 0 root@kontiki:~#date >> Thu Nov 6 18:37:17 SAST 2014 >> 0 root@kontiki:~#/etc/init.d/ssh stop >> 0 root@kontiki:~#ps axuw|grep sshd >> root 1513 0.0 0.0 61364 2796 ?Ss Nov02 0:00 >> /usr/sbin/sshd -D >> root 7361 0.0 0.1 111844 4072 ?Ss Nov03 0:00 sshd: >> jan [priv] >> jan 7537 0.0 0.0 111844 2076 ?SNov03 0:00 sshd: >> jan@pts/9 >> root 32198 0.0 0.0 8868 652 pts/9R+ 18:37 0:00 grep >> --color=auto sshd >> 0 root@kontiki:~#lsb_release -d >> Description:Ubuntu 14.04.1 LTS >> 0 root@kontiki:~# >> >> >> >> On 6 November 2014 18:36, Jan Groenewald wrote: >> >>> 14.04 server installs. >>> >>> >>> On 6 November 2014 18:27, Brian Murray wrote: >>> What release did you notice this on? It worked fine for me on Vivid. [ 8:26AM ] [ bdmurray@impulse:~ ] $ sudo /etc/init.d/ssh stop ssh stop/waiting [ 8:27AM ] [ bdmurray@impulse:~ ] $ ssh localhost ssh: connect to host localhost port 22: Connection refused ** Changed in: openssh (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of AIMS, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1390012 Title: "/etc/init.d/ssh stop" does not stop ssh server processes Status in “openssh” package in Ubuntu: Incomplete Bug description: Running "/etc/init.d/ssh stop" does not result in ssh server being stopped. Running "service ssh stop" works fine. As a result, running "/etc/init.d/ssh restart" does not restart sshd so new settings from sshd_config won't be loaded. Using "service ssh restart" works fine, but ideally using the init script should still work as long as it's still there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1390012/+subscriptions -- Mailing list: https://launchpad.net/~aims Post to : a...@lists.launchpad.net Unsubscribe : https://launchpad.net/~aims More help : https://help.launchpad.net/ListHelp >>> >>> >>> >>> -- >>> .~. >>> /V\ Jan Groenewald >>> /( )\www.aims.ac.za >>> ^^-^^ >>> >> >> >> >> -- >> .~. >> /V\ Jan Groenewald >> /( )\www.aims.ac.za >> ^^-^^ >> > > > > -- > .~. > /V\ Jan Groenewald > /( )\www.aims.ac.za > ^^-^^ > -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- You received this bug
[Bug 1386052] Re: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced
I've decided not to accept the Utopic SRU of this until Haw's comment regarding it not logging anymore is addressed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollen in Ubuntu. https://bugs.launchpad.net/bugs/1386052 Title: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollen/+bug/1386052/+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 1366174] Re: apache2 SEGV with multiple SSL sites
I have attached a backport to 2.4.7 to this comment. This is a backport of the backport to 2.4.x in upstream svn. More details in the commit message. This is a straight patch to the source (produced from git) rather than a proper packaged up patch, if you see what I mean. I've put this up on github too for ease of review: https://github.com/abligh/apache2-2.4.7-ubuntu-trusty/commit/6e24e496c7aee8aa1ff13a41dae71c91fe8c0bbe ** Patch added: "LP#1366174: Backport PR54357 to 2.4.7 - Crash during restart or at startup in mod_ssl, in certinfo_free() function registered by ssl_stapling_ex_init()" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1366174/+attachment/4254782/+files/0001-LP-1366174-Backport-PR54357-to-2.4.7-Crash-during-re.patch -- 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/1366174 Title: apache2 SEGV with multiple SSL sites To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1366174/+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 1390240] [NEW] Sync euca2ools 3.1.0-1 (main) from Debian unstable (main)
Public bug reported: Please sync euca2ools 3.1.0-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * fix euca-get-console-output when redirected to a file (LP: #1266898). * fix euca-get-console-output when redirected to a file (LP: #1266898). * fix euca-get-console-output when redirected to a file (LP: #1266898). Patch has been fixed upstream (look @ file euca2ools/commands/ec2/getconsoleoutput.py line 58 instead of no more existing euca2ools/commands/euca/getconsoleoutput.py) Changelog entries since current vivid version 3.0.2-1ubuntu1: euca2ools (3.1.0-1) unstable; urgency=medium 5d9d911 Merge tag 'v3.1.0' into debian/unstable Closes: #734616, #758910 1cf5c42 Depends on python-requestbuilder >= 0.2.3. bc2ef72 Conforms to Policy 3.9.6. -- Charles Plessy Thu, 09 Oct 2014 08:20:20 +0900 ** Affects: euca2ools (Ubuntu) Importance: Wishlist Status: New ** Changed in: euca2ools (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to euca2ools in Ubuntu. https://bugs.launchpad.net/bugs/1390240 Title: Sync euca2ools 3.1.0-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/euca2ools/+bug/1390240/+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 1387881] Re: qemu fails to recognize full virtualization
Answers to some of your questions: Can you only get this on one particular host (i.e. hardware type)? - No as I can repro in KVM -Is there anything in syslog? - Nothing relevant Which packages (dpkg -l | grep qemu) ii qemu-utils 2.0.0+dfsg-2ubuntu1.6 amd64 QEMU utilities Does a reboot (without installing new packages) fix the problem? - No -- 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/1387881 Title: qemu fails to recognize full virtualization To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1387881/+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 1382257] Re: Add "readme" to Azure's ephemeral (resource) disk
Uploaded a new version of walinuxagent that includes an upstart job that will provide the warning. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1382257 Title: [SRU] Add "readme" to Azure's ephemeral (resource) disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1382257/+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 1377964] Re: maas-proxy logrotate permission denied
** Changed in: maas (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1377964 Title: maas-proxy logrotate permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1377964/+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 1382257] Re: Add "readme" to Azure's ephemeral (resource) disk
This will need to be SRU'd back to prior releases. I debated making this a build recipe piece, however, I think that the logic here should be up- datable. After it appears in Vivid, I'll start the SRU process for this. ** Summary changed: - Add "readme" to Azure's ephemeral (resource) disk + [SRU] Add "readme" to Azure's ephemeral (resource) disk ** Description changed: - When the Azure Linux agent handles the resource disk it adds a file on - the newly formatted partition called "DATALOSS_WARNING_README.txt". The - purpose of this file is to warn customers that the disk is temporary and - may be wiped if the VM is rebooted or moved to another host. + [JUSTIFICATION] Ephemeral disks on Azure are per-boot ephemeral are + unsafe for storing data. Microsoft has asked that a warning file be + placed on the disks. This would normally be handled by the agent, + however, since Ubuntu uses cloud-init for provisioning of the ephemeral + disk, the warning file is not placed. + + [FIX] Added an upstart job that places the warning file on the ephemeral + device when the instance is provisioned using Cloud-init. + + [TEST] + 1. Install new version of walinuxagent + 2. Reboot + 3. Confirm that DATALOSS_WARNING_README.txt exists + 4. Run "chattr -i /mnt/DATALOSS_WARNING_README.txt" + 5. Reboot + 6. Confirm that DATALOSS_WARNING_README.txt is re-written + + [ORIGINAL REPORT] + When the Azure Linux agent handles the resource disk it adds a file on the newly formatted partition called "DATALOSS_WARNING_README.txt". The purpose of this file is to warn customers that the disk is temporary and may be wiped if the VM is rebooted or moved to another host. Since cloud-init handles the resource disk for Ubuntu VMs in Azure, can we have cloud-init add this file as well when it formats the resource/ephemeral disk? In the Linux agent we have to following code to define this file: - README_FILENAME="DATALOSS_WARNING_README.txt" README_FILECONTENT="""\ WARNING: THIS IS A TEMPORARY DISK. Any data stored on this drive is SUBJECT TO LOSS and THERE IS NO WAY TO RECOVER IT. Please do not use this disk for storing any personal or application data. For additional details to please refer to the MSDN documentation at : http://msdn.microsoft.com/en-us/library/windowsazure/jj672979.aspx """ - -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1382257 Title: [SRU] Add "readme" to Azure's ephemeral (resource) disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1382257/+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 1389830] Re: Don't use wlan0 for cluster to region communication [when cluster and region are on same machine]
On Thursday 06 Nov 2014 11:22:56 you wrote: > Could packaging detect whether the cluster and region are on the same > machine and if so use lo? Kind of - if you're installing the all-in-one meta "maas" package it *could*, however it still needs an IP address, and it doesn't matter if it's the lo or the eth* one as the kernel optimises that away for you anyway. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1389830 Title: Don't use wlan0 for cluster to region communication [when cluster and region are on same machine] To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1389830/+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
