keep getting "the daemon is not active" even after running hyp daemon start

restarted computer, reinstalled hypercore-cli but i still keep getting "the daemon is not active", any ideas to fix this?

Encountering the same issue on two machines. Debian Buster and Windows 10 both running Node.js 16.9.1. I am not encountering this on a third Debian Buster instance running Node 16.9.1, where the daemon starts and is seeding.

PS C:\Users\metanomial> hyp daemon start
Hyperspace daemon started
Mirroring daemon started
Daemon is running.
PS C:\Users\metanomial> hyp daemon status
Daemon not active

I'm seeing this as well on macOS 11.5.2, node 16.9.1. A workaround for me was to install hyperspace directly npm i hyperspace -g and run the daemon directly in the foreground using $ hyperspace

Actually, that fixed hyp daemon status but other commands, hyp info, hyp create drive, still report The daemon is not active.

I am having this same issue. I can't create hyperdrives.

I guess this has something to do with the address not being hole-punchable?
First terminal:

Second one:

When I tried to hyp create drive, hyp daemon start or hyp daemon status first terminal would log:
Remote client opened
Remote client closed

I also had this problem, but downgraded node to v14 and then it worked. Unsure if that was related, but that was something that changed that made it work. Could be worth trying out at least.

I am having this same issue. I can't create hyperdrives.

$ hyp daemon start
Hyperspace daemon started
Mirroring daemon started
Daemon is running.
$ hyp daemon status
Daemon not active
$ node -v 
v17.2.0

It would be nice if some of you could try downgrading node to version 14 and see if that helps you.

I cloned the git repo to troubleshoot this issue.

It prints The daemon is not active when running anything other than hyp daemon or hyp beam because hyper.setup() fails:

cli/bin/hyp.js

Lines 104 to 114 in cd56bb6

    
           try { 
        
             if (!obj.name.startsWith('daemon') && obj.name !== 'beam') { 
        
               await hyper.setup() 
        
             } 
        
           } catch (err) { 
        
             console.error('The daemon is not active. Please run:') 
        
             console.error('') 
        
             console.error('  hyp daemon start') 
        
             console.error('') 
        
             process.exit(2) 
        
           }

Which fails because it fails to connect to either hyperspace or the mirroring service:

cli/lib/hyper/index.js

Lines 15 to 18 in cd56bb6

    
           export async function setup ({canStartDaemon} = {canStartDaemon: false}) { 
        
             await setupClient('hyperspace', 'Hyperspace', () => new HyperspaceClient(), canStartDaemon) 
        
             await setupClient('hyperspace-mirroring-service', 'Mirroring', () => new MirroringClient(), canStartDaemon) 
        
           }

So far, I got it working by simply:

$ npm i -g hyperspace hyperspace-mirroring-service
$ hyperspace
$ hyperspace-mirroring-service

Now it works:

$ hyp info --live
No hypers active.

Spawn daemon process without setting up an stdio pipe to the parent p…

Same here, node v16.13.1, macos 12.1.
It should be "auto-connecting", right?

Also BeakerBrowser couldn't connect to hyper:// addresses either, not sure if it's related or not.

Check out PR #57 and see if it works.

was on node 17, downgraded to 14 and it worked

Linux with node v16.13.2 does not work, either. Same behaviour.

Downgraded to Nodejs v14 after all these comments. Still getting the same response.

$ hyp daemon start
Hyperspace daemon started
Mirroring daemon started
Daemon is running.
$ hyp info --live
The daemon is not active. Please run:

  hyp daemon start

@pfrazee

If someone could look at PR #57 that would be very helpful.

@pfrazee, could you take a moment?

@specious

@specious I'm sorry, I really can't -- I'm engaged with a new job rn, I have to punt this to the hypercore team

@pfrazee

If someone could look at PR #57 that would be very helpful.

@pfrazee, could you take a moment?

This hotfix seems to solve the problem.
Thank you!

Solves it 🎉

Navigation Menu

Repository navigation

keep getting "the daemon is not active" even after running hyp daemon start #52

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	try {
	if (!obj.name.startsWith('daemon') && obj.name !== 'beam') {
	await hyper.setup()
	}
	} catch (err) {
	console.error('The daemon is not active. Please run:')
	console.error('')
	console.error(' hyp daemon start')
	console.error('')
	process.exit(2)
	}

	export async function setup ({canStartDaemon} = {canStartDaemon: false}) {
	await setupClient('hyperspace', 'Hyperspace', () => new HyperspaceClient(), canStartDaemon)
	await setupClient('hyperspace-mirroring-service', 'Mirroring', () => new MirroringClient(), canStartDaemon)
	}

keep getting "the daemon is not active" even after running hyp daemon start #52

Description

Activity

metanomial commented on Sep 19, 2021

cablehead commented on Sep 30, 2021

jaoiaisoh commented on Dec 1, 2021

jaoiaisoh commented on Dec 1, 2021

ralphtheninja commented on Dec 9, 2021

felixdrp commented on Dec 13, 2021

ralphtheninja commented on Dec 13, 2021

specious commented on Jan 1, 2022

alexindigo commented on Jan 9, 2022

specious commented on Jan 9, 2022

robindiddams commented on Jan 11, 2022

dwehrmann commented on Feb 22, 2022

marvinpoo commented on Mar 4, 2022

specious commented on Mar 4, 2022

pfrazee commented on Mar 4, 2022

marvinpoo commented on Mar 7, 2022

luandro commented on Mar 10, 2022

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions