Skip to content
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

Successful Backup not writing to Eventlog since latest update #3492

Closed
irstmon opened this issue Nov 13, 2018 · 3 comments
Closed

Successful Backup not writing to Eventlog since latest update #3492

irstmon opened this issue Nov 13, 2018 · 3 comments
Labels
pending user feedback needs information from the original poster

Comments

@irstmon
Copy link

irstmon commented Nov 13, 2018

Hi,

Since the upgrade to "2.0.4.1_experimental_2018-11-08" duplicati now logs to eventlog that it has send the email (1339) - but before there was an event that I could check with nagios: "Duplicati Backup erfolgreich" (1338). Since the email entry does not reflect wether the backup was successful or not - is there any chance to get 1338 back again?

Thanks!

@ts678
Copy link
Collaborator

ts678 commented Jan 16, 2024

I downloaded source code for 2.0.4.1_experimental_2018-11-08 but could find nothing that is mentioning 1339 or 1338.
EventLog Class seems to be how .NET Framework writes to the Windows event log, and you can see examples currently in
https://github.com/duplicati/duplicati/blob/master/Duplicati/WindowsService/ServiceControl.cs
I'm not sure what Event ID is made if it's not explicitly given (as is so here), but I find no WriteEntry elsewhere in 2.0.4.1.
Do you happen to have an old sample event around, in the chance it gives further clues? Is this issue even still of interest?

Note that you can use a run-script-after to study the backup results and do whatever you like, using tools you can obtain.

@ts678 ts678 added the pending user feedback needs information from the original poster label Jan 16, 2024
@irstmon
Copy link
Author

irstmon commented Jan 16, 2024

I don't have an old sample anymore since eventlogs have rolled over since then multiple times and even the computers are not existent anymore. For me it's no longer important since I've since switched to not using duplicati.

Thanks anyway for taking a look at this - and sorry for not closing it

@ts678
Copy link
Collaborator

ts678 commented Jan 16, 2024

Thanks for the reply. Closing issue now.

@ts678 ts678 closed this as completed Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending user feedback needs information from the original poster
Projects
None yet
Development

No branches or pull requests

2 participants