Open bhoover10001 opened 7 years ago
A few questions:
sudo api-umbrella processes
?tail -500 /var/log/api-umbrella/elasticsearch/current
?I believe I'm using the latest version of API Umbrella.
sudo api-umbrella version returns 0.14.0
sudo api-umbrella processes returns a blank line.
There is no file or folder at /var/log/api-umbrella/elasticsearch/current The only thing in /var/log/api-umbrella/elasticsearch is a config file.
As a further data point, our IT Manager is saying that AppArmor is running on our instance of Ubuntu, and he thinks that might have stopped things from starting.
Once we removed AppArmor, it appears that we could start it, but we could not restart or stop the server.
Everything did work correctly on a brand new 16.04 Ubunutu release.
Are you able to add APIs? For its working fine but when I am trying to add APIs and I cannot able see them in analytics after publishing. let me know how to come across this problem
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 379CE192D401AB61
we are getting this error when we are trying to add api umbrella repo
As far as I remember, API-Umbrella appeared to be running.
We just tried it again on AWS with 14.04 Unbuntu and with AppArmor turned off, and got the same symptoms. It again installed with no issues at all when we upgrade the systems to Unbuntu 16.04
I'm trying to run API Umbrella on a brand new Ubuntu 14.04.5 server at AWS.
Most of API Umbrella runs , but I'm not able to get any of the reports to run. I'm also not able to restart or stop the server using sudo /etc/init.d/api-umbrella restart or stop.
I've been looking for any log files, but haven't found any that indicate why API Umbrella doesn't appear to have fully started.
If I run a ps -ef | grep api, I get the following (after startup):
root 1440 1 0 19:07 ? 00:00:01 api-umbrella /opt/api-umbrella/etc/perp root 1444 1440 0 19:07 ? 00:00:00 perpd /opt/api-umbrella/etc/perp api-umb+ 1457 1444 0 19:07 ? 00:00:02 mongod --config /opt/api-umbrella/etc/mongod.conf root 1459 1444 0 19:07 ? 00:00:00 bash /opt/api-umbrella/embedded/apps/core/current/bin/api-umbrella-nginx-reloader root 1463 1444 0 19:07 ? 00:00:00 bash /opt/api-umbrella/embedded/apps/core/current/bin/api-umbrella-geoip-auto-updater root 1465 1444 0 19:07 ? 00:00:00 nginx: master process nginx -p /opt/api-umbrella/embedded/apps/core/current/ -c /opt/api-umbrella/etc/nginx/router.conf api-umb+ 1467 1444 0 19:07 ? 00:00:03 ./bin/delayed_job --pid-dir=/opt/api-umbrella/var/run run api-umb+ 1469 1444 0 19:07 ? 00:00:00 rsyslogd -n -f /opt/api-umbrella/etc/rsyslog.conf -i /opt/api-umbrella/var/run/rsyslogd.pid api-umb+ 1471 1444 0 19:07 ? 00:00:00 traffic_cop --stdout api-umb+ 1473 1444 0 19:07 ? 00:00:01 mora -config /opt/api-umbrella/etc/mora.properties api-umb+ 1475 1444 0 19:07 ? 00:00:00 puma 3.7.0 (unix:///opt/api-umbrella/var/run/web-puma.sock) [web-app]
api-umb+ 4686 1444 0 19:08 ? 00:00:00 svlogd -ttt /opt/api-umbrella/var/log/web-puma
api-umb+ 4687 1444 0 19:08 ? 00:00:00 svlogd -ttt /opt/api-umbrella/var/log/mora
api-umb+ 4688 1444 0 19:08 ? 00:00:00 svlogd -ttt /opt/api-umbrella/var/log/nginx-reloader
devadmin 6377 2838 0 19:14 pts/0 00:00:00 grep --color=auto api
api-umb+ 1519 1471 0 19:07 ? 00:00:00 /opt/api-umbrella/embedded/bin/traffic_manager api-umb+ 1605 1465 0 19:07 ? 00:00:00 nginx: worker process api-umb+ 1606 1465 0 19:07 ? 00:00:00 nginx: worker process api-umb+ 1688 1519 0 19:07 ? 00:00:04 /opt/api-umbrella/embedded/bin/traffic_server -M --httpport 14009:fd=7 api-umb+ 1697 1475 0 19:07 ? 00:00:03 puma: cluster worker 0: 1475 [web-app]
api-umb+ 1699 1475 0 19:07 ? 00:00:03 puma: cluster worker 1: 1475 [web-app]
api-umb+ 4641 1444 0 19:08 ? 00:00:00 [java]
If I manually kill the API Umbrella services will a sudo kill -9 and then restart API Umbrella with sudo /etc/init.d/api-umbrella start I start getting a lot of messages in the current session of api-umbrella: warning: pausing for restart of ./rc.log ... api-umbrella: warning: pausing for restart of ./rc.log ...
At this point, API Umbrella appears to be running, except the analytics.
/etc/api-umbrella/api-umbrella.yml has not been changed. All lines are commented out.