Page MenuHomekolab.org

Improper System FQDN should be a fatal error
Open, NormalPublic

Description

People skip through the "preparing your system" part of the "installation guide" like crazy, and end up hitting severe and fatal errors in setup-kolab.

I had originally posted a blog article on kolab.org but that has now vanished.

I propose I give in to my temptation and make the checks and balances work out in favour of less fatal failures with no path to recovery;

When setup-kolab is launched, instead of issuing a warning, cause a fatal error and quit the program with an explanatory message.

Implementation Design Considerations

  • A proper FQDN is used for self-reference in 389, and nowadays is necessary for successful integration between Manticore, Chwala and Roundcube Kolab Plugins 's kolab_files plugin -- it's an iframe vs. browser security thing.
  • To check whether the system has a proper FQDN, we currently just look at the configured hostname and the ip address on the socket with the default route. We now need to also check whether the client (desktop) can use the same address to get to the server. We should take in to account that a system may be called demo01.example.org whereas the address to use to reach it may be demo.kolab.io, or even webmail.kolab.io or kolab.io/apps.

    For this reason I would bump the number of hours estimated from 1 to 8.

Details

Ticket Type
Task

Event Timeline

jh23453 added a subscriber: jh23453.Feb 5 2016, 6:28 PM

Please see one of my mails - I did everything the guides asked for - but still failed.
So my guess is that the guide needs some updates too.

Please see the thread in devel@lists.kolab.org starting at
Message-ID: <83bn8cvson.fsf@echidna.jochen.org>

In T977#13817, @jh23453 wrote:

Please see one of my mails - I did everything the guides asked for - but still failed.
So my guess is that the guide needs some updates too.

Please see the thread in devel@lists.kolab.org starting at
Message-ID: <83bn8cvson.fsf@echidna.jochen.org>

I can't search through the list of failures having happened back then, which may (or may not) have been resolved since then, scouting for the one or two set of symptoms that possibly describe a scenario that could potentially intervene with the generic line of thought of this ticket.

petersen rescinded a token.

Maybe re-post the article in The Hub and provide a link to it in the message.

vincent closed this task as Resolved.Feb 11 2016, 12:32 PM
vincent claimed this task.
vincent reopened this task as Open.

Doh!

vanmeeuwen removed vincent as the assignee of this task.Feb 11 2016, 12:38 PM

You would typically not assign the task to yourself ;-)

vanmeeuwen updated the task description. (Show Details)Feb 11 2016, 12:44 PM
vanmeeuwen edited a custom field.

Yes, I own it now.

pasik added a subscriber: pasik.Nov 25 2017, 2:38 PM
vanmeeuwen lowered the priority of this task from 60 to Normal.Mar 22 2019, 12:28 PM

Correcting the priority from 60/40 to Normal