Bareos 17.2.4 Restore via WebUI "Oops, something went wrong, probably too many files."

[AndyPL]

Hi,

After the backup I wanted to browse the contents of the directory from the WebUI level but I get the message "Oops, something went wrong, probably too many files."
I am using the latest version of UI from the repo for Debian 9

Regards

[Daniel]

Hi,

I saw the error several time on my system, too. I use Ubuntu Server 16.04 and bareos 17.2.4. But the restore seems to be completed, no files are missing. So I think it es only a problem with showing the files in WebUI.

[Dakota Pilot]

On Monday, February 5, 2018 at 8:54:46 AM UTC-5, Daniel wrote:
> Hi,
>
> I saw the error several time on my system, too. I use Ubuntu Server 16.04 and bareos 17.2.4. But the restore seems to be completed, no files are missing. So I think it es only a problem with showing the files in WebUI.

I've seen it in the last several versions. I added my comments to a bug on it but have heard nothing.

[Jens Köhler]

Hey guys,

we are having the same issue with two separate Bareos 17.2.4 servers. One is a fresh install, the other one has been upgraded from 16.2.4 to 17.2.4. The error occurs as soon as we want to display the content of a bigger directory in the file selection tree. Bigger means the folder contains more than like 100 files or so. That's annoying considering you have a really big directory of which you can't see the content so you are forced to restore the whole thing in case of emergency.

-

Additionally I didn't expect to always get a restore of the whole directory if I mark just one file in it to be restored. Did you experience that aswell? Or is it normal behaviour and I'm missing something?


-----Ursprüngliche Nachricht-----
Von: bareos...@googlegroups.com [mailto:bareos...@googlegroups.com] Im Auftrag von Dakota Pilot
Gesendet: Mittwoch, 14. Februar 2018 22:38
An: bareos-users
Betreff: [bareos-users] Re: Bareos 17.2.4 Restore via WebUI "Oops, something went wrong, probably too many files."

--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
To post to this group, send email to bareos...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jörg Steffens]

About what Ticket you are talking?
https://bugs.bareos.org/view.php?id=887 ? I think, the issues should be
fixed by now (in the source code).



--
Jörg Steffens joerg.s...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221 630693-91
http://www.bareos.com Fax: +49 221 630693-10

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer:
S. Dühr, M. Außendorf, Jörg Steffens, P. Storz

[Dakota Pilot]

This is the report I added a comment to. https://bugs.bareos.org/view.php?id=803. As of 17.2.4 the webui simply spins and errors out with "maybe too many files". The 887 issue says it will eventually show the files but takes a very, very long time. I and the reporter of 803 never get any files listed. If 17.2.5 is released I can upgrade and see what happens.

[aeron...@gmail.com]

I also reported the issue of not being able to display in bug
https://bugs.bareos.org/view.php?id=891

It is slightly different as I do not get a long spinner. within a few
seconds it displays whatever it is going to.

Also notice that it works better on my Linux machines that on my windows
machine.

Also notice that one of my directories is over 11,000 files in multiple
sub directories but I have others that are just a few files (less that
10) that will not display.

Also Jens, If I mark one file I only get that file for restore.

Also I have tried a restore using bconsole, and it worked correctly on
offending directory.

After the initial response I have heard nothing.

bee

[Jens Köhler]

Hi,

just in case someone still struggles with the "Oops, something went wrong, probably too many files" issue when trying to open directories with a lot of files or some really big files in Bareos Webui Restore tree, this commit fixes the problem, atleast for me:

https://github.com/bareos/bareos-webui/commit/ee232a6f04eaf2a7c1084fee981f011ede000e8a

Thanks to fbergkemper

-----Ursprüngliche Nachricht-----
Von: bareos...@googlegroups.com [mailto:bareos...@googlegroups.com] Im Auftrag von Jens Köhler
Gesendet: Donnerstag, 15. Februar 2018 07:55
An: bareos-users
Betreff: AW: [bareos-users] Re: Bareos 17.2.4 Restore via WebUI "Oops, something went wrong, probably too many files."

Hey guys,

we are having the same issue with two separate Bareos 17.2.4 servers. One is a fresh install, the other one has been upgraded from 16.2.4 to 17.2.4. The error occurs as soon as we want to display the content of a bigger directory in the file selection tree. Bigger means the folder contains more than like 100 files or so. That's annoying considering you have a really big directory of which you can't see the content so you are forced to restore the whole thing in case of emergency.

-

Additionally I didn't expect to always get a restore of the whole directory if I mark just one file in it to be restored. Did you experience that aswell? Or is it normal behaviour and I'm missing something?


-----Ursprüngliche Nachricht-----
Von: bareos...@googlegroups.com [mailto:bareos...@googlegroups.com] Im Auftrag von Dakota Pilot
Gesendet: Mittwoch, 14. Februar 2018 22:38
An: bareos-users
Betreff: [bareos-users] Re: Bareos 17.2.4 Restore via WebUI "Oops, something went wrong, probably too many files."

On Monday, February 5, 2018 at 8:54:46 AM UTC-5, Daniel wrote:
> Hi,
>
> I saw the error several time on my system, too. I use Ubuntu Server 16.04 and bareos 17.2.4. But the restore seems to be completed, no files are missing. So I think it es only a problem with showing the files in WebUI.

I've seen it in the last several versions. I added my comments to a bug on it but have heard nothing.

[Frank Bergkemper]

Hi,

Am 23.02.2018 um 12:55 schrieb Jens Köhler:
> Hi,
>
> just in case someone still struggles with the "Oops, something went wrong, probably too many files" issue when trying to open directories with a lot of files or some really big files in Bareos Webui Restore tree, this commit fixes the problem, atleast for me:
>
> https://github.com/bareos/bareos-webui/commit/ee232a6f04eaf2a7c1084fee981f011ede000e8a
>
> Thanks to fbergkemper
>
> -----Ursprüngliche Nachricht-----
> Von: bareos...@googlegroups.com [mailto:bareos...@googlegroups.com] Im Auftrag von Jens Köhler
> Gesendet: Donnerstag, 15. Februar 2018 07:55
> An: bareos-users
> Betreff: AW: [bareos-users] Re: Bareos 17.2.4 Restore via WebUI "Oops, something went wrong, probably too many files."
>
> Hey guys,
>
> we are having the same issue with two separate Bareos 17.2.4 servers. One is a fresh install, the other one has been upgraded from 16.2.4 to 17.2.4. The error occurs as soon as we want to display the content of a bigger directory in the file selection tree. Bigger means the folder contains more than like 100 files or so. That's annoying considering you have a really big directory of which you can't see the content so you are forced to restore the whole thing in case of emergency.
>
> -
>
> Additionally I didn't expect to always get a restore of the whole directory if I mark just one file in it to be restored. Did you experience that aswell? Or is it normal behaviour and I'm missing something?
>

I do have a question regarding the restore of a whole directory instead
of just the selected file.

What type of OS and DB is in use in that case?

>
> -----Ursprüngliche Nachricht-----
> Von: bareos...@googlegroups.com [mailto:bareos...@googlegroups.com] Im Auftrag von Dakota Pilot
> Gesendet: Mittwoch, 14. Februar 2018 22:38
> An: bareos-users
> Betreff: [bareos-users] Re: Bareos 17.2.4 Restore via WebUI "Oops, something went wrong, probably too many files."
>
> On Monday, February 5, 2018 at 8:54:46 AM UTC-5, Daniel wrote:
>> Hi,
>>
>> I saw the error several time on my system, too. I use Ubuntu Server 16.04 and bareos 17.2.4. But the restore seems to be completed, no files are missing. So I think it es only a problem with showing the files in WebUI.
>
> I've seen it in the last several versions. I added my comments to a bug on it but have heard nothing.
>

Cheers
Frank

--
Frank Bergkemper frank.be...@bareos.com
Bareos GmbH & Co. KG Phone: +49-221-630693-94
http://www.bareos.com

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH

Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz

[Jens Köhler]

Hello Frank,

we noticed it on two independent servers with CentOS 7 and MariaDB (MySQL).

Same issue (## PB2): https://groups.google.com/forum/#!topic/bareos-users/MiAzxqhUVx8


-----Ursprüngliche Nachricht-----
Von: bareos...@googlegroups.com [mailto:bareos...@googlegroups.com] Im Auftrag von Frank Bergkemper
Gesendet: Freitag, 23. Februar 2018 16:40
An: bareos...@googlegroups.com
Betreff: Re: [bareos-users] Re: Bareos 17.2.4 Restore via WebUI "Oops, something went wrong, probably too many files."

[Dakota Pilot]

Unfortunately, it did not work here on 17.2.4. After a very, very long time it gave me the oops error.

[Jens Köhler]

If I understand things correctly, this should help: https://github.com/bareos/bareos-webui/commit/a562e5fee9adc19ebdec86c4f75f9ee6bd7f5d86

-----Ursprüngliche Nachricht-----
Von: bareos...@googlegroups.com [mailto:bareos...@googlegroups.com] Im Auftrag von Dakota Pilot

Gesendet: Sonntag, 25. Februar 2018 05:12
An: bareos-users
Betreff: Re: [bareos-users] Re: Bareos 17.2.4 Restore via WebUI "Oops, something went wrong, probably too many files."

[Dakota Pilot]

That helped some. I can now get the list of directories and their files and move into them in the tree. Sometimes it hangs and won't open a directory giving me the oops error but then if I go back and click again it works.

I just replaced (after saving the originals) my files with the two from Github.

[aeron...@gmail.com]

I found a solution to my problem of Web-ui not displaying directories and files.
I submitted to bareos bug tracker on bug 0000891.
Hopefully the Bareos team will consider the possible fix.

have a good day.

[Frank Bergkemper]

Bugreport 891 was related to 893, which already has been fixed. The
missing relation between those is now set in our bugtracker, thanks anyways.

https://bugs.bareos.org/view.php?id=891
https://bugs.bareos.org/view.php?id=893