Bug 1859805

Summary:	cjdroute won't start when "pipe": "/tmp" specified in /etc/cjdroute.conf
Product:	[Fedora] Fedora EPEL	Reporter:	Stuart D Gathman <stuart>
Component:	cjdns	Assignee:	Orphan Owner <extras-orphan>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	stuart
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-07-09 03:16:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stuart D Gathman 2020-07-23 04:25:23 UTC

Description of problem:
cjdroute won't start

Version-Release number of selected component (if applicable):
cjdns-20.7-1.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. uncomment "pipe": "/tmp" at bottom of cjdroute.conf
2. make sure preceding entry has comma :-)
3. (re)start cjdns

Actual results:
 cjdroute2.c:753 Pipe directory not writable: [/tmp]

Expected results:
normal startup

Additional info:
works in 20.6

Comment 1 Stuart D Gathman 2020-07-23 04:25:49 UTC

Workaround: don't specify pipe directory

Comment 2 Stuart D Gathman 2020-07-23 04:33:03 UTC

Also works to specify "pipe": "/tmp/cjdroute.sock" 

So the example config was just wrong.

Comment 3 Fedora Admin user for bugzilla script actions 2023-02-07 00:05:36 UTC

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 4 Troy Dawson 2024-07-09 03:16:18 UTC

EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.