Bug #30
improve error handling on parsing files.
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Javi Fontan | % Done: | 0% | |
| Category: | Client API & Library | |||
| Target version: | Release 1.0 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: |
Description
If the oned.conf is not in the proper format, the one start command always fails and does not give a descriptive message of the reason.
i.e. if you have one uncommented line like this (the one with ---)
#defaultvalues and configuration parameters for the driver
----------------------------------------------
IM_MAD = [
name
< < <
when you try to execute the one start you get:
:bin$ one start
oned and scheduler started
basic_string::_S_construct NULL not valid
< < <
this is because of the error handling on the yak and lex modules for parsing the oned.conf file.
Associated revisions
Bug partially fixed from to ticket #30, now the parsing error is showed in the STDOUT...
git-svn-id: http://svn.opennebula.org/trunk@66 3034c82b-c49b-4eb3-8279-a7acafdc01c0
History
#1
Updated by anonymous - almost 13 years ago
The problem was caused, because we tried to use the Logger before initialize it, so now we show this error on the stdout, still when this happen the scheduler (mm_sched) is initialized which shouldn't occur.
:bin$ one start
oned and scheduler started
Error while parsing configuration file:
syntax error, unexpected NL, expecting EQUAL at line 21, columns 1065:1066
Could not load nebula configuration file.
lgonzalez@boxita:bin$ pgrep -l mm_sched
11963 mm_sched
#2
Updated by Ruben S. Montero almost 13 years ago
- Status changed from New to Closed
- Resolution set to fixed