New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression: Problem with GBAK -V and -Y parameter checking [CORE3995] #4327
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: @ibaseru complains how? on what Linux? btw, this is not support list, but I can't resist to comment your backup options: and, if you don't want backup to do garbage collection, and run faster - specify -B -G. If you want to discuss it, send a message to firebird-support list. |
Commented by: Ivan Arabadzhiev (intelrullz) LinuxFromScratch (in case it actually matters) My complain is simple : gbak:creating file stdout I believe it should not happen when I have already specified a -Y (and thus redirected the verbose output), unless there has been some major change in 2.5.2 which makes it a problem to execute such a backup. Am I missing something? Because I have restored 2.5.1/2.1.* backups made this way and they have never been corrupt. As for used parameters : |
Modified by: @AlexPeshkoff |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 Alpha 1 [ 10331 ] Fix Version: 2.5.3 [ 10461 ] |
Commented by: PizzaProgram Ltd. (szakilaci) As mentioned in a "duplicate" issue: CORE4009 I've just experienced it, as I've tried to move from 2.1.5 to 2.5.2 version. My program failed to make backups. And it's not good, if NOTHING happens in the command line window. This function worked perfectly in 2.1 version !!! see: CORE762?focusedCommentId=26272&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_26272 My customers are not programmers. If they see "something running" in a black window for 3 minutes, they wait patiently like a sheep, but if it's just empty and waiting > they try to force-close. And still.. the big question is > WHY isn't this message just shown, and the verbosity rather just ignored AS long this error isn't fixed, it's still better, than missing a scheduled backup, just because someone upgraded a database on one of the 1000 machines ! I really had liked to change from 2.1, but I still have to stay by it. :( |
Commented by: @AlexPeshkoff Laszlo, did you pay attention that an assue is resolved? That means that you may use snapshot builds or wait for 2.5.3. |
Commented by: PizzaProgram Ltd. (szakilaci) Just tested 2.5.3 snapshot. Verbose still not working. 1. gbak -B -T -V ......................... is NOT ignored nor showing any verbose messages on screen but drops an error and backup is FAILED !!! IMHO this tracker should be re-opened, or a new one should be created pointing to this one. |
Modified by: @AlexPeshkoffstatus: Resolved [ 5 ] => Reopened [ 4 ] resolution: Fixed [ 1 ] => Fix Version: 3.0 Alpha 1 [ 10331 ] => Fix Version: 2.5.3 [ 10461 ] => |
Commented by: @AlexPeshkoff Hi Laszlo p.2 & p.4 are working, looks like only p.1 to be fixed. |
Commented by: PizzaProgram Ltd. (szakilaci) As I've mentioned, "3." is nothing, just a workaround test. Tried to redirect messages from file to the consol. You can forget about it. The important thing is: ... or at least temporary: 1/b: ignore it and let the backup run ! MANY THANKS ! PS: personaly it would be enough for me, if verbose message would be only: a "percentage line" 0.001% ..0.002% ... updating every 500ms in the same line, if that's quicker to do. Whatever easier to you ! (IMHO restoring how it was at 2.1 would be best.) |
Commented by: @AlexPeshkoff Restored original behavior when gbak is used in 'stdout' mode as utility. |
Modified by: @AlexPeshkoffstatus: Reopened [ 4 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 Alpha 1 [ 10331 ] Fix Version: 2.5.3 [ 10461 ] |
Commented by: PizzaProgram Ltd. (szakilaci) Tested. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: Sean Leyne (seanleyne)summary: Slight problem with GBAK parameter checking => Regression: Problem with GBAK -V and -Y parameter checking |
Modified by: Sean Leyne (seanleyne)issuetype: Improvement [ 4 ] => Bug [ 1 ] |
Submitted by: Ivan Arabadzhiev (intelrullz)
Is duplicated by CORE4009
Votes: 3
Up to Fb 2.5.1 I had the following crontask running to backup without a temporary file
/opt/firebird/bin/gbak -IG -E -USER $USERNAME -PASSWORD $PASSWORD -V -Y $BACKUP_NAME.log -T -B /storage/fb_db/aton/aton.fdb stdout | /usr/bin/pbzip2 -3 -cp3z - > $BACKUP_NAME.fbk.bz2
I recently upgraded to 2.5.2, which complains about verbose output and stdout at the same time. The check makes sense but I have already redirected the log to another file. Is there anyway the next version will take that into account? I`d prefer to have it out there just in case and I don`t really need the temporary file.
Commits: 7e8a1d1 538dc8c 4c3978e c1a4759
The text was updated successfully, but these errors were encountered: