I replaced the log4j-cloud file with the one from the link, and CS still
starts, but is still not logging. I did re-added my customizations, which
involve sending logs to an external log server. To test, I removed my
customizations, and I am now logging. I noticed that I am now logging to the
Date: Tuesday, July 15, 2025 at 11:23 PM
To: [email protected]
Subject: Re: Upgrade from 4.19 to 4.20 stopped logging
WARNING: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
Hi
Thank you, Rohit.
Do I also need to replace the log4j2.xml file as well along with the
log4j2-cloud.xml file?
Regards,
Marty Godsey
Rudio, LLC
From: Rohit Yadav
Date: Tuesday, July 15, 2025 at 11:23 PM
To: [email protected]
Subject: Re: Upgrade from 4.19 to 4.20 stopped logging
thub.com/apache/cloudstack/blob/4.20/client/conf/log4j-cloud.xml.in
Regards.
From: Marty Godsey
Sent: Wednesday, July 16, 2025 06:53
To: [email protected]
Subject: Upgrade from 4.19 to 4.20 stopped logging
Hello,
I saw the bug where upgrading from
Hello,
I saw the bug where upgrading from 4.19 to 4.20.1 stopped the logger, but it
also stopped the management server from logging. I don’t have the issue of my
management server not starting; it starts fine, but I have no logs being
generated.
I didn’t see a clear fix. What should I check
GitHub user nemethga closed a discussion: Logging into multiple domains with an
ldap account
Hi there,
Is it possible to log in to multiple domains in cloudstack with an ldap
account? I didn't find such an option in the documentation.
GitHub link: https://github.com/apache/cloud
GitHub user DaanHoogland added a comment to the discussion: Logging into
multiple domains with an ldap account
You can if you link domain to an ldap group, you can link another domain to the
same group. From the documentation look at auto-import and auto-sync. I am not
sure if it will work
GitHub user kiranchavala added a comment to the discussion: Logging into
multiple domains with an ldap account
@nemethga It's possible with Saml authentication, not sure about Ldap
GitHub link:
https://github.com/apache/cloudstack/discussions/10706#discussioncomment-12827919
This
GitHub user btzq added a comment to the discussion: Centralised logging via
rsyslog
Hi, this is something we are looking forward to! Currently monitoring VR is
difficult. So we are really looking forward to it!
GitHub link:
https://github.com/apache/cloudstack/discussions/9179
[email protected]
Subject: Logging into fresh cloudstack 4.18 installation
Hello,
I have installed a fresh cloudstack 4.18. When I visit the UI for the
forest time I am taken into login page. I have nir set admin password yet
because I have not taken into guided setip page.
Please advise.
Disc
Hello,
I have installed a fresh cloudstack 4.18. When I visit the UI for the
forest time I am taken into login page. I have nir set admin password yet
because I have not taken into guided setip page.
Please advise.
GitHub user lucas-a-martins added a comment to the discussion: logging
standards in CloudStack
Hey, @weizhouapache. Sorry for the delay;
About your sugestion, I think you have a good idea here. Also, we already have
something like this with `com.cloud.api.ApiServer#handleRequest`.
I didn&#
GitHub user DaanHoogland added a comment to the discussion: Centralised logging
via rsyslog
@soreana should/can we mark this for 4.16?
GitHub link:
https://github.com/apache/cloudstack/discussions/9179#discussioncomment-9677697
This is an automatically sent email for users
GitHub user soreana added a comment to the discussion: Centralised logging via
rsyslog
@rhtyd good :+1:
Sorry for late, we got a lot of issues recently, I can't find a room to work on
this pr. Maybe next week 🤞
GitHub link:
https://github.com/apache/cloudstack/discussions
GitHub user rohityadavcloud added a comment to the discussion: Centralised
logging via rsyslog
Removing 4.16 milestone as PR has no milestone; let's move this back if the
milestone tagging changes.
GitHub link:
https://github.com/apache/cloudstack/discussions/9179#discussioncomment-96
GitHub user soreana added a comment to the discussion: Centralised logging via
rsyslog
No, they are legitimate requirements :D
GitHub link:
https://github.com/apache/cloudstack/discussions/9179#discussioncomment-9677696
This is an automatically sent email for users
GitHub user soreana added a comment to the discussion: Centralised logging via
rsyslog
@DaanHoogland Honestly, it took a lot of time to apply the changes you required
to merging this pr. I discussed it with my colleagues, and we concluded that it
isn't our priority now. We focused on
GitHub user rohityadavcloud added a comment to the discussion: Centralised
logging via rsyslog
I think it's possible to do this as part of a custom systemvm.iso where you can
bake-in your deployment specific option. Any further update on this @soreana or
we can close the issue?
GitHub
GitHub user rohityadavcloud added a comment to the discussion: Centralised
logging via rsyslog
I think it may be possible via some log4j config?
GitHub link:
https://github.com/apache/cloudstack/discussions/9179#discussioncomment-9677703
This is an automatically sent email for users
GitHub user soreana added a comment to the discussion: Centralised logging via
rsyslog
@DaanHoogland When do you planned for 4.16 release?
GitHub link:
https://github.com/apache/cloudstack/discussions/9179#discussioncomment-9677698
This is an automatically sent email for users
GitHub user DaanHoogland added a comment to the discussion: Centralised logging
via rsyslog
tnx for your efforts @soreana , i'm marking it as unplanned for now, feel free
to come back at any time of your convenience.
GitHub link:
https://github.com/apache/cloudstack/discussions
GitHub user soreana added a comment to the discussion: Centralised logging via
rsyslog
I asked our PO. We made a story to work on that. :)
GitHub link:
https://github.com/apache/cloudstack/discussions/9179#discussioncomment-9677700
This is an automatically sent email for users
GitHub user DaanHoogland added a comment to the discussion: Centralised logging
via rsyslog
@soreana are you still planning for this?
GitHub link:
https://github.com/apache/cloudstack/discussions/9179#discussioncomment-9677692
This is an automatically sent email for users
GitHub user DaanHoogland added a comment to the discussion: Centralised logging
via rsyslog
this summer somewhere.
GitHub link:
https://github.com/apache/cloudstack/discussions/9179#discussioncomment-9677699
This is an automatically sent email for [email protected].
To
GitHub user DaanHoogland added a comment to the discussion: Centralised logging
via rsyslog
> @DaanHoogland Honestly, it took a lot of time to apply the changes you
> required to merging this pr. I discussed it with my colleagues, and we
> concluded that it isn't our priority n
GitHub user soreana created a discussion: Centralised logging via rsyslog
# ISSUE TYPE
* Feature Idea
# COMPONENT NAME
~~~
Systemvm
~~~
# CLOUDSTACK VERSION
~~~
It can be merge to 4.14
~~~
# CONFIGURATION
# OS / ENVIRONMENT
Used Ubuntu 18:04 as a host for management
GitHub user DaanHoogland added a comment to the discussion: logging standards
in CloudStack
@weizhouapache a possible solution to this could be to add an error uuid to the
exception and use this in the loging. Users don't see the logging but only
exceptions thrown. idea?
GitHub link:
GitHub user weizhouapache added a comment to the discussion: logging standards
in CloudStack
@lucas-a-martins and me had some discussion on [#8603
](https://github.com/apache/cloudstack/pull/8603#issuecomment-2092439013)
I think it is better to raise the discussion here.
Basically the
GitHub user DaanHoogland edited a comment on the discussion: logging standards
in CloudStack
I didn't know about the stacktrace limit option, that is good.
> Another point is that we would have to change the whole code base to comply
> with this standard.
This is true what eve
GitHub user DaanHoogland added a comment to the discussion: logging standards
in CloudStack
I didn't know about the stacktrace limit option, that is good.
> Another point is that we would have to change the whole code base to comply
> with this standard.
This is true what ever we
GitHub user GutoVeronezi added a comment to the discussion: logging standards
in CloudStack
I believe that adding an error message in `ERROR` followed by the stack trace
in `DEBUG` is not so interesting. For instance, if we have the `INFO` level
enabled and an exception occurs, we would not
briel,
I’m using 4.19.
--
Jimmy
Van: Gabriel Santos
Datum: dinsdag, 2 april 2024 om 20:13
Aan:[email protected]
Onderwerp: Re: Vm logging when assigning other users
Hi, Jimmy!
I'm glad you figured it out, but yes, the logging can be really
annoying. What version of CloudStack were
Hi Gabriel,
I’m using 4.19.
--
Jimmy
Van: Gabriel Santos
Datum: dinsdag, 2 april 2024 om 20:13
Aan: [email protected]
Onderwerp: Re: Vm logging when assigning other users
Hi, Jimmy!
I'm glad you figured it out, but yes, the logging can be really
annoying. What version of Cloud
Hi, Jimmy!
I'm glad you figured it out, but yes, the logging can be really
annoying. What version of CloudStack were you using? I'll check it out
and, hopefully, improve it.
---
Gabriel Santos
On 02/04/2024 12:52, Jimmy Huybrechts wrote:
So in the end it was the template I use
So in the end it was the template I used for them which I just found out by
giving it permissions step by step, but shouldn’t that be listed somewhere
where it is?
--
Jimmy
Van: Jimmy Huybrechts
Datum: dinsdag, 2 april 2024 om 17:01
Aan: [email protected]
Onderwerp: Vm logging when
Hi,
So sometimes the logging annoys me, as in it tells you exactly nothing.
I’m trying to assign a VM to a different user, from the users account I can see
the compute offering, I can see the network, and yet if I try to assign it it
just says:
Failed to move vm due to Account
[{"accoun
GitHub user DaanHoogland added a comment to the discussion: logging standards
in CloudStack
I like your summary @JoaoJandre except for the error bit:
> Error:
>
> * Include a reason why the system can not execute a user request or
> why part of the system is degraded;
&
e doing fine.
>
> Currently, there is a discussion in GitHub [1] regarding the CloudStack
> logging standards. Mostly, logs are written based on the developer's
> feelings about what should be logged and how; however, operators are the
> ones constantly dealing with logs. With that i
Hello guys,
Hope you are doing fine.
Currently, there is a discussion in GitHub [1] regarding the CloudStack
logging standards. Mostly, logs are written based on the developer's
feelings about what should be logged and how; however, operators are the
ones constantly dealing with logs.
GitHub user JoaoJandre added a comment to the discussion: logging standards in
CloudStack
Here are some guidelines I think would be a good start (adapted from
@DaanHoogland 's post on the mailing list)
Fatal:
- Include a reason why the system can not function anymore;
- Be followed
Hello,
Is it possible to log outgoing SMTP connections via VR? Or I should do
this on physical network side?
Hello, comunity.
We recently developed simulator image for ACS 4.9.3 integrated with Apache
Kafka event bus logging system. This is for development purposes. We use
Kafka as integration point, so we need it. It's published in:
GitHub: https://github.com/bwsw/cs-simulator-kafka
DockerHub:
On Thu, Apr 21, 2016 at 9:49 AM, Paul Angus
wrote:
> Hey Daan,
>
> I understand from a purists point of view, but to me messages like:
>
> INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-113:ctx-56d9f9f2)
> Scan hung worker VM to recycle
>
> Are part of the inner workings of cloudstack, and
--Original Message-
From: Frank Louwers [mailto:[email protected]]
Sent: 21 April 2016 08:14
To: [email protected]
Subject: Re: CloudStack Logging
Hi Paul,
I’d love to see improvement in that area! Especially for my operational admins,
the biggest issue we face is this:
- Someo
Place, Covent Garden, London WC2N 4HSUK
@shapeblue
-Original Message-
From: Daan Hoogland [mailto:[email protected]]
Sent: 20 April 2016 23:12
To: [email protected]
Subject: Re: CloudStack Logging
Paul,
Your classification of levels seems right. I wouldn't say WARN mean
me :)
I think these failures are quite an easy use-case to improve logging on. If a
VM can’t be started because of a “capacity” issue, it would we good to log (in
a non-debug, non-info log):
- Which hosts were considered for CPU/Mem (based on zone, tags etc) (list them
by name pref, not by
operational admins, the people who need
> to know the health of their cloud and deal with issues as they're
> constantly reading the log.
>
> However, I'm not proposing to add or remove any messages, just revisit the
> categorisation. If the 'operator' has their
sues as they're constantly
reading the log.
However, I'm not proposing to add or remove any messages, just revisit the
categorisation. If the 'operator' has their logging on debug they'd actually
see the same messages. The idea is to make turning the logging down to INFO
feas
Hello,
I have a question what is the criteria that you are going to follow to decide
the log record importance. Who is the user that you will design the logging
process for. Is it for finding issues with the installation or is it for
security breaches or auditing.
These questions are good to
Paul Angus
[email protected]
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
-Original Message-
From: Simon Weller [mailto:[email protected]]
Sent: 19 April 2016 21:51
To: [email protected]; [email protected]
Subject: Re: CloudSta
Paul,
Are you wanting for focus on logs on releases later than a particular version
(e.g. 4.6)?
- Si
From: Paul Angus
Sent: Tuesday, April 19, 2016 10:55 AM
To: [email protected]; [email protected]
Subject: RE: CloudStack Logging
No
eblue
-Original Message-
From: [email protected] [mailto:[email protected]] On Behalf Of
Will Stevens
Sent: 19 April 2016 16:53
To: [email protected]
Cc: [email protected]
Subject: Re: CloudStack Logging
Thanks Paul. Are you looking for only logs with erro
> @shapeblue
>
> -Original Message-
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Will Stevens
> Sent: 19 April 2016 16:40
> To: [email protected]
> Cc: [email protected]
> Subject: Re: CloudStack Logging
>
Will Stevens
Sent: 19 April 2016 16:40
To: [email protected]
Cc: [email protected]
Subject: Re: CloudStack Logging
I like this initiative Paul. I just wanted to check with you. Do you know if
there is any confidential information like credentials or the like that is
logged in
n Tue, Apr 19, 2016 at 11:34 AM, Paul Angus
wrote:
> Hi All,
>
> I'm running an initiative to improve CloudStack logging. I'm going to be
> analysing logs and re-categorising the DEBUG, INFO, WARN and ERROR where
> appropriate such that we can reduce the default logging
Hi All,
I'm running an initiative to improve CloudStack logging. I'm going to be
analysing logs and re-categorising the DEBUG, INFO, WARN and ERROR where
appropriate such that we can reduce the default logging level to INFO without
losing important troubleshooting information, wh
I am studying the logging process used by CloudStack and came accross
the configuration file that is used by Log4j. What is confusing to me is
that all the resources is stating that the "log4j-cloud.xml" is
supposed to be the file used to confiugre the logging, but what I have
notic
Thanks for the info!
> From: [email protected]
> To: [email protected]
> Subject: Re: Logging...
> Date: Wed, 27 Aug 2014 16:57:27 +
>
> On agents or mgmt server, edit /etc/cloudstack/*/log4j-cloud.xml
>
> Look for lines that read similar to
>
>
On agents or mgmt server, edit /etc/cloudstack/*/log4j-cloud.xml
Look for lines that read similar to
And change INFO to DEBUG
On Aug 25, 2014, at 2:00 PM, Michael Phillips wrote:
> Seems the logging level in 4.4 has been toned down, how do you crank it up to
> verbose levels?
>
Seems the logging level in 4.4 has been toned down, how do you crank it up to
verbose levels?
I had ran into the same problem too,and what I did is wait for a little
while.CS is somewhat confused because it allows you to log in while it's
not really ready to do so. Just wait for a little while until the log says
something like User admin is ready.
2013/7/12 Anton Rubets
> I have some pr
I have some problems, because I don't check if my mysql base start. And
check your mysql config :-)
On Jul 11, 2013 11:34 PM, "Davide Blasi" wrote:
>
>
> Hi all,
>
> I'm trying to setup cloudstack 4.1.
>
> I'm using a debian wheezy with ubuntu packages from : deb
> http://cloudstack.apt-get.eu/ub
Hi all,
I'm trying to setup cloudstack 4.1.
I'm using a debian wheezy with ubuntu packages from : deb
http://cloudstack.apt-get.eu/ubuntu precise 4.1
I think I have followed all steps in the html guide,
but when I try to login as admin/password for the first time it says: "invalid
username
63 matches
Mail list logo
