Abort parodus start without hw-mac command line argument

[xmidt-org]

Abort parodus start without hw-mac command line argument

[shilpa24balaji]

When parodus is started without command line arguments, then it gets into infinite loop. This problem exists in old version afbb5c5

./parodus
[1527302436][PARODUS][Info]: ********** Starting component: Parodus **********
[1527302436][PARODUS][Info]: parodus local_url is NULL. adding default url
[1527302436][PARODUS][Info]: cfg->webpa_protocol is PARODUS-2.0-afbb5c5
[1527302436][PARODUS][Info]: CJWT is disabled, Hence proceeding without validation
[1527302436][PARODUS][Info]: Received reboot_reason as:
[1527302436][PARODUS][Info]: Received reconnect_reason as:webpa_process_starts
[1527302436][PARODUS][Info]: server_Address
[1527302436][PARODUS][Info]: User-Agent: PARODUS-2.0-afbb5c5 (unknown; unknown/unknown;)
[1527302436][PARODUS][Error]: Failed to GET Reboot reason value
[1527302436][PARODUS][Info]: X-WebPA-Convey Header: [107]{"boot-time":0,"webpa-protocol":"PARODUS-2.0-afbb5c5","webpa-last-reconnect-reason":"webpa_process_starts"}
[1527302436][PARODUS][Info]: Device_id mac:
[1527302436][PARODUS][Info]: Try connecting with Ipv6 mode
[1527302436][PARODUS][Info]: Ipv6 connection failed. Try connecting with Ipv4 mode
[1527302436][PARODUS][Error]: getaddrinfo: Name or service not known
[1527302436][PARODUS][Info]: Waiting with backoffRetryTime 0 seconds

In the latest parodus master without any arguments is fixed

./parodus
[1527294717][PARODUS][Info]: ********** Starting component: Parodus **********
[1527294717][PARODUS][Info]: Setting default values to parodusCfg
[1527294717][PARODUS][Info]: cfg->webpa_protocol is PARODUS-2.0-7a7e7ac
[1527294717][PARODUS][Info]: Parsing parodus command line arguments..
[1527294717][PARODUS][Error]: Missing webpa url argument
Aborted (core dumped)

If bad mac like empty is passed then this error is returned:

[1527294880][PARODUS][Error]: Bad mac address

[shilpa24balaji]

Since both parodus start without arguments and hw-mac both are addressed in latest, closing this issue