Stuck "Scuttling..." on 3.11.5 and 3.11.6

[funwhilelost]

Since migrating to 3.11.5 my Patchwork seems to just sit there "Scuttling...". I then installed 3.11.6 with the same results.

I cloned the repo and built it from source to find this in console:
git-ssb is not installed, or not available in path

afaik it should spawn a git-ssb server on its own, correct? I had an older version installed a couple days ago and it worked fine.

I went ahead and did a manual npm install git-ssb and restarted the server to get this exception and stack trace:

Error: Cannot find module 'ssb-about'
    at Module._resolveFilename (module.js:543:15)
    at Function.Module._resolveFilename (D:\git\patchwork\node_modules\electron\dist\resources\electron.asar\common\reset-search-paths.js:35:12)
    at Function.Module._load (module.js:473:25)
    at Module.require (module.js:586:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (D:\git\patchwork\server-process.js:31:8)
    at Object.<anonymous> (D:\git\patchwork\server-process.js:74:3)
    at Module._compile (module.js:642:30)
    at Object.Module._extensions..js (module.js:653:10)
    at Module.load (module.js:561:32)

There is also a deprecation notice when installing git-ssb:

npm WARN deprecated git-ssb@2.3.6: Installing git-ssb from centralized npm registry is deprecated; use ssb-npm
npm WARN deprecated git-remote-ssb@2.0.4: Installing git-remote-ssb from centralized npm registry is deprecated; use ssb-npm instead
npm WARN deprecated ssb-git-repo@2.8.3: Installing ssb-git-repo from centralized npm registry is deprecated; use ssb-npm instead
npm WARN @staltz/sbot-gossip@1.2.3 requires a peer of scuttlebot@>=11 but none is installed. You must install peer dependencies yourself.
npm WARN acorn-dynamic-import@4.0.0 requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.

I'm not familiar with the ssb-npm toolchain, but maybe this is the root of the issue with booting it on Windows.

[christianbundy]

Hey, sorry that Patchwork is giving you a hard time. Just to be clear, is this the problem?

Since migrating to 3.11.5 my Patchwork seems to just sit there "Scuttling...".

You shouldn't need git-ssb to run Patchwork, and the "git-ssb is not installed" is informational rather than an error (although I agree, it does look like an error).

[funwhilelost]

Oh, interesting. Maybe a red herring. I went back to 3.11.4 and things are working.

[christianbundy]

It's important to get your installation up-to-date with 3.11.6, I'm happy to help you debug.

How long have you left it alone while it says "Scuttling"? Does it post any config output? I'm hoping for a bit more info to help figure out what's going on.

[lpar]

Same problem with Linux.

[christianbundy]

Could either/both of you post the output of ssb-server status? If you don't have it installed I think you should be able to run it with npx ssb-server status, assuming you have NPM installed.

[funwhilelost]

How long have you left it alone while it says "Scuttling"? Does it post any config output? I'm hoping for a bit more info to help figure out what's going on.

I left it for about 12 hours, seeing if there was some DB rebuild or something. When that didn't work I wiped the .ssb directory and just restored my gossip.json, manifest.json, secret, and ssb-secret.7z. I let that run for about 12 hours with no results. Just "Scuttling..." Where is the "config output" stored? I poked around in .ssb looking for something human-readable but didn't come up with anything.

Here's what I get on an npm start:

{ path: 'C:\\Users\\Andy\\.ssb',
  party: true,
  timeout: 0,
  pub: true,
  local: true,
  friends: { dunbar: 150, hops: 2 },
  gossip: { connections: 3, autoPopulate: false },
  connections:
   { outgoing: { net: [Array] },
     incoming: { net: [Array], ws: [Array] } },
  timers: { connection: 0, reconnect: 5000, ping: 300000, handshake: 5000 },
  caps:
   { shs: '...',
     sign: null },
  master: [],
  logging: { level: 'notice' },
  port: 8008,
  blobsPort: 8989,
  server: true,
  _: [],
  host: '::',
  ws:
   { host: '::',
     port: 8989,
     scope: [ 'device', 'local', 'public' ],
     transform: 'shs' },
  keys:
   { curve: 'ed25519',
     public: '...',
     private: null,
     id: '...' },
  remote: 'net:127.0.0.1:undefined~...' }
Error: Cannot find module 'ssb-about'
    at Module._resolveFilename (module.js:543:15)
    at Function.Module._resolveFilename (D:\git\patchwork\node_modules\electron\dist\resources\electron.asar\common\reset-search-paths.js:35:12)
    at Function.Module._load (module.js:473:25)
    at Module.require (module.js:586:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (D:\git\patchwork\server-process.js:31:8)
    at Object.<anonymous> (D:\git\patchwork\server-process.js:74:3)
    at Module._compile (module.js:642:30)
    at Object.Module._extensions..js (module.js:653:10)
    at Module.load (module.js:561:32)

From npx ssb-server status:

D:\git\patchwork\node_modules\ssb-server\bin.js
Error: Could not connect to ssb-server :::8008
Use the "start" command to start it.

So I ran npx ssb-server start to get it running:

D:\git\patchwork\node_modules\ssb-server\bin.js
ssb-server 13.6.3 C:\Users\Andy\.ssb logging.level:notice
my key ID: etENdjc9Qg0hS56E5XkLhf58DYsqK18kit8Sp0qTT/8=.ed25519
The specified module could not be found.
\\?\D:\git\patchwork\node_modules\ssb-db\node_modules\leveldown\build\Release\leveldown.node

[lpar]

I think mine is getting stuck because of #972. I'm running the AppImage and there's no ssb-server binary in the mounted temporary directory as far as I can tell.

[christianbundy]

Maybe a silly question, but have you tried restarting the app a few times? I've had it get stuck scuttling, but after a few minutes I'll restart and it'll work just fine.

@funwhilelost

This looks like your error:

Error: Cannot find module 'ssb-about'
    at Module._resolveFilename (module.js:543:15)
    at Function.Module._resolveFilename (D:\git\patchwork\node_modules\electron\dist\resources\electron.asar\common\reset-search-paths.js:35:12)
    at Function.Module._load (module.js:473:25)
    at Module.require (module.js:586:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (D:\git\patchwork\server-process.js:31:8)
    at Object.<anonymous> (D:\git\patchwork\server-process.js:74:3)
    at Module._compile (module.js:642:30)
    at Object.Module._extensions..js (module.js:653:10)
    at Module.load (module.js:561:32)

Can you verify that ~/.ssb/config is empty? I'm curious whether maybe you modified something when you set up git-ssb. This is also concerning:

  remote: 'net:127.0.0.1:undefined~...' }

This looks like it doesn't know which port to connect on, so it's trying to connect on undefined? That looks broken to me, I'm curious whether you have the same output @lpar.

[mmckegg]

Patchwork 3.11.6 doesn’t use ebt, so the fact that there is ebt in the status output means that another sbot is running (not patchwork’s one).

Have you tried restarting your machine?

[DavidBurela]

I've got the same issues since upgrading. It just stays stuck on "scuttling" with no listed pubs.
I tried emptying out the .ssb folder, but it is still stuck scuttling. I have uninstalled and reinstalled.

If I try to add a pub I get the error "could not connect to sbot"

[bloodyKnuckles]

For several days after upgrading to 3.11.16 I was having the same problem. I just now tried launching patchwork again and I'm getting posts—Welcome back! :)

[modgethanc]

I'm getting the same problem with both updates; I'm running from the Appimage and it sits on 'scuttling...' with no further output. I've probably left it running for like ten hours total at this point, including after a reboot. I don't have a .ssb/config file, either.

[christianbundy]

I restarted, pulled git master and npm install/started the latest with the same result.

Could you confirm whether this talking about git-ssb or Patchwork? I'm interested to know whether this is only a problem with Patchwork 3.11.5 and 3.11.6 or whether it's also causing problems on master.

[doublec]

I get the same issue on Linux, stuck at "Scuttling" using the AppImage. Terminal shows the following error constantly scrolling:

Error: transport:unix did not remember scope, expected:local got:public
    at /tmp/.mount_PatchwYhfNex/app/resources/app.asar/node_modules/secret-stack/core.js:138:27
    at Array.forEach (<anonymous>)
    at /tmp/.mount_PatchwYhfNex/app/resources/app.asar/node_modules/secret-stack/core.js:134:26
    at Array.forEach (<anonymous>)
    at /tmp/.mount_PatchwYhfNex/app/resources/app.asar/node_modules/secret-stack/core.js:133:24
    at Array.forEach (<anonymous>)
    at setupMultiserver (/tmp/.mount_PatchwYhfNex/app/resources/app.asar/node_modules/secret-stack/core.js:132:55)
    at EventEmitter.getAddress (/tmp/.mount_PatchwYhfNex/app/resources/app.asar/node_modules/secret-stack/core.js:205:11)
    at EventEmitter.hooked [as getAddress] (/tmp/.mount_PatchwYhfNex/app/resources/app.asar/node_modules/hoox/index.js:10:15)
    at /tmp/.mount_PatchwYhfNex/app/resources/app.asar/node_modules/scuttlebot/plugins/local.js:83:30
Error: transport:unix did not remember scope, expected:local got:public
    at /tmp/.mount_PatchwYhfNex/app/resources/app.asar/node_modules/secret-stack/core.js:138:27
    at Array.forEach (<anonymous>)
    at /tmp/.mount_PatchwYhfNex/app/resources/app.asar/node_modules/secret-stack/core.js:134:26
    at Array.forEach (<anonymous>)
    at /tmp/.mount_PatchwYhfNex/app/resources/app.asar/node_modules/secret-stack/core.js:133:24
    at Array.forEach (<anonymous>)
    at setupMultiserver (/tmp/.mount_PatchwYhfNex/app/resources/app.asar/node_modules/secret-stack/core.js:132:55)
    at EventEmitter.getAddress (/tmp/.mount_PatchwYhfNex/app/resources/app.asar/node_modules/secret-stack/core.js:205:11)
    at EventEmitter.hooked [as getAddress] (/tmp/.mount_PatchwYhfNex/app/resources/app.asar/node_modules/hoox/index.js:10:15)
    at /tmp/.mount_PatchwYhfNex/app/resources/app.asar/node_modules/scuttlebot/plugins/local.js:83:30