Closed (cannot reproduce)
Project:
Octopus
Version:
6.x-2.0-rc10
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
6 Nov 2013 at 12:42 UTC
Updated:
8 May 2014 at 09:07 UTC
Jump to comment: Most recent
Comments
Comment #1
omega8cc commentedI can't reproduce this. Is this on any specific platform/distro?
Comment #2
playfulwolf commentedno, this is D723 on static/platfroms
the same continues every other day
platform is openVZ 12.04 LTS with rsyslog removed
It repeats on every morning again! So only cloning helps.
I think the same was on the BOA 2.0.9 but right now cannot check this.
On the other non-dev sites on the same server everything works fine, will check other conditions and other platforms.
What else should I check?
Comment #3
omega8cc commentedThis obviously sounds like something related to admin dos protection, but is weird if this affects only some sites (maybe cookie is affected by some modules used etc). Could you try to set
disable_admin_dos_protection = TRUEin this site INI file and see if that helps?Comment #4
playfulwolf commentedI cannot find ANY files in that directory - seems they were not created. The same for the other static/platforms/platform_name/sites/site.com, on all the sites: created now or migrated form 2.0.9
Permission problem during upgrade?
Wen verifying (any) site:
/data/disk/o1/static/platforms/d723b/sites is 775, owned by o1.ftp
Comment #5
playfulwolf commentedComment #6
omega8cc commentedThese permissions related warnings are normal in custom platforms and not related to anything here. The daily.sh script will fix them. The INI templates and any active INI files are added by daily.sh script, so it is not instant.
Comment #7
omega8cc commentedMoving to the correct queue.
Comment #8
playfulwolf commentedthe problem is gone - also only on the second day ini files appeared, had no need to modify them.
It may be related to issue when rsyslog is disabled and sysklogd is not installed.
thank you.
Comment #9
omega8cc commentedThanks for the update.
Comment #10
playfulwolf commentedIt just happened again - for no reason I was logged automatically from dev site and when accesing admin/modules - redirecting to title page
Comment #11
playfulwolf commentedComment #12
playfulwolf commentedmodifying ini file on site level does not help, nginx error logs are ok, access logs show that it was accessed the title page, not admin/modules
Comment #13
playfulwolf commentedafter running "Delete/rebuild registry" and "Cron" on Aegir panel - everything is fine again, so one of this tasks is somehow related
Comment #14
omega8cc commentedWe can't reproduce it. Feel free to reopen, but only once you will have steps/details to reproduce it.
Comment #15
playfulwolf commentedok, this is repeating every day at ~15:00, with system time set correctly, so it is no some kind of 3AM cron job
Comment #16
omega8cc commentedBOA doesn't run any task ~3 PM. There is a cron task running 9 minutes after each full hour /var/xdrago/clear.sh but I fail to see how it could be relevant.
Comment #17
playfulwolf commentednow seems that after migrating site form dev.1.mysite.com to dev.mysite.com and then cloning it to dev.1.mysite.com - everything works on dev.mysite.com that strange redirect is alive in dev.1.mysite.com
Can you try now to reproduce?
Comment #18
omega8cc commentedI can't reproduce this, unfortunately. I have also more general advice that you should never use dev-like keyword in the main site name, only in aliases. This is because it changes some default behaviours and may cause edge case WTF which is not possible to reproduce.
Comment #19
playfulwolf commentedso what would be an advice, if sitename.com is a fully active site, and some work is done on its clone, like clone.sitename.com, but there are needed active all the time those Devel*, Update* modules (which are disabled every day on non dev.* sites)
Comment #20
omega8cc commentedUse
_MODULES_SKIP="devel foo bar"to list modules you want to whitelist. Also, if you will make any module normally auto-disabled a part of a feature or profile, so internally required, it will be ignored, even if not listed in_MODULES_SKIPComment #21
playfulwolf commentedTo reproduce:
1.Create any sub.site.com, it does not matter if it has "dev" or not (probably the best is to test with dev.site.com) on custom 7.23 platform
2. Install some modules, like 50-100 of the most poplar ones: Views, Context, Fields, Jquery ui. No other special requirements
3. Log in as user1, stay logged in, do not touch site for ~24h - stay in any page, for example /admin/modules or /admin/context
4. After those 24h, simply access any page under /admin/
Comment #22
omega8cc commentedThis is by design. Feel free to customize this in
/data/conf/override.global.inc[EDIT] Fixed the link to point to the correct line in global.inc
Comment #23
playfulwolf commentedNo no no!!! This is not like that - that /admin/ page KEEPS redirecting to title page and is NOT accessible until site is cloned:
1. Access /admin/anypage - now it shows title page, also logs out
2. After login - that exact /admin/anypage is not accessible, keeps redirecting to title page
Comment #24
omega8cc commentedWell, I think this is exactly what happens here:
1. After 24 hours the cookie is already expired (no cookie effectively).
2. Since there is no cookie, 'disable_admin_dos_protection = FALSE' forces the redirect to the homepage, as designed.
What may add some confusion is the fact the browser on your computer *remembers* (caches) that redirect.
I would recommend that you try to disable /admin protection by setting 'disable_admin_dos_protection = TRUE' in the site or platform level INI file and then remember to either use different browser for testing, or clear all caches *and* restart the browser so it no longer forces the redirect.
Comment #25
playfulwolf commented'disable_admin_dos_protection = TRUE' is set on first your reply.
Yes, this is some kind of browser problem as the problem repeats itself on Firefox (primary browser) and everything is fine with SW-Iron, but I still do not understand why. If there was going the same earlier I should already seen, but now...
Restarting Firefox does not help, clearing site caches also does not but clearing Firefox cache does.
I do not think that manual clearing the browser cache is normal practice to solve such behavior, or is it?
Comment #26
omega8cc commentedIt is normal, as long as it is considered normal that browsers cache redirect requests.
Comment #27
playfulwolf commentedThis is getting annoying. Probably I haven't explained properly, what this bug does:
1. Log in as a user 1.
2. Stay logged in for more than 24h, do not do anything! Just leave that tab of the browser open.
3. Access any page which only available for user 1, like /admin/modules
You will redirected to title page as your session is expired - this is normal. Now, if you login again as a user 1 and try to access EXACTLY the same page - /admin/modules you will be automatically redirected to title page, and that page (exactly that and not any else) - /admin/modules is inaccessible until you clear all caches in browser.
It is definitely not a normal but may need to be tested on different servers and configs.
Use last stable BOA, no errors or issues.
Comment #28
omega8cc commented1. Make sure you don't force anything cookies related on local.settings.php
2. Adjust previously missing variable added in BOA-2.2.4 to match your needs
3. Make sure you don't have code/module messing with cookies
4. If nothing else helps, use disable_admin_dos_protection
Comment #29
omega8cc commented