I am trying to setup Slack notifications for Phabricator using etcinit/phabulous. However, Phabricator does not seem to be notifying the server.
My config looks like this:
{
feed.http-hooks: [ "http://127.0.0.1:8085/v1/feed/receive" ]
}
If I run curl http://127.0.0.1:8085 from within the server I get
{"messages":["Welcome to the Phabulous API"],"status":"success","version":"2.4.0-beta1"}
I am running Phabulous in debug mode, but I can see no request is ever made to 127.0.0.1:8085 since Gin shows no debug message.
Am I missing some configuration in Phabricator to actually made feed.http-hooks work?
Turns out I had to restart the daemon.
Above configuration didn't work for me, but this works:
{"feed.http-hooks":"https://callback_domain.xyz"}
Related
I'm setup kibana local development by following up the wiki from
https://github.com/elastic/kibana/blob/7.1/CONTRIBUTING.md#setting-up-your-development-environment
yarn es snapshot
i'm able to run elastichsearch locally at http://localhost:9200/ with above cli.
yarn start
i'm able to start the server for kibana with above cli, and according to log, it promote me to open http://localhost:5601/ykl,
server log [15:57:39.991] [info][listening] Server running at http://localhost:5603/ykl
server log [15:57:40.150] [info][status][plugin:spaces#8.0.0] Status changed from yellow to green - Ready
after i logined with default user/password, it return back a error response.
{"statusCode":403,"error":"Forbidden","message":"Forbidden"}
I'm not able to access page
http://localhost:5601/ykl/app/kibana#/management,
it will redirect me to http://localhost:5601/ykl/#/management with error response just as above error json response.
My question is what's wrong with the default user account to access homepage? how to change kibana configuration to allow me to access homepage.
ps:
I'm able to open status page without any problem http://localhost:5601/ykl/status#?_g=()
I found answer myself.
just use another default user account which has permission, actually, i login with elastic and it works
https://www.elastic.co/guide/en/elastic-stack-overview/7.1/built-in-users.html
I am trying to set up syslog so that we can have our app in different environments log to different files.
Everything works great for our development environment, but no logs are coming through for our staging environment.
Here is the snippet from our config file, 01-app.conf,
# staging
if ($programname == "api-staging") then {
action(type="omfile" file="/var/log/staging/api.log")
stop
}
# development
if ($programname == "api-development") then {
action(type="omfile" file="/var/log/development/api.log")
stop
}
user.* /var/log/other/user.log
stop
I have our config file start with 01 because the app logs go to multiple places if they respect the default config before our own.
Given that the development logs are getting routed correctly and that removing stop from the staging rule sends logs to /var/log/other/user.log, I am pretty confident there is not an issue with sending the logs to the box itself, but is somehow a problem with the routing.
An example log from /var/log/other/user.log that should be in /var/log/staging/api.log is this:
Sep 14 17:28:33 RD0003FF77E220 api-staging[58340]: "...", so I know that the programname I am looking for in the config is the correct name.
The syslog user did not have access to the staging directory so it could not write the logs there.
I have gone through some tools like nagios, collectd but they din't find best as we need to monitor no_of_req/sec for each virtual host with all response status, with response time also.
I'm Using ELK Stack:
Separate access logs for each server block for better visibility or you can separate charts via URLs.
Then Use ELK stack:
Feed the logs to logstash via filebeat.
Create grok pattern for your log model.
Create charts via kibana and monitor in real time.
For realtime monitoring:
Try netdata, Its amazing. Please note its not a replacement for nagios or zabbix.
After some quick research, I found this: check_nginx_status.pl. I think defining something like:
define command {
command_name check-nginx
command_line $USER1$/check_nginx_status.pl -H $HOSTADDRESS$ -s $ARG1$ -u $ARG2$ $ARG3$ $ARG4$ $ARG5$ $ARG6$
}
is probably just what you're looking for.
The -s flag ($ARG1$) would be the hostname of the virtual host
The -u flag ($ARG2$) would be the specific url (/something/status)
And then the rest of the args would be used if you needed to add any additional flags.
Hope this helps!
After following this tutorial to deploy my app to Azure, my app is working perfectly fine on most fronts.
However, when I try to send an email, it will never come through. The error log states
[2015-10-06 01:25:58] app.ERROR: Exception occurred while flushing email queue: Connection could not be established with host 127.0.0.1 [An attempt was made to access a socket in a way forbidden by its access permissions. #10013] [] []
So apparently it is still trying to use the parameters.yml settings that the app had generated in the beginning.
I have however edited the parameters.yml file to point to my SendGrid account, but those settings don't seem to be used. I have already restarted the server and cleared the cache multiple times to no avail.
Any idea what I'm doing wrong?
Clearing the cache through php app/console cache:clear apparently did not clear the parameters.yml cache.
For something else, I had to manually delete my cache folders through Azure's command line via rm -rf app/cache/* and this also solved my parameters.yml issue.
I've been trying to installing JDeveloper and Weblogic server , and when trying to login as first time as Administrator in console of weblogic ,
The Server give me this error A required MBean Server is disabled which prevents the proper operation of the Weblogic Administration Console Please enable the DomainRuntimeMBean Server and the Edit MBean Server in this domain's configuration.
also I was maked search in "Oracle Forums" i found answer like that :
Also check to make sure there were no errors in the server log during
startup or when you connected to the MBean Server. Sometimes errors can
occur that cause the MBean Server to appear to be disabled. but that answer doesn't help me.
The question is "How to enable **DomainRuntimeMBean**?"
As per this link, try to delete the pending folder within your domain root and restart the server. The default domain has got some corruption in the console settings.
instead of using PC_NAME use URL
e.g. instead of My_PC:7001/console --> use 127.0.0.1:7001/console - Amartya Bandyopadhyay