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

Bucket notification- The connection file as of now doesnot check the connectivity as soon as the notification executes it empties the folder #8608

Open
ramya-c3 opened this issue Dec 18, 2024 · 1 comment
Labels

Comments

@ramya-c3
Copy link

Environment info

  • NooBaa Version: 4.18
  • Platform: standalone

Actual behavior

1.Even though the connection is not successful the log file gets emptied on execution of notification executable.

NOTIFICATION_LOG_DIR; /usr/local/noobaa-core/node/bin/node /usr/local/noobaa-core/src/cmd/manage_nsfs.js notification

Expected behavior

1.It should wait till the connection is restored before emtying the directory

Steps to reproduce

More information - Screenshots / Logs / Other output

@ramya-c3 ramya-c3 added the NS-FS label Dec 18, 2024
@alphaprinz
Copy link
Contributor

This is not the behaviour I'm seeing.
When notificator is ran while external server is done, failed notifications are re-written in the NOTIFICATION_LOG_DIR.
Note that notification log filename is different.
Once external server is up (and notificator is re-ran), all failed notification will be sent.

If you're seeing a different behaviour please detail the scenario, provide logs and content of the NOTIFICATION_LOG_DIR before and after relevant steps.

As a side note, the specified command mentions NOTIFICATION_LOG_DIR, but does not set it.
You need to either set in the command, eg
NOTIFICATION_LOG_DIR=/path/to/dir /usr/local/noobaa-core/node/bin/node /usr/local/noobaa-core/src/cmd/manage_nsfs.js notification
or set the NOTIFICATION_LOG_DIR in the config file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants