cache miss

[ffa]

Hi, I keep getting a lot of the below error in my unicorn error log. I'm using version 0.10.1-rc3 and planning on updating to .11 tonight.

cache: [GET /crm] miss

cache: [GET /crm/tasks] miss

cache: [GET /crm/campaigns] miss

cache: [POST /crm/logout] invalidate, pass

cache: [GET /crm/login] miss

here is some data from my production.log for the same page (replaced the servers actual ip with <ip>):

Started GET "/crm/login" for <ip> at Thu Apr 05 17:08:13 -0500 2012

  Processing by AuthenticationsController#new as HTML

Rendered authentications/new.html.haml within layouts/application (28.2ms)

Rendered layouts/_header.html.haml (10.5ms)

Rendered layouts/_about.html.haml (2.0ms)

Rendered layouts/_footer.html.haml (14.2ms)

Rendered layouts/_tabless.html.haml (14.7ms)

Completed 200 OK in 241ms (Views: 58.9ms | ActiveRecord: 65.3ms)

[Nathan Broadbent]

Hi,

Is FFCRM actually working in your web browser, though? These just look like cache hits & misses, so I can't diagnose anything without further information

Cheers

Nathan

--
You received this message because you are subscribed to the Google Groups "Fat Free CRM Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/fat-free-crm-users/-/-F_MFU0bI0gJ.
To post to this group, send email to fat-free-...@googlegroups.com.
To unsubscribe from this group, send email to fat-free-crm-us...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fat-free-crm-users?hl=en.

[ffa]

I attached two of my production configuration files with "..." replacing full directory paths. Should I try merging in the master branch or the tag .11 to update?

Yes, FFCRM is working. But, sometimes, I get 404 page not found errors (log info below). So, I reload the page and FFCRM show up again. The error log shows that the cache misses every time. I precompiled the assets as well using RAILS_ENV="production" RAILS_RELATIVE_URL_ROOT="/crm" bundle exec rake assets:precompile. 

I am running FFCRM and Redmine on the same server using the similar unicorn.rb config file setups for both. Redmine works fine, but FFCRM seems to be having some problems.

here is excerpt from my unicorn error log that occurs before/during the 404 page not found error.

E, [2012-04-06T04:58:21.726348 #16782] ERROR -- : worker=0 PID:16786 timeout (31s > 30s), killing

E, [2012-04-06T04:58:22.495375 #16782] ERROR -- : reaped #<Process::Status: pid=16786,signaled(SIGKILL=9)> worker=0

I, [2012-04-06T04:58:32.625712 #22533]  INFO -- : worker=0 ready

On Thursday, April 5, 2012 6:18:37 PM UTC-7, nathan.f77 wrote:

Hi,

Is FFCRM actually working in your web browser, though? These just look like cache hits & misses, so I can't diagnose anything without further information

Cheers

Nathan

On Fri, Apr 6, 2012 at 6:14 AM, ffa wrote:

Hi, I keep getting a lot of the below error in my unicorn error log. I'm using version 0.10.1-rc3 and planning on updating to .11 tonight.

cache: [GET /crm] miss

cache: [GET /crm/tasks] miss

cache: [GET /crm/campaigns] miss

cache: [POST /crm/logout] invalidate, pass

cache: [GET /crm/login] miss

here is some data from my production.log for the same page (replaced the servers actual ip with <ip>):

Started GET "/crm/login" for <ip> at Thu Apr 05 17:08:13 -0500 2012

  Processing by AuthenticationsController#new as HTML

Rendered authentications/new.html.haml within layouts/application (28.2ms)

Rendered layouts/_header.html.haml (10.5ms)

Rendered layouts/_about.html.haml (2.0ms)

Rendered layouts/_footer.html.haml (14.2ms)

Rendered layouts/_tabless.html.haml (14.7ms)

Completed 200 OK in 241ms (Views: 58.9ms | ActiveRecord: 65.3ms)

--
You received this message because you are subscribed to the Google Groups "Fat Free CRM Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/fat-free-crm-users/-/-F_MFU0bI0gJ.

To post to this group, send email to fat-free-crm-users@googlegroups.com.
To unsubscribe from this group, send email to fat-free-crm-users+unsub...@googlegroups.com.

[ffa]

never mind, the update fixed this issue.