You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 9, 2018. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: