Mark Murawski wrote at about 11:46:24 -0500 on Monday, November 14, 2022: > > On 11/3/22 14:41, backu...@kosowsky.org wrote: > > Mark Murawski wrote at about 14:29:44 -0400 on Thursday, November 3, 2022: > > > Hi Christopher, > > > > > > Thanks for the kind response. > > > > > > I found the possibly culprit log entry that I attached to this thread > > > just earlier. > > > 2022-11-03 08:08:49 Can't run BackupPC_zipCreate while BackupPC_dump > > > is running on host xyz > > > > You think???? Log seems pretty clear. > > Might be a good idea to look at the logs *before* bothering us with > > likely phantom bugs. > > Can you define how this situation is a "phantom bug". I pretty > clearly explained the lack of feedback from the UI when this condition > occurs and you get sent a zero byte zip file with no explanation.
The logs were clear -- this is Enterprise software and when something doesn't work, one is expected to check the logs (as well as doing other basic troubleshooting homework). If backups or restores don't work -- for whatever reason -- the first thing to do is check the logs!!! (how many times do I have to say that???) This is not child-proof Windows consumer software where the UI is expected to do everything and spoon-feed all the answers. The GUI is only there to help with basic tasks -- indeed the GUI itself is mostly focused on making it easier for users to change config parameters and launch backups/restores -- it is not meant to be idiot-proof or a substitute for logs. Indeed, many users (myself included) never even use the GUI since the CLI is much more powerful and accessible. As such, there is not a huge ongoing investment being made in adding more bells and whistles (unless an individual user -- hint you -- contributes code). The fact that the UI doesn't pop up a nice shiny, themed dialog box explaining why your restore failed is NOT a BUG. At most, it's a feature request to include more debugging info directly in the GUI -- and you are welcome to submit code that provides such messaging. That being said, the GUI did undoubtedly signal an error -- just not in a pop-up. Had you looked under "Restore Summary", you would have seen presumably that your restore had no files or no data. The top status text may also have noted something. I can assure you that there are many, many even more egregious or alternatively subtle ways for backups (or restores) to fail in part or in full and there is no nice shiny GUI that signals many such errors. That's why you need to check and test backups as well as restores -- if there are issues, then... drumbeat... check the logs! > Again... unneeded hostility. Not hostility -- just reaction to: 1. Laziness -- you made all types of claims and request for help before doing even minimal troubleshooting yourself 2. Calling "BUG" multiple times just because you didn't get the notification in the way you wanted. At most this is a "Feature Request" for more direct error messages for those who don't want to trouble themselves to look in the logs or even on the status page. Personally, though, I think adding more error messages will only give a false sense of security leading users to think that their backups and restores are intact just so long as they don't have error messages. Given the large number of ways in which backups and restores can fail subtly, this would only give a false sense of security. > Check your attitude at home. Pot-kettle. If you want help: (1) Be polite (2) Do your homework (3) Don't expect free tech support to compensate for your laziness (4) Don't call things bugs until you have verified that they are indeed bugs (5) Drop the entitled attitude and implication that others should be writing better error notification code to suit your specific needs > Why are you doing your best to push new people away? Because you still don't seem to get that your approach has been rude and lazy from the get-go. I am happy to encourage users who are respectful of other peoples time, who are willing to learn a little and at least read the FAQ before asking for help, and who are potentially willing to even give back. BTW, you clearly don't seem to use much FOSS, especially Enterprise-level. I wish I had a nickel for every time I encountered so-called "attitude" when I would jump in as a newbie asking on some Forum, for help without doing any prep work and without giving even the most major of relevant background info. _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/