Opened 7 years ago

Closed 6 years ago

#1691 closed defect (fixed)

throw proper exception on invalid hostname in rasmgr.conf

Reported by: Dimitar Misev Owned by: Dimitar Misev
Priority: major Milestone: 9.7
Component: rasserver Version: development
Keywords: Cc: Peter Baumann
Complexity: Medium

Description

If the -host value in rasmgr.conf is wrong rasserver dies without any meaningful exception/log message; this needs to be fixed.

To reproduce edit rasmgr.conf and set the -host parameters to some invalid values (different from the output of hostname).

Change History (6)

comment:1 by Vlad Merticariu, 7 years ago

Milestone: 9.5 → Future

comment:2 by Dimitar Misev, 7 years ago

Milestone: Future → 9.6

This is a bad confusing problem and needs to be resolved soon.

comment:3 by Dimitar Misev, 7 years ago

Milestone: 9.6 → 9.7

comment:4 by Dimitar Misev, 6 years ago

Owner: changed from bbell to Dimitar Misev
Status: new → assigned

comment:5 by Dimitar Misev, 6 years ago

Patch submitted, errors look like this:

[WARNING] - 2018-11-07 15:42:46,627, servergroupimpl.cc:168: Failed registering server 61df34fd-b280-4b21-be8f-2383bb176aee: Server could not be reached at blade:7002, invalid -host in rasmgr.conf?

[WARNING] - 2018-11-07 15:42:58,682, servergroupimpl.cc:168: Failed registering server f614965f-6152-49f2-bc24-e44657519366: Server could not be reached at blade:7002, invalid -host in rasmgr.conf?

[WARNING] - 2018-11-07 15:43:10,737, servergroupimpl.cc:168: Failed registering server 35b597a9-1ae9-49a4-8184-a9ee00b5941d: Server could not be reached at blade:7002, invalid -host in rasmgr.conf?

[ERROR] - 2018-11-07 15:43:10,737, servergroupimpl.cc:184: Server registration in group N1 failed too many times.

comment:6 by Dimitar Misev, 6 years ago

Resolution: → fixed
Status: assigned → closed
Note: See TracTickets for help on using tickets.