#9583: Unhandled SIGSEGV with 4.5.2.alpha0 on t2
-----------------------+----------------------------------------------------
Reporter: mpatel | Owner: drkirkby
Type: defect | Status: new
Priority: blocker | Milestone: sage-4.5.2
Component: solaris | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------+----------------------------------------------------
Comment(by drkirkby):
I just checked if anything odd had happened on 't2'. There are no obvious
errors in the log file - just the usual ones related to the fact
'disk.math' has been mis-configured.
{{{
Jul 22 05:56:37 t2 nfs: [ID 236337 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]NFS op OP_GETATTR got error NFS4ERR_STALE causing
recovery action NR_STALE.
Jul 22 05:56:37 t2 nfs: [ID 236337 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]NFS op OP_LOOKUP got error NFS4ERR_STALE causing
recovery action NR_STALE.
Jul 22 05:56:37 t2 nfs: [ID 236337 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]NFS op OP_GETATTR got error NFS4ERR_STALE causing
recovery action NR_STALE.
Jul 22 05:56:37 t2 nfs: [ID 236337 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]NFS op OP_LOOKUP got error NFS4ERR_STALE causing
recovery action NR_STALE.
Jul 22 05:56:37 t2 nfs: [ID 236337 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]NFS op OP_GETATTR got error NFS4ERR_STALE causing
recovery action NR_STALE.
Jul 22 05:56:37 t2 nfs: [ID 286389 kern.info] NOTICE: [NFS4][Server:
disk][Mntpt: /home]File ./sergey/core (rnode_pt: 30107802420) was closed
due to NFS recovery error on server disk(failed to recover from
NFS4ERR_STALE NFS4ERR_STALE)
Jul 22 05:56:37 t2 nfs: [ID 941083 kern.info] NOTICE: NFS4 FACT SHEET:
Jul 22 05:56:37 t2 Action: NR_STALE
Jul 22 05:56:37 t2 NFS4 error: NFS4ERR_STALE
Jul 22 06:26:59 t2 sshd[11907]: [ID 800047 auth.crit] fatal: Write failed:
Broken pipe
Jul 22 07:40:45 t2 sshd[18797]: [ID 800047 auth.crit] fatal: Write failed:
Broken pipe
Jul 22 09:16:24 t2 sshd[7318]: [ID 800047 auth.crit] fatal: Read from
socket failed: Connection reset by peer
Jul 22 11:11:05 t2 sshd[6504]: [ID 800047 auth.crit] fatal: Read from
socket failed: Connection reset by peer
}}}
No messages today, so its probably not a problem on 't2'.
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9583#comment:2>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
