Multicast - Could not compete tasking
-
@Wayne-Workman what does ftp errors have to do with multicast?
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@Tom-Elliott after the ftp issue was fixed, @cyrmoon had an issue at the end of multicast. That’s how we got on this topic.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
Daily Clean Installation Results:
https://fogtesting.fogproject.us/
FOG Reporting:
https://fog-external-reporting-results.fogproject.us/ -
@Wayne-Workman then how about we move the multicast stuff to its own thread and solve this one? It will help minimize confusion. The way I read this currently the problem the thread was working with is broken.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@Tom-Elliott forked. @cyrmoon we are in this thread now.
-
Sorry about sounding rude, that was not my intention at all. Yes, it should be it’s own thread as it is completely it’s own issue. I am working on fixing this though.
-
@cyrmoon So the task finishes now and removes it from the DB and the hosts reboot properly, just they’re showing up as cancelled now, correct?
-
Added code that should properly complete a tasking. Please let me know if all is better now.
Thanks,
-
Anything?
-
Calling out for @cyrmoon again! Any news on this? As well moving this to the problem section as I am pretty sure this is not a bug…
-
@Developers @Moderators
I messaged him in chat and ping’d him here in the thread.I’m thinking that forking threads isn’t good because people may bookmark the original thread they posted in. He might have came back to the original thread via a bookmark and seen that all his new posts were just gone…
I think that locking threads is a better option once the issue is solved, or we have looser customs about people addressing their next issue in their original thread. With the forums searching functionality, it may not be such a bad idea to just let folks keep going in the original thread. Also, another option is after forking, leave a link behind for them to find where the fork went to. Maybe that should be a feature in nodeBB? Auto-link to the fork, and maybe even send an email to the individual who’s posts were forked? Maybe even auto-message them too with the link and a short message of what happened.
