View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000852bareos-corewebuipublic2017-09-11 15:192021-08-30 13:01
ReporterRyushin Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionunable to reproduce 
PlatformLinuxOSDebianOS Version8
Product Version17.2.3 
Summary0000852: Bareos-WebUI Cannot Display Volume Page With 1680 voulmes After Bug Fix 719
DescriptionThere seems to be two problems. I have 1680 Volumes on this one installation (I have two other installations that are similar).

PHP Max Memory needs to be massively increased otherwise it runs out of of memory. I initially had 256M and I had to increase the PHP5 value to 3072M to stop receiving out of memory errors.

First error with 256M: Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 2 bytes) in /usr/share/bareos-webui/vendor/zendframework/zend-json/src/Json.php on line 58

Second error with 1024M: Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 72 bytes) in /usr/share/bareos-webui/module/Media/src/Media/Model/MediaModel.php on line 55

After increasing the memory to 3072M, the next error is Maximum Execution Time is encountered. Increasing it from 30 to 300 seconds still does not result in a page being displayed.
Fatal error: Maximum execution time of 30 seconds exceeded in /usr/share/bareos-webui/module/Media/src/Media/Model/MediaModel.php on line 55

Also this last update had BAT being uninstalled which I figured was because the database schema was updated and BAT was being deprecated anyway.
Steps To ReproduceHave a lot of volumes and try to view Storages, Volumes page.
TagsNo tags attached.

Activities

frank

frank

2017-09-13 13:29

developer   ~0002735

There is a pending commit waiting for review which introduces limit and offset arguments for the list volumes command webui will make use of in future.
frank

frank

2021-08-05 12:52

developer   ~0004201

There were numerous fixes since this report has been opened, please let us know if the problem still persists after updating to one of our latest maintained versions 20.x, 19.x or 18.x.
frank

frank

2021-08-30 13:01

developer   ~0004237

This bug report is being closed due to inactivity.

Please reopen or create a new report if you still encounter this issue.

Thank you!

Issue History

Date Modified Username Field Change
2017-09-11 15:19 Ryushin New Issue
2017-09-12 12:10 frank Assigned To => frank
2017-09-12 12:10 frank Status new => assigned
2017-09-13 13:29 frank Note Added: 0002735
2021-08-05 12:52 frank Status assigned => feedback
2021-08-05 12:52 frank Note Added: 0004201
2021-08-30 13:01 frank Assigned To frank =>
2021-08-30 13:01 frank Status feedback => closed
2021-08-30 13:01 frank Resolution open => unable to reproduce
2021-08-30 13:01 frank Note Added: 0004237