This message was deleted.
# puppet-enterprise
s
This message was deleted.
b
you want to update it or you want to know the current state?
d
its been escalated to a high priority ticket but there is no further update yet. I will highlight this on the internal channels
v
I opened a sev2 ticket, my infra is totally dead 😞
d
That's disappointing let me see what I can find out
v
I have unlinked /etc/puppetlabs/puppetserver/code (I use versioned deploy) and puppetservers came online, so it's not as bad now
I think it could be to this process. kill doesn't get rid of it and I am hesitant to use kill -9
Copy code
pe-pupp+ 2468844       1  0 10:12 ?        00:00:01 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/bin/r10k deploy --config /opt/puppetlabs/server/data/code-manager/r10k.yaml --verbose warn --cachedir /opt/puppetlabs/server/data/code-manager/worker-caches/deploy-pool-1-2 environment production --modules --incremental
c
you could always use signal 15 which is a bit nicer, and will give you dditional output if STDOUT was respected….
v
that's what I did, no dice
d
Just to confirm is the workaround using unlinking still having impact?
v
unlinking helped to bring puppetservers up
but puppet code deploy still fails. and I think that process might to blame
shouldn't be running for 3 hours anyway
d
Right im just going to highlight this is not a everything working workaround if code deploy is still failing / running that long. I'm not sure they are clear on that
🤷‍♂️ 1
v
Copy code
# strace -p 2468844
strace: Process 2468844 attached
futex(0x9981e0, FUTEX_WAIT_PRIVATE, 0, NULL