Andrew Any Luck,
I am not really sure whats going with your logging, and I am not familiar
with ubuntu install.
Did you compile from source or install from package manager... Can you
share the install doc you used?
This may help you figure out where the service is logging to... If it is
logging at all.
Start the cloudstack-managment service
Then run lsof to get a list of files the service may be logging to.
I did something like this
$ sudo /usr/sbin/lsof | grep cloud | grep log | grep -v jar
java 3962 cloud 1w REG 253,1 138689112
146997 /var/log/cloudstack/management/catalina.out
java 3962 cloud 2w REG 253,1 138689112
146997 /var/log/cloudstack/management/catalina.out
java 3962 cloud 44w REG 253,1 0
138520 /var/log/cloudstack/management/access_log.2014-06-10.txt
java 3962 cloud 231w REG 253,1 0
138526 /var/log/cloudstack/management/catalina.2014-06-10.log
java 3962 cloud 232w REG 253,1 0
138528 /var/log/cloudstack/management/localhost.2014-06-10.log
java 3962 cloud 233w REG 253,1 0
140351 /var/log/cloudstack/management/manager.2014-06-10.log
java 3962 cloud 234w REG 253,1 0
140388 /var/log/cloudstack/management/host-manager.2014-06-10.log
java 3962 cloud 235w REG 253,1 1918848
136886 /var/log/cloudstack/management/apilog.log
java 3962 cloud 236w REG 253,1 1078
139104 /var/log/cloudstack/awsapi/awsapi.log
java 3962 cloud 238w REG 253,1 12993994
140094 /var/log/cloudstack/management/management-server.log
java 3962 cloud 273w REG 253,1 0
138520 /var/log/cloudstack/management/access_log.2014-06-10.txt
java 3962 cloud 468w REG 253,1 1918848
136886 /var/log/cloudstack/management/apilog.log
java 3962 cloud 469w REG 253,1 1078
139104 /var/log/cloudstack/awsapi/awsapi.log
java 3962 cloud 471w REG 253,1 12993994
140094 /var/log/cloudstack/management/management-server.log
Also look at the cloudstack-managment startup script it basically calls the
tomcat startup script
start)
. /etc/rc.d/init.d/tomcat6
Take a look at that script and you will see log location
# Define the tomcat log file
$ cat . /etc/rc.d/init.d/tomcat6
TOMCAT_LOG="${TOMCAT_LOG:-/var/log/${NAME}-initd.log}"
If this all checks out and the application is still not logging I would
guess you may not a full install.
Few more things you can do.
Run ldd or strace against the tomcat6 and see what you get.
TOMCAT_SCRIPT="/usr/sbin/tomcat6"
Put tomcat into debug mode
in your tomcat6.conf do something like this.
JAVA_OPTS="${JAVA_OPTS} -Xdebug
Good Luck!
On Mon, Jun 9, 2014 at 7:55 AM, Andrew Chiw <[email protected]> wrote:
> I’m using Ubuntu Saucy (13.10). Very very sure, look:
> root@sri02:/var/log# ls -lR cloudstack*
> cloudstack:
> total 4
> drwx------ 2 root root 4096 Jun 6 13:51 agent
>
> cloudstack/agent:
> total 292
> -rw------- 1 root root 289290 Jun 6 15:35 agent.log
> -rw-r--r-- 1 root root 345 Jun 6 13:51 security_group.log
>
> cloudstack-management:
> total 0
> root@sri02:/var/log#
>
> I’m running cloudstack-agent and management on the same machine (it’s just
> for testing).
>
>
> On Jun 9, 2014, at 1:47 PM, Derek Page <[email protected]> wrote:
>
> Are you sure you don't have two directries under /var/log?
>
> [root@stacktest1 log]# pwd
> /var/log
> [root@stacktest1 log]# ls -ld cloud*
> drwxr-xr-x 6 root root 4096 May 7 14:32 cloudstack
> drwxrwx--- 2 root root 4096 Mar 25 11:01 cloudstack-management
>
>
> My /var/log/cloudstack-managment directory is empty.
> My /var/log/cloudstack/managment directory has logs.
>
> [root@stacktest1 management]# ls
> access_log.2014-05-07.txt management-server.log.2014-05-09.gz
> access_log.2014-05-19.txt management-server.log.2014-05-10.gz
> access_log.2014-05-20.txt management-server.log.2014-05-11.gz
> access_log.2014-05-21.txt management-server.log.2014-05-12.gz
>
>
> What disto are you using? This is the case for CentOS 6.5
>
> On Mon, Jun 9, 2014 at 7:42 AM, Andrew Chiw <[email protected]>
> wrote:
>
>> Hey Derek, thanks for replying.
>> I did what you said, reran cloudstack-setup-management (it creates
>> cloudstack-management under logs, not cloudstack/management) and the same
>> error still happens.
>> /var/log/cloudstack-management is empty, even when I’ve sent HTTP
>> requests to the server.
>> Here is my sudoers, I assume cloudstack-setup-management added this line:
>>
>> cloud ALL =NOPASSWD : /bin/chmod, /bin/cp, /bin/mkdir, /bin/mount,
>> /bin/umount
>> Defaults:cloud !requiretty
>>
>> Thanks,
>> Andrew
>> > Hi Andrew,
>> >
>> > Look here:
>> > /var/log/cloudstack/management
>> > management-server.log or catalina.out
>> >
>> >
>> > Stop cloudstack-managment
>> > run
>> > $ /usr/bin/cloudstack-setup-management
>> > and start cloudstack-managment again.
>> >
>> > When I first set it up my puppet config was over writing my sudoers file
>> > removing user cloud's sudo rights.
>> > Starting cloudstack with no cloud sudo rights results in a tomcat 404.
>> >
>> > I would start there.
>> >
>> >
>> >
>> > On Fri, Jun 6, 2014 at 9:51 AM, Andrew Chiw <[email protected]>
>> wrote:
>> >
>> >> Hello everybody, I’ve installed cloudstack-management, setup the
>> >> databases, and started cloudstack-management, but tomcat6 still gives
>> me a
>> >> 404 on localhost:8080/client.
>> >> There are no log files created under /var/log/cloudstack-management.
>> And I
>> >> don’t know why but cloudstack-agent creates its logs under
>> >> /var/log/cloudstack/agent instead. I restarted cloudstack-management
>> again,
>> >> looked at /var/log/tomcat6, which was empty too. What can I do now?
>> >>
>> >> I’m running tomcat 6.0.37, upgraded to ubuntu saucy to get that.
>> >> Thanks,
>> >> Andrew
>> >
>> >
>> >
>> >
>> > --
>> > Derek Page
>> > Operations Engineer
>> > KAYAK
>>
>
>
>
> --
> Derek Page
> Operations Engineer
> KAYAK
>
>
>
--
Derek Page
Operations Engineer
KAYAK
