1# FAQs 2 3## System startup interrupted due to "parse failed!" error 4 5**Problem** 6 7During system startup, the error message "\[Init\] InitReadCfg, parse failed! please check file /etc/init.cfg format." is displayed, and the startup is interrupted, as shown in the following figure. 8 9**Figure 1** Error information<a name="fig15217111545118"></a> 10 11 12**Cause** 13 14During the modification of the **init.cfg** file, required commas \(,\) or parentheses are missing or unnecessary ones are added. As a result, the file's JSON format becomes invalid. 15 16**Solution** 17 18Check the **init.cfg** file and ensure that its format meets the JSON specifications. 19 20## System automatically restarted again and again 21 22**Problem** 23 24After the image burning is complete, the system keeps restarting. 25 26**Cause** 27 28Each service started by the init process has the **importance** attribute, as described in Table 3 in [Job Management](../subsystems/subsys-boot-init-jobs.md). 29 30- If the attribute value is **0**, the init process does not need to restart the development board when the current service process exits. 31- If the attribute value is **1**, the init process needs to restart the development board when the current service process exits. 32 33During the startup of a service whose **importance** is **1**, if the service exits due to a process crash or an error, the init process automatically restarts the development board. 34 35**Solution** 36 371. View logs to identify the service that encounters a process crash or exits due to an error, rectify the issue, and then burn the image again. 382. Alternatively, change the value of **importance** to **0** for the service that exits due to a process crash or an error, and then burn the image again. In this way, the development board will not be restarted even if the service exits. 39 40## Failed to call the **SetParameter** or **GetParameter** API with correct parameter values 41 42**Problem** 43 44Calling the **SetParameter** or **GetParameter** API fails even if correct values are passed to all input parameters. 45 46**Cause** 47 48Permission verification has been enabled for the **SetParameter** and **GetParameter** APIs. If the UID of the caller is greater than 1000, that is, the caller does not have the permission to call these APIs, API calls will fail even if the parameters are correct. 49 50**Solution** 51 52No action is required. 53 54
