Edge for private cloud 4.17.01.
I am running Edge on a server that shuts down at a fixed time every day.
Every morning crontab launches each component.
Today component startup was failing.
I would like to investigate but I do not know where to look at the log.
Please tell me where the execution log of apigee - all is stored.
Solved! Go to Solution.
solved.
Thank you very much for your help.
The log I was looking for was /var/spool/mail/root.
I executed the status check command of today I got a message that I did not have at the moment.
-------------------------------------------------------------
[root@xxxxxxxx ~] /opt/apigee/apigee-service/bin/apigee-all status
+ apigee-service apigee-cassandra status
apigee-service: apigee-cassandra: OK
+ apigee-service apigee-zookeeper status
apigee-service: apigee-zookeeper: OK
You have new mail in /var/spool/mail/root
-------------------------------------------------------------
Until yesterday there was no message "You have new mail in /var/spool / mail / root".
It is unknown why the message was outputted.
Why you shutdown every day?
What order do you use for startup?
What component didn't startup?
@Maudrit , Just a small suggestion, Please use comments for any queries / feedback / comments. Answers are strictly for answers. Converting answer to comment. Thanks !
If this is affecting your production system please open a support ticket.
Hi @Maudrit, Thank you.
I am sorry that the explanation is not enough.
There will be no service impact as it will be a talk of the test environment.
I know that the order is important.
Now all components are up and running.
The problem I am having now is not that the component did not start.
Please tell me how to investigate when the same thing happens in the future.
>Why you shutdown every day?
→We are shutting down to save AWS fee.
>What order do you use for startup?
→Control the order by execution time alone.
Start zookeeper & cassandra at 9:05
Start openldap at 9:08
Start all components at 9:10
>What component didn't startup?
→management-server, Message Processor, postgresql
@Tomoya Kimura, Are you saying that the log files are empty, maybe management and mp unable to write to logs (permission issue) and failing?
Can you check all edge directories and files are owned by 'apigee
BTW "I am running Edge on a server that shuts down at a fixed time every day" - can you elaborate on this statement?
Hi @Maruti Chand , Thank you.
Since the log is not empty, the authority is irrelevant.
Today 's date was not written.
All edge directories and files are owned by 'apigee'.
>BTW "I am running Edge on a server that shuts down at a fixed time every day" - can you elaborate on this statement?
→We are testing in a test environment.
We are shutting down to save AWS fee.
Since the log is not empty -- so what do you see in the logs? any exceptions?
I'm sorry, because I am using a translation tool.
I am inconvenienced in English.
I do not know which logs to look at in the first place.
Now I was replying while watching MessageProcessor log.
/opt/apigee/var/log/edge-message-processor/logs/startupruntaimeerrors.log
/opt/apigee/var/log/edge-message-processor/logs/system.log
/opt/apigee/var/log/edge-message-processor/logs/transactions.log
I will attach a log.
The event is improving.
I think that it has not been output to MessageProccessor log because startup failed.
I just want to know the log when apigee-all.sh fails.
If apigee-all.sh fails, will not log output?
solved.
Thank you very much for your help.
The log I was looking for was /var/spool/mail/root.
I executed the status check command of today I got a message that I did not have at the moment.
-------------------------------------------------------------
[root@xxxxxxxx ~] /opt/apigee/apigee-service/bin/apigee-all status
+ apigee-service apigee-cassandra status
apigee-service: apigee-cassandra: OK
+ apigee-service apigee-zookeeper status
apigee-service: apigee-zookeeper: OK
You have new mail in /var/spool/mail/root
-------------------------------------------------------------
Until yesterday there was no message "You have new mail in /var/spool / mail / root".
It is unknown why the message was outputted.
Thank you @Tomoya Kimura for sharing the solution with community. I am sure it will help many other, Way to go ! +1