Unable to start workspaces due to Syntax error in che-plugin-registry
See original GitHub issueDescribe the bug
Unable to start workspaces as the che-plugin-registry is failing to start.
=> sourcing 10-set-mpm.sh ...
=> sourcing 20-copy-config.sh ...
=> sourcing 40-ssl-certs.sh ...
AH00526: Syntax error on line 39 of /opt/rh/httpd24/root/etc/httpd/conf.d/mod_security.conf:
ModSecurity: Failed to open debug log file: /var/log/httpd24/modsec_debug.log
Che version
- nightly
Steps to reproduce
Try to start any new or existing workspace.
Runtime
- kubernetes
Installation method
- helm
Environment
- Cloud
- other (Rancher/AWS)
Issue Analytics
- State:
- Created 4 years ago
- Comments:18 (18 by maintainers)
Top Results From Across the Web
Troubleshoot issues accessing your WorkSpace from the ...
This error typically indicates that the WorkSpaces client can authenticate over port 443, but can't establish a connection over TCP port ...
Read more >Administration Guide Red Hat CodeReady Workspaces 2.0
CodeReady Workspaces 2.0 introduces two registries: the plug-in registry and the devfile registry. They are static websites where the metadata of CodeReady ...
Read more >Devfile v2 and IDE plug-ins in Eclipse Che - Medium
Devfile v1 were handled by Eclipse Che Server workspace engine using ... need to be there else the VS Code java extension may...
Read more >WorkSpaces — Boto3 Docs 1.26.37 documentation
The error code that is returned if the Standby WorkSpace could not be created. ... always create a new one when you want...
Read more >AWS Workspaces CLI: Syntax for `Start - Stack Overflow
This command is timing out. It feels like 101 but can't find any references online. Thanks for your help.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@amisevsk here’s the output when I force the image to run with a custom entrypoint:
It looks like this is now fixed somehow, closing.