(Solved) Disruption - Candidate and Vacancy search

Dear user,

At this moment, 11/07 around 11:30, there is a malfunction. More information can be found below.

This disruption concerns:
- Candidate search tab
- Vacancy search tab

What is going on?
Search, the module that regulates the search functionality for these tabs has crashed. We're currently rebooting the service, it's possible it's not stabl yet. We're currently looking into the cause of the crash.

Because of this crash multiple indexes have gone corupt, we'll restore these as soon as possible.

What can you notice?
When you navigate to one of the tabs, you'll get the message: "Service temporarily unavailable". This message will be shown as long as Search is offline.

When the service is available again, it's possible you won't see any results but instead a message "Oops. Something went wrong". This is caused by the corrupt indexes. We're going to remake these indexes, but this will take some time.

Is there a workaround available?
Unfortunately, there is no workaround.

When do we expect this to be fixed?
We expect Search to be online around noon.

With this article we'll keep you informed, our apologies for any inconvenience this may have caused.

Any questions?
Our support is available for questions. You can reach us at 010 - 49 80 988 or by e-mail support@connexys.com

Kind regards,
Connexys

Comments

  • Avatar
    Richard de Witt

    Search is back online!
    In the end the downtime was about 10 minutes.

    We've also found the cause, which is a bit technical. I'll do my best to explain it:

    We create a XML file of all the information on which you can search. This XML is then passed on the our Search module, which extracts the information and indexes the data. This morning we had 1 XML file with an unallowed character. Search couldn't handle this and crashed.

    We don't have a solution yet with which we can prevent such errors. We also haven't been able to trace the XML which contained this error yet.