You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by "Nguyen, Kyle" <Ky...@mlp.com.INVALID> on 2023/05/02 19:47:28 UTC
"Broken pipe" when trying to use the CLI
Hi.
We are getting “Broken pipe” when trying nifi-toolkit. How would we go about debugging this? Any help is appreciated! Thanks!
root@bizdev-nifi-dev:/opt/nifi/nifi-toolkit-current/bin# ./cli.sh
Session loaded from /root/.nifi-cli.config
#> session show
Current Session:
nifi.props = /opt/nifi/nifi-current/conf/dev.nifi-cli.nifi.properties
#> nifi pg-list
ERROR: Error executing command 'pg-list' : Broken pipe (Write failed)
Per documentation for cli toolkit: https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html#security-configuration
Currently the CLI supports authenticating with a client certificate and an optional proxied-entity. A common scenario would be running the CLI from one of the nodes where NiFi or NiFi Registry is installed, which allows the CLI to use the same keystore and truststore as the NiFi/NiFi Registry instance.
We have a keystore and truststore to secure our instance:
root@bizdev-nifi-dev:/opt/nifi/nifi-current/conf# cat nifi.properties | grep -i --color=auto jks
nifi.security.keystore=/opt/certs/keystore.jks
nifi.security.keystoreType=JKS
nifi.security.truststore=/opt/certs/truststore.jks
nifi.security.truststoreType=JKS
root@bizdev-nifi-dev:/opt/nifi/nifi-current/conf# grep -i --color=auto jks login-identity-providers.xml
<property name="TLS - Keystore">/opt/certs/keystore.jks</property>
<property name="TLS - Keystore Type">JKS</property>
<property name="TLS - Truststore">/opt/certs/truststore.jks</property>
<property name="TLS - Truststore Type">JKS</property>
Then inside my cli-toolkit properties file, I have:
root@bizdev-nifi-dev:/opt/nifi/nifi-current/conf# cat dev.nifi-cli.nifi.properties
baseUrl=https://bizdev-nifi-dev.nonprd.aws.mlp.com
keystore=/opt/certs/keystore.jks
keystoreType=JKS
keystorePasswd=*****************
keyPasswd=*****************
truststore=/opt/certs/truststore.jks
truststoreType=JKS
truststorePasswd=************
[cid:17261f6184a4cff311]
Kyle Nguyen
Corporate Technology, Software Engineer
Millennium Management LLC
399 Park Avenue | New York, NY 10022
📞 +1.212.708.1366 | 📱 +1.929.837.1788
mlp.com<https://www.mlp.com/home/>
######################################################################
The information contained in this communication is confidential and
may contain information that is privileged or exempt from disclosure
under applicable law. If you are not a named addressee, please notify
the sender immediately and delete this email from your system.
If you have received this communication, and are not a named
recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited.
######################################################################
Re: "Broken pipe" when trying to use the CLI
Posted by Bryan Bende <bb...@gmail.com>.
Hello,
You can add -verbose to the command to see a full error trace, however I'm
not sure it will tell you much more than the broken pipe message.
Broken pipe generally means some kind of network issue, typically it means
the other side of the connection closed the connection while the current
side was trying to read or write.
Ultimately I don't think it is really a CLI issue.
-Bryan
On Tue, May 2, 2023 at 3:51 PM Nguyen, Kyle <Ky...@mlp.com.invalid>
wrote:
> Hi.
>
>
>
> We are getting “Broken pipe” when trying nifi-toolkit. How would we go
> about debugging this? Any help is appreciated! Thanks!
>
>
>
> root@bizdev-nifi-dev:/opt/nifi/nifi-toolkit-current/bin# ./cli.sh
>
> Session loaded from /root/.nifi-cli.config
>
> #> session show
>
> Current Session:
>
> nifi.props = /opt/nifi/nifi-current/conf/dev.nifi-cli.nifi.properties
>
> #> nifi pg-list
>
> ERROR: Error executing command 'pg-list' : Broken pipe (Write failed)
>
>
>
> Per documentation for cli toolkit:
> https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html#security-configuration
>
>
>
> Currently the CLI supports authenticating with a client
> certificate and an optional proxied-entity. A common scenario would be
> running the CLI from one of the nodes where NiFi or NiFi Registry is
> installed, which allows the CLI to use the same keystore and truststore as
> the NiFi/NiFi Registry instance.
>
>
>
> We have a keystore and truststore to secure our instance:
>
>
>
> root@bizdev-nifi-dev:/opt/nifi/nifi-current/conf# cat nifi.properties |
> grep -i --color=auto jks
>
> nifi.security.keystore=/opt/certs/keystore.jks
>
> nifi.security.keystoreType=JKS
>
> nifi.security.truststore=/opt/certs/truststore.jks
>
> nifi.security.truststoreType=JKS
>
> root@bizdev-nifi-dev:/opt/nifi/nifi-current/conf# grep -i --color=auto
> jks login-identity-providers.xml
>
> <property name="TLS - Keystore">/opt/certs/keystore.jks</property>
>
> <property name="TLS - Keystore Type">JKS</property>
>
> <property name="TLS - Truststore">/opt/certs/truststore.jks</property>
>
> <property name="TLS - Truststore Type">JKS</property>
>
>
>
> Then inside my cli-toolkit properties file, I have:
>
>
>
> root@bizdev-nifi-dev:/opt/nifi/nifi-current/conf# cat
> dev.nifi-cli.nifi.properties
>
> baseUrl=https://bizdev-nifi-dev.nonprd.aws.mlp.com
>
> keystore=/opt/certs/keystore.jks
>
> keystoreType=JKS
>
> keystorePasswd=*****************
>
> keyPasswd=*****************
>
> truststore=/opt/certs/truststore.jks
>
> truststoreType=JKS
>
> truststorePasswd=************
>
>
>
> [image: cid:17261f6184a4cff311]
>
> *Kyle Nguyen*
> Corporate Technology, Software Engineer
>
>
>
> *Millennium Management LLC*
>
> 399 Park Avenue | New York, NY 10022
>
> 📞 +1.212.708.1366 | 📱 +1.929.837.1788
>
> mlp.com <https://www.mlp.com/home/>
>
>
>
>
>
> ######################################################################
>
> The information contained in this communication is confidential and
>
> may contain information that is privileged or exempt from disclosure
>
> under applicable law. If you are not a named addressee, please notify
>
> the sender immediately and delete this email from your system.
>
> If you have received this communication, and are not a named
>
> recipient, you are hereby notified that any dissemination,
>
> distribution or copying of this communication is strictly prohibited.
> ######################################################################
>
>