Hi,
Am 23.04.2015 um 06:39 schrieb Dietmar Maurer:
(gdb) bt full
#0 clog_dump_json (clog=0x2cf94d0, str=0x1fd0700, ident=optimized
out, max_entries=50) at logger.c:167
node = optimized out
msg = optimized out
cur = 0x64350140
ident = optimized out
I can't tell you the value of count, as it is optimized out. So as far
as i understand the gdb documentation i can't restore it.
clog-size is:
(gdb) p clog-size
$1 = 131072
OK, so cpos is clearly out of range.
Please test with my workaround - that should
at least avoid the crash.
Am 23.04.2015 um 07:49 schrieb Dietmar Maurer:
I now tried to add a workaround:
https://git.proxmox.com/?p=pve-cluster.git;a=commitdiff;h=9483da1abd3d8d33cbc6786966628dfa3adefb99
and uploaded a new package to pvetest.
maybe you can test if that helps?
Thanks. Have it installed.
I now tried to add a workaround:
https://git.proxmox.com/?p=pve-cluster.git;a=commitdiff;h=9483da1abd3d8d33cbc6786966628dfa3adefb99
and uploaded a new package to pvetest.
maybe you can test if that helps?
___
pve-devel mailing list
Do you know how to print them?
Stefan
Excuse my typo sent from my mobile phone.
Am 23.04.2015 um 06:39 schrieb Dietmar Maurer diet...@proxmox.com:
(gdb) bt full
#0 clog_dump_json (clog=0x2cf94d0, str=0x1fd0700, ident=optimized
out, max_entries=50) at logger.c:167
node = optimized
Do you know how to print them?
not from memory, sorry.
Or can I download the core dump?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Am 07.02.2015 um 15:55 schrieb Dietmar Maurer:
THis won't help as my build and your build will differ. SO the kernel
message a have from the crash will not be applyable with gdb to my debug
symbols.
Sure, you also need to reproduce the bug :-( I guess we should really provide
a
debug
Hi Dietmar,
i can build a debug package on my own to debug this issue.
I just don't know how to pass -DDEBUG to gcc with your makefile /
configure script. Can you tell me?
Stefan
Am 09.02.2015 um 11:30 schrieb Stefan Priebe - Profihost AG:
Am 09.02.2015 um 08:50 schrieb Stefan Priebe -
...@proxmox.com, pve-devel pve-devel@pve.proxmox.com
Envoyé: Lundi 9 Février 2015 12:20:14
Objet: Re: [pve-devel] crashes of pmxcfs
Hi Dietmar,
i can build a debug package on my own to debug this issue.
I just don't know how to pass -DDEBUG to gcc with your makefile /
configure script. Can you
diet...@proxmox.com, pve-devel pve-devel@pve.proxmox.com
Envoyé: Lundi 9 Février 2015 12:20:14
Objet: Re: [pve-devel] crashes of pmxcfs
Hi Dietmar,
i can build a debug package on my own to debug this issue.
I just don't know how to pass -DDEBUG to gcc with your makefile /
configure script. Can
Am 07.02.2015 um 15:55 schrieb Dietmar Maurer:
THis won't help as my build and your build will differ. SO the kernel
message a have from the crash will not be applyable with gdb to my debug
symbols.
Sure, you also need to reproduce the bug :-( I guess we should really provide
a
debug
Am 07.02.2015 um 08:57 schrieb Dietmar Maurer:
Never saw that. Can you reproduce it?
No have seen it only once. DO you have debugging packages? I could then
reconstruct the line where it was crashing using gdb, the kernel line
and the debugging symbol.
No, sorry - you need to compile
THis won't help as my build and your build will differ. SO the kernel
message a have from the crash will not be applyable with gdb to my debug
symbols.
Sure, you also need to reproduce the bug :-( I guess we should really provide a
debug
package for such problems.
Never saw that. Can you reproduce it?
No have seen it only once. DO you have debugging packages? I could then
reconstruct the line where it was crashing using gdb, the kernel line
and the debugging symbol.
No, sorry - you need to compile yourself. I will try to debug that next week.
Am 05.02.2015 um 16:56 schrieb Dietmar Maurer:
Is this crash known? Should we probably use a wrapper which restarts
pmxcfs on a crash?
Never saw that. Can you reproduce it?
No have seen it only once. DO you have debugging packages? I could then
reconstruct the line where it was crashing
Is this crash known? Should we probably use a wrapper which restarts
pmxcfs on a crash?
Never saw that. Can you reproduce it?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Hi,
today i got this crash on all nodes of a cluster:
pmxcfs[4272]: segfault at 213c379f ip 0041a730 sp
7f22b4c943b8 error 4 in pmxcfs[40+25000]
Biggest problem i could no longer log in via SSH as /etc/pve was not
reachable anymore.
Is this crash known? Should we probably
On Thu, 5 Feb 2015 16:56:27 +0100 (CET)
Dietmar Maurer diet...@proxmox.com wrote:
Is this crash known? Should we probably use a wrapper which restarts
pmxcfs on a crash?
Never saw that. Can you reproduce it?
Maybe we are hitting this bug (segfault error 4 at libc-2.17.so)?
18 matches
Mail list logo
