[
https://issues.apache.org/jira/browse/KUDU-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin updated KUDU-2005:
--------------------------------
Description:
If pointing to non-existent files using {{-webserver_certificate_file}} and
{{-webserver_private_key_file}} flags, kudu-master and kudu-tserver fail to
start with obscure error message like the following:
{noformat}
F0510 10:33:30.088955 27653 master_main.cc:71] Check failed: _s.ok() Bad
status: Network error: Webserver: Could not start on address 0.0.0.0:8051
{noformat}
Nothing else is in the WARNING or ERROR log files indicate that the issue was
about not being able to load the data from the specified files.
The only trace of the real cause of the issue can be found in the INFO log file:
{noformat}
I0510 10:33:30.046664 27653 webserver.cc:148] Webserver: Enabling HTTPS support
I0510 10:33:30.046880 27653 webserver.cc:297] Webserver: set_ssl_option: cannot
open /etc/tls/kudu-master.cert.pem: error:02001002:system library:fopen:No such
file or directory
W0510 10:33:30.046972 27653 net_util.cc:293] Failed to bind to 0.0.0.0:8051.
Trying to use lsof to find any processes listening on the same port:
I0510 10:33:30.047003 27653 net_util.cc:296] $ export PATH=$PATH:/usr/sbin ;
lsof -n -i 'TCP:8051' -sTCP:LISTEN ; for pid in $(lsof -F p -n -i 'TCP:8051'
-sTCP:LISTEN | grep p | cut -f 2 -dp) ; do while [ $pid -gt 1 ] ; do ps h
-fp $pid ; stat=($(</proc/$pid/stat)) ; pid=${stat[3]} ; done ; done
W0510 10:33:30.088867 27653 net_util.cc:303]
{noformat}
It's necessary to make the error message informative and actionable.
was:
If pointing to non-existent files using {{--webserver_certificate_file}} and
{{--webserver_private_key_file}} flags, kudu-master and kudu-tserver fail to
start with obscure error message like the following:
{noformat}
F0510 10:33:30.088955 27653 master_main.cc:71] Check failed: _s.ok() Bad
status: Network error: Webserver: Could not start on address 0.0.0.0:8051
{noformat}
Nothing else is in the WARNING or ERROR log files indicate that the issue was
about not being able to load the data from the specified files.
The only trace of the real cause of the issue can be found in the INFO log file:
{noformat}
I0510 10:33:30.046664 27653 webserver.cc:148] Webserver: Enabling HTTPS support
I0510 10:33:30.046880 27653 webserver.cc:297] Webserver: set_ssl_option: cannot
open /etc/tls/kudu-master.cert.pem: error:02001002:system library:fopen:No such
file or directory
W0510 10:33:30.046972 27653 net_util.cc:293] Failed to bind to 0.0.0.0:8051.
Trying to use lsof to find any processes listening on the same port:
I0510 10:33:30.047003 27653 net_util.cc:296] $ export PATH=$PATH:/usr/sbin ;
lsof -n -i 'TCP:8051' -sTCP:LISTEN ; for pid in $(lsof -F p -n -i 'TCP:8051'
-sTCP:LISTEN | grep p | cut -f 2 -dp) ; do while [ $pid -gt 1 ] ; do ps h
-fp $pid ; stat=($(</proc/$pid/stat)) ; pid=${stat[3]} ; done ; done
W0510 10:33:30.088867 27653 net_util.cc:303]
{noformat}
It's necessary to make the error message informative and actionable.
> Non-actionable error message if pointing
> --webserver_{certificate,private_key}_file to non-existing files
> ---------------------------------------------------------------------------------------------------------
>
> Key: KUDU-2005
> URL: https://issues.apache.org/jira/browse/KUDU-2005
> Project: Kudu
> Issue Type: Bug
> Components: master, tserver
> Affects Versions: 1.3.1
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
>
> If pointing to non-existent files using {{-webserver_certificate_file}} and
> {{-webserver_private_key_file}} flags, kudu-master and kudu-tserver fail to
> start with obscure error message like the following:
> {noformat}
> F0510 10:33:30.088955 27653 master_main.cc:71] Check failed: _s.ok() Bad
> status: Network error: Webserver: Could not start on address 0.0.0.0:8051
> {noformat}
> Nothing else is in the WARNING or ERROR log files indicate that the issue was
> about not being able to load the data from the specified files.
> The only trace of the real cause of the issue can be found in the INFO log
> file:
> {noformat}
> I0510 10:33:30.046664 27653 webserver.cc:148] Webserver: Enabling HTTPS
> support
> I0510 10:33:30.046880 27653 webserver.cc:297] Webserver: set_ssl_option:
> cannot open /etc/tls/kudu-master.cert.pem: error:02001002:system
> library:fopen:No such file or directory
> W0510 10:33:30.046972 27653 net_util.cc:293] Failed to bind to 0.0.0.0:8051.
> Trying to use lsof to find any processes listening on the same port:
> I0510 10:33:30.047003 27653 net_util.cc:296] $ export PATH=$PATH:/usr/sbin ;
> lsof -n -i 'TCP:8051' -sTCP:LISTEN ; for pid in $(lsof -F p -n -i 'TCP:8051'
> -sTCP:LISTEN | grep p | cut -f 2 -dp) ; do while [ $pid -gt 1 ] ; do ps h
> -fp $pid ; stat=($(</proc/$pid/stat)) ; pid=${stat[3]} ; done ; done
> W0510 10:33:30.088867 27653 net_util.cc:303]
> {noformat}
> It's necessary to make the error message informative and actionable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
