Re: error: Unable to start server (community 3.18.0)

ut-oh, may have popped the cork a bit too quick.  Now cf-execd fails to 
start.  Looking at cf-execd.service, it contains the text of a symlink:

root@baker1 [cfengine3.service.wants]# cd /usr/lib/systemd/system/
root@baker1 [system]# ll cf*
-rw-r--r--. 1 root root  462 Jun 23 10:53 cf-apache.service
-rw-r--r--. 1 root root  864 Jun 23 10:53 cfengine3.service
-rw-r--r--. 1 root root  101 Jul  7 09:28 cf-execd.service
-rw-r--r--. 1 root root  443 Jun 23 10:53 cf-hub.service
-rw-r--r--. 1 root root  358 Jun 23 10:53 cf-monitord.service
-rw-r--r--. 1 root root 1150 Jun 23 10:53 cf-postgres.service
-rw-r--r--. 1 root root  664 Jun 23 10:53 cf-runalerts.service
-rw-r--r--. 1 root root  437 Jun 23 10:53 cf-serverd.service
root@baker1 [system]# cat cf-execd.service 
lrwxrwxrwx. 1 root root 40 Dec  8  2017 cf-execd.service -> 
/usr/lib/systemd/system/cf-execd.service

So I replaced this with cf-execd.service from github but still not 
working.  This is from the journal:

systemd: Cannot add dependency job for unit cf-execd.service, ignoring: 
Unit is not loaded properly: Invalid argument.

On Wednesday, July 7, 2021 at 1:40:37 PM UTC-5 Beto wrote:

> Yes sir, ipv6 is disabled..
>
> On Wednesday, July 7, 2021 at 1:19:45 PM UTC-5 [email protected] 
> wrote:
>
>> Perfect. Thank you. The issue is with the bind interface of "::" aka ipv6 
>> wildcard address, if this fails then we don't fall back to ipv4.
>>
>> Do you by chance have ipv6 disabled? I would suspect the answer is yes 
>> but would like to know for sure.
>>
>> Thanks,
>> Craig
>>
>> On Wednesday, July 7, 2021 at 1:05:56 PM UTC-5 Beto wrote:
>>
>>> Oh btw this is RHEL7.
>>>
>>> On Wednesday, July 7, 2021 at 1:00:32 PM UTC-5 Beto wrote:
>>>
>>>> That did it.  Thanks, Craig!
>>>>
>>>> On Wednesday, July 7, 2021 at 12:45:10 PM UTC-5 
>>>> [email protected] wrote:
>>>>
>>>>> Can you include some basic information like OS name/version? Thanks!
>>>>>
>>>>> Yes. This is likely a known issue we are working through right now. 
>>>>>
>>>>> Please remove or comment out this section of policy and try again.
>>>>>
>>>>>
>>>>> https://github.com/cfengine/masterfiles/blob/3.18.x/controls/cf_serverd.cf#L73-L77
>>>>>
>>>>> If it still fails, please start cf-serverd with strace
>>>>>
>>>>> ```
>>>>> strace /var/cfengine/bin/cf-serverd -F
>>>>> ```
>>>>>
>>>>> Hopefully the policy fix resolves the issue for you.
>>>>>
>>>>> -Craig
>>>>> On Wednesday, July 7, 2021 at 12:36:05 PM UTC-5 Beto wrote:
>>>>>
>>>>>> I installed community 3.18.0 and masterfiles 3.18.0.  cf-serverd 
>>>>>> fails with the  message in the subject and exits with rc 1, which I can't 
>>>>>> find documented.  No other errors appear in verbose output.
>>>>>>
>>>>>> Anyone got a clue?  TIA
>>>>>>
>>>>>

-- 
You received this message because you are subscribed to the Google Groups "help-cfengine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/help-cfengine/2a18f03c-cc89-4fbb-8f33-da78e4336cb7n%40googlegroups.com.