#9274 Fedora planet gives many tracebacks and errors and not working
Closed: Fixed 7 months ago by pingou. Opened 7 months ago by smooge.

Describe what you would like us to do:

The fedora planet is currently not updating. The errors for this have been masked by sending all the output to /dev/null due to the number of 404 and 500 errors being listed. However there are multiple AMQP errors too.

I don't know why things are broken and have to head to a datacenter for work so am putting in a general ticket for others to debug

When do you need this to be done by? (YYYY/MM/DD)

This looks related to/caused by the fedora-messaging switch.

The venus package was updated, but it needs:

  • certs generated and installed
  • a user / queue setup in rabbitmq
  • playbook adjustments to do the above.

I can try and do it, but if someone else would like to, fine with me. ;)

Metadata Update from @mohanboddu:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: medium-gain, medium-trouble, ops

7 months ago

I added the cert/user/config, I see now:

ERROR:planet.runner:TypeError: time.struct_time(tm_year=2020, tm_mon=8, tm_mday=25, tm_hour=15, tm_min=41, tm_sec=46, tm_wday=1, tm_yday=238, tm_isdst=0) is not JSON serializable
ERROR:planet.runner:  File "/usr/lib/python2.7/site-packages/planet/spider.py", line 506, in spiderPlanet
    writeCache(uri, feed_info, data)
ERROR:planet.runner:  File "/usr/lib/python2.7/site-packages/planet/spider.py", line 243, in writeCache
    "post": entry,
ERROR:planet.runner:  File "/usr/lib/python2.7/site-packages/fedora_messaging/api.py", line 246, in publish
    _session_cache.session.publish(message, exchange=exchange)
ERROR:planet.runner:  File "/usr/lib/python2.7/site-packages/fedora_messaging/_session.py", line 152, in publish
    self._connect_and_publish(exchange, message)
ERROR:planet.runner:  File "/usr/lib/python2.7/site-packages/fedora_messaging/_session.py", line 193, in _connect_and_publish
ERROR:planet.runner:  File "/usr/lib/python2.7/site-packages/fedora_messaging/message.py", line 499, in _encoded_body
    return json.dumps(self.body).encode("utf-8")
ERROR:planet.runner:  File "/usr/lib64/python2.7/json/__init__.py", line 243, in dumps
    return _default_encoder.encode(obj)
ERROR:planet.runner:  File "/usr/lib64/python2.7/json/encoder.py", line 207, in encode
    chunks = self.iterencode(o, _one_shot=True)
ERROR:planet.runner:  File "/usr/lib64/python2.7/json/encoder.py", line 270, in iterencode
    return _iterencode(o, 0)
ERROR:planet.runner:  File "/usr/lib64/python2.7/json/encoder.py", line 184, in default
    raise TypeError(repr(o) + " is not JSON serializable")

So, I think it's finding new posts now, but something is wrong in the venus patch for sending them?

cc @zlopez 

Metadata Update from @pingou:
- Issue untagged with: ops
- Issue tagged with: dev

7 months ago

Metadata Update from @pingou:
- Issue assigned to pingou

7 months ago

Good news, I've found the fix https://apps.fedoraproject.org/datagrepper/raw?rows_per_page=1&delta=127800&category=planet :)

Now we "just" need to get it into the RPM again and update it on people02

I'm going to close this one in favor of https://pagure.io/fedora-infrastructure/issue/8462 which will track the remaining work.

Thanks @kevin for taking care of the user/queue/certificates!

Metadata Update from @pingou:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

7 months ago

Login to comment on this ticket.

Boards 1
dev Status: Done