question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Config Support]: v12 - error on config file but not telling me what the error/line is. Does not start.

See original GitHub issue

Describe the problem you are having

[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
11:37:50.554 INF [api] listen addr=:1984
11:37:50.554 INF [rtsp] listen addr=:8554
11:37:50.554 INF [webrtc] listen addr=:8555
11:37:50.554 INF [srtp] listen addr=:8443
[2022-11-03 11:37:52] frigate.app                    INFO    : Starting Frigate (0.12.0-1bc9efd)
*************************************************************
*************************************************************
***    Your config file is not valid!                     ***
***    Please check the docs at                           ***
***    https://docs.frigate.video/configuration/index     ***
*************************************************************
*************************************************************
***    Config Validation Errors                           ***
*************************************************************
1 validation error for FrigateConfig
live
  extra fields not permitted (type=value_error.extra)
Traceback (most recent call last):
  File "/opt/frigate/frigate/app.py", line 344, in start
    self.init_config()
  File "/opt/frigate/frigate/app.py", line 78, in init_config
    user_config = FrigateConfig.parse_file(config_file)
  File "/opt/frigate/frigate/config.py", line 977, in parse_file
    return cls.parse_obj(config)
  File "pydantic/main.py", line 521, in pydantic.main.BaseModel.parse_obj
  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for FrigateConfig
live
  extra fields not permitted (type=value_error.extra)
*************************************************************
***    End Config Validation Errors                       ***
*************************************************************
[cmd] python3 exited 1
exit OK
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
11:38:47.446 INF [api] listen addr=:1984
11:38:47.446 INF [webrtc] listen addr=:8555
11:38:47.446 INF [rtsp] listen addr=:8554
11:38:47.446 INF [srtp] listen addr=:8443
[2022-11-03 11:38:48] frigate.app                    INFO    : Starting Frigate (0.12.0-1bc9efd)
*************************************************************
*************************************************************
***    Your config file is not valid!                     ***
***    Please check the docs at                           ***
***    https://docs.frigate.video/configuration/index     ***
*************************************************************
*************************************************************
***    Config Validation Errors                           ***
*************************************************************
1 validation error for FrigateConfig
live
  extra fields not permitted (type=value_error.extra)
Traceback (most recent call last):
  File "/opt/frigate/frigate/app.py", line 344, in start
    self.init_config()
  File "/opt/frigate/frigate/app.py", line 78, in init_config
    user_config = FrigateConfig.parse_file(config_file)
  File "/opt/frigate/frigate/config.py", line 977, in parse_file
    return cls.parse_obj(config)
  File "pydantic/main.py", line 521, in pydantic.main.BaseModel.parse_obj
  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for FrigateConfig
live
  extra fields not permitted (type=value_error.extra)
*************************************************************
***    End Config Validation Errors                       ***
*************************************************************
[cmd] python3 exited 1
exit OK
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

Version

On logs above

Frigate config file

Will provide if it's relevant, please ask.

Relevant log output

As above

Frigate stats

No response

Operating system

Debian

Install method

Docker CLI

Coral version

CPU (no coral)

Any other information that may be helpful

Surely the validation should tell me where the error is… not helpful to just tell me that there is an error on the config file, if the parser knows where it is then tell me the exact line so I can go fix it!

Issue Analytics

  • State:open
  • Created a year ago
  • Comments:9 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
blakeblackshearcommented, Nov 3, 2022

We publish development builds for internal testing just like every other project does. Soon enough, automatic builds from the dev branch will be pushed to dockerhub on every commit. This is a common practice and also done by Home Assistant: https://hub.docker.com/r/homeassistant/home-assistant/tags

The official stance would be:

Development builds are meant for testing or for those who want bleeding edge access to new features. You should expect undocumented breaking changes and known/unknown issues, so be prepared to read through the source code changes if you would like to use them. We aren’t quite ready for general users to test them and don’t have the bandwidth to provide config support after each commit during development. If you need this kind of help, please wait until a beta release.

The best place to look when using development issues will be the draft release PR.

Tone is difficult to communicate in written text. As I am sure you have seen on here, @NickM-27 puts forth more effort than anyone else to help others. I tend to give people the benefit of the doubt.

0reactions
github-actions[bot]commented, Dec 4, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error "config file error: line 44: ignoring line due to no section ...
Error config file error: line 44: ignoring line due to no section is shown in /var/log/messages during the restart of nfs-server service.
Read more >
Article ID : 000020441 Cannot apply configuration template to ...
Cannot apply configuration template to fully managed device (Error: ... This issue does not appear to affect new templates created in v12.6 or...
Read more >
There was an error in web.config. Please correct before ...
Hi, When I try your tip of opening and closing the Web.config file I get the error right away. Good, I had not...
Read more >
Knowledge Base - Customer Support
Applies to V12.x Issue When Unica user with Non Platform admin role assigned to it create a New Job Notification in Platform scheduler,...
Read more >
Failed to load next.config.js - Stack Overflow
however all it is telling me is Not Supported. I'm not familiar with the error and was looking for guidance. reactjs · next.js....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found