So what do I need to do to reference Ohai data in an Omnibus 4.0
software definition?
I do know in some cases there are chef-sugar helpers like windows?
that can be used to switch on platform conditions. I couldn’t find
relevant documentation, and if someone could point me at an example it
would be kindly appreciated.
While I try to figure out how to get node to at least temporarily log it’s errors,
I am hoping that there is a common issue with launching node instances
from Chef.
execute “execute run.sh” do
cwd "/opt/prodname/data"
command "./run.sh"
action :run
end
At first I thought that it might not be running, but checking the process table
for instances of node (or processes that contain the string “node” ;0) showed that
the node instances were launched but that they dropped out of memory a few seconds
late: (every – == one second)
while (true) do ps -ef | grep node| grep -v grep; echo “–”; sleep 1; done
I tried adding redirection to the lines in run.sh, to ensure that no output was uncultured
but to no avail. (i.e. adding 2>&1 >/tmp/script#out resulted in no output to these logs)
This seems like more of a node question, and if you can confirm that this is the case,
then I will turn to that, with appreciation.
While I try to figure out how to get node to at least temporarily log it's errors,
I am hoping that there is a common issue with launching node instances
from Chef.
execute "execute run.sh" do
cwd "/opt/prodname/data"
command "./run.sh"
action :run
end
At first I thought that it might not be running, but checking the process table
for instances of node (or processes that contain the string "node" ;0) showed that
the node instances were launched but that they dropped out of memory a few seconds
late: (every -- == one second)
while (true) do ps -ef | grep node| grep -v grep; echo "--"; sleep 1; done
I tried adding redirection to the lines in run.sh, to ensure that no output was uncultured
but to no avail. (i.e. adding 2>&1 >/tmp/script#out resulted in no output to these logs)
This seems like more of a node question, and if you can confirm that this is the case,
then I will turn to that, with appreciation.
While I try to figure out how to get node to at least temporarily log it's errors,
I am hoping that there is a common issue with launching node instances
from Chef.
execute "execute run.sh" do
cwd "/opt/prodname/data"
command "./run.sh"
action :run
end
At first I thought that it might not be running, but checking the process table
for instances of node (or processes that contain the string "node" ;0) showed that
the node instances were launched but that they dropped out of memory a few seconds
late: (every -- == one second)
while (true) do ps -ef | grep node| grep -v grep; echo "--"; sleep 1; done
I tried adding redirection to the lines in run.sh, to ensure that no output was uncultured
but to no avail. (i.e. adding 2>&1 >/tmp/script#out resulted in no output to these logs)
This seems like more of a node question, and if you can confirm that this is the case,
then I will turn to that, with appreciation.
So what do I need to do to reference Ohai data in an Omnibus 4.0
software definition?
I do know in some cases there are chef-sugar helpers like windows?
that can be used to switch on platform conditions. I couldn't find
relevant documentation, and if someone could point me at an example it
would be kindly appreciated.
So what do I need to do to reference Ohai data in an Omnibus 4.0
software definition?
I do know in some cases there are chef-sugar helpers like windows?
that can be used to switch on platform conditions. I couldn't find
relevant documentation, and if someone could point me at an example it
would be kindly appreciated.