Since moving to 5.4.0-65.73 I've twice experienced a crash in
raw_spin_lock(). Is this related or a different issue? This happened
at 5:11pm yesterday.
[274680.293259] BUG: unable to handle page fault for address: c0561000
[274680.293276] #PF: supervisor write access in kernel mode
[2746
Done. We'll see if this occurs again.
FYI my system got a lot more stable once I moves /tmp off my M.2 drive
around the end of Dec. The drive was showing clean and not logging any
SMART errors, and I hadn't seen another dentry_unlink_inode fault until
last week (though that one was due to some m
Another triggered at 12:04am last night. Here's what's running:
find / -ls 2>/dev/null | gzip -c > /backupvol/rootfs/MANIFEST.gz
Top confirms:
top - 00:04:17 up 1 day, 13:05, 1 user, load average: 3.26, 2.38, 1.71
Tasks: 290 total, 3 running, 287 sleeping, 0 stopped, 0 zombi
Public bug reported:
Happened twice last night, precisely one hour apart
root@nas:/var/log# grep "Dec 23 0[23]:13:" /var/log/syslog*
/var/log/syslog:Dec 23 02:13:01 nas CRON[156065]: (root) CMD (date >>
/var/log/sensors.log; /usr/bin/sensors -f >> /var/log/sensors.log)
/var/log/syslog:Dec 23 02:
** Attachment added: "d-push.log.txt"
https://bugs.launchpad.net/ubuntu/+source/d-push/+bug/1611350/+attachment/4717490/+files/d-push.log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611350
** Attachment added: "config.php.txt"
https://bugs.launchpad.net/ubuntu/+source/d-push/+bug/1611350/+attachment/4717492/+files/config.php.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611350
** Attachment added: "d-push-error.log.txt"
https://bugs.launchpad.net/ubuntu/+source/d-push/+bug/1611350/+attachment/4717491/+files/d-push-error.log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
Upgraded to 16.04.1 LTS. d-push was removed during the upgrade. I did
an 'apt-get install d-push' to reinstall, though it was generating a lot
of "array to string conversion" errors and my iPhone wasn't seeing any
new mail. I then attempted to purge and reinstall with a cle
Public bug reported:
Running default utopic install. ntopng starts as /etc/rc2.d/S02ntopng.
however ntopng requires redis-server, which starts as /etc/rc2.d
/S02redis-server. This means redis-server is not running when ntopng
tries to start, and thus is fails every time.
Simplest solution would
On Sun, 10 Oct 2010 09:55:25 -, Dave Walker
wrote:
> @Geoff, Are you still seeing this behavior?
I have not seen this since upgrading to 10.04.
--
apache running at 100% indefinitely
https://bugs.launchpad.net/bugs/575175
You received this bug notification because you are a member of Ubunt
On Wed, 05 May 2010 17:18:47 -, Chuck Short
wrote:
> Can you attach the output of dpkg -l | grep apache and dpkg -l | grep
> php. Also if possible can you test this on lucid?
>
> Thanks
> chuck
I only have one server, so I can't test on lucid until I can upgrade it,
but here's the dpkg info
Is there something specific you want?
1. the specific steps or actions you took that caused you to encounter
the problem,
This is a web server. It started apache on boot for me when I rebooted
the host a week ago. It ran for a week or so. I logged in after being
out of town for the weekend and
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/47795269/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/47795271/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/47795272/ProcStatus.txt
--
apache
Public bug reported:
Binary package hint: apache2
Description:Ubuntu 9.10
Release:9.10
Arch: amd64
This apache2 process has been running for days at 100% CPU. There were
actually ~6 or 7 of them - I killed all but one, to get my load down
from 12+ to something usable.
I have the same issue with a fresh 64-bit Karmic install. I have two
identical copies of my root volume (I did an 'rsync -a -x -I /
/newroot'), and a number of LVs. If I boot off /dev/sdb2, the LVs mount
fine and my host boots OK. If I boot off sdb1 or off /dev/md/d1 (which
is sdb1 - and the who
15 matches
Mail list logo
