Sorry in advance for the wall of text but I hope it will answer any initial information you usually need to ask for.
The particulars: OS: Debian Bookworm, latest packages Bacula Version: 15.0.2 from Bacula community PPA Bacularis: 3.2.1 from bacularis PPA installed locally Bacularis Alt: bacularis docker container from hub.docker.com latest version 4.3.0 WebServer: nginx 1.22.1 - bookworm/main PPA FPM: 2:8.2 bookworm/main PPA Postgres: 15.0.2 from Bacula community PPA I have an issue with Bacularis but it happens in two different versions so I can't tell if its a bacularis issue or nginx/php-fpm. This has been driving me insane and google searches return nothing relevant. I've been trying to troubleshoot this myself for months and I'm out of ideas. Bacularis is properly configured to use my bacula backend, all other bacularis functions both from 3.2.1 local and 4.3.0 docker work fine. This has to be something local to my setup as I have to believe if it happened to others it would have been solved already. I did try searching the mailing list archive but I may not be using the correct terms to search for, mostly I get back Microsoft Windows Client issues of which this is not. Problem/How to Reproduce (for me anyway): To create a new job I start with addding/configuring both FileSet and JobDefs section through Bacularis, usually by copying the settings from a different job, however this issue still happens if creating a job from scratch and not copying anything from another job. The creation of a new FileSet and new JobDefs (Pools too) works fine. When I get to the point of creating a new Job no matter what I do when I try to add the fileset through the Bacularis pull down menu the job creation window shrinks/collapses so that you can only see the title bar, the title bar stays regular size it doesn't shrink/collapse. There is no way to resize it again, you no longer can see any buttons or configuration options, you just can't do anything. Even trying different orders of adding the configuration options to the Job, even adding the FileSet choice as the last step, once you get to add the fileset through the bacularis add fileset menu drop down the window collapses to just the title bar of the window. This is the only function have found that causes this issue. I will gladly provide screenshots if the mailing list will allow. I don't expect anyone to be able to replicate this issue, it seems too odd for it to be something common without it being a known bug of some sort. Troubleshooting steps already taken: 1. Try different version of Bacula - upgraded both bacula and postgres from 13.x.x to 15.0.2 using the community PPA and the upgrade scripts in /opt/bacula/scripts. All other functions appear to be working fine, I can do all other tasks without issue from creating filesets, pools, jobdefs, add/remove hardware etc etc. All existing jobs are both backing up and restoring as expected. 2. Tried different version of Bacularis, 3.2.1 is installed locally from the community PPA, I also installed the dockerhub container version of Bacularis 4.3.0 but the issue persists. 3. Checked all file permissions in /opt/bacula and /etc/bacularis, all appear to be normal, all other functions work as expected. bacula-dir.conf gets updated fine with new filesets, pools, jobdefs but I am unable to save any new jobs because the window collapses preventing you from hitting "Save". 4. Scrapped the entire upgraded instance and installed 15.0.2 from scratch, except for the database, that is still upgraded from 13.x.x. Sadly I no longer have the 13.x.x version or even if I did, there are many jobs that I would lose reverting. This issue didn't manifest for me until several months after the db upgrade as I hadn't needed to add any jobs prior to that. 5. Log analysis of bacula logs: show nothing but normal operations, no errors at all 6. Log analysis of nginx: access.log shows normal operations, error.log is empty zero byte file, the perms are correct, nginx can write to it. 7. php-fpm logs - have not tried, need to be activated - will try if helpful but I would think if it was php-fpm the container version from dockerhub would rule that out. 8. systemd journal/syslog show no errors. 9. Tried multiple different browsers: Firefox (current), Chrome (current), Microsoft Edge (current) - each using both normal and incognito modes 10. Tried from several different computers using either Linux or Windows, including one laptop/OS that was fresh from the store. I do not have a MacBook to try. 11. Adding job manually to bacula-dir.conf - works as expected however this is not sustainable. This leads me to believe that bacula itself is working as expected and that the issue is either somehow related to my environment (which I changed to test) or nginx/php-fpm/bacularis. 12. The one other step I have not tried would be to test another webserver, apache or lighttpd. I'm willing to try this but I had hoped using the docker container would rule out any issues locally with nginx/php-fpm as those containers are independently created. 13. Double checked all Web/API configurations, all "Test" buttons all report green and good. I have no reason to suspect any misconfiguration between bacula and Web/API but I don't exactly know what to look for either. 14. I tried examining the content of bacula-dir.conf to look for any extra characters, uncommented junk, whatever trying to see if there was some sort of a parsing error when creating a new job but I didn't think anything looked out of place. I can provide a copy but I would need to sanitize it first. All other functions work as expected so I didn't think it was a configuration issue. My window collapsing issue happens prior to hitting "Save" as it prevents you from hitting "Save" so I didn't think it was a conf type error. I believe I have tried everything I could think of prior to contacting this mailing list so if anyone knows something else to try, another log to analyze, whatever, I'll try to do it. The one thing I can't do is replace the database but I suppose I could create a totally unique instance with a brand new fresh database if that will narrow the focus somehow. All other functions that would utilize the database appear to be working as expected, jobs are backed up, I can view all the job histories, I can restore from jobs, I can see all the pools/tapes, bconsole has no trouble viewing any of the data that should be from the database. It's just this one stupid window in bacularis that I need to use that refuses to play ball. Thank you in advance for any suggestions you might have. Again, sorry for the wall of text but I'm frustrated and this is driving me nuts.
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
