juju status
...
ceph-osd/0 active idle 0 192.168.3.46 Unit is ready (1 OSD)
ceph-osd/1* active idle 1 192.168.3.57 Unit is ready (1 OSD)
ceph-osd/2 blocked idle 2 192.168.3.30 No block devices detected using current configuration
...
debug-log --replay --include ceph-osd/2
unit-ceph-osd-1: 17:22:02 INFO unit.ceph-osd/2.juju-log Updating status.
unit-ceph-osd-1: 17:22:02 INFO juju.worker.uniter.operation ran "update-status" hook (via explicit, bespoke hook script)
I scrolled back and cant's see any other messages. Logs from working unit look the same:
debug-log --replay --include ceph-osd/1
unit-ceph-osd-1: 17:27:59 INFO unit.ceph-osd/1.juju-log Updating status.
unit-ceph-osd-1: 17:28:00 INFO juju.worker.uniter.operation ran "update-status" hook (via explicit, bespoke hook script)
ceph-mon/1 is the leader
juju debug-log --replay --include ceph-mon/1
unit-ceph-mon-1: 17:27:29 WARNING unit.ceph-mon/1.juju-log 0 containers are present in metadata.yaml and refresh_event was not specified. Defaulting to update_status. Metrics IP may not be set in a timely fashion.
unit-ceph-mon-1: 17:27:29 INFO unit.ceph-mon/1.juju-log Updating status
unit-ceph-mon-1: 17:27:29 INFO unit.ceph-mon/1.juju-log Status updated
unit-ceph-mon-1: 17:27:30 INFO unit.ceph-mon/1.juju-log Updating status
unit-ceph-mon-1: 17:27:30 INFO unit.ceph-mon/1.juju-log Status updated
unit-ceph-mon-1: 17:27:30 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
scrolling back does not reveal any other messages.
I think this is because it's been a few days since I've rebooted the machine 2 and juju logs seem to go back <24h.
I'll try rebooting another machine and see if any other messages show up and report back.
I've never used sosreports before. I see it's available on ubuntu. Do you recommend any specific options I should use? Should I attach the results to the bug or upload somewhere else (where?) and post links? Do you need sosreports from one unit of each application or from all of them?
juju status
...
ceph-osd/0 active idle 0 192.168.3.46 Unit is ready (1 OSD)
ceph-osd/1* active idle 1 192.168.3.57 Unit is ready (1 OSD)
ceph-osd/2 blocked idle 2 192.168.3.30 No block devices detected using current configuration
...
debug-log --replay --include ceph-osd/2 osd/2.juju- log Updating status. uniter. operation ran "update-status" hook (via explicit, bespoke hook script)
unit-ceph-osd-1: 17:22:02 INFO unit.ceph-
unit-ceph-osd-1: 17:22:02 INFO juju.worker.
I scrolled back and cant's see any other messages. Logs from working unit look the same:
debug-log --replay --include ceph-osd/1 osd/1.juju- log Updating status. uniter. operation ran "update-status" hook (via explicit, bespoke hook script)
unit-ceph-osd-1: 17:27:59 INFO unit.ceph-
unit-ceph-osd-1: 17:28:00 INFO juju.worker.
ceph-mon/1 is the leader
juju debug-log --replay --include ceph-mon/1 mon/1.juju- log 0 containers are present in metadata.yaml and refresh_event was not specified. Defaulting to update_status. Metrics IP may not be set in a timely fashion. mon/1.juju- log Updating status mon/1.juju- log Status updated mon/1.juju- log Updating status mon/1.juju- log Status updated uniter. operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-ceph-mon-1: 17:27:29 WARNING unit.ceph-
unit-ceph-mon-1: 17:27:29 INFO unit.ceph-
unit-ceph-mon-1: 17:27:29 INFO unit.ceph-
unit-ceph-mon-1: 17:27:30 INFO unit.ceph-
unit-ceph-mon-1: 17:27:30 INFO unit.ceph-
unit-ceph-mon-1: 17:27:30 INFO juju.worker.
scrolling back does not reveal any other messages.
I think this is because it's been a few days since I've rebooted the machine 2 and juju logs seem to go back <24h.
I'll try rebooting another machine and see if any other messages show up and report back.
I've never used sosreports before. I see it's available on ubuntu. Do you recommend any specific options I should use? Should I attach the results to the bug or upload somewhere else (where?) and post links? Do you need sosreports from one unit of each application or from all of them?