I have installed SSRS 2016 on windows 2012 server R2. The SQL server 2016 is configured correctly and TCP enabled. It seems like I can not access the report portal from my machine using my network ID even though I can access it from some servers that are hosted on the same cloud.
I have been trying to find out a reason or a clue but I am really out of ideas. The firewall of the server is disabled and the windows service of SSRS is running under a service account as well as the SQL server instance.
I opened up the service exe file from VS to get more trace logs as the log file doesn't have any error to indicate or direct me on warning or error message unlike the verbose entries I got from the service Console application. Please let me know if you have encountered or seen anything like that before .. I am really puzzled and going nuts !!
Info - 4:22:55 PM - Setting up Debug CRT libraries
Warning - 4:22:55 PM - %_NTDRIVE% not defined... Skipping
Info - 4:22:56 PM - Starting ReportServerWebApp
Info - 4:22:56 PM - Working directory : C:\Program Files\Microsoft
SQL Server\MSRS13.SQL16\Reporting Services\RSWebApp
Info - 4:22:56 PM - Report Server url:
http://localhost:80/reportsdemo
Info - 4:22:56 PM - Report Server Web App virtual root:
/DemoReports
Info - 4:22:56 PM - Web app url: http://+:80/DemoReports/
Info - 4:22:56 PM - Authentication scheme(s): Ntlm
Info - 4:22:56 PM - Registering 0 : AuthSchemeConfig
Info - 4:22:56 PM - Registering 5 : RequestLoggingConfig
Info - 4:22:56 PM - Registering 10 : CustomAuthenticationConfig
Info - 4:22:56 PM - Registering 20 : BasicAuthenticationConfig
Info - 4:22:56 PM - Registering 25 : RequestThrottlingConfig
Info - 4:22:56 PM - Registering 30 : CsrfTokenCreationConfig
Info - 4:22:56 PM - Registering 40 : LanguageConfig
Info - 4:22:56 PM - Registering 50 : XFrameOptionsConfig
Info - 4:22:56 PM - Registering 50 : ClassicUrlRedirecterConfig
Info - 4:22:56 PM - Registering 50 : PopulateHeadersConfig
Info - 4:22:56 PM - Registering 53 : LocalRequestMiddlewareConfig
Info - 4:22:56 PM - Registering 55 : ClassicUrlRewriterConfig
Info - 4:22:56 PM - Registering 100 : FileSystemConfig
Info - 4:22:56 PM - Registering 190 : ServiceUnavailableConfig
Info - 4:22:56 PM - Registering 200 : DatabaseAvailableConfig
Info - 4:22:56 PM - Registering 300 : CsrfTokenValidationConfig
Info - 4:22:56 PM - Registering 500 : WebApiOwinConfig
Info - 4:22:57 PM - Registering 600 : ODataWebApiOwinConfig
Verbose - 4:23:02 PM - [nh78byvq]: Request received
Warning - 4:23:02 PM - [nh78byvq]: CSRF Token not generated due to
exception:
Microsoft.ReportingServices.Diagnostics.Utilities.CannotValidateEncryptedDataException:
The report server was unable to validate the integrity of encrypted
data in the database.
Verbose - 4:23:03 PM - [nh78byvq]: 10.206.197.30: GET /index.html -
Response 304- 0:00:00.1191454
Verbose - 4:23:03 PM - [r0eyb35z]: Request received
Warning - 4:23:03 PM - [r0eyb35z]: CSRF Token not generated due to
exception:\n
Microsoft.ReportingServices.Diagnostics.Utilities.CannotValidateEncryptedDataException:
The report server was unable to validate the integrity of encrypted
datain the database.
Related
I have deployed my service running on spring boot in openshift. The spring boot service initializes good and we see the below logs which is good.
2020-05-06 19:32:33.930 INFO 1 --- [ main] c.a.r.l.MyApplication : Started MyApplication in 44.227 seconds (JVM running for 67.578)
2020-05-06 19:32:38.706 INFO 1 --- [nio-8198-exec-1] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring DispatcherServlet 'dispatcherServlet'
2020-05-06 19:32:38.709 INFO 1 --- [nio-8198-exec-1] o.s.web.servlet.DispatcherServlet : Initializing Servlet 'dispatcherServlet'
2020-05-06 19:32:38.802 INFO 1 --- [nio-8198-exec-1] o.s.web.servlet.DispatcherServlet : Completed initialization in 93 ms
However the containers ready status shows 0/1 and after 5 mins i see this warning and the pod restarts.
The container has been running for more than five minutes and has not passed its readiness check
and i see
Readiness probe failed: HTTP probe failed with statuscode: 404
What could be wrong?
Readiness probe failed: HTTP probe failed with statuscode: 404
This indicates that the URL that you specified for your readinessProbe does not exist (HTTP 404). So check how your readinessProbe is defined (which URI is called) and make sure there is a valid response.
For Spring Boot, there is an actuator available for Health endpoints, see the following documentation: https://docs.spring.io/spring-boot/docs/current/reference/html/production-ready-features.html
Here is an example:
[..]
spec:
containers:
- args:
image: k8s.gcr.io/readiness
readinessProbe:
httpGet:
path: /healthz
In the example above, make sure that the /healthz endpoint exists.
You can find more information on how to configure Readiness Probes in the OpenShift documentation.
All my hosts stopped reporting stats to collectd google gateway. This is due to some internal change on google side.
In logs files I see this:
Jan 13 08:52:36 ign-rpt01 systemd[1]: Stopping LSB: start and stop Stackdriver Agent...
Jan 13 08:52:36 ign-rpt01 stackdriver-agent[10768]: mesg: ttyname failed: Inappropriate ioctl for device
Jan 13 08:52:36 ign-rpt01 stackdriver-agent[10768]: * Stopping Stackdriver metrics collection agent stackdriver-agent
Jan 13 08:52:37 ign-rpt01 stackdriver-agent[10768]: ...done.
Jan 13 08:52:37 ign-rpt01 systemd[1]: Stopped LSB: start and stop Stackdriver Agent.
Jan 13 08:52:37 ign-rpt01 systemd[1]: Starting LSB: start and stop Stackdriver Agent...
Jan 13 08:52:37 ign-rpt01 stackdriver-agent[10794]: mesg: ttyname failed: Inappropriate ioctl for device
Jan 13 08:52:37 ign-rpt01 stackdriver-agent[10794]: * Starting Stackdriver metrics collection agent stackdriver-agent
Jan 13 08:52:38 ign-rpt01 stackdriver-agent[10794]: Unable to determine collectd endpoint!
Jan 13 08:52:38 ign-rpt01 stackdriver-agent[10794]: * not starting, configuration error
Jan 13 08:52:38 ign-rpt01 stackdriver-agent[10794]: ...fail!
Jan 13 08:52:38 ign-rpt01 systemd[1]: Started LSB: start and stop Stackdriver Agent.
Jan 13 08:53:16 ign-rpt01 extractd[10869]: Error sending processes data: Stackdriver gateway replied with a 401: <html><title>HTTP 401: Unauthorized (Invalid API key)</title><body>HTTP 401: Unauthorized (Invalid API key)</body></html>
Jan 13 08:54:16 ign-rpt01 extractd[10903]: Error sending processes data: Stackdriver gateway replied with a 401: <html><title>HTTP 401: Unauthorized (Invalid API key)</title><body>HTTP 401: Unauthorized (Invalid API key)</body></html>
Jan 13 08:55:16 ign-rpt01 extractd[10947]: Error sending processes data: Stackdriver gateway replied with a 401: <html><title>HTTP 401: Unauthorized (Invalid API key)</title><body>HTTP 401: Unauthorized (Invalid API key)</body></html>
When I go to stackdriver account settings:
The following instances are using a deprecated configuration of the monitoring agent. Alerting policies referencing metrics from these agents do not work as intended and are currently unsupported. Dashboards using metrics from these agents are also unsupported and will soon stop working.
Please update your monitoring agent. Learn more
Okay, it turns out that now only --write-gcm is supported now.
TL;DR version
Just run this:
curl -O "https://repo.stackdriver.com/stack-install.sh"
sudo bash stack-install.sh --write-gcm
And hey, my stats are starting to come in again:
After deploying a brand new Google Compute Engine instance with full API access and installing the Stackdriver agent, the Monitoring is not showing any metrics from the agent.
According to the Install Agent manual no further settings (like manually configurating an API key) should be required.
The agent service status also shows the following error:
$ systemctl status stackdriver-agent
Jul 13 10:14:00 host stackdriver-agent[21203]: [ OK ]
Jul 13 10:14:00 host systemd[1]: Started LSB: start and stop Stackdriver Agent.
Jul 13 10:14:00 host collectd[21226]: Initialization complete, entering read-loop.
Jul 13 10:14:00 host collectd[21226]: match_throttle_metadata_keys: 1 history entries, 1 distinct keys, 46 bytes server memory.
Jul 13 10:14:00 host collectd[21226]: tcpconns plugin: Reading from netlink succeeded. Will use the netlink method from now on.
Jul 13 10:14:00 host collectd[21226]: write_gcm: Asking metadata server for auth token
Jul 13 10:14:01 host collectd[21226]: write_gcm: Unsuccessful HTTP request 403: {
"error": {
"code": 403,...
Jul 13 10:14:01 host collectd[21226]: write_gcm: Error talking to the endpoint.
Jul 13 10:14:01 host collectd[21226]: write_gcm: wg_transmit_unique_segment failed.
Jul 13 10:14:01 host collectd[21226]: write_gcm: wg_transmit_unique_segments failed. Flushing.
Google Cloud Console shows the instance having:
Cloud API access scopes
This instance has full API access to all Google Cloud services.
and running the following command inside the instance shows:
$ curl --silent -f -H "Metadata-Flavor: Google" http://169.254.169.254/computeMetadata/v1/instance/service-accounts/default/scopes
https://www.googleapis.com/auth/cloud-platform
Any thoughts on what is going wrong?
I figured it out:
You have to enable the Google Monitoring API in the API Manager, which is not enabled by default. No need to specify an API key, the default application credentials are picked up.
Interestingly, I have two projects which also use Stackdriver Monitoring since early this year and those do not require the Google Monitoring API to be enabled.
I am getting the following error when I try to start the server manually or from command prompt.
Stopping NodeJS cartridge
Sun Dec 20 2015 10:29:20 GMT-0500 (EST): Stopping application 'nodejs' ...
Sun Dec 20 2015 10:29:20 GMT-0500 (EST): Stopped Node application 'nodejs'
Starting NodeJS cartridge
Sun Dec 20 2015 10:29:21 GMT-0500 (EST): Starting application 'nodejs' ...
Waiting for application port (8080) become available ...
Application 'nodejs' failed to start (port 8080 not available)
Failed to execute: 'control restart' for /var/lib/openshift/5671bca50c1e66a111000114/nodejs
Please provide any solution. Thanks in advance.
I'm trying to get Message Archive Management ( mam ) on a prosody server
working.
I tried it with SQLite3, MySQL and PostgreSQL.
Always this log:
Oct 20 14:56:21 general info Hello and welcome to Prosody version 0.9.7
Oct 20 14:56:21 general info Prosody is using the epoll backend for connecti$
Oct 20 14:56:22 localhost:mam error Could not open archive storage
The archive is existing in /var/lib/prosody/.