You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
two different sets of totals and same pid of 6. now i would think this is because, OK nova has the main DB and the API DB, but looking in plugin.py, CollectionTarget is a process-wide singleton, multiple engines go into it. i see there are two Senders set up, which is wrong and we can see messages being sent twice above, but...they send on the same collection target which should mean only one value. the above are running in containers so "6" is local to a container, need to see if that is a factor here.
The text was updated successfully, but these errors were encountered:
so if you look in the podman containers for all 8 nova services, they are all on pid 6 :) which means we have an issue here that these are different processes but they see the same pid due to containers :)
and im going to take a guess that running in a docker container, you have a pid, the job of "hey what's my pid on the host machine?" is exactly where "sandbox" would say, GET LOST YOU'RE IN A SANDBOX WE'RE TRYING TO PRETEND THIS IS SECURE! . sooooo.....pid + hostname is not enough! we need something else for containers with net=host. bleah.
zzzeek
changed the title
multiple engines, same process
multiple engines, multiple containers, same pid
Nov 19, 2019
This is so that multiple processes on the same host that
happen to have the same pid due to namespacing / containers
may still be disambiguated. it also allows a recycled
pid to appear as a new process.
Fixes: #9
Change-Id: I605263c848c4a7899e47cab81e90542be993d2d2
we see this in nova, multiple sets of values:
two different sets of totals and same pid of 6. now i would think this is because, OK nova has the main DB and the API DB, but looking in plugin.py, CollectionTarget is a process-wide singleton, multiple engines go into it. i see there are two Senders set up, which is wrong and we can see messages being sent twice above, but...they send on the same collection target which should mean only one value. the above are running in containers so "6" is local to a container, need to see if that is a factor here.
The text was updated successfully, but these errors were encountered: