-
Notifications
You must be signed in to change notification settings - Fork 38
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
ns doesn't exist. #39
Comments
I'll take a look |
…), plus add a Prune Stalled button on the Running Jobs page
May have fixed it in the PR, but I'll have to check it later...signing off for now. |
Please check if the issue is fixed in 4.1.0 |
@Siba94 did the fix I did work? |
checking it right now. i'll let you know about it. |
No, still have the same issue. |
@Siba94 - Oh I know what's going on - the database and collection don't exist yet in Mongo. If you create then run a job, it should fix that, however I should see if there's a way to catch that before executing the count command. |
Thanks a lot. @mmucklo |
@Siba94 could you verify now against release 4.2.0? |
@mmucklo Let me check. I will update you. |
@Siba94 Ok, thanks, let me know... |
@mmucklo still have the same issue. I had a job collection also as mentioned by you before running the count command create job first but when I run the count command it still generates the same exception. |
Ok, let me check it out. |
I think I got it this time in 4.3.1 - yours is responding "ns doesn't exist" whereas mine was responding "namespace does not exist". The code should now catch both. Let me know, --Matt |
@Siba94 - did 4.3.1 fix the issue for you? |
@mmucklo let me check it |
@Siba94 - ok thanks once again... |
Thanks a lot @mmucklo it's working perfectly. |
@Siba94 - good news thanks. Closing the issue. |
I am using 4.0 version of this bundle and whenever I run console command dtc:queue:count, it gives me a exception -> ns doesn't exist.
The text was updated successfully, but these errors were encountered: