Re: Unable to locate datastore with id

[Asai]

Thanks,

The next problem seems to be now, that there was an original snapshot that is 
no longer there.  When I try to snapshot the volume I’m working on, it fails, 
because it’s looking for an initial snapshot that the database says is still 
there, but which was actually removed when I removed the other Primary Storage 
volume.  Does that make sense?  What do I need to change in the database for 
that volume to be able to snapshot?
Asai


> On Aug 24, 2017, at 1:53 PM, Rafael Weingärtner  
> wrote:
> 
> Do not remove (delete), to remove you can mark the flags. First set the
> removed date flag and then the state as Destroyed.
> 
> On Thu, Aug 24, 2017 at 1:10 PM, Asai  wrote:
> 
>> I the DB table snapshot_store_ref I see two snapshots listed with store_id
>> 3.  Can I safely remove those rows?
>> Asai
>> Network and Systems Administrator
>> GLOBAL CHANGE MEDIA
>> office: 520.398.2542
>> http://globalchange.media
>> Tucson, AZ
>> 
>>> On Aug 24, 2017, at 1:06 PM, Asai  wrote:
>>> 
>>> I can see now that id 3 refers to a primary storage that I had to remove
>> a while ago.  It’s still in the DB, though, and seems to be causing the
>> error.  What steps should I take to remove this reference completely from
>> the DB?
>>> Asai
>>> 
>>> 
 On Aug 24, 2017, at 11:20 AM, Gabriel Beims Bräscher <
>> gabrasc...@gmail.com> wrote:
 
 Just adding to Rafael's comment. Constant database backup is also a
>> great
 idea.
 
 2017-08-24 15:19 GMT-03:00 Rafael Weingärtner <
>> rafaelweingart...@gmail.com>:
 
> I would suggest you taking quite a lot of care before executing
>> anything in
> the database.
> Please, do not hesitate to ask for further assistance here.
> 
> On Thu, Aug 24, 2017 at 2:15 PM, Asai 
>> wrote:
> 
>> Thank you very much for the assistance.  I will try that.
>> Asai
>>> On Aug 24, 2017, at 11:12 AM, Rafael Weingärtner <
>> rafaelweingart...@gmail.com> wrote:
>>> 
>>> Yes, quite easily.
>>> I do not know if your problem is the same (you need a human not
>> paying
>> much
>>> attention to cause this type of problem), but basically, you can
>> check
> in
>>> the database what is the data store with id = 3, and then the volumes
> of
>>> snapshots that are allocated in this data store, and then you can
> remove
>>> them manually setting the flags.
>>> 
>>> 
>>> On Thu, Aug 24, 2017 at 2:09 PM, Asai 
>> wrote:
>>> 
 Do you recall if it was able to be fixed?
 Asai
 
 
> On Aug 24, 2017, at 11:03 AM, Rafael Weingärtner <
 rafaelweingart...@gmail.com> wrote:
> 
> I have seen this issue before. In the environment I noticed it, it
> was
> caused by someone that manually deleted a volume in the database in
>> order
> to remove a data store, but the snapshot that was using that volume
> was
 not
> removed. Then, the data store was removed. By delete here I mean
>> setting
> the flag "removed" in the database to some data and the "state" to
> destroyed.
> 
> On Thu, Aug 24, 2017 at 1:45 PM, Asai 
 wrote:
> 
>> Greetings,
>> 
>> I was browsing to the Snapshots section under “Storage” today and
> came
 up
>> with this error:
>> 
>> Unable to locate datastore with id 3
>> 
>> I am unable to figure this out.  I went to the Secondary Storage
>> server
>> and it looks like all the snapshots are there from 2 days ago.
>> Can
 someone
>> please assist me on how to troubleshoot this problem?
>> Asai
>> 
>> 
>> 
> 
> 
> --
> Rafael Weingärtner
 
 
>>> 
>>> 
>>> --
>>> Rafael Weingärtner
>> 
>> 
> 
> 
> --
> Rafael Weingärtner
> 
>>> 
>> 
>> 
> 
> 
> -- 
> Rafael Weingärtner

Re: Unable to locate datastore with id

[Rafael Weingärtner]

Do not remove (delete), to remove you can mark the flags. First set the
removed date flag and then the state as Destroyed.

On Thu, Aug 24, 2017 at 1:10 PM, Asai  wrote:

> I the DB table snapshot_store_ref I see two snapshots listed with store_id
> 3.  Can I safely remove those rows?
> Asai
> Network and Systems Administrator
> GLOBAL CHANGE MEDIA
> office: 520.398.2542
> http://globalchange.media
> Tucson, AZ
>
> > On Aug 24, 2017, at 1:06 PM, Asai  wrote:
> >
> > I can see now that id 3 refers to a primary storage that I had to remove
> a while ago.  It’s still in the DB, though, and seems to be causing the
> error.  What steps should I take to remove this reference completely from
> the DB?
> > Asai
> >
> >
> >> On Aug 24, 2017, at 11:20 AM, Gabriel Beims Bräscher <
> gabrasc...@gmail.com> wrote:
> >>
> >> Just adding to Rafael's comment. Constant database backup is also a
> great
> >> idea.
> >>
> >> 2017-08-24 15:19 GMT-03:00 Rafael Weingärtner <
> rafaelweingart...@gmail.com>:
> >>
> >>> I would suggest you taking quite a lot of care before executing
> anything in
> >>> the database.
> >>> Please, do not hesitate to ask for further assistance here.
> >>>
> >>> On Thu, Aug 24, 2017 at 2:15 PM, Asai 
> wrote:
> >>>
>  Thank you very much for the assistance.  I will try that.
>  Asai
> > On Aug 24, 2017, at 11:12 AM, Rafael Weingärtner <
>  rafaelweingart...@gmail.com> wrote:
> >
> > Yes, quite easily.
> > I do not know if your problem is the same (you need a human not
> paying
>  much
> > attention to cause this type of problem), but basically, you can
> check
> >>> in
> > the database what is the data store with id = 3, and then the volumes
> >>> of
> > snapshots that are allocated in this data store, and then you can
> >>> remove
> > them manually setting the flags.
> >
> >
> > On Thu, Aug 24, 2017 at 2:09 PM, Asai 
>  wrote:
> >
> >> Do you recall if it was able to be fixed?
> >> Asai
> >>
> >>
> >>> On Aug 24, 2017, at 11:03 AM, Rafael Weingärtner <
> >> rafaelweingart...@gmail.com> wrote:
> >>>
> >>> I have seen this issue before. In the environment I noticed it, it
> >>> was
> >>> caused by someone that manually deleted a volume in the database in
>  order
> >>> to remove a data store, but the snapshot that was using that volume
> >>> was
> >> not
> >>> removed. Then, the data store was removed. By delete here I mean
>  setting
> >>> the flag "removed" in the database to some data and the "state" to
> >>> destroyed.
> >>>
> >>> On Thu, Aug 24, 2017 at 1:45 PM, Asai 
> >> wrote:
> >>>
>  Greetings,
> 
>  I was browsing to the Snapshots section under “Storage” today and
> >>> came
> >> up
>  with this error:
> 
>  Unable to locate datastore with id 3
> 
>  I am unable to figure this out.  I went to the Secondary Storage
>  server
>  and it looks like all the snapshots are there from 2 days ago.
> Can
> >> someone
>  please assist me on how to troubleshoot this problem?
>  Asai
> 
> 
> 
> >>>
> >>>
> >>> --
> >>> Rafael Weingärtner
> >>
> >>
> >
> >
> > --
> > Rafael Weingärtner
> 
> 
> >>>
> >>>
> >>> --
> >>> Rafael Weingärtner
> >>>
> >
>
>


-- 
Rafael Weingärtner

Re: Unable to locate datastore with id

[Asai]

I the DB table snapshot_store_ref I see two snapshots listed with store_id 3.  
Can I safely remove those rows?
Asai
Network and Systems Administrator
GLOBAL CHANGE MEDIA
office: 520.398.2542
http://globalchange.media
Tucson, AZ

> On Aug 24, 2017, at 1:06 PM, Asai  wrote:
> 
> I can see now that id 3 refers to a primary storage that I had to remove a 
> while ago.  It’s still in the DB, though, and seems to be causing the error.  
> What steps should I take to remove this reference completely from the DB?
> Asai
> 
> 
>> On Aug 24, 2017, at 11:20 AM, Gabriel Beims Bräscher  
>> wrote:
>> 
>> Just adding to Rafael's comment. Constant database backup is also a great
>> idea.
>> 
>> 2017-08-24 15:19 GMT-03:00 Rafael Weingärtner :
>> 
>>> I would suggest you taking quite a lot of care before executing anything in
>>> the database.
>>> Please, do not hesitate to ask for further assistance here.
>>> 
>>> On Thu, Aug 24, 2017 at 2:15 PM, Asai  wrote:
>>> 
 Thank you very much for the assistance.  I will try that.
 Asai
> On Aug 24, 2017, at 11:12 AM, Rafael Weingärtner <
 rafaelweingart...@gmail.com> wrote:
> 
> Yes, quite easily.
> I do not know if your problem is the same (you need a human not paying
 much
> attention to cause this type of problem), but basically, you can check
>>> in
> the database what is the data store with id = 3, and then the volumes
>>> of
> snapshots that are allocated in this data store, and then you can
>>> remove
> them manually setting the flags.
> 
> 
> On Thu, Aug 24, 2017 at 2:09 PM, Asai 
 wrote:
> 
>> Do you recall if it was able to be fixed?
>> Asai
>> 
>> 
>>> On Aug 24, 2017, at 11:03 AM, Rafael Weingärtner <
>> rafaelweingart...@gmail.com> wrote:
>>> 
>>> I have seen this issue before. In the environment I noticed it, it
>>> was
>>> caused by someone that manually deleted a volume in the database in
 order
>>> to remove a data store, but the snapshot that was using that volume
>>> was
>> not
>>> removed. Then, the data store was removed. By delete here I mean
 setting
>>> the flag "removed" in the database to some data and the "state" to
>>> destroyed.
>>> 
>>> On Thu, Aug 24, 2017 at 1:45 PM, Asai 
>> wrote:
>>> 
 Greetings,
 
 I was browsing to the Snapshots section under “Storage” today and
>>> came
>> up
 with this error:
 
 Unable to locate datastore with id 3
 
 I am unable to figure this out.  I went to the Secondary Storage
 server
 and it looks like all the snapshots are there from 2 days ago.  Can
>> someone
 please assist me on how to troubleshoot this problem?
 Asai
 
 
 
>>> 
>>> 
>>> --
>>> Rafael Weingärtner
>> 
>> 
> 
> 
> --
> Rafael Weingärtner
 
 
>>> 
>>> 
>>> --
>>> Rafael Weingärtner
>>> 
> 

Re: Unable to locate datastore with id

[Asai]

I can see now that id 3 refers to a primary storage that I had to remove a 
while ago.  It’s still in the DB, though, and seems to be causing the error.  
What steps should I take to remove this reference completely from the DB?
Asai


> On Aug 24, 2017, at 11:20 AM, Gabriel Beims Bräscher  
> wrote:
> 
> Just adding to Rafael's comment. Constant database backup is also a great
> idea.
> 
> 2017-08-24 15:19 GMT-03:00 Rafael Weingärtner :
> 
>> I would suggest you taking quite a lot of care before executing anything in
>> the database.
>> Please, do not hesitate to ask for further assistance here.
>> 
>> On Thu, Aug 24, 2017 at 2:15 PM, Asai  wrote:
>> 
>>> Thank you very much for the assistance.  I will try that.
>>> Asai
 On Aug 24, 2017, at 11:12 AM, Rafael Weingärtner <
>>> rafaelweingart...@gmail.com> wrote:
 
 Yes, quite easily.
 I do not know if your problem is the same (you need a human not paying
>>> much
 attention to cause this type of problem), but basically, you can check
>> in
 the database what is the data store with id = 3, and then the volumes
>> of
 snapshots that are allocated in this data store, and then you can
>> remove
 them manually setting the flags.
 
 
 On Thu, Aug 24, 2017 at 2:09 PM, Asai 
>>> wrote:
 
> Do you recall if it was able to be fixed?
> Asai
> 
> 
>> On Aug 24, 2017, at 11:03 AM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>> 
>> I have seen this issue before. In the environment I noticed it, it
>> was
>> caused by someone that manually deleted a volume in the database in
>>> order
>> to remove a data store, but the snapshot that was using that volume
>> was
> not
>> removed. Then, the data store was removed. By delete here I mean
>>> setting
>> the flag "removed" in the database to some data and the "state" to
>> destroyed.
>> 
>> On Thu, Aug 24, 2017 at 1:45 PM, Asai 
> wrote:
>> 
>>> Greetings,
>>> 
>>> I was browsing to the Snapshots section under “Storage” today and
>> came
> up
>>> with this error:
>>> 
>>> Unable to locate datastore with id 3
>>> 
>>> I am unable to figure this out.  I went to the Secondary Storage
>>> server
>>> and it looks like all the snapshots are there from 2 days ago.  Can
> someone
>>> please assist me on how to troubleshoot this problem?
>>> Asai
>>> 
>>> 
>>> 
>> 
>> 
>> --
>> Rafael Weingärtner
> 
> 
 
 
 --
 Rafael Weingärtner
>>> 
>>> 
>> 
>> 
>> --
>> Rafael Weingärtner
>> 

Re: Unable to locate datastore with id

[Gabriel Beims Bräscher]

Just adding to Rafael's comment. Constant database backup is also a great
idea.

2017-08-24 15:19 GMT-03:00 Rafael Weingärtner :

> I would suggest you taking quite a lot of care before executing anything in
> the database.
> Please, do not hesitate to ask for further assistance here.
>
> On Thu, Aug 24, 2017 at 2:15 PM, Asai  wrote:
>
> > Thank you very much for the assistance.  I will try that.
> > Asai
> > > On Aug 24, 2017, at 11:12 AM, Rafael Weingärtner <
> > rafaelweingart...@gmail.com> wrote:
> > >
> > > Yes, quite easily.
> > > I do not know if your problem is the same (you need a human not paying
> > much
> > > attention to cause this type of problem), but basically, you can check
> in
> > > the database what is the data store with id = 3, and then the volumes
> of
> > > snapshots that are allocated in this data store, and then you can
> remove
> > > them manually setting the flags.
> > >
> > >
> > > On Thu, Aug 24, 2017 at 2:09 PM, Asai 
> > wrote:
> > >
> > >> Do you recall if it was able to be fixed?
> > >> Asai
> > >>
> > >>
> > >>> On Aug 24, 2017, at 11:03 AM, Rafael Weingärtner <
> > >> rafaelweingart...@gmail.com> wrote:
> > >>>
> > >>> I have seen this issue before. In the environment I noticed it, it
> was
> > >>> caused by someone that manually deleted a volume in the database in
> > order
> > >>> to remove a data store, but the snapshot that was using that volume
> was
> > >> not
> > >>> removed. Then, the data store was removed. By delete here I mean
> > setting
> > >>> the flag "removed" in the database to some data and the "state" to
> > >>> destroyed.
> > >>>
> > >>> On Thu, Aug 24, 2017 at 1:45 PM, Asai 
> > >> wrote:
> > >>>
> >  Greetings,
> > 
> >  I was browsing to the Snapshots section under “Storage” today and
> came
> > >> up
> >  with this error:
> > 
> >  Unable to locate datastore with id 3
> > 
> >  I am unable to figure this out.  I went to the Secondary Storage
> > server
> >  and it looks like all the snapshots are there from 2 days ago.  Can
> > >> someone
> >  please assist me on how to troubleshoot this problem?
> >  Asai
> > 
> > 
> > 
> > >>>
> > >>>
> > >>> --
> > >>> Rafael Weingärtner
> > >>
> > >>
> > >
> > >
> > > --
> > > Rafael Weingärtner
> >
> >
>
>
> --
> Rafael Weingärtner
>

Re: Unable to locate datastore with id

[Rafael Weingärtner]

I would suggest you taking quite a lot of care before executing anything in
the database.
Please, do not hesitate to ask for further assistance here.

On Thu, Aug 24, 2017 at 2:15 PM, Asai  wrote:

> Thank you very much for the assistance.  I will try that.
> Asai
> > On Aug 24, 2017, at 11:12 AM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
> >
> > Yes, quite easily.
> > I do not know if your problem is the same (you need a human not paying
> much
> > attention to cause this type of problem), but basically, you can check in
> > the database what is the data store with id = 3, and then the volumes of
> > snapshots that are allocated in this data store, and then you can remove
> > them manually setting the flags.
> >
> >
> > On Thu, Aug 24, 2017 at 2:09 PM, Asai 
> wrote:
> >
> >> Do you recall if it was able to be fixed?
> >> Asai
> >>
> >>
> >>> On Aug 24, 2017, at 11:03 AM, Rafael Weingärtner <
> >> rafaelweingart...@gmail.com> wrote:
> >>>
> >>> I have seen this issue before. In the environment I noticed it, it was
> >>> caused by someone that manually deleted a volume in the database in
> order
> >>> to remove a data store, but the snapshot that was using that volume was
> >> not
> >>> removed. Then, the data store was removed. By delete here I mean
> setting
> >>> the flag "removed" in the database to some data and the "state" to
> >>> destroyed.
> >>>
> >>> On Thu, Aug 24, 2017 at 1:45 PM, Asai 
> >> wrote:
> >>>
>  Greetings,
> 
>  I was browsing to the Snapshots section under “Storage” today and came
> >> up
>  with this error:
> 
>  Unable to locate datastore with id 3
> 
>  I am unable to figure this out.  I went to the Secondary Storage
> server
>  and it looks like all the snapshots are there from 2 days ago.  Can
> >> someone
>  please assist me on how to troubleshoot this problem?
>  Asai
> 
> 
> 
> >>>
> >>>
> >>> --
> >>> Rafael Weingärtner
> >>
> >>
> >
> >
> > --
> > Rafael Weingärtner
>
>


-- 
Rafael Weingärtner

Re: Unable to locate datastore with id

[Asai]

Thank you very much for the assistance.  I will try that.
Asai
> On Aug 24, 2017, at 11:12 AM, Rafael Weingärtner 
>  wrote:
> 
> Yes, quite easily.
> I do not know if your problem is the same (you need a human not paying much
> attention to cause this type of problem), but basically, you can check in
> the database what is the data store with id = 3, and then the volumes of
> snapshots that are allocated in this data store, and then you can remove
> them manually setting the flags.
> 
> 
> On Thu, Aug 24, 2017 at 2:09 PM, Asai  wrote:
> 
>> Do you recall if it was able to be fixed?
>> Asai
>> 
>> 
>>> On Aug 24, 2017, at 11:03 AM, Rafael Weingärtner <
>> rafaelweingart...@gmail.com> wrote:
>>> 
>>> I have seen this issue before. In the environment I noticed it, it was
>>> caused by someone that manually deleted a volume in the database in order
>>> to remove a data store, but the snapshot that was using that volume was
>> not
>>> removed. Then, the data store was removed. By delete here I mean setting
>>> the flag "removed" in the database to some data and the "state" to
>>> destroyed.
>>> 
>>> On Thu, Aug 24, 2017 at 1:45 PM, Asai 
>> wrote:
>>> 
 Greetings,
 
 I was browsing to the Snapshots section under “Storage” today and came
>> up
 with this error:
 
 Unable to locate datastore with id 3
 
 I am unable to figure this out.  I went to the Secondary Storage server
 and it looks like all the snapshots are there from 2 days ago.  Can
>> someone
 please assist me on how to troubleshoot this problem?
 Asai
 
 
 
>>> 
>>> 
>>> --
>>> Rafael Weingärtner
>> 
>> 
> 
> 
> -- 
> Rafael Weingärtner

Re: Different Time/Timezone on ACS node and hypervisors

[Gabriel Beims Bräscher]

I am not sure if different time zones would be the cause of your snapshot
issues.
Can you please provide us with more details and, if possible, some logs
related to your problem?

Thanks.

2017-08-14 3:05 GMT-03:00 Makrand :

> Hey All,
>
> Is there any possible problem or impact if cloudstack VM/Machine have
> different time/time zone than rest of hypervisor hots in the cloud? Let's
> assume both scenarios:-
> a) One ACS VM/Machine managing multiple zones (ACS VM in one location wiht
> native timezone. Other hypervisors pools have natuve time set )
> b) Each zone has it's dedicated ACS VM (ACS VM have time set as GMT, where
> as hypervisor have native time set)
>
> FYI, we are facing some issues with snapshot (XENserver as hypervisor).
> Just ruling out possible reasons.
>
>
> --
> Makrand
>

RE: Failed to find db.properties

[Paul Angus]

Yes I do.  Thank you 


Kind regards,

Paul Angus

paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Rodrigo Baldasso [mailto:rodr...@loophost.com.br] 
Sent: 24 August 2017 18:25
To: users@cloudstack.apache.org
Subject: Re: Failed to find db.properties

I think that by 'we', he meant 'cloudstack'.

http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.9/overview/index.html#minimum-system-requirements


[]'s.

- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 24/08/2017 14:21:44, Jevgeni Zolotarjov  wrote:
end of story? no one can help me?

On Thu, Aug 24, 2017 at 8:15 PM, Paul Angus
wrote:

> Ah.
>
> We don't support a Debian based management server - the Debian repo works
> for Ubuntu 14.04 definitely (not sure if we have 16.04 sorted yet).
> For CentOS the current latest is 7.3
>
>
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com]
> Sent: 24 August 2017 18:13
> To: users@cloudstack.apache.org
> Subject: Re: Failed to find db.properties
>
> Debian 8.9
> the service is called tomcat7 in debian - not tomcat
>
> On Thu, Aug 24, 2017 at 8:10 PM, Paul Angus
> wrote:
>
> > Hi Jevgeni,
> >
> > What OS are you running your management server on? (sorry if it's buried
> > in your post somewhere).
> > The log suggest that tomcat7 isn't installed, or isn't where CloudStack
> is
> > expecting it to be.
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com]
> > Sent: 24 August 2017 18:06
> > To: users@cloudstack.apache.org
> > Subject: Re: Failed to find db.properties
> >
> > It seems that there is something wrong with your installation. Maybe a
> > corrupted file?
> >
> > On Thu, Aug 24, 2017 at 1:04 PM, Jevgeni Zolotarjov
> > j.zolotar...@gmail.com>
> > wrote:
> >
> > > sorry. this log file is correct
> > >
> > > DEBUG:root:execute:/usr/bin/lsb_release -i
> > > DEBUG:root:execute:hostname -f
> > > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8080
> > > DEBUG:root:Failed to execute:
> > > DEBUG:root:execute:ufw allow 8080/tcp
> > > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8250
> > > DEBUG:root:Failed to execute:
> > > DEBUG:root:execute:ufw allow 8250/tcp
> > > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 9090
> > > DEBUG:root:Failed to execute:
> > > DEBUG:root:execute:ufw allow 9090/tcp
> > > DEBUG:root:execute:rm -f /etc/cloudstack/management/server.xml
> > > DEBUG:root:execute:ln -s /etc/cloudstack/management/server7-nonssl.xml
> > > /etc/cloudstack/management/server.xml
> > > DEBUG:root:execute:rm -f /usr/share/cloudstack-management/bin
> > > DEBUG:root:execute:ln -s /usr/share/tomcat7/bin
> > > /usr/share/cloudstack-management/bin
> > > DEBUG:root:execute:rm -f /usr/share/cloudstack-management/lib
> > > DEBUG:root:execute:ln -s /usr/share/tomcat7/lib
> > > /usr/share/cloudstack-management/lib
> > > DEBUG:root:execute:touch /var/run/cloudstack-management.pid
> > > DEBUG:root:execute:chown cloud.cloud /var/run/cloudstack-
> management.pid
> > > DEBUG:root:execute:hostname --fqdn
> > > DEBUG:root:execute:chown cloud:cloud -R /var/lib/cloudstack/
> > > DEBUG:root:execute:chmod +x -R
> > > /usr/share/cloudstack-management/webapps/client/WEB-
> INF/classes/scripts/
> > > DEBUG:root:execute:sudo /usr/sbin/service tomcat status
> > > DEBUG:root:Failed to execute:● tomcat.service
> > > Loaded: not-found (Reason: No such file or directory)
> > > Active: inactive (dead)
> > > DEBUG:root:execute:sudo /usr/sbin/service tomcat stop
> > > DEBUG:root:Failed to execute:Failed to stop tomcat.service: Unit
> > > tomcat.service not loaded.
> > > DEBUG:root:execute:sudo update-rc.d -f tomcat remove
> > > DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
> > > DEBUG:root:Failed to execute:● cloudstack-management.service -
> CloudStack
> > > Management Server
> > > Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> > > enabled)
> > > Active: failed (Result: exit-code) since Thu 2017-08-24 18:15:22
> CEST;
> > > 15min ago
> > > Main PID: 19262 (code=exited, status=1/FAILURE)
> > >
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:235)
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:307)
> > > at
> > > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at

RE: Failed to find db.properties

[Paul Angus]

As Rodrigo says, I should say that the CloudStack community doesn't support the 
mgmt. server running on Debian in that the packaging has not been designed to 
take the Debian OS into account, and we don't run any testing on Debian mgmt. 
servers.

While someone in the community might know how to get the mgmt. server to run on 
Debian - I wouldn't recommend going that way, as we just don't do any testing 
on Debian.

Your best bet is to go for CentOS 7.3 (or Ubuntu 14.04 if you want something 
Debian based)



Kind regards,

Paul Angus

paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] 
Sent: 24 August 2017 18:21
To: users@cloudstack.apache.org
Subject: Re: Failed to find db.properties

end of story? no one can help me?

On Thu, Aug 24, 2017 at 8:15 PM, Paul Angus 
wrote:

> Ah.
>
> We don't support a Debian based management server - the Debian repo works
> for Ubuntu 14.04 definitely (not sure if we have 16.04 sorted yet).
> For CentOS the current latest is 7.3
>
>
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com]
> Sent: 24 August 2017 18:13
> To: users@cloudstack.apache.org
> Subject: Re: Failed to find db.properties
>
> Debian 8.9
> the service is called tomcat7 in debian - not tomcat
>
> On Thu, Aug 24, 2017 at 8:10 PM, Paul Angus 
> wrote:
>
> > Hi Jevgeni,
> >
> > What OS are you running your management server on?  (sorry if it's buried
> > in your post somewhere).
> > The log suggest that tomcat7 isn't installed, or isn't where CloudStack
> is
> > expecting it to be.
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com]
> > Sent: 24 August 2017 18:06
> > To: users@cloudstack.apache.org
> > Subject: Re: Failed to find db.properties
> >
> > It seems that there is something wrong with your installation. Maybe a
> > corrupted file?
> >
> > On Thu, Aug 24, 2017 at 1:04 PM, Jevgeni Zolotarjov <
> > j.zolotar...@gmail.com>
> > wrote:
> >
> > > sorry. this log file is correct
> > >
> > > DEBUG:root:execute:/usr/bin/lsb_release -i
> > > DEBUG:root:execute:hostname -f
> > > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8080
> > > DEBUG:root:Failed to execute:
> > > DEBUG:root:execute:ufw allow 8080/tcp
> > > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8250
> > > DEBUG:root:Failed to execute:
> > > DEBUG:root:execute:ufw allow 8250/tcp
> > > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 9090
> > > DEBUG:root:Failed to execute:
> > > DEBUG:root:execute:ufw allow 9090/tcp
> > > DEBUG:root:execute:rm -f /etc/cloudstack/management/server.xml
> > > DEBUG:root:execute:ln -s /etc/cloudstack/management/server7-nonssl.xml
> > > /etc/cloudstack/management/server.xml
> > > DEBUG:root:execute:rm -f /usr/share/cloudstack-management/bin
> > > DEBUG:root:execute:ln -s /usr/share/tomcat7/bin
> > > /usr/share/cloudstack-management/bin
> > > DEBUG:root:execute:rm -f /usr/share/cloudstack-management/lib
> > > DEBUG:root:execute:ln -s /usr/share/tomcat7/lib
> > > /usr/share/cloudstack-management/lib
> > > DEBUG:root:execute:touch /var/run/cloudstack-management.pid
> > > DEBUG:root:execute:chown cloud.cloud /var/run/cloudstack-
> management.pid
> > > DEBUG:root:execute:hostname --fqdn
> > > DEBUG:root:execute:chown cloud:cloud -R /var/lib/cloudstack/
> > > DEBUG:root:execute:chmod +x -R
> > > /usr/share/cloudstack-management/webapps/client/WEB-
> INF/classes/scripts/
> > > DEBUG:root:execute:sudo /usr/sbin/service tomcat status
> > > DEBUG:root:Failed to execute:● tomcat.service
> > >Loaded: not-found (Reason: No such file or directory)
> > >Active: inactive (dead)
> > > DEBUG:root:execute:sudo /usr/sbin/service tomcat stop
> > > DEBUG:root:Failed to execute:Failed to stop tomcat.service: Unit
> > > tomcat.service not loaded.
> > > DEBUG:root:execute:sudo update-rc.d -f tomcat remove
> > > DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
> > > DEBUG:root:Failed to execute:● cloudstack-management.service -
> CloudStack
> > > Management Server
> > >Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> > > enabled)
> > >Active: failed (Result: exit-code) since Thu 2017-08-24 18:15:22
> CEST;
> > > 15min ago
> > >  Main PID: 19262 (code=exited, status=1/FAILURE)
> > >
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:235)
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > 

Re: Failed to find db.properties

[Rodrigo Baldasso]

I think that by 'we', he meant 'cloudstack'.

http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.9/overview/index.html#minimum-system-requirements


[]'s.

- - - - - - - - - - - - - - - - - - -

Rodrigo Baldasso - LHOST

(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 24/08/2017 14:21:44, Jevgeni Zolotarjov  wrote:
end of story? no one can help me?

On Thu, Aug 24, 2017 at 8:15 PM, Paul Angus
wrote:

> Ah.
>
> We don't support a Debian based management server - the Debian repo works
> for Ubuntu 14.04 definitely (not sure if we have 16.04 sorted yet).
> For CentOS the current latest is 7.3
>
>
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com]
> Sent: 24 August 2017 18:13
> To: users@cloudstack.apache.org
> Subject: Re: Failed to find db.properties
>
> Debian 8.9
> the service is called tomcat7 in debian - not tomcat
>
> On Thu, Aug 24, 2017 at 8:10 PM, Paul Angus
> wrote:
>
> > Hi Jevgeni,
> >
> > What OS are you running your management server on? (sorry if it's buried
> > in your post somewhere).
> > The log suggest that tomcat7 isn't installed, or isn't where CloudStack
> is
> > expecting it to be.
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com]
> > Sent: 24 August 2017 18:06
> > To: users@cloudstack.apache.org
> > Subject: Re: Failed to find db.properties
> >
> > It seems that there is something wrong with your installation. Maybe a
> > corrupted file?
> >
> > On Thu, Aug 24, 2017 at 1:04 PM, Jevgeni Zolotarjov
> > j.zolotar...@gmail.com>
> > wrote:
> >
> > > sorry. this log file is correct
> > >
> > > DEBUG:root:execute:/usr/bin/lsb_release -i
> > > DEBUG:root:execute:hostname -f
> > > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8080
> > > DEBUG:root:Failed to execute:
> > > DEBUG:root:execute:ufw allow 8080/tcp
> > > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8250
> > > DEBUG:root:Failed to execute:
> > > DEBUG:root:execute:ufw allow 8250/tcp
> > > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 9090
> > > DEBUG:root:Failed to execute:
> > > DEBUG:root:execute:ufw allow 9090/tcp
> > > DEBUG:root:execute:rm -f /etc/cloudstack/management/server.xml
> > > DEBUG:root:execute:ln -s /etc/cloudstack/management/server7-nonssl.xml
> > > /etc/cloudstack/management/server.xml
> > > DEBUG:root:execute:rm -f /usr/share/cloudstack-management/bin
> > > DEBUG:root:execute:ln -s /usr/share/tomcat7/bin
> > > /usr/share/cloudstack-management/bin
> > > DEBUG:root:execute:rm -f /usr/share/cloudstack-management/lib
> > > DEBUG:root:execute:ln -s /usr/share/tomcat7/lib
> > > /usr/share/cloudstack-management/lib
> > > DEBUG:root:execute:touch /var/run/cloudstack-management.pid
> > > DEBUG:root:execute:chown cloud.cloud /var/run/cloudstack-
> management.pid
> > > DEBUG:root:execute:hostname --fqdn
> > > DEBUG:root:execute:chown cloud:cloud -R /var/lib/cloudstack/
> > > DEBUG:root:execute:chmod +x -R
> > > /usr/share/cloudstack-management/webapps/client/WEB-
> INF/classes/scripts/
> > > DEBUG:root:execute:sudo /usr/sbin/service tomcat status
> > > DEBUG:root:Failed to execute:● tomcat.service
> > > Loaded: not-found (Reason: No such file or directory)
> > > Active: inactive (dead)
> > > DEBUG:root:execute:sudo /usr/sbin/service tomcat stop
> > > DEBUG:root:Failed to execute:Failed to stop tomcat.service: Unit
> > > tomcat.service not loaded.
> > > DEBUG:root:execute:sudo update-rc.d -f tomcat remove
> > > DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
> > > DEBUG:root:Failed to execute:● cloudstack-management.service -
> CloudStack
> > > Management Server
> > > Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> > > enabled)
> > > Active: failed (Result: exit-code) since Thu 2017-08-24 18:15:22
> CEST;
> > > 15min ago
> > > Main PID: 19262 (code=exited, status=1/FAILURE)
> > >
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:235)
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:307)
> > > at
> > > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > sun.reflect.NativeMethodAccessorImpl.invoke(
> > NativeMethodAccessorImpl.java:
> > > 62)
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > > DelegatingMethodAccessorImpl.java:43)
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > 

Re: Failed to find db.properties

[Jevgeni Zolotarjov]

end of story? no one can help me?

On Thu, Aug 24, 2017 at 8:15 PM, Paul Angus 
wrote:

> Ah.
>
> We don't support a Debian based management server - the Debian repo works
> for Ubuntu 14.04 definitely (not sure if we have 16.04 sorted yet).
> For CentOS the current latest is 7.3
>
>
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com]
> Sent: 24 August 2017 18:13
> To: users@cloudstack.apache.org
> Subject: Re: Failed to find db.properties
>
> Debian 8.9
> the service is called tomcat7 in debian - not tomcat
>
> On Thu, Aug 24, 2017 at 8:10 PM, Paul Angus 
> wrote:
>
> > Hi Jevgeni,
> >
> > What OS are you running your management server on?  (sorry if it's buried
> > in your post somewhere).
> > The log suggest that tomcat7 isn't installed, or isn't where CloudStack
> is
> > expecting it to be.
> >
> >
> > Kind regards,
> >
> > Paul Angus
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com]
> > Sent: 24 August 2017 18:06
> > To: users@cloudstack.apache.org
> > Subject: Re: Failed to find db.properties
> >
> > It seems that there is something wrong with your installation. Maybe a
> > corrupted file?
> >
> > On Thu, Aug 24, 2017 at 1:04 PM, Jevgeni Zolotarjov <
> > j.zolotar...@gmail.com>
> > wrote:
> >
> > > sorry. this log file is correct
> > >
> > > DEBUG:root:execute:/usr/bin/lsb_release -i
> > > DEBUG:root:execute:hostname -f
> > > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8080
> > > DEBUG:root:Failed to execute:
> > > DEBUG:root:execute:ufw allow 8080/tcp
> > > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8250
> > > DEBUG:root:Failed to execute:
> > > DEBUG:root:execute:ufw allow 8250/tcp
> > > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 9090
> > > DEBUG:root:Failed to execute:
> > > DEBUG:root:execute:ufw allow 9090/tcp
> > > DEBUG:root:execute:rm -f /etc/cloudstack/management/server.xml
> > > DEBUG:root:execute:ln -s /etc/cloudstack/management/server7-nonssl.xml
> > > /etc/cloudstack/management/server.xml
> > > DEBUG:root:execute:rm -f /usr/share/cloudstack-management/bin
> > > DEBUG:root:execute:ln -s /usr/share/tomcat7/bin
> > > /usr/share/cloudstack-management/bin
> > > DEBUG:root:execute:rm -f /usr/share/cloudstack-management/lib
> > > DEBUG:root:execute:ln -s /usr/share/tomcat7/lib
> > > /usr/share/cloudstack-management/lib
> > > DEBUG:root:execute:touch /var/run/cloudstack-management.pid
> > > DEBUG:root:execute:chown cloud.cloud /var/run/cloudstack-
> management.pid
> > > DEBUG:root:execute:hostname --fqdn
> > > DEBUG:root:execute:chown cloud:cloud -R /var/lib/cloudstack/
> > > DEBUG:root:execute:chmod +x -R
> > > /usr/share/cloudstack-management/webapps/client/WEB-
> INF/classes/scripts/
> > > DEBUG:root:execute:sudo /usr/sbin/service tomcat status
> > > DEBUG:root:Failed to execute:● tomcat.service
> > >Loaded: not-found (Reason: No such file or directory)
> > >Active: inactive (dead)
> > > DEBUG:root:execute:sudo /usr/sbin/service tomcat stop
> > > DEBUG:root:Failed to execute:Failed to stop tomcat.service: Unit
> > > tomcat.service not loaded.
> > > DEBUG:root:execute:sudo update-rc.d -f tomcat remove
> > > DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
> > > DEBUG:root:Failed to execute:● cloudstack-management.service -
> CloudStack
> > > Management Server
> > >Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> > > enabled)
> > >Active: failed (Result: exit-code) since Thu 2017-08-24 18:15:22
> CEST;
> > > 15min ago
> > >  Main PID: 19262 (code=exited, status=1/FAILURE)
> > >
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:235)
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:307)
> > > at
> > > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > sun.reflect.NativeMethodAccessorImpl.invoke(
> > NativeMethodAccessorImpl.java:
> > > 62)
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > > DelegatingMethodAccessorImpl.java:43)
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > java.lang.reflect.Method.invoke(Method.java:498)
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > > org.apache.commons.daemon.support.DaemonLoader.load(
> > DaemonLoader.java:212)
> > > Aug 24 18:15:22 servername jsvc.exec[19263]: 2017-08-24 18:15:22 19264
> > > jsvc.exec 

RE: Failed to find db.properties

[Paul Angus]

Ah.

We don't support a Debian based management server - the Debian repo works for 
Ubuntu 14.04 definitely (not sure if we have 16.04 sorted yet).
For CentOS the current latest is 7.3



Kind regards,

Paul Angus

paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Jevgeni Zolotarjov [mailto:j.zolotar...@gmail.com] 
Sent: 24 August 2017 18:13
To: users@cloudstack.apache.org
Subject: Re: Failed to find db.properties

Debian 8.9
the service is called tomcat7 in debian - not tomcat

On Thu, Aug 24, 2017 at 8:10 PM, Paul Angus 
wrote:

> Hi Jevgeni,
>
> What OS are you running your management server on?  (sorry if it's buried
> in your post somewhere).
> The log suggest that tomcat7 isn't installed, or isn't where CloudStack is
> expecting it to be.
>
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com]
> Sent: 24 August 2017 18:06
> To: users@cloudstack.apache.org
> Subject: Re: Failed to find db.properties
>
> It seems that there is something wrong with your installation. Maybe a
> corrupted file?
>
> On Thu, Aug 24, 2017 at 1:04 PM, Jevgeni Zolotarjov <
> j.zolotar...@gmail.com>
> wrote:
>
> > sorry. this log file is correct
> >
> > DEBUG:root:execute:/usr/bin/lsb_release -i
> > DEBUG:root:execute:hostname -f
> > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8080
> > DEBUG:root:Failed to execute:
> > DEBUG:root:execute:ufw allow 8080/tcp
> > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8250
> > DEBUG:root:Failed to execute:
> > DEBUG:root:execute:ufw allow 8250/tcp
> > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 9090
> > DEBUG:root:Failed to execute:
> > DEBUG:root:execute:ufw allow 9090/tcp
> > DEBUG:root:execute:rm -f /etc/cloudstack/management/server.xml
> > DEBUG:root:execute:ln -s /etc/cloudstack/management/server7-nonssl.xml
> > /etc/cloudstack/management/server.xml
> > DEBUG:root:execute:rm -f /usr/share/cloudstack-management/bin
> > DEBUG:root:execute:ln -s /usr/share/tomcat7/bin
> > /usr/share/cloudstack-management/bin
> > DEBUG:root:execute:rm -f /usr/share/cloudstack-management/lib
> > DEBUG:root:execute:ln -s /usr/share/tomcat7/lib
> > /usr/share/cloudstack-management/lib
> > DEBUG:root:execute:touch /var/run/cloudstack-management.pid
> > DEBUG:root:execute:chown cloud.cloud /var/run/cloudstack-management.pid
> > DEBUG:root:execute:hostname --fqdn
> > DEBUG:root:execute:chown cloud:cloud -R /var/lib/cloudstack/
> > DEBUG:root:execute:chmod +x -R
> > /usr/share/cloudstack-management/webapps/client/WEB-INF/classes/scripts/
> > DEBUG:root:execute:sudo /usr/sbin/service tomcat status
> > DEBUG:root:Failed to execute:● tomcat.service
> >Loaded: not-found (Reason: No such file or directory)
> >Active: inactive (dead)
> > DEBUG:root:execute:sudo /usr/sbin/service tomcat stop
> > DEBUG:root:Failed to execute:Failed to stop tomcat.service: Unit
> > tomcat.service not loaded.
> > DEBUG:root:execute:sudo update-rc.d -f tomcat remove
> > DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
> > DEBUG:root:Failed to execute:● cloudstack-management.service - CloudStack
> > Management Server
> >Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> > enabled)
> >Active: failed (Result: exit-code) since Thu 2017-08-24 18:15:22 CEST;
> > 15min ago
> >  Main PID: 19262 (code=exited, status=1/FAILURE)
> >
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:235)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:307)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:
> > 62)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:43)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > java.lang.reflect.Method.invoke(Method.java:498)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > org.apache.commons.daemon.support.DaemonLoader.load(
> DaemonLoader.java:212)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: 2017-08-24 18:15:22 19264
> > jsvc.exec error: Cannot load daemon
> > Aug 24 18:15:22 servername systemd[1]: cloudstack-management.service:
> main
> > process exited, code=exited, status=1/FAILURE
> > Aug 24 18:15:22 servername systemd[1]: cloudstack-management.service:
> > control process exited, code=exited status=255
> > Aug 24 18:15:22 servername systemd[1]: Unit cloudstack-management.service
> > entered 

Re: Failed to find db.properties

[Jevgeni Zolotarjov]

Debian 8.9
the service is called tomcat7 in debian - not tomcat

On Thu, Aug 24, 2017 at 8:10 PM, Paul Angus 
wrote:

> Hi Jevgeni,
>
> What OS are you running your management server on?  (sorry if it's buried
> in your post somewhere).
> The log suggest that tomcat7 isn't installed, or isn't where CloudStack is
> expecting it to be.
>
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com]
> Sent: 24 August 2017 18:06
> To: users@cloudstack.apache.org
> Subject: Re: Failed to find db.properties
>
> It seems that there is something wrong with your installation. Maybe a
> corrupted file?
>
> On Thu, Aug 24, 2017 at 1:04 PM, Jevgeni Zolotarjov <
> j.zolotar...@gmail.com>
> wrote:
>
> > sorry. this log file is correct
> >
> > DEBUG:root:execute:/usr/bin/lsb_release -i
> > DEBUG:root:execute:hostname -f
> > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8080
> > DEBUG:root:Failed to execute:
> > DEBUG:root:execute:ufw allow 8080/tcp
> > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8250
> > DEBUG:root:Failed to execute:
> > DEBUG:root:execute:ufw allow 8250/tcp
> > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 9090
> > DEBUG:root:Failed to execute:
> > DEBUG:root:execute:ufw allow 9090/tcp
> > DEBUG:root:execute:rm -f /etc/cloudstack/management/server.xml
> > DEBUG:root:execute:ln -s /etc/cloudstack/management/server7-nonssl.xml
> > /etc/cloudstack/management/server.xml
> > DEBUG:root:execute:rm -f /usr/share/cloudstack-management/bin
> > DEBUG:root:execute:ln -s /usr/share/tomcat7/bin
> > /usr/share/cloudstack-management/bin
> > DEBUG:root:execute:rm -f /usr/share/cloudstack-management/lib
> > DEBUG:root:execute:ln -s /usr/share/tomcat7/lib
> > /usr/share/cloudstack-management/lib
> > DEBUG:root:execute:touch /var/run/cloudstack-management.pid
> > DEBUG:root:execute:chown cloud.cloud /var/run/cloudstack-management.pid
> > DEBUG:root:execute:hostname --fqdn
> > DEBUG:root:execute:chown cloud:cloud -R /var/lib/cloudstack/
> > DEBUG:root:execute:chmod +x -R
> > /usr/share/cloudstack-management/webapps/client/WEB-INF/classes/scripts/
> > DEBUG:root:execute:sudo /usr/sbin/service tomcat status
> > DEBUG:root:Failed to execute:● tomcat.service
> >Loaded: not-found (Reason: No such file or directory)
> >Active: inactive (dead)
> > DEBUG:root:execute:sudo /usr/sbin/service tomcat stop
> > DEBUG:root:Failed to execute:Failed to stop tomcat.service: Unit
> > tomcat.service not loaded.
> > DEBUG:root:execute:sudo update-rc.d -f tomcat remove
> > DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
> > DEBUG:root:Failed to execute:● cloudstack-management.service - CloudStack
> > Management Server
> >Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> > enabled)
> >Active: failed (Result: exit-code) since Thu 2017-08-24 18:15:22 CEST;
> > 15min ago
> >  Main PID: 19262 (code=exited, status=1/FAILURE)
> >
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:235)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:307)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:
> > 62)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:43)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > java.lang.reflect.Method.invoke(Method.java:498)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > org.apache.commons.daemon.support.DaemonLoader.load(
> DaemonLoader.java:212)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: 2017-08-24 18:15:22 19264
> > jsvc.exec error: Cannot load daemon
> > Aug 24 18:15:22 servername systemd[1]: cloudstack-management.service:
> main
> > process exited, code=exited, status=1/FAILURE
> > Aug 24 18:15:22 servername systemd[1]: cloudstack-management.service:
> > control process exited, code=exited status=255
> > Aug 24 18:15:22 servername systemd[1]: Unit cloudstack-management.service
> > entered failed state.
> > DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management stop
> > DEBUG:root:execute:sudo update-rc.d -f cloudstack-management remove
> > DEBUG:root:execute:sudo update-rc.d -f cloudstack-management defaults
> > DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
> > DEBUG:root:Failed to execute:● cloudstack-management.service - CloudStack
> > Management Server
> >Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> > enabled)
> >Active: failed 

Re: Failed to find db.properties

[Jevgeni Zolotarjov]

how something can be wrong?
I am installing to virgin clean Debian 8.9 machine
using these repository
http://packages.shapeblue.com/cloudstack/upstream/debian/4.10/
and the guide found on cloudstack website.

The only thing, I did - was installation of Java8

On Thu, Aug 24, 2017 at 8:05 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> It seems that there is something wrong with your installation. Maybe a
> corrupted file?
>
> On Thu, Aug 24, 2017 at 1:04 PM, Jevgeni Zolotarjov <
> j.zolotar...@gmail.com>
> wrote:
>
> > sorry. this log file is correct
> >
> > DEBUG:root:execute:/usr/bin/lsb_release -i
> > DEBUG:root:execute:hostname -f
> > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8080
> > DEBUG:root:Failed to execute:
> > DEBUG:root:execute:ufw allow 8080/tcp
> > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8250
> > DEBUG:root:Failed to execute:
> > DEBUG:root:execute:ufw allow 8250/tcp
> > DEBUG:root:execute:iptables-save|grep INPUT|grep -w 9090
> > DEBUG:root:Failed to execute:
> > DEBUG:root:execute:ufw allow 9090/tcp
> > DEBUG:root:execute:rm -f /etc/cloudstack/management/server.xml
> > DEBUG:root:execute:ln -s /etc/cloudstack/management/server7-nonssl.xml
> > /etc/cloudstack/management/server.xml
> > DEBUG:root:execute:rm -f /usr/share/cloudstack-management/bin
> > DEBUG:root:execute:ln -s /usr/share/tomcat7/bin
> > /usr/share/cloudstack-management/bin
> > DEBUG:root:execute:rm -f /usr/share/cloudstack-management/lib
> > DEBUG:root:execute:ln -s /usr/share/tomcat7/lib
> > /usr/share/cloudstack-management/lib
> > DEBUG:root:execute:touch /var/run/cloudstack-management.pid
> > DEBUG:root:execute:chown cloud.cloud /var/run/cloudstack-management.pid
> > DEBUG:root:execute:hostname --fqdn
> > DEBUG:root:execute:chown cloud:cloud -R /var/lib/cloudstack/
> > DEBUG:root:execute:chmod +x -R
> > /usr/share/cloudstack-management/webapps/client/WEB-INF/classes/scripts/
> > DEBUG:root:execute:sudo /usr/sbin/service tomcat status
> > DEBUG:root:Failed to execute:● tomcat.service
> >Loaded: not-found (Reason: No such file or directory)
> >Active: inactive (dead)
> > DEBUG:root:execute:sudo /usr/sbin/service tomcat stop
> > DEBUG:root:Failed to execute:Failed to stop tomcat.service: Unit
> > tomcat.service not loaded.
> > DEBUG:root:execute:sudo update-rc.d -f tomcat remove
> > DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
> > DEBUG:root:Failed to execute:● cloudstack-management.service - CloudStack
> > Management Server
> >Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> > enabled)
> >Active: failed (Result: exit-code) since Thu 2017-08-24 18:15:22 CEST;
> > 15min ago
> >  Main PID: 19262 (code=exited, status=1/FAILURE)
> >
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:235)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:307)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:
> > 62)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:43)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > java.lang.reflect.Method.invoke(Method.java:498)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > org.apache.commons.daemon.support.DaemonLoader.load(
> DaemonLoader.java:212)
> > Aug 24 18:15:22 servername jsvc.exec[19263]: 2017-08-24 18:15:22 19264
> > jsvc.exec error: Cannot load daemon
> > Aug 24 18:15:22 servername systemd[1]: cloudstack-management.service:
> main
> > process exited, code=exited, status=1/FAILURE
> > Aug 24 18:15:22 servername systemd[1]: cloudstack-management.service:
> > control process exited, code=exited status=255
> > Aug 24 18:15:22 servername systemd[1]: Unit cloudstack-management.service
> > entered failed state.
> > DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management stop
> > DEBUG:root:execute:sudo update-rc.d -f cloudstack-management remove
> > DEBUG:root:execute:sudo update-rc.d -f cloudstack-management defaults
> > DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
> > DEBUG:root:Failed to execute:● cloudstack-management.service - CloudStack
> > Management Server
> >Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> > enabled)
> >Active: failed (Result: exit-code) since Thu 2017-08-24 18:15:22 CEST;
> > 15min ago
> >  Main PID: 19262 (code=exited, status=1/FAILURE)
> >
> > Aug 24 18:15:22 servername jsvc.exec[19263]: at
> > org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:307)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke0(Native 

RE: Failed to find db.properties

[Paul Angus]

Hi Jevgeni,

What OS are you running your management server on?  (sorry if it's buried in 
your post somewhere).
The log suggest that tomcat7 isn't installed, or isn't where CloudStack is 
expecting it to be.


Kind regards,

Paul Angus

paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com] 
Sent: 24 August 2017 18:06
To: users@cloudstack.apache.org
Subject: Re: Failed to find db.properties

It seems that there is something wrong with your installation. Maybe a
corrupted file?

On Thu, Aug 24, 2017 at 1:04 PM, Jevgeni Zolotarjov 
wrote:

> sorry. this log file is correct
>
> DEBUG:root:execute:/usr/bin/lsb_release -i
> DEBUG:root:execute:hostname -f
> DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8080
> DEBUG:root:Failed to execute:
> DEBUG:root:execute:ufw allow 8080/tcp
> DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8250
> DEBUG:root:Failed to execute:
> DEBUG:root:execute:ufw allow 8250/tcp
> DEBUG:root:execute:iptables-save|grep INPUT|grep -w 9090
> DEBUG:root:Failed to execute:
> DEBUG:root:execute:ufw allow 9090/tcp
> DEBUG:root:execute:rm -f /etc/cloudstack/management/server.xml
> DEBUG:root:execute:ln -s /etc/cloudstack/management/server7-nonssl.xml
> /etc/cloudstack/management/server.xml
> DEBUG:root:execute:rm -f /usr/share/cloudstack-management/bin
> DEBUG:root:execute:ln -s /usr/share/tomcat7/bin
> /usr/share/cloudstack-management/bin
> DEBUG:root:execute:rm -f /usr/share/cloudstack-management/lib
> DEBUG:root:execute:ln -s /usr/share/tomcat7/lib
> /usr/share/cloudstack-management/lib
> DEBUG:root:execute:touch /var/run/cloudstack-management.pid
> DEBUG:root:execute:chown cloud.cloud /var/run/cloudstack-management.pid
> DEBUG:root:execute:hostname --fqdn
> DEBUG:root:execute:chown cloud:cloud -R /var/lib/cloudstack/
> DEBUG:root:execute:chmod +x -R
> /usr/share/cloudstack-management/webapps/client/WEB-INF/classes/scripts/
> DEBUG:root:execute:sudo /usr/sbin/service tomcat status
> DEBUG:root:Failed to execute:● tomcat.service
>Loaded: not-found (Reason: No such file or directory)
>Active: inactive (dead)
> DEBUG:root:execute:sudo /usr/sbin/service tomcat stop
> DEBUG:root:Failed to execute:Failed to stop tomcat.service: Unit
> tomcat.service not loaded.
> DEBUG:root:execute:sudo update-rc.d -f tomcat remove
> DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
> DEBUG:root:Failed to execute:● cloudstack-management.service - CloudStack
> Management Server
>Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> enabled)
>Active: failed (Result: exit-code) since Thu 2017-08-24 18:15:22 CEST;
> 15min ago
>  Main PID: 19262 (code=exited, status=1/FAILURE)
>
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:235)
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:307)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 62)
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> java.lang.reflect.Method.invoke(Method.java:498)
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:212)
> Aug 24 18:15:22 servername jsvc.exec[19263]: 2017-08-24 18:15:22 19264
> jsvc.exec error: Cannot load daemon
> Aug 24 18:15:22 servername systemd[1]: cloudstack-management.service: main
> process exited, code=exited, status=1/FAILURE
> Aug 24 18:15:22 servername systemd[1]: cloudstack-management.service:
> control process exited, code=exited status=255
> Aug 24 18:15:22 servername systemd[1]: Unit cloudstack-management.service
> entered failed state.
> DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management stop
> DEBUG:root:execute:sudo update-rc.d -f cloudstack-management remove
> DEBUG:root:execute:sudo update-rc.d -f cloudstack-management defaults
> DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
> DEBUG:root:Failed to execute:● cloudstack-management.service - CloudStack
> Management Server
>Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> enabled)
>Active: failed (Result: exit-code) since Thu 2017-08-24 18:15:22 CEST;
> 15min ago
>  Main PID: 19262 (code=exited, status=1/FAILURE)
>
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:307)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native 

Re: Failed to find db.properties

[Rafael Weingärtner]

It seems that there is something wrong with your installation. Maybe a
corrupted file?

On Thu, Aug 24, 2017 at 1:04 PM, Jevgeni Zolotarjov 
wrote:

> sorry. this log file is correct
>
> DEBUG:root:execute:/usr/bin/lsb_release -i
> DEBUG:root:execute:hostname -f
> DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8080
> DEBUG:root:Failed to execute:
> DEBUG:root:execute:ufw allow 8080/tcp
> DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8250
> DEBUG:root:Failed to execute:
> DEBUG:root:execute:ufw allow 8250/tcp
> DEBUG:root:execute:iptables-save|grep INPUT|grep -w 9090
> DEBUG:root:Failed to execute:
> DEBUG:root:execute:ufw allow 9090/tcp
> DEBUG:root:execute:rm -f /etc/cloudstack/management/server.xml
> DEBUG:root:execute:ln -s /etc/cloudstack/management/server7-nonssl.xml
> /etc/cloudstack/management/server.xml
> DEBUG:root:execute:rm -f /usr/share/cloudstack-management/bin
> DEBUG:root:execute:ln -s /usr/share/tomcat7/bin
> /usr/share/cloudstack-management/bin
> DEBUG:root:execute:rm -f /usr/share/cloudstack-management/lib
> DEBUG:root:execute:ln -s /usr/share/tomcat7/lib
> /usr/share/cloudstack-management/lib
> DEBUG:root:execute:touch /var/run/cloudstack-management.pid
> DEBUG:root:execute:chown cloud.cloud /var/run/cloudstack-management.pid
> DEBUG:root:execute:hostname --fqdn
> DEBUG:root:execute:chown cloud:cloud -R /var/lib/cloudstack/
> DEBUG:root:execute:chmod +x -R
> /usr/share/cloudstack-management/webapps/client/WEB-INF/classes/scripts/
> DEBUG:root:execute:sudo /usr/sbin/service tomcat status
> DEBUG:root:Failed to execute:● tomcat.service
>Loaded: not-found (Reason: No such file or directory)
>Active: inactive (dead)
> DEBUG:root:execute:sudo /usr/sbin/service tomcat stop
> DEBUG:root:Failed to execute:Failed to stop tomcat.service: Unit
> tomcat.service not loaded.
> DEBUG:root:execute:sudo update-rc.d -f tomcat remove
> DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
> DEBUG:root:Failed to execute:● cloudstack-management.service - CloudStack
> Management Server
>Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> enabled)
>Active: failed (Result: exit-code) since Thu 2017-08-24 18:15:22 CEST;
> 15min ago
>  Main PID: 19262 (code=exited, status=1/FAILURE)
>
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:235)
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:307)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 62)
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> java.lang.reflect.Method.invoke(Method.java:498)
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:212)
> Aug 24 18:15:22 servername jsvc.exec[19263]: 2017-08-24 18:15:22 19264
> jsvc.exec error: Cannot load daemon
> Aug 24 18:15:22 servername systemd[1]: cloudstack-management.service: main
> process exited, code=exited, status=1/FAILURE
> Aug 24 18:15:22 servername systemd[1]: cloudstack-management.service:
> control process exited, code=exited status=255
> Aug 24 18:15:22 servername systemd[1]: Unit cloudstack-management.service
> entered failed state.
> DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management stop
> DEBUG:root:execute:sudo update-rc.d -f cloudstack-management remove
> DEBUG:root:execute:sudo update-rc.d -f cloudstack-management defaults
> DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
> DEBUG:root:Failed to execute:● cloudstack-management.service - CloudStack
> Management Server
>Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> enabled)
>Active: failed (Result: exit-code) since Thu 2017-08-24 18:15:22 CEST;
> 15min ago
>  Main PID: 19262 (code=exited, status=1/FAILURE)
>
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:307)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 62)
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> java.lang.reflect.Method.invoke(Method.java:498)
> Aug 24 18:15:22 servername jsvc.exec[19263]: at
> org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:212)
> Aug 24 18:15:22 servername 

Re: Failed to find db.properties

[Jevgeni Zolotarjov]

sorry. this log file is correct

DEBUG:root:execute:/usr/bin/lsb_release -i
DEBUG:root:execute:hostname -f
DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8080
DEBUG:root:Failed to execute:
DEBUG:root:execute:ufw allow 8080/tcp
DEBUG:root:execute:iptables-save|grep INPUT|grep -w 8250
DEBUG:root:Failed to execute:
DEBUG:root:execute:ufw allow 8250/tcp
DEBUG:root:execute:iptables-save|grep INPUT|grep -w 9090
DEBUG:root:Failed to execute:
DEBUG:root:execute:ufw allow 9090/tcp
DEBUG:root:execute:rm -f /etc/cloudstack/management/server.xml
DEBUG:root:execute:ln -s /etc/cloudstack/management/server7-nonssl.xml
/etc/cloudstack/management/server.xml
DEBUG:root:execute:rm -f /usr/share/cloudstack-management/bin
DEBUG:root:execute:ln -s /usr/share/tomcat7/bin
/usr/share/cloudstack-management/bin
DEBUG:root:execute:rm -f /usr/share/cloudstack-management/lib
DEBUG:root:execute:ln -s /usr/share/tomcat7/lib
/usr/share/cloudstack-management/lib
DEBUG:root:execute:touch /var/run/cloudstack-management.pid
DEBUG:root:execute:chown cloud.cloud /var/run/cloudstack-management.pid
DEBUG:root:execute:hostname --fqdn
DEBUG:root:execute:chown cloud:cloud -R /var/lib/cloudstack/
DEBUG:root:execute:chmod +x -R
/usr/share/cloudstack-management/webapps/client/WEB-INF/classes/scripts/
DEBUG:root:execute:sudo /usr/sbin/service tomcat status
DEBUG:root:Failed to execute:● tomcat.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
DEBUG:root:execute:sudo /usr/sbin/service tomcat stop
DEBUG:root:Failed to execute:Failed to stop tomcat.service: Unit
tomcat.service not loaded.
DEBUG:root:execute:sudo update-rc.d -f tomcat remove
DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
DEBUG:root:Failed to execute:● cloudstack-management.service - CloudStack
Management Server
   Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
enabled)
   Active: failed (Result: exit-code) since Thu 2017-08-24 18:15:22 CEST;
15min ago
 Main PID: 19262 (code=exited, status=1/FAILURE)

Aug 24 18:15:22 servername jsvc.exec[19263]: at
org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:235)
Aug 24 18:15:22 servername jsvc.exec[19263]: at
org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:307)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Aug 24 18:15:22 servername jsvc.exec[19263]: at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Aug 24 18:15:22 servername jsvc.exec[19263]: at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Aug 24 18:15:22 servername jsvc.exec[19263]: at
java.lang.reflect.Method.invoke(Method.java:498)
Aug 24 18:15:22 servername jsvc.exec[19263]: at
org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:212)
Aug 24 18:15:22 servername jsvc.exec[19263]: 2017-08-24 18:15:22 19264
jsvc.exec error: Cannot load daemon
Aug 24 18:15:22 servername systemd[1]: cloudstack-management.service: main
process exited, code=exited, status=1/FAILURE
Aug 24 18:15:22 servername systemd[1]: cloudstack-management.service:
control process exited, code=exited status=255
Aug 24 18:15:22 servername systemd[1]: Unit cloudstack-management.service
entered failed state.
DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management stop
DEBUG:root:execute:sudo update-rc.d -f cloudstack-management remove
DEBUG:root:execute:sudo update-rc.d -f cloudstack-management defaults
DEBUG:root:execute:sudo /usr/sbin/service cloudstack-management status
DEBUG:root:Failed to execute:● cloudstack-management.service - CloudStack
Management Server
   Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
enabled)
   Active: failed (Result: exit-code) since Thu 2017-08-24 18:15:22 CEST;
15min ago
 Main PID: 19262 (code=exited, status=1/FAILURE)

Aug 24 18:15:22 servername jsvc.exec[19263]: at
org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:307)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Aug 24 18:15:22 servername jsvc.exec[19263]: at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Aug 24 18:15:22 servername jsvc.exec[19263]: at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Aug 24 18:15:22 servername jsvc.exec[19263]: at
java.lang.reflect.Method.invoke(Method.java:498)
Aug 24 18:15:22 servername jsvc.exec[19263]: at
org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:212)
Aug 24 18:15:22 servername jsvc.exec[19263]: 2017-08-24 18:15:22 19264
jsvc.exec error: Cannot load daemon
Aug 24 18:15:22 servername systemd[1]: cloudstack-management.service: main
process exited, code=exited, status=1/FAILURE
Aug 24 18:15:22 servername systemd[1]: cloudstack-management.service:
control process exited, code=exited status=255
Aug 24 18:15:22 servername systemd[1]: Unit 

Re: Failed to find db.properties

[Jevgeni Zolotarjov]

Aug 22, 2017 7:34:17 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with directory [/usr/share/tomcat7/common/classes],
exists: [false], isDirectory: [false], canRead: [false]
Aug 22, 2017 7:34:17 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with directory [/usr/share/tomcat7/common], exists:
[false], isDirectory: [false], canRead: [false]
Aug 22, 2017 7:34:17 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with directory [/usr/share/tomcat7/server/classes],
exists: [false], isDirectory: [false], canRead: [false]
Aug 22, 2017 7:34:17 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with directory [/usr/share/tomcat7/server], exists:
[false], isDirectory: [false], canRead: [false]
Aug 22, 2017 7:34:17 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with directory [/usr/share/tomcat7/shared/classes],
exists: [false], isDirectory: [false], canRead: [false]
Aug 22, 2017 7:34:17 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with directory [/usr/share/tomcat7/shared], exists:
[false], isDirectory: [false], canRead: [false]
Aug 22, 2017 7:34:18 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Aug 22, 2017 7:34:18 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 345 ms
Aug 22, 2017 7:34:18 PM org.apache.catalina.core.StandardService
startInternal
INFO: Starting service Catalina
Aug 22, 2017 7:34:18 PM org.apache.catalina.core.StandardEngine
startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.56 (Debian)
Aug 22, 2017 7:34:18 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory /var/lib/tomcat7/webapps/ROOT
Aug 22, 2017 7:34:18 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory /var/lib/tomcat7/webapps/ROOT
has finished in 398 ms
Aug 22, 2017 7:34:18 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Aug 22, 2017 7:34:18 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 437 ms
Aug 22, 2017 7:34:23 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-8080"]
Aug 22, 2017 7:34:23 PM org.apache.catalina.core.StandardService
stopInternal
INFO: Stopping service Catalina
Aug 22, 2017 7:34:23 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-8080"]
Aug 22, 2017 7:34:23 PM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-8080"]
Aug 22, 2017 7:42:24 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with directory [/usr/share/tomcat7/common/classes],
exists: [false], isDirectory: [false], canRead: [false]
Aug 22, 2017 7:42:24 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with directory [/usr/share/tomcat7/common], exists:
[false], isDirectory: [false], canRead: [false]
Aug 22, 2017 7:42:25 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with directory [/usr/share/tomcat7/server/classes],
exists: [false], isDirectory: [false], canRead: [false]
Aug 22, 2017 7:42:25 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with directory [/usr/share/tomcat7/server], exists:
[false], isDirectory: [false], canRead: [false]
Aug 22, 2017 7:42:25 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with directory [/usr/share/tomcat7/shared/classes],
exists: [false], isDirectory: [false], canRead: [false]
Aug 22, 2017 7:42:25 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with directory [/usr/share/tomcat7/shared], exists:
[false], isDirectory: [false], canRead: [false]
Aug 22, 2017 7:42:26 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Aug 22, 2017 7:42:26 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1158 ms
Aug 22, 2017 7:42:26 PM org.apache.catalina.core.StandardService
startInternal
INFO: Starting service Catalina
Aug 22, 2017 7:42:26 PM org.apache.catalina.core.StandardEngine
startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.56 (Debian)
Aug 22, 2017 7:42:27 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory /var/lib/tomcat7/webapps/ROOT
Aug 22, 2017 7:42:29 PM org.apache.catalina.util.SessionIdGenerator
createSecureRandom
INFO: Creation of SecureRandom instance for session ID generation using
[SHA1PRNG] took [1,376] milliseconds.
Aug 22, 2017 7:42:29 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deployment of web application directory /var/lib/tomcat7/webapps/ROOT
has finished in 1,902 ms
Aug 22, 2017 7:42:29 PM org.apache.coyote.AbstractProtocol start

Re: Failed to find db.properties

[Rafael Weingärtner]

Did you send the log file?
I think it is not possible to send attachments through this mailing list.

On Thu, Aug 24, 2017 at 12:39 PM, Jevgeni Zolotarjov  wrote:

> I guess, this management setup log file explains the root of evil.
> There are many errors, though setup reports everything is OK.
>
>
>
> On Thu, Aug 24, 2017 at 4:12 PM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
>> db.properties is there.
>> Can you post your log files somewhere?
>>
>> On Thu, Aug 24, 2017 at 8:51 AM, Jevgeni Zolotarjov <
>> j.zolotar...@gmail.com>
>> wrote:
>>
>> > This is what I have in
>> > /etc/cloudstack/
>> > /etc/cloudstack/management/
>> >
>> > root@servername:/var/cache/tomcat7/Catalina/localhost/client# cd
>> > /etc/cloudstack/
>> > root@servername:/etc/cloudstack# ls -al
>> > total 20
>> > drwxr-xr-x   5 root root 4096 Aug 23 16:31 .
>> > drwxr-xr-x 100 root root 4096 Aug 23 19:26 ..
>> > drwxr-xr-x   2 root root 4096 Aug 23 14:27 agent
>> > drwxr-xr-x   2 root root 4096 Aug 24 09:23 management
>> > drwxr-xr-x   2 root root 4096 Aug 22 19:34 usage
>> > root@servername:/etc/cloudstack# cd management/
>> > root@servername:/etc/cloudstack/management# ls -al
>> > total 176
>> > drwxr-xr-x 2 root root   4096 Aug 24 09:23 .
>> > drwxr-xr-x 5 root root   4096 Aug 23 16:31 ..
>> > -rw-r--r-- 1 root root   8945 Jul 12 12:33 catalina.policy
>> > -rw-r--r-- 1 root root   3795 Jul 12 12:33 catalina.properties
>> > -rw-r--r-- 1 root root   1649 Jul 12 12:33 classpath.conf
>> > -rw-r--r-- 1 root root   1435 Jul 12 12:33 context.xml
>> > -rw-r- 1 root cloud  3273 Jul 12 12:33 db.properties
>> > -rw-r--r-- 1 root root  23292 Jul 12 12:33 ehcache.xml
>> > -rw-r--r-- 1 root root976 Jul 12 12:33 environment.properties
>> > -rw-r--r-- 1 root root927 Jul 12 12:33 java.security.ciphers
>> > -rw-r--r-- 1 root root   7467 Jul 12 12:33 log4j-cloud.xml
>> > -rw-r--r-- 1 root root   3257 Jul 12 12:33 logging.properties
>> > -rw-r--r-- 1 root root   6722 Jul 12 12:33 server7-nonssl.xml
>> > -rw-r--r-- 1 root root   7251 Jul 12 12:33 server7-ssl.xml
>> > -rw-r--r-- 1 root root   6767 Jul 12 12:33 server-nonssl.xml
>> > -rw-r--r-- 1 root root   7300 Jul 12 12:33 server-ssl.xml
>> > lrwxrwxrwx 1 root root 45 Aug 24 09:23 server.xml ->
>> > /etc/cloudstack/management/server7-nonssl.xml
>> > lrwxrwxrwx 1 root root 46 Aug 23 16:37 tomcat6.conf ->
>> > /etc/cloudstack/management/tomcat6-nonssl.conf
>> > -rw-r--r-- 1 root root   2692 Jul 12 12:33 tomcat6-nonssl.conf
>> > -rw-r--r-- 1 root root   2821 Jul 12 12:33 tomcat6-ssl.conf
>> > -rw-r--r-- 1 root root   1383 Jul 12 12:33 tomcat-users.xml
>> > -rw-r--r-- 1 root root  50428 Jul 12 12:33 web.xml
>> >
>> >
>> > On Thu, Aug 24, 2017 at 2:13 PM, Rafael Weingärtner <
>> > rafaelweingart...@gmail.com> wrote:
>> >
>> > > Is there a db.properties in /etc/cloudstack.. folder?
>> > >
>> > > On Thu, Aug 24, 2017 at 3:27 AM, Jevgeni Zolotarjov <
>> > > j.zolotar...@gmail.com>
>> > > wrote:
>> > >
>> > > > Did that "setup --tomcat7" now.
>> > > > Output:
>> > > > Starting to configure CloudStack Management Server:
>> > > > Configure Firewall ...[OK]
>> > > > Configure CloudStack Management Server ...[OK]
>> > > > CloudStack Management Server setup is Done!
>> > > >
>> > > > But no difference, when I try to run client application. Absolutely
>> the
>> > > > same result in catalina.log - Failed to find db.properties
>> > > >
>> > > >
>> > > >
>> > > > On Thu, Aug 24, 2017 at 1:24 AM, ilya > >
>> > > > wrote:
>> > > >
>> > > > > Rafael has a point there - please try with tomcat7
>> > > > >
>> > > > > Also - please look into catalina.out/log for further debugging
>> info.
>> > > > >
>> > > > > On 8/23/17 9:23 AM, Rafael Weingärtner wrote:
>> > > > > > did you run setup-management --tomcat7?
>> > > > > >
>> > > > > > On Wed, Aug 23, 2017 at 12:20 PM, Jevgeni Zolotarjov <
>> > > > > j.zolotar...@gmail.com
>> > > > > >> wrote:
>> > > > > >
>> > > > > >> Yes, I did, as it is suggested in the guide:
>> > > > > >> cloudstack-setup-database then setup-management
>> > > > > >>
>> > > > > >>
>> > > > > >> On Aug 23, 2017 7:11 PM, "Rafael Weingärtner" <
>> > > > > rafaelweingart...@gmail.com
>> > > > > >>>
>> > > > > >> wrote:
>> > > > > >>
>> > > > > >> did you run cloudstack-setup-database and ...setup-management?
>> > > > > >>
>> > > > > >>
>> > > > > >> On Wed, Aug 23, 2017 at 11:16 AM, Jevgeni Zolotarjov <
>> > > > > >> j.zolotar...@gmail.com
>> > > > > >>> wrote:
>> > > > > >>
>> > > > > >>> Here you go
>> > > > > >>>
>> > > > > >>> management-server.log is not available, which probably means,
>> the
>> > > > > >>> application did not reach that far and exited due to missing
>> DB
>> > > > access
>> > > > > >>>
>> > > > > >>> On Wed, Aug 23, 2017 at 6:03 PM, Gabriel Beims Bräscher <
>> > > > > >>> gabrasc...@gmail.com> wrote:
>> > > > > >>>
>> > > > >  Hi Jevgeni,
>> > > > > 
>> > > > >  Can you 

Re: Failed to find db.properties

[Jevgeni Zolotarjov]

I guess, this management setup log file explains the root of evil.
There are many errors, though setup reports everything is OK.



On Thu, Aug 24, 2017 at 4:12 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> db.properties is there.
> Can you post your log files somewhere?
>
> On Thu, Aug 24, 2017 at 8:51 AM, Jevgeni Zolotarjov <
> j.zolotar...@gmail.com>
> wrote:
>
> > This is what I have in
> > /etc/cloudstack/
> > /etc/cloudstack/management/
> >
> > root@servername:/var/cache/tomcat7/Catalina/localhost/client# cd
> > /etc/cloudstack/
> > root@servername:/etc/cloudstack# ls -al
> > total 20
> > drwxr-xr-x   5 root root 4096 Aug 23 16:31 .
> > drwxr-xr-x 100 root root 4096 Aug 23 19:26 ..
> > drwxr-xr-x   2 root root 4096 Aug 23 14:27 agent
> > drwxr-xr-x   2 root root 4096 Aug 24 09:23 management
> > drwxr-xr-x   2 root root 4096 Aug 22 19:34 usage
> > root@servername:/etc/cloudstack# cd management/
> > root@servername:/etc/cloudstack/management# ls -al
> > total 176
> > drwxr-xr-x 2 root root   4096 Aug 24 09:23 .
> > drwxr-xr-x 5 root root   4096 Aug 23 16:31 ..
> > -rw-r--r-- 1 root root   8945 Jul 12 12:33 catalina.policy
> > -rw-r--r-- 1 root root   3795 Jul 12 12:33 catalina.properties
> > -rw-r--r-- 1 root root   1649 Jul 12 12:33 classpath.conf
> > -rw-r--r-- 1 root root   1435 Jul 12 12:33 context.xml
> > -rw-r- 1 root cloud  3273 Jul 12 12:33 db.properties
> > -rw-r--r-- 1 root root  23292 Jul 12 12:33 ehcache.xml
> > -rw-r--r-- 1 root root976 Jul 12 12:33 environment.properties
> > -rw-r--r-- 1 root root927 Jul 12 12:33 java.security.ciphers
> > -rw-r--r-- 1 root root   7467 Jul 12 12:33 log4j-cloud.xml
> > -rw-r--r-- 1 root root   3257 Jul 12 12:33 logging.properties
> > -rw-r--r-- 1 root root   6722 Jul 12 12:33 server7-nonssl.xml
> > -rw-r--r-- 1 root root   7251 Jul 12 12:33 server7-ssl.xml
> > -rw-r--r-- 1 root root   6767 Jul 12 12:33 server-nonssl.xml
> > -rw-r--r-- 1 root root   7300 Jul 12 12:33 server-ssl.xml
> > lrwxrwxrwx 1 root root 45 Aug 24 09:23 server.xml ->
> > /etc/cloudstack/management/server7-nonssl.xml
> > lrwxrwxrwx 1 root root 46 Aug 23 16:37 tomcat6.conf ->
> > /etc/cloudstack/management/tomcat6-nonssl.conf
> > -rw-r--r-- 1 root root   2692 Jul 12 12:33 tomcat6-nonssl.conf
> > -rw-r--r-- 1 root root   2821 Jul 12 12:33 tomcat6-ssl.conf
> > -rw-r--r-- 1 root root   1383 Jul 12 12:33 tomcat-users.xml
> > -rw-r--r-- 1 root root  50428 Jul 12 12:33 web.xml
> >
> >
> > On Thu, Aug 24, 2017 at 2:13 PM, Rafael Weingärtner <
> > rafaelweingart...@gmail.com> wrote:
> >
> > > Is there a db.properties in /etc/cloudstack.. folder?
> > >
> > > On Thu, Aug 24, 2017 at 3:27 AM, Jevgeni Zolotarjov <
> > > j.zolotar...@gmail.com>
> > > wrote:
> > >
> > > > Did that "setup --tomcat7" now.
> > > > Output:
> > > > Starting to configure CloudStack Management Server:
> > > > Configure Firewall ...[OK]
> > > > Configure CloudStack Management Server ...[OK]
> > > > CloudStack Management Server setup is Done!
> > > >
> > > > But no difference, when I try to run client application. Absolutely
> the
> > > > same result in catalina.log - Failed to find db.properties
> > > >
> > > >
> > > >
> > > > On Thu, Aug 24, 2017 at 1:24 AM, ilya 
> > > > wrote:
> > > >
> > > > > Rafael has a point there - please try with tomcat7
> > > > >
> > > > > Also - please look into catalina.out/log for further debugging
> info.
> > > > >
> > > > > On 8/23/17 9:23 AM, Rafael Weingärtner wrote:
> > > > > > did you run setup-management --tomcat7?
> > > > > >
> > > > > > On Wed, Aug 23, 2017 at 12:20 PM, Jevgeni Zolotarjov <
> > > > > j.zolotar...@gmail.com
> > > > > >> wrote:
> > > > > >
> > > > > >> Yes, I did, as it is suggested in the guide:
> > > > > >> cloudstack-setup-database then setup-management
> > > > > >>
> > > > > >>
> > > > > >> On Aug 23, 2017 7:11 PM, "Rafael Weingärtner" <
> > > > > rafaelweingart...@gmail.com
> > > > > >>>
> > > > > >> wrote:
> > > > > >>
> > > > > >> did you run cloudstack-setup-database and ...setup-management?
> > > > > >>
> > > > > >>
> > > > > >> On Wed, Aug 23, 2017 at 11:16 AM, Jevgeni Zolotarjov <
> > > > > >> j.zolotar...@gmail.com
> > > > > >>> wrote:
> > > > > >>
> > > > > >>> Here you go
> > > > > >>>
> > > > > >>> management-server.log is not available, which probably means,
> the
> > > > > >>> application did not reach that far and exited due to missing DB
> > > > access
> > > > > >>>
> > > > > >>> On Wed, Aug 23, 2017 at 6:03 PM, Gabriel Beims Bräscher <
> > > > > >>> gabrasc...@gmail.com> wrote:
> > > > > >>>
> > > > >  Hi Jevgeni,
> > > > > 
> > > > >  Can you share with us some log files (catalina.log,
> > > > > >> management-server.log
> > > > >  and others that might be useful)?
> > > > > 
> > > > > 
> > > > >  2017-08-23 11:53 GMT-03:00 Jevgeni Zolotarjov <
> > > > j.zolotar...@gmail.com
> > > > > >:
> > > > > 
> > > > > > Hi
> > > > > >
> > > > > 

Re: Failed to find db.properties

[Rafael Weingärtner]

db.properties is there.
Can you post your log files somewhere?

On Thu, Aug 24, 2017 at 8:51 AM, Jevgeni Zolotarjov 
wrote:

> This is what I have in
> /etc/cloudstack/
> /etc/cloudstack/management/
>
> root@servername:/var/cache/tomcat7/Catalina/localhost/client# cd
> /etc/cloudstack/
> root@servername:/etc/cloudstack# ls -al
> total 20
> drwxr-xr-x   5 root root 4096 Aug 23 16:31 .
> drwxr-xr-x 100 root root 4096 Aug 23 19:26 ..
> drwxr-xr-x   2 root root 4096 Aug 23 14:27 agent
> drwxr-xr-x   2 root root 4096 Aug 24 09:23 management
> drwxr-xr-x   2 root root 4096 Aug 22 19:34 usage
> root@servername:/etc/cloudstack# cd management/
> root@servername:/etc/cloudstack/management# ls -al
> total 176
> drwxr-xr-x 2 root root   4096 Aug 24 09:23 .
> drwxr-xr-x 5 root root   4096 Aug 23 16:31 ..
> -rw-r--r-- 1 root root   8945 Jul 12 12:33 catalina.policy
> -rw-r--r-- 1 root root   3795 Jul 12 12:33 catalina.properties
> -rw-r--r-- 1 root root   1649 Jul 12 12:33 classpath.conf
> -rw-r--r-- 1 root root   1435 Jul 12 12:33 context.xml
> -rw-r- 1 root cloud  3273 Jul 12 12:33 db.properties
> -rw-r--r-- 1 root root  23292 Jul 12 12:33 ehcache.xml
> -rw-r--r-- 1 root root976 Jul 12 12:33 environment.properties
> -rw-r--r-- 1 root root927 Jul 12 12:33 java.security.ciphers
> -rw-r--r-- 1 root root   7467 Jul 12 12:33 log4j-cloud.xml
> -rw-r--r-- 1 root root   3257 Jul 12 12:33 logging.properties
> -rw-r--r-- 1 root root   6722 Jul 12 12:33 server7-nonssl.xml
> -rw-r--r-- 1 root root   7251 Jul 12 12:33 server7-ssl.xml
> -rw-r--r-- 1 root root   6767 Jul 12 12:33 server-nonssl.xml
> -rw-r--r-- 1 root root   7300 Jul 12 12:33 server-ssl.xml
> lrwxrwxrwx 1 root root 45 Aug 24 09:23 server.xml ->
> /etc/cloudstack/management/server7-nonssl.xml
> lrwxrwxrwx 1 root root 46 Aug 23 16:37 tomcat6.conf ->
> /etc/cloudstack/management/tomcat6-nonssl.conf
> -rw-r--r-- 1 root root   2692 Jul 12 12:33 tomcat6-nonssl.conf
> -rw-r--r-- 1 root root   2821 Jul 12 12:33 tomcat6-ssl.conf
> -rw-r--r-- 1 root root   1383 Jul 12 12:33 tomcat-users.xml
> -rw-r--r-- 1 root root  50428 Jul 12 12:33 web.xml
>
>
> On Thu, Aug 24, 2017 at 2:13 PM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > Is there a db.properties in /etc/cloudstack.. folder?
> >
> > On Thu, Aug 24, 2017 at 3:27 AM, Jevgeni Zolotarjov <
> > j.zolotar...@gmail.com>
> > wrote:
> >
> > > Did that "setup --tomcat7" now.
> > > Output:
> > > Starting to configure CloudStack Management Server:
> > > Configure Firewall ...[OK]
> > > Configure CloudStack Management Server ...[OK]
> > > CloudStack Management Server setup is Done!
> > >
> > > But no difference, when I try to run client application. Absolutely the
> > > same result in catalina.log - Failed to find db.properties
> > >
> > >
> > >
> > > On Thu, Aug 24, 2017 at 1:24 AM, ilya 
> > > wrote:
> > >
> > > > Rafael has a point there - please try with tomcat7
> > > >
> > > > Also - please look into catalina.out/log for further debugging info.
> > > >
> > > > On 8/23/17 9:23 AM, Rafael Weingärtner wrote:
> > > > > did you run setup-management --tomcat7?
> > > > >
> > > > > On Wed, Aug 23, 2017 at 12:20 PM, Jevgeni Zolotarjov <
> > > > j.zolotar...@gmail.com
> > > > >> wrote:
> > > > >
> > > > >> Yes, I did, as it is suggested in the guide:
> > > > >> cloudstack-setup-database then setup-management
> > > > >>
> > > > >>
> > > > >> On Aug 23, 2017 7:11 PM, "Rafael Weingärtner" <
> > > > rafaelweingart...@gmail.com
> > > > >>>
> > > > >> wrote:
> > > > >>
> > > > >> did you run cloudstack-setup-database and ...setup-management?
> > > > >>
> > > > >>
> > > > >> On Wed, Aug 23, 2017 at 11:16 AM, Jevgeni Zolotarjov <
> > > > >> j.zolotar...@gmail.com
> > > > >>> wrote:
> > > > >>
> > > > >>> Here you go
> > > > >>>
> > > > >>> management-server.log is not available, which probably means, the
> > > > >>> application did not reach that far and exited due to missing DB
> > > access
> > > > >>>
> > > > >>> On Wed, Aug 23, 2017 at 6:03 PM, Gabriel Beims Bräscher <
> > > > >>> gabrasc...@gmail.com> wrote:
> > > > >>>
> > > >  Hi Jevgeni,
> > > > 
> > > >  Can you share with us some log files (catalina.log,
> > > > >> management-server.log
> > > >  and others that might be useful)?
> > > > 
> > > > 
> > > >  2017-08-23 11:53 GMT-03:00 Jevgeni Zolotarjov <
> > > j.zolotar...@gmail.com
> > > > >:
> > > > 
> > > > > Hi
> > > > >
> > > > > I am installing Cloudstack 4.10 on Debian Jessie using guides
> > from
> > > > > http://cloudstack-installation.readthedocs.io/en/latest/
> > > >  management-server/
> > > > > index.html
> > > > >
> > > > > Apparently the installation process was smooth. But I cannot
> get
> > > > >> client
> > > > > running on tomcat7
> > > > > From catalina.out log file I can read
> > > > >
> > > > > Failed to find db.properties
> > > > >

SystemVMs in Alert State | 4.7.1 release

[Vijay Sachdeva]

Dear Team,

Has anyone gone through this, i.e. system VMs agent state never come up until n 
unless you ping the management server IP from system VM. If you don’t ping the 
same and when you run the “ssvm_check.sh” script it shows not connectivity to 
port 8250.

The time you ping the management server IP and run the script, it connects to 
port 8250 and agent state comes to UP state.

Thanks

Vijay Sachdeva
Consultant - Cloud & Virtualisation


A-4, LGF, C.R.Park, New Delhi - 110019 
24x7 011-40551409 | M +918826699409
www.indiqus.com 

Re: Failed to find db.properties

[Jevgeni Zolotarjov]

This is what I have in
/etc/cloudstack/
/etc/cloudstack/management/

root@servername:/var/cache/tomcat7/Catalina/localhost/client# cd
/etc/cloudstack/
root@servername:/etc/cloudstack# ls -al
total 20
drwxr-xr-x   5 root root 4096 Aug 23 16:31 .
drwxr-xr-x 100 root root 4096 Aug 23 19:26 ..
drwxr-xr-x   2 root root 4096 Aug 23 14:27 agent
drwxr-xr-x   2 root root 4096 Aug 24 09:23 management
drwxr-xr-x   2 root root 4096 Aug 22 19:34 usage
root@servername:/etc/cloudstack# cd management/
root@servername:/etc/cloudstack/management# ls -al
total 176
drwxr-xr-x 2 root root   4096 Aug 24 09:23 .
drwxr-xr-x 5 root root   4096 Aug 23 16:31 ..
-rw-r--r-- 1 root root   8945 Jul 12 12:33 catalina.policy
-rw-r--r-- 1 root root   3795 Jul 12 12:33 catalina.properties
-rw-r--r-- 1 root root   1649 Jul 12 12:33 classpath.conf
-rw-r--r-- 1 root root   1435 Jul 12 12:33 context.xml
-rw-r- 1 root cloud  3273 Jul 12 12:33 db.properties
-rw-r--r-- 1 root root  23292 Jul 12 12:33 ehcache.xml
-rw-r--r-- 1 root root976 Jul 12 12:33 environment.properties
-rw-r--r-- 1 root root927 Jul 12 12:33 java.security.ciphers
-rw-r--r-- 1 root root   7467 Jul 12 12:33 log4j-cloud.xml
-rw-r--r-- 1 root root   3257 Jul 12 12:33 logging.properties
-rw-r--r-- 1 root root   6722 Jul 12 12:33 server7-nonssl.xml
-rw-r--r-- 1 root root   7251 Jul 12 12:33 server7-ssl.xml
-rw-r--r-- 1 root root   6767 Jul 12 12:33 server-nonssl.xml
-rw-r--r-- 1 root root   7300 Jul 12 12:33 server-ssl.xml
lrwxrwxrwx 1 root root 45 Aug 24 09:23 server.xml ->
/etc/cloudstack/management/server7-nonssl.xml
lrwxrwxrwx 1 root root 46 Aug 23 16:37 tomcat6.conf ->
/etc/cloudstack/management/tomcat6-nonssl.conf
-rw-r--r-- 1 root root   2692 Jul 12 12:33 tomcat6-nonssl.conf
-rw-r--r-- 1 root root   2821 Jul 12 12:33 tomcat6-ssl.conf
-rw-r--r-- 1 root root   1383 Jul 12 12:33 tomcat-users.xml
-rw-r--r-- 1 root root  50428 Jul 12 12:33 web.xml


On Thu, Aug 24, 2017 at 2:13 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Is there a db.properties in /etc/cloudstack.. folder?
>
> On Thu, Aug 24, 2017 at 3:27 AM, Jevgeni Zolotarjov <
> j.zolotar...@gmail.com>
> wrote:
>
> > Did that "setup --tomcat7" now.
> > Output:
> > Starting to configure CloudStack Management Server:
> > Configure Firewall ...[OK]
> > Configure CloudStack Management Server ...[OK]
> > CloudStack Management Server setup is Done!
> >
> > But no difference, when I try to run client application. Absolutely the
> > same result in catalina.log - Failed to find db.properties
> >
> >
> >
> > On Thu, Aug 24, 2017 at 1:24 AM, ilya 
> > wrote:
> >
> > > Rafael has a point there - please try with tomcat7
> > >
> > > Also - please look into catalina.out/log for further debugging info.
> > >
> > > On 8/23/17 9:23 AM, Rafael Weingärtner wrote:
> > > > did you run setup-management --tomcat7?
> > > >
> > > > On Wed, Aug 23, 2017 at 12:20 PM, Jevgeni Zolotarjov <
> > > j.zolotar...@gmail.com
> > > >> wrote:
> > > >
> > > >> Yes, I did, as it is suggested in the guide:
> > > >> cloudstack-setup-database then setup-management
> > > >>
> > > >>
> > > >> On Aug 23, 2017 7:11 PM, "Rafael Weingärtner" <
> > > rafaelweingart...@gmail.com
> > > >>>
> > > >> wrote:
> > > >>
> > > >> did you run cloudstack-setup-database and ...setup-management?
> > > >>
> > > >>
> > > >> On Wed, Aug 23, 2017 at 11:16 AM, Jevgeni Zolotarjov <
> > > >> j.zolotar...@gmail.com
> > > >>> wrote:
> > > >>
> > > >>> Here you go
> > > >>>
> > > >>> management-server.log is not available, which probably means, the
> > > >>> application did not reach that far and exited due to missing DB
> > access
> > > >>>
> > > >>> On Wed, Aug 23, 2017 at 6:03 PM, Gabriel Beims Bräscher <
> > > >>> gabrasc...@gmail.com> wrote:
> > > >>>
> > >  Hi Jevgeni,
> > > 
> > >  Can you share with us some log files (catalina.log,
> > > >> management-server.log
> > >  and others that might be useful)?
> > > 
> > > 
> > >  2017-08-23 11:53 GMT-03:00 Jevgeni Zolotarjov <
> > j.zolotar...@gmail.com
> > > >:
> > > 
> > > > Hi
> > > >
> > > > I am installing Cloudstack 4.10 on Debian Jessie using guides
> from
> > > > http://cloudstack-installation.readthedocs.io/en/latest/
> > >  management-server/
> > > > index.html
> > > >
> > > > Apparently the installation process was smooth. But I cannot get
> > > >> client
> > > > running on tomcat7
> > > > From catalina.out log file I can read
> > > >
> > > > Failed to find db.properties
> > > >
> > > > But this file is present in
> > > > ./etc/cloudstack/management/db.properties
> > > > ./etc/cloudstack/usage/db.properties
> > > >
> > > > Please help.
> > > >
> > > 
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >> --
> > > >> Rafael Weingärtner
> > > >>
> > > >
> > > >
> > > >
> > >
> >
>
>
>
> --
> Rafael Weingärtner
>

Re: Failed to find db.properties

[Rafael Weingärtner]

Is there a db.properties in /etc/cloudstack.. folder?

On Thu, Aug 24, 2017 at 3:27 AM, Jevgeni Zolotarjov 
wrote:

> Did that "setup --tomcat7" now.
> Output:
> Starting to configure CloudStack Management Server:
> Configure Firewall ...[OK]
> Configure CloudStack Management Server ...[OK]
> CloudStack Management Server setup is Done!
>
> But no difference, when I try to run client application. Absolutely the
> same result in catalina.log - Failed to find db.properties
>
>
>
> On Thu, Aug 24, 2017 at 1:24 AM, ilya 
> wrote:
>
> > Rafael has a point there - please try with tomcat7
> >
> > Also - please look into catalina.out/log for further debugging info.
> >
> > On 8/23/17 9:23 AM, Rafael Weingärtner wrote:
> > > did you run setup-management --tomcat7?
> > >
> > > On Wed, Aug 23, 2017 at 12:20 PM, Jevgeni Zolotarjov <
> > j.zolotar...@gmail.com
> > >> wrote:
> > >
> > >> Yes, I did, as it is suggested in the guide:
> > >> cloudstack-setup-database then setup-management
> > >>
> > >>
> > >> On Aug 23, 2017 7:11 PM, "Rafael Weingärtner" <
> > rafaelweingart...@gmail.com
> > >>>
> > >> wrote:
> > >>
> > >> did you run cloudstack-setup-database and ...setup-management?
> > >>
> > >>
> > >> On Wed, Aug 23, 2017 at 11:16 AM, Jevgeni Zolotarjov <
> > >> j.zolotar...@gmail.com
> > >>> wrote:
> > >>
> > >>> Here you go
> > >>>
> > >>> management-server.log is not available, which probably means, the
> > >>> application did not reach that far and exited due to missing DB
> access
> > >>>
> > >>> On Wed, Aug 23, 2017 at 6:03 PM, Gabriel Beims Bräscher <
> > >>> gabrasc...@gmail.com> wrote:
> > >>>
> >  Hi Jevgeni,
> > 
> >  Can you share with us some log files (catalina.log,
> > >> management-server.log
> >  and others that might be useful)?
> > 
> > 
> >  2017-08-23 11:53 GMT-03:00 Jevgeni Zolotarjov <
> j.zolotar...@gmail.com
> > >:
> > 
> > > Hi
> > >
> > > I am installing Cloudstack 4.10 on Debian Jessie using guides from
> > > http://cloudstack-installation.readthedocs.io/en/latest/
> >  management-server/
> > > index.html
> > >
> > > Apparently the installation process was smooth. But I cannot get
> > >> client
> > > running on tomcat7
> > > From catalina.out log file I can read
> > >
> > > Failed to find db.properties
> > >
> > > But this file is present in
> > > ./etc/cloudstack/management/db.properties
> > > ./etc/cloudstack/usage/db.properties
> > >
> > > Please help.
> > >
> > 
> > >>>
> > >>>
> > >>
> > >>
> > >> --
> > >> Rafael Weingärtner
> > >>
> > >
> > >
> > >
> >
>



-- 
Rafael Weingärtner

Re: Failed to find db.properties

[Jevgeni Zolotarjov]

Did that "setup --tomcat7" now.
Output:
Starting to configure CloudStack Management Server:
Configure Firewall ...[OK]
Configure CloudStack Management Server ...[OK]
CloudStack Management Server setup is Done!

But no difference, when I try to run client application. Absolutely the
same result in catalina.log - Failed to find db.properties



On Thu, Aug 24, 2017 at 1:24 AM, ilya  wrote:

> Rafael has a point there - please try with tomcat7
>
> Also - please look into catalina.out/log for further debugging info.
>
> On 8/23/17 9:23 AM, Rafael Weingärtner wrote:
> > did you run setup-management --tomcat7?
> >
> > On Wed, Aug 23, 2017 at 12:20 PM, Jevgeni Zolotarjov <
> j.zolotar...@gmail.com
> >> wrote:
> >
> >> Yes, I did, as it is suggested in the guide:
> >> cloudstack-setup-database then setup-management
> >>
> >>
> >> On Aug 23, 2017 7:11 PM, "Rafael Weingärtner" <
> rafaelweingart...@gmail.com
> >>>
> >> wrote:
> >>
> >> did you run cloudstack-setup-database and ...setup-management?
> >>
> >>
> >> On Wed, Aug 23, 2017 at 11:16 AM, Jevgeni Zolotarjov <
> >> j.zolotar...@gmail.com
> >>> wrote:
> >>
> >>> Here you go
> >>>
> >>> management-server.log is not available, which probably means, the
> >>> application did not reach that far and exited due to missing DB access
> >>>
> >>> On Wed, Aug 23, 2017 at 6:03 PM, Gabriel Beims Bräscher <
> >>> gabrasc...@gmail.com> wrote:
> >>>
>  Hi Jevgeni,
> 
>  Can you share with us some log files (catalina.log,
> >> management-server.log
>  and others that might be useful)?
> 
> 
>  2017-08-23 11:53 GMT-03:00 Jevgeni Zolotarjov  >:
> 
> > Hi
> >
> > I am installing Cloudstack 4.10 on Debian Jessie using guides from
> > http://cloudstack-installation.readthedocs.io/en/latest/
>  management-server/
> > index.html
> >
> > Apparently the installation process was smooth. But I cannot get
> >> client
> > running on tomcat7
> > From catalina.out log file I can read
> >
> > Failed to find db.properties
> >
> > But this file is present in
> > ./etc/cloudstack/management/db.properties
> > ./etc/cloudstack/usage/db.properties
> >
> > Please help.
> >
> 
> >>>
> >>>
> >>
> >>
> >> --
> >> Rafael Weingärtner
> >>
> >
> >
> >
>