segmentation fault in iscsid at startup

Bug #1656838 reported by Christoph Fiehe
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
open-iscsi (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I am running Ubuntu 16.04 as VM in an OpenStack Newton environment using Ceph Jewel as storage backend and I get segfaults caused by iscsid at VM startup occasionally. I am using the Ubuntu Cloud Image which can be found here: https://cloud-images.ubuntu.com/xenial/current/

Please find attached the correspondig crash file. Unfortunately, I haven't found a way to reproduce the problem so far.

I will keep the crashed VM, so if you need more input, I will try to provide them.

Revision history for this message
Christoph Fiehe (fiehe) wrote :
summary: - segmentation fault in iscsid at boot
+ segmentation fault in iscsid at startup
Revision history for this message
Christoph Fiehe (fiehe) wrote :

$ apt-cache policy open-iscsi
open-iscsi:
  Installed: 2.0.873+git0.3b4b4500-14ubuntu3.1
  Candidate: 2.0.873+git0.3b4b4500-14ubuntu3.3
  Version table:
     2.0.873+git0.3b4b4500-14ubuntu3.3 500
        500 http://nova.clouds.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 *** 2.0.873+git0.3b4b4500-14ubuntu3.1 100
        100 /var/lib/dpkg/status
     2.0.873+git0.3b4b4500-14ubuntu3 500
        500 http://nova.clouds.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

Revision history for this message
Nish Aravamudan (nacc) wrote :

@Jens:

That is surprising! Is it possible to get a backtrace from the .crash?

-Nish

Changed in open-iscsi (Ubuntu):
status: New → Triaged
Revision history for this message
Brian Murray (brian-murray) wrote :

I tried retracing it and didn't get anything useful out of it.

Stacktrace:
 #0 0x0000000000000000 in ?? ()
 No symbol table info available.
 #1 0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (LWP 1297):
 #0 0x0000000000000000 in ?? ()
 No symbol table info available.
 #1 0x0000000000000000 in ?? ()
 No symbol table info available.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Clear old bug s that had no updates, there was no further insight into the crashes reported here.
Neither how to reproduce nor by the check of the existing crash data.

Also there was no similar report coming up in last 6 months triage, so it seems an uncommon/special issue.

For now I'll set this to incomplete as it isn't actionable without further data.

Changed in open-iscsi (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for open-iscsi (Ubuntu) because there has been no activity for 60 days.]

Changed in open-iscsi (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.