name: Bug report
about: store-demo.sh fails to build the web ui for stork
Describe the bug Trying to build the stork server, web-ui web-apache docker containers . Checked out the latest code and tried to run the stork-demo.sh script that builds these images. it is exiting with error to build the web-ui image.
Expected behavior Able to see the stork demo to start running.
Contacting you How can ISC reach you to discuss this matter further? If you do not specify any means such as e-mail, jabber id or a telephone, we may send you a message on github with questions when we have them.
Thanks a lot @slawek . I killed my other docker containers that were running and re ran the build, it went through.
Hi @slawek,
Sure will give it a try , Is there a configuration on Ram , cpu that you can suggest.
On Fri, 1 Dec 2023, 17:55 Slawek Figiel (@slawek), gitlab@gitlab.isc.org wrote:
Slawek Figiel https://gitlab.isc.org/slawek commented #1236 (comment 420712):
Hello @varsraja https://gitlab.isc.org/varsraja!
Thank you for your report.
It seems the build process was killed due to exceeding the resource usage limits (137 exit status). Preparing the UI bundle (ng build call) requires a lot of CPU and memory due to Angular and NodeJS specificity.
In some setups, Docker limits memory up to 2GB by default. Please check your configuration and try to slightly increase the limit(s) if any are set.
— Reply to this email directly or view it on GitLab #1236 (comment 420712). You're receiving this email because you have been mentioned on gitlab.isc.org. Unsubscribe https://gitlab.isc.org/-/sent_notifications/REDACTED/unsubscribe from this thread · Manage all notifications https://gitlab.isc.org/-/profile/notifications · Help https://gitlab.isc.org/help
name: Bug report
about: store-demo.sh fails to build the web ui for stork
Describe the bug Trying to build the stork server, web-ui web-apache docker containers . Checked out the latest code and tried to run the stork-demo.sh script that builds these images. it is exiting with error to build the web-ui image.
Expected behavior Able to see the stork demo to start running.
Contacting you How can ISC reach you to discuss this matter further? If you do not specify any means such as e-mail, jabber id or a telephone, we may send you a message on github with questions when we have them.
Sure @tomek . Thanks for letting me know
On Fri, 22 Oct 2021, 17:17 Tomek Mrugalski (@tomek), gitlab@gitlab.isc.org wrote:
Milestone changed to Kea2.1-backlog %kea2.1-backlog (Sep 30, 2021–Jun 29, 2022)
— Reply to this email directly or view it on GitLab #1969. You're receiving this email because of your account on gitlab.isc.org. If you'd like to receive fewer emails, you can unsubscribe https://gitlab.isc.org/-/sent_notifications/REDACTED/unsubscribe from this thread or adjust your notification settings.
Regarding the logging config -> Kea logs in /var/log/kea-dhcp4.log. The default values of Kea logging for logsize and version to maintain are set. However we push the logs to Elasticsearch using fluent-bit. Approximately it came to 49GB/day since the logging level at Debug.
Thanks. I will give this a try and let you know.
We did collect around Gbs of log, but during this duration we didn't see any error message in kea logs. In fact the logging was sparse during this period. The logs looked as if nothing was wrong. Will try to get the logs for the duration we faced the issue.
Hi Razvan Becheriu,
Thanks for your reply. Will take a look at it more closely. But as far as I know, the postgres doesn't have any cleanup jobs. Any specific thing we can check to know if some cleanup has taken place? Is there any kea dhcp logs that we can search for?
@tomek Can you please guide us on this. We are consistently hitting this issue. Given it happens only on every 8th day with given set of parameters, can you tell us what might be causing this issue.
Hi All, We are running performance tests for kea dhcp using the perf-dhcp provided by kea .
Attaching our config for kea-dhcp4.conf and kea-dhcp-ddns.confkea-dhcp4.confkea-dhcp-ddns.conf