Pardon, I mean
http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-13-current.tar.gz
of course.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1458323
Title:
Asterisk cra
http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-11-current.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1458323
Title:
Asterisk crashes with default install
A good first step would be upgrading to latest upstream LTS release which is
13.6.0
Chances are - it's already fixed there.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1458323
Ti
Blacklisting res_pjsip is by no mean "fix" - the chan_sip is legacy
stack, the pjsip is the one recommended to use. If asterisk in ubuntu is
so broken that pjsip is not working properly than it's good enough
reason to switch distro.
I think the importance got to be set to critical.
--
You receiv
Workaround until ubuntu will finally decide to migrate from ancient squid
version is to use ppa:
https://launchpad.net/~brightbox/+archive/ubuntu/squid-ssl
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.l
Public bug reported:
All the ubuntu version ship embarrassingly old version of squid which does not
even have TLS support in it!
This is both useless and insecure. The obvious solution would be to switch to
adequate version and get TLS support enabled by default.
** Affects: squid (Ubuntu)
Bug trackers are for information related to bugs. If you're unable to
contribute something meaningful - go whine someplace else: there're
forums, twitter, social networks for that.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in
> I'm not a systemd hater
Don't flatter yourself. Since when exactly inability of some users to
run "sudo apt install ntpdate" equals to "systemd hegemony"?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.l
My bad - turned out to be permission issue which prevented asterisk from
reading it's config files. Nevertheless - having native .service file
instead of legacy shell script would make this a bit easier to
troubleshoot.
** Changed in: asterisk (Ubuntu)
Status: New => Invalid
--
You receiv
Public bug reported:
lxc-attach -n mycont -- timedatectl
Failed to create bus connection: No such file or directory
while on the host timedatectl works just fine.
lxc Version: 1.1.2-0ubuntu3 on ubuntu 15.04 x86_64
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You
Attached are the only 2 modified configuration files.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1477105
Title:
asterisk failed to start under systemd
To manage notifications
** Attachment added: "sip.conf"
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1477105/+attachment/4432500/+files/sip.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/
** Attachment added: "extensions.conf"
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1477105/+attachment/4432499/+files/extensions.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launc
Public bug reported:
Installed asterisk from repo on 15.04 x86_64: Version: 1:13.1.0~dfsg-1ubuntu2
When started automatically on boot it's failing - no binding to ports 5060 for
unknown reason.
Curiously when started manually (as root of course) asterisk is working
just fine. So I guess it's hai
Public bug reported:
I've created privileged lxc container on ubuntu 15.04 x86_64 (sudo lxc-
create...) added their ethernet interface connected to dsl modem - so
far so good: pppoe-discovery from inside the container recognoze it,
pppoeconf is able to configure it.
The problem is that the contai
Thanks for clarification! Would be kinda helpful if lxc-start could
print actual numbers (X quota configured for bridge123, Y is in use).
What's the upper limit on those quota numbers? Can I have 100 bridges
with 400 interfaces in each?
--
You received this bug notification because you are a
lxc-start -n asterisk -F
Quota reached.
lxc-start: start.c: lxc_spawn: 1000 failed to create configured network
lxc-start: start.c: __lxc_start: 1164 failed to spawn 'asterisk'
lxc-start: start.c: main: 344 The container failed to start.
lxc-start: start.c: main 348 Additional information can be ob
Also, what does "Quota reached." mean? What kind of quota is that?
--
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/1470580
Title:
unprivileged lxc containers fails with custom bridge
To
Btw, is there a way to make logging to actually work and log everything?
Maybe add --logging-indeed-log or smth like that in addition to existing -l and
--logfile?
** Changed in: lxc (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member o
cat /etc/lxc/lxc-usernet
# USERNAME TYPE BRIDGE COUNT
x veth ibr1 8
x veth xbr1 8
x veth ubr1 8
cat .local/share/lxc/asterisk/config
# Template used to create this container
Commenting those 2 lines change nothing - same error. Is there way to
figure out what exactly went wrong while creating network? The log seems
way too brief about it even with debug enabled.
** Changed in: lxc (Ubuntu)
Status: Incomplete => New
--
You received this bug notification becaus
Public bug reported:
Using 15.04 x86_64 with all the updates installed.
I'd like 2 containers to communicate with each other via bridge interface. For
that I've created interface as follows:
/etc/systemd/network/internalbridge1.netdev:
[NetDev]
Name=ibr1
Kind=bridge
/etc/lxc/lxc-usernet:
# USERN
cat /etc/os-release
NAME="Ubuntu"
VERSION="15.04 (Vivid Vervet)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 15.04"
VERSION_ID="15.04"
HOME_URL="http://www.ubuntu.com/";
SUPPORT_URL="http://help.ubuntu.com/";
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
That's another one I think. Let me
How does this triggering happens normally? I mean should ssh server call
something specific explicitly?
--
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/1467611
Title:
unprivileged lxc co
I still don't get the point about lsh - I mean what's the difference
with openssh? Are there some specific step by ssh server with regards to
user session setup necessary? Or some specific system-wide configuration
required somewhere?
--
You received this bug notification because you are a member
cat /proc/self/cgroup
10:cpuset:/system.slice/lsh-server.service
9:memory:/system.slice/lsh-server.service
8:freezer:/system.slice/lsh-server.service
7:blkio:/system.slice/lsh-server.service
6:hugetlb:/system.slice/lsh-server.service
5:perf_event:/system.slice/lsh-server.service
4:cpu,cpuacct:/syst
cat /proc/self/cgroups
cat: /proc/self/cgroups: No such file or directory
Hmm.. what ssh server have to do with this?
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
What is "regular user session"? Does ssh connection counts or it have to
be local console login?
** Changed in: lxc (Ubuntu)
Status: Incomplete => New
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Yes, I thought it would be more clear cause I can't change the title of
this bug. Once the patch is applied and updated meta-packages pushed
both bugs could be safely closed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu
It would be much better to replace it with systemd-timesyncd calls and
drop ntpdate dependency altogether.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/583994
Title:
Consider replacin
Is there some detailed notes on why upstart is still used for user
sessions instead of systemd? Is it just lack of time or there are some
technical reasons not to switch to systemd here as well?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscri
So the only thing needed to fix this bug is to update squid to 3.5 and
rebuild with --enable-ssl while having libnettle and gnutls installed?
Or there are some changes to package build-depends required?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
32 matches
Mail list logo
