Hi John,
Yeahh that's annoying. Haystack logs this for User objects because Django
doesn't have a field that's updated whenever profile data updates. I'd love
to fix this, but the workarounds are.. unclean.
While not ideal, as it could mask other issues, you could always try
redirecting stderr to /dev/null:
rb-site manage .... 2>/dev/null
That should at the very least keep those errors out of your logs. You can
redirect stdout as well, if you need to.
Glad you were able to get the upgrade working, given the age and messy
install. Review Board should be able to upgrade straight from 1.6.9 to
3.0.15 without installing intermediate releases, but I gather you hit some
issues that prevented that from working?
Christian
On Mon, Jul 22, 2019 at 1:07 PM john h <bike.gm...@gmail.com> wrote:
> Hi all,
>
> I recently upgraded a ReviewBoard install from Ubuntu 14.04/RB 1.6.9 to
> 18.04/3.0.15. I did it by advancing through each final minor release of
> RB with pip (starting with 1.7.xx, since that was the earliest available
> via pip), and running rb-site upgrade and recommended commands/edits. RB
> was messily/incompletely installed, and I had to remove/reinstall
> /usr/local/python2.7/dist-packages to clean up the dependency mess in
> there. More details if needed-- it was fairly messy, and I'm a little
> unsure the site is 100% clean at this point, but it appears to be Mostly
> Working.
>
> Search functionality had never been enabled or installed in crontab. I
> did that (using Whoosh, our site seems fairly small at 6000 review requests
> over a decade), but now I'm getting the following error from sudo -u
> www-data "/usr/bin/python" "/usr/local/bin/rb-site" manage "/var/www/
> mercury-reviewboard.pct.niksun.com" update_index -- -a 1:
>
> WARNING:py.warnings:/usr/local/lib/python2.7/dist-packages/haystack/indexes.py:167:
> UserWarning: No updated date field found for 'User' - not restricting by
> age.
> warnings.warn(update_field_msg)
>
> Indexing 82 users
> Indexing 0 Review Requests
>
> My first try at indexing had this all running as root, so I removed the
> data/search-index directory, reran everything as the www-data user RB is
> running as, and the error persists. How might I clear this error? TOO
> MUCH MAIL FROM ROOT :)
>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "Review Board Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/reviewboard/4248b707-3179-431a-a8e7-d9bd43c09cf0%40googlegroups.com
> <https://groups.google.com/d/msgid/reviewboard/4248b707-3179-431a-a8e7-d9bd43c09cf0%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
Christian Hammond
President/CEO of Beanbag <https://www.beanbaginc.com/>
Makers of Review Board <https://www.reviewboard.org/>
--
Supercharge your Review Board with Power Pack:
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons:
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
---
You received this message because you are subscribed to the Google Groups
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/reviewboard/CAE7Vndk0j-YuUNL17sETB%2BuKZu2XrNBAm0nK9G9xc54js9OcZg%40mail.gmail.com.
