After some testing with own debug output, I found the cause for the hang
and I added a support request for davfs2:
https://savannah.nongnu.org/support/?109009
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
I can confirm the same problems on Ubuntu Server 15.10 which comes with
davfs2 1.5.2.
A reboot is the only way to resolve that error. And sometimes even the reboot
is not correctly finished
and a reset of the machine is needed.
--
You received this bug notification because you are a member of U
When I use
apport-cli -u 1516269
it returns:
ERROR: You need to use apport-collect for updating an existing bug
** Attachment added: "linux.apport"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516269/+attachment/4519669/+files/linux.apport
--
You received this bug notification bec
The ReportingBugs documentation says I should send the apport file via
ubuntu-bug -c -u
But this gives me:
Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash
file]
ubuntu-bug: error: -u/--update-bug option cannot be used together with options
for a new report
Shall I
It is a headless server in a datacenter with remote access only. Is
there another way to use apport-collect?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516269
Title:
ata NCQ error with md, drbd
After checking with kernel 4.2.0-16-generic again, I got the error too.
I have another server (same hardware) still running with 4.2.0-16-generic (not
updated yet) and the error doesn't show up, so I thought the update of the
kernel brought the problem. The servers hardware was completely exchang
Cannot run apport-collect (error on headless server).
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516269
Title:
ata NCQ error
Public bug reported:
With Ubuntu wily kernel 4.2.0-18-generic a SyncTarget to a DRBD on LVM
on MD Raid1 produces errors:
Nov 14 17:46:20 kobol kernel: [ 198.351892] ata1.00: exception Emask 0x60 SAct
0x38 SErr 0x800 action 0x6 frozen
Nov 14 17:46:20 kobol kernel: [ 198.351922] ata1.00: irq_sta
Actually it is a very acceptable workaround. I switched to upstart and
it works fine. Boot and shutdown is even faster (which I don't really
need in a server environment). The upstart way seems to be more stable
and reliable than systemd. My two cents from a server administrator
point of view: Avoi
I have the same problem with Vivid. Will there be a fix / backport
available?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480440
Title:
libvirt does not wait for guests to shut down
To manage no
The reason why sometimes (on some installations) no error is reported,
is of course if the 'priority' given with -p is a current valid process
ID. Which means that this process is changed by ionice instead of
calling updatedb.
--
/etc/cron.daily/find has wrong ionice parameter
https://bugs.launch
Public bug reported:
In /etc/cron.daily/find is ionice used when starting updatedb. The is
... ionice -c ${IONICE_CLASS:-2} -p ${IONICE_PRIORITY:-7} updatedb ...
So the option -p is used to set the priority. But ionice uses -p to set a
specific process ID and to
set the priority the -n parameter
I forgot to tell that I talk about gutsy here.
--
/etc/cron.daily/find has wrong ionice parameter
https://bugs.launchpad.net/bugs/159472
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
13 matches
Mail list logo
