Passenger SecurityUpdateChecker Error - passenger

In passenger.log such error occurs:
2018-02-24 11:13:03.6657 1536/T5 age/Cor/SecurityUpdateChecker.h:362 ]:
Security update check failed: Couldn't connect to server for
https://securitycheck.phusionpassenger.com:443/v1/check.json
(if this error persists check your connection security or try upgrading Passenger)
(next check in 24 hours)
Please help how to investigate and solve this.

Related

Laravel & VestaCP: 500 Internal Server Error

Im trying to deploy a Laravel 5.8.* project to my host while using the next template: Laravel web template for VestaCP but I am getting the next error:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at info#iberoseguridad.eu to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
Also, this is the error log from my host:
[Mon Jun 03 19:17:12.497219 2019] [core:error] [pid 22984] [client 68.183.55.192:33376] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: mydomain
Is there any way to fix this error?

Issue installing openwhisk with incubator-openwhisk-devtools

I have a blocking issue installing openwhisk with docker
I typed make quick-start right after a git pull of the project incubator-openwhisk-devtools. My OS is Fedora 29, docker version is 18.09.0, docker-compose version is 1.22.0. JDk 8 Oracle.
I get the following error:
[...]
adding the function to whisk ...
ok: created action hello
invoking the function ...
error: Unable to invoke action 'hello': The server is currently unavailable (because it is overloaded or down for maintenance). (code ciOZDS8VySDyVuETF14n8QqB9wifUboT)
[...]
[ERROR] [#tid_sid_unknown] [Invoker] failed to ping the controller: org.apache.kafka.common.errors.TimeoutException: Expiring 1 record(s) for health-0: 30069 ms has passed since batch creation plus linger time
[ERROR] [#tid_sid_unknown] [KafkaProducerConnector] sending message on topic 'health' failed: Expiring 1 record(s) for health-0: 30009 ms has passed since batch creation plus linger time
Please note that controller-local-logs.log is never created.
If I issue a touch controller-local-logs.log in the right directory the log file is always empty after I try to issue make quick-start again.
http://localhost:8888/ping gives me the right answer: pong.
http://localhost:9222 is not reacheable.
Where am I wrong?
Thank you in advance

Opnenms UI error - HTTP ERROR: 503

I am facing issue while accessing the opennms UI throwing below error
HTTP ERROR: 503
Problem accessing /opennms/alarm/detail.htm. Reason:
Service Unavailable
OpenNMS Version: 1.10.10
Let me know if you need any trpe of logs detail
I know this is a frustrating answer, but seriously, upgrade. Version 1.10.10 is simply ancient.
The version numbering for OpenNMS has dropped the "1." so you are basically on version "10" while the current version is "22".
If you want to try to fix this on 1.10 the problem is usually caused by an error in a .properties file. What I would do is stop OpenNMS:
/opt/opennms/bin/opennms stop
and then remove the log files
rm -rf /opt/opennms/logs/*
then restart OpenNMS
/opt/opennms/bin/opennms start
While that won't fix the problem, you can then
cd /opt/opennms/logs
and then grep for ERROR or FATAL log messages. Those should tell you which file has the problem.

Vertica admintools error

when I try to connect to database from admintools I am getting following error:
Error: Unable to connect to database
Hint: Username or password could be invalid
I have found in the logs following error:
Apr 20 08:08:29 [24291] [vsql.connect spawn] Exception: Error! pty.fork() failed: out of pty devices
Do you know what is the problem?
Your node might be down
Check logs at
/opt/vertica/log
or at
/opt/vertica/config/admintools.conf
check restart policy section is right
[Database:mydb] host = 11.11.11.11
restartpolicy = ksafe

New Relic, Heroku error: ERROR : [New Relic] Error running task in worker loop, likely a server error

I am using Papertrail to monitor my heroku app and it seems that I am getting this same error repeatedly:
app/web.2: ** [NewRelic][12/13/13 17:14:17 +0000 f00d3735-79e0-4b0a-9e0d-9315444e2641 (2)] ERROR : Error running task in worker loop, likely a server error:
I read in the ruby docs here that this is probably:
This is probably a server error which has been logged in the server along
# with your account name. Check and see if the agent listener is in the
# stack trace and log it quietly if it is.
I am not quite sure how to debug it and would love some help. Thanks!
Please let me know if my source code would be helpful

Resources