Empty log files

Hi @syzygist
Can you see log files in BackWPUp Log file folder section? ( BackWPUp -> Settings -> Log file folder )
I means, using a file manager plugin or FTP access to see files inside Log file folder path

Yes. I downloaded the most recent one and checked it. It’s the same as the logs I’m receiving by email, headers only, i.e., all of the lines beginning with [INFO], but nothing below that.

Log level is showing as Normal in the header and Normal (translated) – which I assume means human readable – in the settings.

@syzygist
weird,
please go to BackWPUp -> Settings -> Logs -> Logging Level -> Debug(not translated ),re-run the job and check the latest log file again.
Can you see the log?

Yes, it looks like a full log when set to Debug (not translated).

So after I did this, I set it back to Normal (translated) and ran it again – empty log file again. I tried viewing the log while the job was running, and it looked like nothing was writing to it.

Then I set the logging to Normal (not translated) and backed up again. That gave the same result as Normal (translated) – [INFO] header lines only, no log content.

I thought I might as well round out the experiment by running it with a Debug (translated) log. This produced a log that looked a lot like the Debug (not translated) log, so I switched the setting back to Debug (not translated) in case I had chosen the wrong debug setting the first time, and ran it one last time. This produced the same log I got the first time, so I guess there is no difference between Debug (translated) and Debug (not translated)?

Don’t know whether this helps, but we reviewed emailed log files and determined that the last normal log was on 9/27/17. On the next backup, 10/4/17, we saw the first empty log. I note that there was an update from vs. 3.4.1 to 3.4.2 during that interval.

Hi @syzygist
So you can see the full log after set BWP logging level to debug?

Yes.

@syzygist
Could you check your server log or give it in here?
Is there any error in your server log?

No, no errors in the server log for the past week.

@syzygist
So I think maybe your wp-config has disabled debug mode,
could you please add these line to the wp-config.php file to see if WordPress throws any error?
Edit your wp-config.php, before /* That's all, stop editing! Happy blogging. */
Add this line
define( 'WP_DEBUG_LOG', true );
After that try to run the job again then go to your wp-content folder to see if there are a file named debug.log.
Do you see any error in debug.log ?

I added define( 'WP_DEBUG_LOG', true ); to wp-config and ran the backup job, but there was no debug.log in wp-content. Then I tried changing define('WP_DEBUG', false); to define('WP_DEBUG', true); and ran the job again, but still no debug log.

Hi @syzygist
it’s really weird, never get this problem before.
Could you please try to uninstall BackWPUp and after that, reinstall it again to see if this problem got fixed?
Thanks!
If not, I really don’t know what happens ??

If I uninstall, will I lose my backup files, log files, or jobs I have already set up?

@syzygist
You will lose your jobs settings, all backup files and log files will not be intact ??

So I will lose the backups and logs as well?

@syzygist
of course, NOOOO ??
you won’t lost the backups and logs ??