search for: unrecoverable

Displaying 20 results from an estimated 261 matches for "unrecoverable".

2008 Jul 13
1
Photoshop CS2 Crash under Wine, "Unable to continue because of a hardware or system error. Sorry, but this error is unrecoverable."
I recently came across a post (circa jan-feb 2008) where a user had encountered a fatal and unrecoverable crash when starting Photoshop for the second or subsequent time. I've noticed that this issue has happened to many people, myself included while installing it on someone's system today, and that, while there is a short-term workaround (noted below), nobody has yet posted an actual permane...
2013 Feb 24
2
[LLVMdev] Phabricator homepage "UNRECOVERABLE FATAL ERROR"
When accessing the Phabricator homepage <http://llvm-reviews.chandlerc.com/> I see: <http://llvm-reviews.chandlerc.com/P53>. The rest of the site seems to be fine (e.g. I can access that paste fine, and all Differential links that I see on the list work fine), but the homepage just dies. Is this a known issue? -- Sean Silva
2013 Feb 24
0
[LLVMdev] Phabricator homepage "UNRECOVERABLE FATAL ERROR"
On Sat, Feb 23, 2013 at 8:27 PM, Sean Silva <silvas at purdue.edu> wrote: > When accessing the Phabricator homepage > <http://llvm-reviews.chandlerc.com/> I see: > > <http://llvm-reviews.chandlerc.com/P53>. > > The rest of the site seems to be fine (e.g. I can access that paste > fine, and all Differential links that I see on the list work fine), > but
2013 Feb 25
2
[LLVMdev] Phabricator homepage "UNRECOVERABLE FATAL ERROR"
The problem should be fixed (according to upstream it's a bad apc version that is part of archlinux). Let me know if the error persists... Thanks! /Manuel On Mon, Feb 25, 2013 at 9:16 AM, Manuel Klimek <klimek at google.com> wrote: > I filed an upstream bug: > https://secure.phabricator.com/T2594 > > > On Sun, Feb 24, 2013 at 10:43 AM, Anton Korobeynikov < >
2013 Feb 25
0
[LLVMdev] Phabricator homepage "UNRECOVERABLE FATAL ERROR"
On Mon, Feb 25, 2013 at 9:33 AM, Manuel Klimek <klimek at google.com> wrote: > > Let me know if the error persists... > Still broken on my end. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130225/46d34b42/attachment.html>
2013 Feb 25
1
[LLVMdev] Phabricator homepage "UNRECOVERABLE FATAL ERROR"
Can you give it another spin? Thx On Mon, Feb 25, 2013 at 11:17 AM, Sean Silva <silvas at purdue.edu> wrote: > > > > On Mon, Feb 25, 2013 at 9:33 AM, Manuel Klimek <klimek at google.com> wrote: > >> >> Let me know if the error persists... >> > > Still broken on my end. > -------------- next part -------------- An HTML attachment was
2013 Feb 25
0
[LLVMdev] Phabricator homepage "UNRECOVERABLE FATAL ERROR"
I filed an upstream bug: https://secure.phabricator.com/T2594 On Sun, Feb 24, 2013 at 10:43 AM, Anton Korobeynikov < anton at korobeynikov.info> wrote: > Yes. I'm seeing the problem. > > The error text is: > > Cannot override final method LiskDAO::loadOneRelative() > > > /srv/http/phabricator/src/applications/repository/storage/PhabricatorRepository.php:7 >
2007 Mar 27
0
Samba hangs badly making the OS hang unrecoverably too
Hi everybody, i'm getting mad regarding a very serious (since it's happening on a production server) issue with a samba domain joined installation. This machine has worked perfectly for an year and the last configuration tune up and version upgrade (3.0.23c) went along fine in the first days of January. It's been two weeks approximately now since we started to have a bad issue, a
2013 Feb 24
2
[LLVMdev] Phabricator homepage "UNRECOVERABLE FATAL ERROR"
Yes. I'm seeing the problem. The error text is: Cannot override final method LiskDAO::loadOneRelative() /srv/http/phabricator/src/applications/repository/storage/PhabricatorRepository.php:7 On Sun, Feb 24, 2013 at 10:19 PM, Manuel Klimek <klimek at google.com> wrote: > On Sat, Feb 23, 2013 at 8:27 PM, Sean Silva <silvas at purdue.edu> wrote: >> >> When accessing
2017 Nov 09
2
Error logged in fuse-mount log file
...rfs 3.10.1 and i am seeing below msg in fuse-mount log file. what does this error mean? should i worry about this and how do i resolve this? [2017-11-07 11:59:17.218973] W [MSGID: 109005] [dht-selfheal.c:2113:dht_selfheal_directory] 0-glustervol-dht: Directory selfheal fail ed : 1 subvolumes have unrecoverable errors. path = /fol1/fol2/fol3/fol4/fol5, gfid =3f856ab3-f538-43ee-b408-53dd3da617fb [2017-11-07 11:59:17.218935] I [MSGID: 109063] [dht-layout.c:713:dht_layout_normalize] 0-glustervol-dht: Found anomalies in /fol1/fol2/fol3/fol4/fol5 (gfid = 3f856ab3-f538-43ee-b408-53dd3da617fb). Holes=1 overlaps=...
2009 Jul 13
7
OpenSolaris 2008.11 - resilver still restarting
Just look at this. I thought all the restarting resilver bugs were fixed, but it looks like something odd is still happening at the start: Status immediately after starting resilver: # zpool status pool: rc-pool state: DEGRADED status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using ''zpool clear'' or replace the device with ''zpool replace''. see: http://www.sun.com/m...
2007 Mar 16
8
ZFS checksum error detection
Hi all. A quick question about the checksum error detection routines in ZFS. Surely ZFS can decide about checksum errors in a redundant environment but what about an non-redundant one? We connected a single RAID5 array to a v440 as a NFS server and while doing backups and the like we see the "zpool status -v" checksum error counters increment once in a while. Nevertheless the
2017 Nov 13
2
Error logged in fuse-mount log file
...>> what does this error mean? should i worry about this and how do i resolve >> this? >> >> [2017-11-07 11:59:17.218973] W [MSGID: 109005] >> [dht-selfheal.c:2113:dht_selfheal_directory] 0-glustervol-dht: Directory >> selfheal fail >> ed : 1 subvolumes have unrecoverable errors. path = >> /fol1/fol2/fol3/fol4/fol5, gfid =3f856ab3-f538-43ee-b408-53dd3da617fb >> [2017-11-07 11:59:17.218935] I [MSGID: 109063] >> [dht-layout.c:713:dht_layout_normalize] 0-glustervol-dht: Found >> anomalies in /fol1/fol2/fol3/fol4/fol5 (gfid = >> 3f856ab3-f5...
2007 Nov 09
3
Major problem with a new ZFS setup
...x0, FRU: 0x0 Nov 8 04:13:59 mondo4 scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0 Finally trying to do a zpool status yields: root at mondo4:/# zpool status -v pool: LogData state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using ''zpool clear'' or replace the device with ''zpool replace''. see: http://www.sun.com/m...
2007 Jun 05
4
CentOS 5 Issues Booting Under VMWare
...s *extremely* slow to boot (as in it takes over an hour to boot CentOS 5 on a machine that boots CentOS 3 & 4 in less than one minute). Then, after an hour of slowly watching the messages go by on the console and the CPU of the host machine pegged at 100%, I get this error: VMware Workstation unrecoverable error: (vcpu-0) NOT_REACHED F(562):1742 A log file is available in ... I have done a "minimal install" of CentOS 5 (all checkboxes in the category/task selection screen are unchecked -- so to X-Windows involved) and the virtual machine has 750MB of RAM. I'm using VMWare Workstation...
2017 Nov 10
0
Error logged in fuse-mount log file
...e-mount log > file. > > what does this error mean? should i worry about this and how do i resolve > this? > > [2017-11-07 11:59:17.218973] W [MSGID: 109005] > [dht-selfheal.c:2113:dht_selfheal_directory] 0-glustervol-dht: Directory > selfheal fail > ed : 1 subvolumes have unrecoverable errors. path = > /fol1/fol2/fol3/fol4/fol5, gfid =3f856ab3-f538-43ee-b408-53dd3da617fb > [2017-11-07 11:59:17.218935] I [MSGID: 109063] > [dht-layout.c:713:dht_layout_normalize] 0-glustervol-dht: Found anomalies > in /fol1/fol2/fol3/fol4/fol5 (gfid = 3f856ab3-f538-43ee-b408-53dd3da617fb...
2006 Oct 03
2
pdf/ convert/ font problem
...as there are several subroutines for the analysis that are not relevant here anyway). ------------------------------------------------ The pdf loads into acroread or xpdf fine, so is not corrupted, but ghostscript gives an error: ERROR: /invalidfont in --.type1execchar--ESP Ghostscript 815.02: Unrecoverable error, exit code 1 Operand stack: --dict:4/4(L)-- --dict:16/17(ro)(G)-- 108 a71 -string- Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_...
2017 Nov 14
2
Error logged in fuse-mount log file
...3.10.1 and i am seeing below msg in fuse-mount log file. what does this error mean? should i worry about this and how do i resolve this? [2017-11-07 11:59:17.218973] W [MSGID: 109005] [dht-selfheal.c:2113:dht_selfheal_directory] 0-glustervol-dht: Directory selfheal fail ed : 1 subvolumes have unrecoverable errors. path = /fol1/fol2/fol3/fol4/fol5, gfid =3f856ab3-f538-43ee-b408-53dd3da617fb [2017-11-07 11:59:17.218935] I [MSGID: 109063] [dht-layout.c:713:dht_layout_normalize] 0-glustervol-dht: Found anomalies in /fol1/fol2/fol3/fol4/fol5 (gfid = 3f856ab3-f538-43ee-b408-53dd3da617fb). Holes=1 overlaps...
2002 Jul 01
1
deamon error message
...Jul 1 14:48:51 localhost tinc.percipia[1275]: tincd 1.0pre7 starting Jul 1 14:48:51 localhost modprobe: modprobe: Can't locate module char-major-36 Jul 1 14:48:51 localhost tinc.percipia[1275]: Could not open /dev/misc/net/tun: No such device Jul 1 14:48:51 localhost tinc.percipia[1275]: Unrecoverable error Jul 1 14:48:51 localhost tinc.percipia[1275]: Restarting in 900 seconds! Jul 1 14:50:06 localhost kernel: Universal TUN/TAP device driver 1.4 (C)1999-2001 M axim Krasnyansky Jul 1 14:51:18 localhost tinc.percipia[1292]: tincd 1.0pre7 (Apr 25 2002 18:34:45) starting, debug level 1 Jul 1 14...
2005 Aug 26
4
system crash
We just had * crash on us - no calls could be made / received. We had to kill -9 the * process. Checking the error logs, I came across these two lines, with the times matching the crash: Aug 26 13:48:00 WARNING[19282] pbx.c: Local/6024@AgentQ-94ce,2 already has PBX structure?? Aug 26 13:48:00 WARNING[19282] channel.c: Thread -1105359952 Blocking 'Local/6024@AgentQ-94ce,2', already