Public bug reported:
Looks like unattended-upgrades failed?
I just ran the update again and it installed an altered config file.
#> apt-get install ntpdate
Setting up ntpdate (1:4.2.6.p5+dfsg-3ubuntu2.14.04.10) ...
Configuration file '/etc/network/if-up.d/ntpdate'
==> Deleted (by you or by a
I'm attaching the email from unattended-upgrades which I think caused
the problem.
** Attachment added: "email output from unattended-upgrades"
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1631789/+attachment/4758355/+files/unattended-upgrades-output.txt
--
You received this bug
** Summary changed:
- failed call to setgid causes 500 internal server error
+ Does not support uid's and gid's above 65535 on x86-64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517214
Title:
Juerg is right. I actually took this problem to upstream's mailing list:
https://lists.err.no/pipermail/mpm-itk/2015-November/000958.html
Juerg's patch seems to unconditionally cap gid's and uid's to UINT_MAX,
which I think is 65535 on all platforms. I am not sure how that's
different from
Public bug reported:
I am having a problem where in my AssignUserID blocks mpm-itk
will fail with an internal server error. This shows up in the log:
(itkmpm: pid=29765 uid=33, gid=33) itk_post_perdir_config():
setgid(120208): Operation not permitted
I downloaded the source code and noticed I
I have tested the new binutils package on the test program at the top of
this ticket. I no longer see the Inconsistency detected... message,
but I do receive a segfault.
Here is what I did to upgrade:
# cat /etc/apt/sources.list.d/trusty-proposed.list
deb http://archive.ubuntu.com/ubuntu/
*** This bug is a duplicate of bug 1210525 ***
https://bugs.launchpad.net/bugs/1210525
** This bug has been marked a duplicate of bug 1210525
package gforth 0.7.0+ds2-0.1 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
--
You
I'm having the same problem in Ubuntu 14.04, and I've managed to blame
it on gccgo-4.9 (gccgo) somehow.
My symptoms were like this: clang++ can't find any stl headers, seems to
find C headers ok, but the linker can't find `-lstdc++`. It seemed to
affect all the clang-3.x packages.
I tracked it
Just a note that Bug #1176020 is also describing a side effect of this
same problem (same web server in question here).
We are disabling our remote loghost and seeing if that theory holds.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Just a note that Bug #1176020 is also describing a side effect of this
same problem (same web server in question here).
We are disabling our remote loghost and seeing if that theory holds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Landon's suggestion appears to be a fix for us too (thanks!). I did
alter the source package so I don't have to remember that should the
package have to be rebuilt one day. I set DEB_LDFLAGS_SET on the main
call to debhelper. I've included a patch to be precise.
That does not appear to be a good
Landon's suggestion appears to be a fix for us too (thanks!). I did
alter the source package so I don't have to remember that should the
package have to be rebuilt one day. I set DEB_LDFLAGS_SET on the main
call to debhelper. I've included a patch to be precise.
That does not appear to be a good
Ah, just missed that. Thanks for clearing that up. I've marked this
report invalid.
** Changed in: puppet (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
Ah, just missed that. Thanks for clearing that up. I've marked this
report invalid.
** Changed in: puppet (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390771
Public bug reported:
The scripts from vim-puppet are installed to `/usr/share/vim/addons`
which doesn't appear to be used by the current vim distributed with
Ubuntu 14.04. The net effect is that installing the vim-puppet package
seems to do nothing when you edit Puppet scripts.
Here is an
Public bug reported:
The scripts from vim-puppet are installed to `/usr/share/vim/addons`
which doesn't appear to be used by the current vim distributed with
Ubuntu 14.04. The net effect is that installing the vim-puppet package
seems to do nothing when you edit Puppet scripts.
Here is an
OK, here is the updated backtrace with nam-dbg and libtk8.6-dbg
installed:
#0 0x777504ba in Tk_PkgInitStubsCheck (interp=0x6a4340,
version=0x448b8b 8.1, exact=0)
at /build/buildd/tk8.6-8.6.1/unix/../generic/tkWindow.c:3400
#1 0x00417981 in main (argc=1,
This problem has continued over the past few months. We slogged through
the strace output a few times and just today found this:
[pid 935] sendto(11, 27Sep 22 13:06:30 automount[92..., 90, MSG_NOSIGNAL,
NULL, 0) = -1 ECONNREFUSED (Connection refused)
[pid 935] close(11) = 0
This problem has continued over the past few months. We slogged through
the strace output a few times and just today found this:
[pid 935] sendto(11, 27Sep 22 13:06:30 automount[92..., 90, MSG_NOSIGNAL,
NULL, 0) = -1 ECONNREFUSED (Connection refused)
[pid 935] close(11) = 0
This issue still persists for me. If this affects you then you should
mark it so at the top of the bug report's page.
In the mean time I have checked if the same problem is in Debian sid.
The segfault is not there (it does fail for another reason but it did
not seem related to this issue). This
Public bug reported:
Any time I try to run the nam executable I get a segmentation fault:
$ nam
Segmentation fault (core dumped)
$ nam nam.out
Segmentation fault (core dumped)
I tried to get a backtrace in gdb. Seems to be problem in the Tk
initialization routines:
Program received signal
Sorry for the delayed response. A few weeks after this problem started,
unattended-upgrades caught an update off of either precise-security or
precise-updates and we no longer had this problem. You can consider the
issue resolved, at least for us.
Thanks!
--
You received this bug notification
I had this same problem too. I wonder if this is actually a mixture of a
confusing init script message mixed with the quirks about how uwsgi
decided to respond to signals.
This tipped me off:
http://serverfault.com/questions/347819/ubuntu-11-10-with-nginx-and-
uwsgi
So uwsgi has two pidfile
Just to make sure all the information is together, I noticed earlier
there was a piece of a log message in that stack trace I posted. I tried
to see what I could do to piece together part of it:
%s: lookup(ldap): query failed for search dn %s: %s
became
Invalid DN syntax: lookup(ldap):
Just to make sure all the information is together, I noticed earlier
there was a piece of a log message in that stack trace I posted. I tried
to see what I could do to piece together part of it:
%s: lookup(ldap): query failed for search dn %s: %s
became
Invalid DN syntax: lookup(ldap):
This started happening almost daily so we are looking for a fix.
I'm starting to wonder if this is actually a duplicate of Bug #593603
In any case I'm working on figuring out what in our site's LDAP database
is causing the crash, if anything.
--
You received this bug notification because you
This started happening almost daily so we are looking for a fix.
I'm starting to wonder if this is actually a duplicate of Bug #593603
In any case I'm working on figuring out what in our site's LDAP database
is causing the crash, if anything.
--
You received this bug notification because you
Public bug reported:
Over the past few months we noticed our web server would no longer serve
requests out of directories normally mounted by autofs, which is
configured to be backed by LDAP. We knew a reboot would fix the problem
temporarily but it would recur after several weeks. We just
Public bug reported:
Over the past few months we noticed our web server would no longer serve
requests out of directories normally mounted by autofs, which is
configured to be backed by LDAP. We knew a reboot would fix the problem
temporarily but it would recur after several weeks. We just
I tried the -generic versions of the kernels mentioned here:
- 3.2.56: bug exists
- 3.2.57: bug exists
- 3.2.58: normal boot
- 3.2.59: normal boot
So the later versions appeared OK (aside from not having proper graphics
drivers but I expected that). I went ahead and tested all of them since
56
Public bug reported:
Several of our Dell Precision T3600 (and possibly all) machines cannot
seem to find their OS partition after they automatically installed
3.2.0-63-generic this morning. We physically removed the drives and made
sure they were in good shape and the BIOS seems to recognize the
apport information
** Attachment added: PciMultimedia.txt
https://bugs.launchpad.net/bugs/1323836/+attachment/4120948/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card0.Amixer.info.txt
https://bugs.launchpad.net/bugs/1323836/+attachment/4120940/+files/Card0.Amixer.info.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags added: apport-collected
** Description changed:
Several of our Dell Precision T3600 (and possibly all) machines cannot
seem to find their OS partition after they automatically installed
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1323836/+attachment/4120946/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1323836
Title:
[Dell
apport information
** Attachment added: Card1.Amixer.values.txt
https://bugs.launchpad.net/bugs/1323836/+attachment/4120944/+files/Card1.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.launchpad.net/bugs/1323836/+attachment/4120942/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card1.Codecs.codec.0.txt
https://bugs.launchpad.net/bugs/1323836/+attachment/4120945/+files/Card1.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.launchpad.net/bugs/1323836/+attachment/4120941/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1323836/+attachment/4120947/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1323836
Title:
[Dell
apport information
** Attachment added: Card1.Amixer.info.txt
https://bugs.launchpad.net/bugs/1323836/+attachment/4120943/+files/Card1.Amixer.info.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/1323836/+attachment/4120939/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1323836
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1323836/+attachment/4120950/+files/ProcCpuinfo.txt
** Bug watch added: Debian Bug tracker #746642
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746642
--
You received this bug notification because
I'm not entirely sure that script is working correctly. I don't have
physical access to this machine right now, but if there are any logs I
can provide note them in the comments. I'm attaching the fstab just in
case it is useful.
I also wanted to note the similarity in this recent bug in Debian:
Public bug reported:
The /etc/init.d/samba script appears to try and start smbd/nmbd
improperly. If a user types service samba restart here is the
behavior:
root@cups:~# service samba restart
root@cups:~# echo $?
1
I tried to track down the problem a bit by putting set -x on the init
script:
Public bug reported:
The /etc/init.d/samba script appears to try and start smbd/nmbd
improperly. If a user types service samba restart here is the
behavior:
root@cups:~# service samba restart
root@cups:~# echo $?
1
I tried to track down the problem a bit by putting set -x on the init
script:
I ran into a very similar behavior as well. There is an ongoing
discussion at ubuntuforums where I posted some info but I think it is
better suited here. Here is the thread:
http://ubuntuforums.org/showthread.php?t=2159402
So this is on Ubuntu 13.10 with znes package version 1.510+bz2-5ubuntu3.
47 matches
Mail list logo
