Skip to content
This repository has been archived by the owner on Mar 9, 2018. It is now read-only.

Rapns daemon process get killed #188

Open
McGar opened this issue Dec 16, 2013 · 4 comments
Open

Rapns daemon process get killed #188

McGar opened this issue Dec 16, 2013 · 4 comments

Comments

@McGar
Copy link

McGar commented Dec 16, 2013

I have a rapns process run as a daemon, but I found it always get killed in the next day after deploying with capistrano, when I try to start it by hand with "rapns env", it complains "Permission denied" for the log file generated by one of my customized daily loggers which is not for rapns, so I guess rapns get killed because of permission issue to access that log file.

So my question is why rapns tries to access the log file not for itself, I mean I have defined a custom logger for it.

@ileitch
Copy link
Owner

ileitch commented Jan 3, 2014

I need more information. Have you configured Rapns to access this log file? Rapns will use the default Rails logger unless configured otherwise.

@WindStill
Copy link

I have the problem too. When run as a daemon( bundle exec rapns production ),it has no error, but it will be killed in about 10 seconds without any error or message in the log. I can find rapns.id file included the process id, but the process is not alive.
But if run in the foreground, it is OK. It can connect to aps and deliver notification and I can recieve the message on the iOS devices.

My system is Ubuntu x86_64 and ruby version is ruby-1.9.3p194.

@McGar
Copy link
Author

McGar commented Jan 15, 2014

I did not config rapns to that log which complains "Permission denied".

@WindStill
Copy link

I'm sorry, I don't have the permission problem. Just cann't run as daemon. It didn't show any error and I could not find error infos in the log file.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants