<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>13705</bug_id>
          
          <creation_ts>2019-12-13 18:14:45 +0000</creation_ts>
          <short_desc>master] bitbake and hashserve.sock left behind when ^C a build</short_desc>
          <delta_ts>2022-04-28 16:53:32 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>core</component>
          <version>3.1</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium+</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>4.1 M1</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Armin Kuster">akuster</reporter>
          <assigned_to name="Armin Kuster">akuster</assigned_to>
          <cc>akuster808</cc>
    
    <cc>JPEWhacker</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>randy.macleod</cc>
    
    <cc>richard.purdie</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Don&apos;t know</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>85826</commentid>
    <comment_count>0</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2019-12-13 18:14:45 +0000</bug_when>
    <thetext>I have these variables defined:

SOURCE_MIRROR_URL ?= &quot;http://downloads.yoctoproject.org/mirror/sources/&quot;
SSTATE_MIRRORS ?= &quot;file://.* http://sstate.yoctoproject.org/PATH&quot;


BB_SIGNATURE_HANDLER = &quot;OEEquivHash&quot;


The mirrors are down so there is a very long ETA. 

I control-c and bitbake.sock and hashserve.sock are left behind.

Next time bitbake is invoked, it times out and the cooker log indicates hashserve.sock exists.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>85827</commentid>
    <comment_count>1</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2019-12-13 18:15:15 +0000</bug_when>
    <thetext>or I get this traceback

NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#8)... (Traceback (most recent call last):
  File &quot;/home/akuster/oss/maint/poky/bitbake/lib/bb/main.py&quot;, line 455, in setup_bitbake
    server_connection = bb.server.process.connectProcessServer(sockname, featureset)
  File &quot;/home/akuster/oss/maint/poky/bitbake/lib/bb/server/process.py&quot;, line 490, in connectProcessServer
    sock.connect(os.path.basename(sockname))
BlockingIOError: [Errno 11] Resource temporarily unavailable
)
ERROR: Unable to connect to bitbake server, or start one (server startup failures would be in bitbake-cookerdaemon.log)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>85828</commentid>
    <comment_count>2</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2019-12-13 18:17:38 +0000</bug_when>
    <thetext>I think there are 3 problems here:

1) No good timeout for SSTATE_MIRROR
2) Traceback
3) Cleanup after cntl-c

I can open additional bugs for the other two.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>85843</commentid>
    <comment_count>3</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2019-12-17 00:00:02 +0000</bug_when>
    <thetext>I suspect the files &quot;left behind&quot; still belong to a currently running bitbake server which isn&apos;t responsive.

Was there bitbake processes left behind from the first Ctrl+C&apos;d build?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>85862</commentid>
    <comment_count>4</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2019-12-19 15:44:53 +0000</bug_when>
    <thetext>we will create a new bug for the SSATE_MIRROR time and leave this as is.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>85868</commentid>
    <comment_count>5</comment_count>
    <who name="Armin Kuster">akuster</who>
    <bug_when>2019-12-19 16:27:02 +0000</bug_when>
    <thetext>opened

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13716 for the SSTATE_MIRROR issue.

This then becomes the cntl-c issue</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>92995</commentid>
    <comment_count>6</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2022-04-11 22:24:05 +0000</bug_when>
    <thetext>Armin, We&apos;ve fixed a few Control-C issues, could you check if this is still reproducible or if you prefer, one of us could just move it to 3.6-M1.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>93156</commentid>
    <comment_count>7</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2022-04-21 15:14:26 +0000</bug_when>
    <thetext>Is this still a problem?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>93202</commentid>
    <comment_count>8</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2022-04-28 14:56:46 +0000</bug_when>
    <thetext>Ping.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>93216</commentid>
    <comment_count>9</comment_count>
    <who name="akuster">akuster808</who>
    <bug_when>2022-04-28 16:53:32 +0000</bug_when>
    <thetext>works for me.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>