Yes - this is an issue with the filename, there should be an updated
version on the config repo already:

file: "[% ARGS.0.replace('[^\\w-]','_') %].crt"

Oliver

Am 16.11.21 um 16:19 schrieb Jess Johnson:
> Ok, I found that. There are two directories in the publishing.yaml
> /tmp
> /var/www/download 
>
> Both of these have been written successfully since this one workflow
> failed and continues to fail publish, so I think it might be something
> to do with the filename?
> CN=hostname:8111,DC=infra,DC=bwi,C=US
>
> Could the :8111 be causing the issue?
>
> Jess
>
> On Tue, Nov 16, 2021 at 12:47 AM Oliver Welter <[email protected]
> <mailto:[email protected]>> wrote:
>
>     Hi Jess,
>
>     the old sample configuration has a "publish to disk" target for
>     all certificates configured, I would assume that the defined path
>     does not exists or is not writeable. The targets are defined in
>     publishing.yaml, the "link" to a publish target is set in the
>     certificate profiles.
>
>     Oliver
>
>     Am 15.11.21 um 18:14 schrieb Jess Johnson:
>>     The cert signed successfully but publish (to what?) is failing. 
>>     My CRL was expired so maybe that was it? I refreshed it,
>>     successfully signed two more certs and they published, again to
>>     what?.
>>
>>     I retried the workflow on the one that failed and it still
>>     failed. How can I figure out what's wrong? 
>>
>>     Type     certificate_publishing
>>     Creator  jesse
>>     State    PUBLISH
>>     Action   certpublish_publish_profile
>>     Run State        Loop retries exceeded
>>
>>
>>     2021-11-15 16:26:08 UTC  WARN    Retry exceeded on action
>>     certpublish_publish_profile ([undef])
>>     2021-11-15 16:26:08 UTC  INFO    Publication failed for target
>>     disk, requeuing ([undef])
>>     2021-11-15 16:26:08 UTC  INFO    Start publication to
>>     <redacted>:8111 for CN=<redacted>:8111,DC=infra,DC=bwi,C=US
>>     ([undef])
>>     2021-11-15 16:26:08 UTC  INFO    Reloaded 1 targets from queue
>>     ([undef])
>>
>>
>>
>>
>>     _______________________________________________
>>     OpenXPKI-users mailing list
>>     [email protected] 
>> <mailto:[email protected]>
>>     https://lists.sourceforge.net/lists/listinfo/openxpki-users 
>> <https://lists.sourceforge.net/lists/listinfo/openxpki-users>
>
>
>     -- 
>     Protect your environment -  close windows and adopt a penguin! 
>
>     _______________________________________________
>     OpenXPKI-users mailing list
>     [email protected]
>     <mailto:[email protected]>
>     https://lists.sourceforge.net/lists/listinfo/openxpki-users
>     <https://lists.sourceforge.net/lists/listinfo/openxpki-users>
>
>
>
> _______________________________________________
> OpenXPKI-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openxpki-users


-- 
Protect your environment -  close windows and adopt a penguin! 

_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users

Reply via email to