So you:
1. run that command
2. get a brand new agent.properties as a result
3. start the service
but you don't see it in the process table?
The agent's STDOUT doesn't go to the agent log, only log4j stuff. So
if there were an error not printed via logger you'd not see it. I'm
not as familiar with the debian/ubuntu stuff off the top of my head,
but in /etc/init.d/cloudstack-agent on CentOS we do:
start() {
echo -n $"Starting $PROGNAME: "
if hostname --fqdn >/dev/null 2>&1 ; then
$JSVC -cp "$CLASSPATH" -pidfile "$PIDFILE" \
-errfile $LOGDIR/cloudstack-agent.err -outfile
$LOGDIR/cloudstack-agent.out $CLASS
RETVAL=$?
echo
else
Which sends STDOUT to cloudstack-agent.out and errors to
cloudstack-agent.err. You can look to see what Ubuntu does.
Out of curiosity, what do you get when you do 'lsmod | grep kvm' ? I
know you didn't end up using it, but the devcloud-kvm instructions for
vmware fusion tell you to ensure that your guest has hardware
virtualization passthrough enabled, I'm wondering if it isn't.
On Wed, Sep 25, 2013 at 4:11 PM, Mike Tutkowski
<mike.tutkow...@solidfire.com> wrote:
> These results look good:
>
> mtutkowski@ubuntu:~$ sudo cloudstack-setup-agent -m 192.168.233.1 -z 1 -p 1
> -c 1 -g 6b4aa1c2-2ac9-3c60-aabe-704aed40c684 -a --pubNic=cloudbr0
> --prvNic=cloudbr0 --guestNic=cloudbr0
> Starting to configure your system:
> Configure Apparmor ... [OK]
> Configure Network ... [OK]
> Configure Libvirt ... [OK]
> Configure Firewall ... [OK]
> Configure Nfs ... [OK]
> Configure cloudAgent ... [OK]
> CloudStack Agent setup is done!
>
> However, these results are the same:
>
> mtutkowski@ubuntu:~$ ps -ef | grep jsvc
> 1000 4314 3725 0 16:10 pts/1 00:00:00 grep --color=auto jsvc
>
>
> On Wed, Sep 25, 2013 at 3:48 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> This appears to be the offending method:
>>
>> public String parseCapabilitiesXML(String capXML) {
>>
>> if (!_initialized) {
>>
>> return null;
>>
>> }
>>
>> try {
>>
>> _sp.parse(new InputSource(new StringReader(capXML)), this);
>>
>> return _capXML.toString();
>>
>> } catch (SAXException se) {
>>
>> s_logger.warn(se.getMessage());
>>
>> } catch (IOException ie) {
>>
>> s_logger.error(ie.getMessage());
>>
>> }
>>
>> return null;
>>
>> }
>>
>>
>> The logging I do from this method (not shown above), however, doesn't seem
>> to end up in agent.log. Not sure why that is.
>>
>> We invoke this method and I log we're in this method as the first thing I
>> do, but it doesn't show up in agent.log.
>>
>> The last message in agent.log is a line saying we are right before the
>> call to this method.
>>
>>
