This was a one time event, and I don't know of a way to replicate it at
this time. Monitors of the box showed it was largely idle at the time
the bug exhibited itself. VMware reported repeated high/low CPU
consumption from the time of the bug until it was forced off and
restarted. The host WAS
Public bug reported:
Ubuntu 3.2.0-64.97-virtual 3.2.59
One of our Production systems crashed with the following kernel.log
messages (we use a custom syslog setup):
Jun 13 01:06:04 www-node01 kernel: [593611.895631] [ cut here
]
Jun 13 01:06:04 www-node01 kernel:
Public bug reported:
Flickr deprecated their HTTP api in favor of HTTPS only, thus flickrfs
is no longer are able to connect/mount or function properly.
Here's a link to flickr's policy change that went into effect on june 27th
Public bug reported:
Flickr deprecated their HTTP api in favor of HTTPS only, thus any of
the tools in libflickr-upload-perl no longer are able to connect or
function properly.
Here's a link to flickr's policy change that went into effect on june 27th
Public bug reported:
Flickr changed to an HTTPS only API on june 27th 2014 breaking
libflickr-api-perl
http://code.flickr.net/2014/04/30/flickr-api-going-ssl-only-on-june-
27th-2014/ documents the change in the API
The libflickr perl api still references http URL's and thus is unusable
in that
I have also verified this failure exists with open-vm-tools
2011.12.20-562307-0ubuntu1 against kernel 3.2.0-76.111 when my nodes
failed to come up completely on VMware (waiting for network which
depended on the vmxnet driver which wasn't there)
CC [M]
I have also verified this failure exists with open-vm-tools
2011.12.20-562307-0ubuntu1 against kernel 3.2.0-76.111 when my nodes
failed to come up completely on VMware (waiting for network which
depended on the vmxnet driver which wasn't there)
CC [M]
Installing open-vm-dkms/open-vm-tools (2011.12.20-562307-0ubuntu1.1) from
precise-proposed has solved the compile issue for the 3.2.0-76.111 kernel.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Installing open-vm-dkms/open-vm-tools (2011.12.20-562307-0ubuntu1.1) from
precise-proposed has solved the compile issue for the 3.2.0-76.111 kernel.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
This completely breaks SYSLOG logging of PHP-fpm setups. Not
daemoninzing the process results in php-fpm ignoring the error_log
option and screws things royally in a multi-server setup where
centralized logging is used with syslog...
Please revert this bad design.
--
You received this bug
This completely breaks SYSLOG logging of PHP-fpm setups. Not
daemoninzing the process results in php-fpm ignoring the error_log
option and screws things royally in a multi-server setup where
centralized logging is used with syslog...
Please revert this bad design.
--
You received this bug
Public bug reported:
In trusty, php5-fpm is started by upstart with the --nodaemonize options
which causes php5-fpm to ignore the error_log options in
/etc/php5/fpm/php-fpm.conf regarding syslog. Thus, central log aggregation of
clusters of servers for php5-fpm is now completely broken.
In
I'm affected by this bug across 10 production servers, is there a
fix/workaround for trusty, that doesn't involve a manual kernel roll?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358226
Title:
I developed a workaround based upon:
http://serverfault.com/questions/114052/logging-a-daemons-output-with-
upstart based upon the Last (Feb 12th) solution..
changed bits of /etc/init/php5-fpm.conf
script
exec bash EOT
exec 1 (logger -t syslog_tag_for_php) 21
exec /usr/sbin/php5-fpm
I developed a workaround based upon:
http://serverfault.com/questions/114052/logging-a-daemons-output-with-
upstart wit hthe Last (Feb 12th) solution..
changed bits of /etc/init/php5-fpm.conf
script
exec bash EOT
exec 1 (logger -t syslog_tag_for_php) 21
exec /usr/sbin/php5-fpm --nodaemonize
slight correction:
exec bash EOT
should be:
exec bash EOT
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423933
Title:
php-fpm fails to use syslog when started by upstart
To manage
I developed a workaround based upon:
http://serverfault.com/questions/114052/logging-a-daemons-output-with-
upstart based upon the Last (Feb 12th) solution..
changed bits of /etc/init/php5-fpm.conf
script
exec bash EOT
exec 1 (logger -t syslog_tag_for_php) 21
exec /usr/sbin/php5-fpm
Audit rules trigger this crash. (Strlen)
See http://imgur.com/sWXVpvX,yYMgmOS#0
Linked to bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444141
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Test scenario: Revert audit config to stock (as installed by vendor
pkgs), boot is clean, system stable, add my rules (which have worked
in all previous relases), restart audit daemon, system still working,
restart Apache, BANG! kernel panic!
BUG: unable to handler kernel NULL pointer
Can someone please re-open this bug and mark it as critical.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444141
Title:
linux: 3.13.0-51.84 -proposed tracker
To manage notifications about this
Public bug reported:
Applying 3.13.0-51.84 as per normal update process, reboot of node results in
hard crash. Unfortunately since it's on VMware ESXi it's no possible to catch
scrollback, however a screenshot of hte majority of the crash is linked below:
.http://i.imgur.com/y1531Bl.png
3.13.0-51.84 crashes on every node I've used it on on VMware ESXi 5.5
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450504
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444141
Title:
** Attachment added: auditd.conf used when system crashes on boot
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450504/+attachment/4388398/+files/auditd.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Disabling my audit config and rules seems to present the crash.
** Attachment added: audit rules used when the system crashes hard on boot
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450504/+attachment/4388397/+files/audit.rules
--
You received this bug notification because you
NOTE: Most of these systems that were crashing were Apache Webservers
using php5-fpm with unix domain socket communication between the two of
them, the other's were MySQL, they didn't crash as quickly but did
within minutes of bootup. All packages were ubuntu repo provided,
though the apache and
Disabling the audit rules that were in place eliminates the crash.
More details in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450504
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444141
3.13.0-52.86 DOES work and no longer exhibits the crash/oops when
booted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450442
Title:
Kernel Oops - unable to handle kernel NULL pointer dereference
3.13.0.52-85 still has the same panic related to the audit
subsystem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450442
Title:
Kernel Oops - unable to handle kernel NULL pointer dereference
*** This bug is a duplicate of bug 1450442 ***
https://bugs.launchpad.net/bugs/1450442
3.13.0.52.85 STILL exhibits the exact same problem and crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The problem was resolved in #86, not #85
--
David J. Andruczyk
Systems Administrator
University IT - Enterprise Applications
44 Celebration Drive, Suite 3-100
Rochester, NY 14627
E-mail: david.andruc...@rochester.edu
Office: 585-275-9106
-Original Message-
From: boun...@canonical.com
I am getting the same problem now when imaging machines with MAAS. none
of them are booting up properly. The machines being imaged are Bionic,
using mdmadm RAID1 OS mirrors
All result in:
error: symbol `grub_calloc' not found.
Entering rescue mode...
grub rescue>
This has us dead in the
Note for our maas installs (bionic image, in house built from a upstream ubuntu
cloudimg customized with our specific needs) the ephemeral being used to image
the machine is
Thu, 30 Jul. 2020 11:09:10HTTP Request -
/images/ubuntu/amd64/ga-20.04/focal/daily/boot-initrd
Thu, 30 Jul. 2020
This affects 20.04 as well where the root device is on mdadm
(/dev/md127)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274320
Title:
Error: diskfilter writes are not supported
To manage
This breaks the maas snap in a bad way for API heavy users which appears to
have the broken version of python-twisted embedded within it:
maas 2.9.2-9164-g.ac176b5c4 11851 2.9/stable canonical* -
See https://bugs.launchpad.net/maas/+bug/1918206
--
You received this bug
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677668
Title:
no GARPs during ephemeral boot
To manage notifications about this bug
This causes problems for me as well during maas re-imaging wiht maas
2.9.2. see https://discourse.maas.io/t/changing-ips-and-lack-of-
gratuitous-arp-and-the-pain-it-causes/4800
Ideally when pxebooting, pxelinux.0 should send a gratuitous arp and in
theory it should solve the issue. Perhaps I'm
36 matches
Mail list logo
