text:
Python agent is missing sessions

The integration tests are showing that the python agent is missing sessions. The symptom is that detecting the filesystem will hang indefinitely.
https://build.whamcloud.com/view/IML/job/manager-for-lustre/510/execution/node/50/log/
10:22:39  May 14 14:22:37 DEBUG iml_cmd: Running cmd: Command { std: "/usr/bin/iml" "filesystem" "detect", kill_on_drop: false }

A few other details here:
From the job scheduler:
[2020-05-14 14:09:47,768: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: c1.local/226f1032-d6e4-42ea-a886-8babd0f7a209
[2020-05-14 14:09:47,768: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: c1.local/226f1032-d6e4-42ea-a886-8babd0f7a209
[2020-05-14 14:09:47,768: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session 226f1032-d6e4-42ea-a886-8babd0f7a209 because
[2020-05-14 14:09:47,768: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session 226f1032-d6e4-42ea-a886-8babd0f7a209 because
[2020-05-14 14:09:57,753: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/a62f3387-98e8-4cc5-b92b-15d650f8f81b
[2020-05-14 14:09:57,753: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/a62f3387-98e8-4cc5-b92b-15d650f8f81b
[2020-05-14 14:09:57,753: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session a62f3387-98e8-4cc5-b92b-15d650f8f81b because
[2020-05-14 14:09:57,753: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session a62f3387-98e8-4cc5-b92b-15d650f8f81b because
[2020-05-14 14:10:17,751: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds2.local/4d532d52-2c48-4c85-83c4-a6a9e0cd1a37
[2020-05-14 14:10:17,751: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds2.local/4d532d52-2c48-4c85-83c4-a6a9e0cd1a37
[2020-05-14 14:10:17,752: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session 4d532d52-2c48-4c85-83c4-a6a9e0cd1a37 because
[2020-05-14 14:10:17,752: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session 4d532d52-2c48-4c85-83c4-a6a9e0cd1a37 because
[2020-05-14 14:10:27,734: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss1.local/208daef6-7309-4665-b470-12137a82f8c0
[2020-05-14 14:10:27,734: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss1.local/208daef6-7309-4665-b470-12137a82f8c0
[2020-05-14 14:10:27,735: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session 208daef6-7309-4665-b470-12137a82f8c0 because
[2020-05-14 14:10:27,735: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session 208daef6-7309-4665-b470-12137a82f8c0 because
[2020-05-14 14:10:47,758: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds1.local/3283dadc-0a93-464c-852e-11611d7ec914
[2020-05-14 14:10:47,758: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds1.local/3283dadc-0a93-464c-852e-11611d7ec914
[2020-05-14 14:10:47,758: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session 3283dadc-0a93-464c-852e-11611d7ec914 because
[2020-05-14 14:10:47,758: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session 3283dadc-0a93-464c-852e-11611d7ec914 because
[2020-05-14 14:12:26,445: INFO/job_scheduler] _notify: Updating .boot_time of item 4 (mds1.local) from 2020-05-14 13:56:17+00:00 to 2020-05-14 14:12:04+00:00
[2020-05-14 14:12:26,445: INFO/job_scheduler] _notify: Set boot_time=2020-05-14 14:12:04+00:00 on mds1.local (ManagedHost-4) and saved
[2020-05-14 14:12:26,451: INFO/job_scheduler] run_next: 0 runnable jobs of (0 pending, 0 tasked)
[2020-05-14 14:12:26,498: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds1.local/0b2575a1-562c-476a-aff1-dce5860e1379
[2020-05-14 14:12:26,498: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds1.local/0b2575a1-562c-476a-aff1-dce5860e1379
[2020-05-14 14:12:54,945: INFO/job_scheduler] _notify: Updating .boot_time of item 5 (mds2.local) from 2020-05-14 13:56:46+00:00 to 2020-05-14 14:12:40+00:00
[2020-05-14 14:12:54,945: INFO/job_scheduler] _notify: Set boot_time=2020-05-14 14:12:40+00:00 on mds2.local (ManagedHost-5) and saved
[2020-05-14 14:12:54,951: INFO/job_scheduler] run_next: 0 runnable jobs of (0 pending, 0 tasked)
[2020-05-14 14:12:55,019: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds2.local/c65c1334-f0ab-4e2d-b6af-124f991ae4b0
[2020-05-14 14:12:55,019: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds2.local/c65c1334-f0ab-4e2d-b6af-124f991ae4b0
[2020-05-14 14:13:54,214: INFO/job_scheduler] _notify: Updating .boot_time of item 1 (oss1.local) from 2020-05-14 13:57:23+00:00 to 2020-05-14 14:13:12+00:00
[2020-05-14 14:13:54,214: INFO/job_scheduler] _notify: Set boot_time=2020-05-14 14:13:12+00:00 on oss1.local (ManagedHost-1) and saved
[2020-05-14 14:13:54,217: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss1.local/44e7267e-b1c2-4de5-aa25-12fe8083da1d
[2020-05-14 14:13:54,217: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss1.local/44e7267e-b1c2-4de5-aa25-12fe8083da1d
[2020-05-14 14:13:54,221: INFO/job_scheduler] run_next: 0 runnable jobs of (0 pending, 0 tasked)
[2020-05-14 14:14:05,324: INFO/job] AlertState: Raised <class 'chroma_core.models.command.CommandRunningAlert'> on Command object at severity 20
[2020-05-14 14:14:05,325: INFO/command_plan] add_jobs: done checking dependencies
[2020-05-14 14:14:05,335: INFO/command_plan] add_jobs: created Job 29 (Trigger plugin poll for linux plugins)
[2020-05-14 14:14:05,387: INFO/job_scheduler] run_next: 1 runnable jobs of (1 pending, 0 tasked)
[2020-05-14 14:14:05,392: INFO/job_scheduler] Job 29: RunJobThread.run
[2020-05-14 14:14:05,392: INFO/job] invoke_agent on agent oss2.local trigger_plugin_update {'plugin_names': [u'linux']}
[2020-05-14 14:14:05,392: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 30 seconds remain
[2020-05-14 14:14:05,392: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 30 seconds remain
[2020-05-14 14:14:06,394: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 29 seconds remain
[2020-05-14 14:14:06,394: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 29 seconds remain
[2020-05-14 14:14:07,395: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 28 seconds remain
[2020-05-14 14:14:07,395: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 28 seconds remain
[2020-05-14 14:14:08,396: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 27 seconds remain
[2020-05-14 14:14:08,396: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 27 seconds remain
[2020-05-14 14:14:09,398: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 26 seconds remain
[2020-05-14 14:14:09,398: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 26 seconds remain
[2020-05-14 14:14:10,399: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 25 seconds remain
[2020-05-14 14:14:10,399: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 25 seconds remain
[2020-05-14 14:14:11,400: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 24 seconds remain
[2020-05-14 14:14:11,400: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 24 seconds remain
[2020-05-14 14:14:12,401: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 23 seconds remain
[2020-05-14 14:14:12,401: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 23 seconds remain
[2020-05-14 14:14:13,402: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 22 seconds remain
[2020-05-14 14:14:13,402: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 22 seconds remain
[2020-05-14 14:14:14,404: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 21 seconds remain
[2020-05-14 14:14:14,404: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 21 seconds remain
[2020-05-14 14:14:15,405: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 20 seconds remain
[2020-05-14 14:14:15,405: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 20 seconds remain
[2020-05-14 14:14:16,406: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 19 seconds remain
[2020-05-14 14:14:16,406: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 19 seconds remain
[2020-05-14 14:14:17,408: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 18 seconds remain
[2020-05-14 14:14:17,408: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 18 seconds remain
[2020-05-14 14:14:18,409: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 17 seconds remain
[2020-05-14 14:14:18,409: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 17 seconds remain
[2020-05-14 14:14:19,410: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 16 seconds remain
[2020-05-14 14:14:19,410: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 16 seconds remain
[2020-05-14 14:14:20,411: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 15 seconds remain
[2020-05-14 14:14:20,411: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 15 seconds remain
[2020-05-14 14:14:21,413: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 14 seconds remain
[2020-05-14 14:14:21,413: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 14 seconds remain
[2020-05-14 14:14:22,414: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 13 seconds remain
[2020-05-14 14:14:22,414: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 13 seconds remain
[2020-05-14 14:14:23,415: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 12 seconds remain
[2020-05-14 14:14:23,415: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 12 seconds remain
[2020-05-14 14:14:24,416: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 11 seconds remain
[2020-05-14 14:14:24,416: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 11 seconds remain
[2020-05-14 14:14:25,418: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 10 seconds remain
[2020-05-14 14:14:25,418: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 10 seconds remain
[2020-05-14 14:14:26,419: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 9 seconds remain
[2020-05-14 14:14:26,419: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 9 seconds remain
[2020-05-14 14:14:27,420: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 8 seconds remain
[2020-05-14 14:14:27,420: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 8 seconds remain
[2020-05-14 14:14:28,421: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 7 seconds remain
[2020-05-14 14:14:28,421: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 7 seconds remain
[2020-05-14 14:14:29,422: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 6 seconds remain
[2020-05-14 14:14:29,422: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 6 seconds remain
[2020-05-14 14:14:30,423: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 5 seconds remain
[2020-05-14 14:14:30,423: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 5 seconds remain
[2020-05-14 14:14:31,425: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 4 seconds remain
[2020-05-14 14:14:31,425: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 4 seconds remain
[2020-05-14 14:14:32,426: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 3 seconds remain
[2020-05-14 14:14:32,426: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._send: no session yet for oss2.local, 3 seconds remain
[2020-05-14 14:14:32,550: INFO/job_scheduler] _notify: Updating .boot_time of item 2 (oss2.local) from 2020-05-14 13:57:54+00:00 to 2020-05-14 14:14:12+00:00
[2020-05-14 14:14:32,550: INFO/job_scheduler] _notify: Set boot_time=2020-05-14 14:14:12+00:00 on oss2.local (ManagedHost-2) and saved
[2020-05-14 14:14:32,556: INFO/job_scheduler] run_next: 0 runnable jobs of (0 pending, 1 tasked)
[2020-05-14 14:14:32,707: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/fb094d04-d303-4de8-b015-1099d8d2047e
[2020-05-14 14:14:32,707: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/fb094d04-d303-4de8-b015-1099d8d2047e
[2020-05-14 14:14:33,439: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc 41e9a08a-e2e4-4851-80e9-9c8527b4cb0c
[2020-05-14 14:14:33,439: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc 41e9a08a-e2e4-4851-80e9-9c8527b4cb0c
[2020-05-14 14:14:58,165: INFO/job_scheduler] _notify: Updating .boot_time of item 3 (c1.local) from 2020-05-14 13:58:31+00:00 to 2020-05-14 14:14:42+00:00
[2020-05-14 14:14:58,165: INFO/job_scheduler] _notify: Set boot_time=2020-05-14 14:14:42+00:00 on c1.local (ManagedHost-3) and saved
[2020-05-14 14:14:58,171: INFO/job_scheduler] run_next: 0 runnable jobs of (0 pending, 1 tasked)
[2020-05-14 14:14:58,221: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: c1.local/038d4640-3bf1-4437-89ca-c8c4a42a91e5
[2020-05-14 14:14:58,221: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: c1.local/038d4640-3bf1-4437-89ca-c8c4a42a91e5
[2020-05-14 14:15:33,418: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/fb094d04-d303-4de8-b015-1099d8d2047e
[2020-05-14 14:15:33,418: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/fb094d04-d303-4de8-b015-1099d8d2047e
[2020-05-14 14:15:33,418: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session fb094d04-d303-4de8-b015-1099d8d2047e because
[2020-05-14 14:15:33,418: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session fb094d04-d303-4de8-b015-1099d8d2047e because
[2020-05-14 14:15:33,419: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/9d102869-d4b5-4295-8528-423cc504be71
[2020-05-14 14:15:33,419: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/9d102869-d4b5-4295-8528-423cc504be71
[2020-05-14 14:15:33,444: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc 41e9a08a-e2e4-4851-80e9-9c8527b4cb0c
[2020-05-14 14:15:33,444: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc 41e9a08a-e2e4-4851-80e9-9c8527b4cb0c
[2020-05-14 14:15:33,445: ERROR/job_scheduler] Job 29 step 0 encountered an agent error: Communications error with oss2.local because session terminated
[2020-05-14 14:15:33,470: INFO/job_scheduler] Job 29: complete_job: Updating cache
[2020-05-14 14:15:33,470: INFO/job_scheduler] Job 29 completing (errored=True, cancelled=False)
[2020-05-14 14:15:33,492: INFO/job_scheduler] run_next: 0 runnable jobs of (0 pending, 0 tasked)
[2020-05-14 14:15:37,766: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/9d102869-d4b5-4295-8528-423cc504be71
[2020-05-14 14:15:37,766: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/9d102869-d4b5-4295-8528-423cc504be71
[2020-05-14 14:15:37,766: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session 9d102869-d4b5-4295-8528-423cc504be71 because
[2020-05-14 14:15:37,766: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session 9d102869-d4b5-4295-8528-423cc504be71 because
[2020-05-14 14:15:43,554: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/1f7ea883-120f-476a-b15e-0ac6171a998a
[2020-05-14 14:15:43,554: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/1f7ea883-120f-476a-b15e-0ac6171a998a
[2020-05-14 14:18:18,799: INFO/job_scheduler] _notify: Updating .boot_time of item 4 (mds1.local) from 2020-05-14 14:12:04+00:00 to 2020-05-14 14:17:58+00:00
[2020-05-14 14:18:18,799: INFO/job_scheduler] _notify: Set boot_time=2020-05-14 14:17:58+00:00 on mds1.local (ManagedHost-4) and saved
[2020-05-14 14:18:18,805: INFO/job_scheduler] run_next: 0 runnable jobs of (0 pending, 0 tasked)
[2020-05-14 14:18:18,870: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds1.local/0b2575a1-562c-476a-aff1-dce5860e1379
[2020-05-14 14:18:18,870: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds1.local/0b2575a1-562c-476a-aff1-dce5860e1379
[2020-05-14 14:18:18,870: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session 0b2575a1-562c-476a-aff1-dce5860e1379 because
[2020-05-14 14:18:18,870: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session 0b2575a1-562c-476a-aff1-dce5860e1379 because
[2020-05-14 14:18:18,872: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds1.local/5dcb137a-304b-4f52-b9ca-35294dc2eb53
[2020-05-14 14:18:18,872: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds1.local/5dcb137a-304b-4f52-b9ca-35294dc2eb53
[2020-05-14 14:18:55,586: INFO/job_scheduler] _notify: Updating .boot_time of item 5 (mds2.local) from 2020-05-14 14:12:40+00:00 to 2020-05-14 14:18:34+00:00
[2020-05-14 14:18:55,586: INFO/job_scheduler] _notify: Set boot_time=2020-05-14 14:18:34+00:00 on mds2.local (ManagedHost-5) and saved
[2020-05-14 14:18:55,592: INFO/job_scheduler] run_next: 0 runnable jobs of (0 pending, 0 tasked)
[2020-05-14 14:18:55,802: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds2.local/c65c1334-f0ab-4e2d-b6af-124f991ae4b0
[2020-05-14 14:18:55,802: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds2.local/c65c1334-f0ab-4e2d-b6af-124f991ae4b0
[2020-05-14 14:18:55,802: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session c65c1334-f0ab-4e2d-b6af-124f991ae4b0 because
[2020-05-14 14:18:55,802: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session c65c1334-f0ab-4e2d-b6af-124f991ae4b0 because
[2020-05-14 14:18:55,804: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds2.local/01119db4-bc2c-41b3-9a92-1466fca27ed7
[2020-05-14 14:18:55,804: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds2.local/01119db4-bc2c-41b3-9a92-1466fca27ed7
[2020-05-14 14:19:40,521: INFO/job_scheduler] _notify: Updating .boot_time of item 1 (oss1.local) from 2020-05-14 14:13:12+00:00 to 2020-05-14 14:19:22+00:00
[2020-05-14 14:19:40,521: INFO/job_scheduler] _notify: Set boot_time=2020-05-14 14:19:22+00:00 on oss1.local (ManagedHost-1) and saved
[2020-05-14 14:19:40,527: INFO/job_scheduler] run_next: 0 runnable jobs of (0 pending, 0 tasked)
[2020-05-14 14:20:41,477: INFO/job_scheduler] _notify: Updating .boot_time of item 2 (oss2.local) from 2020-05-14 14:14:12+00:00 to 2020-05-14 14:20:04+00:00
[2020-05-14 14:20:41,477: INFO/job_scheduler] _notify: Set boot_time=2020-05-14 14:20:04+00:00 on oss2.local (ManagedHost-2) and saved
[2020-05-14 14:20:41,483: INFO/job_scheduler] run_next: 0 runnable jobs of (0 pending, 0 tasked)
[2020-05-14 14:20:41,549: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/1f7ea883-120f-476a-b15e-0ac6171a998a
[2020-05-14 14:20:41,549: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/1f7ea883-120f-476a-b15e-0ac6171a998a
[2020-05-14 14:20:41,549: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session 1f7ea883-120f-476a-b15e-0ac6171a998a because
[2020-05-14 14:20:41,549: WARNING/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: aborting session 1f7ea883-120f-476a-b15e-0ac6171a998a because
[2020-05-14 14:20:41,551: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/5b2809d5-6e07-4962-b691-753e27ac1120
[2020-05-14 14:20:41,551: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/5b2809d5-6e07-4962-b691-753e27ac1120
[2020-05-14 14:20:52,681: INFO/job] AlertState: Raised <class 'chroma_core.models.command.CommandRunningAlert'> on Command object at severity 20
[2020-05-14 14:20:52,683: INFO/command_plan] add_jobs: done checking dependencies
[2020-05-14 14:20:52,695: INFO/command_plan] add_jobs: created Job 30 (Trigger plugin poll for linux plugins)
[2020-05-14 14:20:52,749: INFO/job_scheduler] run_next: 1 runnable jobs of (1 pending, 0 tasked)
[2020-05-14 14:20:52,752: INFO/job_scheduler] Job 30: RunJobThread.run
[2020-05-14 14:20:52,753: INFO/job] invoke_agent on agent oss1.local trigger_plugin_update {'plugin_names': [u'linux']}
[2020-05-14 14:20:52,768: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc e72ce9a0-3aed-4b4c-8de0-5a9b81fd1502
[2020-05-14 14:20:52,768: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc e72ce9a0-3aed-4b4c-8de0-5a9b81fd1502
[2020-05-14 14:22:38,264: INFO/job] AlertState: Raised <class 'chroma_core.models.command.CommandRunningAlert'> on Command object at severity 20
[2020-05-14 14:22:38,266: INFO/command_plan] add_jobs: done checking dependencies
[2020-05-14 14:22:38,274: INFO/command_plan] add_jobs: created Job 31 (Scan for Lustre targets)
[2020-05-14 14:22:38,287: INFO/job_scheduler] run_next: 1 runnable jobs of (1 pending, 1 tasked)
[2020-05-14 14:22:38,291: INFO/job_scheduler] Job 31: RunJobThread.run
[2020-05-14 14:22:38,293: INFO/job] invoke_agent on agent oss1.local device_plugin {'plugin': 'linux_network'}
[2020-05-14 14:22:38,293: INFO/job] invoke_agent on agent oss2.local device_plugin {'plugin': 'linux_network'}
[2020-05-14 14:22:38,301: INFO/job] invoke_agent on agent c1.local device_plugin {'plugin': 'linux_network'}
[2020-05-14 14:22:38,303: INFO/job] invoke_agent on agent mds1.local device_plugin {'plugin': 'linux_network'}
[2020-05-14 14:22:38,306: INFO/job] invoke_agent on agent mds2.local device_plugin {'plugin': 'linux_network'}
[2020-05-14 14:22:38,310: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc b49c4886-d50d-47e7-9788-1d52b6455ae5
[2020-05-14 14:22:38,310: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc b49c4886-d50d-47e7-9788-1d52b6455ae5
[2020-05-14 14:22:38,323: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc 47e20104-1ea6-40f5-a2d9-c7559133df4f
[2020-05-14 14:22:38,323: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc 47e20104-1ea6-40f5-a2d9-c7559133df4f
[2020-05-14 14:22:38,335: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc 71392348-d3f9-48dd-87bf-f368091ef6e8
[2020-05-14 14:22:38,335: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc 71392348-d3f9-48dd-87bf-f368091ef6e8
[2020-05-14 14:22:38,347: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc afe1e536-63ff-479d-9164-4de3c6554d10
[2020-05-14 14:22:38,347: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc afe1e536-63ff-479d-9164-4de3c6554d10
[2020-05-14 14:22:38,359: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc 00478591-78cc-4310-90d4-7040086caa6f
[2020-05-14 14:22:38,359: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc 00478591-78cc-4310-90d4-7040086caa6f
[2020-05-14 14:22:38,413: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: c1.local/038d4640-3bf1-4437-89ca-c8c4a42a91e5
[2020-05-14 14:22:38,413: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: c1.local/038d4640-3bf1-4437-89ca-c8c4a42a91e5
[2020-05-14 14:22:38,413: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session c1.local/038d4640-3bf1-4437-89ca-c8c4a42a91e5
[2020-05-14 14:22:38,413: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session c1.local/038d4640-3bf1-4437-89ca-c8c4a42a91e5
[2020-05-14 14:22:38,414: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc 71392348-d3f9-48dd-87bf-f368091ef6e8
[2020-05-14 14:22:38,414: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc 71392348-d3f9-48dd-87bf-f368091ef6e8
[2020-05-14 14:22:38,460: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc 71392348-d3f9-48dd-87bf-f368091ef6e8
[2020-05-14 14:22:38,460: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc 71392348-d3f9-48dd-87bf-f368091ef6e8
[2020-05-14 14:22:38,461: INFO/job] invoke_agent on agent c1.local device_plugin {'plugin': 'linux'}
[2020-05-14 14:22:38,473: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc f5a51f1a-792a-482a-8b50-8b57b9ee6649
[2020-05-14 14:22:38,473: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc f5a51f1a-792a-482a-8b50-8b57b9ee6649
[2020-05-14 14:22:38,531: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/5b2809d5-6e07-4962-b691-753e27ac1120
[2020-05-14 14:22:38,531: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/5b2809d5-6e07-4962-b691-753e27ac1120
[2020-05-14 14:22:38,531: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session oss2.local/5b2809d5-6e07-4962-b691-753e27ac1120
[2020-05-14 14:22:38,531: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session oss2.local/5b2809d5-6e07-4962-b691-753e27ac1120
[2020-05-14 14:22:38,531: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc afe1e536-63ff-479d-9164-4de3c6554d10
[2020-05-14 14:22:38,531: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc afe1e536-63ff-479d-9164-4de3c6554d10
[2020-05-14 14:22:38,532: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds2.local/01119db4-bc2c-41b3-9a92-1466fca27ed7
[2020-05-14 14:22:38,532: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds2.local/01119db4-bc2c-41b3-9a92-1466fca27ed7
[2020-05-14 14:22:38,532: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session mds2.local/01119db4-bc2c-41b3-9a92-1466fca27ed7
[2020-05-14 14:22:38,532: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session mds2.local/01119db4-bc2c-41b3-9a92-1466fca27ed7
[2020-05-14 14:22:38,533: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc 00478591-78cc-4310-90d4-7040086caa6f
[2020-05-14 14:22:38,533: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc 00478591-78cc-4310-90d4-7040086caa6f
[2020-05-14 14:22:38,534: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: c1.local/038d4640-3bf1-4437-89ca-c8c4a42a91e5
[2020-05-14 14:22:38,534: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: c1.local/038d4640-3bf1-4437-89ca-c8c4a42a91e5
[2020-05-14 14:22:38,534: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session c1.local/038d4640-3bf1-4437-89ca-c8c4a42a91e5
[2020-05-14 14:22:38,534: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session c1.local/038d4640-3bf1-4437-89ca-c8c4a42a91e5
[2020-05-14 14:22:38,534: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc f5a51f1a-792a-482a-8b50-8b57b9ee6649
[2020-05-14 14:22:38,534: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc f5a51f1a-792a-482a-8b50-8b57b9ee6649
[2020-05-14 14:22:38,536: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds1.local/5dcb137a-304b-4f52-b9ca-35294dc2eb53
[2020-05-14 14:22:38,536: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds1.local/5dcb137a-304b-4f52-b9ca-35294dc2eb53
[2020-05-14 14:22:38,536: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session mds1.local/5dcb137a-304b-4f52-b9ca-35294dc2eb53
[2020-05-14 14:22:38,536: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session mds1.local/5dcb137a-304b-4f52-b9ca-35294dc2eb53
[2020-05-14 14:22:38,536: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc 47e20104-1ea6-40f5-a2d9-c7559133df4f
[2020-05-14 14:22:38,536: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc 47e20104-1ea6-40f5-a2d9-c7559133df4f
[2020-05-14 14:22:38,537: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc f5a51f1a-792a-482a-8b50-8b57b9ee6649
[2020-05-14 14:22:38,537: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc f5a51f1a-792a-482a-8b50-8b57b9ee6649
[2020-05-14 14:22:38,552: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc 47e20104-1ea6-40f5-a2d9-c7559133df4f
[2020-05-14 14:22:38,552: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc 47e20104-1ea6-40f5-a2d9-c7559133df4f
[2020-05-14 14:22:38,553: INFO/job] invoke_agent on agent mds1.local device_plugin {'plugin': 'linux'}
[2020-05-14 14:22:38,565: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc 3c0e4bee-34d3-4074-b350-277da539e36f
[2020-05-14 14:22:38,565: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc 3c0e4bee-34d3-4074-b350-277da539e36f
[2020-05-14 14:22:38,568: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc afe1e536-63ff-479d-9164-4de3c6554d10
[2020-05-14 14:22:38,568: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc afe1e536-63ff-479d-9164-4de3c6554d10
[2020-05-14 14:22:38,569: INFO/job] invoke_agent on agent oss2.local device_plugin {'plugin': 'linux'}
[2020-05-14 14:22:38,575: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc 00478591-78cc-4310-90d4-7040086caa6f
[2020-05-14 14:22:38,575: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc 00478591-78cc-4310-90d4-7040086caa6f
[2020-05-14 14:22:38,576: INFO/job] invoke_agent on agent mds2.local device_plugin {'plugin': 'linux'}
[2020-05-14 14:22:38,581: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc adb19756-8ee7-4985-90d4-fcfea8c85123
[2020-05-14 14:22:38,581: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc adb19756-8ee7-4985-90d4-fcfea8c85123
[2020-05-14 14:22:38,592: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc 5e9741d6-26ea-4ff9-b0c0-389b05231b20
[2020-05-14 14:22:38,592: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: starting wait for rpc 5e9741d6-26ea-4ff9-b0c0-389b05231b20
[2020-05-14 14:22:38,653: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds1.local/5dcb137a-304b-4f52-b9ca-35294dc2eb53
[2020-05-14 14:22:38,653: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds1.local/5dcb137a-304b-4f52-b9ca-35294dc2eb53
[2020-05-14 14:22:38,654: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session mds1.local/5dcb137a-304b-4f52-b9ca-35294dc2eb53
[2020-05-14 14:22:38,654: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session mds1.local/5dcb137a-304b-4f52-b9ca-35294dc2eb53
[2020-05-14 14:22:38,654: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc 3c0e4bee-34d3-4074-b350-277da539e36f
[2020-05-14 14:22:38,654: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc 3c0e4bee-34d3-4074-b350-277da539e36f
[2020-05-14 14:22:38,655: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/5b2809d5-6e07-4962-b691-753e27ac1120
[2020-05-14 14:22:38,655: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: oss2.local/5b2809d5-6e07-4962-b691-753e27ac1120
[2020-05-14 14:22:38,655: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session oss2.local/5b2809d5-6e07-4962-b691-753e27ac1120
[2020-05-14 14:22:38,655: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session oss2.local/5b2809d5-6e07-4962-b691-753e27ac1120
[2020-05-14 14:22:38,655: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc adb19756-8ee7-4985-90d4-fcfea8c85123
[2020-05-14 14:22:38,655: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc adb19756-8ee7-4985-90d4-fcfea8c85123
[2020-05-14 14:22:38,660: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds2.local/01119db4-bc2c-41b3-9a92-1466fca27ed7
[2020-05-14 14:22:38,660: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: mds2.local/01119db4-bc2c-41b3-9a92-1466fca27ed7
[2020-05-14 14:22:38,660: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session mds2.local/01119db4-bc2c-41b3-9a92-1466fca27ed7
[2020-05-14 14:22:38,660: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: good session mds2.local/01119db4-bc2c-41b3-9a92-1466fca27ed7
[2020-05-14 14:22:38,660: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc 5e9741d6-26ea-4ff9-b0c0-389b05231b20
[2020-05-14 14:22:38,660: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger.on_rx: completing rpc 5e9741d6-26ea-4ff9-b0c0-389b05231b20
[2020-05-14 14:22:38,688: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc 3c0e4bee-34d3-4074-b350-277da539e36f
[2020-05-14 14:22:38,688: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc 3c0e4bee-34d3-4074-b350-277da539e36f
[2020-05-14 14:22:38,701: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc adb19756-8ee7-4985-90d4-fcfea8c85123
[2020-05-14 14:22:38,701: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc adb19756-8ee7-4985-90d4-fcfea8c85123
[2020-05-14 14:22:38,708: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc 5e9741d6-26ea-4ff9-b0c0-389b05231b20
[2020-05-14 14:22:38,708: INFO/chroma_core.services.job_scheduler.agent_rpc] AgentRpcMessenger._complete: completed wait for rpc 5e9741d6-26ea-4ff9-b0c0-389b05231b20

Here's interesting to me in the output above is that the rpc for oss1 at the end never completes, but I don't think the call is hanging on this rpc specifically. Further investigation into OSS1 reveals an unknown session that takes place in Job 29:
[14/May/2020:14:22:38] daemon WARNING Received a message for unknown session action_runner/44e7267e-b1c2-4de5-aa25-12fe8083da1d

Futhermore, I'm seeing the following error:
[2020-05-14 14:15:33,445: ERROR/job_scheduler] Job 29 step 0 encountered an agent error: Communications error with oss2.local because session terminated
[2020-05-14 14:15:33,470: INFO/job_scheduler] Job 29: complete_job: Updating cache
[2020-05-14 14:15:33,470: INFO/job_scheduler] Job 29 completing (errored=True, cancelled=False)
[2020-05-14 14:15:33,492: INFO/job_scheduler] run_next: 0 runnable jobs of (0 pending, 0 tasked)

This message can be traced back to https://github.com/whamcloud/integrated-manager-for-lustre/blob/master/chroma_core/services/job_scheduler/agent_rpc.py#L148. I haven't been able to prove this out yet but my theory is that when it encounters this error it seems to leave any other sessions hanging; in this case, the session for oss1. Because this session hangs, another job executes and runs on oss1 but because it's already hung up this rpc will never finish.

source: gharchive/issue

repo: whamcloud/integrated-manager-for-lustre

license: MIT

license_type: permissive

license_source: github-api


text:
Feature: Use a native way to provide jsdom globally

Brief description
No response
Freeform description field
No response

The jsdom library lacks a native solution for this task. Users have the option to create a file, perhaps named setup-file.js or similar, but this requires additional effort. The decision has been made to persist with using the jsdom-global package to address this issue.


text:
players stats returns empty stats for specific date

I have been trying to fetch some players' stats at a given date from last season, and it returns '-' for all the stats, excluding small amount of players which receive the true stats. is there a problem with yahoo's api?

can you share the sport, player, and date in question?
you could also try entering the information here https://yahoo-fantasy-node-docs.vercel.app/resource/player/stats which is basically a raw implementation of the library so it might point to whether there's something wrong in your code or this library.

I have verified it their too, for example looking for NBA, players id 5317, on the 2023-10-25.

What is the game key you are using? I see the data for 428.p.5317
My guess is you're using nba.p.5317?

Indeed that was the problem, thank you

It's frustrating. When you're using the "current" season, you can default to the league key (nba, mlb, nhl), but if you're using a past season you need to use the game key for THAT season to get stats from that year.
Glad it's sorted :)

authors: tanierell whatadewitt

repo: whatadewitt/yahoo-fantasy-sports-api


text:
Only count text characters towards length

Fixes #26 and  #27

Nice, great catch! Thanks @Huluk 💟

source: gharchive/pull-request

authors: Huluk whatyouhide

repo: whatyouhide/vim-lengthmatters

license: WTFPL


text:
PATCH requests not supported?

Getting the following error TypeError: _fetchMock2.default.patch is not a function when attempting to:
fetchMock.patch('some-link', {})

Does the fetch-mock api support mocking PATCH requests?

read the docs https://github.com/wheresrhys/fetch-mock/blob/master/README.md#head

authors: christian-schulze wheresrhys

repo: wheresrhys/fetch-mock

license: mit

license_source: bigquery


text:
isSupported does not work for anything other than NDEF on iOS

seems like isSupported never got updated on iOS from v1.
IsoDep is returning false for isSupported, even though it is supported
Code below shows we are only checking for Ndef or a blank string
RCT_EXPORT_METHOD(isSupported: (NSString *)tech callback:(nonnull RCTResponseSenderBlock)callback)
{
    if (isSupported()) {
        // iOS only supports Ndef starting from iOS 11.0 (on iPhone 7 onwards)
        if ([tech isEqualToString:@""] || [tech isEqualToString:@"Ndef"]) {
            callback(@[[NSNull null], @YES]);
            return;
        }
    }

    callback(@[[NSNull null], @NO]);
}

@thecalvinchan thanks for reporting, this should be fixed in next release.

Fixed in latest v2.0.2, thanks!


text:
Fix META with ocp-build

ocp-build does not handle the += in META file.

I'm pretty sure this needs to be fixed in ocp-build.

Yes, I think :) . I try that today. If you want to close this PRs, it's OK.

Let's wait until it's clear what the ocp-build outcome is.

@dinosaure Was there any progress with ocp-build?

I fixed locally ocp-build, and OCamlPro merged my PR but I don't know when is the next release :( ! So, you can close this PR, I can use my PR instead.

OK, thanks!

authors: dinosaure whitequark


text:
multi_teleop connection issues

I am having troubles connecting to multiple quadrotors using your ROS node. I have been following your comments on the bitcraze blog:
https://www.bitcraze.io/2015/04/towards-crazyswarms-2/
I have downloaded your radio_multi-link python client and my radio and crazyflies have the most up-to-date firmware. I am currently running on ROS hyrdo, but will shortly be upgrading to Indigo, on Ubuntu 12.04.
When I run the mutli_teleop_xbox360 node I get the following errors over and over:
[INFO] [WallTime: 1430944581.092314] Connecting to radio://0/80/2M
[INFO] [WallTime: 1430944581.092744] Connecting to radio://0/72/2M
[FATAL] [WallTime: 1430944581.093472] Connection to radio://0/72/2M failed: Couldn't load link driver: Link already open!
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/cflib/crazyflie/init.py", line 217, in open_link
self._link_error_cb)
File "/usr/local/lib/python2.7/dist-packages/cflib/crtp/init.py", line 90, in get_link_driver
instance.connect(uri, link_quality_callback, link_error_callback)
File "/usr/local/lib/python2.7/dist-packages/cflib/crtp/radiodriver.py", line 110, in connect
raise Exception("Link already open!")
Exception: Link already open!
Thanks!

Hi Andy,
It looks like the ROS package is not picking up my radio_multilink
branch but rather some other installed version (without multi-link)
support. What do you specify as crazyflieSDK? (Either change it in the
launch file or use "roslaunch crazyflie_demo multi_teleop_xbox360.launch
crazyflieSDK:=<path/to/local/version/of/https://github.com/whoenig/crazyflie-clients-python/tree/radio_multilink>"
I hope that helps!
Wolfgang
On 05/06/2015 01:53 PM, Andy wrote:

I am having troubles connecting to multiple quadrotors using your ROS
node. I have been following your comments on the bitcraze blog:
https://www.bitcraze.io/2015/04/towards-crazyswarms-2/
I have downloaded your radio_multi-link python client and my radio and
crazyflies have the most up-to-date firmware. I am currently running
on ROS hyrdo, but will shortly be upgrading to Indigo, on Ubuntu 12.04.
When I run the mutli_teleop_xbox360 node I get the following errors
over and over:
[INFO] [WallTime: 1430944581.092314] Connecting to radio://0/80/2M
[INFO] [WallTime: 1430944581.092744] Connecting to radio://0/72/2M
[FATAL] [WallTime: 1430944581.093472] Connection to radio://0/72/2M
failed: Couldn't load link driver: Link already open!
Traceback (most recent call last):
File
"/usr/local/lib/python2.7/dist-packages/cflib/crazyflie/init.py",
line 217, in open_link
self./link_error_cb)
File "/usr/local/lib/python2.7/dist-packages/cflib/crtp/_init/.py",
line 90, in get_link_driver
instance.connect(uri, link_quality_callback, link_error_callback)
File
"/usr/local/lib/python2.7/dist-packages/cflib/crtp/radiodriver.py",
line 110, in connect
raise Exception("Link already open!")
Exception: Link already open!
Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/whoenig/crazyflie_ros/issues/3.

Hi Wolfgang,
Thanks for the response. Apparently when I pulled your crazyflie python client I forgot to pull from the correct branch.
Thanks for your quick response!
Andy

authors: mechAndy whoenig


text:
Neovim py3eval fix

Fix #203

Waiting to merge until @tomtomjhj opens an issue with neovim so I can link to it. May also want to include a fix for the warning message not being displayed if it isn't too difficult.

repo: whonore/Coqtail


text:
version 0.4.9

Description
bumping version

Pull Request Test Coverage Report for Build 984545336

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.915%

Totals

Change from base Build 980164614:
0.0%

Covered Lines:
3349

Relevant Lines:
4022

💛  - Coveralls

authors: coveralls lalmei

repo: whylabs/whylogs


text:
canvas依赖安装失败，下载的文件不存在！

龙大，你好！
canvas依赖安装失败，看了日志显示下载文件错误，看了官方库里也没有这个版本的文件。

同这个问题，现在解决了吗？

同这个问题，现在解决了吗？

没有，

同这个问题，现在解决了吗？

这个要装在PYTHON3哪里才可以

同这个问题，现在解决了吗？

这个要装在PYTHON3哪里才可以

青龙的docker采用的精简版linux，需要安装编译依赖
apk add build-base g++ cairo-dev jpeg-dev pango-dev giflib-dev

同样的问题

build-base g++ cairo-dev jpeg-dev pango-dev giflib-dev

装了这几个还是安装canvas失败了

最新版本泽呢么都装不上node-canvas

最新版本怎么都装不上node-canvas

同这个问题，现在解决了吗？

这个要装在PYTHON3哪里才可以

青龙的docker采用的镜像为alpine linux，所以安装canvas前需要安装相关的编译依赖
apk add build-base g++ cairo-dev jpeg-dev pango-dev giflib-dev

感谢大佬的方法，已解决！！！

authors: 2604237845 FairyWorld HorrZzz SekiBetu aliyy2021 naiveclub

repo: whyour/qinglong


text:
🛑 Girasol 🇩🇪 (de) is down

In 9f1b7fd, Girasol 🇩🇪 (de) (https://holiday-lescala.com/h/haus-girasol/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Girasol 🇩🇪 (de) is back up in 2a55520 after 28 minutes.

repo: whytspace/upptime-holiday-lescala


text:
Add remote schema support, compile validators & improve logging

Change the topic configuration from an array of strings to an object, with
each topic configured with its own options object.
Support loading of remote schemas by setting the .schema config property to
a URL starting with http:// or https://.
Compile validators for better performance.
Improve startup error logging. This should probably be incorporated into
service-template.

/cc @wikimedia/services @ottomata

repo: wikimedia/restevent


text:
add PT and RU to available languages

Hey @wikiti 👋

add PT and RU to available languages

📖 https://www.deepl.com/api.html#api_reference_article
🗞 https://www.deepl.com/blog/20181205.html

Hey @neumayr!
Thank you for your contribution.
Best regards,
Daniel

authors: neumayr wikiti

repo: wikiti/deepl-rb


text:
[WFCORE-1588] Register runtime attribtes depends on the server type

register runtime attribute in the ConcreteResourceRegistration only when they are
meaningful (for the given ProcessType/RunningMode).
rename attribute's flag to FORCE_REGISTRATION to
RUNTIME_SERVICE_NOT_REQUIRED and update the API in
AttributeDefinitionBuilder
add call to setRuntimeServiceNotRequired() for every attribute definition that
was flagged as storage-runtime but was not depending on runtime
services to handle the attribute.

JIRA: https://issues.jboss.org/browse/WFCORE-1588

I run a recursive resource description of a WildFly domain with wildfly-core master and again with this branch to check that there are no significant changes. The two descriptions can be diffed in this gist: https://gist.github.com/jmesnil/85298beec5cece30a50abc40043db37f/revisions
The changes are located in the messaging-activemq and undertow subsystem:
Changes in the resource description:
* /profile=*/subsystem=messaging-activemq/jms-bridge=*
  * paused
  * started
* /profile=*/subsystem=messaging-activemq/server=*/{acceptor|remote-acceptor|http-acceptor|invm-acceptor}
  * started
* /profile=*/subsystem=messaging-activemq/server=*/bridge=*
  * started
* /profile=*/subsystem=messaging-activemq/server=*/queue=*
  * dead-letter-address
  * expiry-address
  * id
  * paused
  * temporary
* /profile=*/subsystem=messaging-activemq/server=*/core-address=*
  * binding-names
  * number-of-bytes-per-page
  * number-of-pages
  * queue-names
* /profile=*/subsystem=messaging-activemq/server=*/core-address=*/role=*
  * consume
  * create-durable-queue
  * create-non-durable-queue
  * delete-durable-queue
  * delete-non-durable-queue
  * manage
  * send
* /profile=*/subsystem=messaging-activemq/server=*/cluster-connection=*
  * node-id
  * started
  * topology
* /profile=*/subsystem=messaging-activemq/server=*/broadcast-group=*
  * started
* /profile=*/subsystem=messaging-activemq/server=*/runtime-queue=*
  * dead-letter-address
  * durable
  * expiry-address
  * filter
  * id
  * paused
  * queue-address
  * temporary
* /profile=*/subsystem=messaging-activemq/server=*/jms-topic=*
  * temporary
  * topic-address
* /profile=*/subsystem=messaging-activemq/server=*/jms-queue=*
  * dead-letter-address
  * expiry-address
  * paused
  * queue-address
  * temporary
* /profile=*/subsystem=undertow/configuration=filter/mod-cluster=*/balancer=*
  * max-attempts
  * sticky-session
  * sticky-session-force
  * sticky-session-path
  * sticky-session-remove
  * wait-worker
* /profile=*/subsystem=undertow/configuration=filter/mod-cluster=*/balancer=*/node=*
  * aliases
  * cache-connections
  * elected
  * flush-packets
  * load
  * load-balancing-group
  * max-connections
  * open-connections
  * ping
  * queue-new-requests
  * read
  * request-queue-size
  * status
  * timeout
  * ttl
  * uri
  * written
* /profile=*/subsystem=undertow/configuration=filter/mod-cluster=*/balancer=*/node=*/context=*
  * requests
  * status

The changes in the messaging-activemq subsystem are correct (as these attributes requires an Artemis runtime and must not be available in the profiles) and fixes https://issues.jboss.org/browse/WFLY-6690.
The changes in the undertow subsystem looks also correct as these runtime attributes require a modcluster service. They won't fail if the user query them as the code check for the presence of the modcluster service but will return "nothing" when they are invoked in the domain profiles.
However I think it is more correct to remove them from the profile as it makes no sense to have them here.

Linux Build 4029 outcome was FAILURE using a merge of 2da96acfb1f1f5d74cd736240c63d6f9de6931ae
Summary: Tests failed: 3 (3 new), passed: 3630, ignored: 56 Build time: 00:41:02
Failed tests
org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.testComposite:     "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "failure-description" => "WFLYCTL0201: Unknown attribute 'log-file'",
            "rolled-back" => true
        },
        "step-2" => {"outcome" => undefined},
        "step-3" => {"outcome" => undefined}
    },
    "failure-description" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0201: Unknown attribute 'log-file'"}},
    "rolled-back" => true
} expected:<[success]> but was:<[failed]>
	at org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.testComposite(ResponseStreamTestCase.java:218)
------- Stdout: -------
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "failure-description" => "WFLYCTL0201: Unknown attribute 'log-file'",
            "rolled-back" => true
        },
        "step-2" => {"outcome" => undefined},
        "step-3" => {"outcome" => undefined}
    },
    "failure-description" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0201: Unknown attribute 'log-file'"}},
    "rolled-back" => true
}

org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.testMasterHost:     "outcome" => "failed",
    "failure-description" => "WFLYCTL0201: Unknown attribute 'log-file'",
    "rolled-back" => true
} expected:<[success]> but was:<[failed]>
	at org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.readLogFile(ResponseStreamTestCase.java:494)
	at org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.testMasterHost(ResponseStreamTestCase.java:179)
------- Stdout: -------
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0201: Unknown attribute 'log-file'",
    "rolled-back" => true
}

org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.testSlaveHost:     "outcome" => "failed",
    "failure-description" => "WFLYCTL0201: Unknown attribute 'log-file'",
    "rolled-back" => true
} expected:<[success]> but was:<[failed]>
	at org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.readLogFile(ResponseStreamTestCase.java:494)
	at org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.testSlaveHost(ResponseStreamTestCase.java:185)
------- Stdout: -------
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0201: Unknown attribute 'log-file'",
    "rolled-back" => true
}

Windows Build 3402 outcome was FAILURE using a merge of dbb066374a93bb7782c198f82c24a2a342492ba2
Summary: Tests failed: 3 (3 new), passed: 3630, ignored: 56 Build time: 00:49:49
Failed tests
org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.testComposite:     "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "failure-description" => "WFLYCTL0201: Unknown attribute 'log-file'",
            "rolled-back" => true
        },
        "step-2" => {"outcome" => undefined},
        "step-3" => {"outcome" => undefined}
    },
    "failure-description" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0201: Unknown attribute 'log-file'"}},
    "rolled-back" => true
} expected:<[success]> but was:<[failed]>
	at org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.testComposite(ResponseStreamTestCase.java:218)
------- Stdout: -------
{
    "outcome" => "failed",
    "result" => {
        "step-1" => {
            "outcome" => "failed",
            "failure-description" => "WFLYCTL0201: Unknown attribute 'log-file'",
            "rolled-back" => true
        },
        "step-2" => {"outcome" => undefined},
        "step-3" => {"outcome" => undefined}
    },
    "failure-description" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0201: Unknown attribute 'log-file'"}},
    "rolled-back" => true
}

org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.testMasterHost:     "outcome" => "failed",
    "failure-description" => "WFLYCTL0201: Unknown attribute 'log-file'",
    "rolled-back" => true
} expected:<[success]> but was:<[failed]>
	at org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.readLogFile(ResponseStreamTestCase.java:494)
	at org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.testMasterHost(ResponseStreamTestCase.java:179)
------- Stdout: -------
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0201: Unknown attribute 'log-file'",
    "rolled-back" => true
}

org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.testSlaveHost:     "outcome" => "failed",
    "failure-description" => "WFLYCTL0201: Unknown attribute 'log-file'",
    "rolled-back" => true
} expected:<[success]> but was:<[failed]>
	at org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.readLogFile(ResponseStreamTestCase.java:494)
	at org.jboss.as.test.integration.domain.suites.ResponseStreamTestCase.testSlaveHost(ResponseStreamTestCase.java:185)
------- Stdout: -------
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0201: Unknown attribute 'log-file'",
    "rolled-back" => true
}

Full integration - Windows Build 1478 outcome was FAILURE using a merge of dbb066374a93bb7782c198f82c24a2a342492ba2
Summary: Tests failed: 1 (1 new), passed: 3377, ignored: 198 Build time: 01:19:10
Failed tests
org.jboss.as.test.manualmode.security.SecuredDataSourceTestCase.test:  at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:146)
 at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:66)
 at org.jboss.as.test.integration.security.common.servlets.DataSourceTestServlet.doGet(DataSourceTestServlet.java:85)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
 at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
 at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
 at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
 at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
 at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
 at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
 at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
 at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
 at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
 at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
 at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
 at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
 at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
 at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
 at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
 at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
 at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
 at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
 at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:285)
 at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:264)
 at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
 at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:175)
 at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202)
 at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:802)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at java.lang.Thread.run(Thread.java:745)
Caused by: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/SecuredDataSourceTestCase
 at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:656)
 at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:429)
 at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:747)
 at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138)
 ... 31 more
Caused by: javax.resource.ResourceException: IJ031084: Unable to create connection
 at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:345)
 at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:352)
 at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.access$200(LocalManagedConnectionFactory.java:62)
 at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory$1$1.run(LocalManagedConnectionFactory.java:259)
 at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory$1$1.run(LocalManagedConnectionFactory.java:250)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.security.auth.Subject.doAs(Subject.java:422)
 at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory$1.run(LocalManagedConnectionFactory.java:249)
 at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory$1.run(LocalManagedConnectionFactory.java:246)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:245)
 at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1320)

retest this please

authors: jmesnil wildfly-ci

repo: wildfly/wildfly-core


text:
[WFLY-15047] EJB (Un)marshaller resource leak

Fixes https://issues.redhat.com/browse/WFLY-15047

marshaller and unmarshaller have a finish() method that does the cleanup. In fact, its close() method just calls finish(). So adding a call to close() will duplicate what's already done by finish() method for places where finish() is already called. So I think it's better to add a finally clause to make sure finish() is always called for cleanup.

@chengfang I should have checked that :-( I suggest to remove the finish() to avoid the duplication. try-with-resource is caring for the correct Exception/Suppressed Ex handling including to avoid NullPointer.

I have found a second issue here: finish() and flush() had the wrong order and flush() was sometimes in use, sometimes not. It's fixed now.

Hello @bstansberry Tests passed for this PR and it's approved. Could you check and merge, please?

authors: boris-unckel chengfang

repo: wildfly/wildfly


text:
[WFLY-16305] Upgrade cryptacular to 1.2.5

Fixes https://issues.redhat.com/browse/WFLY-16305

@boris-unckel  This looks good to me .

authors: boris-unckel jimma


text:
WFLY-15859 Re-authentication after reboot, even though HttpSession are persisted

https://issues.redhat.com/browse/WFLY-15859
Draft referencing SNAPSHOT versions of requisite elytron artifacts to accommodate cross-project testing.
Requires wildfly-core release containing Final version of elytron components.

Thanks @pferraro

authors: bstansberry pferraro